Blog Post
Interim guidance for Alberta time zone changes 2026
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.
The governments making these changes need to give Microsoft enough time to include the new time zones in their OS and applications....
- ricky_chippyOct 17, 2026Copper 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.