Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Outlook for iOS to match Android Authenticator Auto Open Behavior

From Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.

Rollout

Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".

Schedule dates changed in the text

Date phrases in schedule sentences differ between the versions we saw
  • Seen 30 Jan 2025 early January 2024 → early January 2025, late January 2025
  • Seen 11 Dec 2024 late November 2024, mid-December 2024 → early January 2024

Read from date phrases in Microsoft's text, not from notice metadata. A changed phrase can be a moved rollout, a new milestone or just rewording; "What changed" below shows which.

What the notice says

Microsoft’s text, safely structured

Updated January 30, 2025: We have updated the rollout timeline below. Thank you for your patience.

We're changing the way Outlook for iOS authenticates users with the Authenticator mobile app integration to match Outlook for Android. Currently in Outlook for iOS users are required to tap a button called "Open Authenticator" to initiate the Authenticator app authentication flow. In Outlook for Android this flow opens automatically without requiring the user to tap a button. We will now be matching that behavior in iOS so the user no longer has to tap the "Open Authenticator" button.

When this will happen

General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out this change in early January 2025 (previously late November) and expect to complete by late January 2025 (previously mid-December).

How this will affect your organization

You are receiving this message because our reporting indicates your organization may be using Outlook for iOS. To see how many users are currently using Outlook for iOS there are report instructions here: Microsoft 365 Reports in the admin center - Email apps usage

Users will no longer need to tap the "Open Authenticator" button to initiate Authenticator app based mobile authentication, when this change is implemented.

What you need to do to prepare

When this change takes effect, users and admins will not need to do anything for your organization to take advantage of this behavior.

Information about device enrollment with Intune for iOS can be found here: Overview of Apple device enrollment in Microsoft Intune.

What changed

Between archive captures, newest first
  1. Updated December 10, 2024:January 30, 2025: We have updated the rollout timeline below. Thank you for your patience. … High, DoD): We will begin rolling out this change in early January 20242025 (previously late November) and expect to complete by late January 2025 (previously mid-December). How this will affect your organization: You are receiving this …

    • Tags Feature update, User impact → Updated message, Feature update, User impact

    Updated December 10, 2024: We have updated the rollout timeline below. Thank you for your patience. We're changing the way Outlook for iOS authenticates users with the Authenticator … Authenticator" button. When this will happen: General Availability (Worldwide, GCC, GCC High, DoD)DoD): We will begin rolling out this change in late Novemberearly January 2024 (previously late November) and expect to complete by mid-December 2024.late January (previously mid-December). How this will affect your organization: You are receiving this message because …

  2. · first version seen

Learn more

Links from the notice and their documentation checks

No related announcements were found in the saved public history. Check the source for newer announcements.

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
  • 2 linked pages have not been read yet.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 00:16 UTC · 274 of 275 readable · 251 fully read · 18 waiting for GitHub's hourly limit · documentation 469/469 current