Public mode

No tenant, Graph, or device access. Every item links to its source. What this means

Some sources or documents need attention: 258/260 feeds/APIs · 417/444 docs · checked 21:28 UTC Customize Public modeDiscuss ChangeIntel on Discord

Action required: Review property changes for Exchange Online scenarios

Action date

in 27 days Act by , as Microsoft's metadata states

What the notice says

Microsoft's text, with its sections, lists and tables; source markup removed

What and why

As part of our ongoing Exchange Online management and directory modernization efforts, we're simplifying legacy management scenarios and removing properties. We are deprecating selected properties returned or used with the following Exchange Online PowerShell scenarios:

  • Get-Mailbox -Migration
  • New-Mailbox -Migration

If your scripts, applications, or automation use these scenarios, review the affected properties and determine whether your workflows depend on them.

The change will be introduced in two phases:

  • Beginning November 15, 2026: Selected properties will no longer be returned in applicable Get-Mailbox -Migration and New-Mailbox -Migration responses.
  • Beginning December 15, 2026: The affected properties will be blocked from being configured through applicable New-Mailbox -Migration scenarios.

Rollout schedule

We will begin rolling out mid-November 2026 and expect to complete by mid-November 2026.

Impact on your organization

Your organization may be affected if you have scripts, applications, third-party solutions, or operational workflows that use the affected properties with -Migration scenarios.

For example, a script using: Get-Mailbox -Migration will no longer receive the affected properties in the returned object beginning November 10, 2026. This may affect automation that depends on those properties being present or expects a fixed set of properties in the response. If your workflows don't use any of the affected properties, no action is required.

Action required / Recommendations

Before November 15, 2026:

Required Actions

Review your -Migration workflows and make any required changes before November 15, 2026.

If an affected property is required for your scenario and you can't remove the dependency, contact Microsoft Support and provide the property name, cmdlet, usage scenario, and expected impact.

What changed

Between the versions this installation saw, newest first

This installation has seen one version of this notice, first on 19 Oct 2026. Later changes will show here.

Linked documentation

Microsoft pages the notice links to

This site links to Microsoft's pages instead of copying them. Installations inside an organization can keep a copy for comparison.

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.
  • Versions before 19 Oct 2026: this installation first saw the notice after Microsoft posted it.
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 19 Oct 21:28 UTC · 258 of 260 readable · 256 fully read · documentation 417/444 current