Daily.Entra.News7 changes were tracked across 2 Microsoft Entra products. The leading updates include Retirement of external access token for actionable messages – moving to Microsoft Entra authentication; Run a registration campaign to set up passkey or Microsoft Authenticator; Add custom headers to native authentication network requests in iOS (Swift).
Learn how to run a registration campaign in Microsoft Entra ID to nudge users toward passkeys or Microsoft Authenticator for stronger sign-in security.
b. Copy the link from Post-back/ACS URL field in Samsara into the **Reply URL** text box in Entra ID.
External access tokens for actionable messages will be retired by May 15, 2026, replaced by Microsoft Entra authentication to enhance security. Organizations must update integrations before this date, as messages using legacy tokens will fail. The phase-out completes by June 8, 2026.
Learn how to attach custom x-* headers to native authentication network requests in an iOS (Swift) app to integrate fraud-detection SDKs with Microsoft Entra External ID.
Learn how to attach custom x-* headers to native authentication network requests in an Android (Kotlin) app to integrate fraud-detection SDKs with Microsoft Entra External ID.
By default, after a customer signs in to an app that uses your user flow, they see a **Stay signed in?** prompt asking whether to stay signed in across browser sessions. If the user selects **Yes**, a persistent authentication cookie is issued and they remain signed in across browser sessions. If they select **No**, a non-persistent cookie is issued.
1. On the **New SAML/WS-Fed IdP** page, enter the following:
