Several improvements in this regard have since come online. Please see Morgan’s comments (posted 6/11/2018). Thanks
181 votesunplanned · AdminSQL Database feature voting forum admins (Product Owner, Microsoft Azure) responded
There are no plans to make this change, but we’ll keep this item open for voting and comments. Thanks
Planned for SQL DB- no time frame to share yet. Available in SQL Managed Instance
This is not on our roadmap and we have no plans for it long term.
Thank you for your suggestion.
Thanks for the feedback. We’re working on a lot of great stuff and will continue to expand the functionality in the preview portal to match the full portal over time. You’ll see things like this become available over time.
Thank you for this suggestion! It has been escalated to the Windows Azure engineering team for further evaluation. We will post here to gather additional information as-appropriate.
Thank you for your feedback!
Right now the workaround is to set your authentication/authorization option to enabled, but set the action for unauthenticated requests to “allow.” Then manually redirect unauthenticated requests to the secured endpoints to the authorization flow at /.auth/login/done.
We would like to add more robust support for multiple auth levels in the future. I am placing this item in “unplanned” to be used in future planning sessions.
Azure App Service TeamMike commented
I like this idea and would see it allowed because I have the same issue.
At the moment our recommended method for checking the identity of the current user is to check several attributes added to incoming requests. This is to allow your application to go completely in and out of memory on lower priced tiers without “always-on.” Check out the tutorial below for the header names.
We would like to have language specific auth functionality like this in the future. I am placing this item in “unplanned” to be used in future planning sessions.
thanks for your feedback!
Azure App Service Team
Work on this feature has started. Will update here when this becomes generally available.
Thank you for your suggestion and votes.
The Azure Resource Manager team is actively investigating the scenarios around renaming resource groups. To help us better understand the use-cases and to determine which implementations may be viable to address the problem, we would appreciate if you could fill out this 3-minute survey:
Thank you for your feedback. While it is unlikely we’ll address this suggestion in the near future, we’ll reassess based on the number of votes it receives.
Azure Search Product Team
We are taking this feedback and working to improve our messages.