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.
- Lab Services should enable all options for auto shutdown
- Lab Services should not allow template virtual machines for labs
- Lab Services should require non-admin user for labs
- 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 moreRelated posts
Now Available: Sort Geospatial Query Results by ST_Distance in Azure Cosmos DB
Azure Cosmos DB’s geospatial capabilities just got even better! We’re excited to announce that you can now sort query results by distanc...
Query Advisor for Azure Cosmos DB: Actionable insights to improve performance and cost
Azure Cosmos DB for NoSQL now features Query Advisor, designed to help you write faster and more efficient queries. Whether you’re optimizing ...
Azure Developer CLI: Azure Container Apps Dev-to-Prod Deployment with Layered Infrastructure
This post walks through how to implement “build once, deploy everywhere” patterns using Azure Container Apps with the new azd publ...
Accelerate Your Growth: Azure Cosmos DB Partner Acceleration Program
Accelerate Your Growth: Azure Cosmos DB Partner Acceleration Program Unlock 360° Success with the Cosmos DB Engineering Team Are you ready to ...
Transforming Field Operations with AI, Azure Maps & Dynamics 365
Efficient field operations are the backbone of successful, data-driven organizations. Yet, many businesses continue to struggle with scattered...
Failures Happen in Cloud, but how Azure Cosmos DB keeps your Applications Online
The only thing that’s constant in distributed systems is failures. No cloud platform is immune to failures — from regional outages and transie...
The `azd` extension to configure GitHub Copilot coding agent integration with Azure
This post shares how to set up the GitHub Copilot coding agent integration with Azure resources and services by using the Azure Developer CLI ...