Skip to Content

MC1461700 Session and Response Sharing in M365 Copilot

Summary

  • Microsoft 365 Copilot is adding session sharing and response sharing so users can generate a link to share either an entire chat session or a single Copilot response with others in the same organization.
  • Recipients will be able to open shared content in a read-only view and continue the conversation in their own Copilot chat.
  • Shared session content captures only what exists at the time the link is created; later messages remain private.
  • Sharing does not grant access to underlying Microsoft 365 content referenced in the chat, and existing permissions still apply.
  • The feature is enabled by default, but admins can disable it tenant-wide in the Microsoft 365 admin center.

Microsoft 365 Copilot introduces Session and Response Sharing, allowing users to share chat sessions or individual responses via links within their organization. Shared content is read-only, with recipients able to continue conversations. The feature rolls out late August 2026, is enabled by default, and can be disabled tenant-wide by admins.

MC1461700 Session and Response Sharing in M365 Copilot

Microsoft 365 Message Center ID: MC1461700
Primary Service: M365 Copilot
Admin Impact: Low
User Impact: Medium
Release Start: 31 Aug 2026
Release End: 01 Sept 2026
Last Modified: September 8, 2026
Category: Plan for change
Tags: New feature, User impact
Status: Launched
Products & Platforms: Microsoft Copilot (Microsoft 365)
Roadmap ID: 562353

History

Updated September 8, 2026: We have updated the timeline.
8/25/2026 Item Added to Message Center

Microsoft Message

We’re introducing Session and Response Sharing for Microsoft 365 Copilot. This feature allows users to share either an entire Copilot chat session or an individual Copilot response by creating a link that can be shared with others in the same organization.

Session Sharing helps users share the context of a Copilot conversation, while Response Sharing enables sharing of a specific Copilot-generated response. Recipients can view the shared content in a read-only experience and continue the conversation in their own Copilot chat, making it easier for teams to collaborate, reuse work, and share insights without copying and pasting content.

Rollout Schedule

General Availability (Worldwide): Rollout will begin in late August 2026 and is expected to complete by late September 2026 (previously early September).

Impact on Your Organization

Who is affected

All Microsoft 365 Copilot users.

Platforms and services

Microsoft 365 Copilot

What will happen

  • Users will be able to share a complete Copilot chat session or an individual response through a shareable link.
  • Recipients in the same organization can open shared content in a read-only experience.
  • Recipients can continue from the shared content in their own Copilot chat session.
  • Session sharing captures only the conversation content available at the time the link is created. Messages added after sharing remain private and are not included in the shared session.
  • Sharing a chat session or response does not grant access to referenced files, emails, meetings, chats, or other Microsoft 365 content. Existing permissions continue to apply.
  • The feature is enabled by default.

Action Required / Recommendations

No action is required if you want users in your organization to use this feature.

If you do not want users to share Copilot sessions or responses, administrators can disable the feature tenant-wide by navigating to:

  • Microsoft 365 admin center > Copilot > Settings > Copilot session and response sharing
  • Clear the Allow users to share Copilot sessions and responses setting.

Note that this control applies tenant-wide and cannot be scoped to specific users or groups.

Compliance Considerations

  • The feature provides users with a new way to share Copilot-generated content within the organization.
  • Sharing does not grant access to underlying Microsoft 365 content referenced in a chat, such as files, emails, or meetings. Existing permissions continue to govern access to those resources.
  • An administrative control is available to enable or disable the feature across the tenant. The control cannot be scoped through Entra ID groups or other user/group-based targeting.
  • The feature is enabled by default.