logo
search
Copilot Permission Problems

Fix SharePoint Copilot Agent Reverting to Default Settings

Maira MehtabMaira Mehtab Sep 28, 2026 869 views

Question details

The user is trying to understand why their newly set custom Copilot agent will not stay as the default choice and keeps reverting to the automatically generated SharePoint agent once the browser is reopened.

Product
Microsoft SharePoint
Device & OS
not provided
Scenario
Setting a custom Copilot agent as the default AI assistant for a SharePoint site.
Observed behavior
The custom Copilot agent fails to save as the default preference, automatically reverting back to the default SharePoint agent after the web browser is closed and reopened.
Before you start

Verify that your Microsoft 365 subscription is currently active and check the Microsoft Service Health dashboard to ensure there are no temporary outages affecting SharePoint or Copilot services.

Solution 1Recommended

Assign SharePoint Site Owner Permissions

Only users in the SharePoint Site Owners group have the required administrative privileges to approve an agent and permanently set it as the default.

1
Access Site Settings

Navigate to your SharePoint site, click on the Settings gear icon in the top right corner, and select 'Site permissions'.

2
Check Permission Level

Verify that your user account is listed under the Site Owners group. If you are only a Member or Visitor, you will not be able to save default agent configurations.

3
Request Owner Access

If you lack the necessary permissions, contact your IT administrator to have your account added to the Site Owners group.

4
Reapply the Default Agent

Once owner permissions are granted, navigate back to the Copilot agent settings, select your custom agent, set it as default, and restart your browser to confirm the change has been saved.

Site-Level Configuration Limits: Setting a default Copilot agent only applies at the primary site level. This configuration does not cascade and will not work for SharePoint subsites.
Free Microsoft Office alternative

Try WPS Office for Seamless and Lightweight Productivity

If complex backend permission settings in Microsoft 365 and SharePoint are slowing down your daily workflow, consider switching to WPS Office. It provides a highly compatible, easy-to-use offline and cloud environment for all your document, spreadsheet, and presentation needs without the hassle of complex enterprise configurations.

  1. 1. Visit the Official Site: Go to the official WPS Office website to access the latest version.
  2. 2. Download the Installer: Click on the Free Download button that corresponds to your operating system (Windows, Mac, or Linux).
  3. 3. Install and Edit: Run the installer, open WPS Office, and seamlessly drag and drop your existing Office files to begin working immediately.
Fully compatible with Microsoft Office formats, including .docx, .xlsx, and .pptx.Features a built-in AI assistant (WPS AI) to help you write, summarize, and analyze data efficiently.Lightweight installation with a familiar, easy-to-navigate interface for quick onboarding.Completely free core features, making it an excellent alternative for personal and team productivity.
microsoft office alternative - wps office

Frequently Asked Questions

Why does my Copilot default setting work on the main SharePoint site but not on subsites?

Microsoft currently restricts the default Copilot agent configuration to the root site level. Setting a default agent does not apply to or inherit down to any subsites created under the main site.

Do I need to be a Site Owner to use a custom Copilot agent in SharePoint?

You do not necessarily need to be a Site Owner to use an agent if it has been shared with you, but you must be a member of the SharePoint Site Owners group to approve an agent and permanently set it as the default for the site.

What should I do if clearing my browser cache doesn't stop the agent from reverting?

If clearing your cache, trying alternative browsers, and verifying your Site Owner permissions does not fix the issue, you should ask your Microsoft 365 admin to open a support ticket with Microsoft to investigate potential backend service errors.