Planned for SQL DB- no time frame to share yet. Available in SQL Managed Instance
An error occurred while saving the commentTomasz K commented
Managed instances in preview (as per https://docs.microsoft.com/en-us/azure/sql-database/sql-database-managed-instance-transact-sql-information ) " GETDATE() and other built-in date/time functions always returns time in UTC time zone. See GETDATE". This will be available in GA?
Thank you for your feedback. We’re considering this for a future release of Azure Search.
Azure Search Product Team
We can add support for deleting resources, if that’s important. Confirming via a secret would require additional work from the ARM team to support that flow. Fingerprint confirmation is easy enough, since that’d just be an added confirmation. Deleting locked resources is also do-able with an extra confirmation.
207 votes23 comments · Azure Active Directory » Self-Service Password Reset · Flag idea as inappropriate… · Admin →
Hi folks! I apologies for the delay in response and I deeply appreciate your feedback. I understand how important this feature is for your and your users. We do not yet have plans to implement this feature, but please keep voting if this is important to you to help us prioritize appropriately.
Thank you for your feedback!
We would like to add more robust OData support. I am placing this item in “unplanned” to be used in future planning sessions.
Azure App Service Team
We have made some great progress on this idea and most of our services today do support move resources across groups.
We are still working towards 100% support and while we do that it would be great if you can help us prioritize the missing services.
Please file individual asks on each service category present in uservoice and vote for it.
Azure Portal Team
AAD currently requires a strict directory scoping. We can investigate options if this is a popular request.
We are likely to support this in phases. Stay tuned for more details.
We have been considering all of the risks and investigating the steps required to ensure we implement this feature with high positive impact and low to no negative impact.
After this investigation we have decided we will enable Pay-As-You-Go customers the option to configure a spending limit on a Pay-As-You-Go subscription, with appropriate safeguards and measures to prevent both service abuse and production service failure.
We have not yet finished determining the details of what this feature will look like, nor do we have a timeline for release, but we have heard your voices and have added this feature to our backlog.
Thanks for your continued feedback,
-Adam (Azure Billing Team)