Service Update
| Availability | September 5th - 8th, 2023 |
| Product(s) | Email Security Cloud Gateway (CG) |
| Who's affected | Azure Directory Synchronization customers |
Overview
As part of Mimecast's ongoing effort to improve the performance and security of our services, we would like to inform you of a change for Azure Active Directory Synchronization Integrations. Due to the high volume of API activity against the Microsoft Graph API during the automated Azure Directory synchronization time window, Microsoft has begun to throttle Mimecast connections. Unfortunately, using the Microsoft-recommended retry schedule did not resolve this issue. Mimecast will therefore update the schedule for automated Azure Directory synchronizations so that the number of connections to the Microsoft Graph API can be redistributed.
What's changing
Azure Directory Synchronizations were previously initiated automatically at 8 a.m., 1 p.m., and 11 p.m. daily, based on the time zone the Mimecast account is hosted in. Instead of previous initiation times, such automated synchronizations will now be initiated within a time window. The window is still based on the time zone the Mimecast account is hosted in and is now:
- Between 8 a.m. and 11 a.m.
- Between 1 p.m. and 4 p.m.
- Between 12 a.m. and 3 a.m.
If the number of users of your account is below 500 seats, it’s highly likely that your automated synchronizations will be initiated towards the end of the new time windows.
Administrators can still initiate synchronizations at any time. When initiated near the beginning of the time window used by automated synchronizations, requests against the Microsoft Graph API are more likely to be throttled.
Recommended actions
Customers should review our Knowledge Hub, accessible through Mimecaster Central.
Comments
Please sign in to leave a comment.