Dynamics 365 apps and Dataverse are being updated to add the new Canadian time zone definitions in support of the 2026 time zone changes in Manitoba, Alberta, and British Columbia. This is a general awareness message to support the changes and complements MC1510951 — Windows updates are available for 2026 time zone changes in Canada . Rollout schedule The Dataverse update is being deployed through the regular release schedule and is scheduled to reach the Canada region by October 31, 2026. How does this affect me? The new time zones will become available across Dynamics 365 apps and within the Dataverse service. What action do I need to take? After the Dataverse update is available, affected users must select the appropriate new region-specific time zone. The update does not automatically change their existing selection. Review the application-specific guidance below and validate business processes that depend on local times in the affected regions. Dynamics 365 Field Service : Impact: Schedule Board may display times that are incorrect by one hour. Some mobile scenarios may also display incorrect dates or times when the new Canadian time zones are selected. The new time zones may also appear at the bottom of the time-zone lists in Bookable Resource and working hours forms rather than in their expected positions. Action: If not already applied, install the available Field Service app update through Power Platform admin center to address the Schedule Board issue. Mobile fixes remain in progress, with published workarounds available. For affected scenarios, follow the applicable Known Issue instructions to temporarily select an alternative time zone with the same UTC offset. Review the following Known Issues for details and workarounds: Schedule Board may display incorrect times for Western Canadian regions starting November 1, 2026 Newly added Western Canadian time zones not correctly sorted in Bookable Resource time zone dropdown Newly added Western Canadian time zones are not correctly positioned in working hours form NativeExperience syncs wrong time zone QuickNote displays incorrect timestamp with new Canadian time zones
On December 11, 2026, the Proactive control rename feature for canvas apps in Power Apps will be no longer available. How does this affect me? After December 11, 2026, makers and tenant administrators will no longer have access to Copilot (AI-powered assistant) suggestions for renaming similar controls or applying multiple suggested renames in canvas apps. Existing app control names and formulas will remain unchanged. Once this feature is retired: Copilot (AI-powered assistant) will no longer suggest names for similar controls or offer to apply multiple suggested renames when a supported control is manually renamed. This change is enforced and cannot be opted out. Existing app control names and formulas will not be affected. What action do I need to take? There is no action required by makers. Tenant administrators should inform makers about this retirement.
Starting on December 11, 2026, the Use Copilot to create and edit Power Fx formulas and Power Apps Ideas formula assistance features in Power Apps will be no longer available. How does this affect me? The affected features will no longer be available to makers who use them to generate or transform Power Fx formulas after December 11, 2026. This will not impact existing formulas in published apps. What action do I need to take? There is no action required by makers. Tenant administrators should inform makers about this retirement.
Microsoft Entra passkeys on Windows will be generally available from late April 2026, enabling passwordless, phishing-resistant sign-in on Windows devices without requiring explicit admin allow-listing. It supports corporate, personal, and shared devices, with control via Authentication Methods policies and Conditional Access. No action is needed unless blocking is desired.
Starting March 2026, Microsoft Entra ID will GA passkey profiles and synced passkeys for tenants with Passkeys (FIDO2) enabled. Existing tenants will be auto-migrated to a default passkey profile with configurable passkeyType. Registration campaign settings and rollout timelines vary by cloud region.
Starting November 30, 2026, the Translate slides feature in PowerPoint Live during Microsoft Teams meetings will be retired worldwide. Attendees will no longer translate slides; slides will display in their original language. No admin action is needed, but organizations should notify users and update related training materials.
Granular Conditional Access for Teams meetings lets admins enforce targeted security controls like multifactor authentication for specific meetings. Rolling out from November 2026 (preview) to January 2027 (general availability), admins must configure authentication contexts, Conditional Access policies, and Teams meeting policies to enable this feature.
Microsoft Teams is replacing the Copilot meeting policy with two new policies—MeetingAI and TranscriptionWithMeetingAI—for clearer control over AI features and transcription in meetings. Organizers gain granular AI management options. Rollout begins mid-November 2026, with automatic migration of existing settings; no admin action required unless using automation.
The 'Activity in Other Accounts and Orgs' panel in Teams will allow users to preview and open chats and channels from multiple accounts without tenant switching. Rolling out from November 2026 to February 2027, it enhances external collaboration with no security or compliance changes. No admin action required.
Microsoft Teams will add pinch-to-zoom on shared screens using touchpads, enhancing visibility of small text and details. This feature rolls out worldwide in mid to late November 2026, enabled by default in all meetings. Organizations should update sharing policies and inform users; no compliance issues identified.
Microsoft Defender XDR's CallActivityEvents table enables security teams with Defender for Office 365 Plan 2 to investigate suspicious Microsoft Teams calls and meetings by analyzing activities, initiators, organizers, and related messages. Available worldwide from November 2026, it integrates with advanced hunting, event streaming API, and Microsoft Sentinel for enhanced threat detection.
On November 30, 2026, record-level copresence in model-driven apps will have reached end of support. How does this affect me? Users will no longer see who else is working on the record or have access to a presence card. This change does not affect record sharing, user pictures, or status in grids and lookups. The underlying behavior when multiple users edit the same record hasn't changed: if two users save changes to the same record, the most recent save still overwrites any previous changes. What's changing is visibility — without copresence, users won't see that someone else may be viewing or editing the record at the same time. What action do I need to take? Admins should inform their users that copresence in model-driven apps will no longer be available after November 30, 2026. Users can continue to reach other users they collaborate with directly using existing entry points in the app, or through supporting apps like Outlook and Teams.
Dynamics 365 Apps
Microsoft Dataverse
