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. Lab/user policy to deny claiming/unclaiming VMs

    Please add the ability to completely disable claimable VMs in DevTest Labs. The feature is abused to generate tons of unclaimed VMs in the lab under VMs-per-user policy.

    1 vote

    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 - Security  ·  Flag idea as inappropriate…  ·  Admin →
  2. 1 vote

    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 →
  3. Have an option to adjust notification time before auto-shutdown

    Right now, automatically, the notification time before auto-shutdown is 30 minutes (unless it can be specified somewhere else and I haven't found it). It would be nice to be able to adjust it to something like 60 minutes. This would be nice if we could control this for each VM.

    1 vote

    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 →
  4. Progress meter for Dev Test Lab creation

    Creating VM's by nature can be slow, seeing progress or maybe diagnostic logs would help elevate frustration when spinning up this product.

    1 vote

    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 →
  5. The option to suspend auto shutdown for a few hours

    It would be a very nice feature to suspend the auto shutdown for a few hours. I.e. when you are working late or have a long running process that you expect to finish a few hours after the auto shutdown time.

    1 vote

    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 →
  6. auto shutdown email notification needs also webhook field to be filled

    Cannot add email address for VM auto shutdown.
    After switching "yes" at "Send notification before auto-shutdown - filling only the "Email address" field correctly -
    while "Webhook URL" is empty -
    the "Save" button does not get enabled - it is still disabled.

    1 vote

    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

    3 comments  ·  Flag idea as inappropriate…  ·  Admin →

    This is not a known issue. Ideally, user should be able to enter the email address only and click the Save button. This may be a bug we may need to investigate with your lab as we are not able to reproduce it on our end.
    Are you still experiencing this issue? If so can you please create a support ticket with us so that we can look into your lab.
    Link: https://portal.azure.com/?feature.customPortal=false#blade/Microsoft_Azure_Support/HelpAndSupportBlade/overview

  7. Use a single resource group for arm deployments

    DTL now offers the ability to use a single resource group for all VMs. It would be nice to extend this to arm based environments too. This for easier policy management

    1 vote

    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. Claim VM using a specific tag

    "az lab vm claim" command in CLI should allow claiming of VMs that tagged with a specific tag:
    az lab vm claim -tag XYZ <rest of params>

    This would be useful when VMs are created in different ways, and then tagged appropriately. For example I might create 50 VMs with a certain version of my app, and tag them as "V1", and 50 more VMs with a newer version of my app tagged as "V2". And users should be able to claim a VM from any of the two versions by specifying the tag in the command.

    1 vote

    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 →
  9. 1 vote

    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

    need-feedback  ·  2 comments  ·  Classroom Labs  ·  Flag idea as inappropriate…  ·  Admin →
  10. Having the right to stop/start a VM should imply also having the right to schedule automatic shutdown.

    It makes little sense to me to separate the two rights for the same VM. It would simplify administration if I didn't have to contact a manager just to not have the VM suddenly die when I need to work late.

    1 vote

    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  ·  DevTest Labs - Virtual Machines  ·  Flag idea as inappropriate…  ·  Admin →

    The schedule is applied at two levels viz. lab level and VM level.
    Depending on the policy applied by your lab owner, you as a lab user can modify the schedule on your machine.
    The policies include:
    - Lab user can modify schedule and/or opt out
    - Lab user can modify schedule but cannot opt out
    - Lab user cannot modify schedule nor opt out

    If you are not able to modify the schedule, it might be because of the policy your lab owner has set on the lab.

    Hope this helps!

  11. Way to change auto-shutdown settings programmatically per-instance (rather than lab wide)

    Currently you can set the auto-shutdown settings on a lab-wide basis either manually or in an ARM template that creates a DevTest Labs instance. However, when you create environments using an ARM template base which creates multiple VM's, they all have the auto-shutdown settings of the DevTest Lab.

    If the Lab policy allows the user to change the Auto-Shutdown settings, then you can manually change them on a per-VM basis through the UI, but there doesn't appear to be a way of changing those settings programmatically (either in the ARM template that creates the environment or through PowerShell after creation).

    1 vote

    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 →
  12. would be nice to get a "power this machine now" - link, with notification mail. to allow for it to shut down and have a handy up link.

    would be nice to get a "power this machine now" - link, with notification mail. to allow for it to shut down and have a handy up link.

    1 vote

    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 →
  13. Is there is possibility to define create a pool of Auto shutdown VM's and set shut down if idle, but start when load exceed 50%

    Is there is possibility to define create a pool of Auto shutdown VM's and set shut down if idle, but start VM when load exceeds on any server in pool by 50-60%

    1 vote

    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 →
  14. 1 vote

    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  ·  Classroom Labs  ·  Flag idea as inappropriate…  ·  Admin →
  15. Give permissions to Manage Resource Groups Created by VMs in DevTest Lab

    When Creating a VM in Dev Test Labs they are created in new Resource Groups. Since Resource Groups can not contained within each other, they are created "parallel" to the Resoruce Group the DevTest Lab is contained in.

    The newly created Resoruce Groups should automatically have the same Users with the same Roles assigned to them, so i can manage and configure the RBAC on one Resource Group containing the DevTest Lab.

    1 vote

    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  ·  DevTest Labs - Virtual Machines  ·  Flag idea as inappropriate…  ·  Admin →
  16. Bug found in Azure Pipelines Agent - DevTest Labs

    To reproduce, create a new Windows 10 VM in DevTest Labs with an ampersand (&) in the password.

    Add the Azure Pipelines Agent to configure an agent in Azure DevOps.

    Enter details in the artifact configuration pane, and specify the VM user/password for logon. Use the saved secret option.

    Notice that the pipeline agent fails with the following message:
    Testing agent connection.
    2019-01-24 14:36:46Z: Settings Saved.
    ERROR: Invalid windows credentials entered. Try again or ctrl-c to quit

    1 vote

    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  ·  DevTest Labs - Virtual Machines  ·  Flag idea as inappropriate…  ·  Admin →
  17. VM size explanation column

    Would be great to have a description field for VM size list to explain customers the use case of specific vm varieties

    1 vote

    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 →
  18. Value of input parameter _artifactsLocation should be set with a trailing '/' when provisioning a lab from a custom ARM template

    Using uri function (https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-template-functions-string#uri) in the ARM template is not possible because it truncates the end of parameter _artifactsLocation:

    Currently Azure sets parameter _artifactsLocation to a value like this: https://.blob.core.windows.net/artifacts/YYY/ZZZ
    As a result, function uri truncates the end (ZZZ) and returns https://
    .blob.core.windows.net/artifacts/YYY
    This prevents to call nested resources using function uri
    To fix this, _artifactsLocation value should have a trailing "/" like this: https://***.blob.core.windows.net/artifacts/YYY/ZZZ/

    1 vote

    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 →
  19. Better logging for artifacts

    I'm trying to use the "Run Powershell" artifact to execute two lines of Powershell. When I run these on the command line in my VM it takes about 3 seconds to execute. I've been waiting over 15 minutes for my VM to finish creating in the portal, and there is no way to see the status of my script.

    Can you please make this a bit more transparent to the user? Like maybe post the output of the script somewhere in the logs? I looked everywhere but couldn't find any clues as to what's going wrong with my script. A…

    1 vote

    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 →
  20. It is very confused that a scheduled shutdown at 19:00 existing and DO NOT notice the users.

    It is very confused that a scheduled shutdown at 19:00 existing and DO NOT notice the users.

    1 vote

    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 →
  • Don't see your idea?

Feedback and Knowledge Base