36 votes5 comments · Azure Active Directory » Role-based Access Control · Flag idea as inappropriate… · Admin →
We are looking into it and will update you when we know more.
Arturo via Chen
Thanks for the feedback. We will review our current Azure Monitor capability for VPN connections to see if we can provide this alerting capability, or leveraging Az Monitor Diagnostics logs/OMS.
Thanks for the feedback! We are interested in collecting feedback on this request – please vote for it if this is something you like to see.
We’re also interested in learning more what people want to use the SFTP/FTPS for and which protocol they prefer. Please feel free to leave us a comment letting us know more detail!
Program Manager, Azure Files
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:
Apologies closed in error. Reopening
Thank you for your feedback! This work is on our backlog. However, it is unlikely to happen in the coming year. We will update here if this changes.
Currently, you can configure all lab VMs to be created in an existing resource group instead of the lab creating a new RG per VM.
For ARM environments, every environment is spun up in its own RG to allow for better cost tracking user and policy management for resources created for that specific environment.
Thanks for your feedback! As more further investigate, the DevTest Labs supports VSTS Git and GitHub today. I’ve added this into the backlog. Given different Git repo offers different client for Labs to use and connect to, it’d be helpful if you could share with us which one you want to support first, so that the Labs can support them one by one. Thanks!
Domain registration is being evaluated and remains on our long term road-map. However, it is not planned for CY 2019.
Azure CDN by default ignores Vary header except when it is used with Vary: accept-encoding. This is done as the Vary header can easily cause serious cache bloat issues. Long term we are targeting feature to allow users to easily adjust this default behavior.
42 votesunder review · 0 comments · Networking » Content Delivery Network · Flag idea as inappropriate… · Admin →
118 votesunder review · 2 comments · Networking » Content Delivery Network · Flag idea as inappropriate… · Admin →
137 votesunder review · 2 comments · Networking » Content Delivery Network · Flag idea as inappropriate… · Admin →
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
An error occurred while saving the commentAlex Angas commented
Will the ability to link a resource group also be the solution for the "Deploy an Azure Resource Manager Template into a DevTest Lab" idea? Seems like it would work well for both!
When a new DevTest Lab is created, it does create a resource group consists of a Lab resource, a storage account and a virtual network. VM creation needs to happen within the Lab though, while it also creates a separate resource group just for the VM. Is it something mentioned here that you want to create VM (as “services”) from the normal VM creation flow in Azure outside of the Lab but the Lab somehow can recognize it, or are you asking for a different thing? If it’s the former, what’s the downside in your opinion that you’d prefer to do that outside of the Lab? I appreciate any clarification. Thanks!