Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Update to MC1510951: Canada 2026 time zone changes — Microsoft 365 impact and required admin actions

Returned by 2 reference tenants · Corroborated by Microsoft 365 Message Center Archive by Merill Fernando
Microsoft 365 suite

Microsoft category: Prevent or fix issues. Read the notice and linked documentation for any recommendations or required actions; whether your tenant is affected is not known here.

What the notice says

Microsoft’s text, safely structured

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

  1. Outlook and Exchange Online (calendar): Users must move to the new time zone. Existing events do not migrate automatically. Recurring meetings require additional review.
  2. Microsoft Teams Rooms on Windows: Some devices may display time one hour behind Windows until Edge/WebView2 is updated.

Potential impact (under validation)

  1. Microsoft Teams (desktop, web, mobile) and other Teams devices
  2. Outlook for iOS, Android, and Mac
  3. Microsoft Bookings
  4. Shifts
  5. SharePoint Online
  6. OneDrive

What you need to do

  1. Ensure Windows devices in affected regions have the latest Windows updates (including October 2026 updates).
  2. Ask users in affected regions to select the new time zone in Outlook and review meetings scheduled after November 1, especially recurring series.
  3. Plan to run the Exchange Online PowerShell remediation cmdlet for non-recurring meetings once released (target: October 28, 2026).
  4. Update Microsoft Edge and WebView2 on Teams Rooms on Windows and confirm room time display matches Windows.
  5. Keep Teams, Outlook (including iOS/Android/Mac), and other Microsoft 365 apps current.
  6. Test key scenarios before November 1: recurring meetings, free/busy, Bookings appointments, Shifts schedules, and SharePoint regional settings.
  7. If issues occur, open a support case in the Microsoft 365 admin center and include #Canada Time-Zone in the title.

We will continue updating this post as product teams confirm impact, publish mitigations, and release additional guidance.

What changed

Between the versions we saw, newest first

This installation has seen one version of this notice, first on 26 Oct 2026. Later changes will show here.

These are the archive's capture times. They are separate from the versions returned by our reference tenants.

Read the archive's current copy

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

  1. Outlook and Exchange Online (calendar): Users must move to the new time zone. Existing events do not migrate automatically. Recurring meetings require additional review.
  2. Microsoft Teams Rooms on Windows: Some devices may display time one hour behind Windows until Edge/WebView2 is updated.

Potential impact (under validation)

  1. Microsoft Teams (desktop, web, mobile) and other Teams devices
  2. Outlook for iOS, Android, and Mac
  3. Microsoft Bookings
  4. Shifts
  5. SharePoint Online
  6. OneDrive

What you need to do

  1. Ensure Windows devices in affected regions have the latest Windows updates (including October 2026 updates).
  2. Ask users in affected regions to select the new time zone in Outlook and review meetings scheduled after November 1, especially recurring series.
  3. Plan to run the Exchange Online PowerShell remediation cmdlet for non-recurring meetings once released (target: October 28, 2026).
  4. Update Microsoft Edge and WebView2 on Teams Rooms on Windows and confirm room time display matches Windows.
  5. Keep Teams, Outlook (including iOS/Android/Mac), and other Microsoft 365 apps current.
  6. Test key scenarios before November 1: recurring meetings, free/busy, Bookings appointments, Shifts schedules, and SharePoint regional settings.
  7. If issues occur, open a support case in the Microsoft 365 admin center and include #Canada Time-Zone in the title.

We will continue updating this post as product teams confirm impact, publish mitigations, and release additional guidance.

  1. Update to MC1510951: Canada 2026 time zone changes — Microsoft 365 impact and required admin actions Action date: 1 Nov 2026

Learn more

Links from the notice and their documentation checks

This site links to Microsoft's pages instead of copying them. Installations inside an organization can keep a copy for comparison.

Other posts named in this one

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
  • Some history or links were left out of the website export to keep it within its size limits.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 08:58 UTC · 274 of 275 readable · 252 fully read · 18 waiting for GitHub's hourly limit · documentation 469/469 current