Microsoft Entra Agent ID
Developer

Call APIs as a user in a fleet with the Auth SDK sidecar

In brief

New guidance describes using OBO with the routed agent’s identity to call downstream APIs for a signed-in user, including Python and JavaScript examples.

What Entra admins need to know

Configure delegated permissions and sidecar API profiles, and enable GetAuthorizationHeader; otherwise AgentIdentity is ignored. Ensure the authorized agent identity is used for each request.

This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

new file mode 100644

title: Call APIs as a user in a fleet with the Auth SDK sidecar description: Use the On-Behalf-Of flow with the routed agent's identity to call APIs for a signed-in user through the Auth SDK sidecar in a shared runtime. titleSuffix: Microsoft Entra Agent ID ms.topic: how-to ms.date: 11/05/2026 ms.reviewer: dastrock ai-usage: ai-assisted

#customer-intent: As a developer building an agent hosting platform with the Auth SDK sidecar, I want agents in my fleet to call APIs on behalf of the signed-in user with their own agent identity.

Call APIs as a user in a fleet with the Auth SDK sidecar

After the runtime routes a user's request to an agent, the agent can call APIs for that user with the On-Behalf-Of (OBO) flow. Forward the user's token to the sidecar, and pass the routed agent's identity in the AgentIdentity parameter. The downstream token represents both the signed-in user and that agent.

Prerequisites

Configure the sidecar

Add a delegated profile for each API to the runtime sidecar:

{
  "Sidecar": {
    "AllowOverrides": {
      "GetAuthorizationHeader": true
    }
  },
  "DownstreamApis": {
    "custom-api-user": {
      "BaseUrl": "https://api.contoso.com/",
      "Scopes": [
        "api://<custom-api-client-id>/<delegated-scope>"
      ]
    }
  }
}

Explicitly enable GetAuthorizationHeader as shown, even if you previously disabled overrides by following the single-instance setup. Otherwise the sidecar ignores AgentIdentity. Only trusted runtime code should select and send identity overrides.

Get a token for the signed-in user

After routing the request and confirming the user can access the agent, call the sidecar:

Python

def authorization_header_for_user(
    inbound_auth_header: str, agent_id: str, api_name: str
) -> str:
    registration = directory.find(agent_id)

    response = requests.get(
        f"{SIDECAR_URL}/AuthorizationHeader/{api_name}",
        params={"AgentIdentity": registration["agent_identity_id"]},
        headers={"Authorization": inbound_auth_header},
        timeout=5,
    )
    if response.status_code in (401, 403):
        raise PermissionError("The sidecar rejected the user token or OBO request.")
    response.raise_for_status()
    return response.json()["authorizationHeader"]


inbound_auth_header = request.headers.get("Authorization")
authorize_agent_request(inbound_auth_header, agent_id)

api_response = requests.get(
    "https://api.contoso.com/user-data",
    headers={
        "Authorization": authorization_header_for_user(
            inbound_auth_header, agent_id, "custom-api-user"
        )
    },
    timeout=10,
)
api_response.raise_for_status()

JavaScript

async function authorizationHeaderForUser(inboundAuthHeader, agentId, apiName) {
    const registration = await directory.find(agentId);

    const params = new URLSearchParams({
        AgentIdentity: registration.agentIdentityId,
    });
    const response = await fetch(
        `${SIDECAR_URL}/AuthorizationHeader/${apiName}?${params}`,
        { headers: { Authorization: inboundAuthHeader } }
    );
    if (response.status === 401 || response.status === 403) {
        throw new Error("The sidecar rejected the user token or OBO request.");
    }
    if (!response.ok) {
        throw new Error(`Sidecar request failed with status ${response.status}.`);
    }
    const { authorizationHeader } = await response.json();
    return authorizationHeader;
}

const inboundAuthHeader = req.headers.authorization;
await authorizeAgentRequest(inboundAuthHeader, req.params.agentId);

const apiResponse = await fetch("https://api.contoso.com/user-data", {
    headers: {
        Authorization: await authorizationHeaderForUser(
            inboundAuthHeader, req.params.agentId, "custom-api-user"
        ),
    },
});

Always use the agent ID that passed the access check. If the runtime used a different agent's identity, the downstream API would see the wrong agent acting for the user. Don't send the inbound token directly to the downstream API, and don't log either authorization header.

Call specific resources

Use the scopes and endpoints from the linked resource articles, while keeping the fleet's blueprint client ID and override settings. The single-instance requests omit AgentIdentity. For each fleet resource request, call authorization_header_for_user or authorizationHeaderForUser to supply the routed agent identity and inbound user token.

ResourceGuidance
Custom APICall a custom API as a user
Azure servicesCall Azure services as a user
Microsoft GraphCall Microsoft Graph as a user

Related content

Daily Entra.News

Get daily email updates

Get a concise summary of the latest Microsoft Entra updates delivered straight to your inbox.

Loading the secure signup form…