|
| 1 | +--- |
| 2 | +title: Manage AI model deployment in Azure AI Foundry (Preview) |
| 3 | +description: Control AI model deployment in Azure AI Foundry Portal with built-in Azure Policy definitions. Learn how to govern and manage model deployments effectively. |
| 4 | +#customer intent: As an IT admin, I want to control the deployment of AI models in Azure AI Foundry Portal so that I can ensure compliance with organizational policies. |
| 5 | +author: jonburchel |
| 6 | +ms.author: jburchel |
| 7 | +ms.reviewer: aashishb |
| 8 | +ms.date: 09/22/2025 |
| 9 | +ms.topic: how-to |
| 10 | +ms.service: azure-ai-foundry |
| 11 | +ai-usage: ai-assisted |
| 12 | +--- |
| 13 | + |
| 14 | +# Control AI model deployment with built-in policy in Azure AI Foundry portal (Preview) |
| 15 | + |
| 16 | +Azure Policy provides built-in policy definitions that help you govern the deployment of AI models in Azure AI Foundry Portal. You can use |
| 17 | +these policies to control what models your developers can deploy in Azure AI Foundry portal. |
| 18 | + |
| 19 | +## Prerequisites |
| 20 | + |
| 21 | +- An Azure account with an active subscription. If you don't have one, create a [free Azure account](https://azure.microsoft.com/free/). Your |
| 22 | + Azure account lets you access the Azure AI Foundry portal. |
| 23 | + |
| 24 | +- Permissions to create and assign policies. To create and assign policies, you must be an [Owner](/azure/role-based-access-control/built-in-roles#owner) or [Resource Policy Contributor](/azure/role-based-access-control/built-in-roles#resource-policy-contributor) at the Azure subscription or resource group level. |
| 25 | + |
| 26 | +- Familiarity with Azure Policy. To learn more, see [What is Azure Policy?](/azure/governance/policy/overview). |
| 27 | + |
| 28 | +## Enable the policy |
| 29 | + |
| 30 | +1. From the [Azure portal](https://portal.azure.com/), select **Policy** from the left side of the page. You can also |
| 31 | + search for **Policy** in the search bar at the top of the page. |
| 32 | + |
| 33 | +1. From the left side of the Azure Policy Dashboard, select **Authoring**, **Definition**, and then search for `\[Preview\]: Cognitive Services Deployments should only use approved Registry Models` in the search bar within the page. You can also directly navigate to [policy definition creation page](https://ms.portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetail.ReactView/id/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2Faafe3651-cb78-4f68-9f81-e7e41509110f/version/1.0.0-preview/scopes~/%5B%22%2Fsubscriptions%2Fa4393d89-7e7f-4b0b-826e-72fc42c33d1f%22%2C%22%2Fsubscriptions%2Fd128f140-94e6-4175-87a7-954b9d27db16%22%2C%22%2Fsubscriptions%2F562da9fc-fd6e-4f24-a6aa-99827a7f6f91%22%5D/contextRender~/false). |
| 34 | + |
| 35 | +1. Select on **Assign** to assign the policy: |
| 36 | + |
| 37 | + - **Scope**: Select the scope where you want to assign the policy. The scope can be a management group, subscription, or resource group. |
| 38 | + - **Policy definition**: this section should already have a value of `\[Preview\]: Cognitive Services Deployments should only use approved Registry Models`. |
| 39 | + - **Assignment name**: Enter a unique name for the assignment. |
| 40 | + |
| 41 | + The rest of the fields can be left as their default values or you can customize as needed for your organization. |
| 42 | + |
| 43 | +1. Select **Next** at the bottom of the page or the **Parameters** tab at the top of the page. |
| 44 | + |
| 45 | +1. In the **Parameters** tab, deselect **Only show parameters that needs input or review** to see all fields: |
| 46 | + |
| 47 | + - **Effect**: Set to [**Deny**](/azure/governance/policy/concepts/effect-deny). |
| 48 | + |
| 49 | + > [!NOTE] |
| 50 | + > Using the [**audit**](/azure/governance/policy/concepts/effect-audit) option allows you to configure the policy to log information to your own compliance dashboard. |
| 51 | +
|
| 52 | + - **Allowed Models Publishers**: This field expects a list of **publisher's name** in quotation and separated by commas. Here's an example that shows where to find a publisher name: |
| 53 | + |
| 54 | + 1. Go to [Azure AI Foundry model catalog](/azure/ai-foundry/how-to/model-catalog-overview) in Foundry Portal |
| 55 | + 1. Select a model (for example, GPT-5). |
| 56 | + 1. You find publisher name on the model card as shown in the following screenshot. For example, in this case it's `OpenAI`. |
| 57 | + |
| 58 | + :::image type="content" source="media/model-deployment-policy/gpt-5-model-card.png" alt-text="Screenshot of Azure AI Foundry model catalog showing a model card with the publisher name highlighted."::: |
| 59 | + |
| 60 | + - **Allowed Asset Ids**: This field expects a list of **model asset ids** in quotation and separated by commas. |
| 61 | + |
| 62 | + To get the model asset ID strings and model publishers' name use the following steps: |
| 63 | + |
| 64 | + 1. Go to the [Azure AI Foundry model catalog](/azure/ai-foundry/how-to/model-catalog-overview). |
| 65 | + 1. For each model you want to allow, select the model to view the details. In the model detail information, copy the **Model ID** value. For example, the value might look like `azureml://registries/azure-openai/models/gpt-35-turbo/versions/3` for GPT-3.5-Turbo model. |
| 66 | + |
| 67 | + > [!IMPORTANT] |
| 68 | + > The model ID value must be an exact match for the model. If the model ID isn't an exact match, policy doesn't work as expected. |
| 69 | +
|
| 70 | + 1. Select **Review + create** tab and verify that the policy assignment is correct. When ready, select **Create** to assign the policy. |
| 71 | + 1. Notify your developers that the policy is in place. They receive an error message if they try to deploy a model that isn't on the list of allowed models. |
| 72 | + |
| 73 | +## Monitor compliance |
| 74 | + |
| 75 | +To monitor compliance with the policy, follow these steps: |
| 76 | + |
| 77 | +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. |
| 78 | + |
| 79 | +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. |
| 80 | + |
| 81 | +## Update the policy assignment |
| 82 | + |
| 83 | +To update an existing policy assignment with new models, follow these steps: |
| 84 | + |
| 85 | +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. |
| 86 | +1. From the left side of the Azure Policy Dashboard, select **Assignments** and find the existing policy assignment. Select the ellipsis (...) next to the assignment and select **Edit assignment**. |
| 87 | +1. From the **Parameters** tab, update the **Allowed models** parameter with the new model IDs. |
| 88 | +1. From the **Review + Save** tab, select **Save** to update the policy assignment. |
| 89 | + |
| 90 | +## Best practices |
| 91 | + |
| 92 | +- **Granular scoping**: Assign policies at the appropriate scope to balance control and flexibility. For example, apply at the subscription level to control all resources in the subscription, or apply at the resource group level to control resources in a specific group. |
| 93 | +- **Policy naming**: Use a consistent naming convention for policy assignments to make it easier to identify the purpose of the policy. Include information such as the purpose and scope in the name. |
| 94 | +- **Documentation**: Keep records of policy assignments and configurations for auditing purposes. Document any changes made to the policy over time. |
| 95 | +- **Regular reviews**: Periodically review policy assignments to ensure they align with your organization's requirements. |
| 96 | +- **Testing**: Test policies in a nonproduction environment before applying them to production resources. |
| 97 | +- **Communication**: Make sure developers are aware of the policies in place and understand the implications for their work. |
| 98 | + |
| 99 | +## Related content |
| 100 | + |
| 101 | +- [Azure Policy overview](/azure/governance/policy/overview) |
| 102 | +- [Azure AI Foundry model catalog](/azure/ai-foundry/how-to/model-catalog-overview) |
0 commit comments