← Previous day

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

Native Authentication V2 guidance now separates browser domain requirements from mobile clients

The 18 November updates were dominated by documentation revisions, but several have practical administrator value: Embedded Native Authentication V2 guidance defines the browser-versus-native domain split and lists MSAL.js 5.29.1; SSPR writeback guidance covers PHS staged rollout with Cloud Sync; PIM and Windows Server with Intune preview scope is clearer; and Global Secure Access now states concrete cloud-firewall limits. Remaining edits mainly refine terminology, navigation, links, or examples.

This period briefing was generated by AI from the tracked Microsoft Learn and Message Center changes.

40 updates

16

Migrate Embedded native authentication from V1 to V2

Feature updateAction required

The documentation now requires tenant-verified custom domains for browser-based apps, while native Android and iOS clients can use their configured service authority without one or a CORS proxy. The listed MSAL.js minimum version is now 5.29.1.

Howto Arc Sign In Windows

Doc update

The documentation now alerts administrators who opted in to the public preview for managing Windows Server with Intune to verify the scope and assess whether qualifying devices may be affected.

Native Authentication API V2 reference

Doc update

The reference now identifies the API as V2 and explains that tenant-verified custom domains are required for browser-based apps, such as SPAs, but not for native iOS or Android clients using native HTTP transports.

Native Authentication Configure App

Feature updateAction required

Browser-based apps, including SPAs, require a tenant-verified custom domain for Native Authentication API V2. Android and iOS apps using native HTTP transports can use their configured service authority without a custom domain.

Embedded native authentication CORS concepts

Doc update

The documentation now scopes the custom-domain and CORS guidance to browser integrations using Embedded native authentication or BYO UX. It also states that non-browser clients using native HTTP transports don't require a custom domain.

Native Authentication

Feature updateAction required

Browser-based apps require a tenant-verified custom domain, while non-browser clients using native HTTP transports do not.

Native Authentication Flow

Feature updateAction required

The documentation now requires a tenant-verified custom domain for browser-based apps, such as SPAs, but not for non-browser clients such as iOS and Android apps.

Quickstart Native Authentication

Doc update

The React Next.js quickstart now uses MSAL for JavaScript 5.29.1 instead of 5.29.0, including the installation command.

Howto Vm Sign In Azure Ad Windows

Doc update

The documentation wording was revised around MDM enrollment and Microsoft Entra authentication. It explains that enabling the capability joins the Arc-enabled machine to Microsoft Entra and targets machines not joined to another domain.

Howto Vm Sign In Azure Ad Windows

Public previewAction required

The guide now tells administrators who opted in to Windows Server management with Intune to verify the scope and assess qualifying devices.

Howto Arc Sign In Windows

Doc update

The instructions were revised around Microsoft Entra joining Arc-enabled machines and disconnecting them from another domain before enabling the capability.

Howto Arc Sign In Windows

Doc update

The guide was revised to state that enabling the capability Microsoft Entra joins the Arc-enabled machine and is intended for machines not planned to join another domain, such as on-premises Active Directory or Microsoft Entra Domain Services.

Howto Vm Sign In Azure Ad Windows

Doc update

The documentation now identifies the joined device as an Arc-enabled machine and states that the scenario is intended for machines not planned to join another domain, such as on-premises Active Directory or Microsoft Entra Domain Services.

Howto Vm Sign In Azure Ad Windows

Doc update

The documentation now states that Entra Connect V2 users do not also need the Entra extension. It also explains the domain-join scenario when the extension is installed on a workgroup machine.

2

Howto Arc Sign In Windows

Doc update

The documentation now links to the current preview resource and states that qualifying devices might be automatically enrolled when the Entra extension is deployed.

Howto Vm Sign In Azure Ad Windows

Doc update

The documentation replaces the TechCommunity link with the aka.ms link for the public preview of managing Windows Server with Intune.

1

Microsoft Entra audit log activity reference

Doc update

The audit activities reference now includes resource policy events covering creation, updates, deletion, restoration, assignments, definitions, versions, and configuration.

1
1

Audit Activities

Doc update

The audit activities reference changes the category label from “Resource Policy” to “ResourcePolicy” for resource policy activities.

1
3

What is Privileged Identity Management?

Doc update

The PIM documentation now lists preview capabilities for My Access role activation, agent access, virtual machine connections, session analytics and recordings, session management, lower-privileged role activation, and active-to-eligible assignment conversion. It also notes that licensing and setup requirements vary.

Identity Governance Overview

Doc update

The documentation now covers PIM preview support for just-in-time Azure resource access by agents and agent identities, plus Azure Bastion session analytics, recordings, and session disconnection.

Pim Configure

Doc update

The overview now distinguishes activating eligible access from connecting to Azure VMs or supported Azure Arc-enabled Linux servers. It also specifies that selected active Azure Bastion sessions can be disconnected without deactivating role assignments.

2

Identity Governance Overview

Doc update

The overview now refers to PIM capabilities extending just-in-time Azure resource access to agents and agent identities, while the linked agent capability remains marked as preview.

Identity Governance Overview

Doc update

The overview now clarifies connections to Azure virtual machines or supported services and separates Azure Bastion session recordings from session disconnection.

1

Entitlement Management Reports

Doc update

The documentation now directs administrators through ID Governance > Entitlement Management > Reports > Access Drift instead of Access Guardian.

11

Supported Features

Doc update

The support matrix now documents OnPasswordSubmit across the listed integration paths and its support for just-in-time password migration during sign-in. It also clarifies custom URL domain requirements for browser-based API V2 apps versus non-browser native clients, and updates recovery and verification labels.

Choose Authentication Approach

Feature updateAction required

The documentation now states that V2 requires a tenant-verified custom domain for browser-based apps and recommends planning a CORS proxy or edge policy. BYO UX guidance now emphasizes independently hosted, reusable authentication websites.

Planning Your Solution

Feature updateAction required

The documentation now states that browser-based apps using Native Authentication API V2 require a tenant-verified custom domain, while native non-browser clients do not. BYO UX still requires one.

Custom URL Domains

Feature updateAction required

Native Authentication API V2 requires a tenant-verified custom domain for browser-based apps such as SPAs, while non-browser iOS and Android clients using native HTTP transports do not require one.

Enable Password Reset Customers

Doc update

The Microsoft-hosted authentication section now describes Email OTP and SMS as supported recovery methods and explains the password-reset flow after passcode verification.

User Attributes

Doc update

The documentation now directs Embedded native authentication and BYO UX users to follow the native authentication attribute contract, including exact returned `attributeId` values, current requirements, and validation metadata.

Bring Your Own Ux

Doc update

Five related-topic links had trailing periods removed. Their destinations and topics are unchanged.

Bring Your Own Ux

Doc update

The reference page’s three related-document links were reformatted for consistent list and punctuation styling.

Configure Bring Your Own Ux

Doc update

The configuration page’s overview and API/protocol reference links no longer include trailing periods.

1

Current Known Limitations

Doc update

The documentation now states that cloud firewall supports up to 1,000 rules per tenant and a combined total of 500 sources and destinations per rule.

Daily Entra.News

Get daily email updates

Get a concise summary of the latest Microsoft Entra updates delivered straight to your inbox.

Loading the secure signup form…