Power Automate and Power Pages: Canada Time-Zone Fixes for November 1, 2026
Calendars are only part of Canada’s November 1, 2026 time change for Microsoft customers. Scheduled desktop flows, Dataverse date filters, model-driven apps and room displays can all run one hour off. Here is what Microsoft has published, what is confirmed and what is still being tested.
Status, October 29, 2026: Microsoft’s support page was last updated October 27. Most Power Platform effects are still listed as under validation, and the Power Automate Desktop trigger fix is not due until November 5 to 23. Treat the temporary settings below as stop-gaps and recheck Microsoft’s pages before changing production flows.
Install the October 2026 Windows time-zone update on every machine that runs desktop flows. For Power Automate Desktop scheduled triggers, Microsoft’s temporary settings are Arizona for British Columbia, Saskatchewan for Alberta and Bogota, Lima, Quito for Manitoba. Test Power Pages date filters from November 1.
These rules cover British Columbia (UTC−07:00), Alberta (UTC−06:00) and Manitoba (UTC−05:00). Microsoft says the affected Northwest Territories locations follow Alberta, and northwestern Ontario follows Manitoba.
Check your exposure
Which fix applies to you?
Pick the region your users or machines are in and the Microsoft product you run.
Power Automate Desktop: temporary time-zone settings
Beginning November 1, scheduled triggers that use the existing Mountain, Pacific or Central zones may run one hour off the intended local time in affected regions. The Get current date and time action also has limits while the new zones and updated time-zone data are unavailable.
Until the new regional zones appear in the scheduled-trigger selector, Microsoft’s interim settings are:
| Region | Select in the scheduled trigger | Offset it gives |
|---|---|---|
| British Columbia | Arizona | UTC−07:00 |
| Alberta | Saskatchewan | UTC−06:00 |
| Manitoba | Bogota, Lima, Quito | UTC−05:00 |
Each substitute is a zone that already keeps one offset all year, which is why it matches the new rule. Apply it only to the affected scheduled triggers. Do not change the time zone of users or computers. Microsoft has not published a temporary setting for the Northwest Territories or northwestern Ontario, so check the Message Center before improvising one.
Where this comes from: the three settings appear in Microsoft’s Power Platform Message Center post MC1526712, published October 27, 2026. The main Microsoft Support page links to Outlook and regional guidance but does not repeat them. The link below is a third-party archive of that post, so confirm it in your own Microsoft 365 admin center.
Windows zone IDs behind those names
If you edit a flow definition or script instead of using the picker, the usual Windows IDs for the three substitute zones are below. These are standard Windows naming, not an extra Microsoft instruction, so test before you rely on them.
| Display name | Windows ID | Use only for |
|---|---|---|
| (UTC−07:00) Arizona | US Mountain Standard Time | British Columbia stop-gap |
| (UTC−06:00) Saskatchewan | Canada Central Standard Time | Alberta stop-gap |
| (UTC−05:00) Bogota, Lima, Quito | SA Pacific Standard Time | Manitoba stop-gap |
Power Pages and Dataverse: dates may be one hour behind
From November 1 through December 31, 2026, dates converted by Dataverse and date-based filters in Power Pages may be one hour behind. From 2027, dates and times recorded during past standard-time periods may also display one hour wrong. Dates rendered directly in the browser are not affected by the identified issue.
A simple way to test, suggested by us and not by Microsoft: pick a record with a known 9:00 AM local time, then compare how the page shows it, how a Dataverse-converted value shows it and whether a date filter includes or excludes it. Do not edit stored dates by hand unless Microsoft’s guidance for your exact case says to.
Microsoft product status board
| Product | Microsoft status | What to do |
|---|---|---|
| Outlook and Exchange Online (calendar) | Confirmed impact | Pick the new zone, review meetings after November 1, plan the Exchange cmdlet for non-recurring meetings. |
| Microsoft Teams Rooms on Windows | Confirmed impact, mitigation available | Update Edge and WebView2, then check the display against Windows. |
| SharePoint On-Prem | Confirmed impact | Correct zones may be missing on November 1. Update due November 10, 2026. |
| Power Automate Desktop (RPA) | Under validation | Install the Windows update, use the temporary settings, retest after November 5 to 23. |
| Power Pages | Under validation | Test Dataverse-converted dates and date filters. |
| Power Apps (model-driven) | Under validation | After the service update, pick the new regional zone. Existing dates can display differently. |
| Dynamics 365 Finance and Operations | Under validation | Users may see wrong local times until they select the new regional zone. |
| Teams clients, Outlook for iOS, Android and Mac, Bookings, Shifts, OneDrive | Under validation | Keep apps updated and check items scheduled after November 1. |
| SharePoint Online, Dynamics 365 Sales, Customer Service, Customer Insights, Contact Center, Business Central | Impact mitigated | Configuration updates were scheduled for late October. Users may still need to pick the new zone. |
| Power Apps (canvas), Power Automate Process Mining, Azure, Teams Graph | No impact anticipated | Behavior depends on the device, so keep devices updated. |
Timeline of dates that matter
- October 28, 2026Target date for the Exchange Online PowerShell cmdlet for non-recurring meetings. Confirm it is available in your tenant.
- October 29, 2026SharePoint Online configuration update due in the Canada region.
- October 31, 2026Manitoba’s Official Time Act change comes into force.
- November 1, 2026BC, Alberta, Manitoba and the aligned regions do not turn clocks back. Power Pages date window begins.
- November 5 to 23, 2026Planned rollout of Power Automate Desktop scheduled-trigger updates.
- November 10, 2026SharePoint On-Prem update due.
- December 31, 2026End of the stated Power Pages window. Past-date display issues may continue from 2027.
Admin checklist before November 1
0 of 8 done
Power Platform Canada time zone: FAQs
Does Power Automate cloud flow need the same fix?
Microsoft’s published notice names Power Automate Desktop scheduled triggers, not cloud flows. Check each cloud flow that uses Mountain, Pacific or Central time and test its next run. Wait for Microsoft’s guidance before changing production schedules.
Which zone do I pick for Alberta in Power Automate Desktop?
Microsoft’s temporary setting for Alberta is Saskatchewan. It keeps UTC−06:00 all year, which matches Alberta’s new rule.
Which zone do I pick for British Columbia?
Arizona, which keeps UTC−07:00 all year. For calendar settings in Outlook, follow the separate Outlook guidance instead.
Which zone do I pick for Manitoba?
Bogota, Lima, Quito, which is UTC−05:00 all year.
What about the Northwest Territories and northwestern Ontario?
Microsoft says the affected Northwest Territories locations align with Alberta and northwestern Ontario aligns with Manitoba. It has not published matching temporary settings for them, so confirm in the Message Center before choosing one.
Will Power Pages dates stay one hour behind forever?
Microsoft’s stated window for the current-date issue is November 1 to December 31, 2026. It also says dates recorded in past standard-time periods may display one hour wrong from 2027. Microsoft is still validating this, so recheck its page.
Do I need to change my users’ computer time zones?
No. Install the Windows update and use the correct local time zone. The temporary Power Automate Desktop settings apply only to the affected scheduled triggers.
Sources: Microsoft Support: Canada 2026 time zone changes, guidance for Microsoft products (KB 5134344) and Message Center archive of MC1526712, Power Platform time zone changes in Canada (third-party copy of a Microsoft post).
Calendar fixes: Outlook time zone changes for BC, Alberta and Manitoba and Google Calendar fix for Canadian clock changes.
More on this site: Canada clock change guide, Alberta and Manitoba time change and Outlook for Mac British Columbia (UTC−08:00).
Checked October 29, 2026. Microsoft updates these pages as product teams confirm impact, so verify before relying on a workaround.
