Microsoft Entra: Upcoming changes to federatedTokenValidationPolicy default settings
Microsoft Entra will enforce stricter federatedTokenValidationPolicy by default starting mid-August 2026, blocking federated sign-ins when internalDomainFederation doesn’t match the user’s UPN domain. This affects tenants with federated domains configured before December 2025 and aims to enhance security against cross-domain sign-in risks. To strengthen security for federated authentication, Microsoft Entra will update the default behavior of federatedTokenValidationPolicy. This policy governs how Microsoft Entra validates federated authentication tokens and determines whether sign-ins are allowed when the internalDomainFederation does not match the user’s UPN domain. Previously, enforcing this behavior required explicit tenant configuration, but it will now be applied by default to reduce the risk of unintended cross-domain sign-ins caused by misconfigured or overly permissive federation trust relationships. When this will happen General Availability (Worldwide, GCC, GCCH, and DoD): We will begin rolling out in mid-August 2026 and expect to complete by mid-August 2026. How this affects your organization Who is affected Microsoft 365 tenants using federated authentication in Microsoft Entra Admins managing federated domains that were configured before December 2025 Applies only to federated domains that have an internalDomainFederation object What will happen By default, federated sign-ins will be blocked when the internalDomainFederation does not match the user’s UPN domain. The internalDomainFederation object is typically created automatically during federation setup with Active Directory Federation Services (AD FS) or other identity providers (IdPs). This stricter default behavior of the federatedTokenValidationPolicy is already enforced for federated domains added since December 2025. After this change, the same behavior will apply to all existing federated domains with an internalDomainFederation object. Impacted sign-ins will fail with the error: AADSTS5000820: Sign-in blocked by Federated Token Validation policy. Contact your administrator for details. There is no change to the user experience unless cross-domain federated sign-ins are currently occurring. What you can do to prepare No action is required for most organizations. Cross-domain federated sign-ins will be blocked automatically as part of this security improvement. Organizations that rely on cross-domain federated sign-ins should review their existing federation configurations before rollout. (Strongly discouraged) If required for business continuity, Security Administrators, Hybrid Identity Administrators, or External Identity Provider Administrators can use Microsoft Graph […]
The post Microsoft Entra: Upcoming changes to federatedTokenValidationPolicy default settings appeared first on M365 Admin.
Published on:
Learn moreWe can help you with Microsoft Entra: Upcoming changes to federatedTokenValidationPolicy default settings
If you want help implementing, troubleshooting, or improving this product, contact us and we’ll point you in the right direction.
Related posts
Copilot Studio – Create Dataverse agent users with Microsoft Entra agent ‘s user account
We are announcing the ability to create Dataverse agent users with Microsoft Entra agent’s user account in Copilot Studio. This feature ...
Low-latency alerts and metrics in Monitor
We are announcing the ability to evaluate alert rules and review supported metrics for business-critical resources every hour in Monitor, help...
Enhanced prompt categories for Microsoft 365 Copilot in Microsoft Copilot Dashboard and Agent 365 Business Analytics
Microsoft 365 Copilot introduces 13 enhanced prompt categories replacing four legacy ones in the Copilot Dashboard and Agent 365 Business Anal...
Microsoft Teams mobile: Updated app bar and More menu on iOS and iPadOS
Microsoft Teams for iOS/iPadOS will update the app bar and More menu to align with iOS 26 design, showing four apps plus a categorized More me...
Microsoft Copilot: GPT-6.2 Sol and Astra rolling out
Microsoft Copilot is expanding AI model options with GPT-6.2 Sol and Astra, rolling out across Cowork, Copilot Studio, Word, Excel, PowerPoint...
Power Platform Monitor – Route alert notifications to connector-backed destinations
We are announcing the ability to route Power Platform Monitor alert notifications to Microsoft Teams, SMS, work item tracking systems, and oth...
Updates to Workforce Insights Agent (Frontier) for Admins in Microsoft 365 Copilot
Microsoft 365 Copilot’s Workforce Insights Agent (Frontier) adds a workspace for admins to configure organizational data and context, im...
Microsoft Teams: Tenant policy controls who can record and transcribe
Microsoft Teams will introduce a tenant policy controlling who can record and transcribe meetings, allowing admins to set permissions for orga...
Microsoft Copilot: In-app browsing will be enabled by default in the desktop app
Microsoft Copilot desktop app will enable in-app browsing by default starting January 2027, allowing users to open websites shared in chat wit...
Copilot video creation in Clipchamp Video Hub is now live in Frontier Public
Copilot video creation in Clipchamp Video Hub is now in public preview, enabling users to create and refine videos from documents and prompts ...