Blog Post

Daylight Saving Time & Time Zone Blog
3 MIN READ

Alberta 2026 time zone update available now

Naveen_Shankar's avatar
Oct 14, 2026

Editor's note October 27, 2026: We've updated this blog post to include additional IT guidance for Microsoft products. Microsoft has released an update to address the new time-related change for Alberta...

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 is releasing the Windows updates below in support of this decision. This change is available in the September 2026 non-security preview update, released on September 22, 2026, for Windows 11, versions 25H2, 24H2. All other supported Windows versions will receive the update as part of the October monthly security update scheduled for release on October 13, 2026. 

Visit Interim guidance for Alberta time zone changes 2026 for an earlier announcement of this change.  

Updates by Windows version 

Here are the knowledge base (KB) articles that contain the Alberta DST adjustment for different versions of Windows: 

Product 

KB number 

Windows 26H1

KB5127653

Windows 11, versions 25H2, 24H2 

KB5124010 

Windows 11, version 23H2 

KB5126653 

Windows Server 2025 

KB5126646 

Windows Server 2022 

KB5126655 

Windows 10 Enterprise LTSC 2021 

KB5126657 

Windows Server 2019 

KB5126651 

Windows Server 2016 

KB5126868 

 

All Windows updates containing this adjustment have the following release note text: 

“[Date and Time] This update enables permanent Daylight Savings Time (DST) support for British Columbia and Alberta starting in November 2026.” 

Workarounds 

Important: Some Microsoft 365 apps and services, such as Outlook and Exchange Online calendars, require admin and user action. Microsoft Teams Rooms on Windows devices need an Edge/WebView2 update. Other Microsoft 365 workloads are being validated. For guidance and latest updates, refer to Canada 2026 time zone changes: Guidance for Microsoft products. 

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 workaround. After November 1st, 2026, we suggest using the below fixed-offset alternatives only as temporary workarounds: 

Affected area 

Existing choice before the transition 

Temporary 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. 
     

Visit Interim guidance for Alberta time zone changes 2026 for an earlier announcement of this change.  

For Microsoft's official policy on DST and time zone changes, please see Daylight saving time help and support. For information on how to update Windows to use the latest global time zone rules, see How to configure daylight saving time for Microsoft Windows operating systems. 

Updated Nov 02, 2026
Version 5.0

8 Comments

  • DJeffrey's avatar
    DJeffrey
    Tin Contributor

    Well, this is turning into a nightmare.  Microsoft has released the patch for Windows 11 and Servers, but there are a many of side-effects.  Here are some of the other items:

    • SharePoint Calendars needs to be adjusted.
    • Teams code base is inconsistent; you see a mixture of times shifts in the Calendar and Chat Log.
    • Teams Rooms - depending if it is Android or Windows, should be checked.
    • Google Chrome does not know how to use the new time zone.  (https://support.google.com/chrome/thread/472933334/chrome-incorrectly-detects-alberta-s-new-utc%E2%88%926-timezone-as-utc%E2%88%927?hl=en)
    • Apple Calander needs to be checked, if it is connected to Exchange

    https://support.microsoft.com/en-us/outlook/calendar/timezone-changes-for-canada-provinces

    https://learn.microsoft.com/en-us/answers/questions/6002950/microsoft-bookings-timezone-support-for-british-co

    https://devblogs.microsoft.com/azure-sql/canadas-2026-time-zone-updates-guidance-for-microsoft-sql/

    https://learn.microsoft.com/en-us/answers/questions/6026743/new-outlook-for-mac-and-outlook-for-ios-display-al

    Additionally, this year IsDaylightSavingTime returns TRUE, next year it is FALSE.  Who thinks that will not causes a programming issue.

    #Store current time zone value
    $tz = Get-TimeZone
    $tz
    
    #show before and after values for UTC offset and DST support
    $dates = @(
        [datetime]'2026-10-31 12:00',
        [datetime]'2026-11-01 12:00',
        [datetime]'2026-12-01 12:00',
        [datetime]'2027-01-15 12:00',
        [datetime]'2027-07-15 12:00'
    )
    foreach ($date in $dates){
        [PSCustomObject]@{
            Date      = $date
            UTCOffset = $tz.GetUtcOffset($date)
            IsDST     = $tz.IsDaylightSavingTime($date)
        }
    }
    
    #show adjustment rules
    $tz.GetAdjustmentRules() | Format-List *

    Results in:

    Date                   UTCOffset IsDST
    ----                   --------- -----
    10/31/2026 12:00:00 PM -06:00:00  True
    11/1/2026 12:00:00 PM  -06:00:00  True
    12/1/2026 12:00:00 PM  -06:00:00  True
    1/15/2027 12:00:00 PM  -06:00:00 False
    7/15/2027 12:00:00 PM  -06:00:00 False

     

    • DJeffrey's avatar
      DJeffrey
      Tin Contributor

      We continue to uncover new complexities with this change. Here’s one most organizations probably haven’t considered: what happens to recurring meetings that include Teams Room calendars when some employees have moved their meetings from “US & Canada” to “Alberta” and others haven’t?  Those meeting updates get declined.... 

      Some companies are planning to avoid the issue by simply switching to the Saskatchewan time zone. That may be easier in the short term, but it doesn’t solve the underlying problem. It just postpones it.

  • ELangeland's avatar
    ELangeland
    Tin Contributor

    On the new time zone, the Work Hours and location features in Outlook and Teams are not working.

    In Classic Outlook, my existing work hours show correctly in the calendar, and existing locations are displayed. However, I can't change them.

    In Outlook on the web, work locations aren't shown, and when attempting to set them via the Options I get a banner message "Something went wrong while updating your schedule. Please try again later."

    In Teams, no one's work location is shown, and I am not able to see or set my own work location.

    I can't be certain this is specifically related to the time zone update, but that is the only change since last week, when this worked normally.

  • ELangeland's avatar
    ELangeland
    Tin Contributor

    With this OS update installed and the new time zone set, there are issues in Teams:

    Also, time stamps on Teams chat messages are one hour off, and users on the original time zone show the wording "Your time zone is 1 h behind." in their contact card pop-up.

  • abe_ybanez's avatar
    abe_ybanez
    Copper Contributor

    We currently have a mismatch on time in our TMRs. The PC itself has the new time zone and has changed to it. Windows time is correct.

    But the meeting room panel when it is in the Teams account displays the wrong time.  The Alberta Time Zone is also not available on myaccount.microsoft.com.

    I will second DDJeffrey. The communication has been underwhelming. 

  • DJeffrey's avatar
    DJeffrey
    Tin Contributor

    In the previous versions of the posting here you had reference to Outlook.  Since that was information was dropped, does that mean?

    A) It was never a problem; B) It will be fine; C) Microsoft will automatically update all reoccurring meetings across the Standard and Daylight times that were previously set; D) All the Daylight calendar reoccurring meetings will shift by an hour; E) Not sure, we will get back to you.

    We have already seen issues (shift ahead one hour) as we try and get ahead of this and shift our Teams Meeting Room equipment.  What is the status of that?  (Looking for information on both Android and Windows TMR)

    Now you have us thinking... How will meetings show up in Apple Calendar and iOS Outlook Calendar?  What about Android?

    The communications of this change and impacts has been underwhelming.

    • ELangeland's avatar
      ELangeland
      Tin Contributor

      What I see in Outlook (classic Outlook for Windows with M365 mailboxes) is that pre-existing meetings show as created in the prior time zone. They need to be edited and updated to the new time zone manually.