Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Microsoft regularly communicates work done to maintain and update Microsoft Power Platform (Power Apps, Power Automate, Microsoft Copilot Studio, and other services), and Microsoft Dynamics 365 apps (Sales, Customer Service, Supply Chain Management, and others) to ensure security, performance, availability, and to provide new features and functionality. Microsoft also communicates details of service incidents including the potential user experience, the start and end times of the incident, and any workaround that might be available.
For each of these scenarios, Microsoft provides communication through the Microsoft 365 admin center in the Message Center, and the Service health dashboard. The Microsoft 365 admin center also has the ability to send email for a weekly digest of all messages, emails for major updates only, and emails for data privacy messages. You can opt in to this communication stream by following the instructions in Preferences.
You can view service health information for Dynamics 365 and Power Platform products in the Power Platform admin center. Learn more in How do I check my online service health?
Microsoft might also send direct email to users assigned to the Power Platform administrator or Dynamics 365 administrator role in an impacted tenant. If you're not sure who your admin is, learn more in Find your administrator or support person. To assign a service admin role to a user, follow the instructions in Assign a service admin role to a user.
Scheduled system updates and maintenance
Microsoft regularly performs updates and maintenance on the service and apps through a weekly update process. This update process delivers security and minor service improvements on a weekly basis, with each update rolling out region-by-region according to a safe deployment schedule, arranged in Stations. You can find more information about the schedule of Station deployments on the Released Versions of Dataverse page.
New features and capabilities are continually released for preview and general availability. For details on upcoming features and release timelines, refer to the Microsoft Copilot Roadmap.
There are also two major service update events in April (Wave 1) and October (Wave 2) that are delivered through the weekly update mechanism, and details can be found in the Dynamics 365 and Microsoft Power Platform release plans.
Minor service updates
Minor service updates contain customization changes to support new features, product improvements, and bug fixes. Microsoft deploys them on a weekly basis, region by region, according to a Safe Deployment Process. Each week, every region gets:
- An updated deployment, starting with the First Release region
- A Message Center notification with the date that the deployment begins to be applied to the infrastructure
- A link to the weekly release notes that contain the list of fixes that are included
Note
The date the deployment is applied to the infrastructure isn't the date the update is applied to the environment. An asynchronous process updates the environment and any apps during subsequent regional maintenance windows. Although there's no expected degradation to service performance or availability, during this maintenance window users might see short, intermittent impact such as transient SQL errors or a redirect to the sign-in screen.
You can verify that the update completed successfully by checking the version number on the About page of the environment or looking at the environment details on the Power Platform admin center. You can find a list of service updates on the Released Versions page.
Major release events
Microsoft continuously rolls out new capabilities and functionality. These updates are backward compatible, so your apps and customizations continue to work after the update. New features with major, disruptive changes to the user experience are off by default, which means administrators can first test, then use these features for their organization. Administrators can use an "Opt-in" feature to get early access to the changes.
The Microsoft 365 admin portal's Message Center publishes notifications for major feature releases. You can also refer to the Microsoft Copilot Roadmap for upcoming features and release timelines, filtered for Power Platform and Dynamics 365 services.
Security updates
The service teams regularly perform the following tasks to ensure the security of the system:
- Scan the service to identify possible security vulnerabilities.
- Assess the service to ensure that key security controls are operating effectively.
- Evaluate the service to determine exposure to any vulnerabilities identified by the Microsoft Security Response Center (MSRC), which regularly monitors external vulnerability awareness sites.
These teams also identify and track any issues and take swift action to mitigate risks when necessary.
How do I find out about security updates?
Because the service teams strive to apply risk mitigations in a way that doesn't require service downtime, administrators usually don't see Message Center notifications for security updates. If a security update does require service impact, it's considered planned maintenance. The update includes the estimated impact duration and the window when the work occurs.
For more information about security, go to the Trust Center.
Planned maintenance
Planned maintenance includes updates and changes to the service to provide increased stability, reliability, and performance.
These changes can include:
- Hardware or infrastructure updates.
- Integrated services, such as a new version of Microsoft 365 or Azure.
- Service changes and software updates.
- Minor service updates that occur several times per year. Learn more in Service updates.
Unplanned maintenance
Power Platform services and Dynamics 365 apps (Sales, Customer Service, Supply Chain Management, and others) can encounter issues that require unplanned changes to protect availability. Microsoft strives to provide as much notification as possible during these events, but because they can't be predicted, they're not considered planned maintenance.
When this type of maintenance occurs, your organization receives an Unplanned Maintenance notification in the Message Center. Microsoft also attempts to send an email to all System Administrators in the environment that is affected by the unplanned maintenance. You can see the status of current unplanned maintenance activities in the Message Center.
Regional maintenance windows
To limit the impact on customers and their users, Microsoft plans the maintenance window according to the region where the environments are deployed. The following maintenance timeline list shows the maintenance window for each region. The times are shown in Coordinated Universal Time (UTC, which is also known as Greenwich Mean Time). For organizations with users around the globe, Microsoft recognizes that these maintenance windows might affect you differently. Microsoft apologizes for the impact this issue might have on your users.
Maintenance timeline
To limit the impact on users, plan the maintenance window according to the region where environments are deployed. The following list shows the maintenance window for each region. The times are shown in Coordinated Universal Time (UTC, which is also known as Greenwich Mean Time).
The following times are service update times. Database updates run as soon as possible depending on the system load during the maintenance window of the environment. In addition to the listed update windows, database updates also run 24 hours on weekends (Saturdays and Sundays). Customizing your environment's maintenance window to expand the hours or stagger it from the default window for the region, can significantly improve the speed at which database updates are applied to your organization.
| Region | URL | Window (UTC) |
|---|---|---|
| NAM | crm.dynamics.com | 2 AM to 11 AM |
| DEU | crm.microsoftdynamics.de | 5 PM to 2 AM |
| SAM | crm2.dynamics.com | 12 AM to 10 AM |
| CAN | crm3.dynamics.com | 1 AM to 10 AM |
| EUR | crm4.dynamics.com | 6 PM to 3 AM |
| FRA | crm12.dynamics.com | 6 PM to 3 AM |
| APJ | crm5.dynamics.com | 3 PM to 8 PM |
| OCE | crm6.dynamics.com | 11AM to 9PM |
| JPN | crm7.dynamics.com | 10 AM to 7 PM |
| IND | crm8.dynamics.com | 7:30PM to 1AM |
| GCC | crm9.dynamics.com | 2 AM to 11 AM |
| GCC High | crm.microsoftdynamics.us | 2 AM to 11 AM |
| GBR | crm11.dynamics.com | 6 PM to 3 AM |
| ZAF | crm14.dynamics.com | 5 PM to 2 AM |
| UAE | crm15.dynamics.com | 3 PM to 12 AM |
| GER | crm16.dynamics.com | 6 PM TO 3 AM |
| CHE | crm17.dynamics.com | 6 PM to 3 AM |
| CHN | crm.dynamics.cn | 3 PM to 9 PM |
Service incidents
A service incident is an event, or series of events, that typically causes multiple customers to have a degraded experience with one or more services. These incidents are platform issues that cause unplanned downtime—including unavailability, performance degradation, and problems that interfere with service management. We communicate service incidents through an authenticated experience on the Microsoft 365 admin portal Service health dashboard to provide visibility of service health to administrators across multiple cloud services. Examples of service incidents include:
- Unable to sign in to a specific environment or admin portal
- Slow performance in apps or Dataverse queries
- Error messages or unexpected blank pages
How do I find out about service incidents?
Check the Service health dashboard to view the status of the service, details about existing service incidents, and up to 30 days of history. The Power Platform admin center offers a view of service health information in the Support page. Service health knows which tenants you manage, so it shows a much more accurate view of any known issues impacting your services than nonauthenticated sources of information. If you're experiencing an issue that's not displayed in the Service health dashboard, contact Microsoft support by creating a ticket in the Power Platform admin center.
If there's a broad customer impact during a service incident, we might also provide status updates on one of several service-specific support pages, including the Power Apps support page, Power Automate support page, or the Power BI support page.
If the Power Platform or Microsoft 365 admin portal is unavailable or experiencing issues, we provide status updates through the unauthenticated Service Health Status page.
What information is provided about service incidents?
During the event, we include information that's related to the user impact, duration, any feasible workaround, and preliminary root cause. Our goal is to provide status updates on an hourly cadence, although this guideline might be reduced for substantive new information or extended based on waiting on recovery activities. When the service is restored to optimal operation, we publish a final status update and determine if other post-incident reports are provided based on the breadth and type of impact to customers.
A post-incident report (PIR) might be published after five business days on the Microsoft 365 Service health dashboard for certain events.
This report summarizes the following details:
- Summary
- User Experience
- Timeline of major activities or actions
- Contributing Factors
- Next steps
Other methods of receiving notifications
Because of the critical nature of service notifications and communications, there are other methods of connecting to Service Communications.
- Sign up for email notifications for new incidents that affect your tenant and status changes for an active incident.
- Download and install the Microsoft 365 Admin mobile app on your mobile device to view service updates and incident notifications.
- Connect directly to our service communications using an externally accessible Service Communication API.
- Track your message center tasks in Planner.