GoKawiilMicrosoft scrambles to fix time-zone bugs after parts of Canada skip clock change
After certain Canadian provinces stopped observing daylight-saving time changes on November 1, Microsoft confirmed widespread time-zone bugs across Outlook, Power Automate, Fabric, SharePoint and Power Pages. Fixes range from manual calendar updates in Outlook to workarounds that have users select unrelated time zones like Saskatchewan, Arizona or Bogota in Power Automate and Fabric, with some permanent fixes not expected until mid-November or December.
GoKawiil's interpretation of the reporting above, not reported fact.
The episode shows how deeply time-zone assumptions are baked into enterprise software, and how a regional policy change can ripple across an entire product suite built on shared infrastructure. Admins and users are left manually reconciling calendars in the meantime, which suggests Microsoft's systems were not built to handle regional daylight-saving exceptions gracefully.
- Canadian provinces ending seasonal clock changes exposed time-zone bugs across multiple Microsoft products.
- Outlook users must manually update calendar entries, with recurring meetings requiring extra rework.
- Full fixes are staggered, with SharePoint On-Prem due November 10 and Power Pages not expected until December 12.
Source: news.slashdot.org, 2026-11-02
Published there as: “Microsoft's Canada Timezone Troubles Leave Admins Fixing Calendars, Pretending They're In Bogota”
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.