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/concepts/rbac-azure-ai-foundry.md
+33-6Lines changed: 33 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,12 +8,13 @@ ms.custom:
8
8
- build-2024
9
9
- ignite-2024
10
10
ms.topic: concept-article
11
-
ms.date: 09/15/2025
11
+
ms.date: 09/25/2025
12
12
ms.reviewer: deeikele
13
13
ms.author: jburchel
14
14
author: jonburchel
15
15
ai.usage: ai-assisted
16
16
---
17
+
17
18
# Role-based access control for Azure AI Foundry
18
19
19
20
> [!NOTE]
@@ -47,7 +48,7 @@ The key differences between **Azure AI Project Manager** and **Azure AI Account
47
48
- Create new Azure AI Foundry account resources. Only the **Azure AI Account Owner** can do this.
48
49
The second difference appears in the role definitions: the data action `Microsoft.CognitiveServices/*`. This data action lets the user complete any read, write, or delete data actions within a project. The **Azure AI Project Manager** can perform this action, but the **Azure AI Account Owner** can't. Only **Azure AI User** and **Azure AI Project Manager** get data actions for an AI project. Think of **Azure AI Project Manager** as an elevated **Azure AI User**.
49
50
50
-
In addition to these built-in role assignments, there are Azure privileged administrator roles like Owner, Contributor, and Reader. These roles aren't specific to Azure AI Foundry resource permissions, so use the built-in roles above for least privilege access.
51
+
In addition to these built-in role assignments, there are Azure privileged administrator roles like Owner, Contributor, and Reader. These roles aren't specific to Azure AI Foundry resource permissions, so use the previously described built-in roles for least privilege access.
51
52
52
53
Use the following table to see the privileges for each built-in role, including the Azure privileged administrator roles:
53
54
@@ -204,7 +205,7 @@ This table shows an example of role-based access control (RBAC) for an enterpris
| IT admin | Subscription Owner | The IT admin ensures the Azure AI Foundry resource meets enterprise standards. Assign managers the **Azure AI Account Owner** role on the resource to let them create new Azure AI Foundry accounts. Assign managers the **Azure AI Project Manager** role on the resource to let them create projects within an account. |
206
207
| Managers | Azure AI Account Owner on Azure AI Foundry resource | Managers manage the Azure AI Foundry resource, deploy models, audit compute resources, audit connections, and create shared connections. They can't build in projects, but they can assign the **Azure AI User** role to themselves and others to start building. |
207
-
| Team lead or lead developer | Azure AI Project Manager on Azure AI Foundry resource | Lead developers create projects for their team and start building in those projects. After creating a project, project owners invite other members and assign the **Azure AI User** role. |
208
+
| Team lead or lead developer | Azure AI Project Manager on Azure AI Foundry resource | Lead developers create projects for their team and start building in those projects. After you create a project, project owners invite other members and assign the **Azure AI User** role. |
208
209
| Team members or developers | Azure AI User on Azure AI Foundry resource | Developers build agents in a project. |
209
210
210
211
> [!IMPORTANT]
@@ -245,7 +246,33 @@ To create a custom role, use one of the following articles:
245
246
246
247
For more information about custom roles, see the [Azure custom roles](/azure/role-based-access-control/custom-roles) article.
247
248
248
-
## Next steps
249
+
## Use Microsoft Entra groups with Azure AI Foundry
250
+
251
+
Microsoft Entra ID provides several ways to manage access to resources, applications, and tasks. With Microsoft Entra groups, you can grant access and permissions to a group of users instead of to each individual user. Microsoft Entra groups can be created in the Azure portal for enterprise IT admins to simplify the role assignment process for developers. When you create an Microsoft Entra group, you can minimize the number of role assignments required for new developers working on Foundry projects by assigning the group the required role assignment on the necessary resource.
252
+
253
+
Complete the following steps to use Entra ID groups with Azure AI Foundry:
254
+
255
+
1. Navigate to **Groups** in the Azure portal.
256
+
1. Create a new **Security** group in the Groups portal.
257
+
1. Assign the Owner of the Microsoft Entra group and add individual user
258
+
principles in your organization to the group as Members. Save the
259
+
group.
260
+
1. Navigate to the resource that requires a role assignment.
261
+
262
+
1.**Example:** To build Agents, run traces, and more in Foundry, the minimum privilege ‘Azure AI User’ role must be assigned to your user principle. Assing the ‘Azure AI User’ role to your new Microsoft Entra group so all users in your enterprise can build in Foundry.
263
+
1.**Example:** To use Tracing and Monitoring features in Azure AI Foundry, a ‘Reader’ role assignment on the connected Application Insights resource is required. Assign the ‘Reader’ role to your new Microsoft Entra group so all users in your enterprise can use the Tracing and Monitoring feature.
264
+
265
+
1. Navigate to Access Control (IAM).
266
+
1. Select the role to assign.
267
+
1. Assign access to “User, group, or service principle” and select the new Security group.
268
+
1. Review and assign. Role assignment now applies to all user principles assigned to the group.
269
+
270
+
To learn more about Entra ID groups, prerequisites, and limitations, refer to:
271
+
272
+
-[Learn about groups, group membership, and access in Microsoft Entra](/entra/fundamentals/concept-learn-about-groups).
273
+
-[How to manage groups in Microsoft Entra](/entra/fundamentals/how-to-manage-groups).
274
+
275
+
## Related content
249
276
250
-
-[Create a project](../how-to/create-projects.md)
251
-
-[Add a connection in Azure AI Foundry portal](../how-to/connections-add.md)
277
+
-[Create a project](../how-to/create-projects.md).
278
+
-[Add a connection in Azure AI Foundry portal](../how-to/connections-add.md).
Copy file name to clipboardExpand all lines: articles/ai-foundry/how-to/develop/trace-application.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -66,7 +66,7 @@ The following steps show how to configure your resource:
66
66
1. Once the connection is configured, you're ready to use tracing in any project within the resource.
67
67
68
68
> [!TIP]
69
-
> Make sure you have the [Log Analytics Reader role](/azure/azure-monitor/logs/manage-access?tabs=portal#log-analytics-reader) assigned in your Application Insights resource. To learn more on how to assign roles, see [Assign Azure roles using the Azure portal](/azure/role-based-access-control/role-assignments-portal).
69
+
> Make sure you have the [Log Analytics Reader role](/azure/azure-monitor/logs/manage-access?tabs=portal#log-analytics-reader) assigned in your Application Insights resource. To learn more on how to assign roles, see [Assign Azure roles using the Azure portal](/azure/role-based-access-control/role-assignments-portal). Use [Microsoft Entra groups](../../concepts/rbac-azure-ai-foundry.md#use-microsoft-entra-groups-with-azure-ai-foundry) to more easily manage access for users.
70
70
71
71
1. Go to the landing page of your project and copy the project's endpoint URI. You need it later.
0 commit comments