Skip to content

My auth has suddenly quit working today (9/18) #34098

Closed

Description

@ehagenmsft

I have created several copilot skills that require authentication. All were working up until yesterday, but now today they are all failing with authentication issues. I keep getting this error:

The Kusto MCP is unavailable, and the REST fallback failed Azure authentication with  AADSTS901001  due to an invalid  software_agent_id . Azure CLI requires a fresh  az logout  /  az login  authentication before the query can run.

az login is not authenticating for me. It keeps saying "broswer-based sign-in is still injecting the invalid agent ID, so I'm switching to device-code flow. Device-code flow fails to authenticate me.

This issue is severely restricting my work, so assistance would be greatly appreciated. Thanks!

Activity

  1. yonzhan commented on Sep 18, 2026

    @yonzhan
    Collaborator

    Thank you for opening this issue, we will look into it.

  2. added
    customer-reportedIssues that are reported by GitHub users external to the Azure organization.
    Accountaz login/account
    Azure CLI TeamThe command of the issue is owned by Azure CLI team
    questionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that
    on Sep 18, 2026
  3. added this to the Backlog milestone on Sep 18, 2026
  4. microsoft-github-policy-service commented on Sep 19, 2026

    @microsoft-github-policy-service
    Contributor

    🔔 Routing this issue to @Azure/act-identity-squad.

  5. x-engineering-agent commented on Sep 19, 2026

    @x-engineering-agent
    Contributor

    To distinguish an Azure CLI sign-in failure from the Copilot/Kusto integration, please share:

    • Your Azure CLI version (az version), operating system, shell, and how Azure CLI was installed.
    • The exact login commands and flags you used, and whether they were run directly in a terminal or by a Copilot skill.
    • Whether the problem also occurs in a terminal outside Copilot. For browser and device-code sign-in, provide the actual sanitized terminal error, rather than the assistant's explanation, and say whether either flow succeeds.

    Please omit tokens, device codes, credentials, and complete debug logs. The error code and sanitized error text are sufficient. I'll pick this up automatically once you reply.

  6. microsoft-github-policy-service commented on Sep 19, 2026

    @microsoft-github-policy-service
    Contributor

    🔔 Routing this issue to @Azure/act-identity-squad.

  7. ehagenmsft commented on Sep 21, 2026

    @ehagenmsft
    Author

    Looks like this self-resolved after 48 hours.

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

Metadata

Metadata

Labels

Accountaz login/accountAuto-AssignAuto assign by botAzure CLI TeamThe command of the issue is owned by Azure CLI teamX Engineering Agent Needs InfoAgent is waiting for the reporter to replyact-identity-squadcustomer-reportedIssues that are reported by GitHub users external to the Azure organization.questionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions