Others

Troubleshoot Office 365 Connectors Failing to Save

Ayan MasoodAyan Masood Oct 10, 2026 869 views

Question details

The user is unable to save Office 365 connectors after entering a name, resulting in a consistent failure across all connectors.

Troubleshoot Office 365 Connectors That Fail to Save
Product
Office 365
Device & OS
not provided
Scenario
Setting up and attempting to save configurations for Office 365 connectors.
Observed behavior
All Office 365 connectors fail immediately after a connector name is entered and the Save button is clicked.
Before you start

Ensure you have Microsoft 365 tenant administrator permissions, as you will need elevated access to check the global service health and submit official support requests.

Solution 1Recommended

Check Service Health and Escalate with HAR Logs

Verify if there is an ongoing Microsoft service outage and collect network logs to help the Microsoft support team investigate the tenant-specific failure.

When all connectors across a tenant fail to save simultaneously, it highly indicates a backend service problem or a tenant-wide bug rather than a user error. Identifying active incidents or providing browser network data is the most effective way to resolve this.

1
Check the Service Health Dashboard

Log in to the Microsoft 365 admin center using your administrator credentials. Navigate to Health, then click on Service health to see if there are any known incidents affecting connectors.

2
Collect Browser HAR Logs

If the dashboard shows no related incidents, open your web browser's Developer Tools by pressing F12. Go to the Network tab, ensure 'Preserve log' is checked, and attempt to save the connector again to capture the failure. Right-click the network activity and select 'Save all as HAR with content'.

3
Open a Microsoft Support Request

Return to the Microsoft 365 admin center, navigate to Support, and click New service request. Describe the issue stating that all connectors fail to save, and attach your exported HAR logs so the development team can investigate.

Check Service Health and Escalate with HAR Logs
Administrator Privileges Required: Only users with the appropriate administrator roles can access the service health dashboard or open support requests on behalf of the tenant.
Free Microsoft Office alternative

Experience Seamless Productivity with WPS Office

If you are encountering recurring issues with cloud services or simply looking for a reliable, fast, and free productivity suite, WPS Office provides an outstanding alternative. It delivers essential tools for document creation, spreadsheets, and presentations without the heavy resource usage of other platforms.

  1. 1. Download the Installer: Visit the official WPS Office website and download the free installer for Windows, Mac, or Linux.
  2. 2. Install WPS Office: Run the downloaded file and follow the quick setup wizard to install the software on your device.
  3. 3. Edit Your Documents: Launch WPS Office to immediately open, edit, and save your existing Word, Excel, and PowerPoint files natively.
Highly compatible with Microsoft Office formats, including .docx, .xlsx, and .pptx.Lightweight installation that ensures fast performance even on older hardware.Free to use with a familiar, tabbed interface that requires zero learning curve.Built-in PDF editing tools for easy document conversion and management.
microsoft office alternative - wps office

Frequently Asked Questions

What is an Office 365 connector?

Office 365 connectors are integrations that deliver content and updates from third-party services directly into Microsoft 365 groups or Microsoft Teams channels, keeping your team informed in a centralized location.

How do I ensure my HAR log captures the connector error?

Make sure you open the Network tab in Developer Tools (F12) before clicking the 'Save' button. Check the 'Preserve log' box so the browser doesn't clear the network requests if it redirects after the error occurs.

Why do I need to open a support ticket for connector failures?

When multiple or all connectors fail consistently upon saving, it usually points to a tenant-level synchronization issue or an unlisted service outage that only Microsoft's backend engineering teams can resolve.