Loading...

What’s new with Azure Policy for Lab Services?

What’s new with Azure Policy for Lab Services?

Azure Lab Services has added 4 built-in Azure policies. Azure Policy help IT administrators to manage and prevent issues automatically.  Policy definitions enforce rules and effects for your resource. This blogpost summarizes the new policies available in the August 2022 Update for Azure Lab Services.

  1.  Lab Services should enable all options for auto shutdown
  2. Lab Services should not allow template virtual machines for labs
  3. Lab Services should require non-admin user for labs
  4. Lab Services should restrict allowed virtual machine SKU sizes

For a full list of built-in policies, including policies for Lab Services, see Azure Policy built-in policy definitions.

 

Lab Services should enable all options for auto shutdown

This policy is used to enforce that all shutdown options are enabled while creating the lab. During policy assignment, lab administrators can choose the following effects.

 

Effect Behavior
Audit Labs will show on the compliance dashboard as non-compliant when all shutdown options are not enabled for a lab.
Deny Lab creation will fail if all shutdown options are not enabled.

 

Lab Services should not allow template virtual machines for labs

This policy can be used to restrict customization of lab templates. While creating a new lab, there is an option either to “create a template virtual machine” or “Use virtual machine image without customization”. If this policy is enabled, only the “Use virtual machine image without customization” is allowed . During policy assignment, lab administrators can choose the following effects.

 

Effect Behavior
Audit Labs will show on the compliance dashboard as non-compliant when a template virtual machine is used for a lab.
Deny Lab creation to fail if “create a template virtual machine” option is used for a lab.

 

Lab Services require non-admin user for labs

This policy is used to enforce using non-admin accounts while creating a lab. With the August 2022 Update, you can choose to add a non-admin account to the VM image. This new feature allows you to keep separate credentials for VM admin and non-admin users. For more information to create a lab with a non-admin user, see Tutorial: Create and publish a lab, which shows how to give a student non-administrator account rather than default administrator account on the “Virtual machine credentials” page of the new lab wizard.
During the policy assignment the lab administrator can choose the following effects.

 

Effect Behavior
Audit Labs show on the compliance dashboard as non-compliant when non-admin accounts is not used while creating the lab.
Deny Lab creation will fail if “Give lab users a non-admin account on their virtual machines” is not checked while creating a lab.  

 

Lab Services should restrict allowed virtual machine SKU sizes

This policy is used to enforce which SKUs are allowed to be used while creating the lab. For example, a lab administrator might want to prevent educators from creating labs with GPU SKUs since they are not needed for any classes being taught. This policy would allow lab administrators to enforce which SKUs are allowed to be used while creating the lab. During the policy assignment the Lab Administrator can choose the following effects.

 

Effect Behavior
Audit Labs shows on the compliance dashboard as non-compliant when a non-allowed SKU is used while creating the lab.
Deny Lab creation will fail if SKU chosen while creating a lab is not allowed as per the policy assignment.

 

In tomorrow’s blogpost we’ll see how to use the “Lab Services should restrict allowed virtual machine SKU sizes” azure policy.

 

Thanks,

Lab Services Team

References:

 

 

Published on:

Learn more
Azure Lab Services articles
Azure Lab Services articles

Azure Lab Services articles

Share post:

Related posts

Microsoft Azure Fundamentals #2: Designing Real-Time Bi-Directional Sync Between Dataverse and Azure SQL for Multi-Region Deployments

Here’s a detailed technical breakdown of designing a real-time bi-directional sync between Dataverse and Azure SQL for multi-region deployment...

4 hours ago

Azure DevOps local MCP Server is generally available

Today we are excited to take our local MCP Server for Azure DevOps out of preview 🥳. Since the initial preview announcement, we’ve work...

1 day ago

Announcing the new Azure DevOps Server RC Release

We’re excited to announce the release candidate (RC) of Azure DevOps Server, bringing new features previously available in our hosted version....

6 days ago

How to Integrate Azure Service Bus with Microsoft Dynamics 365 CRM Step by Step with Example?

Keeping data flowing between applications is critical in today’s connected business world. Organizations using Microsoft Dynamics 365 CR...

10 days ago

Enhancing Secure Sign-Ins with Temporary Access Pass in Azure Active Directory

Introduction While working on improving user account recovery scenarios, a common challenge often arises: how to securely allow a user to sign...

11 days ago

Azure SDK Release (September 2025)

Azure SDK releases every month. In this post, you'll find this month's highlights and release notes. The post Azure SDK Release (September 202...

11 days ago

Batch Processing Triggered Pipeline Runs in Azure Synapse

This post describes a pattern for batch processing triggered pipeline runs in Azure Synapse

12 days ago

Reliably refreshing a Semantic Model from Azure Data Factory or Synapse Pipelines

This post describes a pattern for reliably refreshing Power BI semantic models from Azure Data Factory or Azure Synapse Pipelines.

12 days ago
Stay up to date with latest Microsoft Dynamics 365 and Power Platform news!
* Yes, I agree to the privacy policy