Skip to content

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

Closed

Description

@ChenxiJiang333

Description:
When testing Scenario 4: Hello World (.NET, Invocations), after azd ai agent run successfully started locally, executing the local invocation command azd ai agent invoke --local --protocol invocations '{"message": "Hello from C# local"}' failed. The local log showed the error: All Managed Identity sources are unavailable. See the image below for details.
Image
Image

Steps to Reproduce:

  1. Run azd ai agent init --manifest "https://github.com/microsoft-foundry/foundry-samples/blob/main/samples/python/hosted-agents/bring-your-own/responses/notetaking-agent/agent.manifest.yaml".
  2. Run azd up.
  3. Run azd ai agent run.
  4. From a second terminal, run azd ai agent invoke --local --protocol invocations '{"message": "Hello from C# local"}'.

Environment:

Expected Behavior:
Local invoke can succeed.

JeffreyCA and Rick Winter (@RickWinter) for notification.

Activity

  1. ChenxiJiang333 commented on Jul 10, 2026

    @ChenxiJiang333
    Author

    JeffreyCA and Rick Winter (@RickWinter) Retested with the latest versions 1.0.0-beta.5 of ai agent extension, this issue can still be reproduced.

    Environment:

  2. ChenxiJiang333 commented on Jul 22, 2026

    @ChenxiJiang333
    Author

    JeffreyCA and Rick Winter (@RickWinter) Retested with the latest versions 1.0.0-beta.6 of ai agent extension, this issue can still be reproduced.

    Environment:

  3. ankitbko commented on Jul 25, 2026

    @ankitbko
    Contributor

    Which sample has the issue? Image shows a dotnet sample but the link is python sample

  4. ChenxiJiang333 commented on Jul 27, 2026

    @ChenxiJiang333
    Author

    Which sample has the issue? Image shows a dotnet sample but the link is python sample

    My bad, it's the issue of dotnet sample: https://github.com/microsoft-foundry/foundry-samples/blob/main/samples/csharp/hosted-agents/bring-your-own/invocations/HelloWorld/azure.yaml.

  5. ChenxiJiang333 commented on Jul 31, 2026

    @ChenxiJiang333
    Author

    JeffreyCA and Rick Winter (@RickWinter) Retested with the latest versions 1.0.0-beta.8 of ai agent extension, this issue can still be reproduced.

    Environment:

  6. ChenxiJiang333 commented on Aug 7, 2026

    @ChenxiJiang333
    Author

    JeffreyCA and Rick Winter (@RickWinter) Retested with the latest version of ai agent extension, this issue can still be reproduced.

    Environment:

  7. ChenxiJiang333 commented on Aug 19, 2026

    @ChenxiJiang333
    Author

    JeffreyCA and Rick Winter (@RickWinter) Retested with the latest version of ai agent extension, this issue can still be reproduced.

    Environment:

  8. ChenxiJiang333 commented on Aug 28, 2026

    @ChenxiJiang333
    Author

    JeffreyCA and Rick Winter (@RickWinter) Retested with the latest version 1.0.0-beta.13 of ai agent extension, this issue can still be reproduced.

    Environment:

  9. ChenxiJiang333 commented on Sep 11, 2026

    @ChenxiJiang333
    Author

    JeffreyCA and Rick Winter (@RickWinter) Retested with the latest version 1.0.0-beta.14 of ai agent extension, this issue can still be reproduced.

    Environment:

  10. JeffreyCA commented on Sep 11, 2026

    @JeffreyCA
    Contributor

    ChenxiJiang333 can you re-test with the changes in #975 and see if it resolves the issue?

  11. ChenxiJiang333 commented on Sep 14, 2026

    @ChenxiJiang333
    Author

    Hi JeffreyCA, it works to resolve the issue with that change.

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

Metadata

Metadata

Labels

bugSomething isn't working

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions