• Feature: Microsoft Copilot Pages (Loop collaborative canvas in Copilot Chat)
• Rollout Timeline: Late August to Early September 2026 (Worldwide GA)
• Admin Action Required: None (Client-side UX update)
• Security & Compliance: 100% Unchanged (OneDrive/SharePoint storage, DLP & eDiscovery retained)
Microsoft Copilot Pages is a dynamic, collaborative canvas inside Microsoft 365 Copilot Chat that allows enterprise teams to transform transient AI chat answers into persistent, shareable Microsoft Loop components. Starting late August through early September 2026, Microsoft is updating how users create and reference these Pages across their workflow.
Microsoft is scoping the "Edit in Pages" control in Copilot Chat to creation only. As of the GA rollout window closing the first week of September 2026, browsing and re-opening an existing Copilot Page no longer happens through that dropdown — it happens through the "/" slash-command menu in the prompt box or the Library tab. This is Message Center post MC1466760, and it's a pure client UX change with zero admin toggles attached.
What's Changing
Today, the "Edit in Pages" menu in Microsoft 365 Copilot and Copilot Chat does double duty: it creates a brand-new Page and it surfaces/edits existing Pages the user has previously generated. After the rollout described in MC1466760, that menu is scoped to net-new Page creation only. Discovery and insertion of existing Pages moves to two dedicated surfaces:
- The Library tab — now the primary browse surface for all previously created Pages.
- The "/" slash-command menu inside the Copilot prompt box — a fast inline picker to reference or re-open an existing Page mid-conversation.
Microsoft's stated wording is explicit that this is cosmetic/workflow-only: "No existing Pages, content, or sharing permissions will be affected." Pages remain Loop components physically backed by files in the creating user's OneDrive or the relevant SharePoint site, and every existing sharing link, sensitivity label, DLP policy, and eDiscovery hold continues to apply exactly as it does today.
Before vs. After Workflow Comparison
| Capability | Today (Before September 2026) | Starting Rollout (After) |
|---|---|---|
| Creating New Pages | "Edit in Pages" menu in chat | "Edit in Pages" menu (Dedicated exclusively to creation) |
| Finding Existing Pages | "Edit in Pages" dropdown menu | Library Tab (Primary browsing hub) |
| Referencing Mid-Chat | Manual search or re-creating page | "/" Slash Menu directly inside prompt box |
| Permissions & DLP | Inherited from OneDrive / SharePoint | Unchanged — identical security and retention policies |
Who's Affected & When
This applies to every tenant with users licensed for Microsoft 365 Copilot or the Microsoft 365 Copilot Chat (pay-as-you-go / free) SKU, across Word, Teams, Outlook, and the standalone Copilot Chat experience at m365.cloud.microsoft. Per the roadmap entry, this is a straight General Availability, Worldwide rollout — there is no Targeted Release or preview ring gating it.
| Attribute | Value |
|---|---|
| Message Center ID | MC1466760 |
| Rollout start (UTC) | 2026-09-03T23:00:28Z |
| Phase | GA — Worldwide (no preview ring) |
| Severity | Normal / informational |
| Opt-out available | ✗ No |
| Admin toggle / policy | ✗ None exists |
| Impacts Pages content or permissions | ✗ No change |
What This Means for Your Environment
Nothing changes at the tenant configuration layer — no Graph endpoint, no CSV/report schema, no Purview audit record structure is modified. The CopilotInteraction record type in the Unified Audit Log continues to log Page-related operations exactly as before. What breaks is tribal knowledge and documentation: any adoption deck, Viva Learning module, or intranet quick-reference screenshot showing "Edit in Pages > browse my existing Pages" is now factually wrong. If your organization has trained users to rely exclusively on that dropdown for reopening Pages, expect a spike in "where did my Page go?" help desk tickets in the first two weeks of September.
Third-party adoption-tracking browser extensions or governance tools that scrape Copilot UI text/DOM selectors for the old "Edit in Pages" browse flow may also silently stop matching — check with any vendor providing Copilot usage dashboards built on UI scraping rather than the Graph reporting API.
Action Items
- Pull a usage baseline before the cutover. Run a Unified Audit Log query for
CopilotInteractionrecords withPageCreated/PageEditedoperations to quantify how many users are actively creating Pages — this tells you who needs proactive comms. - Confirm Message Center receipt. Validate that MC1466760 has posted to your tenant and hasn't had its dates revised.
- Update training artifacts. Any screenshot or SOP referencing "Edit in Pages" as a browse mechanism needs a Library tab / "/" menu correction.
- Push a short Copilot champion notice. One paragraph: "Edit in Pages now only creates new Pages. Use / or the Library tab to reopen an existing one."
- No technical remediation required. Confirm with your security/compliance team that no DLP, sensitivity label, or sharing-link review is triggered — this is UI-only.
# Required Scopes: AuditLog.Read.All (Graph) / View-Only Audit Logs (EXO RBAC)
# Requires Exchange Online Management module for Search-UnifiedAuditLog
# Run BEFORE the Sep 2026 cutover to baseline Copilot Pages usage
#region Connect
Connect-ExchangeOnline
#region Baseline audit pull - last 30 days of Page activity
$startDate = (Get-Date).AddDays(-30)
$endDate = Get-Date
$results = @()
$sessionId = "CopilotPagesAudit-$(Get-Date -Format yyyyMMddHHmm)"
try {
do {
$batch = Search-UnifiedAuditLog `
-StartDate $startDate `
-EndDate $endDate `
-RecordType CopilotInteraction `
-Operations "PageCreated","PageEdited" `
-SessionId $sessionId `
-SessionCommand ReturnLargeSet `
-ResultSize 5000
if ($batch) { $results += $batch }
} while ($batch.Count -eq 5000)
$results |
Select-Object CreationDate, UserIds, Operations, AuditData |
Export-Csv -Path .\CopilotPagesActivity_Baseline.csv -NoTypeInformation
Write-Output "Exported $($results.Count) Copilot Pages events to CSV."
exit 0
}
catch {
Write-Error "Audit pull failed: $($_.Exception.Message)"
exit 1
}
# Required Scopes: User.Read.All, Organization.Read.All (Microsoft Graph)
# Enumerate users assigned a Copilot license SKU to scope comms distribution list
#region Connect via Microsoft.Graph v2 (NOT AzureAD/MSOnline - deprecated)
Connect-MgGraph -Scopes "User.Read.All","Organization.Read.All" -NoWelcome
try {
# Common SKU part numbers: Microsoft_365_Copilot, Copilot_Chat
$copilotSkuNames = @("Microsoft_365_Copilot", "Copilot_Chat")
$licensedUsers = Get-MgUser -All -Property Id,DisplayName,UserPrincipalName,AssignedLicenses |
Where-Object {
$_.AssignedLicenses.SkuId | ForEach-Object {
(Get-MgSubscribedSku -All | Where-Object SkuId -eq $_).SkuPartNumber -in $copilotSkuNames
}
}
$licensedUsers |
Select-Object DisplayName, UserPrincipalName |
Export-Csv -Path .\CopilotLicensedUsers_ForComms.csv -NoTypeInformation
Write-Output "Exported $($licensedUsers.Count) Copilot-licensed users."
exit 0
}
catch {
Write-Error "Graph enumeration failed: $($_.Exception.Message)"
exit 1
}
# Change-management validation helper (no Graph/EXO dependency)
# Confirms MC1466760 acknowledgement + produces adoption report stub
function Test-MC1466760Readiness {
[CmdletBinding(SupportsShouldProcess)]
param(
[Parameter(Mandatory)][string]$MessageCenterId = "MC1466760",
[Parameter(Mandatory)][string]$OutputPath = ".\MC1466760_AdoptionReport.md"
)
try {
$checklist = [ordered]@{
"MessageCenterPostReviewed" = $false
"TrainingDocsAudited" = $false
"ChampionNoticeSent" = $false
"UsageBaselineCaptured" = $false
"ThirdPartyToolsValidated" = $false
}
if ($PSCmdlet.ShouldProcess($OutputPath, "Generate adoption report")) {
$report = @"
# Copilot Pages UX Change - Adoption Readiness Report
**Message Center ID:** $MessageCenterId
**Generated:** $(Get-Date -Format u)
| Checklist Item | Status |
|---|---|
$(($checklist.GetEnumerator() | ForEach-Object { "| $($_.Key) | $($_.Value) |" }) -join "`n")
**Next review date:** $((Get-Date).AddDays(7).ToString('yyyy-MM-dd'))
"@
$report | Out-File -FilePath $OutputPath -Encoding utf8
Write-Output "Report generated at $OutputPath"
}
exit 0
}
catch {
Write-Error "Report generation failed: $($_.Exception.Message)"
exit 1
}
}
# Test-MC1466760Readiness -WhatIf
Original announcement: Microsoft 365 admin center → Health → Message Center → MC1466760.