Fix eDiscovery PowerShell Cmdlets Missing with App-Only Authentication
Question details
Users are unable to access or execute specific eDiscovery PowerShell commands (such as Add-eDiscoveryCaseAdmin) when connecting to Microsoft Purview via a multitenant Azure application using client-credential authentication.
- Product
- Microsoft Purview / Exchange Online PowerShell
- Device & OS
- not provided
- Scenario
- A user is attempting to manage eDiscovery cases automatically via PowerShell scripts relying on app-only authentication.
- Observed behavior
- The connection is successful, but the required eDiscovery cmdlets are missing or unrecognized in the PowerShell session.
Ensure you have Global Administrator or Security Administrator privileges in your Microsoft 365 tenant to verify Azure Active Directory application permissions and update Exchange roles.
Verify Application Permissions and Update the PowerShell Module
Confirm that your Azure app holds the correct API permissions and update your ExchangeOnlineManagement module to correctly load the cmdlets.
When using app-only authentication, PowerShell cmdlets are only loaded if the connected service principal possesses the exact required roles and permissions. Missing application permissions will prevent eDiscovery cmdlets from appearing in the session.
Go to the Azure portal and check your multitenant application's API permissions. Ensure that it has the required eDiscovery operations allowed, specifically looking for the 'eDiscovery.Manage' application permission and required Exchange/Purview roles.
Open PowerShell as an Administrator and execute the command 'Update-Module -Name ExchangeOnlineManagement' to ensure you are running the latest version.
Close your current PowerShell window entirely. Open a new session and reconnect to apply the updated permissions cache to your environment.
Manage Compliance Reports and Logs with WPS Office
While resolving complex Microsoft PowerShell configuration issues, you can rely on WPS Office as a free, lightweight, and easy-to-use alternative for handling your exported eDiscovery CSV logs, compliance reports, and case documentation with seamless format compatibility.
- 1. Download WPS Office: Visit the official WPS website to download and install the free office suite on your device.
- 2. Analyze CSV Logs: Open WPS Spreadsheet to seamlessly review and filter large CSV export logs generated by eDiscovery.
- 3. Document Findings: Use WPS Writer to draft your compliance summaries and save them in DOCX format for easy sharing.
Frequently Asked Questions
Why are some Exchange Online cmdlets missing when using app-only authentication?
App-only authentication strictly relies on the exact permissions granted to the application's service principal. If a specific RBAC role or an API permission (such as eDiscovery.Manage) is absent, the backend refuses to load the corresponding cmdlets in your session.
How do I refresh my PowerShell session after assigning new permissions?
You must completely disconnect the current session by closing the PowerShell window. Open a new PowerShell instance and reconnect using Connect-ExchangeOnline to ensure the newly assigned roles are pulled into the local session cache.
Which module contains the eDiscovery cmdlets?
The Security and Compliance PowerShell cmdlets, including eDiscovery commands, are bundled with the ExchangeOnlineManagement module. Ensure it is fully updated by running Update-Module -Name ExchangeOnlineManagement.
