GoKawiilMicrosoft software still misreads clocks after Canada ends time changes
Several Canadian regions, including parts of British Columbia, Alberta and Manitoba, stopped observing daylight saving changes on November 1, locking into fixed UTC offsets. Microsoft has confirmed that Outlook, Power Automate, Fabric and SharePoint On-Prem have not fully adapted, producing incorrect meeting times and requiring manual fixes from users and administrators.
GoKawiil's interpretation of the reporting above, not reported fact.
The episode shows how deeply time zone assumptions are baked into enterprise software, so a regional policy change can ripple into scheduling chaos for businesses relying on Microsoft 365. Recommended workarounds, such as having Power Automate and Fabric treat affected users as being in Saskatchewan, Arizona or Bogota, suggest Microsoft is patching the problem with approximations rather than a clean fix while permanent updates remain in development.
- Parts of British Columbia, Alberta and Manitoba ended seasonal clock changes on November 1, staying fixed on UTC-07:00, UTC-06:00 and UTC-05:00.
- Outlook calendar entries after that date may be an hour off, and only meeting organizers can correct them, with recurring meetings requiring manual recreation.
- Microsoft is developing PowerShell fixes and other patches, with some corrections, like SharePoint On-Prem's, not expected until November 10 or later.
Source: theregister.com — Carly Page, 2026-11-03
Published there as: “Microsoft's Canada timezone troubles leave admins fixing calendars”
Read the original report → The summary and analysis above are GoKawiil's own, written from reporting by the source above. Facts and quotes belong to the original publisher.