Microsoft's Canada Timezone Troubles Leave Admins Fixing Calendars, Pretending They're In Bogota
8 105Microsoft is scrambling to fix time-zone problems across Outlook, Power Automate, Fabric, SharePoint and other products after parts of Canada stopped observing seasonal clock changes on November 1. "The company has confirmed 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," reports The Register. From the report: 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 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.
8 comments
Re:IST (Score: 5, Funny)
by TwistedGreen ( 80055 ) on Monday November 02, 2026 @01:38PM (#66406365)
I tried to use Swatch Internet Time but Outlook still doesn't recognize scheduling meetings with @beats
Re:Those who cannot remember the past... (Score: 5, Interesting)
by acroyear ( 5882 ) on <jws-slashdot@javaclientcookbook.net> on Monday November 02, 2026 @03:47PM (#66406593)
The 'prior art' is not y2k but rather the DST change in 2006 (to our current weekends in North America).
That was when they restructured most of their timezone information into easily updated files that made the operating system generally adapt pretty quickly, along with client-side software for anything *newly* generated in scheduling software.
However, the issues here are what to do about already-existing scheduled events - how do they adapt depends on what your internal model is for storing "where" they are (which timezone they're meant to follow). If you didn't separate out America/Vancouver in your system because it was always the same as America/Los_Angeles...it is an almost unfixable problem because you have no way to isolate what is and isn't in "Canada".
So this is why I've been saying, for months now since it was announced, that it was going to be a mess because there wasn't enough time to develop and test the solutions in the middle of all of the other work that app teams are doing (often with reduced resources due to the layoffs of the last 3 years) before everything went live. You really want this stuff tested AT LEAST 6 months before the first change, preferably a full year.
I can't imagine the scheduling disasters for anybody actually using Egypt time over the last 15 years, when they ditched DST, *partially* brought it back (the day would change based on Ramadan) and then in March of '23 announced that in April of '23 they would go back to switching. Pretty sure anybody of any import just set their clocks collectively to something from Europe for the stability.
Re:Can't we define the timezone as a UTC offset? (Score: 5, Informative)
by Kernel Kurtz ( 182424 ) on Monday November 02, 2026 @01:42PM (#66406375)
Can't we define the timezone as a UTC offset? I thought WIndows, macOS and Linux all allowed that?
On Linux in this case you can use the Etc/GMT+5 timezone (note the POSIX inversion is not a typo), which is a permanent UTC-5 with no DST changes.
Re:Can't we define the timezone as a UTC offset? (Score: 5, Interesting)
by kqs ( 1038910 ) on Monday November 02, 2026 @07:29PM (#66407009)
I don't really agree. Timezones, DST, and TZ definitions are very well understood. Every year several (mostly small) countries make last-minute TZ changes and they get pushed out and handled; this is not new and untested tech. Sure we need some level of QA; we always need more testing! but changing a TZ file has very few side effects. All internal time info is already stored at UTC, so the TZ changes how it is displayed but not how it is consumed or calculated. MS did not push out critical changes for a rather major country, despite having sufficient time and incentive. And the change was not difficult or fragile.
How did no one test this? (Score: 5, Insightful)
by Murdoch5 ( 1563847 ) on Monday November 02, 2026 @01:20PM (#66406333)
The changes to Canadian timezones didn't happen on short notice, they were established months ago. Microsoft had more than enough time to adjust all the timezones, meaning this screw up is intentional. Adding to the increasing list of things Microsoft can't manage, telling time . . . maybe they should visit an elementary school, I'm sure a Jr K teacher could help them.
Re:How did no one test this? (Score: 5, Insightful)
by ceoyoyo ( 59147 ) on Monday November 02, 2026 @01:28PM (#66406347)
From the summary it sounds like they did adjust the timezones but they didn't anticipate that anyone would actually change timezones. That doesn't particularly surprise me since Windows doesn't even have a setting to keep the system clock in UTC.
As a Canuck ..... (Score: 5, Funny)
by DaveyJJ ( 1198633 ) on Monday November 02, 2026 @01:40PM (#66406369)
I did love the recent headline in The Beaverton (our version of The Onion).
No one in Canada knows what time it is anywhere else in Canada
Actually is a hard problem, fault of politicians (Score: 5, Insightful)
by caseih ( 160668 ) on Monday November 02, 2026 @01:52PM (#66406403)
This is actually a much harder problem to address than it would seem. Obviously if the remote meeting event was in, say New York, and I find myself in a place where MDT is now year round, a simple time zone conversion is all that's needed and nothing breaks so long as the local client has an updated time zone list. But if the meeting was scheduled in a city that is now part of a different time zone, now it's off for everyone all over the world. And there's no easy way for the calendaring system to know the difference between those two scenarios. So we have a mess for sure, and it's a mess of a just a few politicians' making.