Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more here.

Lab Services

Azure Lab Services is a service that enables you to easily set up and provide on-demand access to various systems and software for any workload: teaching a class, setting up a development or test environment, or running trials with customers. Manage and scale your group’s resources in lab environments, while minimizing waste and controlling cost. Choose between the two lab types, classroom lab or devtest lab, for an experience that is tailored to your scenario.

Visit the Azure Lab Services page to learn more.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Bastion support for Classroom Labs

    Similar to DevTest Labs, and perhaps even more important, Classroom Labs should support Bastion Host or any other mechanism that gets around port restrictions. Students should be able to get to their virtual machines without having to ask an IT department to grant access through their firewall to non-standard ports (which gets denied more often than not anyway).

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Classroom Labs  ·  Flag idea as inappropriate…  ·  Admin →
  2. Give Warning to Users About Shutdown

    Currently, when a shutdown is initiated in the schedule, it force quits all programs and shuts down the machine without any notice to the user. This abrupt of a shutdown could result in a loss of work if the user is active at the time of the scheduled shutdown. Please provide an option when scheduling a shutdown to give notice to the user (see attached for an example). This can be achieved with the simple command: shutdown /s /t 300

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Classroom Labs  ·  Flag idea as inappropriate…  ·  Admin →
  3. Copying custom images from one DTLab to another

    Due to the RBAC role hard limit of 2000 per subscription, we find ourselves creating new subscription and new DTLabs as a work around. There is not a straight forward way for us to copy custom images created in the old DTLabs to the new ones. It would be nice if there is a way to just copy custom images without going through multiple steps of spinning up a new VM and sysprep it and turn it back to a VHD image again, just so we can copy it to the new DTLab.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Allow mandatory artifacts with parameters set by lab admins

    The new feature to have mandatory artifacts is great, but doesn't allow artifacts which require parameters, to keep the process simple.

    It would be good if we could enable mandatory artifacts which do use parameters, provided the parameters have already been provided by the lab admins. This gives greater flexibility on the mandatory artifacts we can set up, but still keeps the VM creation process simple for the user.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  5. Allow devtestlab resource types in private repo templates

    Currently only non devtest labs resource types are supported in creating resources in environments via private repo based around templates as bases... But we may need a scenario where we create a custom image after the vm is sys prepped in devtest labs and create resources based on that image.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. 6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. host

    Access entire lab via public FQDN.
    Be able to have a public hostname (rds.contoso.com) where you RDP to and it automatically drops you into a claimable VM in the lab pool.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. show vm cost on Allowed virtual machine sizes page

    I would be perfect if vm cost can be optioned to show when choosing VM size on Allowed virtual machine sizes blade under Azure DTL policy.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Sort the list of custom images

    I have a bunch of custom images in my lab. i want to be able to sort them so that i can see them in a particular order - the order i want, not the order you want.

    Also i want additional fields. For instance, created date or last VM created date.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. 6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. ability to hide repository information

    We need to share our labs and artifacts with many users outside of our team and also sometimes with external customers.
    As the repository is private and hosted on internal servers, for security reasons we would like ability to hide the repository source information for all the users. It would be nice if
    1. Go to repository option [click 3 dots against your repository] can be disabled.
    2. Ability to disable the click on selected repositories can be provided, so user cannot see repository details in configuration.

    Thanks,
    Sachin

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for your suggestion! There are some ways to solve these problems today: 1) for “go to repository” menu item from the three dots, you can control the permission at the repository level (i.e. don’t give users read permission to your repo), so that even if users click that item, they will get access deny when trying to access the repo. 2) to disallow users to see repo details, you can create a custom role and remove the read permission to the repo details from the built-in DevTest Labs User role. Do these solutions work with you? If not, could you explain the reason so that we can design the right solution for you?

  12. Anti-malware installation

    It would be great if, as part of provisioning a new VM, you could specify that Microsoft Anti-Malware (or other products) is to be installed as well. Current work-around is to push it out afterwards from Security Center but this allows for a little too much human error

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. Support Microsoft.DevTestLab/labs/virtualMachines in Devtest Labs private repo

    Currently in the ARM template saved in DevOps private repo, we can only use Microsoft.Compute/virtualMachines.

    If Microsoft.DevTestLab/labs/virtualMachines is defined, it will throw out a error "Resource type \"Microsoft.DevTestLabs/labs\" and its nested resource types are not supported in this flow".

    I think the ARM template should support both in the private repo. In many use cases, it's much convenient to use Labs/virtualMachines to deploy the instance. For example, you can define artifacts and it's easier to reference vnet used in DTL.

    In https://social.msdn.microsoft.com/Forums/azure/en-US/370221a9-3a27-40b0-abf9-853df57dd9be/deploy-lab-via-arm-template-using-a-sysprepped-custom-image-vhd-fails?forum=AzureDevTestLabs

    Leo from Microsoft mentioned it was in the backlog since 2017.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  DevTest Labs - ARM Environments  ·  Flag idea as inappropriate…  ·  Admin →
  14. Ability to configure lab settings programmatically

    Currently there seems to be no way to programmatically (without the use of the Portal by manually clicking) set DevTest Labs settings like:
    - globally setting the Encryption Set
    - enabling Browser Connect
    - defining VM placement settings (in one RG vs. each in separate RG)

    Please correct me if I'm wrong, but this is a real blocker when doing the settings as automated as possible.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  DevTest Labs - ARM Environments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Include version number used from Shared Image Gallery in the UI

    Posted on behalf of SimonG-2988:
    https://docs.microsoft.com/en-us/answers/questions/76577/index.html

    "The fact that using labs and lab formulas, we can now link to a shared image gallery image is fantastic. But the GUI simply reports that the VM base is the gallery image name - how do we know which version of the image was used (latest or 1.0.3, 1.0.4 etc.)? The GUI is now a little lacking in info. Before, when we had to spin up a VM and turn it into a custom lab image version, the base was reported as the custom image name (which included our image version). Please can…

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  16. Ability to disable or hide [Connect] button if [Browser connect] is enabled by Bastion integration

    We have both [Connect] and [Browser connect] button for VMs if we configure DevTest Labs integrated with Azure Bastion. (Public Preview right now.) It would be great if we could disable or hide [Connect] button for specific users when DevTest Labs owner wants users to connect VMs only from [Browser connect].

    • To create custom role without '.../getRdpFileContents/action' and assign users doesn't help because users have Owner permission to VMs after they claim.
    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  DevTest Labs - Virtual Machines  ·  Flag idea as inappropriate…  ·  Admin →
  17. Enable Tagging to either be applied via Policy or inherited from the Lab Account

    We have to apply Tags to resources so we can charge schools for Azure usage. We use Policies on Resource Groups to Tag resources automatically on creation.
    The Lab Account has it Tags created correctly on creation - however, any Labs created within the account do not have tags applied. (The back-end is probably not in the resource group)

    Can Labs created in a Lab Account obey any polices as if they are also in the resource group - or can they have the option to inherit the tags of the Lab Account they belong to.

    We cannot use this…

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  Classroom Labs  ·  Flag idea as inappropriate…  ·  Admin →
  18. Assign multiple VMs to a student with their own vnet so they can create a network

    We have an in house lab experience where we can assign multiple windows/Linux VMs to students, these all come with a public IP and part of a Vnet so they can create their own network and test client/server applications between them

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Classroom Labs  ·  Flag idea as inappropriate…  ·  Admin →
  19. Set up auto-shutdown from Azure cloud shell

    Set up auto-shutdown from Azure cloud shell.
    Can't find anything existing.
    Somethin like:
    az vm command with --set-autoshutdown --zone UTC --time 2:AM --reapeat true

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  DevTest Labs -PowerShell and CLI  ·  Flag idea as inappropriate…  ·  Admin →
  20. Auto-shutdown is basically useless without auto-startup!

    Adding auto-shutdown to production VMs could be interesting if there was an auto-startup! Pretty incredible to have to say it, really.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base