đź“‹ Microsoft Entra Documentation Changes

Daily summary for changes since April 7th 2026, 9:40 PM PDT

Report generated on April 8th 2026, 9:40 PM PDT

📊 Summary

16
Total Commits
0
New Files
4
Modified Files
0
Deleted Files
8
Contributors

📝 Modified Documentation Files

+2 / -6 lines changed
Commit: Remove preview note in documentation
Changes:
Before
After
title: Protect enterprise generative AI apps with prompt injection protection (preview)
description: "Protect your enterprise generative AI apps from prompt injection attacks with Microsoft's AI Gateway prompt injection protection."
ms.topic: how-to
ms.date: 03/24/2026
ms.author: jayrusso
author: HULKsmashGithub
ms.reviewer: KaTabish
 
---
 
# Protect enterprise generative AI applications with prompt injection protection (preview)
 
Prompt injection attacks pose a significant risk for generative AI apps. Bad actors craft malicious input to make a large language model (LLM) ignore instructions, expose sensitive data, perform unintended actions, or generate harmful content.
 
## High-level architecture
:::image type="content" source="media/how-to-ai-prompt-injection-protection/prompt-shield-architecture.png" alt-text="Diagram showing the architecture of network content filtering with Global Secure Access and Microsoft Purview." lightbox="media/how-to-ai-prompt-injection-protection/prompt-shield-architecture.png":::
 
> [!IMPORTANT]
> The Prompt Injection Protection feature is currently in PREVIEW.
> This information relates to a prerelease product that might be substantially modified before release. Microsoft makes no warranties, expressed or implied, with respect to the information provided here.
title: Protect enterprise generative AI apps with prompt injection protection (preview)
description: "Protect your enterprise generative AI apps from prompt injection attacks with Microsoft's AI Gateway prompt injection protection."
ms.topic: how-to
ms.date: 04/08/2026
ms.author: jayrusso
author: HULKsmashGithub
ms.reviewer: KaTabish
 
---
 
# Protect enterprise generative AI applications with prompt injection protection
 
Prompt injection attacks pose a significant risk for generative AI apps. Bad actors craft malicious input to make a large language model (LLM) ignore instructions, expose sensitive data, perform unintended actions, or generate harmful content.
 
## High-level architecture
:::image type="content" source="media/how-to-ai-prompt-injection-protection/prompt-shield-architecture.png" alt-text="Diagram showing the architecture of network content filtering with Global Secure Access and Microsoft Purview." lightbox="media/how-to-ai-prompt-injection-protection/prompt-shield-architecture.png":::
 
## Prerequisites
 
To complete the steps in this process, you must have the following prerequisites in place:
+1 / -1 lines changed
Commit: Update reviewer for continuous access evaluation doc
Changes:
Before
After
ms.subservice: conditional-access
ms.topic: concept-article
ms.date: 03/24/2026
ms.reviewer: vmahtani
ms.custom:
- has-adal-ref
- ai-gen-docs-bap
ms.subservice: conditional-access
ms.topic: concept-article
ms.date: 03/24/2026
ms.reviewer: sreyanthmora
ms.custom:
- has-adal-ref
- ai-gen-docs-bap
Modified by Faith Moraa Ombongi on Apr 8, 2026 12:10 PM
đź“– View on learn.microsoft.com
+1 / -1 lines changed
Commit: Remove broken link
Changes:
Before
After
| `acrs` | Auth Context IDs | JWT | Microsoft Entra ID | Indicates the Auth Context IDs of the operations that the bearer is eligible to perform. Auth Context IDs can be used to trigger a demand for step-up authentication from within your application and services. Often used along with the `xms_cc` claim. |
| `auth_time` | Time when the user last authenticated. | JWT | | |
| `ctry` | User's country/region | JWT | | This claim is returned if it's present and the value of the field is a standard two-letter country/region code, such as FR, JP, SZ, and so on. |
| `email` | The reported email address for this user | JWT, SAML | MSA, Microsoft Entra ID | This value is included by default if the user is a guest in the tenant. For managed users (the users inside the tenant), it must be requested through this optional claim or, on v2.0 only, with the OpenID scope. This value isn't guaranteed to be correct, and is mutable over time - never use it for authorization or to save data for a user. For more information, see [Validate the user has permission to access this data](access-tokens.md). If you're using the email claim for authorization, we recommend [performing a migration to move to a more secure claim](./migrate-off-email-claim-authorization.md). If you require an addressable email address in your app, request this data from the user directly, using this claim as a suggestion or prefill in your UX. |
| `fwd` | IP address | JWT | | Adds the original address of the requesting client (when inside a VNET). |
| `groups` | Optional formatting for group claims | JWT, SAML | | The `groups` claim is used with the GroupMembershipClaims setting in the [application manifest](reference-app-manifest.md), which must be set as well. |
| `idtyp` | Token type | JWT access tokens | Special: only in app-only access tokens | The value is `app` when the token is an app-only token. This claim is the most accurate way for an API to determine if a token is an app token or an app+user token. |
| `acrs` | Auth Context IDs | JWT | Microsoft Entra ID | Indicates the Auth Context IDs of the operations that the bearer is eligible to perform. Auth Context IDs can be used to trigger a demand for step-up authentication from within your application and services. Often used along with the `xms_cc` claim. |
| `auth_time` | Time when the user last authenticated. | JWT | | |
| `ctry` | User's country/region | JWT | | This claim is returned if it's present and the value of the field is a standard two-letter country/region code, such as FR, JP, SZ, and so on. |
| `email` | The reported email address for this user | JWT, SAML | MSA, Microsoft Entra ID | This value is included by default if the user is a guest in the tenant. For managed users (the users inside the tenant), it must be requested through this optional claim or, on v2.0 only, with the OpenID scope. This value isn't guaranteed to be correct, and is mutable over time - never use it for authorization or to save data for a user. For more information, see [Validate the user has permission to access this data](access-tokens.md). If you require an addressable email address in your app, request this data from the user directly, using this claim as a suggestion or prefill in your UX. |
| `fwd` | IP address | JWT | | Adds the original address of the requesting client (when inside a VNET). |
| `groups` | Optional formatting for group claims | JWT, SAML | | The `groups` claim is used with the GroupMembershipClaims setting in the [application manifest](reference-app-manifest.md), which must be set as well. |
| `idtyp` | Token type | JWT access tokens | Special: only in app-only access tokens | The value is `app` when the token is an app-only token. This claim is the most accurate way for an API to determine if a token is an app token or an app+user token. |
+1 / -1 lines changed
Commit: Adding email
Changes:
Before
After
|[Grit](https://www.gritiam.com/migration.html) |"Grit Software has deep expertise in consumer identity and access management, with a strong track record of helping Fortune 500 and mid-market companies execute complex transformation projects successfully and on time. For Azure AD B2C to Microsoft Entra External ID migrations, Grit's AI-powered migration service uses advanced coding agents to deliver accurate migrations in days, while ensuring customer data isn't sent to the underlying AI models." | [email protected] |
|[Modern 42](https://www.modern42.com/blog/microsoft-recommends-modern-42-for-azure-ad-b2c-entra-external-id-migrations-australia) |"Modern 42 is a specialist identity consultancy delivering enterprise-grade identity advisory and engineering services across Australia. With Microsoft Entra External ID experience for government and private sector customers, Modern 42 has both the technical expertise and experience required to assist any organization to transition from Azure AD B2C to Microsoft Entra External ID, no matter how complex or simple. Modern 42's approach combines strategic consulting with hands-on technical implementation, ensuring CIAM solutions align with your business objectives, regulatory requirements, customer experience expectations, and security best practices." | [email protected] |
|[PlanB.](https://www.planb.net/en/post/microsoft-entra-external-id) |"PlanB. combines deep identity and security expertise with a strong focus on measurable business outcomes. As an experienced partner within the Microsoft Entra ecosystem, we help organizations securely integrate and manage external identities at scale—customers, agents, partners, and suppliers—across their digital platforms. From identity strategy and architecture through hands-on implementation of Microsoft Entra External ID, we ensure security, governance, compliance, and user experience work seamlessly together. Our mission is to simplify complex identity scenarios, reduce risk, and enable sustainable digital growth built on trusted identity foundations." | Felix Rohmeier (Solution Expert for Identity), [email protected] |
|[Slalom](https://www.slalom.com/us/en/who-we-are/newsroom/microsoft-slalom-accelerate-microsoft-entra-migrations) |"Slalom is a trusted Microsoft partner that helps organizations modernize identity systems at scale. As an integration partner for Entra External ID migrations, Slalom offers practical experience in identity migrations, organizational change management, and secure customer access. Their B2C to Entra External ID migration approach combines strategic planning, architectural expertise, and proven delivery tools to simplify complex migrations and reduce risk. This empowers organizations to provide secure, scalable customer identity solutions and fully leverage the Microsoft Entra platform." | |
|[WhoIAM](https://whoiam.ai/product/azureadb2c-to-entraexternalid-migrati/) |"WhoIAM is a trusted specialist in Microsoft customer identity, uniquely positioned to guide organizations through the transition from Azure AD B2C to Microsoft Entra External ID. Founded by former Microsoft identity engineering leaders, WhoIAM brings deep, hands-on expertise across Azure AD B2C, Entra, and large-scale CIAM platforms. Through purpose-built migration tooling, proven just-in-time and bulk migration patterns, and close collaboration with customer engineering and security teams, WhoIAM helps organizations modernize identity with minimal disruption—ensuring continuity today while building a future-ready external identity foundation on Microsoft Entra." | [email protected] |
 
### Next steps
|[Grit](https://www.gritiam.com/migration.html) |"Grit Software has deep expertise in consumer identity and access management, with a strong track record of helping Fortune 500 and mid-market companies execute complex transformation projects successfully and on time. For Azure AD B2C to Microsoft Entra External ID migrations, Grit's AI-powered migration service uses advanced coding agents to deliver accurate migrations in days, while ensuring customer data isn't sent to the underlying AI models." | [email protected] |
|[Modern 42](https://www.modern42.com/blog/microsoft-recommends-modern-42-for-azure-ad-b2c-entra-external-id-migrations-australia) |"Modern 42 is a specialist identity consultancy delivering enterprise-grade identity advisory and engineering services across Australia. With Microsoft Entra External ID experience for government and private sector customers, Modern 42 has both the technical expertise and experience required to assist any organization to transition from Azure AD B2C to Microsoft Entra External ID, no matter how complex or simple. Modern 42's approach combines strategic consulting with hands-on technical implementation, ensuring CIAM solutions align with your business objectives, regulatory requirements, customer experience expectations, and security best practices." | [email protected] |
|[PlanB.](https://www.planb.net/en/post/microsoft-entra-external-id) |"PlanB. combines deep identity and security expertise with a strong focus on measurable business outcomes. As an experienced partner within the Microsoft Entra ecosystem, we help organizations securely integrate and manage external identities at scale—customers, agents, partners, and suppliers—across their digital platforms. From identity strategy and architecture through hands-on implementation of Microsoft Entra External ID, we ensure security, governance, compliance, and user experience work seamlessly together. Our mission is to simplify complex identity scenarios, reduce risk, and enable sustainable digital growth built on trusted identity foundations." | Felix Rohmeier (Solution Expert for Identity), [email protected] |
|[Slalom](https://www.slalom.com/us/en/who-we-are/newsroom/microsoft-slalom-accelerate-microsoft-entra-migrations) |"Slalom is a trusted Microsoft partner that helps organizations modernize identity systems at scale. As an integration partner for Entra External ID migrations, Slalom offers practical experience in identity migrations, organizational change management, and secure customer access. Their B2C to Entra External ID migration approach combines strategic planning, architectural expertise, and proven delivery tools to simplify complex migrations and reduce risk. This empowers organizations to provide secure, scalable customer identity solutions and fully leverage the Microsoft Entra platform." | [email protected] |
|[WhoIAM](https://whoiam.ai/product/azureadb2c-to-entraexternalid-migrati/) |"WhoIAM is a trusted specialist in Microsoft customer identity, uniquely positioned to guide organizations through the transition from Azure AD B2C to Microsoft Entra External ID. Founded by former Microsoft identity engineering leaders, WhoIAM brings deep, hands-on expertise across Azure AD B2C, Entra, and large-scale CIAM platforms. Through purpose-built migration tooling, proven just-in-time and bulk migration patterns, and close collaboration with customer engineering and security teams, WhoIAM helps organizations modernize identity with minimal disruption—ensuring continuity today while building a future-ready external identity foundation on Microsoft Entra." | [email protected] |
 
### Next steps