Exchange Online Remote PowerShell Throttling Limits and Bulk Command Errors
Question details
An administrator wants to understand Exchange Online PowerShell throttling and reduce errors during bulk commands.

- Product
- Exchange Online PowerShell
- Device & OS
- not provided
- Scenario
- Running bulk Set and New operations against Exchange Online.
- Observed behavior
- Bulk commands trigger throttling errors, and the administrator needs to know which limits apply.
Record the exact throttling error, affected cmdlets, and approximate number of concurrent operations. Check which Exchange Online PowerShell module and connection method your script uses.
Reduce Exchange Online PowerShell throttling during bulk operations
Use smaller batches and controlled retries when bulk Set or New commands encounter throttling.
Exchange Online applies service-side limits to protect shared resources. Throttling can depend on factors such as concurrent requests, command type, and service conditions; tenant-specific policy details are not available through the on-premises Get-ThrottlingPolicy cmdlet.
Historical Remote PowerShell figures included concurrency limits of 3 per user and 9 per tenant, a queue depth of 50, and cmdlet limits of 200 for PowerShell and 25 for Exchange. These are reported legacy values, not guaranteed current limits or a formula for calculating your tenant's budget. Destructive operations also had separate limits.
Run Get-Module -ListAvailable ExchangeOnlineManagement in PowerShell to check the installed module. Use the current Exchange Online PowerShell module and Connect-ExchangeOnline; the legacy Remote PowerShell connection method has been retired.
Review your script's parallel jobs and runspaces, and reduce the number of simultaneous commands. Split the input list into smaller batches instead of submitting every Set or New operation at once.
Add a pause between batches, for example with Start-Sleep, and retry throttled requests with increasing delays. If the response provides a retry interval, wait at least that long before retrying.
Review the error output and query the target objects before rerunning failed operations. In particular, verify whether a New command already created an object so a retry does not create a duplicate.
If throttling continues at a low request rate, open Help & support in the Microsoft 365 admin center and provide the error details, affected cmdlets, and timestamps.

Track bulk operation results in WPS Spreadsheets
WPS Office is a free, lightweight, easy-to-use Office alternative with a familiar interface and compatibility with Microsoft Office formats for a smooth transition. Use WPS Spreadsheets to review exported bulk-operation results; it does not change Exchange Online throttling.

Frequently Asked Questions
Can I use Get-ThrottlingPolicy to see my Exchange Online limits?
No. Get-ThrottlingPolicy applies to on-premises Exchange Server and does not expose the tenant's Exchange Online throttling policy.
Are the old Remote PowerShell limits still guaranteed?
No. Reported values such as three concurrent connections per user are historical Remote PowerShell figures, not guaranteed limits for current Exchange Online PowerShell connections.
How can I reduce throttling in a bulk PowerShell script?
Reduce parallel jobs, process smaller batches, and add delays with Start-Sleep. Retry throttled requests with increasing delays, and honor any retry interval returned by the service.
Should I retry every failed New command immediately?
No. Check whether the target object was created before retrying, and wait for any service-provided retry interval. This helps avoid duplicate objects and further throttling.
Where can I get help if throttling continues?
Open Help & support in the Microsoft 365 admin center. Include the exact errors, timestamps, affected cmdlets, and your approximate concurrency.




