Skepra / Web recovery & resilience

Copilot CLI workflow sign-in fails on a client build runner after 1.0.112 provider change

Copilot CLI 1.0.112 adds Microsoft 365 sign-in and BYOK or custom-provider workflow options. The useful client decision is which identity, provider and fallback the runner is actually allowed to use.

Discuss the next maintenance decision

Copilot CLI 1.0.112 adds Microsoft 365 sign-in and BYOK or custom-provider workflow options. The useful client decision is which identity, provider and fallback the runner is actually allowed to use.

The decision this scenario creates

An agency can update GitHub Copilot CLI and discover that a client-facing workflow depends on a new sign-in or model-provider path. The release does not prove that every organization, account or runner can use it.

Run a bounded runner check

Use a disposable repository and non-production runner. Record the exact CLI version, runner, operating system, workflow owner, authentication mode, provider, billing owner and exit status. Run a read-only task and record whether it is authenticated, rejected, unavailable or ambiguous.

Hand back a provider decision

Return the workflow version, approved authentication mode, provider and billing ownership, bounded test result and explicit fallback. Do not copy a personal token into CI.

Limits

This article does not establish that a client runner is affected. No client environment was accessed.