tmacocx
My feedback
-
101 votes
tmacocx supported this idea ·
-
136 votes
tmacocx supported this idea ·
-
123 votes
Hi there,
This is one of the many improvements our development team is hoping to include in future iterations of our product. I can’t guarantee that we have the resources to get this done any time soon, but it definitely should be in the pipeline.
-Adam (Azure Billing Team)
tmacocx supported this idea ·
-
1,495 votes
Domain registration is being evaluated and remains on our long term road-map. However, it is not planned for CY 2019.
-Rohin KAn error occurred while saving the comment tmacocx supported this idea ·
-
303 votes
tmacocx supported this idea ·
-
369 votes
Upvotes: 249
<=-=Oct 4 2016 2:15PM=-=>This is similar to my feedback located here: https://connect.microsoft.com/SQLServer/feedback/details/2769130/sql-2016-temporal-tables-with-triggers. The solution I suggest is similar to this, and could be used in many different cases developing using SQL server.
<=-=Jan 10 2017 9:43AM=-=>I would love this too. The issue is that many/most applications don’t use Windows Auth in the connection to SQL Server (connection pooling issues, etc), so SQL can’t get the User information
<=-=Jan 10 2017 9:51AM=-=>@Sanford
Just to clarify, I am not asking for an “automatically store user name” feature. I’m asking for “automatically store whatever I want, based on whatever expression I provide.” So the fact that the user name may or may not be available is not really relevant.
That said, there are plenty of workarounds for various situations. I imagine that if you’re using a shared connection, you can get some notion of “user” some other…
tmacocx supported this idea ·
-
1,818 votes
Unfortunately the complexity to implement dark mode into SSMS v18 is prohibitive and this item remains unplanned. Regular updates and improvements to SQL Server Management Studio are continuing, but most of the net new innovations in the graphical tooling space can be expected to be seen in Azure Data Studio.
-Drew
tmacocx supported this idea ·
-
49 votes
tmacocx supported this idea ·
-
62 votes
Thanks for this suggestion – we currently plan to continue requiring storage so users can get the best experience possible with persisted state across all the interfaces Cloud Shell is available. Please upvote this if you agree though as we’re always listening to the community!
tmacocx supported this idea ·
-
97 votes
tmacocx supported this idea ·
-
213 votes
tmacocx supported this idea ·
-
59 votes
There are CLI commands today for moving between Consumption and Premium plans. However, we currently still do not support App Service migration. This is still planned work, and we will be investigating. Thank you for your patience
-
Carytmacocx supported this idea ·
-
53 votes
Thanks for your feedback. Currently, we don’t have any plans for C++ support in Functions. We will monitor the votes on this request to accordingly inform the priority on our backlog.
tmacocx supported this idea ·
-
107 votes
This is currently on our radar and is now planned work. Thanks for voting!
- Cary, Azure Functions
tmacocx supported this idea ·
-
32 votes
tmacocx supported this idea ·
-
44 votes
We understand the gap, and are actively reviewing the scenario around password expiry notifications
tmacocx supported this idea ·
-
174 votes
Thanks for the feedback on this. There are several ways to do Azure AD join (OOBE, bulk enrollment and Autopilot) which provide a richer experience to join devices to Azure AD. We’re continuously working to enhance those, so currently this is unplanned for the near future. Please continue to vote to help us prioritize
—
Ravitmacocx supported this idea ·
-
146 votes17 comments · Azure Active Directory » Multi-factor Authentication · Flag idea as inappropriate… · Admin →
We are planning to provide a migration path to customers from MFA server to cloud MFA.
If you are using voice and SMS, you can already use the Authentication methods APIs to migrate the data: https://docs.microsoft.com/graph/api/resources/authenticationmethods-overview
If you are using the Authenticator app, users can enable Phone Sign-in to authenticate without passwords in the cloud: https://docs.microsoft.com/azure/active-directory/authentication/howto-authentication-passwordless-phone#azure-mfa-server
tmacocx supported this idea ·
-
143 votes16 comments · Azure Active Directory » Role-based Access Control · Flag idea as inappropriate… · Admin →
We recently added deny capability to Azure’s RBAC system, in the form of deny assignments that can be set by the system only. The first Azure feature to use deny is BluePrint. We intend to add a configurable deny capability in the future, but have not yet announced any details.
Cheers,
/Stuart and Balajitmacocx supported this idea ·
-
252 votes
This is in progress, you can see a preview when creating policy thought the Conditional Access API. Coming soon to polices created in the Conditional Access UX.
tmacocx supported this idea ·
Would be interested in having Azure be a proper registrar with the ability to purchase and/or transfer domains into our tenant, or subscription, to manage.