Merging changes synced from https://github.com/MicrosoftDocs/entra-docs-pr (branch live)

Author: Learn Build Service GitHub App

docs/agent-id/agent-oauth-protocols.md

@@ -11,7 +11,7 @@ ms.reviewer: jmprieur
 
 # Authentication protocols in agents
 
-Agents use OAuth 2.0 protocols with specialized token exchange patterns enabled by Federated Identity Credentials (FIC). All agent auth flows involve multi-stage token exchanges where the agent identity blueprint impersonates the agent identity to perform operations. This article explains the authentication protocols and token flows used by agents. It covers delegation scenarios, autonomous operations, and federated identity credential patterns. Microsoft recommends that you use our SDKs like [Microsoft Entra SDK for Agent ID](https://aka.ms/entra/sdk/agentid) since implementing these protocol steps isn't easy.
+Agents use OAuth 2.0 protocols with specialized token exchange patterns enabled by Federated Identity Credentials (FIC). All agent auth flows involve multi-stage token exchanges where the agent identity blueprint impersonates the agent identity to perform operations. This article explains the authentication protocols and token flows used by agents. It covers delegation scenarios, autonomous operations, and federated identity credential patterns. Microsoft recommends that you use our SDKs like [Microsoft Entra ID Auth SDK (sidecar)](https://aka.ms/entra/sdk/agentid) since implementing these protocol steps isn't easy.
 
 All agent entities are confidential clients that can also serve as APIs for On-Behalf-Of scenarios. Interactive flows aren't supported for any agent entity type, ensuring that all authentication occurs through programmatic token exchanges rather than user interaction flows.
 

docs/agent-id/authentication-with-auth-sdk-sidecar.md

@@ -77,8 +77,8 @@ The [Microsoft Entra Agent ID sidecar samples](https://github.com/microsoft/entr
 
 ## Related content
 
-- [Microsoft Entra SDK for Agent ID documentation](/entra/msidweb/agent-id-sdk/overview)
-- [Acquire tokens and call downstream APIs with Microsoft Entra SDK for Agent ID](microsoft-entra-sdk-for-agent-identities.md)
+- [Microsoft Entra ID Auth SDK (sidecar) documentation](/entra/msidweb/agent-id-sdk/overview)
+- [Acquire tokens and call downstream APIs with Microsoft Entra ID Auth SDK (sidecar)](microsoft-entra-sdk-for-agent-identities.md)
 - [Microsoft Entra Agent ID design patterns](concept-agent-id-design-patterns.md)
 - [Agent identity blueprints](agent-blueprint.md)
 - [Autonomous agent app OAuth flow](agent-autonomous-app-oauth-flow.md)

docs/agent-id/autonomous-agent-authentication-authorization-flow.md

@@ -533,7 +533,7 @@ You can also use the agent's user account principal name instead of the object I
 - [Call Microsoft Graph API](call-api-microsoft-graph.md)
 - [Call custom APIs](call-api-custom.md)
 - [Call Azure services](call-api-azure-services.md)
-- [Acquire token using Microsoft Entra SDK for agent ID](./microsoft-entra-sdk-for-agent-identities.md)
+- [Acquire token using Microsoft Entra ID Auth SDK (sidecar)](./microsoft-entra-sdk-for-agent-identities.md)
 - [Microsoft Graph permissions reference](/graph/permissions-reference)
 - [Permissions and consent in the Microsoft identity platform](/entra/identity-platform/permissions-consent-overview)
 - [Agent's user account flow in agents](agent-user-oauth-flow.md)

docs/agent-id/configure-third-party-agents.md

@@ -198,7 +198,7 @@ If you run into problems during integration, use the following guidance to ident
 
 ## Related content
 
-- [Configure SDK for agent identities](microsoft-entra-sdk-for-agent-identities.md)
+- [Configure Entra ID Auth SDK (sidecar) for agent identities](microsoft-entra-sdk-for-agent-identities.md)
 - [Call Microsoft Graph API](call-api-microsoft-graph.md)
 - [Call custom APIs](call-api-custom.md)
 - [Call Azure services](call-api-azure-services.md)

docs/agent-id/faq.yml

@@ -127,6 +127,6 @@ sections:
 
           Microsoft.Identity.Web provides higher-level APIs for acquiring tokens for agent identities in .NET applications. Use the [Microsoft.Identity.Web.AgentIdentities](https://github.com/AzureAD/microsoft-identity-web/blob/master/src/Microsoft.Identity.Web.AgentIdentities/README.AgentIdentities.md) package to simplify managing agent identities.
 
-          The Microsoft Entra SDK container wraps Microsoft.Identity.Web as a web service deployed as a sidecar container. Use this option when your agent runs on Kubernetes and/or isn't built in .NET. For more information, see [Microsoft Entra SDK for Agent ID](/entra/msidweb/agent-id-sdk/overview).
+          The Microsoft Entra SDK container wraps Microsoft.Identity.Web as a web service deployed as a sidecar container. Use this option when your agent runs on Kubernetes and/or isn't built in .NET. For more information, see [Microsoft Entra ID Auth SDK (sidecar)](/entra/msidweb/agent-id-sdk/overview).
 
           Microsoft Graph APIs provide agent identity management when the other options don't fit your scenario. For more information, see [Microsoft Graph API for agent identity blueprints](/graph/api/resources/agentidentityblueprint).

docs/agent-id/includes/call-api-common-dotnet.md

@@ -5,7 +5,7 @@ ms.topic: include
 # To guide users on how to call APIs using agent identities in .NET.
 ---
 
-To call an API from an agent, you need to obtain an access token that the agent can use to authenticate itself to the API. We recommend using the *Microsoft.Identity.Web* SDK for .NET to call your web APIs. This SDK simplifies the process of acquiring and validating tokens. For other languages, use the [Microsoft Entra agent SDK for agent ID](/entra/msidweb/agent-id-sdk/overview).
+To call an API from an agent, you need to obtain an access token that the agent can use to authenticate itself to the API. We recommend using the *Microsoft.Identity.Web* SDK for .NET to call your web APIs. This SDK simplifies the process of acquiring and validating tokens. For other languages, use the [Microsoft Entra ID Auth SDK (sidecar)](/entra/msidweb/agent-id-sdk/overview).
 
 ## Prerequisites
 

docs/agent-id/includes/use-microsoft-libraries.md

@@ -6,4 +6,4 @@ ms.topic: include
 ---
 
 > [!WARNING]
-> Microsoft recommends using the approved SDKs like Microsoft.Identity.Web and Microsoft Agent ID SDK libraries to implement these protocols. Manual implementation of these protocols is complex and error-prone, and using the SDKs helps ensure security and compliance with best practices.
+> Microsoft recommends using the approved SDKs like Microsoft.Identity.Web and Microsoft Entra ID Auth SDK (sidecar) libraries to implement these protocols. Manual implementation of these protocols is complex and error-prone, and using the SDKs helps ensure security and compliance with best practices.

docs/agent-id/index.yml

@@ -68,7 +68,7 @@ sections:
         summary: Use an AI coding agent to automate the full Agent ID onboarding workflow, from blueprint creation to agent provisioning.
         url: ./agent-id-ai-guided-setup.md
       - componentType: summary-card
-        title:  Microsoft Entra SDK for agents
+        title:  Microsoft Entra ID Auth SDK (sidecar)
         summary: Integrate agent authentication and authorization with familiar SDKs and developer tools.
         url: ./microsoft-entra-sdk-for-agent-identities.md
       - componentType: summary-card

docs/agent-id/key-concepts.md

@@ -33,7 +33,7 @@ When a blueprint is added to a tenant, Microsoft Entra creates a corresponding p
 
 ### Traditional service principal (not recommended for AI agents)
 
-Traditional service principals were designed for static, deterministic workloads. Microsoft Entra Agent ID exists because service principals lack the governance infrastructure AI agents need.There's no enforced sponsorship, no agent-aware audit entries, and no blueprint-managed lifecycle. For more information, see [Agent identities, service principals, and applications](agent-service-principals.md).
+Traditional service principals were designed for static, deterministic workloads. Microsoft Entra Agent ID exists because service principals lack the governance infrastructure AI agents need. There's no enforced sponsorship, no agent-aware audit entries, and no blueprint-managed lifecycle. For more information, see [Agent identities, service principals, and applications](agent-service-principals.md).
 
 ### Regular user account (not recommended for AI agents)
 
@@ -55,9 +55,9 @@ The agent identity platform introduces an administrative model that separates te
 
 For more information, see [Administrative relationships for agent identities (Owners, sponsors, and managers)](agent-owners-sponsors-managers.md)
 
-## Microsoft Entra SDK for agent ID
+## Microsoft Entra ID Auth SDK (sidecar)
 
-The Microsoft Entra SDK for Agent ID is a containerized web service that handles token acquisition, validation, and secure downstream API calls for agents registered in the Microsoft identity platform. It runs as a companion container alongside your application, allowing you to offload identity logic to a dedicated service. For more information, see [Microsoft Entra SDK for Agent ID](/entra/msidweb/agent-id-sdk/overview).
+The Microsoft Entra ID Auth SDK (sidecar) is a containerized web service that handles token acquisition, validation, and secure downstream API calls for agents registered in the Microsoft identity platform. It runs as a companion container alongside your application, allowing you to offload identity logic to a dedicated service. For more information, see [Microsoft Entra ID Auth SDK (sidecar)](/entra/msidweb/agent-id-sdk/overview).
 
 ## Related content
 

docs/agent-id/microsoft-entra-sdk-for-agent-identities.md

@@ -1,33 +1,33 @@
 ---
-title: Acquire tokens and call downstream APIs with Microsoft Entra SDK for Agent ID
+title: Acquire tokens and call downstream APIs with Microsoft Entra ID Auth SDK (sidecar)
 titleSuffix: Microsoft Entra Agent ID
-description: Learn how autonomous agents acquire tokens using the Microsoft Entra SDK for Agent ID to call downstream APIs independently.
+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 SDK for Agent ID so that my agents can independently call downstream APIs with proper authentication.
+#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.
 ---
 
-# Acquire tokens and call downstream APIs with Microsoft Entra SDK for Agent ID
+# Acquire tokens and call downstream APIs with Microsoft Entra ID Auth SDK (sidecar)
 
-The Microsoft Entra SDK for Agent ID 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 SDK for Agent ID manages token acquisition, validation, and API calls through standard HTTP requests.
+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.
 
 ## Prerequisites
 
 Before you begin, ensure you have:
 
-- [Set up the Microsoft Entra SDK for Agent ID](/entra/msidweb/agent-id-sdk/installation)
+- [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)
 
 ## Deploy your containerized service
 
-Deploy the Microsoft Entra SDK for Agent ID as a containerized service in your environment. Follow the instructions in the [Set up the Microsoft Entra SDK for Agent ID](/entra/msidweb/agent-id-sdk/installation) guide to configure the service with your agent identity details.
+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.
 
-## Configure your Microsoft Entra SDK for Agent ID settings
+## Configure your Microsoft Entra ID Auth SDK (sidecar) settings
 
-Follow these steps to configure your Microsoft Entra SDK for Agent ID settings:
+Follow these steps to configure your Microsoft Entra ID Auth SDK (sidecar) settings:
 
 [!INCLUDE [Dont use secrets](./includes/do-not-use-secrets.md)]
 
@@ -37,19 +37,19 @@ Follow these steps to configure your Microsoft Entra SDK for Agent ID settings:
 
 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.
 
-For more information, see [Configure your Microsoft Entra SDK for Agent ID settings](/entra/msidweb/agent-id-sdk/configuration).
+For more information, see [Configure your Microsoft Entra ID Auth SDK (sidecar) settings](/entra/msidweb/agent-id-sdk/configuration).
 
-## Acquire tokens using the Microsoft Entra SDK for Agent ID
+## Acquire tokens using the Microsoft Entra ID Auth SDK (sidecar)
 
-These are the steps to acquire tokens using the Microsoft Entra SDK for Agent ID:
+These are the steps to acquire tokens using the Microsoft Entra ID Auth SDK (sidecar):
 
-1. Acquire token using the Microsoft Entra SDK for Agent ID. This varies based on whether the agent is operating autonomously or on behalf of a user. There are three scenarios to consider:
+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:
 
     - 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.
 
-    Specify the downstream API by including its name in the request URL based on your agent ID SDK configuration. The authorization header endpoint takes the format `/AuthorizationHeader/{serviceName}` where `serviceName` is the name of the downstream API configured in the SDK settings.
+    Specify the downstream API by including its name in the request URL based on your 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.
 
 1. To acquire an app only token for an autonomous agent, you provide the agent identity client ID in the request.
 
@@ -72,7 +72,7 @@ These are the steps to acquire tokens using the Microsoft Entra SDK for Agent ID
 
 1. For interactive agents, use the on-behalf of flow. The agent first validates the user token granted to it before acquiring the resource token to call the downstream API.
 
-    Agent web API receives user token from the calling application and validates the token via the agent ID SDK `/Validate` endpoint
+    Agent web API receives user token from the calling application and validates the token via the 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
@@ -87,12 +87,12 @@ These are the steps to acquire tokens using the Microsoft Entra SDK for Agent ID
 
 ## Call an API
 
-When obtaining the authorization header for calling a downstream API, the Microsoft Entra SDK for Agent ID returns the `Authorization` header value that can be used directly in your API calls. 
+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 SDK for Agent ID. This endpoint returns token claims for further authorization decisions.
+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.
 
 ## Related content
 
-- [Python implementation of Microsoft Entra SDK for Agent ID](/entra/msidweb/agent-id-sdk/scenarios/using-from-python)
-- [TypeScript implementation of Microsoft Entra SDK for Agent ID](/entra/msidweb/agent-id-sdk/scenarios/using-from-typescript)
-- [Call a downstream API - Microsoft Entra SDK for agent ID docs](/entra/msidweb/agent-id-sdk/scenarios/call-downstream-api)
+- [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)