Public mode

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

Some sources, documents or advisories need attention: 272/272 feeds/APIs · 469/469 docs · 8/9 advisories · checked 08:27 UTC Customize Public modeDiscuss ChangeIntel on Discord

Microsoft Teams frontline BYOD onboarding wizard

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 this installation saw
  • Seen 18 Aug 2026 late November 2025, mid-January 2026
  • Seen 19 May 2026 mid-June 2026, early July 2026
  • Seen 23 Apr 2026 mid-May 2026, early June 2026 → mid-June 2026, early July 2026
  • Seen 23 Mar 2026 late April 2026, early May 2026 → mid-May 2026, early June 2026
  • Seen 19 Feb 2026 mid-March 2026, end of March 2026 → late April 2026, early May 2026
  • Seen 14 Jan 2026 mid-February 2026, end of February 2026 → mid-March 2026, end of March 2026
  • Seen 25 Nov 2025 end of January 2026 → late November 2025, mid-January 2026, mid-February 2026, end of February 2026

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, with source markup removed
Updated August 18, 2026: We have decided not to move forward with this change at this time. We apologize for any inconvenience. Introduction To support frontline workers using personal devices, Microsoft is introducing a dynamic onboarding wizard for Microsoft Teams. This experience is designed to simplify setup on Android and iOS devices, especially in environments with security policies like multi-factor authentication (MFA) and mobile application management. The wizard adapts automatically to your organization’s policies, helping drive secure and efficient Bring Your Own Device (BYOD) adoption. When this will happen: GA, Public Preview: We have decided not to move forward with this change at this time.  How this affects your organization: Who is affected: Frontline workers setting up Microsoft Teams on personal Android or iOS devices What will happen:A new onboarding wizard will be available via web, optimized for desktop kiosks or shared PCs The wizard dynamically adjusts based on your organization’s security policies Supports MFA setup, with emphasis on Microsoft Authenticator push notifications This tool is optional and designed to improve BYOD Microsoft Teams adoption What you can do to prepare: Review the admin documentation to understand the onboarding wizard’s capabilities and limitations Consider integrating the wizard into your new user onboarding workflows Communicate availability to helpdesk and frontline managers Update internal documentation if you support BYOD Microsoft Teams deployment Review documentation at the following link: Set up frontline Teams on personal devices Compliance considerations: No compliance considerations identified, review as appropriate for your organization.

What changed

Between archive captures, newest first
  1. Updated May 19,August 18, 2026: We have updated the timeline. Thank youdecided not to move forward with this change at this time. We apologize for your patience.any inconvenience. Introduction To support frontline workers using personal devices, Microsoft is introducing a … policies, helping drive secure and efficient Bring Your Own Device (BYOD) adoption. This message is associated with Roadmap ID 523213. When this will happen: GA, Public Preview: Rollout begins in late November 2025 and is and expected We have decided not to complete by mid-January 2026 General Availability: Rollout begins in mid-August (previously mid-June) and is and expected to complete by mid-September (previously early July). move forward with this change at this time.  How this affects your organization: Who is affected: Frontline workers setting up …

  2. Updated April 23,May 19, 2026: We have updated the timeline. Thank you for your patience. Introduction … and expected to complete by mid-January 2026 General Availability: Rollout begins in mid-June 2026 mid-August (previously mid-May)mid-June) and is and expected to complete by early July 2026 mid-September (previously early June).July). How this affects your organization: Who is affected: Frontline workers setting up …

  3. Updated MarchApril 23, 2026: We have updated the timeline. Thank you for your patience. … and expected to complete by mid-January 2026 General Availability: Rollout begins in mid-Maymid-June 2026 (previously late April) mid-May) and is and expected to complete by early JuneJuly 2026 (previously early May).June). How this affects your organization: Who is affected: Frontline workers setting up …

  4. Updated February 19,March 23, 2026: We have updated the timeline. Thank you for your patience. Introduction … and expected to complete by mid-January 2026 General Availability: Rollout begins in late April mid-May 2026 (previously mid-March)late April) and is and expected to complete by early MayJune 2026 (previously end of March).early May). How this affects your organization: Who is affected: Frontline workers setting up …

  5. Updated January 14,February 19, 2026: We have updated the timeline. Thank you for your patience. Introduction … and expected to complete by mid-January 2026 General Availability: Rollout begins in mid-Marchlate April 2026 (previously mid-February)mid-March) and is and expected to complete by end of March early May 2026 (previously end of February)March). How this affects your organization: Who is affected: Frontline workers setting up …

  6. Updated November 25, 2025:January 14, 2026: We have updated the timeline. Thank you for your patience. Introduction To … and expected to complete by mid-January 2026 General Availability: Rollout begins in mid-Februarymid-March 2026 (previously late January) mid-February) and is and expected to complete by end of FebruaryMarch 2026 (previously end of January)February) How this affects your organization: Who is affected: Frontline workers setting up …

  7. Updated November 17,25, 2025: We have updated the content.timeline. Thank you for your patience. Introduction To support frontline workers using personal … 523213. When this will happen: Public Preview: Rollout begins in late November 2025 and is and expected to complete by mid-January 2026 General Availability: Rollout begins in mid-February 2026 (previously late JanuaryJanuary) and is and expected to complete by end of JanuaryFebruary 2026 (previously end of January) How this affects your organization: Who is affected: Frontline workers setting up …

    • Tags New feature, User impact → Updated message, New feature, User impact

    Updated November 17, 2025: We have updated the content. Thank you for your patience. Introduction To support frontline workers using personal devices, Microsoft is introducing a … frontline managers Update internal documentation if you support BYOD Microsoft Teams deployment Before rollout, we will update this post with new documentation.Review documentation at the following link: Set up frontline Teams on personal devices Compliance considerations: No compliance considerations identified, review as appropriate for your organization.

  8. · first version seen

Linked documentation

Microsoft pages the notice links to

The notice links to no Microsoft Learn or Support page that this installation reads.

No related evidence found in this installation's recent collection. This does not establish that no announcement exists.

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.
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 26 Oct 08:27 UTC · 272 of 272 readable · 270 fully read · documentation 469/469 current