Apologies. There was apparently a misunderstanding and the status has been corrected.
This specific feedback item is for NAT from private IP space to private IP address
We have just released integration with API management as there is a consumption plan. Please review https://docs.microsoft.com/en-us/azure/azure-functions/functions-openapi-definition to see if this meets your needs.
DNSSEC remains on our long term roadmap, however it is unlikely to be available in CY 2019. If DNSSEC is a critical and immediate requirement for your business we’d suggest that you consider evaluating 3rd party DNS hosting solutions that provide this feature.
Thank you for taking the time to vote on this request. Work on this has commenced. We will email you once it is completed.
If you are interested in participating in the preview please email back.
We are currently investigating how to implement this. The expiration status is not a directory attribute so it is not straight forward how to sync it.
228 votesunder review · 21 comments · Azure Key Vault » Managing application secrets · Flag idea as inappropriate… · Admin →
Totally agree. Right now it is like change a car (new KeyVault) when ashtray is full (separate team wants to use sets of secrets for their project)
You can remove directories by contacting the organization that owns the directory and asking them to remove you.
We can add the ability to hide them, if this is a popular request.
Microsoft is pushing Azure utilization and Win 2016 on x0 Size instances is just awful :) Guys please don`t force us to upload our core image it does not worth it. Or I just spin up one more Linux instead in my lab )
This feature is planned.