Skip to content

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

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

Billy Peralta

, updated Microsoft documentation checked 17 min read

A wooden wall clock above a white desk with a potted plant and a desk lamp

Samantha Gades on Unsplash

Topics: Microsoft 365, SharePoint Online, Outlook, Power Automate, Microsoft Teams, Windows

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.

Updated November 13, 2026: Microsoft has documented the Exchange Online cmdlet that moves existing calendar events to the new time zone, including recurring meetings. See the Outlook section for what it does and doesn’t cover.

Updated November 6, 2026: I corrected my earlier statement that Microsoft’s SharePoint Online update doesn’t change the time zone of existing sites. Older sites in my tenant were already on the new B.C. zone even though I never ran a bulk change, and Microsoft’s documentation doesn’t explain why. Check your own sites before you change anything. I also published a separately developed, open-source PowerShell tool for auditing and updating SharePoint site time zones.

Updated November 3, 2026: Microsoft updated its guidance on November 2. It says Windows and Bookings updates have been released, and it added Shifts, Teams Events and Azure Automation to its list of affected products. They’re covered below, along with Fabric, Power Pages and Dynamics 365 Finance and Operations. The Exchange cmdlet for fixing meetings still has a target date of November 4.

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 existing and newly created sites. Sites still on Pacific Time (US and Canada) can show times an hour behind B.C. time, depending on personal settings.
  • 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.

Updated November 13, 2026: the calendar migration cmdlet

Microsoft has now documented the Exchange Online cmdlet for this, Invoke-CalendarEventMigration (Microsoft Learn). It moves existing meetings and appointments in one mailbox from one time zone to another while keeping the same local time, for example 9 AM Pacific Standard Time to 9 AM British Columbia Standard Time. Microsoft says it also handles recurring meetings, including exceptions to the series.

What to know before you use it:

  • It only moves meetings that mailbox organizes. Meetings where the person is an attendee have to be moved by the organizer.
  • It only covers the default calendar. Events in secondary calendars aren’t moved.
  • Attendees get a meeting update for every migrated meeting. Those messages count toward Exchange Online sending limits, so Microsoft recommends batches and a small date window to start.
  • Changing the mailbox time zone, moving existing events and changing the working hours time zone are separate steps. The cmdlet only moves events. The mailbox time zone is set with Set-MailboxRegionalConfiguration and the working hours time zone with Set-MailboxCalendarConfiguration.

Microsoft’s Outlook guidance points admins to Message Center post MC1521581 for automating the migration. It doesn’t appear in my own tenant’s Message Center, so I can’t confirm its rollout dates. Check your tenant’s Exchange Online PowerShell session to confirm the cmdlet is available. Use -PreviewOnly with a small date window to inspect the meetings that would be migrated, including recurring series and exceptions. Validate the results on a few test mailboxes before working through the rest in batches. If MC1521581 is available in your Message Center, review it for the latest rollout guidance.

Microsoft’s product guidance page still says the cmdlet had a target date of November 4, 2026 and that recurring-meeting support was in development (Canada 2026 time zone changes: guidance for Microsoft products). The cmdlet documentation above is the newer source.

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.
  • Teams Events: the correct time zones may not be available yet. Until they are, Microsoft’s temporary choices for organizers are (UTC-07:00) Yukon for B.C., (UTC-06:00) Saskatchewan for Alberta and (UTC-05:00) Eastern Time (US & Canada) for Manitoba.
  • Other Teams devices: possible issues with the time display and scheduling. Keep device software current and check the displayed time after updates.

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, but Microsoft doesn’t explain whether it changes the time zone of existing sites.

When I checked my own tenant on November 6, 184 older sites and subsites that I could read were already on (UTC-07:00) Pacific Time (British Columbia), although I had never run a bulk time zone change there. Of the three sites created since October 30, two were on Pacific Time (US and Canada) and one was on UTC. One locked older site was still on the old zone, and I couldn’t read about 40 others.

That’s one tenant, not proof that Microsoft moved existing sites everywhere. List your own sites’ time zones rather than assume they did or didn’t move.

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. In my tenant, two of the three sites created since October 30 were on Pacific Time (US and Canada), and the third was on UTC.

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.

I’ve since built a separate, free, open-source PowerShell tool: the SharePoint Online Site Time Zone Updater. It’s a fresh implementation of the same inventory-first approach, not the script I used for that organization.

It checks site and subsite time zones, runs as a dry run by default, and records results and failures in a CSV log. After an -Apply run, it can restore the original time zones from that run’s log. The README explains what has and hasn’t been tested, so review it and start with one test site.

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: Microsoft lists this as mitigated: updates have been released that add the new time zone options for new Bookings. Its wording covers new Bookings, so test an appointment on an existing booking page too.
  • Shifts: added to Microsoft’s list on November 2 as a possible issue, still under validation, with how Shifts handles the new time zones. Microsoft points admins to Message Center post MC1532245. Check a few schedules that cross the change.

Other Microsoft services to check if you use them

These are outside the main checklist, but Microsoft lists them too (Microsoft’s product guidance):

Product Status What to do
Azure Automation Confirmed: a one-hour drift on US-linked time zones. No date for the update yet. Use the same temporary mappings as Power Automate.
Fabric and Power BI service Confirmed: the new time zones aren’t available yet. No date for the update. Until they are, use (UTC-07:00) Arizona for most of B.C., (UTC-06:00) Saskatchewan for Alberta and (UTC-05:00) Bogota, Lima, Quito for Manitoba.
Power Pages Server-formatted dates can appear an hour off, including Liquid output, relative-date filters and Excel exports. A service fix is in progress, with a December 12 milestone. Test the affected pages, and apply the fix once it’s available.
Dynamics 365 Finance and Operations apps Confirmed: incorrect local times unless hotfixes are installed. Check for hotfixes in Lifecycle Services (LCS) or the Power Platform admin center. Apply the update when it’s available, select the new province time zone, and check local times.

Microsoft lists “No impact anticipated” for Power Apps canvas apps and model-driven apps. If users report wrong dates or times, still check their device’s time zone and test the app.

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. Some may already be on the new zone, so start by finding the ones 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 3, 2026:

Need a second set of eyes on Microsoft 365 changes?

I work with internal IT teams across Canada to assess SharePoint and Microsoft 365 changes, troubleshoot tricky configuration issues, and plan practical solutions. That can mean a focused review or a defined project.

16+ years experience Microsoft certified Government & enterprise

Free SharePoint planning resource

Planning a SharePoint migration or governance cleanup?

Download the SharePoint Migration & Governance Readiness Checklist to review migration scope, permissions, governance, Teams/OneDrive strategy, retention, and Copilot readiness.

Download the Checklist

Billy Peralta

SharePoint architect & Microsoft 365 consultant • 16+ years of experience

If you have questions about your SharePoint environment, feel free to reach out.

LinkedIn GitHub

Billy Peralta originally posted this article on 1 November 2026 at 8:00 AM.

Leave a Reply