Skip to content

Fix local authentication in .NET invocations sample - #975

Open
JeffreyCA wants to merge 1 commit into
microsoft-foundry:mainfrom
JeffreyCA:fix-806-azure-core
Open

JeffreyCA wants to merge 1 commit into
microsoft-foundry:mainfrom
JeffreyCA:fix-806-azure-core

Conversation

@JeffreyCA

Copy link
Copy Markdown

Closes #806

Summary

This PR upgrades the .NET Hello World Invocations sample to Azure.AI.AgentServer.Invocations 1.0.0-beta.7. The previous beta.5 dependency resolved Azure.Core 1.59.0, which has a Windows regression where DefaultAzureCredential stops after an unavailable managed identity instead of continuing to local developer credentials.

The updated SDK resolves Azure.Core 1.62.0, which includes the credential-chain fix from Azure/azure-sdk-for-net#60701. This keeps managed identity authentication in Foundry while allowing local runs to use Azure CLI, Azure Developer CLI, Visual Studio, or other configured developer credentials.

Testing

  • Built the .NET 10 sample successfully with no warnings or errors.
  • Confirmed NuGet resolves Azure.AI.AgentServer.Core 1.0.0-beta.29 and Azure.Core 1.62.0.

Upgrade the Invocations SDK so the sample resolves Azure.Core 1.62.0, which includes the DefaultAzureCredential managed identity fallback fix.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: c3c85f8b-4a6a-49a1-afc0-3a00bbf89491
@b72869542-creator

Copy link
Copy Markdown

Hahaha

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Hello World (.NET) local invoke fails on Windows: All Managed Identity sources are unavailable

3 participants