claude-code - 💡(How to fix) Fix Microsoft 365 MCP connector: redirect URI mismatch (AADSTS50011) [1 participants]

AADSTS50011: The redirect URI 'http://localhost:44548/callback' specified in the request does not match the redirect URIs configured for the application '08ad6f98-a4f8-4635-bb8d-f1a3044760f0'. Make sure the redirect URI sent in the request matches one added to your application in the Azure portal.

Request Id: 655a81cc-bc05-4833-80f7-f9c663de2400 Correlation Id: 66ede980-4c88-4e40-ab88-be8c92c7e804 Timestamp: 2026-04-14T15:25:48Z App ID: 08ad6f98-a4f8-4635-bb8d-f1a3044760f0

TL;DR

The Microsoft 365 MCP connector authentication issue can be resolved by registering the dynamic localhost port or a wildcard localhost pattern in the Azure AD app registration.

Guidance

• Verify the redirect URI configured in the Azure portal matches the one used by the OAuth callback, which in this case is http://localhost:44548/callback.
• Update the app registration to include the dynamic localhost port or use a wildcard pattern (e.g., http://localhost/*) to allow any port.
• Ensure the Claude Code configuration is set to use a fixed port or the wildcard pattern that matches the app registration.
• Test the authentication flow again after updating the app registration to confirm the fix.

Example

No code snippet is provided as the issue is related to configuration and app registration.

Notes

The solution assumes that the dynamic port used by the OAuth callback can be registered in the Azure AD app registration. If the port is truly dynamic and cannot be predicted, a wildcard pattern may be the only viable solution.

Recommendation

Apply workaround: Register a wildcard localhost pattern (e.g., http://localhost/*) in the Azure AD app registration to allow any port, as this is a more flexible solution that accommodates dynamic ports.