Skip to content

Commit 41571c5

Browse files
Merge pull request #273839 from Blackmist/245667-roles
245667-roles
2 parents d165da3 + 68f0586 commit 41571c5

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

articles/ai-studio/concepts/rbac-ai-studio.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -162,6 +162,10 @@ If your Azure AI hub is configured with a **user-assigned managed identity**, th
162162

163163
Within the key vault, the user or service principal must have create, get, delete, and purge access to the key through a key vault access policy. For more information, see [Azure Key Vault security](/azure/key-vault/general/security-features#controlling-access-to-key-vault-data).
164164

165+
## Scenario: Use an existing Azure OpenAI resource
166+
167+
When you create a connection to an existing Azure OpenAI resource, you must also assign roles to your users so they can access the resource. You should assign either the **Cognitive Services OpenAI User** or **Cognitive Services OpenAI Contributor** role, depending on the tasks they need to perform. For information on these roles and the tasks they enable, see [Azure OpenAI roles](/azure/ai-services/openai/how-to/role-based-access-control#azure-openai-roles).
168+
165169
## Scenario: Use Azure Container Registry
166170

167171
An Azure Container Registry instance is an optional dependency for Azure AI Studio hub. The following table lists the support matrix when authenticating a hub to Azure Container Registry, depending on the authentication method and the __Azure Container Registry's__ [public network access configuration](/azure/container-registry/container-registry-access-selected-networks).

0 commit comments

Comments
 (0)