Thank you for taking the time to vote for this item.
We are glad to let you know that the work to support this has commenced.
any update on when this functionality is expected to be ready? We also do chargebacks at the Subscription level and this functionality would be of tremendous value to us.
Agree, it would be very helpful if an MSI created in Azure could be synced down to On-Premise AD so it could be used to authenticate with an on-premise VM or SQL Server.
Agreed. this is proving to be a problem in our setup as well. We have two VMs in our backend pool running 2 sites in IIS. Each site is configured with an SSL binding. If any of the SSL Bindings have the Require Server Name Identification checkbox enabled, the Application Gateway shows them as failed in the Backend Health blade.
Thank you for all the votes and feedback. We have started work on this and the capability will be supported soon. If you would like to get in touch with us to discuss your scenarios, please fill this form: https://aka.ms/ApplicationGatewayCohort
Key Vault Notification feature is currently in Public Preview and available in all public regions.
Notification overview :
Any followup or ETA on this request?
Agreed. We issue many SSL Certificates that are only needed internally and we always use our own internal CA when doing so. Having this type of integration would be very helpful.
261 votesstarted · 29 comments · Azure Key Vault » Managing application secrets · Flag idea as inappropriate… · Admin →
82 votes17 comments · Azure Key Vault » Managing application secrets · Flag idea as inappropriate… · Admin →
Agreed. We are trying to standardize our Azure DevOps Release Variables to store all Secrets in KeyVault. The lack of support for Underscores makes this approach impossible for us to fully adhere to since the Variable replacements will not work since most of the variables we need replacements for have underscores in their names.
We are looking at this but it is not on our immediate roadmap. Will update here if this changes.
Thank you for your suggestion.
199 votes10 comments · Azure Kubernetes Service (AKS) » Integration with Azure services · Flag idea as inappropriate… · Admin →
Thanks. This is similar to other feedback we have and this will help us to prioritize this as a feature we can add. I will update here once we have concrete plans to implement.
To get integration stated, we’ve added links to Aqua and Twistlock from overview within a configured registry.
Over time, we’ll provide a more integrated experience, where ACR has vulnerability scanning integrated into the image listing.
DevTest Labs now supports integration with Azure Shared Image Gallery (SIG).
For the scenario you outlined above,
You can extract the images for the VMs you would like to move to a lab
Upload these images to the shared image gallery
Attach the shared image gallery to your lab
Create lab VMs from these images
Upload images to a SIG: https://docs.microsoft.com/en-us/azure/virtual-machines/windows/shared-images-portal
Attach a SIG to a lab: https://docs.microsoft.com/en-us/azure/lab-services/configure-shared-image-gallery
Create a lab VM from a SIG image: https://docs.microsoft.com/en-us/azure/lab-services/add-vm-use-shared-image
We do have this feature on our backlog, but do not have a timeline for it as yet.
We will update the status as soon as we have an ETA.
Can you share with us the type of test environments in these resource groups that you would like to be under DevTest Lab policies?
Would be useful, especially if we could expose objects in blob storage.