Is SharePoint Down? Check Outage and Status

To find out whether SharePoint is down, ask your Microsoft 365 administrator to check Service health in the Microsoft 365 admin center. A confirmed SharePoint outage appears there as an active incident or advisory; reports from coworkers or outage-tracking sites alone do not confirm a Microsoft service problem.

If you are asking “is SharePoint down right now,” first record the exact error and check whether the problem affects other people, devices, and networks. These checks help separate a broad SharePoint service outage from a browser, connection, account, permission, or organization-specific issue.

How do you check the current SharePoint status?

The official source for an organization’s SharePoint service status is the Service health area of the Microsoft 365 admin center. Service health is Microsoft’s administrator view of incidents and advisories that may affect an organization’s services.

1. Ask an authorized Microsoft 365 administrator to open the admin center.
2. In the Health area, select Service health.
3. Look for an active incident or advisory involving SharePoint Online or a related Microsoft 365 service.
4. Open the notice and compare its listed symptoms and affected services with what users are experiencing.
5. Check the notice again later for Microsoft’s updates and confirmation that service has been restored.

A matching active notice is evidence of a confirmed SharePoint outage. If Service health shows no matching notice, the report remains unverified. That does not prove SharePoint is working normally for every user: a new incident may not yet be posted, or the problem may affect only one organization, location, account, or site.

Public reports can reveal that other people are having trouble, but they may combine unrelated problems and cannot replace the official SharePoint service status available to administrators.

Is SharePoint down for everyone or just you?

Run a few quick checks without changing security settings or removing managed software. Stop if your organization’s policies do not allow a particular test.

1. Open the same SharePoint page in another supported browser or a private browsing window. If it works there, stored browser data or an extension may be involved.
2. Try an organization-approved second device. A result on one device only points toward a local device or browser problem.
3. Switch between approved networks, such as your usual office connection and a permitted mobile connection. If only one network fails, report that detail to your administrator or IT team.
4. Open another Microsoft 365 service you normally use. If several services fail, the issue may involve sign-in, the network, or a wider Microsoft 365 incident.
5. Ask a coworker with legitimate access to the same SharePoint site whether the same action fails. Do not ask anyone to share credentials or files.

If many authorized users see the same error across browsers, devices, and networks, a SharePoint outage is more likely. If the failure follows one account, device, network, site, or file, give that pattern to the administrator for investigation.

What are common signs of a SharePoint outage?

Possible signs of a SharePoint service outage include:

• SharePoint pages remain blank, time out, or fail to load.
• Sign-in repeatedly fails or returns an unexpected error.
• Synced libraries show errors, remain pending, or stop updating.
• Files or folders that were previously visible appear to be missing.
• Opening, saving, uploading, or downloading a file fails.
• An access-denied or permission message appears unexpectedly.
• Search, lists, or site features do not return expected results.

These symptoms do not identify the cause by themselves. Missing files can result from synchronization delay, a changed view, or permissions; access-denied messages can reflect account or policy changes. Record the symptom before concluding that a SharePoint outage today is responsible.

What should you do during a SharePoint outage?

1. Save the exact error message, time, site name, affected file or library, and the action that failed. Take a screenshot if organizational policy permits it.
2. Check messages from your Microsoft 365 administrator, IT help desk, or internal status channel for instructions.
3. Avoid repeated uploads, moves, renames, permission changes, or retries. Repeated changes can create conflicts or make later review harder.
4. Do not delete a local file because it appears missing online. Keep the file in its approved location until synchronization and access are checked.
5. Use an approved offline copy only when one is already available and organizational rules permit offline work. Keep track of edits so they can be reviewed after restoration.
6. Protect sensitive information. Do not move work to a personal account, unapproved storage service, or unauthorized device to work around the outage.

If the official notice provides a workaround, follow the version shared by your administrator. Do not weaken security controls or bypass your organization’s administrator while waiting for SharePoint service status updates.

When should you contact your Microsoft 365 administrator or support?

Contact your organization’s administrator or IT help desk when multiple users are affected, another Microsoft 365 service also fails, important work is blocked, or an unexpected permission or missing-file problem continues. Also report the issue when the official status does not mention your symptoms but your checks show a repeatable failure.

Include your account identifier, device and browser type, approximate time, site or library name, exact error text, and the tests you completed. Never send a password, verification code, recovery code, or confidential file unless your organization has an approved secure process.

Authorized administrators can review diagnostics and Service health in the Microsoft 365 admin center. If the problem is not covered by an active notice, an administrator can open a support request through the center and provide tenant-specific details. Regular users should use their organization’s support route rather than trying to represent the organization directly.

What should you do after SharePoint service is restored?

1. Sign in again through your organization’s normal approved method.
2. Reload the affected SharePoint page and retry one action before repeating a larger batch of work.
3. Allow synced libraries time to refresh, then review any conflict or error messages.
4. Check recent files and edits to confirm that uploads, saves, moves, and renames completed as expected.
5. Compare approved offline edits with the restored online copy before replacing or merging content.
6. Report files, pages, or permissions that remain unavailable, even if the general SharePoint status says the incident is resolved.

Service restoration does not always resolve every local sync or permission problem immediately. Preserve error details and contact your administrator if the same issue continues after a fresh sign-in and a careful retry.