Original publish date: October 26, 2026
Last updated: October 30, 2026
KB ID: 5134344
Executive summary
On November 1, 2026, affected locations in British Columbia, Alberta, and Manitoba will not turn their clocks back. They will remain on UTC−07:00, UTC−06:00 and UTC−05:00 respectively. Affected locations in the Northwest Territories (including Yellowknife and Inuvik) align with the Alberta change, and Northwestern Ontario aligns with the Manitoba change.
Product teams are actively confirming impact, mitigations and timelines across Microsoft products. This post reflects what is known as of the date above and will be updated as additional impacts, fixes or confirmations are identified. We recommend you review this post regularly and complete the actions below before November 1, 2026.
At a glance
| Status | Microsoft products |
|---|---|
| Confirmed impact | Outlook and Exchange Online (calendar); Microsoft Teams Rooms on Windows; Teams Auto Attendant; SharePoint On-Prem; Power Automate Desktop + Cloud Flows; Fabric; Microsoft Bookings; Dynamics 365 Finance and Operations |
| Potential impact (under validation) | Microsoft Teams (desktop, web, mobile) and other Teams devices; Outlook for iOS, Android, and Mac; Power Pages |
| No impact expected | Dynamics 365 Sales; Dynamics 365 Customer Insights; Dynamics 365 Customer Service; Dynamics 365 Contact Center; Dynamics 365 Business Central; Dynamics 365 Field Service; Dynamics 365 Commerce; Dynamics 365 Project Operations; Power Apps (Canvas Apps); Power Automate Process Mining; SharePoint Online; Teams Graph; Power Apps – Model Driven Apps |
Recommended actions for admins
Make sure Windows devices used to access Microsoft 365 in affected regions have the latest Windows updates installed. Devices on unsupported Windows versions will not receive the time zone update.
Ask users in affected regions to select the new time zone in Outlook, and review existing meetings, especially recurring series, scheduled after November 1, 2026.
Plan to use the Exchange Online PowerShell cmdlet to remediate non-recurring meetings once it is released (target October 28, 2026).
Update Microsoft Edge and WebView2 on Microsoft Teams Rooms on Windows devices, then confirm the displayed time matches Windows.
Keep Teams, Outlook (including iOS, Android, and Mac) and other Microsoft 365 apps up to date.
Test key scenarios with a pilot group before November 1, 2026: meetings and recurring series, free/busy, Bookings appointments, Shifts schedules, and SharePoint regional settings.
If you see unexpected behavior, open a support case in the Microsoft 365 admin center and include "#CanadaTimeZone" in the case title.
Confirmed impact
| Product | Impact | Mitigation and guidance | Status |
|---|---|---|---|
| Outlook and Exchange Online | Users must move to the new time zone. Existing calendar events do not migrate automatically, and recurring meetings need additional review. Free/busy and Work Hours and Location in Outlook on the web and new Outlook are under investigation. | Follow the Outlook support article for BC, Alberta and Manitoba. An Exchange Online PowerShell cmdlet to remediate non-recurring meetings planned for November 4, 2026 is planned. Recurring meeting remediation is in development. | Cmdlet releasing by November 4, 2026; recurring meetings ETA to be confirmed |
| Teams Rooms on Windows | Affected devices displayed time one hour behind Windows. | Update Microsoft Edge/WebView2 and verify the room display time. | Mitigation available |
| Teams Auto Attendant | Correct time zones may not be available on November 1, 2026. | Manually update the timezones via the posted guidance. | Workaround available |
| SharePoint On-Prem | Correct time zones may not be available on November 1, 2026 | Update to be made available on November 10, 2026 | Update to be made available on November 10, 2026 |
| Power Automate Desktop + Cloud Flows | From November 1, 2026, a 1-hour drift will be observed when using US-linked zones (Mountain/Pacific/Central). | Until support for the new province IDs is available, use temporary mappings:
|
Workaround available |
| Dynamics 365 Finance and Operations apps (Finance, Human Resources, Supply Chain Management) | Affected users may see incorrect local times after November 1, 2026 unless hotfixes are installed and the appropriate new regional time zone is selected | Apply applicable hotfix when available; affected users must then select the appropriate new region-specific time zone. | Customer-installable hotfixes targeted for October 31, 2026, through LCS and Power Platform admin center. |
| Fabric | The new time zones are not yet available in Fabric/Power BI Service | Update to be made available. Until then, customers should use the corresponding temporary time-zone choice:
|
ETA to be confirmed |
| Microsoft Bookings | An error message may appear even when your booking has been successfully created. Your booking details and calendar invitation should still arrive by email as usual. | The fix is progressively rolling out, and the issue should resolve automatically once it reaches your environment. | Updates complete deployment on November 4, 2026. |
| Power Pages | Server-formatted dates can appear one hour off for affected Canadian and neighboring US zones, including Liquid output, relative-date filters, and Excel exports | Apply the service fix once available | A service fix is in progress with a Dec 12 milestone. |
Potential impact (under validation)
Product teams are validating the following Microsoft products. Until confirmation is published here, test the listed scenarios in your environment and keep devices and apps up to date.
| Product | What is being validated | Interim guidance |
|---|---|---|
| Microsoft Teams (desktop, web, mobile) | Meeting scheduling, time zone labels and notifications across clients. | Keep clients current. Validate meetings scheduled after November 1, 2026. |
| Other Teams devices | Device time display and scheduling on Teams devices other than Teams Rooms on Windows. | Keep device software current and check displayed time after updates. |
| Outlook for iOS, Android and Mac | Handling of the new time zones on mobile and Mac clients. | Keep clients updated. Follow the Outlook guidance above. |
Impact mitigated
Product teams have mitigated impact for the following Microsoft products (software updates may be required).
| Product | Mitigation Plan |
|---|---|
| Dynamics 365 Sales | Configuration update is being deployed through the regular release train and is scheduled to reach the Canada region by October 31, 2026. |
| Dynamics 365 Customer Insights | Configuration update is being deployed through the regular release train and is scheduled to reach the Canada region by October 31, 2026. |
| Dynamics 365 Customer Service | Configuration update is being deployed through the regular release train and is scheduled to reach the Canada region by October 31, 2026. |
| Dynamics 365 Contact Center | Configuration update is being deployed through the regular release train and is scheduled to reach the Canada region by October 31, 2026. |
| Dynamics 365 Business Central | Configuration updates online starting October 31, 2026, and is expected to complete by October 29, 2026. The new time zones will be available to all users in Canada by October 29, 2026. The update covers all supported online versions. Customers do not need to install an update or change their deployments. Affected users will need to select the appropriate new region-specific time zone. |
| Dynamics 365 Field Service | Field Service app update is currently available; Mobile app fixes remain in progress, with published workarounds available. |
| Dynamics 365 Project Operations | Updates and rollouts are in progress and will be completed by November 1, 2026. |
| Dynamics 365 Commerce | Updates and rollouts are in progress and will be completed by November 1, 2026. |
| SharePoint Online | Configuration update is being deployed through the regular release train and is scheduled to reach the Canada region by October 29, 2026. |
| Power Apps (Canvas Apps) | No impact anticipated |
| Power Automate Process Mining | No impact anticipated |
| Power Apps (Model-driven Apps) | No impact anticipated |
| Teams Graph | No impact anticipated |
| Azure Products | No significant impact anticipated |
Getting help
If you experience issues or need help assessing your environment, open a support case in the Microsoft admin center and include "#CanadaTimeZone" in the case title. This helps Microsoft identify trends and route your case quickly.
Additional resources
Outlook Time Zone Changes for British Columbia, Alberta, and Manitoba
Interim guidance for British Columbia time zone changes 2026
Canadian time zone changes for Fabric schedules - Microsoft Fabric | Microsoft Learn
We will update this post as product teams confirm impact, release fixes, or publish new guidance.
Change log
| Change date | Change description |
|---|---|
| October 30, 2026 |
|
| October 29, 2026 |
|
| October 28, 2026 |
|
| October 27, 2026 |
|