Configure the Microsoft Entra ID Auth SDK sidecar
In brief
The article now covers sidecar configuration, prerequisites, shared network requirements, local and Azure host credentials, managed identity settings, and Docker Compose deployment examples.
What Entra admins need to know
Administrators configuring the sidecar should use the updated prerequisites and deployment settings, including loopback access and managed identity configuration for Azure hosts.
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.
Acquire tokens and call downstream APIs withConfigure the Microsoft Entra ID Auth SDK (sidecar)sidecar
The Microsoft Entra ID Auth SDK (sidecar)sidecar is a containerized webcompanion service that handles authentication and token acquisition, validation, and downstream API callsacquisition for agents. This SDK communicates with your application through HTTP APIs, providing consistent integration patterns regardless ofagent. It lets your technology stack. Instead of embedding identity logic directly in your application code, the Microsoft Entra ID Auth SDK (sidecar) manages token acquisition, validation, and API calls through standard HTTP requests.
Prerequisites
Before you begin, ensure you have:
Set up the Microsoft Entra ID Auth SDK (sidecar)An agent identity. Record thecloud agentidentity client ID.An agent identity blueprint. Record the agent identity blueprint client ID.Necessary permissions configured in Microsoft Entra ID
Deploy your containerized service
Deploy the Microsoft Entra ID Auth SDK (sidecar)call APIs as a containerized service in your environment. Follow the instructions in the Set up the Microsoft Entra ID Auth SDK (sidecar) guide to configure the service with your agent identity details.
Configure your Microsoft Entra ID Auth SDK (sidecar) settings
Follow these steps to configure your Microsoft Entra ID Auth SDK (sidecar) settings:
[!INCLUDE Dont use secrets]
Set up the necessary components in Microsoft Entra ID. Ensure you register your application in the Microsoft Entra ID tenant.Configure your client credentials. This credential can be a client secret, a certificate, or a managed identity that you're using as a federated identity credential.If you're calling a downstream API, ensure that the necessary permissions are granted. Calling a custom web API requires you to provide the API registration details in the SDK configuration.
For more information, see Configure your Microsoft Entra ID Auth SDK (sidecar) settings.
Acquire tokens using the Microsoft Entra ID Auth SDK (sidecar)
These are the steps to acquire tokens using the Microsoft Entra ID Auth SDK (sidecar):
Acquire token using the Microsoft Entra ID Auth SDK (sidecar). This varies based on whether the agent is operating autonomouslyitself or on behalf of signed-in users.In this article, you configure the sidecar container, its blueprint credential, and downstream API access.
Prerequisites
- Completion of Create an identity for your agent, including tenant enablement, administrator approvals, and the recorded client and object IDs.
- A credential configured on the blueprint.
- Permissions granted to the Agent ID for each downstream API.
- A shared network namespace for the agent and sidecar, such as containers in the same pod.
Add the sidecar container
Run the agent and sidecar in the same network namespace and call the sidecar through
localhost. Production sidecar builds restrict callers to loopback; auser. There are three scenarios to consider:private Docker bridge and asidecarDNS name aren't sufficient. Containers in the same Kubernetes pod or Azure Container Apps app share this boundary. In Docker Compose, usenetwork_mode: "service:sidecar"on the agent. Don't publish the sidecar port.Use the credential configuration for where you run the container:
Autonomous agents: Agents operatingLocal workstation: Follow Run the sidecar for local development for the sample container startup and development credential. Apply the network boundary above and the API profiles and override settings below.- Azure host: Use the following configuration after assigning the managed identity to the host and configuring its federated credential on
their own behalf using service principals createdthe blueprint. It doesn't provide a workstation credential.
The Docker Compose fragment illustrates the shared network layout and uses a user-assigned managed identity as the credential:
Set
AzureAd:ClientCredentials:0:SourceTypetoSignedAssertionFromManagedIdentityandAzureAd:ClientCredentials:0:ManagedIdentityClientIdto the user-assigned managed identity's client ID. This is a different value from the shared agent client ID inAzureAd:ClientId. Container environment variables use__in place of:in these configuration paths.Record the tenant, blueprint, Agent ID, and API identifiers for
agents (autonomous).Autonomousyour scenario in the scenario identifier worksheet before configuring these values.services: sidecar: image: mcr.microsoft.com/entra-sdk/auth-sidecar:1.1.3-azurelinux3.0-distroless environment: AzureAd__Instance: https://login.microsoftonline.com/ AzureAd__TenantId: <tenant-id> AzureAd__ClientId: <agent-client-id> AzureAd__ClientCredentials__0__SourceType: SignedAssertionFromManagedIdentity AzureAd__ClientCredentials__0__ManagedIdentityClientId: <managed-identity-client-id> ASPNETCORE_URLS: http://localhost:5000 agent: image: <agent-image> network_mode: "service:sidecar" environment: SIDECAR_URL: http://localhost:5000Replace
<agent-image>with your agent'suser account: Agents operating on their own behalf using user principals created specificallyimage. This example pins the Linux sidecar to1.1.3-azurelinux3.0-distroless. For Windows, use the matching Windows tag from Auth SDK sidecar container image tags.Use
SignedAssertionFilePathinstead when the container receives a workload identity token from its orchestrator. UseClientSecretonly foragents (for instance agents having their own mailbox)local development. Don't place the blueprint credential in the agent container.For other credential sources, see Microsoft.Identity.Web credential descriptions.
Interactive agents: Agents operating on behalf of human users.To acquire an app-only (client credentials) token for an autonomous agent, you provide the agent identity client ID in the request.GET /AuthorizationHeader/Graph?AgentIdentity=<agent-identity-client-id> Authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbGc...To acquire token for an autonomous agent's user account, provide either the user object ID or User Principal Name but not both. This means providing eitherAgentUsernameorAgentUserId. Providing both causes a validation error. You must also provide theAgentIdentityto specify which agent identity to use for token acquisition. If the agent identity parameter is missing, the request fails with a validation error.GET /AuthorizationHeader/Graph?AgentIdentity=<agent-identity-client-id>&AgentUserId=<agent-user-object-id> Authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbGc...GET /AuthorizationHeader/Graph?AgentIdentity=<agent-identity-client-id>&AgentUsername=<agent-user-principal-name> Authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbGc...For
interactive agents, usecomplete request and response details, see theon-behalf-of (OBO) flow. The agent first validatesAuth SDK sidecar endpoint reference. An unconfigured profile name returns400 Bad Request; correct theuser token granted to it before acquiringroute name or add theresource token to call the downstream API.Agent web API receives user token from the calling application and validates the token via the Microsoft Entra ID Auth SDK (sidecar)matching/ValidateDownstreamApisendpoint Acquire token for downstream APIs by calling/AuthorizationHeaderwith only theAgentIdentityand the incoming authorization header# Step 1: Validate incoming user token GET /Validate Authorization: Bearer <user-token> # Step 2: Get authorization header on behalf of the user GET /AuthorizationHeader/Graph?AgentIdentity=<agent-identity-client-id> Authorization: Bearer <user-token>
Specify the
Configure a downstream API
Give each downstream API a short name. Configure its base URL, scopes, and token type. For example, this profile requests app-only tokens for Microsoft Graph:
{
"DownstreamApis": {
"graph-app": {
"BaseUrl": "https://graph.microsoft.com/v1.0/",
"Scopes": [
"https://graph.microsoft.com/.default"
],
"RequestAppToken": true
}
}
}
The name becomes the {apiName} route value. This example uses graph-app, so the agent requests /AuthorizationHeaderUnauthenticated/graph-app.
The resource-specific articles provide the configuration for each API. To configure the container with environment variables, replace each : in the JSON path with __. For example:
environment:
DownstreamApis__graph-app__BaseUrl: https://graph.microsoft.com/v1.0/
DownstreamApis__graph-app__Scopes__0: https://graph.microsoft.com/.default
DownstreamApis__graph-app__RequestAppToken: "true"
Keep identity overrides disabled
Use the client ID recorded during setup directly. Don't pass AgentIdentity, AgentUserId, or AgentUsername: these select a different identity flow, not the cloud-agent setup in this article.
Keep overrides disabled on the endpoints used by includingthe agent:
{
"Sidecar": {
"AllowOverrides": {
"GetAuthorizationHeader": false,
"GetAuthorizationHeaderUnauthenticated": false,
"CallDownstreamApi": false,
"CallDownstreamApiUnauthenticated": false
}
}
}
Keep the sidecar accessible only through the shared loopback boundary even when overrides are disabled. The unauthenticated endpoints can acquire app-only tokens with the configured credential.
Verify the sidecar
From the agent container in the shared network namespace, request http://localhost:5000/healthz:
GET /healthz
The endpoint reports whether the sidecar is accepting requests. It doesn't verify the credential, consent, or downstream API access. Test token acquisition and a downstream call separately. Don't expose it as a public health endpoint.
Choose an endpoint
| Operation | Endpoint |
|---|---|
| Validate an inbound access token and return its claims | GET /Validate |
| Get an authorization header using an inbound user token | GET /AuthorizationHeader/{apiName} |
| Get an authorization header without an inbound user token | GET /AuthorizationHeaderUnauthenticated/{apiName} |
| Have the sidecar call a configured downstream API | POST /DownstreamApi/{apiName} |
| Have the sidecar call a configured downstream API without an inbound user token | POST /DownstreamApiUnauthenticated/{apiName} |
Use the named downstream API profile without identity query parameters. For example, request /AuthorizationHeaderUnauthenticated/graph-app for app-only access or /AuthorizationHeader/graph with an inbound user token for OBO.
The authorization-header endpoints return an authorizationHeader value. Treat it as a credential and don't log it.
The profile name in the request URL based on your Microsoft Entra ID Auth SDK (sidecar) configuration.endpoint must match a name under DownstreamApis. The authorization header endpoint takes the formatconfiguration above defines graph-app, so /AuthorizationHeaderUnauthenticated/graph-app is valid. It doesn't define a graph profile. To use /AuthorizationHeader/ {serviceName}graphwherefor OBO, configure a separate delegated serviceNamegraphisprofile as shown in Call Microsoft Graph as a user. The endpoint path selects which identity supplies the token; the profile name ofselects the downstream API configured in the SDK settings.configuration.
Call an API
When obtaining the authorization header for calling a downstream API, the Microsoft Entra ID Auth SDK (sidecar) returns the Authorization header value that can be used directly in your API calls.
You can use this header to call the downstream API. The web API should validate the token by calling the /Validate endpoint of the Microsoft Entra ID Auth SDK (sidecar). This endpoint returns token claims for further authorization decisions.entry.
Related contentNext steps
Python implementation of Microsoft Entra ID Auth SDK (sidecar)Run the sidecar for local development.TypeScript implementation of Microsoft Entra ID Auth SDK (sidecar)Call a custom API as the agent.Call a downstream API - Microsoft Entra ID Auth SDK (sidecar) docsAuthenticate users.- Review the sidecar source code.
- Explore the official sidecar samples.
- Build a platform that hosts an agent fleet.
@@ -1,98 +1,152 @@ ----title: Acquire tokens and call downstream APIs with Microsoft Entra ID Auth SDK (sidecar)+title: Configure the Microsoft Entra ID Auth SDK sidecar+description: Set up the Microsoft Entra ID Auth SDK sidecar to get tokens and call APIs. titleSuffix: Microsoft Entra Agent ID-description: Learn how autonomous agents acquire tokens using the Microsoft Entra ID Auth SDK (sidecar) to call downstream APIs independently. ms.topic: how-to-ms.date: 11/05/2025-ms.reviewer: jmprieur-#Customer intent: As a developer building autonomous agents, I want to acquire tokens using the Microsoft Entra ID Auth SDK (sidecar) so that my agents can independently call downstream APIs with proper authentication.+ms.date: 11/06/2026+ai-usage: ai-assisted+ms.reviewer: dastrock++#customer-intent: As an agent developer, I want to configure the Auth SDK sidecar so that my agent can securely acquire tokens for downstream APIs. --- -# Acquire tokens and call downstream APIs with Microsoft Entra ID Auth SDK (sidecar)+# Configure the Microsoft Entra ID Auth SDK sidecar++The Microsoft Entra ID Auth SDK sidecar is a companion service that handles authentication and token acquisition for your agent. It lets your cloud agent call APIs as itself or on behalf of signed-in users. -The Microsoft Entra ID Auth SDK (sidecar) is a containerized web service that handles token acquisition, validation, and downstream API calls for agents. This SDK communicates with your application through HTTP APIs, providing consistent integration patterns regardless of your technology stack. Instead of embedding identity logic directly in your application code, the Microsoft Entra ID Auth SDK (sidecar) manages token acquisition, validation, and API calls through standard HTTP requests.+In this article, you configure the sidecar container, its blueprint credential, and downstream API access. ## Prerequisites -Before you begin, ensure you have:+- Completion of [Create an identity for your agent](create-single-instance-agent.md), including tenant enablement, administrator approvals, and the recorded client and object IDs.+- A credential configured on the blueprint.+- Permissions granted to the Agent ID for each downstream API.+- A shared network namespace for the agent and sidecar, such as containers in the same pod.++## Add the sidecar container++Run the agent and sidecar in the same network namespace and call the sidecar through `localhost`. Production sidecar builds restrict callers to loopback; a private Docker bridge and a `sidecar` DNS name aren't sufficient. Containers in the same Kubernetes pod or Azure Container Apps app share this boundary. In Docker Compose, use `network_mode: "service:sidecar"` on the agent. Don't publish the sidecar port.++Use the credential configuration for where you run the container:++- **Local workstation:** Follow [Run the sidecar for local development](sidecar-local-development.md) for the sample container startup and development credential. Apply the network boundary above and the API profiles and override settings below.+- **Azure host:** Use the following configuration after assigning the managed identity to the host and configuring its federated credential on the blueprint. It doesn't provide a workstation credential.++The Docker Compose fragment illustrates the shared network layout and uses a user-assigned managed identity as the credential:++Set `AzureAd:ClientCredentials:0:SourceType` to `SignedAssertionFromManagedIdentity` and `AzureAd:ClientCredentials:0:ManagedIdentityClientId` to the user-assigned managed identity's client ID. This is a different value from the shared agent client ID in `AzureAd:ClientId`. Container environment variables use `__` in place of `:` in these configuration paths.++Record the tenant, blueprint, Agent ID, and API identifiers for your scenario in the [scenario identifier worksheet](key-concepts.md#record-the-identifiers-for-your-scenario) before configuring these values. -- [Set up the Microsoft Entra ID Auth SDK (sidecar)](/entra/msidweb/agent-id-sdk/installation)-- [An agent identity](./create-delete-agent-identities.md). Record the agent identity client ID.-- [An agent identity blueprint](./create-blueprint.md). Record the agent identity blueprint client ID.-- Necessary [permissions configured in Microsoft Entra ID](grant-agent-access-microsoft-365.md)+```yml+services:+ sidecar:+ image: mcr.microsoft.com/entra-sdk/auth-sidecar:1.1.3-azurelinux3.0-distroless+ environment:+ AzureAd__Instance: https://login.microsoftonline.com/+ AzureAd__TenantId: <tenant-id>+ AzureAd__ClientId: <agent-client-id>+ AzureAd__ClientCredentials__0__SourceType: SignedAssertionFromManagedIdentity+ AzureAd__ClientCredentials__0__ManagedIdentityClientId: <managed-identity-client-id>+ ASPNETCORE_URLS: http://localhost:5000 -## Deploy your containerized service+ agent:+ image: <agent-image>+ network_mode: "service:sidecar"+ environment:+ SIDECAR_URL: http://localhost:5000+``` -Deploy the Microsoft Entra ID Auth SDK (sidecar) as a containerized service in your environment. Follow the instructions in the [Set up the Microsoft Entra ID Auth SDK (sidecar)](/entra/msidweb/agent-id-sdk/installation) guide to configure the service with your agent identity details.+Replace `<agent-image>` with your agent's image. This example pins the Linux sidecar to `1.1.3-azurelinux3.0-distroless`. For Windows, use the matching Windows tag from [Auth SDK sidecar container image tags](https://mcr.microsoft.com/v2/entra-sdk/auth-sidecar/tags/list). -## Configure your Microsoft Entra ID Auth SDK (sidecar) settings+Use `SignedAssertionFilePath` instead when the container receives a workload identity token from its orchestrator. Use `ClientSecret` only for local development. Don't place the blueprint credential in the agent container. -Follow these steps to configure your Microsoft Entra ID Auth SDK (sidecar) settings:+For other credential sources, see [Microsoft.Identity.Web credential descriptions](https://aka.ms/ms-id-web/credential-description). -[!INCLUDE [Dont use secrets](./includes/do-not-use-secrets.md)]+## Configure a downstream API -1. Set up the necessary components in Microsoft Entra ID. Ensure you register your application in the Microsoft Entra ID tenant.+Give each downstream API a short name. Configure its base URL, scopes, and token type. For example, this profile requests app-only tokens for Microsoft Graph: -1. Configure your client credentials. This credential can be a client secret, a certificate, or a managed identity that you're using as a federated identity credential. +```json+{+ "DownstreamApis": {+ "graph-app": {+ "BaseUrl": "https://graph.microsoft.com/v1.0/",+ "Scopes": [+ "https://graph.microsoft.com/.default"+ ],+ "RequestAppToken": true+ }+ }+}+``` -1. If you're calling a downstream API, ensure that the necessary permissions are granted. Calling a custom web API requires you to provide the API registration details in the SDK configuration.+The name becomes the `{apiName}` route value. This example uses `graph-app`, so the agent requests `/AuthorizationHeaderUnauthenticated/graph-app`. -For more information, see [Configure your Microsoft Entra ID Auth SDK (sidecar) settings](/entra/msidweb/agent-id-sdk/configuration).+The resource-specific articles provide the configuration for each API. To configure the container with environment variables, replace each `:` in the JSON path with `__`. For example: -## Acquire tokens using the Microsoft Entra ID Auth SDK (sidecar)+```yml+environment:+ DownstreamApis__graph-app__BaseUrl: https://graph.microsoft.com/v1.0/+ DownstreamApis__graph-app__Scopes__0: https://graph.microsoft.com/.default+ DownstreamApis__graph-app__RequestAppToken: "true"+``` -These are the steps to acquire tokens using the Microsoft Entra ID Auth SDK (sidecar):+## Keep identity overrides disabled -1. Acquire token using the Microsoft Entra ID Auth SDK (sidecar). This varies based on whether the agent is operating autonomously or on behalf of a user. There are three scenarios to consider:+Use the client ID recorded during setup directly. Don't pass `AgentIdentity`, `AgentUserId`, or `AgentUsername`: these select a different identity flow, not the cloud-agent setup in this article. - - Autonomous agents: Agents operating on their own behalf using service principals created for agents (autonomous).- - Autonomous agent's user account: Agents operating on their own behalf using user principals created specifically for agents (for instance agents having their own mailbox).- - Interactive agents: Agents operating on behalf of human users.+Keep overrides disabled on the endpoints used by the agent: - Specify the downstream API by including its name in the request URL based on your Microsoft Entra ID Auth SDK (sidecar) configuration. The authorization header endpoint takes the format `/AuthorizationHeader/{serviceName}` where `serviceName` is the name of the downstream API configured in the SDK settings.+```json+{+ "Sidecar": {+ "AllowOverrides": {+ "GetAuthorizationHeader": false,+ "GetAuthorizationHeaderUnauthenticated": false,+ "CallDownstreamApi": false,+ "CallDownstreamApiUnauthenticated": false+ }+ }+}+``` -1. To acquire an app-only (client credentials) token for an autonomous agent, you provide the agent identity client ID in the request.+Keep the sidecar accessible only through the shared loopback boundary even when overrides are disabled. The unauthenticated endpoints can acquire app-only tokens with the configured credential. - ```bash- GET /AuthorizationHeader/Graph?AgentIdentity=<agent-identity-client-id>- Authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbGc...- ```+## Verify the sidecar -1. To acquire token for an autonomous agent's user account, provide either the user object ID or User Principal Name but not both. This means providing either `AgentUsername` or `AgentUserId`. Providing both causes a validation error. You must also provide the `AgentIdentity` to specify which agent identity to use for token acquisition. If the agent identity parameter is missing, the request fails with a validation error.+From the agent container in the shared network namespace, request `http://localhost:5000/healthz`: - ```bash- GET /AuthorizationHeader/Graph?AgentIdentity=<agent-identity-client-id>&AgentUserId=<agent-user-object-id>- Authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbGc...- ```+```http+GET /healthz+``` - ```bash- GET /AuthorizationHeader/Graph?AgentIdentity=<agent-identity-client-id>&AgentUsername=<agent-user-principal-name>- Authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbGc...- ```+The endpoint reports whether the sidecar is accepting requests. It doesn't verify the credential, consent, or downstream API access. Test token acquisition and a downstream call separately. Don't expose it as a public health endpoint. -1. For interactive agents, use the on-behalf-of (OBO) flow. The agent first validates the user token granted to it before acquiring the resource token to call the downstream API.+## Choose an endpoint - Agent web API receives user token from the calling application and validates the token via the Microsoft Entra ID Auth SDK (sidecar) `/Validate` endpoint- Acquire token for downstream APIs by calling `/AuthorizationHeader` with only the `AgentIdentity` and the incoming authorization header- - ```bash- # Step 1: Validate incoming user token- GET /Validate- Authorization: Bearer <user-token>- - # Step 2: Get authorization header on behalf of the user- GET /AuthorizationHeader/Graph?AgentIdentity=<agent-identity-client-id>- Authorization: Bearer <user-token>- ```+| Operation | Endpoint |+| --- | --- |+| Validate an inbound access token and return its claims | `GET /Validate` |+| Get an authorization header using an inbound user token | `GET /AuthorizationHeader/{apiName}` |+| Get an authorization header without an inbound user token | `GET /AuthorizationHeaderUnauthenticated/{apiName}` |+| Have the sidecar call a configured downstream API | `POST /DownstreamApi/{apiName}` |+| Have the sidecar call a configured downstream API without an inbound user token | `POST /DownstreamApiUnauthenticated/{apiName}` | -## Call an API+Use the named downstream API profile without identity query parameters. For example, request `/AuthorizationHeaderUnauthenticated/graph-app` for app-only access or `/AuthorizationHeader/graph` with an inbound user token for OBO. -When obtaining the authorization header for calling a downstream API, the Microsoft Entra ID Auth SDK (sidecar) returns the `Authorization` header value that can be used directly in your API calls. +The authorization-header endpoints return an `authorizationHeader` value. Treat it as a credential and don't log it. -You can use this header to call the downstream API. The web API should validate the token by calling the `/Validate` endpoint of the Microsoft Entra ID Auth SDK (sidecar). This endpoint returns token claims for further authorization decisions.+The profile name in the endpoint must match a name under `DownstreamApis`. The configuration above defines `graph-app`, so `/AuthorizationHeaderUnauthenticated/graph-app` is valid. It doesn't define a `graph` profile. To use `/AuthorizationHeader/graph` for OBO, configure a separate delegated `graph` profile as shown in [Call Microsoft Graph as a user](sidecar-call-graph-as-user.md). The endpoint path selects which identity supplies the token; the profile name selects the API configuration.++For complete request and response details, see the [Auth SDK sidecar endpoint reference](/entra/msidweb/agent-id-sdk/endpoints).+An unconfigured profile name returns `400 Bad Request`; correct the route name or add the matching `DownstreamApis` entry. -## Related content+## Next steps -- [Python implementation of Microsoft Entra ID Auth SDK (sidecar)](/entra/msidweb/agent-id-sdk/scenarios/using-from-python)-- [TypeScript implementation of Microsoft Entra ID Auth SDK (sidecar)](/entra/msidweb/agent-id-sdk/scenarios/using-from-typescript)-- [Call a downstream API - Microsoft Entra ID Auth SDK (sidecar) docs](/entra/msidweb/agent-id-sdk/scenarios/call-downstream-api)+- [Run the sidecar for local development](sidecar-local-development.md).+- [Call a custom API as the agent](sidecar-call-custom-api-as-agent.md).+- [Authenticate users](sidecar-authenticate-users.md).+- [Review the sidecar source code](https://github.com/AzureAD/microsoft-identity-web/tree/master/src/Microsoft.Identity.Web.Sidecar).+- [Explore the official sidecar samples](https://github.com/microsoft/entra-agentid-samples/tree/dev/sidecar).+- [Build a platform that hosts an agent fleet](sidecar-fleet-provision-agent-identities.md). 