Use a QR code to sign-in to the Outlook mobile apps
As of August 2021, this experience has been put on hold indefinitely for commercial and enterprise users due to organizations' lack of control over them. The work involved in providing these controls is extensive and the Identity team continues to work on them. We rolled back this experience on commercial and enterprise users since we wanted to provide more security and customization for all the different cases they managed.
As the Microsoft 365 administrator, you can enable your users to sign in to Outlook for Android or iOS app on their mobile devices without having to enter their username and password. By scanning a QR code, users can securely authenticate and sign in to Outlook mobile.
In Outlook on the web or other desktop Outlook applications, users may see notifications informing them that they can use Outlook on their mobile device. The administrator can manage these notifications by using Exchange PowerShell. If users choose to send themselves an SMS text message to download the app on their mobile device, a QR code appears on their computer. They'll be able to scan the QR code to log into Outlook on their phone or tablet. This QR code is a short lived token that can only be redeemed once.
The notification is only generated if the following conditions are met:
The QR code experience is enabled for the tenant (this experience is enabled by default).
The user isn't already using Outlook for iOS and Android.
The user has an empty state at reading pane (doesn't select the option of auto opening the first email).
The user didn't dismiss the notification.
In some cases, your users must re-authenticate on their computer to generate the QR code.
Use Exchange PowerShell
This feature is on by default. To disable this feature, use the following steps.
Using PowerShell, you can disable the notifications informing your users about the Outlook mobile apps. This also prevents the QR code sign-in flow from being shown.
Set-OrganizationConfig -MobileAppEducationEnabled <Boolean>
When using the Exchange PowerShell command, changes may take up to 8 hours to propagate.