From 69bdfb8bd865b59df45f9f31a4302468c776ee1f Mon Sep 17 00:00:00 2001 From: Julien Nyambal Date: Mon, 1 Jun 2026 22:27:36 +0200 Subject: [PATCH] Update role assignment from 'Azure AI User' to 'Foundry User' Updated from the documentation: https://learn.microsoft.com/en-us/azure/foundry/concepts/rbac-foundry?tabs=owner --- docs/04-automated-evaluation.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/04-automated-evaluation.md b/docs/04-automated-evaluation.md index 3204486..b0f5a88 100644 --- a/docs/04-automated-evaluation.md +++ b/docs/04-automated-evaluation.md @@ -395,12 +395,12 @@ The evaluation script integrates with GitHub Actions to automatically run evalua Save the `appId`, `tenant`, and `password` values from the output — you will use them in the next steps. - Assign the **Azure AI User** role so the service principal can call the Foundry project API: + Assign the **Foundry User** role so the service principal can call the Foundry project API: ```powershell az role assignment create ` --assignee "" ` - --role "Azure AI User" ` + --role "Foundry User" ` --scope "/subscriptions//resourceGroups//providers/Microsoft.CognitiveServices/accounts/" ``` @@ -665,7 +665,7 @@ Create `experiments/automated/model_comparison.md` with: **Resolution**: - Run `az login` to refresh Azure credentials -- Verify the service principal has the **Azure AI User** role at the CognitiveServices account scope — this role has `Microsoft.CognitiveServices/*` wildcard data actions required for `AIServices/agents/write`. `Azure AI Developer` alone is **not sufficient** +- Verify the service principal has the **Foundry User** role at the CognitiveServices account scope — this role has `Microsoft.CognitiveServices/*` wildcard data actions required for `AIServices/agents/write`. `Azure AI Developer` alone is **not sufficient** - Check `AZURE_AI_PROJECT_ENDPOINT` in `.env` file is correct and includes `/api/projects/` ### OIDC login fails on PR workflows (`AADSTS700213`)