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
The 'VectorizeMaintenanceRequests' function is in error: Microsoft.Azure.WebJobs.Host: Error indexing method 'Functions.VectorizeMaintenanceRequests'. Microsoft.Azure.WebJobs.Extensions.CosmosDB: Cannot create container information for MaintenanceRequests in database ContosoSuites with lease leases in database ContosoSuites : ManagedIdentityCredential authentication unavailable. The requested identity has not been assigned to this resource.
Because it is suggested to use a `local.settings.json´ with the original ManagedIdentity clientId:
But per the documentation, when running locally, the DefaultIdentity class will use the user provided credentials from az login to get a token to connect to CosmosDB, so these values should not be there.
The text was updated successfully, but these errors were encountered:
jmservera
changed the title
Exercice 03_02.003: Error "The requested identity has not been assigned to this resource"
Exercise 03_02.003: Error "The requested identity has not been assigned to this resource"
Feb 5, 2025
In this part of the exercise:
TechExcel-Integrating-Azure-PaaS-and-AI-Services-for-AI-Design-Wins/docs/03_implement_vector_search_in_cosmos_db_nosql/03_02.md
Line 144 in 218c96b
You get:
Because it is suggested to use a `local.settings.json´ with the original ManagedIdentity clientId:
TechExcel-Integrating-Azure-PaaS-and-AI-Services-for-AI-Design-Wins/docs/03_implement_vector_search_in_cosmos_db_nosql/03_02.md
Line 117 in 218c96b
But per the documentation, when running locally, the DefaultIdentity class will use the user provided credentials from
az login
to get a token to connect to CosmosDB, so these values should not be there.The text was updated successfully, but these errors were encountered: