Daily.Entra.NewsDaily AI-generated highlights from Microsoft Learn and Message Center. About this project →
The main substantive addition is a new Global Secure Access how-to for migrating eligible web content filtering policies from V1 to V2. The existing Web Filtering page now links to that guidance. Separate Entra ID and ID Protection updates clarify documented limitations and remediation behavior rather than announcing new features.
Global Secure Access · GeneralThe Global Secure Access migration guide covers eligible and ineligible security profiles, naming, and the guided migration process. Each V1 policy becomes a rule in one enabled V2 policy while preserving destinations, actions, and priorities. Profiles that already contain V2 policies require manual handling, and evaluation across multiple security profiles differs between V1 and V2.
Entra ID · AuthenticationUpdated Entra ID guidance states that authentication-strength policies cannot currently be applied to external users authenticating through Microsoft personal (MSA) accounts. It directs administrators to use the MFA grant control instead. This documents a limitation and alternative control; it does not establish a newly introduced product behavior.
ID Protection · AuthenticationThe updated guidance says disabling the Entra device blocks new token issuance, revokes user sessions, and prompts the user to sign in again. It no longer mentions revoking existing device-bound refresh tokens, making this a documentation clarification rather than evidence of a behavior change.
This period briefing was generated by AI from the tracked Microsoft Learn and Message Center changes.
The guidance now states that authentication strength policies cannot currently be applied to external users authenticating through Microsoft personal (MSA) accounts, alongside the previously listed methods. It directs administrators to use the MFA grant control instead.
The documentation now states that disabling the Entra device blocks new token issuance, revokes user sessions, and prompts the user to sign in again. It no longer mentions revoking existing device-bound refresh tokens.
The web filtering documentation now links to an article explaining how to migrate web content filtering policies from V1 to V2.
A new how-to article explains the guided Global Secure Access migration experience. It covers eligible and ineligible security profiles, migration steps, policy and rule naming, and how V1 policies become rules in a single enabled V2 policy while preserving destinations, actions, and priorities.
