Exchange Online Admins Must Act Now as Microsoft Retires Key PowerShell Properties


exchange online issues
Image credit: Microsoft

Microsoft is working on an upcoming change for Exchange Online, but administrators have little time left to review their automation. The company has confirmed that it is retiring selected properties used by migration-related PowerShell commands. Organizations relying on these properties could see scripts and workflows break unless they make the necessary changes.

Exchange Online migration commands are losing properties

According to Microsoft Message Center ID MC1511071, the change affects Get-Mailbox -Migration and New-Mailbox -Migration. Microsoft is removing selected properties as part of its ongoing directory modernization efforts. The rollout has two stages. Starting November 15, 2026, affected properties will no longer appear in applicable command responses. From December 15, 2026, Microsoft will also block those properties from being configured through applicable New-Mailbox -Migration scenarios.

This could create problems for scripts expecting a fixed set of properties. Applications, third-party solutions, and automated workflows may also be affected. Microsoft says organizations that do not use the affected properties do not need to take action. Microsoft also mentions that some responses may stop returning properties beginning November 10. That makes reviewing existing workflows particularly important.

What Exchange Online administrators need to do

Microsoft recommends reviewing scripts and integrations using Get-Mailbox -Migration, New-Mailbox -Migration, and Set-Mailbox -Migration. Administrators should compare their workflows against the affected property list published here. Any dependency should be removed, followed by proper testing. This should help prevent automation failures after the changes reach Exchange Online.

That being said, Microsoft has also provided an option for organizations unable to remove a dependency. They should contact Microsoft Support and provide the affected property name, cmdlet, usage scenario, and expected impact. All that said, the November 15 deadline has passed by, while the configuration restriction follows on December 15.

More about the topics: microsoft, Microsoft Exchange, PowerShell

Readers help support Windows Report. We may get a commission if you buy through our links. Tooltip Icon

Read our disclosure page to find out how can you help Windows Report sustain the editorial team. Read more

User forum

0 messages