B.C. Time Zone Change 2026: Microsoft 365 Admin Checklist

British Columbia did not turn its clocks back on November 1, 2026. Most of the province now stays on UTC-7 all year, while Washington, Oregon and California fell back to UTC-8. For Microsoft 365 admins, that’s a practical problem: PCs, calendars, SharePoint sites and scheduled flows that still follow (UTC-08:00) Pacific Time (US & Canada) can show or run an hour off for people in B.C. How much depends on each product and its settings, so it’s worth checking rather than assuming.

Microsoft has published guidance for each product, and some fixes are still rolling out. This is the checklist I’m working through with the organizations I support, with links to Microsoft’s guidance for each step.

The short answer

• Windows: install the latest updates and use the new time zone (UTC-07:00) Pacific Time (British Columbia). PCs that can’t get the update can use (UTC-07:00) Yukon for now.
• Outlook: each user switches their calendar to the new time zone. Organizers check meetings on or after November 1, especially recurring series.
• Teams Rooms: update Microsoft Edge and WebView2, then check the room’s clock.
• SharePoint Online: check each site’s time zone. Sites on Pacific Time (US & Canada) now show times an hour behind B.C. time.
• Power Automate: check schedules and time zone conversions. Until flows support the new zones, Microsoft’s temporary choices for B.C. are Arizona in schedule triggers and Yukon in conversions.
• Alberta and Manitoba made the same kind of change, with their own new time zones. Don’t give people there the B.C. zone.

What changed

B.C. adopted permanent daylight time in 2026. The province calls its year-round time Pacific time, set at UTC-7, and the switch was complete when clocks didn’t fall back on November 1, 2026 (B.C. government announcement). Vancouver and Seattle are now an hour apart all winter.

Not every part of B.C. follows that rule. People in the Peace River region and the northern Rocky Mountains were already on UTC-7 all year, so they now match the rest of the province. The East Kootenay and Golden area stays aligned with Alberta, and local governments can still choose their own time zone. If you have offices there, check which time they follow before you assign a time zone.

Alberta and Manitoba also stopped changing their clocks on November 1, 2026. Microsoft added a new time zone for each province (Microsoft’s Outlook guidance):

Province	New time zone
British Columbia	(UTC-07:00) Pacific Time (British Columbia)
Alberta	(UTC-06:00) Mountain Time (Alberta)
Manitoba	(UTC-05:00) Manitoba

This checklist uses the B.C. zone in its examples. If you support people in Alberta or Manitoba, the same steps apply with their zone.

Windows: set the new time zone on every PC

Microsoft added (UTC-07:00) Pacific Time (British Columbia) to Windows in its September and October 2026 updates (Microsoft’s interim guidance for B.C.). Devices on unsupported Windows versions don’t get it.

1. Make sure B.C. devices have the latest Windows updates.
2. Check Settings > Time & language > Date & time. With Set time zone automatically on and location services available, Windows can switch by itself. Otherwise, select the new zone.
3. For a PC that can’t get the update yet, Microsoft’s interim guidance gives (UTC-07:00) Yukon as the temporary choice. Yukon is UTC-7 all year too. Write down which PCs use it and move them to the B.C. zone once they’re updated.

Don’t leave PCs on Pacific Time (US & Canada). That zone fell back on November 1, so those clocks are now an hour behind.

One related problem: older versions of Chrome don’t recognize the new Windows time zone, and SharePoint can fail with “Failed to load current time zone” when saving a date. I wrote up the cause and the fix in Fix “Failed to load current time zone” in SharePoint. Updating the browser is the real fix.

Outlook and Exchange Online: review calendars

This is where most people will notice the change. Changing the Windows time zone doesn’t move existing calendar events, so each user switches their calendar too (Microsoft’s Outlook guidance):

• New Outlook and Outlook on the web: Settings > Calendar > View > Time zones, then set Display my calendar in time zone to (UTC-07:00) Pacific Time (British Columbia) and save.
• Classic Outlook: File > Options > Calendar > Time zones, then pick the new zone.
• Outlook mobile creates events in the device’s time zone, so the phone needs the right zone. Existing events have to be fixed in Outlook on the web or the desktop app.
• Outlook for Mac needs build 16.114.26102345 or later to show the new zones.

Then check meetings on or after November 1:

• Only the organizer can change a meeting with attendees. Attendees get an updated invitation when the organizer saves it.
• Changing the time zone of a recurring series resets its exceptions. If one meeting in the series was moved, write that down first and recreate it afterwards.
• Pay attention to meetings with people in Washington, Oregon or California. During winter those cities are now an hour behind Vancouver.

Microsoft plans an Exchange Online PowerShell cmdlet to fix non-recurring meetings, planned for November 4, 2026. A date for recurring meetings isn’t confirmed yet (Canada 2026 time zone changes: guidance for Microsoft products). I’d wait for Microsoft’s instructions before you run it across a tenant.

Teams and Teams Rooms: test real meetings

Microsoft’s guidance lists these Teams items (Microsoft’s product guidance):

• Teams clients: possible issues with meeting times, time zone labels and notifications. Check meetings scheduled after November 1.
• Teams Rooms on Windows: confirmed. Affected rooms showed the time an hour behind Windows. Update Microsoft Edge and WebView2, then check the time on the room display.
• Teams auto attendants: the correct time zones may not be available yet. Microsoft’s workaround is to update the time zones manually, so check business hours and holiday routing.

Include a meeting room in your testing, not just laptops. A wrong time on the room panel is the first thing people will report.

SharePoint Online: check each site’s time zone

Microsoft lists SharePoint Online as mitigated: a configuration update was scheduled to reach the Canada region by October 29, 2026. In the tenant I worked in, the new zone was already in each site’s time zone list. The update doesn’t change the time zone your sites already use, though.

Why a site can be an hour off

Every SharePoint site has its own time zone in its regional settings, and SharePoint shows dates and times in that time zone (Change regional settings for a site). Many sites in B.C. use (UTC-08:00) Pacific Time (US and Canada). Since November 1 that zone is UTC-8 and B.C. is UTC-7, so those sites show modified dates, list dates and times one hour behind B.C. time.

Two things change what people see:

• Personal settings. People can set their own time zone, which SharePoint uses instead of the site’s (Change your personal language and region settings). If one person still sees a different time, check their personal settings.
• New sites. New sites take the time zone of the SharePoint admin center, which is Pacific Time by default. Microsoft advises against changing the admin center’s own time zone, because creation dates on the Active sites page then mix two time zones (Microsoft’s admin center guidance). Set the time zone on new sites as part of how you create them instead.

Change one site

As a site owner, open Settings > Site information > View all site settings > Regional settings, choose (UTC-07:00) Pacific Time (British Columbia) under Time zone, and select OK.

With PnP PowerShell, this reads the site’s current time zone and finds the new one by name rather than by a numeric ID. Run it against a test site first:

Connect-PnPOnline -Url "https://contoso.sharepoint.com/sites/finance" -Interactive -ClientId "<your-app-id>"

$web = Get-PnPWeb -Includes RegionalSettings, RegionalSettings.TimeZone, RegionalSettings.TimeZones
$current = $web.RegionalSettings.TimeZone
$target = $web.RegionalSettings.TimeZones |
    Where-Object Description -eq "(UTC-07:00) Pacific Time (British Columbia)"

"Current: $($current.Id) $($current.Description)"
if (-not $target) { throw "The new B.C. time zone isn't offered on this site yet." }
"Target:  $($target.Id) $($target.Description)"

Nothing has changed yet. Keep the current ID somewhere safe, then make the change:

$web.RegionalSettings.TimeZone = $target
$web.Update()
Invoke-PnPQuery

To undo it, set the time zone back to the ID you saved, the same way. The approach follows the PnP regional settings sample.

Change many sites

I recently moved every SharePoint site and subsite in a tenant to the new time zone for an organization I support. What made it safe was doing it in this order:

1. Inventory. List every site and every subsite. Subsites have their own regional settings, so changing a site doesn’t change its subsites.
2. Decide the scope. Leave out sites that belong to teams in other time zones, such as an Alberta office.
3. Dry run. Record each site’s address, current time zone and planned change in a CSV file before you change anything.
4. Change in batches and log the result for every site.
5. Check. Open a few sites with more than one account and confirm the times look right.
6. Keep the way back. The CSV with the original time zones is your rollback.

SharePoint Server is different. Microsoft says the correct time zones may not be available in SharePoint Server on November 1 and plans an update for November 10, 2026.

OneDrive

Microsoft’s product guidance doesn’t list a OneDrive issue. Check the modified times on a few B.C. users’ files as part of your testing anyway.

Power Automate: check schedules and conversions

Microsoft confirms that flows using the US-linked time zones (Pacific, Mountain, Central) drift by one hour from November 1, 2026. That covers both cloud flows and Power Automate Desktop (Microsoft’s product guidance).

Check recurrence and schedule triggers, Convert time zone actions, and time zone expressions, starting with flows that send reminders, start approvals or meet deadlines. Power Automate doesn’t support the new province time zones yet, and Microsoft says not to use Alberta, B.C. or Manitoba Standard Time in flows until it does. Use these temporary mappings instead:

Province	Temporary mapping in Power Automate
British Columbia	Yukon Standard Time; Arizona for recurrence and schedule triggers
Alberta	Canada Central Standard Time (Saskatchewan)
Manitoba	SA Pacific Standard Time (Bogota)

The B.C. mappings aren’t interchangeable: use Arizona in triggers and Yukon in conversions. Record every flow you change, so you can move it to the new time zone once Power Automate supports it. Microsoft’s Message Center post MC1526712 has the Power Platform details. For how time zones work in flows, see Convert a time zone in Power Automate.

Bookings and Shifts

• Bookings: an error message could appear even when the booking was created. Microsoft’s fix finishes rolling out on November 4, 2026. If a customer reports an error, check whether the booking exists before asking them to book again.
• Shifts: Microsoft recommends testing schedules. Check a few shifts that cross the change.

What I’d do this week

1. Today: tell staff to update Windows and to use the new time zone in Windows and Outlook. Tell them who to contact if a meeting or a time looks an hour off.
2. First business day: organizers check meetings on or after November 1, starting with recurring series and meetings with US attendees.
3. This week: test one PC, one meeting room, one SharePoint site and one scheduled flow. Then roll the changes out.
4. Before changing SharePoint sites in bulk: export the current time zones, agree on the scope and test the rollback.
5. When Microsoft’s updates land: move PCs off Yukon and flows off the temporary mappings, and test again.

Frequently asked questions

Does B.C. stay on UTC-7 after November 1, 2026?

Yes, most of it. B.C.’s Pacific time is UTC-7 all year. Parts of the northeast were already on UTC-7 all year, and the East Kootenay and Golden area stays aligned with Alberta.

Which Windows time zone should PCs in B.C. use?

(UTC-07:00) Pacific Time (British Columbia), from the September and October 2026 Windows updates. Until a PC has the update, Microsoft’s temporary choice is (UTC-07:00) Yukon.

Do I need to change every SharePoint site?

Not necessarily. Find the sites on Pacific Time (US & Canada), then decide which time zone each one should follow, based on who uses it and what it’s for. Sites that should show B.C. time move to Pacific Time (British Columbia); a site run by an Alberta team may need Alberta’s zone. Check personal settings, make an inventory, and test before you change sites in bulk.

Does changing a site’s time zone change the data?

It changes how dates and times are shown; it doesn’t rewrite the stored values. SharePoint generally stores dates and times in UTC and converts them for display, but date-only columns and integrations can behave differently. Test date-only columns, custom views, flows and reports on a test site before you change many sites.

Why do recurring Outlook meetings need extra care?

Changing the time zone of a recurring series resets its exceptions, so any meeting that was moved goes back to its original time. Only the organizer can make the change, and attendees get an updated invitation.

Sources

Checked November 1, 2026:

• Government of B.C., B.C. adopting permanent daylight saving time
• Microsoft, Canada 2026 time zone changes: guidance for Microsoft products (KB 5134344, updated October 30, 2026)
• Microsoft, Outlook time zone changes for British Columbia, Alberta, and Manitoba
• Microsoft, Interim guidance for British Columbia time zone changes 2026
• Microsoft, Change regional settings for a site
• Microsoft, Change your personal language and region settings
• Microsoft Learn, Best practices for changing site creation time zone display in SharePoint admin center
• PnP, Set SharePoint regional settings
• Microsoft Learn, Convert a time zone in Power Automate