The FAQ now states that identity provider buttons cannot be hidden. Removing a provider from a user flow prevents users from signing up or redeeming invitations with that provider, and `domain_hint` does not change this.
Keep up with Microsoft Entra
Daily AI-generated highlights from Microsoft Learn and Message Center. Browse the archive from 15 April 2025 → About this project →
Day in brief
Customer sign-in guidance says provider removal blocks signup and invitation redemption
Five Microsoft Learn revisions shaped the period. The most consequential update clarifies that customer sign-in identity-provider buttons cannot be hidden: removing a provider from a user flow prevents signup or invitation redemption with that provider, and `domain_hint` does not change the outcome. Other changes remove detailed Security Defaults management guidance, revise governance license mappings, and update federation examples.
- Customer sign-in provider removal blocks signup and invitation redemption
Entra ID · AuthenticationThe FAQ now says identity-provider buttons cannot be hidden. Removing a provider from a user flow prevents users from signing up or redeeming invitations with that provider, and `domain_hint` does not change this behavior. Review flows before removing a provider.
- Security Defaults article removes individual-protection management guidance
Entra ID · FundamentalsThe article no longer includes the section covering individual protections, their preview availability, roles, behavior, and management steps. Administrators relying on the article will no longer find that guidance there.
- Governance licensing guidance updates Microsoft 365 entitlement mappings
ID Governance · FundamentalsThe licensing fundamentals page now maps P1 to Microsoft 365 E3, E5, or E7; P2 to E5 or E7; and Governance capabilities to Microsoft Entra Suite and Microsoft 365 E7. The agent identity licensing reference was also updated.
- Application governance licensing guidance counts governed member users
ID Governance · GovernanceThe updated guidance says a tenant needs at least as many licenses as governed member, or non-guest, users. The count includes users who request, approve, or review application access.
- Federation issuer example uses the source tenant’s primary domain
External ID · GeneralThe user-creation example replaces the source tenant ID with its primary domain name in the issuer value and defines the new placeholder with an example domain. Administrators following the example should use the primary-domain format.
This period briefing was generated by AI from the tracked Microsoft Learn and Message Center changes.
5 updates
Microsoft Entra ID
2 updatesSecurity Defaults
Doc updateThe Security Defaults article no longer includes the section describing individual protections, their preview availability, roles, behavior, and management steps.
Microsoft Entra ID Governance
2 updatesMicrosoft Entra ID Governance licensing fundamentals
Feature updateThe documentation now lists P1 with Microsoft 365 E3, E5, or E7; P2 with E5 or E7; and Governance capabilities with Microsoft Entra Suite and Microsoft 365 E7. The agent identity licensing reference was also updated.
Identity Governance Applications Prepare
Doc updateThe article’s licensing guidance was updated. It states that the tenant needs at least as many licenses as governed member (non-guest) users, including users who request, approve, or review application access.
Microsoft Entra External ID
1 updateEntra Id Federation Customers
Doc updateThe user-creation example replaces the source tenant ID with its primary domain name in the issuer value and defines the new placeholder with an example domain.