Others

Fix Microsoft 365 Connector Stuck on Loading Screen in SharePoint

Huma Ashraf ChHuma Ashraf Ch Oct 9, 2026 871 views

Question details

The Microsoft 365 or Office 365 Connectors web part is stuck on the loading screen and does not display any content.

How to Fix a Microsoft 365 Connector That Is Stuck Loading
Product
Microsoft 365
Device & OS
not provided
Scenario
A user is trying to view a SharePoint page that contains an Office 365 Connectors web part, but the component fails to load data.
Observed behavior
The web part remains continuously stuck in a loading state, taking longer than the expected 40 seconds without displaying the connected content.
Before you start

Verify that your internet connection is stable and ensure you have the appropriate permissions to view the connected data source on the SharePoint page.

Solution 1Recommended

Perform Basic Web Part and Browser Troubleshooting

Use these quick methods to rule out browser cache issues and temporary connection glitches.

In many cases, the Office 365 Connectors web part simply requires extra time to fetch data, or the browser cache might be preventing it from loading properly. Testing different browser environments helps isolate the root cause.

1
Wait for the connector to load

Leave the SharePoint page open for a few minutes. The connector may take approximately 40 seconds or longer to fully process and load its content.

2
Test in a private browser window

Open a Private or Incognito browsing window (Ctrl+Shift+N in Chrome/Edge) and log back into your SharePoint page to bypass any cached data.

3
Try a different web browser

Switch to an entirely different browser, such as Firefox, Edge, or Chrome, to check if the loading issue is isolated to your primary browser.

4
Remove and re-add the web part

Click 'Edit' on the top right of your SharePoint page, delete the stuck Office 365 Connectors web part, and then insert a fresh one to reset the module.

Perform Basic Web Part and Browser Troubleshooting
Normal Loading Times: Do not refresh the page immediately if it seems slow; standard behavior for this specific connector often involves a slight delay before data appears.
Free Microsoft Office alternative

Discover WPS Office for Your Daily Productivity

While SharePoint connector loading issues require intervention from Microsoft support, you can switch to WPS Office for a fast, reliable, and hassle-free document editing experience. It is a powerful suite that meets all your daily productivity needs.

  1. 1. Download the installer: Visit the official WPS website and download the free installation package for your operating system.
  2. 2. Install the software: Run the downloaded file and follow the simple on-screen prompts to complete the installation.
  3. 3. Open your files instantly: Launch WPS Office and directly open your existing Microsoft Office documents without worrying about format conversion.
Seamlessly compatible with Microsoft Word, Excel, and PowerPoint formats (.docx, .xlsx, .pptx).Extremely lightweight installation that ensures fast loading times without system lag.Familiar ribbon-style user interface that makes switching incredibly easy.Free to use, including a comprehensive built-in PDF reader and editor.
microsoft office alternative - wps office

Frequently Asked Questions

Why does the Office 365 Connectors web part take so long to load?

This web part pulls live data from external services and applications, which inherently takes longer to process. It is completely normal for it to take 40 seconds or more to display content.

Can cached browser data cause a web part to get stuck?

Yes, corrupted or outdated browser cache can prevent SharePoint web parts from executing their scripts correctly. Testing in a Private/Incognito window helps determine if this is the cause.

What should I do if removing and re-adding the web part doesn't work?

If removing and re-adding the web part does not resolve the issue, it is highly recommended to have your Microsoft 365 administrator submit a support ticket via the Admin Center, as it may be a backend service degradation.