Skip to content

Docs feedback: Azure proxy wording overemphasizes DCR and underexplains direct Claude/Azure incompatibility #3942

@RajatSetoo

Description

@RajatSetoo

Enhancement

The current wording made me assume that the main blocker with Azure was lack of DCR, and that manual client registration would be a valid workaround.

Because of that, I spent time manually creating the Azure app registration and configuring Claude with the Azure metadata, client ID, and client secret. That made it seem like I was on the right path.

The actual blocker turned out to be later in the flow: Claude was calling Azure’s authorization endpoint with parameters Azure did not accept, such as resource. So in practice, the main issue was direct client-to-Azure protocol incompatibility, not just lack of DCR.

I think the docs should make that clearer.

Metadata

Metadata

Assignees

No one assigned

    Labels

    authRelated to authentication (Bearer, JWT, OAuth, WorkOS) for client or server.documentationUpdates to docs, examples, or guides. Primary change is documentation-related.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions