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-studio/concepts/connections.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
@@ -50,7 +50,7 @@ A data connection offers these benefits:
50
50
When you create a connection with an existing Azure storage account, you can choose between two different authentication methods:
51
51
52
52
-**Credential-based**: Authenticate data access with a service principal, shared access signature (SAS) token, or account key. Users with *Reader* project permissions can access the credentials.
53
-
-**Identity-based**: Use your Microsoft Entra ID or managed identity to authenticate data access.
53
+
-**Identity-based**: Use your Microsoft Entra ID or managed identity to authenticate data access. When using this type of connection, Azure role-based access control (Azure RBAC) is used to determine who can access the connection. You must assign the correct Azure RBAC roles to your developers before they can use the connection. For more information, see [Scenario: Connections using Microsoft Entra ID](rbac-ai-studio.md#scenario-connections-using-microsoft-entra-id-authentication).
54
54
55
55
56
56
The following table shows the supported Azure cloud-based storage services and authentication methods:
0 commit comments