MC1526468 - Update to MC1510951: Canada 2026 time zone changes — Microsoft 365 impact and required admin actions
Microsoft 365 Message Center announcement MC1526468.
MS Message Center's Summary
Certain Canadian regions will not change clocks on November 1 2026 which impacts Microsoft 365 scheduling and calendar accuracy. Administrators must apply the latest Windows updates ensure client applications are current and instruct users in affected regions to manually update their time zone settings and review recurring meetings. Planning for PowerShell remediation and testing key scheduling scenarios before the effective date are strongly recommended.
- Administrator impact
- Administrators must update operating systems review calendar settings and apply remediation scripts for affected users.
- End user impact
- Users in affected regions must manually update their time zone and check meetings for scheduling errors.
- Importance
- 9/10: This change causes widespread calendar disruption and meeting misalignments across multiple Canadian regions requiring urgent administrative preparation before November 1 2026.
Outlook Time Zone Changes for British Columbia Alberta and Manitoba
Interim guidance for British Columbia time zone changes 2026
Microsoft Summary
On November 1, 2026, certain Canadian regions will not change clocks, affecting Microsoft 365 scheduling. Admins must update Windows, Outlook time zones, review meetings, update Teams Rooms, and keep apps current. Testing and support case submission with #Canada Time-Zone are advised.
- Message Center ID
- MC1526468
- Category
- prevent Or Fix Issue
- Severity
- high
- Services
- Microsoft 365 suite
- Tags
- Updated message, User impact, Admin impact
- Published
- 2026-10-26
- Last updated
- 2026-10-26
- Expires
- 2027-01-31
- Action required by
- 2026-11-01
This post updates MC1510951 ((Updated) Windows updates are available for 2026 time zone changes in Canada, posted October 16, 2026). On November 1, 2026, affected locations in British Columbia, Alberta, and Manitoba will not move clocks back and 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. Windows and Microsoft 365 services depend on updated time zone definitions for correct scheduling and display behavior. How this affects your organization Confirmed impact Outlook and Exchange Online (calendar): Users must move to the new time zone. Existing events do not migrate automatically. Recurring meetings require additional review. Microsoft Teams Rooms on Windows: Some devices may display time one hour behind Windows until Edge/WebView2 is updated. Potential impact (under validation) Microsoft Teams (desktop, web, mobile) and other Teams devices Outlook for iOS, Android, and Mac Microsoft Bookings Shifts SharePoint Online OneDrive What you need to do Ensure Windows devices in affected regions have the latest Windows updates (including October 2026 updates). Ask users in affected regions to select the new time zone in Outlook and review meetings scheduled after November 1, especially recurring series. Plan to run the Exchange Online PowerShell remediation cmdlet for non-recurring meetings once released (target: October 28, 2026). Update Microsoft Edge and WebView2 on Teams Rooms on Windows and confirm room time display matches Windows. Keep Teams, Outlook (including iOS/Android/Mac), and other Microsoft 365 apps current. Test key scenarios before November 1: recurring meetings, free/busy, Bookings appointments, Shifts schedules, and SharePoint regional settings. If issues occur, open a support case in the Microsoft 365 admin center and include #Canada Time-Zone in the title. Additional information Outlook Time Zone Changes for British Columbia, Alberta, and Manitoba (Microsoft Support) Interim guidance for British Columbia time zone changes 2026 (DST Blog) Interim guidance for Alberta time zone changes 2026 (DST Blog) Manitoba 2026 time zone update available now (Daylight Saving Time and Time Zone Blog) We will continue updating this post as product teams confirm impact, publish mitigations, and release additional guidance.