Microsoft Roadmap, messagecenter and blogs updates from 26-06-2026

Updated June 25, 2026: We have updated the timeline. Thank you for your patience. 

Introduction

Microsoft Edge for Business will soon support Rewrite, a new feature powered by Microsoft 365 Copilot Chat. This capability helps users draft and rephrase editable text directly within Edge, enhancing productivity and writing quality. Users can access Rewrite by highlighting editable text and right-clicking to open the context menu.

This message is associated with Microsoft 365 Roadmap ID 420335.

When this will happen

General Availability (Worldwide): We will begin rolling late August 2026 and expect to complete rollout by late October 2026. 

How this affects your organization

• Rewrite will be enabled by default for Edge for Business users. 
• Users can access Rewrite by highlighting editable text and right-clicking to open the context menu.

• If Microsoft 365 Copilot is restricted from accessing page content due to Data Loss Prevention (DLP) policies, Rewrite will not function on that content.
• Admins can manage this feature using the InlineComposeEnabled policy setting.

What you can do to prepare

No admin action is required before rollout.

We recommend:

• Reviewing your current DLP configurations to understand how they may impact Rewrite functionality.
• Notifying users about this new capability.
• Updating internal documentation to reflect this change.

Learn more about how DLP affects Copilot access to page content: Microsoft 365 Copilot Chat in Edge and Access to Page Content | Microsoft Edge | Microsoft Learn

Compliance considerations

Updated June 24, 2026: We have updated the content and timeline. Thank you for your patience. 

We’re introducing My Team audiences and expanded targeting capabilities in Viva Engage to help leaders communicate with the employees in their organization and tailor messages to relevant teams, departments, locations, or groups. My Team provides a ready-to-use, automatically maintained audience based on the organizational hierarchy, so leaders can reach the employees who report up to them, including both direct and indirect reports. This audience helps unlock and improve leadership experiences across Viva Engage, making Storyline Announcements, audience analytics, Leadership Corner, and feed and digest distribution more relevant with less setup.

Leaders and delegates can use My Team as-is, review its membership, or further customize and save it as a reusable audience across leader communication experiences. For Storyline Announcements, they can also define recipients at the time of publish, choosing My Team, a saved audience, or a custom audience built using organizational attributes such as department, job title, or country; existing groups like M365 Groups, distribution lists, or security groups; and individual users by name. Together, My Team and flexible targeting make leader communications more relevant, scalable, and easier to manage – with a dynamic default audience and precise targeting for relevant employee groups.

This message is associated with Microsoft 365 Roadmap ID 499895.

[When this will happen:]

• Public Preview (Worldwide): Begins mid-November 2025 and completes by mid-March 2026 (previously early February).
• General Availability (Worldwide): Begins late-July 2026.

[How this affects your organization:]

Who is affected: Leaders and delegates using Viva Engage Storyline Announcements in tenants enrolled in public preview.

What will happen:

• This capability is being introduced as part of the public preview for Viva Engage. During this phase, leaders and their delegates can actively experiment with flexible audience targeting for Storyline Announcements—defining a custom audience at the time of posting, rather than relying solely on pre‑configured Leader Audiences.
• Audiences can include organizational attributes (such as reporting structure, country, department, job title), existing groups (Microsoft 365 Groups, DLs, SGs), or individual users.
• Notifications and delivery channels (Teams, email, Viva Engage Inbox) remain unchanged for recipients.
• No dependency on IT or advance audience setup—leaders can act immediately when communication needs arise.
• Available only in public preview; functionality and targeting options may evolve before general availability.
• Admins should ensure organizational attributes in Entra ID or Organizational Data in Microsoft are accurate to support successful targeting.
• Available platforms: Desktop and web.
• Licensing requirements: This feature requires a premium license available through Viva or Communications and Communities (C&C). Availability may vary depending on your organization’s Microsoft 365 licensing agreement.

[What you can do to prepare:]

No admin action is required for rollout. To prepare, you may want to:

• Validate organizational attributes (reporting structure, country, department, role, job title) in Microsoft Entra ID or Organizational Data in Microsoft.
• Confirm leader and delegate assignments to ensure the right people can use Storyline Announcements and the new targeting control.

Learn more:

• Use your organizational data in Microsoft 365 and Microsoft Viva | Microsoft Viva | Microsoft Learn

[Compliance considerations:]

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

Updated June 25, 2026: We have updated the content and timeline. Thank you for your patience. 

[Introduction]

As part of our ongoing mission to deliver a modern, secure, and scalable one-stop management portal for admins, we are transitioning Teams Android device management from the Teams admin center (TAC) to the Teams Rooms Pro Management portal (PMP).

This move consolidates management of all Teams devices, including Teams Rooms on Windows, Teams Rooms on Android, Teams phones, and Teams panels, into a single unified portal, providing IT admins a consistent and seamless experience for managing devices at scale.

This message is associated with Roadmap ID 555235.

[When this will happen:]

• Public Preview: We started the rollout in early April 2026 to limited customers and starting 26th June, the rollout will expand to majority of public cloud customers.
• General Availability (Worldwide): We expect to complete GA rollout by mid-July 2026 for all the customers in Public cloud
• General Availability (GCC High and DoD): We expect to complete the rollout by late-July 2026.
• General Availability (GCC): We expect to complete the rollout by late-August 2026.
• Device management deprecation in TAC: We will start the deprecation for Public cloud customers in August and expect to complete by end of September 2026 in all the clouds.

[How this affects your organization:]

Who is affected:

Admins who manage Teams Rooms on Android, Teams phones, Teams panels, and SIP Phones.

What will happen:

• By end of June 2026, Android device management capabilities, including inventory, updates, health monitoring, and settings will transition from TAC to PMP for the device types, Teams Rooms on Android, Teams phones, Teams panels and SIP Phones.
• The following capabilities will be available and enhanced in PMP:
• Device inventories for Android-based Teams Rooms, phones, and panels, including metadata and app information
• Remote device actions (restart, log collection, sign-in/out, provisioning, and more)
• Update management
• Device settings management
• Device health monitoring
• SIP device management
• PMP will become the primary portal for all Teams device management. By September 2026, overlapping TAC capabilities (updates, settings, restart, sign-in/out, log collection, provisioning) will be deprecated in TAC.
• The article below serves as the main information source for this transition. It has been updated with the latest timelines, milestones, migration guidance, and readiness steps. We will keep updating it as the rollout progresses.
  • Transitioning Teams Android Device Management from Teams Admin Center to the Teams Rooms Pro Management Portal – Microsoft Teams | Microsoft Learn

[What you need to do to prepare:]

• Monitor the below article for any feature specific updates and timelines. This article also provides migration guidance and pre-requisites for successful transition to PMP.
  • Transitioning Teams Android Device Management from Teams Admin Center to the Teams Rooms Pro Management Portal – Microsoft Teams | Microsoft Learn
• Learn more about Pro Management portal features with these Teams Rooms Pro Management short YouTube videos.
• Update internal helpdesk and IT documentation to reference PMP as the new management portal.

[Compliance considerations]

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

Updated June 25, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

Microsoft Teams is introducing slash (/) commands for apps in the compose box across chats and channels. This change provides a standardized way for users to invoke app functionality directly from the compose box and receive responses inline.

This message is associated with Microsoft 365 Roadmap ID 495002.

[When this will happen:]

• Targeted Release (Worldwide): We will begin rolling out in early July 2026 (previously late May) and expect to complete by early July 2026 (previously late June).
• General Availability (Worldwide): We will begin rolling out in early August 2026 (previously early July) and expect to complete by late August 2026 (previously late July).

[How this affects your organization:]

Who is affected:

• All Microsoft Teams users
• App developers publishing apps in the Teams Store

• Users can type “/” in the compose box to discover and invoke supported app commands.
• Apps can return responses as Targeted Messages (visible only to the user who invoked the command).
• The feature is available by default when apps support slash commands
• No changes to existing admin policies or permissions.
• Apps will only appear in slash commands if their developers update the app manifest to define supported commands.

[What you can do to prepare:]

• No action is required.
• Review internal app inventory and confirm continued availability of apps that adopt slash commands.
• Update internal guidance if you provide documentation on Teams app usage.

[Compliance considerations:]

Introduces a new targeted messaging pattern (user-only visibility) within chats and channels.

Updated June 23, 2026: We have updated the timeline. Thank you for your patience. 

[What and Why]

We are performing planned maintenance to support upcoming updates to PowerPoint Live in Microsoft Teams, which will begin rolling out on June 30, 2026. To keep Teams Rooms aligned with these updates, ensure devices are running the latest supported app versions.

[Rollout Schedule]

Teams Rooms on Windows General Availability

• Worldwide and GCC:  Already available now.
• GCC High: We will begin rolling out in early June 2026 and expect to complete by mid-June 2026.
• DoD: We will begin rolling out in early June 2026 and expect to complete by mid-June 2026.

Teams Rooms on Android General Availability

• Worldwide and GCC: We will begin rolling out in late June 2026 (previously mid-June) and expect to complete by early July 2026 (previously late June).
• GCC High: We will begin rolling out in early July 2026 and expect to complete by mid-July 2026.
• DoD: We will begin rolling out in early July 2026 and expect to complete by mid-July 2026.

[Impact on Your Organization]

Who is affected

• Organizations using Microsoft Teams Rooms devices

Platforms/Services

Microsoft Teams

• Teams Rooms on Windows
• Teams Rooms on Android

What will happen

• Teams Rooms devices running outdated app versions may not fully support PowerPoint Live experience, including:
  • Synchronized media playback
  • Viewing real-time inking and annotation
• There is no change to existing admin policies.
• Functionality remains consistent once devices are updated.

[Action Required/Recommendations]

To maintain PowerPoint Live functionality, complete the following:

• Update Teams Rooms devices to supported versions:
  • Windows: Version 5.6.135 (available now)
  • Android: Version 1449/1.0.96.2026124903 (available mid-June 2026)
• Complete updates before June 30, 2026.
• Review device update processes to ensure compliance across all meeting rooms.
• Notify IT support/helpdesk teams of potential functionality impact if devices are not updated.

[Compliance Considerations]

[What and Why]

Microsoft is introducing explicit grounding integration in Excel Agent, allowing users to upload and process files directly to ground AI responses in their data. This improves productivity by enabling more accurate analysis of large datasets, combining information across multiple files, and supporting a broader range of file types within Excel. By grounding AI in user-provided content, Excel Agent helps deliver more relevant, context-aware insights.

[Rollout Schedule]

• General Availability (Worldwide): Rolling out from late April 2026 through late June 2026.

[Impact on Your Organization]

Who is affected

• Users with access to Excel Agent in Microsoft 365 tenants

Platforms/Services

• Excel Agent (Microsoft 365 apps)

What will happen

• Users will be able to upload files directly within Excel Agent:

   

• Excel Agent will use uploaded files for explicit grounding to improve AI-generated results.
• Users can analyze large datasets and combine insights across multiple files.
• A broader range of file types will be supported.
• The feature will be available within the existing Excel Agent workflow.
• The feature will be enabled by default where Excel Agent is available.
• No changes to existing admin policies are required.

[Action Required/Recommendations]

• No action is required.
• Consider notifying users about this enhancement to help them take advantage of grounded AI capabilities in Excel Agent.
• Update internal documentation or training materials if you reference Excel Agent or Copilot capabilities.

[Compliance considerations]

• Creating a new agent in MCS and configuring it to engage with employees using Microsoft 365.
• Exporting an existing agent, which will automatically configure their agent to target employees using Microsoft 365.

Later this year, we expect iOS 27 and iPadOS 27 to be released by Apple. Microsoft Intune, including the Intune Company Portal and Intune app protection policies (APP, also known as MAM), will require iOS/iPadOS 18 and higher shortly after the iOS/iPadOS 27 release.

[How this will affect your organization:]

If you are managing iOS/iPadOS devices, you might have devices that will not be able to upgrade to the minimum supported version (iOS 18/iPadOS 18). Provided that Microsoft 365 mobile apps are supported on iOS 18/iPadOS 18 and higher, this may not affect you; you have likely already upgraded your OS or devices.

Refer to the following Apple documentation for devices to check which devices support iOS 18 or iPadOS 18 (if applicable):

• Supported iPhone models
• Supported iPad models

For instructions on how to check in the Microsoft Intune admin center which devices or users may be affected, read below. 

Note: Userless iOS and iPadOS devices enrolled through Automated Device Enrollment (ADE) have a slightly nuanced support statement due to their shared usage. The minimum supported OS version will change to iOS 18/iPadOS 18 while the allowed OS version will change to iOS 16/iPadOS 16 and later. For more details, see https://aka.ms/ADE_userless_support.

[What you need to do to prepare:]

Check your Intune reporting to see what devices or users may be affected. For devices with mobile device management (MDM) go to Devices > All devices and filter by OS. For devices with app protection policies go to Apps > Monitor > App protection status and use the Platform and Platform version columns to filter.

To manage the supported OS version in your organization, you can use Microsoft Intune controls for both MDM and APP. For more information, please review: Manage operating system versions with Intune – Microsoft Intune | Microsoft Learn.

Later this year, we expect macOS Golden Gate 27 to be released by Apple. Microsoft Intune, the Company Portal app and the Intune MDM agent will be moving to support macOS 15 (Sequoia) and later. Since the Company Portal app for iOS and macOS are a unified app, this change will occur shortly after the release of macOS 27. This does not affect existing enrolled devices.

[How this will affect your organization:]

This will only affect you if you currently manage, or plan to manage macOS devices with Intune. This may not impact you because your users have likely already upgraded their macOS devices. Refer to macOS Sequoia is compatible with these computers – Apple Support for a list of devices that are supported.

Note: Devices that are currently enrolled on macOS 14.x or below will continue to remain enrolled even when those versions are no longer supported. New devices will be unable to enroll if they are running macOS 14.x or below.

Enrolled macOS devices without user affinity, either through Automated Device Enrollment (ADE) without user affinity or Direct Enrollment, have a slightly nuanced support statement due to their shared usage. For more details, see https://aka.ms/Intune/macOS/ADE-DE-support.

[What you need to do to prepare:]

Check your Intune reporting to see which devices or users may be affected. Go to Devices > All devices and filter by macOS. You can add in additional columns to help identify who in your organization has devices running macOS 14.x or below. Request that your users upgrade their devices to a supported OS version before this change. 

[What and Why:]

Microsoft Purview is introducing a new view-only role management capability that enables administrators with Global Reader and Security Reader roles to view role assignments and scopes within the Microsoft Purview portal and Microsoft Defender portal. This update improves visibility and transparency of compliance role configurations without granting additional permissions, supporting audit readiness and strengthening enterprise security governance.

Rollout Schedule:

• Worldwide (General Availability): Beginning in late July 2026 and expect to complete by late August 2026
• GCC, GCC High, DoD: Beginning in late August 2026 and expect to complete by late September 2026

[Impact on Your Organization:]

Who is affected: Administrators assigned Global Reader or Security Reader roles in Microsoft Entra ID and Microsoft Purview

Platforms/Services:

• Microsoft Purview compliance portal (web)
• Microsoft Entra ID

What will happen:

• Users with Global Reader and Security Reader roles will gain read-only access to the following settings
  • Roles and scope pages in the Microsoft Purview portal
  • Permissions page in the Purview portal
• Admins can view all role memberships and assignments without being able to modify them.
• The feature will be enabled automatically for eligible roles.
• No changes are made to existing permissions or role assignments.
• There is no impact to user workflows.

[Action Required/Recommendations:]

• No action is required.
• Review internal governance or auditing processes to determine if additional stakeholders should be assigned Global Reader or Security Reader roles for visibility.
• Inform compliance or security teams of increased transparency capabilities.
• Update internal documentation if referencing role visibility limitations.

Learn more: Permissions in the Microsoft Purview portal | Microsoft Learn (will be updated before rollout)

[Compliance considerations:]

[What and Why:]

We are updating the data retention period for Microsoft Enterprise Content Delivery Network (eCDN) analytics from 360 days to 180 days. This change aligns with enterprise-ready data governance practices across Microsoft 365, helping organizations maintain compliance while ensuring analytics data is retained for a duration appropriate for operational insights and reporting needs.

[Rollout Schedule:]

• Effective date (Worldwide, GCC, GCC High): July 27, 2026

[Impact on Your Organization:]

Who is affected: Admins and users who rely on Microsoft eCDN analytics reporting

Platforms/Services: Microsoft eCDN analytics (web-based reporting and dashboards)

What will happen:

• Analytics data will be retained for up to 180 days from the time of generation.
• Data older than 180 days will be automatically deleted and no longer accessible.
• The updated retention policy will apply tenant-wide.
• There are no changes to how data is collected or surfaced, only how long it is retained.
• The change is enabled by default with no admin configuration required.

[Action Required / Recommendations:]

No immediate action is required.

• Review any reporting or analytics workflows that rely on data older than 180 days.
• Update internal processes or dashboards to ensure necessary data is exported or archived before July 27, 2026.
• Notify stakeholders who depend on long-term analytics trends.
• Update internal documentation or reporting guidelines as needed.

[Compliance considerations:]

[What and Why:]

We’re introducing a refreshed Libraries view in OneDrive for the web that replaces the existing More places experience. This update makes it easier for users to discover and access SharePoint document libraries across recent activity, Teams, and favorite sites. The new experience improves navigation and findability, helping users and teams quickly return to shared content and work more efficiently.

This message is associated with Roadmap ID 566315.

[Rollout Schedule:]

• Targeted Release (Worldwide): Beginning early July 2026 and expected to complete by mid-July 2026
• General Availability (Worldwide): Beginning mid-July 2026 and expected to complete by late July 2026

[Impact on Your Organization:]

Who is affected: All users of OneDrive for the web

Platforms/Services:

• OneDrive for the web
• SharePoint Online
• Microsoft Teams

What will happen:

• The More places experience will be replaced by a new Libraries view in OneDrive for the web.
• The feature will be enabled by default.
• Users will see more recently accessed document libraries for quicker access.

Screenshot 1: New libraries view showing recently accessed document libraries:



• Users can access libraries tied to Teams and favorite SharePoint sites directly.
• Users can:
  • Filter libraries using keywords.

  Screenshot 2: Recent document libraries, filtered to Site assets

  >

  • Sort libraries by recent activity or alphabetically.
  • Switch between list and tiles views.
• Existing permissions and access controls remain unchanged.
• No admin configuration or policy changes are required.

[Action Required/Recommendations:]

No action is required.

Recommended actions:

• Review and update internal training materials to reflect the new Libraries experience.
• Inform helpdesk and support teams about the replacement of More places.
• Communicate the new capabilities to end users (filtering, sorting, view options).

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

If your organization is running up-to-date versions of Excel, no action is required and you can disregard this message. Otherwise, please review the guidance and take appropriate action.

[What and Why:]

We are updating the authentication flow used by Excel Power Query when connecting to enterprise data sources using Organizational Accounts (Microsoft Entra ID). This change strengthens security and improves the reliability of connections to enterprise services. The update aligns Excel with modern authentication standards, helping organizations better protect access to enterprise data while providing a more consistent sign-in experience.

Newer versions of Excel, including Microsoft 365, already use this updated authentication mechanism and are not affected.

[Rollout Schedule:]

We recommend updating as soon as possible, and no later than July 24, 2026.

[Impact on Your Organization:]

Who is affected:

Excel users who connect to enterprise data sources through Power Query using Organizational Accounts (Microsoft Entra ID) and are running Excel 2021 version 21.08.

Affected Power Query connectors include, but are not limited to:

• Web
• Files (Excel, JSON, and others)
• SharePoint (Lists, Folders, Files)
• SQL Server
• SQL Analysis Services
• OData
• HDFS
• Exchange
• Lakehouse
• Warehouse
• Power BI
• Dataflows
• Dataverse
• SQL Database
• SQL Analytics
• Data Lake Gen 2
• Azure Data Explorer
• Azure Blob
• Azure Table
• PostgreSQL
• Oracle
• Dynamics 365

Platforms/Services:

• Excel (desktop)
• Power Query
• Microsoft Entra ID

What will happen:

• Users running unsupported or outdated Excel versions will lose the ability to authenticate using Organizational Accounts.
• Microsoft 365 and newer supported versions of Excel are not affected.
• Older, unsupported Office versions will no longer function for these authentication scenarios.

[Action Required / Recommendations:]

To avoid disruption:

• Update devices running Excel 2021 version 21.08 to build 16.0.14334.20754 or later by July 24, 2026.
• Devices running Excel versions older than 21.08 should be upgraded to a newer, supported version of Excel.

[Compliance considerations:]

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

[What and Why]

We are introducing a flexible query capability in Microsoft Viva Insights Analytics Workbench that enables insights analysts to explore Microsoft 365 Copilot agent adoption using customizable, self-serve queries. Analysts can combine granular agent usage metrics with organizational attributes to understand trends, create tailored reports, and support data‑driven decision making without relying on predefined dashboards.

This message is associated with Microsoft 365 Roadmap ID 562412.

[Rollout schedule]

• General Availability (Worldwide): We will begin rolling out in late July 2026 and expect to complete by late August 2026. 

[Impact on your organization]

This feature will be enabled automatically for eligible Viva Insights analyst users and does not require admin action prior to deployment.

Who is affected

• Insights analysts using Viva Insights Analytics Workbench
• Organizations using Microsoft 365 Copilot agents
• Organizations must have more than 50 Microsoft 365 Copilot (Premium) license to access and use this feature

Platforms and services

• Viva Insights (web)
• Microsoft 365 Copilot

What will happen

• A new Agent query template will be available in the Analytics Workbench: 

  

• Analysts can use this template to query Copilot agent metrics.
• Queries include agents used within Microsoft 365 Copilot.
• Analysts can combine agent usage data with organizational attributes.
• Analysts can customize and export reports.

[Action required or recommendations]

No action is required to enable this feature.

As an optional step, you may consider:

• Notifying insights analysts about this new capability.
• Updating internal documentation if you reference analytics workflows in Viva Insights.
• Reviewing updated documentation once it becomes available during rollout.

[Compliance considerations]

[What and Why:]

We are updating Viva Insights Copilot Analytics to remove the Viva Insights license requirement for managers to access team views. After this change, eligible managers and their delegates can access manager-scoped Copilot Analytics insights without requiring an assigned Viva Insights license.

This update reduces access barriers, supports broader Copilot adoption across organizations, and enables admins to more accurately define and manage the eligible manager population—while continuing to respect existing admin controls and manager settings.

[Rollout Schedule:]

General Availability (Worldwide, GCC):  We will begin rolling out in mid-July 2026 and expect to complete by late July 2026

[Impact on Your Organization:]

Who is affected:

• Administrators and leaders using Viva Insights Copilot Analytics
• Organizations with manager-scoped insights enabled
• Users permitted through Viva Insights VFAM controls
• Tenants with at least 50 Microsoft 365 Copilot (Premium) licenses or 50 Viva Insights licenses assigned

Platforms/Services:

• Viva Insights (web)
• Microsoft 365 Copilot Analytics

What will happen:

• The license requirement for managers to access team insights views will be removed.
• Eligible managers and delegates will gain access based on admin configuration, not license assignment.
• The feature will be enabled by default.
• Admins can manage access through the Manager settings page in Viva Insights.
• Existing admin controls and manager settings will continue to be respected.

[Action Required / Recommendations:]

No immediate action is required. We recommend that you:

• Review the update and assess impact on reporting, governance, and manager access policies.
• Verify access to manager-scoped team views in Viva Insights admin settings.
• Communicate the change to newly eligible managers.
• Engage your works council or employee representatives, if applicable.

Learn more: Configure manager settings | Microsoft Learn (will be updated prior to rollout)

[Compliance considerations:]

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

[What and Why]

We are updating Microsoft Teams on the web to align with Microsoft Entra ID “Keep Me Signed In” (KMSI) behavior. This change improves security by ensuring that Teams web sessions respect users’ explicit sign-in preferences. If a user does not choose to remain signed in, Teams will no longer persist browser sessions, reducing the risk of unauthorized access on shared or unmanaged devices.

[Rollout Schedule]

General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out in late June 2026 and expect to complete by late July 2026.

[Impact on Your Organization]

Who is affected:

• All users accessing Microsoft Teams via a web browser
• Organizations with specific security or compliance requirements for session persistence

Platforms/Services:

• Microsoft Teams (web)
• Microsoft Entra ID authentication experience

What will happen:

• Teams web will respect the Microsoft Entra KMSI selection during sign-in.
• If users select “Yes” (stay signed in):
• Session behavior remains unchanged.
• Users stay signed in across browser sessions.
• If users select “No” or do not respond to KMSI:
• Local authentication tokens and cached session data are cleared when the browser closes.
• Users must sign in again in a new browser session.
• On managed devices:
• Users may be automatically authenticated using device credentials.
• The KMSI prompt may still appear unless suppressed by tenant settings or Conditional Access policies.
• Tenants using Seamless SSO or AD FS (Integrated Windows Authentication):
• Will continue to bypass the KMSI prompt.
• Sign-in persistence is controlled by the existing SSO configuration.
• This behavior is enabled by default and respects existing tenant configurations.

[Action Required / Recommendations]

No immediate action is required. However, we recommend the following:

• Review your Microsoft Entra ID KMSI configuration and user guidance.
• Inform users that Teams web sessions may no longer persist unless “Stay signed in” is selected.
• Evaluate Conditional Access policies or persistent browser session controls if needed.
• Update internal documentation or helpdesk scripts to reflect this change.

Learn more: Manage the “Stay signed in” prompt in Microsoft Entra ID

[Compliance considerations]

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

[What and Why:]

To address an infrastructure-related reliability issue, we are temporarily disabling group membership management actions from the Group card when it is accessed from SharePoint Online. This ensures users do not initiate membership changes that may fail to complete.

This change is part of our ongoing commitment to provide a more reliable and predictable experience across Microsoft 365 group management.

[Rollout Schedule:]

• General Availability (Worldwide, GCC, GCC High, DoD): Beginning late June 2026 and expected to complete by late June 2026
• Restoration of functionality: We expect to restore the affected Group card membership actions by September 30, 2026

[Impact on Your Organization:]

Who is affected: Users who manage Microsoft 365 group membership from the Group card in SharePoint Online sites.

Platforms/Services:

• SharePoint Online (web)
• Microsoft 365 Groups
• Outlook
• Microsoft Teams
• Microsoft 365 admin center

What will happen:

• The following membership management actions will be temporarily unavailable from the Group card in SharePoint Online:
1. Follow / Stop following in inbox
2. Leave group



3. Remove owner/member
4. Promote member / Demote owner



5. Join / Request to join group

• All other Group card functionality will remain available.
• Users can continue to manage group membership via Outlook, Microsoft Teams, or the Microsoft 365 admin center.
• The change will be enabled automatically during rollout (no admin configuration required).

[Action Required/Recommendations:]

No admin action is required.

• Inform group owners, site owners, and help desk staff about this temporary limitation.
• Advise users to manage group membership through Outlook, Teams, or the Microsoft 365 admin center during this period.
• Update internal documentation and support guidance.
• Prepare support messaging for users who may encounter errors during rollout.

[Compliance considerations:]

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

[What and Why]

Microsoft is introducing support for FTP and SFTP in Endpoint data loss prevention (DLP) in Microsoft Purview. This capability helps organizations monitor and protect sensitive data transferred using FTP and SFTP from managed Windows devices. It prevents unauthorized data exfiltration while maintaining visibility and control and closes a gap in protection across common transfer methods.

[Rollout Schedule]

• Public Preview: Beginning late July 2026 and expected to complete early August 2026
• General Availability (Worldwide, GCC, GCC High, and DoD): Beginning and completing mid-August 2026

[Impact on Your Organization]

Who is affected

• Admins managing Microsoft Purview Endpoint DLP
• Users on managed Windows devices

Platforms/Services

• Microsoft Purview
• Endpoint DLP
• Windows devices

What will happen

• Endpoint DLP will support monitoring and protection of files transferred over FTP and SFTP.
• FTP and SFTP events will appear as a new activity type in Activity Explorer.
• Admins can apply DLP actions such as audit, block, and block with override to FTP and SFTP transfer activities after enabling the capability in policy settings: 

  

• FTP and SFTP protection is not enabled by default. Administrators must configure FTP/SFTP transfer activities in Endpoint DLP policies to apply protection.
• Once enabled, FTP and SFTP transfer activities are evaluated using the conditions, scope, and enforcement actions configured in Endpoint DLP policies.

[Action Required / Recommendations]

No immediate action is required before rollout.

Recommended actions:

• Review your existing Endpoint DLP policies for devices.
• Identify where FTP and SFTP transfer protection should be applied.
• Start with audit only mode before enabling blocking actions.
• Use Activity Explorer to monitor FTP and SFTP events after rollout.
• Refine policies based on observed activity.

Learn more:

• Create and deploy data loss prevention policies | Microsoft Purview | Microsoft Learn
• Get started with activity explorer | Microsoft Purview | Microsoft Learn
• Get started with Endpoint data loss prevention | Microsoft Purview | Microsoft Learn
• Help protect against sharing of a defined set of unsupported files | Microsoft Purview | Microsoft Learn
• Learn about Endpoint data loss prevention | Microsoft Purview | Microsoft Learn

[Compliance Considerations]

This change extends existing Endpoint DLP policy enforcement to additional data transfer channels and may affect how sensitive data movement is monitored and controlled across endpoints. Review as appropriate for your organization.

[What and Why]

We are bringing desktop-style emoji shortcuts to Microsoft Teams on iOS and Android. Users can insert emojis directly in the compose box by typing a keyword between colons (for example, :smile: → 😊).

This update improves consistency across platforms and enhances user productivity by making emoji input faster and more intuitive on mobile devices.

This message is associated with Microsoft 365 Roadmap ID 565370.

[Rollout Schedule]

• Targeted Release (Worldwide): We began rolling out in late March 2026 and expect to complete by early July 2026.
• General Availability (Worldwide): We will begin rolling out in early July 2026 and expect to complete by late July 2026.
• General Availability (GCC): We will begin rolling out in mid-July 2026 and expect to complete by early August 2026.
• General Availability (GCC High): We will begin rolling out in late July 2026 and expect to complete by mid-August 2026.
• General Availability (DoD): We will begin rolling out in early August 2026 and expect to complete by late August 2026.

[Impact on Your Organization]

Who is affected: All Microsoft Teams users on iOS and Android devices

Platforms/Services: Microsoft Teams (iOS and Android)

What will happen:

• Users can open the emoji suggestion menu by typing : followed by at least two characters (e.g., :sm)
• Users can insert emojis by typing a full name between colons (e.g., :smile: → 🙂)
• Common emoticons such as :), :D, and :P automatically convert into emojis
• Lowercase emoticons (e.g., :d, :p) are also supported
• Emoji search supports fuzzy matching and mid-string search
• Custom emojis are supported
• Parenthesis () shortcuts continue to work and will be retired later in alignment with desktop
• The feature is enabled by default with no admin controls

[Action Required / Recommendations]

No action is required.

To prepare your organization:

• Notify your help desk about the updated emoji shortcut experience.
• Update internal training or adoption materials to include emoji shortcuts triggered with :.
• Consider sharing a brief user communication highlighting the new mobile parity experience.

Learn more: 

• Send an emoji or GIF in Microsoft Teams Free | Microsoft Support
• Send an emoji, GIF, or sticker in Microsoft Teams | Microsoft Support

[Compliance considerations]

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

[What and Why]

The Recap app in Microsoft Teams provides a centralized experience for users to find, review, and catch up on meeting recaps. By bringing recordings, transcripts, and AI-powered summaries together, this feature improves personal productivity and helps users quickly stay informed across meetings.

Quick filters help users find the right meetings faster, while audio recap capabilities enable efficient review of multiple meetings in a podcast-style format. Users can also browse and revisit meeting recaps from the past 30 days, making it easier to stay up to date.

This message is associated with Microsoft 365 Roadmap ID 564614.

[Rollout Schedule]

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

[Impact on Your Organization]

Who is affected

•  All Microsoft Teams users

Platforms/Services

• Microsoft Teams for Windows
• Microsoft Teams for Mac
• Microsoft Teams for web
• Mobile support coming soon

What will happen

• The Recap app is a first-party Microsoft Teams core app.
• A new Recap app will be available in Teams and accessible from the app store in the left rail: 

  

• The app is pre-installed but not pinned by default.
• Users will be able to:
  • View meeting recaps from the past 30 days
  • Filter meetings by date, participants, or keywords
  • Access recaps for meetings that include a recording or transcript
  • Watch video recaps or listen to audio recaps: 

    

    

  • Generate a combined audio recap across multiple meetings: 

    

• Users can access the Recap app from the Teams app store by selecting Apps and then Recap, browse recent meetings, and open individual recaps to view or listen.
• AI-powered recap features such as audio recap, video recap, and intelligent summaries require a Microsoft 365 Copilot license.
• Users without a Copilot license can still access recordings and transcripts based on existing permissions.
• The feature is enabled by default.

[Action Required/Recommendations]

No action is required.

Consider the following recommendations:

• Review and update internal training and adoption materials.
• Communicate Copilot licensing requirements for AI-generated recap features.
• Pin the Recap app for your organization using Teams admin center (app setup policies) to improve discoverability.

[Compliance considerations]

No compliance considerations have been identified for this change.

[Introduction]

To help administrators better understand and manage adoption of Copilot connectors, Microsoft is introducing a new Copilot connectors usage report in the Microsoft 365 admin center. This report provides visibility into how connectors are used across Microsoft 365 Copilot experiences, helping organizations assess adoption, identify usage patterns, and optimize connector deployment.

This update supports customer feedback requesting clearer reporting on Copilot connector usage across entry points such as Copilot Chat, Search, and agents.

This message is associated with Microsoft 365 Roadmap ID 519571.

[When this will happen:]

• Public Preview (Worldwide): We will begin rolling out late June 2026 and expect to complete by early July 2026.
• General Availability (Worldwide): We will begin rolling out early September 2026 and expect to complete by mid-September 2026.

[How this affects your organization:]

Who is affected:

• Microsoft 365 administrators
• Organizations using Copilot connectors with the Microsoft 365 Copilot app
• A Microsoft 365 Copilot (Premium) license is required to use this feature

What will happen:

• A new “Connectors” report will appear in Microsoft 365 admin center under Reporting > Usage > Microsoft 365 Copilot > Connectors.



• The report will show:
• Active users of connectors across Copilot Chat, Copilot Search, and agents
• Total connector responses generated in the organization
• Daily trend views of active usage and total responses
• Usage breakdown per user and per connector
• The report is enabled by default and respects existing permissions.
• There is no impact to user workflows.

[What you can do to prepare:]

No action is required before rollout.

• Inform relevant administrators and analytics stakeholders about the new report.
• Review the report after rollout to assess Copilot connector adoption and usage trends.
• Update internal documentation if Copilot reporting is referenced.

Learn more: Copilot connectors usage report documentation

[Compliance considerations:]

This change introduces a new admin usage report that improves visibility into Copilot connector usage. No other compliance considerations are impacted.