SharePoint Online monitoring is the continuous measurement of how SharePoint and OneDrive perform for your users: whether sites open, how long files take to load, and what the device, Wi-Fi, ISP and VPN add along the way. It combines scripted tests with measurements taken on each user's device, so you see a slowdown before the helpdesk does.
Most SharePoint complaints arrive the same way: "SharePoint is slow today." No site, no file, no time. The helpdesk checks Microsoft's status page, sees nothing wrong and asks the user to try again later. Meanwhile, colleagues in the same office have stopped reporting it and simply email attachments instead of sharing links.
Why is SharePoint slow for some users and not others?
SharePoint Online runs in Microsoft's cloud, but the experience is built along the whole path between the user and that cloud. A slow page can come from:
- The device: an ageing laptop, a full disk, a browser with forty tabs open
- The local network: busy office Wi-Fi, or a home router at the other end of the flat
- The ISP: one provider in one region having a bad week
- The VPN: traffic sent back through head office before it reaches Microsoft 365
- The page itself: heavy custom pages, very large libraries, web parts that call slow external services
- Microsoft 365: an incident on Microsoft's side, which does happen
To the user, all of these look the same. Without measurements, the helpdesk is left guessing.
What do Microsoft's own tools show?
Start with what you already have. Service health, in the Microsoft 365 admin center, lists the incidents and advisories Microsoft is working on for your tenant, service by service, including issues detected in your own environment that your organisation needs to act on. Check it first during any incident; our guide to Microsoft 365 Service health explains what it shows and which other signals help.
The admin center also scores network connectivity for each office location, once your sites are declared. It is a good view of how well each office reaches Microsoft 365.
Experience monitoring adds the view from each desk and home office: what one user got, on one device, at the moment they complained, and how that compares with their usual experience.
Synthetic tests or real user monitoring for SharePoint?
There are two ways to measure SharePoint from the user's side, and they answer different questions.
Two ways to monitor SharePoint Online
| Compared on | Synthetic tests | Real user monitoring |
|---|---|---|
| How it works | A probe repeats scripted actions around the clock from the sites you choose, such as opening a SharePoint page or a file in a document library. | A light agent on each device measures how quickly SharePoint and OneDrive respond while people work, along with the device, Wi-Fi, ISP and VPN. |
| What it catches | An outage at night, a slow office, a page that got slower after a change. | One user's bad day, an ISP degrading for home workers, a laptop that cannot keep up. |
| What it misses | The user's own device and home connection. | Devices where the agent is not installed. |
| Best for | Availability of key sites and libraries, and comparison over time. | Helpdesk triage and hybrid workers. |
Most organisations need both. Synthetic tests tell you SharePoint is slower than usual before anyone is at their desk. Real user data tells you who is affected and why.
What should you measure?
- Page load time for your most used sites, such as the intranet home page and key team sites
- Time to open and save a typical file in a document library
- Sign-in time, since a slow sign-in is often reported as "SharePoint is slow"
- How OneDrive responds on the devices that rely on it most
- The network path for each user: Wi-Fi, ISP, VPN and corporate network
- Each user's own baseline, so a real degradation stands out from normal variation
Numbers only become useful when you compare them: today against last week, this ISP against the others, this user against their own normal. For the indicators worth tracking across Outlook, Teams and OneDrive as well, see digital employee experience for Microsoft 365.
How do you turn measurements into fewer tickets?
A dashboard does not fix anything on its own. Three habits make the difference:
- Alert the team that can act. A Wi-Fi problem goes to the site network team, an ISP problem to whoever manages the contract, a Microsoft incident to the service desk with a ready-made message for users.
- Give the helpdesk the user's history. Before calling back, the analyst can see whether this user's SharePoint was slower than usual, and since when.
- Review the trend regularly. Look at which sites, ISPs and devices cost people the most time, and fix the top of the list first.
How Neptune helps
Neptune selects and implements the monitoring tools that fit your estate, combining synthetic tests and real user monitoring where it helps. We agree with you which sites, libraries and user groups to watch first, set thresholds with your helpdesk and network teams, and train them to read the results. See our approach to Microsoft 365 monitoring, or read how the same method applies to Teams and Zoom call quality.
