MC716665Microsoft Exchange admin center: new troubleshooting option

Updated August 1, 2024: The troubleshooting workflows, originally planned to be fully deployed by the end of June, were delayed due to the Exchange Admin Center security review, during which any new features were paused until the review was completed. With the security review now completed, the troubleshooting workflows will begin deploying starting the first week of August 2024.

The Microsoft Exchange admin center (EAC) is launching new troubleshooting workflows to help customers resolve common issues more efficiently.

When this will happen:

Standard Release: We will begin rolling out mid-February 2024 and expect to complete by late June 2024.

How will this affect your organization:

Admins will be able to access the new Troubleshoot option on the left navigation of the Microsoft Exchange admin center. When common issues arise, admins can run the Quick fixes workflow or Collect logs workflow to investigate. These workflows gather logs and data to provide relevant information, making troubleshooting easier. All logs and data are stored on the admin’s local machine for easy access.

The Quick fixes option includes workflows to resolve known issues. Each workflow provides detailed information about the actions it performs and the specific issue it addresses. In this initial release, admins will be able to quickly reset Outlook on the web (OWA) settings for users, helping to resolve various login and calendar-related issues.

The Collect logs workflows can be used to diagnose issues with resource mailboxes functioning in unexpected ways or meetings updating incorrectly for a mailbox. Each workflow executes multiple cmdlets and provides aggregated information, which is then downloaded to the admin’s local machine as logs. These logs can be used to diagnose issues independently or provide additional information before contacting Support.

What you need to do to prepare:

No action is needed to prepare for this change. You may want to notify your users about this change and update any relevant documentation as appropriate.