MC1511071: Exchange Online Deprecates Properties in Get-Mailbox and New-Mailbox Migration Scenarios

MWPRO IMPACT SCORE
OPERATIONAL IMPACT
59
0 25 50 75 100
HIGH IMPACT • REVIEW RECOMMENDED
Recommended Action:
Review the update and plan any required actions before rollout.
▶ What is MWPro Impact Score? Watch our 60‑second explainer

Primary Audience

Exchange AdminsTenant AdminsIT ManagersService Owners
Why this score?
AI Confidence
HIGH
Enough detail is available to trust this assessment.
Assessment Reasoning
This is an active deprecation notice for Exchange Online PowerShell properties used in mailbox migration cmdlets. Admins must identify and update any scripts or applications using affected properties before mid-November 2026. The impact is largely administrative and affects automation reliability rather than end-user experience, with moderate implementation effort needed for script review and testing.
75
🛡️ Admin Impact
15
👥 User Impact
65
⚡ Urgency
60
🔧 Effort
ℹ️ WHAT YOU NEED TO KNOW
📌

AT A GLANCE

Microsoft is deprecating certain properties in Exchange Online PowerShell -Migration scenarios. Review any scripts or integrations that rely on these properties before mid-November 2026.
👥

END USERS

No major end-user change expected.
🛡️

IT ADMINS

Review and update any PowerShell scripts or tools using Get-Mailbox -Migration or New-Mailbox -Migration before November 2026.
📅

ROLLOUT TIMELINE

Upcoming:
November 2026

📢 Official Microsoft Message Center Announcement


Action required: Review property changes for Exchange Online scenarios
Message ID: MC1511071

[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:

  1. Review scripts, applications, and integrations that use Get-Mailbox -Migration, New-Mailbox -Migration, or Set-Mailbox -Migration.
  2. Review the published list of affected properties.
  3. Identify whether your workflows depend on any affected property.
  4. Update and test affected workflows to remove the dependency.
  5. For the complete list of affected properties and additional guidance, see: Changes to Get-Mailbox and New-Mailbox specifically with the Migration parameter | Microsoft Learn.

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.

Source: Microsoft Message Center • Analysed by MWPro

Share This Update