You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/lab-services/azure-polices-for-lab-services.md
+10-2Lines changed: 10 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,15 +40,15 @@ This policy can be used to restrict [customization of lab templates](tutorial-se
40
40
|**Audit**|Labs will show on the [compliance dashboard](/azure/governance/policy/assign-policy-portal#identify-non-compliant-resources) as non-compliant when a template virtual machine is used for a lab.|
41
41
|**Deny**|Lab creation to fail if “create a template virtual machine” option is used for a lab.|
42
42
43
-
## Lab Services require non-admin user for labs
43
+
## Lab Services requires non-admin user for labs
44
44
45
45
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](tutorial-setup-lab.md#create-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.
46
46
47
47
During the policy assignment, the lab administrator can choose the following effects.
48
48
49
49
|**Effect**|**Behavior**|
50
50
|-----|-----|
51
-
|**Audit**|Labs show on the [compliance dashboard](/azure/governance/policy/assign-policy-portal#identify-non-compliant-resources) as non-compliant when non-admin accounts is not used while creating the lab.|
51
+
|**Audit**|Labs show on the [compliance dashboard](/azure/governance/policy/assign-policy-portal#identify-non-compliant-resources) as non-compliant when non-admin accounts are not used while creating the lab.|
52
52
|**Deny**|Lab creation will fail if “Give lab users a non-admin account on their virtual machines” is not checked while creating a lab.|
53
53
54
54
## Lab Services should restrict allowed virtual machine SKU sizes
@@ -60,6 +60,14 @@ During the policy assignment, the Lab Administrator can choose the following eff
60
60
|**Audit**|Labs show on the [compliance dashboard](/azure/governance/policy/assign-policy-portal#identify-non-compliant-resources) as non-compliant when a non-allowed SKU is used while creating the lab.|
61
61
|**Deny**|Lab creation will fail if SKU chosen while creating a lab is not allowed as per the policy assignment.|
62
62
63
+
## Custom policies
64
+
65
+
In addition to the new built-in policies described above, you can create and apply custom policies. This technique is helpful in situations where none of the built-in policies apply or where you need more granularity.
66
+
67
+
Learn how to create custom policies:
68
+
-[Tutorial: Create and manage policies to enforce compliance](../governance/policy/tutorials/create-and-manage.md).
69
+
-[Tutorial: Create a custom policy definition](../governance/policy/tutorials/create-custom-policy-definition.md).
0 commit comments