MC1481325: SharePoint Retires Page Agent (Frontier) and Shifts Authoring to Copilot in SharePoint

MWPRO IMPACT SCORE
OPERATIONAL IMPACT
53
0 25 50 75 100
HIGH IMPACT • REVIEW RECOMMENDED
Recommended Action:
Review the update and plan any required actions before rollout.
▶ What is MWPro Impact Score? Watch our 60‑second explainer

Primary Audience

SharePoint AdminsMicrosoft 365 AdminsIT ManagersService OwnersEnd Users
Why this score?
AI Confidence
HIGH
Enough detail is available to trust this assessment.
Assessment Reasoning
Microsoft is retiring the SharePoint Page Agent (Frontier) preview between mid-October and mid-November 2026. Admins should ensure communication and training updates as page authoring shifts to Copilot in SharePoint. There is no migration required, but documentation and user guidance must be updated. The impact is mainly operational for SharePoint authors and admin communication rather than technical change.
60
🛡️ Admin Impact
40
👥 User Impact
55
⚡ Urgency
45
🔧 Effort
ℹ️ WHAT YOU NEED TO KNOW
📌

AT A GLANCE

The SharePoint Page Agent (Frontier) used in Microsoft 365 Copilot will be retired. SharePoint authors should now use Copilot in SharePoint for page and news authoring.
👥

END USERS

Users will no longer be able to create pages or news posts through the SharePoint Page Agent.
🛡️

IT ADMINS

Inform authors about the retirement, update documentation and workflows, and direct users to Copilot in SharePoint.
📅

ROLLOUT TIMELINE

Upcoming:
Mid-October 2026

📢 Official Microsoft Message Center Announcement


Microsoft SharePoint: Retirement of SharePoint Page Agent (Frontier)
Message ID: MC1481325

[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.

Source: Microsoft Message Center • Analysed by MWPro

Share This Update