Public mode

No tenant, Graph, or device access. Every item links to its source. What this means

Some sources or documents need attention: 253/255 feeds/APIs · 417/444 docs · checked 13:25 UTC Customize Public modeDiscuss ChangeIntel on Discord

Microsoft SharePoint: Retirement of SharePoint Page Agent (Frontier)

Versions captured by this deployment. Earlier versions and notices may be missing; first observed is not first published.

Action date

Microsoft tags this a retirement but gives no action date in the notice metadata. Any date is in the text below.

Microsoft's start date
29 Sep 2026
Last changed by Microsoft
29 Sep 2026
First seen here
19 Oct 2026
Versions seen
1

What the notice says

Microsoft's text, with its sections, lists and tables; source markup removed

What and why

Microsoft will retire the SharePoint Page Agent (Frontier) for SharePoint Online. This early access experience enabled users to turn content from Microsoft 365 Copilot conversations into draft SharePoint pages and news posts.

As Microsoft continues to invest in AI-powered content creation experiences, page and news authoring capabilities are now available directly within SharePoint through Copilot in SharePoint. Users can create and refine content directly within the SharePoint authoring experience.

Rollout schedule

  • Retirement (Frontier preview): Beginning in mid-October 2026 and expected to complete in mid-November 2026

Impact on your organization

Who is affected

  • Organizations that have users creating SharePoint pages or news posts through the SharePoint Page Agent (Frontier) in Microsoft 365 Copilot
  • SharePoint authors who currently initiate page creation from Microsoft 365 Copilot conversations

Platforms and services

  • Microsoft 365 Copilot
  • SharePoint Online
  • Copilot in SharePoint

What will happen

  • The SharePoint Page Agent (Frontier) will no longer be available in Microsoft 365 Copilot after retirement is complete.
  • Users will no longer be able to start new page or news-post authoring interactions through the SharePoint Page Agent.
  • Existing SharePoint pages and news posts previously created through the SharePoint Page Agent will remain available in their SharePoint sites.
  • Existing SharePoint permissions and lifecycle policies for previously created content will continue to apply.
  • Eligible users can continue creating and refining SharePoint pages and news posts using Copilot in SharePoint.
  • No migration of existing content is required.

Action required and recommendations

To prepare for this retirement:

  • Notify SharePoint authors that the SharePoint Page Agent will be retired beginning in mid-October 2026.
  • Direct users to create and refine SharePoint pages and news posts using Copilot in SharePoint.
  • Update internal documentation, training materials, support content, and bookmarks that reference the SharePoint Page Agent or its Microsoft Marketplace listing.
  • Review internal publishing workflows and guidance to ensure they reference the supported authoring experience.
  • Remind authors to review AI-generated content for accuracy, completeness, and compliance with your organization's publishing standards before publishing.

Learn more

Compliance considerations

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

What changed

Between the versions this installation saw, newest first

This installation has seen one version of this notice, first on 19 Oct 2026. Later changes will show here.

Linked documentation

Microsoft pages the notice links to

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
  • Versions before 19 Oct 2026: this installation first saw the notice after Microsoft posted it.
  • 1 linked page has not been read yet.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 19 Oct 13:25 UTC · 253 of 255 readable · 252 fully read · documentation 417/444 current