GitHub Enterprise plugin sends Microsoft v2 authorization request without required scope

What version of the Codex App are you using (From “About Codex” dialog)?

26.901.51231

What subscription do you have?

ChatGPT Business

What platform is your computer?

Linux 6.14.0-37-generic x86_64 x86_64

What issue are you seeing?

I cannot complete authentication for the GitHub Enterprise plugin in the Codex desktop app.

When I install the plugin and follow its login flow, Microsoft Entra displays:

AADSTS900144: The request body must contain the following parameter: 'scope'.

Steps to reproduce:

1. Install the GitHub Enterprise plugin from the Codex desktop app.
2. Start the plugin's sign-in/connect flow.
3. Follow the redirect to Microsoft sign-in.
4. The error above appears, preventing the connection from completing.

Environment:

• GitHub Enterprise Cloud on a company-specific *.ghe.com domain
• Enterprise managed users with Microsoft Entra SSO
• Normal browser sign-in to the Enterprise host succeeds, including MFA, and I can access the repository and pull request.

Troubleshooting already attempted:

• Restarted the computer.
• Reinstalled the GitHub Enterprise plugin.
• Retried authentication.
• The same error persists.

I inspected the failing authorization URL. It targets:
https://login.microsoftonline.com//oauth2/v2.0/authorize

Its parameters include:

response_type=code
client_id=<redacted>
redirect_uri=https://chatgpt.com/connector/oauth/<redacted>
resource=https://graph.microsoft.com
state=<redacted>
ui_locales=en-US

There is no scope parameter, although Microsoft's v2 authorization endpoint requires it. This directly explains the AADSTS900144 error.

The callback points to ChatGPT rather than GitHub's SSO callback. Please inspect the workspace connector's OAuth configuration and generated authorization request, including why connecting the GitHub Enterprise plugin requests the Microsoft Graph resource.

I have not established whether this originates in workspace configuration or the connector implementation.

What steps can reproduce the bug?

Feedback ID: no-active-thread-01a085f8-9fd2-79a1-81ad-ff6c5473df60

What is the expected behavior?

Authentication completes and the plugin can access authorized repositories on our GitHub Enterprise host.

Additional information

No response

Inspect the workspace connector's OAuth configuration and generated authorization URL first; trace the GitHub Enterprise plugin sign-in flow through its ChatGPT callback. Compare the Microsoft v2 authorize request with the reported resource-only request. Done means the flow supplies the required scope and completes authentication for authorized Enterprise repositories.