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/how-to/develop/cloud-evaluation.md
+1-5Lines changed: 1 addition & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,11 +28,7 @@ In this article, you learn how to run evaluations in the cloud (preview) in pre-
28
28
- Azure OpenAI Deployment with GPT model supporting `chat completion`. For example, `gpt-4`.
29
29
- Make sure you're first logged into your Azure subscription by running `az login`.
30
30
31
-
If this is your first time running evaluations and logging it to your Azure AI Foundry project, you might need to do a few additional steps:
32
-
33
-
1. Create and connect your storage account to your Azure AI Foundry project at the resource level. There are two ways you can do this. You can [use a Bicep template](https://github.com/azure-ai-foundry/foundry-samples/blob/main/samples/microsoft/infrastructure-setup/01-connections/connection-storage-account.bicep), which provisions and connects a storage account to your Foundry project with key authentication. You can also [manually create and provision access](../evaluations-storage-account.md) to your storage account in the Azure portal.
34
-
1. Make sure the connected storage account has access to all projects.
35
-
1. If you connected your storage account with Microsoft Entra ID, make sure to give managed identity **Storage Blob Data Owner** permissions to both your account and the Foundry project resource in the Azure portal.
If this is your first time running evaluations or AI red teaming runs on your Azure AI Foundry project, you might need to do a few additional setup steps.
27
-
28
-
1.[Create and connect your storage account](https://github.com/azure-ai-foundry/foundry-samples/blob/main/samples/microsoft/infrastructure-setup/01-connections/connection-storage-account.bicep) to your Azure AI Foundry project at the resource level. This bicep template provisions and connects a storage account to your Foundry project with key authentication.
29
-
2. Make sure the connected storage account has access to all projects.
30
-
3. If you connected your storage account with Microsoft Entra ID, make sure to give MSI (Microsoft Identity) permissions for Storage Blob Data Owner to both your account and Foundry project resource in Azure portal.
### Option 2: Using Azure OpenAI/AI Services deployments
69
+
70
+
If you want to use deployments from your Azure OpenAI or AI Services accounts, you first need to connect these resources to your Foundry project through connections.
71
+
72
+
1.**Create a connection**: Follow the instructions in [Configure project connections](../../foundry-models/how-to/configure-project-connection.md?pivots=ai-foundry-portal#add-a-connection) to connect your Azure OpenAI or AI Services resource to your Foundry project.
73
+
74
+
2.**Get the connection name**: After connecting the account, you'll see the connection created with a generated name in your Foundry project.
75
+
76
+
3.**Configure the target**: Use the format `"connectionName/deploymentName"` for your model deployment configuration:
- Replace `{{account}}`, `{{project}}` with Foundry Project account name and project name.
99
133
- Replace `{{ai_token}}` with Bearer token with audience "<https://ai.azure.com>"
100
-
- Replace `"{{connectionName}}"` with the Azure OpenAI model connection name connected to the Foundry project account.
101
-
- Replace `"{{deploymentName}}"` with the Azure OpenAI deployment name of the AOAI connection account.
134
+
-For Option 1 (Foundry project deployments): Replace `"{{connectionName}}/{{deploymentName}}"` with just `"{{deploymentName}}"` (your model deployment name).
135
+
-For Option 2 (Azure OpenAI/AI Services deployments): Replace `"{{connectionName}}"` with the Azure OpenAI model connection name connected to the Foundry project account, and replace `"{{deploymentName}}"` with the Azure OpenAI deployment name of the Azure OpenAI connection account.
Copy file name to clipboardExpand all lines: articles/ai-foundry/how-to/develop/run-scans-ai-red-teaming-agent.md
+1-5Lines changed: 1 addition & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,11 +28,7 @@ This article guides you through the process of
28
28
29
29
- An Azure AI Foundry project or hubs based project. To learn more, see [Create a project](../create-projects.md).
30
30
31
-
If this is your first time running evaluations or AI red teaming runs on your Azure AI Foundry project, you might need to do a few additional setup steps.
32
-
33
-
1.[Create and connect your storage account](https://github.com/azure-ai-foundry/foundry-samples/blob/main/samples/microsoft/infrastructure-setup/01-connections/connection-storage-account.bicep) to your Azure AI Foundry project at the resource level. This bicep template provisions and connects a storage account to your Foundry project with key authentication.
34
-
2. Make sure the connected storage account has access to all projects.
35
-
3. If you connected your storage account with Microsoft Entra ID, make sure to give MSI (Microsoft Identity) permissions for Storage Blob Data Owner to both your account and Foundry project resource in Azure portal.
If this is your first time running evaluations and logging it to your Azure AI Foundry project, you might need to do a few additional steps:
13
+
14
+
1. Create and connect your storage account to your Azure AI Foundry project at the resource level. There are two ways you can do this. You can [use a Bicep template](https://github.com/azure-ai-foundry/foundry-samples/blob/main/samples/microsoft/infrastructure-setup/01-connections/connection-storage-account.bicep), which provisions and connects a storage account to your Foundry project with key authentication. You can also [manually create and provision access](../how-to/evaluations-storage-account.md) to your storage account in the Azure portal.
15
+
1. Make sure the connected storage account has access to all projects.
16
+
1. If you connected your storage account with Microsoft Entra ID, make sure to give managed identity **Storage Blob Data Owner** permissions to both your account and the Foundry project resource in the Azure portal.
0 commit comments