+1 to having a way to organize secrets. It would be even better to integrate that with RBAC.
While it is true that non-sensitive data should go in a different type of key/value store (like Azure Configuration - https://azure.microsoft.com/en-us/services/app-configuration/), we still have dozens of secrets to maintain for any reasonably-sized service.
Key Vault should provide features to do this, such as folders or tags on individual secrets/keys/certs.
It's a duplicate, but I'll vote for this one too.
+1. I don't understand why it is a requirement to include access policies.
It certainly complicated ARM template deployments for existing Key Vaults, since providing an empty access policies list just wipes out everything that is there.
+1 to all the comments below. What legitimate reason is there for imposing this limit?
291 votesstarted · 33 comments · Azure Key Vault » Managing application secrets · Flag idea as inappropriate… · Admin →
No kidding... 2+ years and countingTraber shared this idea ·
This would be extremely useful, and just a simple text field on the secret. It _shouldn't_ be difficult
95 votes19 comments · Azure Key Vault » Managing application secrets · Flag idea as inappropriate… · Admin →
Key Vault Notification feature is currently in Public Preview and available in all public regions.
Notification overview :
340 votes21 comments · Azure Monitor-Log Analytics » Log Management and Log Collection Policy · Flag idea as inappropriate… · Admin →
This is currently under development, scheduled to be in preview later in 2018
Any update here? Per the last admin response, the preview was supposed to be in late 2018, but I haven't heard anything about it yet.
86 votes7 comments · Azure Monitor-Log Analytics » Log Management and Log Collection Policy · Flag idea as inappropriate… · Admin →
This feature is already in progress, limited preview is expected later in 2018
264 votes17 comments · Azure Monitor-Log Analytics » Workspace Settings / Administration · Flag idea as inappropriate… · Admin →
The platform currently relies on the uniqueness of workspaces names. The effort required to support workspace rename can’t fit in current semester due to higher priority items unfortunately, but we will consider it for the next semester.