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

Product:

Exchange

Platform:

Online, World tenant

Status:

Change type:

Admin impact, Feature update, Updated message

Links:

Details:

Summary:
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.

Details:
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.

Change Category:
XXXXXXX ... free basic plan only

Scope:
XXXXXXX ... free basic plan only

Release Phase:

Created:
2025-07-04

updated:
2025-08-22

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**

XXXXXXX ... free basic plan only

Direct effects for Operations**

Change in output format of database properties
Scripts that parse the output of Exchange Online PowerShell cmdlets may fail or produce errors if not updated to accommodate the new format, leading to potential disruptions in automated processes.
   - roles: IT Administrators, DevOps Engineers
   - references: https://techcommunity.microsoft.com/t5/exchange-team-blog/changing-output-format-for-some-database-properties-in/ba-p/3651230

Increased risk of operational inefficiencies
If scripts are not reviewed and updated, it may lead to increased time spent troubleshooting issues caused by the format change, impacting overall IT operations efficiency.
   - roles: IT Support Staff, System Administrators
   - references: https://techcommunity.microsoft.com/t5/exchange-team-blog/changing-output-format-for-some-database-properties-in/ba-p/3651230

Configutation Options**

XXXXXXX ... paid membership only

explanation for non-techies**

Exchange Online is making a change to the way certain database properties are displayed when using PowerShell cmdlets. Think of it like updating the address format on a letter. Previously, the address might have been simple, like "123 Main St," but now it's more detailed, like "123 Main St, Suite 456, Springfield, IL 62704." This change is meant to make things more efficient and consistent, similar to how a more detailed address helps ensure mail gets delivered correctly.

This update is scheduled to start in October 2025 and finish by November 2025. It's important to note that this change only affects Exchange Online, not any on-premises systems. The new format will provide more detailed information, which helps with backend service optimizations. However, it's mainly for informational purposes and doesn't require any changes to how you manage or automate tasks.

For those who use scripts to pull these property values, it's a good idea to check them to make sure they still work with the new format. It's like making sure your GPS can still find the new address format. There's no need to worry about adjusting any settings or processes, as the change is designed to be seamless.