Use Correlation IDs in SharePoint Support Requests: Practical Checklist for SharePoint Owners

When a SharePoint page fails to load, a document library stops syncing, or a permission change does not take effect, the error message often contains a long string of letters and numbers called a Correlation ID. Many site owners ignore this code because they do not know what it means or how to use it. A Correlation ID acts as a pointer that lets Microsoft support engineers locate the exact server log entry for a failed request. This article explains what a Correlation ID is, why it matters for troubleshooting, and provides a practical checklist you can follow to collect and submit Correlation IDs in your support requests.

What Is a Correlation ID and Why Does SharePoint Generate One

A Correlation ID is a unique GUID that SharePoint assigns to every HTTP request that passes through the server. When you open a site, upload a file, or change a permission, SharePoint logs the details of that request — including the user, the time, the URL, and any errors — and tags it with a Correlation ID. The ID is generated by the SharePoint Unified Logging Service (ULS) and is stored in the ULS trace logs on the server.

The purpose of the Correlation ID is to link a user-facing error to the corresponding server-side log entry. Without it, support engineers would have to search through millions of log entries by time and user, which is slow and unreliable. With the Correlation ID, they can jump directly to the request that failed and see the exact exception, stack trace, and surrounding context.

Correlation IDs appear in several places: in the browser error page, in the SharePoint ULS logs, in the Windows Event Viewer on the SharePoint server, and in diagnostic tools like Fiddler or the browser developer tools. For SharePoint Online, the Correlation ID is visible in the error page and in the browser network traffic, but the ULS logs are not accessible to end users. For SharePoint Server, you can access the ULS logs directly on the server.

Where Correlation IDs Appear in SharePoint Online

In SharePoint Online, the most common place to see a Correlation ID is the error page that appears when a request fails. The error page shows a message like “Sorry, something went wrong” followed by a technical detail section that includes the Correlation ID. You can also find the Correlation ID by opening your browser’s developer tools, reloading the page, and inspecting the network requests. Look for the request that returned a 500 or 400 status code, then check the response headers for the field named “SPRequestGuid” or “X-SharePointHealthScore.”

Where Correlation IDs Appear in SharePoint Server

In SharePoint Server, the Correlation ID appears in the same error page as in Online. Additionally, the ID is recorded in the ULS trace logs located on the server at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\16\LOGS. You can also find it in the Windows Application Event Log under the source “SharePoint Foundation” or “SharePoint Server.”

Checklist: Steps to Collect and Submit a Correlation ID in a Support Request

Follow this checklist each time you experience a SharePoint error that you need to escalate to Microsoft support. Each step is independent, so you can start with the method that is most convenient for you.

1. Capture the Correlation ID from the error page
   When the error page appears, look for a section labeled “Correlation ID” or “Technical Details.” The ID is a 32-character hexadecimal string grouped in five sections, for example: a1b2c3d4-e5f6-7890-abcd-ef1234567890. Copy the entire string to a text file or note. If the error page does not show the ID, move to the next step.
2. Open browser developer tools (F12) and reload the page
   Press F12 to open the developer tools. Click the Network tab. Reload the page or repeat the action that caused the error. Find the request that failed — look for a red entry or a status code starting with 4 or 5. Click the request, then go to the Headers tab. Look for the response header named “SPRequestGuid” or “X-SharePointHealthScore.” The value of SPRequestGuid is the Correlation ID. Right-click the header and select Copy Value.
3. Check the Microsoft 365 admin center Service Health
   Go to the Microsoft 365 admin center at admin.microsoft.com. Navigate to Health > Service Health. Look for any active advisory or incident that mentions SharePoint. If you find an incident, note the incident ID. Microsoft support may ask for both the Correlation ID and the incident ID to confirm that your issue is related to a known service problem.
4. Collect the exact time and time zone of the error
   Record the date and time the error occurred, including your time zone. Support engineers use the time to narrow the log search window. Use a 24-hour format for clarity, for example: 2025-03-18 14:35 UTC.
5. Record the full URL and the action you performed
   Write down the complete URL of the page where the error occurred. Describe the exact action you took — for example, “clicked the Upload button on the Documents library at https://contoso.sharepoint.com/sites/marketing/Shared%20Documents.” Include the name of the library, list, or page.
6. Open the ULS log on the SharePoint server (on-premises only)
   If you are using SharePoint Server, navigate to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\16\LOGS on the server. Open the most recent log file that matches the time of the error. Search for the Correlation ID you captured. The log entry shows the exception type, stack trace, and the component that failed. Copy the relevant section of the log to a text file.
7. Create a support request in the Microsoft 365 admin center
   Go to the Microsoft 365 admin center and navigate to Support > New Service Request. In the description, paste the Correlation ID, the exact time, the URL, and the action you performed. Attach any log files you collected. Select the severity level that matches the impact.

Common Mistakes When Using Correlation IDs in Support Requests

I submitted the wrong Correlation ID from a different request

A common error is copying the Correlation ID from a successful request instead of the failed one. In the browser developer tools, a successful request returns a 200 status code and is not the source of the error. Only requests with a 4xx or 5xx status code contain the Correlation ID for the failure. Always verify the status code before copying the ID.

My Correlation ID is missing from the error page

In some SharePoint Online errors, the error page may not display the Correlation ID. This usually happens when the error occurs before SharePoint can generate a log entry — for example, a network timeout or a reverse proxy error. In that case, check the browser developer tools for the SPRequestGuid header. If the header is also missing, the issue is likely at the network or DNS level, not within SharePoint. Contact your network team first.

I submitted a support request without the Correlation ID

Submitting a support request without a Correlation ID forces the support engineer to search logs manually, which delays the resolution. If you cannot find the Correlation ID, provide the exact time, user account, and URL. The engineer can then run a ULS log query on the server side, but this takes longer. Always try to capture the Correlation ID first.

Item	SharePoint Online	SharePoint Server
Correlation ID visible on error page	Yes	Yes
Access to ULS logs	No (Microsoft manages logs)	Yes (on the server)
Browser developer tools method	Works (SPRequestGuid header)	Works (SPRequestGuid header)
Service Health dashboard available	Yes	No
Typical support response time with ID	1-4 hours	1-2 hours (if logs provided)

Now you can collect a Correlation ID from any SharePoint error using the browser developer tools and the error page. The next time you open a support request, include the Correlation ID, the exact time, the URL, and the action you performed. For SharePoint Server, also attach the relevant section of the ULS log. This checklist reduces the back-and-forth with support and helps resolve issues faster.