| (Updated) Microsoft 365 Copilot: Copilot Pages and Notebooks Creation in OneDriveCategory:Microsoft Copilot (Microsoft 365)Nummer:MC1449182Status:planForChange | Updated November 13, 2026: We have updated the timeline. Thank you for your patience. [What and why] We’re changing where newly created Copilot Pages are stored. Going forward, Copilot Pages created in Copilot Chat, the Microsoft 365 Copilot app, and new Copilot Notebooks will be stored in OneDrive for Business instead of their current location. This change enables organizations to manage newly created Copilot Pages using existing OneDrive for Business governance, compliance, data protection, retention, and lifecycle management capabilities. [Rollout schedule] - General Availability (Worldwide): Beginning in mid-October 2026 (previously mid-August) and expected to complete by late November 2026 (previously late September)
- General Availability (GCC, GCC High, and DoD): Beginning in mid-November 2026 (previously mid-September) and expected to complete by mid-December 2026 (previously early December)
[Impact on your organization] Who is affected Users who create Copilot Pages in: - Copilot Chat
- Microsoft 365 Copilot app
- Copilot Notebooks
Microsoft 365 administrators responsible for governance, compliance, retention, and content management Platforms and services - Microsoft 365 Copilot
- Copilot Chat
- Copilot Notebooks
- OneDrive for Business
- Microsoft Purview compliance solutions
What will happen After rollout: - Newly created Copilot Pages will be stored in users’ OneDrive for Business.
- New Copilot Pages will appear alongside other OneDrive files, such as Word, Excel, and PowerPoint documents.
- New Copilot Notebooks and artifacts created within them will appear alongside other OneDrive files, such as Word, Excel, and PowerPoint documents.
- Existing OneDrive governance, compliance, data protection, retention, lifecycle management, reporting, and investigation capabilities will apply to newly created Copilot Pages.
In addition to all existing governance and management capabilities, the following additional OneDrive for Business capabilities will apply to newly created Copilot Pages: Compliance and legal - Standard file path-based eDiscovery
- Retention labels with record locking
- Information Barriers
- Compliance Boundaries
Data protection - Data Loss Prevention (DLP) policies and mitigation workflows
- Third-party governance solutions that support OneDrive content
Lifecycle management - Retention and lifecycle policies
- Existing departed-user workflows for OneDrive content
Monitoring and oversight - OneDrive storage reporting
- Administrative investigations of content stored in OneDrive
Unaffected files - Existing Copilot Pages will remain in their current location and will not be migrated as part of this change.
- Existing Copilot Notebooks will continue to store all newly created pages in SharePoint Embedded. Only Copilot Notebooks created after this change will store pages in OneDrive.
- Loop workspaces are not affected and will continue to use their current storage location.
IT Admin controls - If your organization has set Create and view Copilot Pages and Copilot Notebooks to Disabled, that setting will continue to be honored after this change.
- This admin control is planned for future retirement. Microsoft will provide additional communication and transition guidance before the setting is retired.
[Action required and recommendations] No action is required for the rollout. We recommend that administrators: - Review existing DLP, retention, and compliance policies that apply to OneDrive for Business.
- Verify that any third-party governance or eDiscovery solutions are configured to monitor OneDrive content as appropriate.
- Update internal documentation and governance guidance for AI-generated content.
- Communicate to users that newly created Copilot Pages will be stored in their OneDrive for Business.
[Compliance considerations] | Question | Answer | | Does this change alter where customer data is stored? | Yes. Newly created Copilot Pages will be stored in OneDrive for Business instead of their previous storage location. | | Does this change affect compliance and governance capabilities? | Yes. Newly created Copilot Pages will be subject to OneDrive for Business compliance capabilities, including eDiscovery, retention labels with record locking, Information Barriers, and Compliance Boundaries. | | Does this change affect data protection controls? | Yes. Existing OneDrive for Business data protection controls, including Data Loss Prevention (DLP) policies and supported third-party governance solutions, can be applied to newly created Copilot Pages. | | Does this change affect lifecycle management and retention processes? | Yes. Existing OneDrive for Business retention policies, lifecycle management capabilities, and departed-user workflows will apply to newly created Copilot Pages. | | Does this change affect how administrators monitor or investigate content? | Yes. Administrators will be able to use standard OneDrive for Business reporting, monitoring, and investigation capabilities for newly created Copilot Pages. |
|
| (Updated) Microsoft Purview: Adaptive scopes add lifecycle status evaluation controls for recipients and site ownersCategory:Microsoft PurviewNummer:MC1450128Status:stayInformed | Updated November 13, 2026: We have updated the timeline. Thank you for your patience. [What and why] Microsoft Purview is introducing lifecycle status evaluation controls for adaptive scopes. This update gives administrators explicit control over whether active, inactive, and soft-deleted recipients and site owners are included in adaptive scope membership. With this change, newly created adaptive scopes will evaluate only active recipients and site owners by default. Administrators can configure adaptive scopes to include inactive and/or soft-deleted recipients and site owners when needed. This update also adds support for ISO 8601 duration values for selected date attributes in the adaptive scope advanced query builder. This message is associated with Microsoft 365 Roadmap ID 568785. [Rollout schedule] - Public Preview: Beginning in December 2026 (previously mid-September) and expected to complete in December 2026 (previously early October)
- General Availability (Worldwide): Beginning in April 2027 (previously mid-October 2026) and expected to complete in April 2027 (previously mid-November 2026)
[Impact on your organization] Who is affected - Microsoft Purview administrators who create or manage adaptive scopes.
- Organizations that use adaptive scopes for Microsoft Purview policy targeting.
Platforms and services - Microsoft Purview
- Adaptive Scopes
What will happen Existing adaptive scopes will continue to function as they do today and will not be automatically modified as part of this rollout. For newly created adaptive scopes: - Active recipients and site owners will be evaluated by default.
- Inactive and soft-deleted recipients or site owners will not be included unless explicitly configured by an administrator.

Administrators will also have the option to update existing adaptive scopes to use explicit lifecycle status evaluation criteria for recipients and site owners. Additionally, adaptive scopes will support ISO 8601 duration values for certain date-based attributes in the advanced query builder. [Action required and recommendations] No action is required before rollout. We recommend that administrators: - Review current adaptive scope configurations and governance requirements.
- Determine whether inactive or soft-deleted recipients and site owners should be included in future adaptive scope definitions.
- Update adaptive scope creation processes and documentation, if applicable, to account for the new lifecycle status settings.
Learn more [Compliance considerations] No compliance considerations have been identified. |
| Release Planner Retirement: D365, Power Platform, and Dataverse Move to AI at WorkCategory:Dynamics 365 Apps
Power Apps
Microsoft Power Automate
Microsoft Dataverse
Power PlatformNummer:MC1461529Status:planForChange | Release Planner is now retired. To stay informed about upcoming capabilities and prepare your organization for feature rollout and adoption, use the resources shared below. To view product availability for Dynamics 365, Power Platform and Copilot Studio, visit the new Learn page at https://aka.ms/d365-product-availability.
Starting this fall, Dynamics 365, Power Platform, and Dataverse roadmap content is joining the
AI at Work roadmap, giving customers a single destination
to discover upcoming capabilities, track rollout progress, and plan adoption across Microsoft’s
business applications, productivity, and AI portfolio.
As part of this transition, Release Planner will
retire on November 15, 2026. Microsoft is also retiring the twice-yearly release wave communication
model in favor of continuous roadmap disclosure and change communications. New capabilities will be
published to the AI at Work roadmap as they become committed and ready to share, providing a more
current and comprehensive view of upcoming innovation.
When this will happen
- September 2026: New Dynamics 365, Power Platform, and Dataverse roadmap items begin publishing directly to the AI at Work roadmap.
- Fall 2026: Existing roadmap items with Public Preview or General Availability dates on or after June 1, 2026 transition from Release Planner to the AI at Work roadmap.
- By November 15, 2026: Release Planner retires. The AI at Work roadmap becomes Microsoft’s primary destination for public roadmap information.
How this affects your organization
If your organization uses Release Planner,
Release Plans on Microsoft Learn,
or release wave announcements for roadmap planning, you will need to transition to the AI at Work roadmap.
Key changes include:
- Release Planner will retire on November 15, 2026.
-
New Release Plans will no longer be published on
Microsoft Learn beginning
in September 2026. Existing Release Plans will remain available for historical reference.
- The September 2026 Release Wave 2 announcement will not occur because release wave communications are being retired.
- Roadmap information will be published continuously rather than grouped into twice-yearly release wave announcements.
-
Roadmap content will be available
through filtering, CSV export, RSS subscriptions,
and the
Release Communications MCP Server
pulls roadmap information directly into your own AI tools and workflows.
- Personalized saved views from My Release Plans will not migrate to the AI at Work roadmap.
What is not changing
This transition changes how Microsoft communicates roadmap information. It does not change how products are built, released, or deployed.
The following remain unchanged:
- Product release schedules
- Deployment and rollout processes
- Upgrade planning and support lifecycles
- Preview and testing programs
- Message Center notifications, which remain the authoritative source for tenant-specific communications
- Microsoft Learn as the home for product documentation and implementation guidance
What you can do to prepare
-
In September, begin using the AI at Work roadmap as
your primary destination for roadmap planning.
- Review internal processes, documentation, bookmarks, and communications that currently reference Release Planner, Release Plans, or release wave announcements.
-
Configure roadmap filters, RSS subscriptions, and CSV exports
to support your organization’s planning processes.
-
Evaluate the Release Communications MCP Server
if your organization integrates roadmap data into planning workflows or AI tools.
- Continue using Message Center for tenant-specific change notifications and deployment communications.
Additional information
The AI at Work roadmap provides a single destination for roadmap information across Microsoft
business applications, productivity experiences, Copilot, agents, and AI solutions. Organizations
are encouraged to familiarize themselves with the roadmap’s filtering, export, RSS, and MCP
capabilities before September 2026 publishing begins.
|