Blog Post

Daylight Saving Time & Time Zone Blog
3 MIN READ

Interim guidance for Alberta time zone changes 2026

Naveen_Shankar's avatar
Aug 07, 2026

Microsoft has made a decision about addressing the new time-related change for Alberta.

Editor's note October 13, 2026: Microsoft has released an update to address the new time-related change for Alberta. Please refer to Alberta 2026 time zone update available now

Earlier in June 2026, the Alberta government made an official announcement that it will stay on Permanent DST or UTC-6 time zone.

The impact of this change is as follows:

  1. Clocks will not be set back by an hour at 02:00 a.m. on November 1st, 2026, for the Alberta time zone.
  2. The Alberta time zone will permanently shift to the UTC-6 time zone.

Microsoft plans to release an update to support this change. However, we require sufficient time to properly build, test, and release such an update for all platforms before the change goes into effect. See How Windows manages time zone changes to better understand the complexities of this process.

Customers must install the update before permanent time changes take effect on November 1st, 2026. This Windows update introduces a new time zone:

Affected areaName displayed in Windows Settings (New Time Zone)Registry time-zone ID
Alberta and affected Northwest Territories locations including Yellowknife and Inuvik(UTC-06:00) Mountain Time (Alberta)Alberta Standard Time

The Alberta time zone also applies to affected Northwest Territories locations, including Yellowknife and Inuvik.

The registry time-zone IDs are intended primarily for administrators and command-line tools. End users normally see only the windows settings display names.

Release Plan

The following platforms will receive an update to support this time zone change as part of September 2026 non-security update, scheduled for September 22, 2026:

  • Windows 11, version 26H2
  • Windows 11, version 25H2
  • Windows 11, version 24H2

The following platforms, including windows server versions will receive the update as part of October 2026 security update, scheduled for October 13, 2026.

  • Windows 11, version 23H2 (supported editions)
  • Windows Server 2025
  • Windows Server 2022
  • Windows Server 2019
  • Windows Server 2016

Note: Windows 11, version 26H1 OS platform will receive an update to support this time zone change as part of October 2026 cumulative non-security update, scheduled for October 28, 2026

For additional information, please review our official policy page and How Windows manages time zone changes.

After installing the update, verify the selected time zone under: Settings > Time & language > Date & time

Case #1 - Automatic time-zone selection 

If Set time zone automatically is enabled and location services are available, Windows will automatically select the appropriate time zone based on the device's location. No manual action is required. It shall be reflecting to (UTC-06:00) Mountain Time (Alberta) windows display name.

Case #2 - Manual time-zone selection

If automatic time-zone selection is disabled, users must select the appropriate zone manually:

  1. Open Settings > Time & language > Date & time.
  2. Turn off Set time zone automatically, if it is enabled.
  3. Under Time zone, select the applicable Windows display name:
    • (UTC-06:00) Mountain Time (Alberta) for Alberta and affected Northwest Territories locations, including Yellowknife and Inuvik.
  4. Confirm that the displayed date and time are correct.

Interim Guidance when the update is unavailable

Before the permanent-time transition takes effect on November 1st, 2026, the existing seasonal zones continue to provide the expected current offset. In cases where the monthly update cannot be received or installed before 1st of November, affected organizations with devices in Alberta are advised to use the following workarounds:

 After November 1st, 2026, we suggest using the below fixed-offset alternatives only as temporary workarounds:

Affected areaExisting choice before the transitionTemporary choice after the transition
Alberta(UTC-07:00) Mountain Time (US & Canada) (Mountain Standard Time)(UTC-06:00) Saskatchewan (Canada Central Standard Time)
Yellowknife and Inuvik(UTC-07:00) Mountain Time (US & Canada) (Mountain Standard Time)(UTC-06:00) Saskatchewan (Canada Central Standard Time)
Southeastern B.C. locations aligning with Alberta(UTC-07:00) Mountain Time (US & Canada) (Mountain Standard Time)(UTC-06:00) Saskatchewan (Canada Central Standard Time)

 

  • These alternatives provide the required UTC offset but have different names, geographic mappings, and historical rules. They should not be treated as permanent replacements. 
  • We recommend installing the Windows monthly update and move to the appropriate region-specific time zone as soon as possible.

Guidance on Outlook: Users will need to update their Outlook settings and change the time zone on any existing calendar events. Refer to Outlook Time Zone Changes for Alberta and British Columbia | Microsoft Support

Updated Oct 27, 2026
Version 7.0

39 Comments

  • JamesEpp's avatar
    JamesEpp
    Iron Contributor

    Beggars can't be choosers, especially without all the official details worked out yet.

    Could Microsoft please work on providing interim guidance to Manitobans in light of (pending) changes to the Official Time Act?

    At present I have two urgent questions:

    1. Are the best candidates for UTC-5 permanent timezones built into Windows (until Manitoba Standard Time is available via an update) "SA Pacific Standard Time" and "Eastern Standard Time (Mexico)"? Should customers use these during the interim?
    2. How should customers respond when it comes to cloud (MS365/D365/Azure) services? Do all services follow the local time/timezone configuration of the client browser or could reconfigurations (to an interim timezone) be required (i.e. Outlook calendaring)?

     

     

    • BisonBrianTownsend's avatar
      BisonBrianTownsend
      Tin Contributor

      Things should be official now - the proclamation from the Lieutenant Governor of the Province of Manitoba has been entered

      https://web2.gov.mb.ca/laws/statutes/proclamations/2023c4(2026-10-31).php
      It refers back to 

      https://web2.gov.mb.ca/laws/statutes/2023/c00423.php which states

      Coming into force

      4  This Act comes into force on a day to be fixed by proclamation.

      So we now have a date for this to officially take place, by proclamation.  I believe that's all the legal hurdles overcome.

  • CoachJayson's avatar
    CoachJayson
    Copper Contributor

    For those of you whose desktop Zoom app broke when Microsoft rolled this out, it looks like Microsoft has something in the new time zone code that Zoom Workplace does not understand.

    In Windows 11, the Zoom Workplace desktop app may start showing the errors below but will not load your actual schedule.

    The particularly helpful part is that Windows Settings does not show that you have been automatically changed to "Mountain Time (Alberta)." It may still display whatever specific time zone you had selected before, such as "Mountain Time (US & Canada)" or "Mountain Time (Edmonton)."

    Behind the scenes, however, Microsoft DID change the time zone to the new Alberta setting, which Zoom Desktop apparently does not recognize.

    The fix is:

    1. Disable automatic time zone detection.
    2. Change your time zone to something other than any UTC-6 time.  If you choose any -6 existing timezone, Microsoft happily keeps it behind the scenes as the new "Mountain Time (Alberta)" without showing this to you.
    3. Change it back to "Mountain Time (US & Canada)."

     

    That forces Windows to actually reset the time zone instead of quietly using the new Alberta configuration while displaying something else in Settings.

    The error will return if you manually set the timezone back to Mountain Time (Alberta), or automatic timezone.  You must leave it manually set to a non Alberta specific timezone until Zoom fixes their timezones.

    I noticed the problem in Zoom, but I am sure Microsoft's wise decision not to tell you in the Settings app that you were automatically reconfigured to the new Alberta time zone will make troubleshooting equally entertaining in any other applications that do not recognize it.

    Zoom errors I encountered:

    You haven't connected your calendar yet. Connect now to manage all your meetings and events in one place.

    or

    Calendar sync failed

    We couldn't detect your device's time zone. Please contact your IT administrator or check your operating system settings.

    or

    Calendar Sync Failed

    An error occurred. Try again later.

    • ricky_chippy's avatar
      ricky_chippy
      Copper Contributor

      It's not just zoom, it's every electron-based app (including Teams for desktop) because Microsoft bungled the implementation of the new time zone and anything browser-based can't determine what the time zone actually is.

      Set your time to the new AB time and then go to this website - https://webbrowsertools.com/timezone/ - It's even broken in Edge. Any website I visit with a timestamp is off by 1h. 

       

  • Mike2068's avatar
    Mike2068
    Tin Contributor

    I installed the September 22 optional update only to find there is no new time zone for AB.  Not sure when this fix is coming.

      • Mike2068's avatar
        Mike2068
        Tin Contributor

        It is strange that the first machine I installed it on did not show up so I did try a second one and can see it there.
        I assume this will be rolled out through the regular patch Tuesday (Oct 13) along with the server side.

  • Lifeguard28's avatar
    Lifeguard28
    Copper Contributor

    I am looking forward to a new time zone for Manitoba too. 

    https://news.gov.mb.ca/news/?archive=&item=75397

    • BisonBrianTownsend's avatar
      BisonBrianTownsend
      Tin Contributor

      It's in there, but I'm not looking forward to it.....

      All calendar events in Outlook store the tz data, so the owners will all need to change from Central Time (US & Canada) to Manitoba time on every single meeting invite.  Outlook Classic will pick up the zone from Windows, but that won't adjust existing calendar objects.

      Outlook on the Web still doesn't have the AB, BC or MB zones.
      New Outlook has BC and AB but not MB.

      Who knows what syncing between those is going to do if there is a tz mismatch.

      Zoom crashes if the tz is unrecognized.


      • ELangeland's avatar
        ELangeland
        Tin Contributor

        Zoom appears fine with the latest version (as of yesterday) installed.

  • DJeffrey's avatar
    DJeffrey
    Tin Contributor

    According to the Microsoft https://aka.ms/time, this process is 2 months behind.  Microsoft needs to provide customers with enough time to adjust processes and test systems and infrastructure.

    • BisonBrianTownsend's avatar
      BisonBrianTownsend
      Tin Contributor

      The governments making these changes need to give Microsoft enough time to include the new time zones in their OS and applications....

      • ricky_chippy's avatar
        ricky_chippy
        Copper Contributor

        Alberta announced the end of time change in March, formalized it in June. 

        Microsoft released the first update for it in a PREVIEW release at the end of September. Then released it in the patch Tuesday release with less than 3 weeks before time change. Predictably things are broken, because it's Microsoft. All electron based apps (including Microsoft's own Teams desktop app) pull the wrong time because the TZ mapping library wasn't updated by Microsoft. My browsers (including Microsoft's own Edge browser) all show the wrong time for the same reason. This is on a PC, not a Mac. I'm using Windows, Office 365 and even across their own products I can't get a consistent time to show up across all my applications. I can't set my work hours in Outlook when I'm in the AB time zone.

        There's a fix posted on the BC interim time zone where someone figured out how to recompile the time zone translation modules to fix all the broken apps under windows. Someone who doesn't work for MS figured this out in like 2 weeks, but Microsoft couldn't sort it or test it in 6 months?

        It's worth mentioning I'm a MS partner and have been for 20 years, this is what I do for a living. It's not a user config issue. It's Microsoft making slop and getting complacent about what they should provide as a minimum to their customers.

        If Microsoft can't add a timezone properly in 6 months, how much notice will they need? Maybe they could stop vibe coding and get a QA team back, but no, it's better that we pay more for less every year.