British Columbia 2026 time zone update available now

Bug: Outlook for Mac – Incorrect UTC−08:00 Label for British Columbia Time Zone and One-Hour Meeting Scheduling Discrepancy

We are testing the new British Columbia time zone ahead of the November 1, 2026 transition to permanent UTC−07:00and have identified two issues in Outlook for Mac.

Issue 1 – Incorrect time-zone label

When selecting Pacific Time (British Columbia) in Outlook for Mac, the time zone displays (UTC−08:00) instead of the expected (UTC−07:00).

Issue 2 – One-hour scheduling discrepancy

We created a meeting for 10:00 AM in Outlook for Mac using the British Columbia time zone. The same meeting appeared at 11:00 AM in Outlook on the web, which was configured to Yukon (UTC−07:00).

We have already configured our Exchange Online mailboxes to Yukon Standard Time as an interim workaround. However, Microsoft's updated guidance recommends British Columbia Standard Time.

Could Microsoft confirm whether these are known Outlook for Mac bugs, whether a fix is planned, and whether organizations should continue using Yukon Standard Time until the issues are resolved?

I found a bug with the timezone conversion at 7 UTC on Jan 1, 2027 in .Net Framework 4.8.

TimeZoneInfo.Local
{(UTC-07:00) Pacific Time (British Columbia)}

TimeZoneInfo.ConvertTimeFromUtc(new DateTime(2027, 1, 1, 6, 0, 0, DateTimeKind.Utc), TimeZoneInfo.Local)
{2026-12-31 11:00:00 PM} -- Correct

TimeZoneInfo.ConvertTimeFromUtc(new DateTime(2027, 1, 1, 7, 0, 0, DateTimeKind.Utc), TimeZoneInfo.Local)
{2026-12-31 11:00:00 PM} -- Wrong

TimeZoneInfo.ConvertTimeFromUtc(new DateTime(2027, 1, 1, 8, 0, 0, DateTimeKind.Utc), TimeZoneInfo.Local)
{2027-01-01 1:00:00 AM} -- Correct

Will this be fixed in a future patch or is this a limitation of the Dynamic DST data stored within the registry?  The same issues exists with the new Alberta timezone at 6 UTC on Jan 1, 2027 as well.

October 26: It's currently not possible to change your time zone to "Pacific Time (British Columbia)" in your Microsoft Account (account.microsoft.com): an error "Something went wrong" is displayed. Network requests capture reveals the issue:

{

"code": "ErrorBadRequestInvalidRequestBody",

"message": "'British Columbia Standard Time' is not a valid time zone.",

"target": "RegionalFormatOverrides.TimeZone"

}

It is not clear why it is referred to as BC Standard Time, since it's actually Daylight Savings Time made permanent for some strange reason.

Setting Yukon (-07:00) works -- and helps.

Hi, Our organizations have several Windows 10 and Windows 11 PC which cant get the new timezone update.
Question: Is it OK to switch them to Yukon time right now or that can only be done after November 1st?

One week until the new time zone kicks in, and few things are still breaking in Outlook and Teams when setting Exchange Online WorkingHoursTimeZone to the new British Columbia Standard Time. Room finders, presence status (busy/available), and Work Hours and Location settings failing to load with "something went wrong" error.

After applying the updates and selecting the new time zone in Windows (and verifying Outlook Classic has the same time zone), the Room Availability feature breaks and hangs on "updating..."

The new timezone appears to work at OS level, but the Microsoft Teams app does not seem to be able to handle it. Teams message timestamps are -1 hour off.

This timezone (and potentially the other newly added one) are not included in the `icu.dll` that ships with Windows; this means that any C++ app using the Microsoft STL will have an exception in `std::chrono::current_zone()` when these new timezones are used.

We are testing out the October monthly and while we have the new BC timezone, powershell states that it still uses DST. It should not say supports daylight savings time, but it does.