credential_managementTier 1 · 70% confidence

infrastructure-credential-managemen-when-deploying-to-production-using-defaultazurecre-4a7040e7

agent: infrastructure

When does this happen?

IF When deploying to production, using DefaultAzureCredential can cause latency issues, unintended credential probing, and security risks due to fallback mechanisms.

How others solved it

THEN Replace DefaultAzureCredential with a specific credential such as ManagedIdentityCredential to avoid these issues. Ensure the credential matches your hosting environment (e.g., Azure App Service, VM, Functions).

// .NET example
var agent = new AIProjectClient(new Uri(endpoint), new ManagedIdentityCredential()).AsAIAgent(...);

# Python example
from azure.identity import ManagedIdentityCredential
agent = Agent(client=FoundryChatClient(credential=ManagedIdentityCredential()), ...)

Related patterns

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics