microsoft-foundry / microsoft-foundry/foundry-samples
Request blocked by Auth Cosmos DB
Nobody has claimed this yet.
- Dominant language
- Bicep
- Stars
- 445
- Forks
- 494
- Avg merge
- 11h 35m
- Merged PRs (30d)
- 38
Description
Hello everyone,
I have an error in the new Azure AI Foundry related to authentication with Cosmos DB.
Initially, I had an AAD connection to Cosmos DB, but I have since switched to API keys. However, I am still receiving the following error:
Error loading your agents.Response status code does not indicate success: Forbidden (403); Substatus: 5300; ActivityId: 66f0becd-1c33-4db6-87b2-b2b5f23fd51e; Reason: (Request blocked by Auth acdb-XYZ : The given request [POST /dbs/enterprise_memory/colls] cannot be authorized by AAD token in data plane. Learn more: https://aka.ms/cosmos-native-rbac. ActivityId: 66f0becd-1c33-4db6-87b2-b2b5f23fd51e, Microsoft.Azure.Documents.Common/2.14.0, Microsoft.Azure.Cosmos.Tracing.TraceData.ClientSideRequestStatisticsTraceDatum, Linux/12 cosmos-netstandard-sdk/3.39.1); Request ID: 0e471b9c-a148-408d-801f-e8476651c130
Here is a screenshot of the error:
Does anyone have any idea what could be causing this? I'm a little confused because the error says something about AAD, but I'm currently using API keys.
Thank you and best regards
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Start with the reported 403/5300 error and compare the Cosmos DB authentication configuration after switching from AAD to API keys with the request's observed AAD token. Done means identifying the configuration mismatch or required authentication setting so agent loading succeeds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- authentication, cloud, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100