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 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. 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.
Admins dealing with the fallout aren't exactly delighted. One sysadmin on Reddit 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 caused trouble for Microsoft before.
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.
Originally published at theregister.com
