Canada stopped changing clocks, and Microsoft's calendars are catching up

Parts of British Columbia, Alberta and Manitoba stopped observing seasonal clock changes on November 1, The Register reports. They did not turn the clocks back. The affected areas now stay on UTC-07:00, UTC-06:00 and UTC-05:00.

UTC is the world's reference time. The number after it says how many hours a place is ahead of or behind that reference.

Microsoft's own notice, as listed in its Message Center (the notes it sends to admins), says the Northwest Territories and Northwestern Ontario are also affected.

Every computer holds a list of time zones and their rules. When a government changes a rule, each program that keeps time needs the new list.

Microsoft has many programs, and each can need its own update. That is why Windows updates, Outlook and cloud tools do not all change at once.

In real life Think of a shared team calendar. If your laptop thinks Alberta is still changing clocks and your colleague's does not, the same meeting can show up at two different times.

The catch: switching to the new Canadian time zones does not update the entries you already have, The Register says. Meetings scheduled after November 1 can be an hour out.

Microsoft's notice says the same thing: existing events do not migrate on their own.

Microsoft's advice, as The Register describes it, is simple:

• Change the calendar time zone in Outlook.
• Update upcoming events and meetings to use it.
• Let the organizer do it for meetings with other people. Only the organizer can make the change.

A recurring meeting is one that repeats, such as a weekly team call. The Register says changing the time zone resets any occurrence you moved before. Those have to be recreated.

Microsoft is working on a repair command for admins, called an Exchange Online PowerShell cmdlet. PowerShell is a tool that lets admins run tasks in bulk. The Register says it covers only non-recurring meetings and is not due until later this week.

An earlier Microsoft notice had pointed to October 28 for that command, so the date has moved. A fix for recurring meetings is still "in development," with no firm date, according to The Register.

For some products, such as Power Automate and Fabric, Microsoft's temporary fix is to pick a different place that shares the right clock. The Register says that can mean Saskatchewan, Arizona or, for Manitobans, Bogota.

Microsoft's guidance, as published in its Message Center notices, lists these by province:

• Alberta: use the new Mountain Time (Alberta) zone after installing the update, or Saskatchewan for now.
• British Columbia: choose Arizona.
• Manitoba: choose Bogota, Lima, Quito.

These places keep the same time as the affected provinces for the winter. You are not moving anywhere. You are just telling the software which clock to follow.

Microsoft's notice lists what it has confirmed and what it is still checking:

• Confirmed: Outlook, Exchange Online calendars and Teams Rooms on Windows.
• Under validation: Teams, Outlook on phones and Mac, Bookings, Shifts, SharePoint Online and OneDrive.

The Register adds two later dates. SharePoint On-Prem customers wait until November 10 for the right zones. Power Pages users could see dates an hour out until a service fix arrives, with Microsoft's milestone set at December 12.

Microsoft also asks admins to install the latest Windows updates, from October 2026 on, and to keep Edge and WebView2 current on Teams Rooms devices. WebView2 is the part that lets apps show web pages inside them.

Why it matters: the timing was tight. The Register says Microsoft published its guidance on October 26, less than a week before the change, and was still adding affected products and workarounds four days later.

One sysadmin on Reddit called Microsoft's guidance "terrible," The Register reports. They said they had written roughly 900 lines of PowerShell to change users' Outlook settings and adjust calendar events by hand. Others switched systems to Saskatchewan time while they waited.

The Register notes that admins were urged to test calendars, recurring meetings and schedules before the November 1 switch. With the guidance arriving so late, that left little time to find out what might break.

Yes. The Register notes that in 2022, Chile delayed its switch to daylight saving time by a week. Microsoft warned then that Windows clocks could be wrong, scheduled tasks could run at unexpected times, and file and log timestamps could be an hour out.

Four years later, it says, governments are still changing time and software still needs to catch up.

Microsoft's notice gives admins a checklist. It is worth reading even if you are not in IT, because it shows how many pieces are involved:

1. Update systems with the latest Windows patches, from October 2026 onward.
2. Reconfigure Outlook. Users must pick the new time zone themselves.
3. Review meetings, particularly recurring series scheduled after November 1.
4. Update Edge and WebView2 on Teams Rooms devices.
5. Keep apps current on every platform.
6. Test the common cases, including recurring meetings and free/busy, the view that shows when people are available.

The notice also says it had expected to publish the repair command three days before the change. In the end, The Register says it is still a few days away.

What's next: watch for Microsoft's updates to the notice. The list of affected products has been growing, so a product that looks fine today may be added tomorrow.

People who live or work in the affected parts of British Columbia, Alberta and Manitoba feel it first. So does anyone who schedules meetings with them.

If you work in another country and book calls with a team in Calgary or Winnipeg, a wrong hour can be yours too. A quick message to confirm the time costs nothing.

The same goes for any shared calendar that mixes people in different places. One person on the wrong zone is enough to make a call start with "Wait, which time did you mean?" Checking the zone on the invite before you accept is a small habit that saves a lot of confusion.

• Check your calendar: look at meetings after November 1, especially repeating ones.
• Ask the organizer: you cannot change a meeting you did not create.
• Admins, plan ahead: open a support case with #Canada Time-Zone in the title if something breaks.
• Wait for fixes: some products do not get theirs until November 10 or later.