Services
Affected Platforms
Summary
A systems update for the Export-ContentExplorerData PowerShell cmdlet is scheduled for February 1-2, 2025, potentially causing script failures. Avoid running scripts during this time and resume after February 3. The new cmdlet will allow exporting all scanned content data, rolling out from July to September 2025. No extra settings are needed.
Details
Updated August 28, 2025: We have updated the timeline. Thank you for your patience.
What is happening: We have a systems update scheduled between (1 Feb - 2 Feb, 2025). This update is for Export-ContentExplorerData PowerShell Cmdlet
How it impacts you: During the update, any Cmdlet-based scripts running at that time might experience failures for some of the Cmdlet calls. To avoid any disruptions, we recommend running your scripts after 3 Feb 2025, when the updates will be fully in place and operational.
Which Cmdlets were impacted: 1. Export-ContentExplorerData
What do you need to do?
Ć¢ā¬Ā¢ Avoid running Cmdlet-based scripts during the (1 Feb - 2 Feb 2025) update.
Ć¢ā¬Ā¢ Resume running your scripts on 3 Feb 2025 to ensure smooth operation.
We apologize for any inconvenience this may cause and appreciate your understanding and cooperation. If you have any questions or need further assistance, please do not hesitate to reach out to our support team.
The current Content Explorer Export feature has a limitation of exporting data only after drilling down to specific location. The new feature coming to General Availability will allow admins to use a new cmdlet within the Security and Compliance PowerShell, Export-ContentExplorerData, to export all rows of data for the content that are scanned and shown on Content Explorer.
This message is associated with Microsoft 365 Roadmap ID 117546
When this will happen:
Rollout will begin late July 2025 (previously late April) and is expected to be complete by early September (previously mid-August 2025).
How this will affect your organization:
This feature can be accessed through the Security and Compliance PowerShell, Export-ContentExplorerData.
What you need to do to prepare:
There are no additional settings needed for this feature. You may want to notify your users about this change and update any relevant documentation as appropriate.