Microsoft Entra Agent ID
AuthenticationValidate agent identity tokens in a downstream API
In brief
The documentation now refers to the “Microsoft Entra ID Auth SDK (sidecar)” instead of the “Microsoft Entra SDK auth sidecar.” The token-validation guidance is otherwise unchanged.
What Entra admins need to know
This is a terminology clarification only; no administrator action or product behavior change is indicated.
This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.
Documentation change
View on Microsoft LearnThe comparison below shows only the changed extract. Use the full-page view for complete context.
Validate agent identity tokens in a downstream API
When an AI agent calls your API through the Microsoft Entra ID Auth SDK auth sidecar,(sidecar), the request includes a Bearer token. Your API validates this token to confirm the request comes from an authenticated agent with the correct permissions. If validation fails, your API returns HTTP 401 with a reason.
This article explains the validation checks and shows how to configure and run a sample weather API that validates agent identity tokens end-to-end.
@@ -13,7 +13,7 @@ ai-usage: ai-assisted # Validate agent identity tokens in a downstream API -When an AI agent calls your API through the Microsoft Entra SDK auth sidecar, the request includes a `Bearer` token. Your API validates this token to confirm the request comes from an authenticated agent with the correct permissions. If validation fails, your API returns HTTP 401 with a reason.+When an AI agent calls your API through the Microsoft Entra ID Auth SDK (sidecar), the request includes a `Bearer` token. Your API validates this token to confirm the request comes from an authenticated agent with the correct permissions. If validation fails, your API returns HTTP 401 with a reason. This article explains the validation checks and shows how to configure and run a sample weather API that validates agent identity tokens end-to-end.