Microsoft Roadmap, messagecenter and blogs updates from 03-04-2026

Updated April 2, 2026: We have updated the timeline. Thank you for your patience. 

We’re introducing federated Copilot connectors in Microsoft 365 Copilot, enabling users to securely connect external apps such as Notion, Canva, or Hubspot directly within Copilot experiences like Researcher. Unlike traditional indexed connectors, federated connectors use the Model Context Protocol (MCP) to access data in real time. This allows users to fetch and read information from connected sources using their own credentials, while maintaining admin-level visibility, control, and governance in the Microsoft 365 admin center.

This feature will be available on the web platform.

A Microsoft 365 Copilot license is required to use this feature.

This message is associated with Microsoft 365 Roadmap ID 501585.

Public Preview: Rollout will begin February 9, 2026 (previously January 12).

Targeted Release: Rollout began mid-February 2026 and completed end of March 2026. 

• Who is affected: All tenants using Microsoft 365 Copilot with access to the Microsoft 365 admin center.
• What will happen:
  • End users will be able to connect to Microsoft-published federated connectors (such as Canva, HubSpot, Linear, Intercom, Google calendar, Google contacts, Notion) directly within Copilot experiences to search or fetch live data.
  • Admins will have visibility and control from the Copilot > Connectors section, where they can
    • View all default Federated copilot connectors enabled by Microsoft.
    • Disable any connectors that are not relevant or compliant for their organization.
    • Use staged rollout to enable these connectors for a limited group of users
  • Admin can also create and manage custom MCP based federated copilot connectors for internal or specialized data sources using an MCP endpoint.

Screenshot 1 – Admin experience:

Screenshot 2 – User experience:

When a Microsoft-published federated Copilot connector first appears in the Microsoft 365 admin center (Copilot > Connectors> Your connections), it will remain admin-only for 7 days before it can be used by end users.

During this seven-day review window, admins can:

• Review newly available federated connectors
• Disable connectors that are not relevant or compliant for their organization
• Use staged rollout to limit availability to specific Entra ID groups
• Any connector disabled during this window will not be rolled out to end users.

Additional steps:

• Review the list of default connectors that will appear in your tenant under Copilot > Connectors > Your Connections. List includes: Canva, HubSpot, Linear, Intercom, Google calendar, Google contacts, Notion and more. You can find them with type ‘MCP’
• Ensure all available connectors align with your organization’s data and compliance policies. Disable any that do not meet requirements directly from the admin center.
• For custom connectors, configure your MCP endpoints with the required tools (search and fetch) and proper authentication (OAuth2).
• Communicate this change to helpdesk staff and update internal documentation as needed.

Updated April 2, 2026: We have updated the content. Thank you for your patience. 

[Introduction]

Beginning in mid‑March 2026, Microsoft Planner will update the agent experience to align naming with Microsoft 365 Copilot and expand availability. As part of this update, the Project Manager agent will be renamed to Planner Agent, the Planner Agent icon will be changed to match the Planner icon, and the agent will become available to users with a Microsoft 365 Copilot license in group-based Planner premium and Planner basic plans.

This update aligns Planner’s agent experience with Microsoft 365 Copilot and expands access to Copilot-powered capabilities.

This message is associated with Microsoft 365 Roadmap ID 511820.

[When this will happen]

• Targeted Release: Rollout will begin in early to mid-March 2026 and is expected to complete between mid- and late March 2026. 
• General Availability (Worldwide): Rollout will begin in mid‑March 2026 and is expected to complete by early May 2026.
• Availability to group-based basic plans: Planner agent will begin rolling out to group-based Planner basic plans starting in mid‑March 2026.

[How this affects your organization]

Who is affected

• Users with a Microsoft 365 Copilot license
• Organizations using group-based Planner premium or Planner basic plans
• Users who previously used the Project Manager agent

What will happen

• The Project Manager agent will be renamed to Planner Agent across Planner interfaces and documentation.
  • There are no functional or behavioral changes associated with this rename.
• Planner Agent will be available to Microsoft 365 Copilot–licensed users in both group-based premium and group-based basic plans.
• Planner Agent will remain enabled by default for licensed users where it is available.
• Existing users will continue to have access to all current capabilities. No action is required.
• The Planner agent provides:
  • Status reporting: Automated creation and management of status reports based on plan data.
  • Task execution: First‑draft task output generation, progress tracking, and iterative refinement.

[What you can do to prepare]

No admin action is required. These updates will roll out automatically.

Admins may optionally:

• Notify users and helpdesk staff about the rename from Project Manager agent to Planner Agent.
• Update internal documentation that references the previous agent name.
• If you want to receive changes earlier, configure Targeted Release for your organization: Set up the Standard or Targeted release options | Microsoft 365 | Microsoft Learn

Learn more: Use Microsoft Purview to manage data security & compliance for Microsoft 365 Copilot & Microsoft 365 Copilot Chat | Microsoft Learn

[Compliance considerations]

Updated April 1, 2026: We have updated the content. Thank you for your patience. 

[Introduction]

We’re improving the formatting of the Authentication Methods Policy Update and Authentication Methods Policy Reset audit log entries in Microsoft Entra ID. Previously, these audit logs included the full authentication methods policy payload under Modified properties, even when only a small number of settings were updated.

With this update, the audit log will now display only the specific properties that changed, along with their corresponding old and new values. The audit log activity name and when it is triggered will not change. This update only changes how modified properties are displayed.

[When this will happen]

• General Availability (Worldwide): Rollout begins early April 2026 and is expected to complete by late April 2026.
• General Availability (GCC, GCCH, DoD): Rollout begins late April 2026 and is expected to complete by late May 2026.

[How this affects your organization]

Who is affected:

• Organizations that use Microsoft Entra ID audit logs, particularly administrators and security teams who review or process Authentication Methods Policy Update or Authentication Methods Policy Reset events.
• This may also affect organizations that rely on audit log modified properties for automated processing, alerting, or custom parsing.

What will happen:

• This update makes audit logs easier to read and interpret by reducing noise and highlighting exactly what was modified during an authentication methods policy update.
• The audit log activity name, event timing, and policy behavior remain unchanged.
• No new audit events are introduced, and existing policy enforcement is not affected.

[What you can do to prepare]

• No action is required for most organizations.
• If you use audit logs for automated processing, alerting, or custom parsing, review any logic that expects the full authentication methods policy payload in Authentication Methods Policy Update or Authentication Methods Policy Reset events’ modified properties.
• After this change, audit log entries for authentication method setting changes will surface only the specific properties that were modified, rather than the entire policy object.
• Policy-wide updates, such as Registration Campaigns and System-preferred MFA, may continue to include the full policy payload. 

Learn more: Microsoft Entra audit log activity reference – Microsoft Entra ID | Microsoft Learn

[Compliance considerations]

No compliance considerations identified, review as appropriate for your organization.

Updated April 2, 2026: We have updated the content. Thank you for your patience. 

[Introduction]

We’re updating the Viva Connections experience in the Microsoft Teams mobile app to provide a more modern, streamlined navigation that is easier to use across all devices. This update simplifies how users move between sections and improves discoverability, while keeping all existing functionality intact.

[When this will happen:]

• General Availability (Worldwide): Rollout begins in early April 2026 and is expected to complete by late April 2026.

[How this affects your organization:]

Who is affected:

• All users who access Viva Connections in the Microsoft Teams mobile app (iOS and Android).

What will happen:

• The Teams mobile Viva Connections experience will move from a three-tab layout (Dashboard, News, Resources) to a pill-based navigation model.
• Users will switch between Viva Connections sections using pill-shaped navigation controls at the top of the experience:
  
• In the News experience:
  • The Unread and Saved for later pills will be replaced with:
    • An Unread toggle
    • A Saved for later button
• There is no change to functionality or content—only the navigation and layout are updated.
• The update is enabled by default and applies automatically.

Before:

After:

[What you can do to prepare:]

• No action is required to enable this update.
• Optionally, inform helpdesk staff and update internal documentation that references the previous navigation.

[Compliance considerations:]

No compliance considerations identified, review as appropriate for your organization.

[Introduction]

Microsoft 365 Copilot (Premium) in PowerPoint now allows users to choose which AI model to use when creating or editing presentations, providing additional flexibility while maintaining existing security, compliance, and admin controls.

This message is associated with Microsoft 365 Roadmap ID 558443.

[When this will happen:]

General Availability (Worldwide): Rollout begins early April 2026 and is expected to complete by early May 2026.

[How this affects your organization:]

Who is affected:

• Microsoft 365 Copilot (Premium)–licensed users using Copilot in PowerPoint.
• Microsoft 365 administrators.

What will happen:

• Users can select which AI model to use when creating or editing slides in Copilot for PowerPoint.
• To switch models, open the Copilot pane and use the dropdown menu in the top-right corner to select a model. The default selection is Auto.



• Available models include OpenAI models and Anthropic’s Claude model.
• The feature is enabled by default.
• Existing Microsoft 365 Copilot security and compliance controls continue to apply.

[What you can do to prepare:]

• No action is required if you want this feature enabled.
• Consider notifying helpdesk or compliance teams that users may see a new model selection option in PowerPoint Copilot.
• Admins can disable Anthropic as a subprocessor in the Microsoft 365 admin center. Learn more: Anthropic as a subprocessor for Microsoft Online Services | Microsoft Learn.

[Compliance considerations:]

[Introduction]

Today, Endpoint Data Loss Prevention (DLP) can only protect content after it’s saved to disk. Based on customer feedback and ongoing security investments, we’re introducing the ability to detect and block egress activities on unsaved files. This enhancement helps organizations prevent data leakage earlier in the workflow by applying DLP protection before content is written to the device.

This message is associated with Microsoft 365 Roadmap ID 511791.

[When this will happen]

General Availability (Worldwide): We will begin rolling out this feature in early April 2026 and expect to complete by mid‑April 2026.

[How this affects your organization]

Who is affected

• Organizations using Endpoint DLP in the Microsoft Purview compliance portal
• Admins who configure or manage Endpoint DLP policies
• Users on devices running anti‑malware Client version 4.18.26020 or later

What will happen

• New policy controls will be available that allow admins to detect or block egress activities involving unsaved files.
• When enabled:
  • Audit print and transfer activities for unsaved files: Endpoint DLP will log egress actions involving unsaved files.
  • Block print and transfer activities for unsaved files: Endpoint DLP will block egress actions involving unsaved files.
• Policy evaluation will begin earlier in the process, before a file is saved to disk.
• This feature is off by default and requires admin configuration to take effect.
• Existing policies continue to function with no changes unless these new settings are configured.

[What you can do to prepare]

• Ensure devices in scope are running anti‑malware Client version 4.18.26020 or later.
• Review your existing Endpoint DLP policies and determine whether to enable the new unsaved‑file controls.
• Update internal documentation or helpdesk materials that describe DLP behavior.
• Communicate these upcoming policy options to your security and compliance teams.

[Compliance considerations]

No compliance considerations identified. Review as appropriate for your organization.

[Introduction]

We’re updating attachment actions in Outlook for iOS by adding new actions and renaming existing ones. These changes improve consistency across attachment experiences in the reading pane and compose scenarios and introduce additional options for previewing and sharing attachments.

[When this will happen:]

• General Availability (Worldwide): Rollout begins late April 2026 and is expected to complete by mid‑May 2026.

[How this affects your organization:]

Who is affected:

• All users using Outlook for iOS.

What will happen:

• New attachment actions in the reading pane:
  • Preview – Preview attachments directly from the reading experience.
  • Send a copy – Send an attachment as a copy directly from the reading experience.
• Attachment action names are updated:
  • Save to device → Share
  • Insert link → Send a link
  • Attach a copy → Send a copy
• Renamed actions apply across reading pane, compose, and file-related scenarios.
• The feature is enabled by default.

[What you can do to prepare:]

• No action is required.
• You may notify users or update internal documentation.

[Compliance considerations:]

No compliance considerations identified, review as appropriate for your organization.

[Introduction]

To provide a more consistent and predictable file viewing experience, we’re updating the user interface for text and image file previewers in Outlook for Android. These changes align text and image previewers with the existing preview experience for Word, Excel, and PowerPoint files.

[When this will happen:]

• General Availability (Worldwide): Rollout begins late April 2026 and completes by mid-May 2026

[How this affects your organization:]

Who is affected:

• All users viewing text and image file attachments in Outlook for Android

What will happen:

• Users will see updated styling in text and image file previewers to match other Office file previewers.
• The overflow action menu will:
  • Display updated icons
  • Use a revised action order consistent with Word, Excel, and PowerPoint previewers
• A new Expand button will appear in the action bar, making it easier to enter full-screen mode.
• The feature is enabled by default and does not change existing policies or workflows.

[What you can do to prepare:]

• No action is required; the update is enabled automatically
• Optionally notify users and helpdesk staff of the UI refresh
• Update internal documentation or screenshots if applicable

[Compliance considerations:]

No compliance considerations identified, review as appropriate for your organization.

[Introduction]

Microsoft Loop will retire the Copilot‑generated Recap option. This change simplifies the Recap experience by focusing on manual creation and editing, while allowing Microsoft to continue investing in other Copilot capabilities across Microsoft 365. The retirement applies only to Copilot‑generated Recaps and does not affect other Copilot features in Microsoft Loop.

[When this will happen]

General Availability (Worldwide): The retirement will begin in early May 2026 and is expected to be completed in late May 2026.

[How this affects your organization]

Who is affected

All Microsoft 365 tenants using Microsoft Loop

What will happen

• The ability to generate Recaps by using Copilot will be removed from the Recap experience in Microsoft Loop.
• Users will no longer be able to generate Recaps using Copilot.
• Users can continue to manually create and edit Recaps.
• This change will be on by default and cannot be configured or reversed by admins.
• Other Copilot features in Microsoft Loop will not be affected.
• No admin configuration or policy changes will be required.
• In Microsoft Loop, the Recap entry point will no longer display the “With AI” label or sparkle icon:

  

•  The Recap experience will remain available for manual creation and editing.

[What you can do to prepare]

No action is required.

Optionally:

• Update internal training or help documentation to remove references to Copilot‑generated Recaps in Microsoft Loop.
• Inform helpdesk staff so they can address potential user questions.

Learn more: Recap changes in Loop with Copilot | Microsoft Support

[Compliance considerations]

[Introduction]

We’re updating AI Interpreter in Microsoft Teams to deliver more accurate and consistent real-time interpretation. These improvements enhance recognition of people’s names and common industry terminology, and Interpreter will now use your organization’s Custom Dictionary from the Microsoft 365 admin center to reflect preferred terms across meetings. This update also expands language availability with the addition of Traditional Chinese.

This message is associated with Microsoft 365 Roadmap ID 558434.

[When this will happen]

• Targeted Release: Rolling out in early April 2026 and expected to complete in mid-April 2026.
• General Availability (Worldwide): Rolling out in mid-April 2026 and expected to complete in late April 2026.

[How this affects your organization]

Who is affected

• Organizations using Microsoft Teams multilingual meetings with Interpreter, live captions, or transcripts, and users licensed for Microsoft 365 Copilot

What will happen

• AI Interpreter accuracy will improve for real-time interpretation.
• Recognition of people’s names and industry-specific terminology will be more consistent.
• Interpreter will use your tenant’s Custom Dictionary from the Microsoft 365 admin center to improve translation consistency.
• Traditional Chinese will be added as a supported language: 

  

• This update applies to all currently supported languages:
  • English
  • Simplified Chinese
  • Traditional Chinese
  • French
  • German
  • Italian
  • Japanese
  • Korean
  • Portuguese
  • Spanish
• The AI Interpreter experience requires a Microsoft 365 Copilot license for users.
• Existing admin policies and configurations are unchanged.
• The feature will be enabled by default for eligible, licensed users.

[What you can do to prepare]

No admin action is required before rollout.

To ensure users can take advantage of this update, you may want to:

• Confirm that users who need AI Interpreter are assigned a Microsoft 365 Copilot license.
• Review and maintain Custom Dictionary entries in the Microsoft 365 admin center.
• Update internal documentation or helpdesk materials if needed.
• Communicate this update to Teams meeting organizers and interpreters who rely on multilingual capabilities.

[Compliance considerations]

No compliance considerations identified. Review as appropriate for your organization.

• Ingest your object-centric event logs from Azure Data Lake or OneLake.
• Map object and event-level attributes to unlock detailed analytical opportunities.
• Visualize your object-centric process in an understandable, customizable, and easy-to-read process map.
• Visualize key metrics in a comprehensive process overview.
• Analyze your process from process execution and throughput time viewpoint.
• Focus on specific process areas by using filters or by specifying a particular path in the Process Analysis widget.

• In April 2026, this enhancement brings green, yellow, and red-color badges to Device security > Secure Boot. 
• In May 2026, notifications will appear outside the app (such as system alerts). 
• In late June 2026, the 2011 Secure Boot certificates begin expiring. Devices need updated 2023 certificates by this date to remain protected and productive. 

• See complete information at IT admin guide: Secure Boot certificate update status in the Windows Security app. 
• If you enable this feature, share this user-focused KB article with them: Secure Boot certificate update status in the Windows Security app. 
• For comprehensive review of Secure Boot certificate updates, visit https://aka.ms/GetSecureBoot.  
• For devices that don’t have these certificates applied, use the specific monitoring and deployment methods described in the Secure Boot playbook. 
• For Windows Server, see Windows Server Secure Boot playbook for certificates expiring in 2026.

• Embedded dialer in Sales Hub: Use a native calling panel across Contacts, Leads, Opportunities, and Accounts to stay in the Sales Hub while handling calls.
• Click to call and manual dialing: Click any phone number to call instantly, search COLA entities, or manually dial using the built in keypad.
• Inbound call handling: Get clear, actionable notifications when calls come in, with customer match and context surfaced right away.
• Automatic call logging: All calls, both inbound and outbound, are saved automatically as phone call activities with duration, direction, and record association.
• Modern calling controls: Use familiar controls like mute, hold, resume, consult, and transfer on a single streamlined surface.
• AI powered conversation intelligence: Get real-time and post-call summaries, transcription, sentiment, action items, and key topics powered by the latest LLMs.
• Call recording and playback: Record calls and review them with speaker separation and jump to insight navigation.

[Introduction]

We’re introducing an improved secure file preview experience for Word, Excel, and PowerPoint files in the OneDrive mobile app for iOS and iPadOS. With this experience, users can preview files directly within the OneDrive app without downloading them to their device or opening them in standalone Microsoft 365 apps. Existing Microsoft 365 security, compliance, and access policies continue to be enforced, helping organizations maintain protection while improving mobile productivity.

[When this will happen:]

General Availability (Worldwide): We will begin rolling out in early April 2026 and expect to complete the rollout by late April 2026.

[How this affects your organization:]

Who is affected:

• All users who access OneDrive files using the OneDrive mobile app on iOS and iPadOS

What will happen:

• Users can preview Word, Excel, and PowerPoint files directly within the OneDrive mobile app.
• Files are previewed securely without being downloaded or stored locally on the device.
• The experience is enabled by default.
• Existing Microsoft 365 security, compliance, sensitivity labels, Conditional Access, and access controls are respected.
• There is no change to file permissions, sharing behavior, or audit logging.

[What you can do to prepare:]

• No action is required.
• Optionally, inform your helpdesk and users about the improved secure preview experience for mobile access.
• Review existing Conditional Access or mobile app protection policies if you have strict mobile access requirements.

Learn more: Apply sensitivity labels to your files | Microsoft Support

[Compliance considerations:]

No compliance considerations identified. Review as appropriate for your organization.

[Introduction]

We’re updating how Microsoft Teams calculates and displays badge counts to make it easier for users to find and clear messages that contribute to their unread count. A badge count is the number displayed on the Teams app and navigation that shows how many unread messages or notifications require user attention. This update introduces clearer visual indicators and simplifies the chat and channels list.

This message is associated with Microsoft 365 Roadmap ID 559612.

[When this will happen:]

• Targeted Release (Worldwide): Rollout will begin in mid-April 2026 and is expected to complete by early May 2026.
• General Availability (Worldwide): Rollout will begin in early May 2026 and is expected to complete by mid-May 2026.

[How this affects your organization:]

Who is affected:

• All users of Microsoft Teams on desktop and mobile.

What will happen:

• Users may notice a change in their overall Teams badge count.
• Users may notice a change in chat badge counts (and Teams badge counts when using split-app mode).
• The new badge count is calculated as the sum of:
  • Unread, unmuted chats
  • Unread personal mentions
  • Unread followed threads
  • Unread tag mentions
• Unread, unmuted chats in the chat list will display a purple dot to indicate they contribute to the badge count.
• In Quick views, Mentions, Followed threads, and Tag mentions will display a purple number showing how many unread items contribute to the badge count.
• Mention charms and Important charms will be removed from the chat and channels list to simplify the experience.
• The feature is enabled by default and does not require admin configuration.

[What you can do to prepare:]

• No admin action is required.
• Consider informing users about how badge counts are calculated to reduce confusion or helpdesk inquiries.
• For followed threads, users can adjust their preferences by going to Settings > Chats and channels and updating Automatically follow threads in channels.
• Update internal training or helpdesk documentation if you reference Teams badge behavior.

[Compliance considerations:]

No compliance considerations identified; review as appropriate for your organization.

[Introduction]

We’re introducing Email summary powered by Security Copilot on the Email Entity page in Microsoft Defender XDR. This AI-driven capability helps security teams quickly understand and respond to email threats by summarizing email detection data into clear, actionable insights. This feature is designed to reduce investigation time and improve analyst efficiency by presenting key signals and analysis in one place.

[When this will happen]

• Public preview: Rollout begins in mid-April 2026 and is expected to complete by late April 2026.
• General availability (Worldwide): Rollout begins in early May 2026 and is expected to complete by mid-May 2026.

[How this affects your organization]

Who is affected

• Security teams and admins using Microsoft Defender XDR
• Microsoft 365 tenants with Security Copilot access and provisioned Security Compute Units (SCUs)

What will happen

• A new Email summary section will appear on the Email entity page in Microsoft Defender XDR: 

  

• Security Copilot will generate AI-driven summaries that include:
  • Email overview: A concise summary of detected threats, actions taken, overrides, and key indicators: 

    

  • Timeline event analysis: A chronological view of actions and outcomes across the email lifecycle: 

    

  • URL analysis: Assessment of URLs extracted from the email to identify known malicious behavior.
  • Attachment analysis: Insights into attachments, highlighting suspicious or harmful files and associated risks.
• This feature requires Security Copilot access and SCUs and is not enabled by default.
• Existing security policies, permissions, and investigation workflows are respected; no policy changes are required.

[What you can do to prepare]

• Ensure Security Copilot Security Compute Units (SCUs) are provisioned in your tenant.
• Verify that intended users have access to Security Copilot.
• Review and update internal investigation workflows or documentation, if applicable.
• Inform security analysts about the new Email summary experience so they can incorporate it into daily investigations.

Learn more:

• Get started with onboarding to Microsoft Security Copilot | Security Copilot | Security | Microsoft Learn
• Learn about Security Copilot for Microsoft 365 E5 included customers | Security Copilot | Security | Microsoft Learn
• Microsoft Security Copilot in Microsoft Defender | Microsoft Defender XDR | Microsoft Learn

[Compliance considerations]

[Introduction]

This message is associated with Roadmap ID 558922.

[When this will happen:]

General Availability (Worldwide): Rollout will begin in mid‑May 2026 and is expected to complete by mid‑May 2026.

[How this affects your organization:]

Who is affected:

• Organizations hosting Microsoft Teams meetings with participants joining via Direct Guest Join from Zoom, Google Meet, or Cisco devices.

What will happen:

• Meetings joined through Direct Guest Join will support up to 16 participant videos in a 4×4 video grid.
• Simulcast streaming will improve video quality and reliability across heterogeneous meeting platforms.
• The enhancement is enabled by default.
• No changes are required to existing Teams policies or meeting workflows.

[What you can do to prepare:]

• No admin action is required.
• Inform users about upcoming improvements to cross‑platform meeting quality.
• Update internal documentation or helpdesk guidance if applicable.

[Compliance considerations:]

[Introduction]

We’re updating the content delivery network (CDN) endpoint used by Microsoft AutoUpdate (MAU) to download updates for Microsoft apps on macOS. This change is part of an infrastructure upgrade to improve the reliability, performance, and security of update delivery by standardizing downloads on Microsoft’s latest CDN endpoint.

[When this will happen:]

• September 2025: MAU version 4.80 is released. MAU defaults to downloading updates from the new CDN endpoint unless configured to use a custom update location.
• Through May 31, 2026: Updates are published to both the legacy and new CDN endpoints.
• June 1, 2026: Updates are published only to the new CDN endpoint.
• August 1, 2026: The legacy CDN endpoint is fully decommissioned.

[How this affects your organization:]

Who is affected:

• Organizations with macOS devices that use Microsoft AutoUpdate (MAU) to receive updates for Microsoft apps.
• Administrators who restrict outbound internet access (for example, firewall rules, proxy rules, or domain allowlists).
• Administrators who override the MAU update location using custom configuration (for example, Custom update channel, ManifestServer, or UpdateCache preferences).

What will happen:

• Starting June 1, 2026, MAU will download updates only from the new CDN endpoint:
  • res.public.onecdn.static.microsoft
• The legacy endpoint
  • officecdnmac.microsoft.com
  • will no longer host newly released update packages after June 1, 2026.
• If access to the new endpoint is blocked, MAU may fail to download updates, which could result in devices remaining on older versions or missing security updates.
• There are no changes to MAU app behavior, update channels, update schedules, or how updates are installed or managed.

[What you can do to prepare:]

• If your organization restricts outbound network access, review firewall, proxy, or allowlist rules to ensure managed Mac devices can access
  • res.public.onecdn.static.microsoft
• Review MAU preferences to confirm they do not reference
  • officecdnmac.microsoft.com
• No action is required if your organization allows outbound internet access and does not configure a custom MAU update location.
• For more information, review MAU preferences documentation: Microsoft AutoUpdate preferences for macOS.

[Compliance considerations:]

No compliance considerations identified, review as appropriate for your organization.

[Introduction]

We’re improving the Viva Glint and Viva Insights integration by introducing a centralized exclusion list in Viva Feature Access Management. This update allows Viva Glint admins to exclude specific users or groups from having their Viva Insights data shared with Viva Glint without having to disable the entire integration. This simplifies configuration and supports consistent, privacy-conscious data-sharing controls.

[When this will happen:]

• General Availability (Worldwide): Rollout begins mid-May 2026 and is expected to complete by late June 2026.

[How this affects your organization:]

Who is affected:

• Tenants using Viva Insights workplace metrics in Viva Glint 
• Viva Glint and Global admins managing Viva Feature Access Management

What will happen:

• If you previously kept the Viva Glint and Viva Insights integration disabled because certain users or groups should not have their Viva Insights metrics shared with Viva Glint, you can now exclude those users or groups and turn on the integration.
• A new setting appears under Viva Glint: “Allow data sharing from Viva Insights.”



• Admins can exclude specific Entra ID users or groups from data sharing.
• Excluded users’ Viva Insights metrics will not be shared with Viva Glint.
• The integration remains unchanged unless admins configure this setting.

[What you can do to prepare:]

• Review whether your organization has users or groups whose Viva Insights data should not be shared with Viva Glint
• No action is required if you want Viva Insights data shared with Viva Glint for all eligible users.
• If you have users or groups whose Viva Insights metrics should not be shared with Viva Glint, you can configure exclusions using the new setting once it becomes available.
• Go to Viva Feature Access Management
• Select Viva Glint
• Open Allow data sharing from Viva Insights
• Choose Off → Specific people and groups



• Add the relevant Entra ID users or groups



• Update internal privacy or data‑sharing documentation if applicable
• Inform HR, analytics, or insights teams of the new control to avoid duplicate or manual workarounds

Learn more: Export Viva Insights data to Viva Glint | Microsoft Learn (will be updated before rollout)

[Compliance considerations:]

[Introduction]

We’re improving the Viva Engage experience in Microsoft Teams for iOS by bringing pinned resources and related communities into the Teams mobile app. Pinned resources highlight important links and files within a community, while related communities help users discover other relevant Viva Engage communities. These are two separate features that work together to improve information access and community discovery.

This update aligns the iOS experience with Engage on the web, the Engage mobile app, and Teams for Android, helping users discover important content and related communities more easily—especially those who rely on Teams on iOS as their primary communication tool.

This message is associated with Roadmap ID 559107.

[When this will happen:]

• General Availability (Worldwide): Rollout begins in late April 2026 and is expected to complete by late April 2026.

[How this affects your organization:]

Who is affected:

• Users who access Viva Engage communities in Microsoft Teams on iOS
• Community admins who manage Viva Engage communities

What will happen:

• Users will see pinned resources for a community directly within Teams on iOS.
• Users will see related communities surfaced within the community experience.



• The experience will match what is already available in the Viva Engage mobile app, Viva Engage on the web, and Teams for Android.
• The feature is enabled by default.
• There are no changes to existing admin policies or configurations.

[What you can do to prepare:]

No admin action is required.

• Communicate this update to end users who use Teams on iOS.
• Encourage Viva Engage community admins to review pinned resources and related communities.
• Update internal documentation or helpdesk guidance, if applicable.

[Compliance considerations:]

No compliance considerations identified, review as appropriate for your organization.