Microsoft's Canada timezone troubles leave admins fixing calendars

Several Canadian regions stopped changing clocks on November 1, leaving parts of British Columbia, Alberta, and Manitoba on fixed UTC offsets. Microsoft’s software had not fully adopted the new time zones, creating incorrect times and scheduling problems across Outlook, Power Automate, Fabric, SharePoint On-Prem, and Power Pages. The largest burden falls on Outlook users: changing a calendar’s time zone does not automatically correct existing events, so upcoming meetings may be an hour off. Organizers must update meetings involving others, while changes to recurring events can undo previously adjusted occurrences, forcing those instances to be recreated.

Microsoft has offered temporary workarounds, including setting some services to zones associated with other places - Saskatchewan, Arizona, or Bogota - while it develops fixes. An Exchange Online PowerShell tool for one-time meetings was expected later that week; a solution for recurring meetings had no confirmed date. SharePoint On-Prem’s updated zones were due November 10, while Power Pages dates could remain wrong until a fix targeted for December 12. Administrators criticized the short notice and incomplete guidance, with one reporting that they had written about 900 lines of PowerShell to change settings and adjust calendars. The episode recalls earlier clock-change disruptions, including Chile’s delayed daylight-saving shift in 2022, and highlights how government time-zone decisions can break software schedules and records.