Microsoft's Canada timezone troubles leave admins fixing calendars

Hacker News Top News

Summary

Microsoft confirmed its software estate hasn't caught up with Canada's November 1 permanent end to seasonal clock changes, leaving admins fixing Outlook calendars, recurring meetings, and workarounds across Power Automate, Fabric, and SharePoint while fixes roll out through December.

No content available
Original Article
View Cached Full Text

Cached at: 11/03/26, 03:44 PM

# Microsoft's Canada timezone troubles leave admins fixing calendars, pretending they're in Bogota Source: [https://www.theregister.com/software/2026/11/02/microsofts-canada-timezone-troubles-leave-admins-fixing-calendars-pretending-theyre-in-bogota/5306934](https://www.theregister.com/software/2026/11/02/microsofts-canada-timezone-troubles-leave-admins-fixing-calendars-pretending-theyre-in-bogota/5306934) [software](https://www.theregister.com/tag/software)Canadian regions stop turning back the clocks, Microsoft wishes it could Microsoft has discovered once again that few things strike fear into the heart of a software engineer quite like a government deciding to fiddle with the clocks\. Parts of Canada stopped observing seasonal clock changes on November 1, leaving affected areas of British Columbia, Alberta, and Manitoba permanently on UTC\-07:00, UTC\-06:00 and UTC\-05:00 respectively\. Unfortunately, Microsoft's sprawling software empire hasn't entirely caught up\. The company has[https://support.microsoft.com/en-us/servicing/os/windows/docs/2026/10/canada-2026-time-zone-changes](https://support.microsoft.com/en-us/servicing/os/windows/docs/2026/10/canada-2026-time-zone-changes)[confirmed](https://support.microsoft.com/en-us/servicing/os/windows/docs/2026/10/canada-2026-time-zone-changes)problems across a chunk of its software estate, leaving some customers facing incorrect times, broken schedules and a collection of workarounds while Redmond catches up\. Outlook users have been left with the most homework\. Switching to the new Canadian time zones won't automatically update existing calendar entries, meaning that meetings scheduled after November 1 are potentially an hour out of whack\. Microsoft[advises](https://support.microsoft.com/en-us/outlook/calendar/timezone-changes-for-canada-provinces)users to change their Outlook calendar time zone, then update upcoming events and meetings to use it\. For meetings involving other people, only the organizer can make the change\. Recurring meetings come with an additional treat: changing the time zone resets any previously moved occurrences, which then have to be recreated\. Anyone with a calendar full of recurring meetings may wish to put the kettle on first\. Microsoft is working on an Exchange Online PowerShell cmdlet to remediate non\-recurring meetings, but according to its guidance, that's not due until later this week\. A fix for recurring meetings remains "in development," with an ETA yet to be confirmed\. Things get stranger with Power Automate and Fabric, where Microsoft's temporary fix involves pretending you're somewhere else entirely\. Depending on the product and province, that could mean Saskatchewan, Arizona or, for Manitobans, Bogota\. Because apparently time zones weren't confusing enough already\. SharePoint On\-Prem customers, meanwhile, have to wait until November 10 for the correct time zones to arrive, while Power Pages users could see server\-formatted dates appear an hour out until a service fix lands\. Microsoft's current milestone for that is December 12\. Admins dealing with the fallout aren't exactly delighted\. One sysadmin on[Reddit](https://www.reddit.com/r/iiiiiiitttttttttttt/comments/1xjukgt/three_new_timezones_enter_in_effect_next_week_in/)said Microsoft's guidance had been "terrible" and claimed to have written roughly 900 lines of PowerShell to change users' Outlook settings and manually adjust calendar events\. Others described switching systems to Saskatchewan time while waiting for Microsoft's new zones to settle in\. Microsoft published its guidance on October 26, less than a week before the change took effect, and was still adding affected products and workarounds four days later\. Meanwhile, admins were urged to test calendars, recurring meetings, and schedules before the November 1 switch, leaving little time to find out what might break\. If any of this sounds familiar, it's because time has[https://www.theregister.com/software/2022/09/07/microsoft-warns-of-bugs-after-nation-pushes-back-dst-switch/1345297](https://www.theregister.com/software/2022/09/07/microsoft-warns-of-bugs-after-nation-pushes-back-dst-switch/1345297)[caused trouble for Microsoft before](https://www.theregister.com/software/2022/09/07/microsoft-warns-of-bugs-after-nation-pushes-back-dst-switch/1345297)\. In 2022, Chile delayed its switch to daylight saving time by a week\. Microsoft responded by warning that Windows clocks could be wrong, scheduled tasks could run at unexpected times, and timestamps on files, transactions, and logs could end up an hour out\. Four years later, governments are still messing with time and software is still apparently objecting\. ®

Similar Articles

British Columbia, Time Zones, and Postgres

Lobsters Hottest

Discusses how British Columbia's permanent switch to Pacific Daylight Time in 2026 affects PostgreSQL timestamp storage, and provides best practices to avoid time zone shift errors using a dual-column pattern.

Time is a-changin’: say goodbye to the leap second

The Verge

国际计量局(BIPM)投票决定提前废除闰秒,原定2035年的计划将提前至明年5月20日生效,改用“闰小时”方案以避免潜在的基础设施故障。Meta、Google、微软和亚马逊等科技巨头此前均支持取消闰秒系统。