If your organisation has staff or customers in British Columbia, Alberta or Manitoba, some of your meetings and automated schedules may now sit an hour away from where they should. Microsoft’s fixes for the Canadian clock change are partial, staggered over weeks and in some cases still undated. Until they land, the cleanup falls on administrators and on individual meeting organizers.
What happened
According to The Register, parts of Canada stopped seasonal clock changes on 1 November. Affected areas of British Columbia, Alberta and Manitoba now stay on UTC-07:00, UTC-06:00 and UTC-05:00 respectively. Microsoft has confirmed problems across several products.
In Outlook, switching to the new Canadian time zones does not update existing calendar entries, so meetings after 1 November can be an hour off. Microsoft’s guidance is to change the calendar time zone and then update upcoming events. For shared meetings, only the organizer can do that. For recurring meetings, the change resets previously moved occurrences, which then need recreating.
The Register reports that an Exchange Online PowerShell cmdlet for non-recurring meetings is due later this week, while a recurring-meeting fix is still in development with no confirmed date. For Power Automate and Fabric, the temporary workaround means selecting another region’s time zone, such as Saskatchewan, Arizona or, for Manitoba, Bogota. SharePoint On-Prem gets the correct zones on 10 November, and Power Pages date formatting has a service-fix milestone of 12 December.
Why it matters
Time zone rules are data that every layer of a software stack copies and caches: operating systems, calendars, workflow engines, databases and on-prem servers. When a government changes the rules, each layer updates on its own schedule. The result is the mismatch now visible across Microsoft’s products, where one tool knows the new zone and another does not.
The timeline is the sharper lesson. The Register says Microsoft published its guidance on 26 October, less than a week before the change, and kept adding affected products and workarounds days later. That leaves little room for the testing Microsoft itself urged. The Register also recalls Chile’s 2022 delay of its daylight saving switch, which brought similar warnings about wrong clocks, misfired scheduled tasks and shifted timestamps. This suggests the problem is recurring, not a one-off.
What it means for you
Start with exposure. List which users, shared mailboxes, meeting rooms, automated flows and reports are tied to the affected provinces. Then audit meetings dated after 1 November, especially those organized by people outside your tenant or by executives whose calendars others depend on.
Decide whether to script or wait. One sysadmin told Reddit users they wrote roughly 900 lines of PowerShell to change Outlook settings and adjust events. Writing your own tooling is costly and risky, particularly for recurring series. If the Exchange Online cmdlet arrives this week as planned, test it on a pilot group first. Do not touch recurring meetings in bulk before a supported fix exists, since the reset of moved occurrences can create more work.
For automation, document every Power Automate and Fabric workaround. A flow set to Bogota or Saskatchewan time is a hidden exception that someone must remember to reverse. Record it, assign an owner and set a reminder to revert once Microsoft’s correct zones are in place. Teams on SharePoint On-Prem should plan around 10 November, and Power Pages owners should expect an hour of drift on server-formatted dates until the December milestone.
Longer term, ask vendors how quickly they ship time zone database updates and how they communicate rule changes. Add government time rule changes to your change calendar so testing starts weeks ahead, not days. Our software coverage follows similar vendor-readiness issues.
What to watch
- Release of the Exchange Online PowerShell cmdlet for non-recurring meetings, due later this week.
- A confirmed date for the recurring-meeting fix, which remains in development.
- The 10 November SharePoint On-Prem update and the 12 December Power Pages milestone.
- Further products added to Microsoft’s affected list as admins report new breakage.
