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