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/ai-foundry/model-inference/how-to/configure-deployment-policies.md
+15-6Lines changed: 15 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,6 +32,8 @@ Follow these steps to create and assign an example custom policy to allow specif
32
32
33
33
2. From the left side of the Azure Policy Dashboard, select **Authoring**, **Definitions**, and then select **+ Policy definition** from the top of the page.
34
34
35
+
:::image type="content" source="../media/configure-deployment-policies/create-new-policy.png" alt-text="An screenshot showing how to create a new policy definition in Azure Policies." lightbox="../media/configure-deployment-policies/create-new-policy.png":::
36
+
35
37
3. In the **Policy Definition** form, use the following values:
36
38
37
39
-**Definition location**: Select the subscription or management group where you want to store the policy definition.
@@ -97,18 +99,20 @@ Follow these steps to create and assign an example custom policy to allow specif
97
99
98
100
8. Optionally, select the **Non-compliance messages** tab at the top of the page and set a custom message for noncompliance.
99
101
100
-
9. Select **Review + create** tab and verify that the policy assignment is correct. When ready, select **Create** to assign the policy.
102
+
9. Select **Review + create** tab and verify that the policy assignment is correct. When ready, select **Create** to assign the policy.
101
103
102
104
10. Notify your developers that the policy is in place. They receive an error message if they try to deploy a model that isn't in the list of allowed models.
103
105
104
106
105
107
# [Enforce specific deployment types](#tab/deployments)
106
108
107
-
The following policy allow you to control which types of deployments are allowed in the Azure AI Services or Azure OpenAI Resources. For example, you may want to prevent them from creating deployments that result in data processed in a different region. Follow these steps to create a policy that denies creating Global processing deployment types.
109
+
The following policy allows you to control which types of deployments are allowed in the Azure AI Services or Azure OpenAI Resources. For example, you may want to prevent them from creating deployments that result in data processed in a different region. Follow these steps to create a policy that denies creating Global processing deployment types.
108
110
109
111
1. From the [Azure portal](https://portal.azure.com), select **Policy** from the left side of the page. You can also search for **Policy** in the search bar at the top of the page.
110
112
111
113
2. From the left side of the Azure Policy Dashboard, select **Authoring**, **Definitions**, and then select **+ Policy definition** from the top of the page.
114
+
115
+
:::image type="content" source="../media/configure-deployment-policies/create-new-policy.png" alt-text="An screenshot showing how to create a new policy definition in Azure Policies." lightbox="../media/configure-deployment-policies/create-new-policy.png":::
112
116
113
117
3. In the **Policy Definition** form, use the following values:
114
118
@@ -152,13 +156,15 @@ The following policy allow you to control which types of deployments are allowed
152
156
- **Assignment name**: Enter a unique name for the assignment.
153
157
- **Policy enforcement**: Make sure that the **Policy enforcement** field is set to **Enabled**. If it isn't enabled, the policy isn't enforced.
154
158
155
-
Select **Next** at the bottom of the page, or the **Parameters** tab at the top of the page.
159
+
:::image type="content" source="../media/configure-deployment-policies/assign-policy-scope.png" alt-text="An screenshot showing to assign the created policy definition to a given scope." lightbox="../media/configure-deployment-policies/assign-policy-scope.png":::
160
+
161
+
7. Select **Next** at the bottom of the page, or the **Parameters** tab at the top of the page.
156
162
157
-
7. Optionally, select the **Non-compliance messages** tab at the top of the page and set a custom message for noncompliance.
163
+
8. Optionally, select the **Non-compliance messages** tab at the top of the page and set a custom message for noncompliance.
158
164
159
-
8. Select **Review + create** tab and verify that the policy assignment is correct. When ready, select **Create** to assign the policy.
165
+
9. Select **Review + create** tab and verify that the policy assignment is correct. When ready, select **Create** to assign the policy.
160
166
161
-
9. Notify your developers that the policy is in place. They receive an error message if they try to deploy a model that isn't in the list of allowed models.
167
+
10. Notify your developers that the policy is in place. They receive an error message if they try to deploy a model that isn't in the list of allowed models.
162
168
163
169
---
164
170
@@ -171,8 +177,11 @@ To verify that the policy is assigned, navigate to **Policy** in the Azure porta
171
177
To monitor compliance with the policy, follow these steps:
172
178
173
179
1. From the [Azure portal](https://portal.azure.com), select **Policy** from the left side of the page. You can also search for **Policy** in the search bar at the top of the page.
180
+
174
181
1. From the left side of the Azure Policy Dashboard, select **Compliance**. Each policy assignment is listed with the compliance status. To view more details, select the policy assignment.
175
182
183
+
:::image type="content" source="../media/configure-deployment-policies/policy-compliance.png" alt-text="An screenshot showing an example of a policy compliance report." lightbox="../media/configure-deployment-policies/policy-compliance.png":::
184
+
176
185
## Update the policy assignment
177
186
178
187
To update an existing policy assignment with new models, follow these steps:
0 commit comments