MC1108848 – (Updated) Changing output format for some database properties in Exchange Online cmdlets

Microsoft Exchange Logo

check before: 2026-02-01

Product:

Exchange

Platform:

Online, World tenant

Status:

Change type:

Admin impact, Feature update, Updated message

Links:

Details:

Summary:
Exchange Online PowerShell cmdlets will update output formats for certain database-related properties starting February 2026, completing by April 2026. This change improves performance and consistency but only affects Exchange Online, not on-premises. No user action is required unless scripts parse these values.

Details:
Updated February 6, 2026: We have updated the content. The scope of the change remains unchanged. Thank you for your patience.
We're updating the output format of certain properties returned by Exchange Online PowerShell cmdlets to improve performance and align with backend service optimizations. This change reduces unnecessary data retrieval and enhances consistency across services.
[When this will happen:]
Rollout will begin in February 2026 (previously October 2025) and complete by April 2026 (previously November 2025).

Change Category:
XXXXXXX ... free basic plan only

Scope:
XXXXXXX ... free basic plan only

Release Phase:

Created:
2025-07-04

updated:
2026-02-07

Task Type

XXXXXXX ... free basic plan only

Docu to Check

XXXXXXX ... free basic plan only

MS How does it affect me

XXXXXXX ... free basic plan only

MS Preperations

XXXXXXX ... free basic plan only

MS Urgency

XXXXXXX ... free basic plan only

MS workload name

XXXXXXX ... free basic plan only

summary for non-techies**

Starting in February 2026, Exchange Online will update the format of certain database-related properties in PowerShell cmdlets to improve performance and consistency, requiring script adjustments if they rely on the old format.

Direct effects for Operations**

Change in Output Format
The output format of certain properties returned by Exchange Online PowerShell cmdlets will change, potentially breaking existing scripts that parse these values.
   - roles: IT Administrators, Developers
   - references: https://techcommunity.microsoft.com/t5/exchange-team-blog/updated-changing-output-format-for-some-database-properties-in/ba-p/3741230

Script Compatibility Issues
Scripts that rely on the previous output format may fail or produce incorrect results, leading to potential disruptions in automated processes.
   - roles: IT Administrators, DevOps Engineers
   - references: https://techcommunity.microsoft.com/t5/exchange-team-blog/updated-changing-output-format-for-some-database-properties-in/ba-p/3741230

Configutation Options**

XXXXXXX ... paid membership only

explanation for non-techies**

XXXXXXX ... free basic plan only

** AI generated content. This information must be reviewed before use.

a free basic plan is required to see more details. Sign up here


A cloudsocut.one plan is required to see all the changed details. If you are already a customer, choose login.
If you are new to cloudscout.one please choose a plan.



change history

DatePropertyoldnew
2026-02-07MC MessagesUpdated January 28, 2026: We have updated timelines for enforcement. The scope of the change remains unchanged. Thank you for your patience.
We're updating the output format of certain properties returned by Exchange Online PowerShell cmdlets to improve performance and align with backend service optimizations. This change reduces unnecessary data retrieval and enhances consistency across services.
[When this will happen:]
Rollout will begin in February 2026 (previously October 2025) and complete by April 2026 (previously November 2025).
Updated February 6, 2026: We have updated the content. The scope of the change remains unchanged. Thank you for your patience.
We're updating the output format of certain properties returned by Exchange Online PowerShell cmdlets to improve performance and align with backend service optimizations. This change reduces unnecessary data retrieval and enhances consistency across services.
[When this will happen:]
Rollout will begin in February 2026 (previously October 2025) and complete by April 2026 (previously November 2025).
2026-02-07MC Last Updated01/28/2026 18:28:512026-02-06T19:03:32Z
2026-02-07MC prepareNo action is required. There are no settings or controls to manage this change. If you have scripts that parse these property values, we recommend reviewing them to ensure compatibility.
The complete list of cmdlets impacted is as follows:
Cmdlet Output Type
Add-DistributionGroupMemberMicrosoft.Exchange.Data.Directory.Management.ReducedRecipient
Get-DistributionGroupMemberMicrosoft.Exchange.Data.Directory.Management.ReducedRecipient
Get-FederatedOrganizationIdentifier Microsoft.Exchange.Data.Directory.Management.FederatedOrganizationIdWithDomainStatus
Get-Mailbox Microsoft.Exchange.Data.Directory.Management.Mailbox
New-MailboxMicrosoft.Exchange.Data.Directory.Management.MailboxPlan
Get-MailboxPlanMicrosoft.Exchange.Data.Directory.Management.MailboxPlan
Get-MailUserMicrosoft.Exchange.Data.Directory.Management.MailUser
New-MailUser Microsoft.Exchange.Data.Directory.Management.MailUser
Get-RecipientMicrosoft.Exchange.Data.Directory.Management.ReducedRecipient
Add-RoleGroupMember Microsoft.Exchange.Data.Directory.Management.ReducedRecipient
Get-RoleGroupMember Microsoft.Exchange.Data.Directory.Management.ReducedRecipient
New-SyncMailPublicFolderMicrosoft.Exchange.Data.Directory.Recipient.ADPublicFolder

The affected properties for each Output Type are as follows:
Output TypeProperty
Microsoft.Exchange.Data.Directory.Recipient.ADPublicFolderDatabase
Microsoft.Exchange.Data.Directory.Recipient.ADPublicFolderHomeMTA
Microsoft.Exchange.Data.Directory.Management.FederatedOrganizationIdWithDomainStatusDelegationTrustLink
Microsoft.Exchange.Data.Directory.Management.MailboxDatabase
Microsoft.Exchange.Data.Directory.Management.MailboxPreviousDatabase
Microsoft.Exchange.Data.Directory.Management.MailboxDisabledArchiveDatabase
Microsoft.Exchange.Data.Directory.Management.MailboxMailboxMoveTargetMDB
Microsoft.Exchange.Data.Directory.Management.MailboxMailboxMoveSourceMDB
Microsoft.Exchange.Data.Directory.Management.MailboxMailboxMoveTargetArchiveMDB
Microsoft.Exchange.Data.Directory.Management.MailboxMailboxMoveSourceArchiveMDB
Microsoft.Exchange.Data.Directory.Management.MailboxPlanDatabase
Microsoft.Exchange.Data.Directory.Management.MailboxPlanPreviousDatabase
Microsoft.Exchange.Data.Directory.Management.MailboxPlanDisabledArchiveDatabase
Microsoft.Exchange.Data.Directory.Management.MailboxPlanMailboxMoveTargetMDB
Microsoft.Exchange.Data.Directory.Management.MailboxPlanMailboxMoveSourceMDB
Microsoft.Exchange.Data.Directory.Management.MailboxPlanMailboxMoveTargetArchiveMDB
Microsoft.Exchange.Data.Directory.Management.MailboxPlanMailboxMoveSourceArchiveMDB
Microsoft.Exchange.Data.Directory.Management.MailUserDisabledArchiveDatabase
No action is required. There are no settings or controls to manage this change. If you have scripts that parse these property values, we recommend reviewing them to ensure compatibility.
The complete list of cmdlets impacted is as follows:
Cmdlet Output Type
Add-DistributionGroupMemberMicrosoft.Exchange.Data.Directory.Management.ReducedRecipient
Get-DistributionGroupMemberMicrosoft.Exchange.Data.Directory.Management.ReducedRecipient
Get-FederatedOrganizationIdentifier Microsoft.Exchange.Data.Directory.Management.FederatedOrganizationIdWithDomainStatus
Get-Mailbox Microsoft.Exchange.Data.Directory.Management.Mailbox
New-MailboxMicrosoft.Exchange.Data.Directory.Management.MailboxPlan
Get-MailboxPlanMicrosoft.Exchange.Data.Directory.Management.MailboxPlan
Get-MailUserMicrosoft.Exchange.Data.Directory.Management.MailUser
New-MailUser Microsoft.Exchange.Data.Directory.Management.MailUser
Get-RecipientMicrosoft.Exchange.Data.Directory.Management.ReducedRecipient
Add-RoleGroupMember Microsoft.Exchange.Data.Directory.Management.ReducedRecipient
Get-RoleGroupMember Microsoft.Exchange.Data.Directory.Management.ReducedRecipient
New-SyncMailPublicFolderMicrosoft.Exchange.Data.Directory.Recipient.ADPublicFolder

The affected properties for each Output Type are as follows:
Output TypeProperty
Microsoft.Exchange.Data.Directory.Management.MailUserMailboxMoveSourceArchiveMDB
Microsoft.Exchange.Data.Directory.Management.MailUserMailboxMoveSourceMDB
Microsoft.Exchange.Data.Directory.Management.MailUserMailboxMoveTargetArchiveMDB
Microsoft.Exchange.Data.Directory.Management.MailUserMailboxMoveTargetMDB
Microsoft.Exchange.Data.Directory.Management.ReducedRecipientDatabase
Microsoft.Exchange.Data.Directory.Management.ReducedRecipientMailboxMoveSourceArchiveMDB
Microsoft.Exchange.Data.Directory.Management.ReducedRecipientMailboxMoveSourceMDB
Microsoft.Exchange.Data.Directory.Management.ReducedRecipientMailboxMoveTargetArchiveMDB
Microsoft.Exchange.Data.Directory.Management.ReducedRecipientMailboxMoveTargetMDB
Microsoft.Exchange.Data.Directory.Recipient.ADPublicFolderDatabase
Microsoft.Exchange.Data.Directory.Recipient.ADPublicFolderHomeMTA
Microsoft.Exchange.Data.Directory.Management.FederatedOrganizationIdWithDomainStatusDelegationTrustLink
Microsoft.Exchange.Data.Directory.Management.MailboxDatabase
Microsoft.Exchange.Data.Directory.Management.MailboxPreviousDatabase
Microsoft.Exchange.Data.Directory.Management.MailboxDisabledArchiveDatabase
Microsoft.Exchange.Data.Directory.Management.MailboxMailboxMoveTargetMDB
Microsoft.Exchange.Data.Directory.Management.MailboxMailboxMoveSourceMDB
Microsoft.Exchange.Data.Directory.Management.MailboxMailboxMoveTargetArchiveMDB
Microsoft.Exchange.Data.Directory.Management.MailboxMailboxMoveSourceArchiveMDB
Microsoft.Exchange.Data.Directory.Management.MailboxPlanDatabase
Microsoft.Exchange.Data.Directory.Management.MailboxPlanPreviousDatabase
Microsoft.Exchange.Data.Directory.Management.MailboxPlanDisabledArchiveDatabase
Microsoft.Exchange.Data.Directory.Management.MailboxPlanMailboxMoveTargetMDB
Microsoft.Exchange.Data.Directory.Management.MailboxPlanMailboxMoveSourceMDB
Microsoft.Exchange.Data.Directory.Management.MailboxPlanMailboxMoveTargetArchiveMDB
Microsoft.Exchange.Data.Directory.Management.MailboxPlanMailboxMoveSourceArchiveMDB
Microsoft.Exchange.Data.Directory.Management.MailUserDisabledArchiveDatabase
2026-01-29MC Last Updated08/21/2025 16:27:322026-01-28T18:28:51Z
2026-01-29MC MessagesUpdated August 21, 2025: We have updated the timeline. Thank you for your patience.
We're updating the output format of certain properties returned by Exchange Online PowerShell cmdlets to improve performance and align with backend service optimizations. This change reduces unnecessary data retrieval and enhances consistency across services.
[When this will happen:]
Rollout will begin in October 2025 (previously August) and complete by November 2025.
Updated January 28, 2026: We have updated timelines for enforcement. The scope of the change remains unchanged. Thank you for your patience.
We're updating the output format of certain properties returned by Exchange Online PowerShell cmdlets to improve performance and align with backend service optimizations. This change reduces unnecessary data retrieval and enhances consistency across services.
[When this will happen:]
Rollout will begin in February 2026 (previously October 2025) and complete by April 2026 (previously November 2025).
2026-01-29MC SummaryExchange Online PowerShell cmdlets will update certain database property formats starting October 2025 to improve performance and consistency. The change affects only Exchange Online, not on-premises. No action is required, but review scripts parsing these values for compatibility.Exchange Online PowerShell cmdlets will update output formats for certain database-related properties starting February 2026, completing by April 2026. This change improves performance and consistency but only affects Exchange Online, not on-premises. No user action is required unless scripts parse these values.
2026-01-29MC End Time01/05/2026 08:00:002026-05-31T09:00:00Z
2026-01-29MC prepareNo action is required. There are no settings or controls to manage this change. If you have scripts that parse these property values, we recommend reviewing them to ensure compatibility.No action is required. There are no settings or controls to manage this change. If you have scripts that parse these property values, we recommend reviewing them to ensure compatibility.
The complete list of cmdlets impacted is as follows:
Cmdlet Output Type
Add-DistributionGroupMemberMicrosoft.Exchange.Data.Directory.Management.ReducedRecipient
Get-DistributionGroupMemberMicrosoft.Exchange.Data.Directory.Management.ReducedRecipient
Get-FederatedOrganizationIdentifier Microsoft.Exchange.Data.Directory.Management.FederatedOrganizationIdWithDomainStatus
Get-Mailbox Microsoft.Exchange.Data.Directory.Management.Mailbox
New-MailboxMicrosoft.Exchange.Data.Directory.Management.MailboxPlan
Get-MailboxPlanMicrosoft.Exchange.Data.Directory.Management.MailboxPlan
Get-MailUserMicrosoft.Exchange.Data.Directory.Management.MailUser
New-MailUser Microsoft.Exchange.Data.Directory.Management.MailUser
Get-RecipientMicrosoft.Exchange.Data.Directory.Management.ReducedRecipient
Add-RoleGroupMember Microsoft.Exchange.Data.Directory.Management.ReducedRecipient
Get-RoleGroupMember Microsoft.Exchange.Data.Directory.Management.ReducedRecipient
New-SyncMailPublicFolderMicrosoft.Exchange.Data.Directory.Recipient.ADPublicFolder

The affected properties for each Output Type are as follows:
Output TypeProperty
Microsoft.Exchange.Data.Directory.Recipient.ADPublicFolderDatabase
Microsoft.Exchange.Data.Directory.Recipient.ADPublicFolderHomeMTA
Microsoft.Exchange.Data.Directory.Management.FederatedOrganizationIdWithDomainStatusDelegationTrustLink
Microsoft.Exchange.Data.Directory.Management.MailboxDatabase
Microsoft.Exchange.Data.Directory.Management.MailboxPreviousDatabase
Microsoft.Exchange.Data.Directory.Management.MailboxDisabledArchiveDatabase
Microsoft.Exchange.Data.Directory.Management.MailboxMailboxMoveTargetMDB
Microsoft.Exchange.Data.Directory.Management.MailboxMailboxMoveSourceMDB
Microsoft.Exchange.Data.Directory.Management.MailboxMailboxMoveTargetArchiveMDB
Microsoft.Exchange.Data.Directory.Management.MailboxMailboxMoveSourceArchiveMDB
Microsoft.Exchange.Data.Directory.Management.MailboxPlanDatabase
Microsoft.Exchange.Data.Directory.Management.MailboxPlanPreviousDatabase
Microsoft.Exchange.Data.Directory.Management.MailboxPlanDisabledArchiveDatabase
Microsoft.Exchange.Data.Directory.Management.MailboxPlanMailboxMoveTargetMDB
Microsoft.Exchange.Data.Directory.Management.MailboxPlanMailboxMoveSourceMDB
Microsoft.Exchange.Data.Directory.Management.MailboxPlanMailboxMoveTargetArchiveMDB
Microsoft.Exchange.Data.Directory.Management.MailboxPlanMailboxMoveSourceArchiveMDB
Microsoft.Exchange.Data.Directory.Management.MailUserDisabledArchiveDatabase
2025-08-22MC MessageTagNamesFeature update, Admin impactUpdated message, Feature update, Admin impact
2025-08-22MC SummaryChanging output format for some database properties in Exchange Online cmdlets to improve performance and consistency. Rollout starts August 2025. The update affects string format of specific properties, but no action is required. Review scripts for compatibility if they parse these values. On-premises Exchange is not affected.Exchange Online PowerShell cmdlets will update certain database property formats starting October 2025 to improve performance and consistency. The change affects only Exchange Online, not on-premises. No action is required, but review scripts parsing these values for compatibility.
2025-08-22MC Last Updated07/04/2025 01:39:192025-08-21T16:27:32Z
2025-08-22MC MessagesWe're updating the output format of certain properties returned by Exchange Online PowerShell cmdlets to improve performance and align with backend service optimizations. This change reduces unnecessary data retrieval and enhances consistency across services.
[When this will happen:]
Rollout will begin in August 2025.
Updated August 21, 2025: We have updated the timeline. Thank you for your patience.
We're updating the output format of certain properties returned by Exchange Online PowerShell cmdlets to improve performance and align with backend service optimizations. This change reduces unnecessary data retrieval and enhances consistency across services.
[When this will happen:]
Rollout will begin in October 2025 (previously August) and complete by November 2025.
2025-08-22MC TitleChanging output format for some database properties in Exchange Online cmdlets(Updated) Changing output format for some database properties in Exchange Online cmdlets
2025-08-22MC End Time10/27/2025 08:00:002026-01-05T08:00:00Z

Last updated 2 weeks ago ago

Leave a Reply

Share to MS Teams

Login to your account

Welcome Back, We Missed You!