Use Correlation IDs in SharePoint Support Requests: Best Settings for Microsoft 365

When you submit a support request for SharePoint Online, Microsoft support engineers often ask for a Correlation ID. This is a unique identifier tied to a specific failed operation in the SharePoint system. Without it, support teams cannot trace the exact error logs, server events, and user actions that caused the problem. This article explains how to find Correlation IDs in SharePoint, what settings you should configure in Microsoft 365 to make them more useful, and how to include them in your support requests for faster resolution.

What Is a Correlation ID and Why Does It Matter for Support?

A Correlation ID is a GUID (Globally Unique Identifier) that SharePoint Online generates for every request that hits the server farm. When an error occurs, the system records the ID along with the exact time, user context, and the code path that failed. Microsoft support engineers use this ID to pull up the corresponding logs from thousands of servers in the Microsoft 365 datacenter.

Without a Correlation ID, support engineers must rely on generic error descriptions and timestamps, which often point to multiple possible causes. This slows down diagnosis and can lead to incorrect root cause identification. By providing a Correlation ID, you give the support team a direct link to the exact failure point, reducing resolution time from days to hours.

Correlation IDs are also valuable for internal troubleshooting. If you manage SharePoint sites, you can use them to correlate user-reported issues with server-side events in the Microsoft 365 admin center or through PowerShell scripts.

How SharePoint Generates a Correlation ID

When a user makes a request to SharePoint Online — such as loading a page, uploading a file, or running a search — the request passes through a load balancer, a web front end, and an application server. Each component adds its own logging information, but the Correlation ID stays constant across all hops. This allows the support team to reconstruct the entire request path.

What Information a Correlation ID Contains

The ID itself is a 32-character hexadecimal string, for example: 5f8a1b2c-3d4e-5f6a-7b8c-9d0e1f2a3b4c. It does not contain any user data or site content. It is purely an identifier for the request transaction. The associated logs include the user name, the site URL, the HTTP method (GET or POST), the response status code, and the module that threw the exception.

Steps to Find and Use a Correlation ID in SharePoint Support Requests

1. Capture the Correlation ID from an error page
   When SharePoint shows a red error banner or a full-page error, the Correlation ID appears at the bottom of the error message. It is often labeled “Correlation ID” or “Correlation:” followed by the GUID. Copy the entire string exactly, including hyphens. Do not close the browser tab until you save the ID.
2. Use the F12 Developer Tools to capture IDs for intermittent errors
   Open the browser developer tools by pressing F12. Go to the Network tab and reload the page or repeat the action that fails. Look for requests with a red status code (400, 401, 403, 500, etc.). Click the failed request, go to the Response Headers section, and find the sprequestguid or X-SharePointHealthScore header. The Correlation ID is often in the sprequestguid field. Copy the value.
3. Enable verbose diagnostic logging in the SharePoint admin center
   Go to SharePoint admin center > Health > Diagnostic logs. Under Log collection, select the site collection or tenant scope. Set the log level to Verbose. This ensures that every operation writes a log entry with a Correlation ID. Note that verbose logging generates large amounts of data, so enable it only when you are actively troubleshooting.
4. Collect the ID from a failed workflow or Power Automate flow
   When a SharePoint workflow or a Power Automate flow fails, open the flow run history. In the error details, look for a field named correlationId or runId. Copy this value. For classic SharePoint workflows, use the Workflow Status page and check the error message for the ID.
5. Use the Microsoft 365 admin center to retrieve logs for a specific user
   Go to Microsoft 365 admin center > Health > Service health. Select the SharePoint Online service. Under Recent issues, find the incident that matches your error. Open the incident and look for Correlation IDs that Microsoft has already collected. You can also use the Message center to find IDs tied to known issues.
6. Submit the Correlation ID in your support request
   When creating a support ticket in the Microsoft 365 admin center, include the Correlation ID in the description field. Also provide the exact date and time (including time zone) when the error occurred, the affected site URL, and the user account that encountered the error. This combination allows the support engineer to find the logs immediately.

If the Support Team Needs More Information

Sometimes a single Correlation ID is not enough. Microsoft support may ask for multiple IDs from the same user session or from a specific time window. This is common when the error is caused by a race condition or a transient service degradation. In that case, collect IDs from several failed attempts and provide the full list.

SharePoint Fails But No Correlation ID Appears

If the error page does not show a Correlation ID, the failure likely occurred before SharePoint could generate one. This can happen when the browser cannot reach the server, or when a proxy or firewall blocks the request. Check the browser console for network errors and verify that the site URL is correct. If the problem is on the client side, the support team cannot use a Correlation ID.

Correlation ID Points to a Known Issue

After you submit the ID, Microsoft support may tell you that the error matches a known service incident. In that case, they will provide a service health advisory with an estimated resolution time. You do not need to perform any additional troubleshooting. The Correlation ID allowed them to match your issue to the existing incident without further investigation.

Correlation ID Expires or Is Not Found

SharePoint Online retains diagnostic logs for a limited period, typically 14 to 30 days. If you try to use a Correlation ID from an error that occurred more than 30 days ago, the logs may have been purged. Always capture the ID as soon as the error happens. For long-running investigations, enable verbose logging and export logs to Azure Log Analytics for longer retention.

Methods to Capture Correlation IDs: Browser vs PowerShell vs Admin Center

Method	When to Use	Pros	Cons
Browser error page	User sees a visible error	No tools needed, immediate capture	Only works for full-page errors, not for partial failures
F12 Developer Tools	Intermittent or silent failures	Captures IDs for any HTTP error	Requires technical skill to interpret headers
SharePoint admin center diagnostic logs	Proactive monitoring of site operations	Captures IDs for all users and operations	Verbose logging can fill storage quickly
PowerShell (Get-SPLogEvent)	Bulk log retrieval for tenant administrators	Automates collection of multiple IDs	Requires SharePoint Online Management Shell and admin rights

With a Correlation ID in hand, you can reduce the time Microsoft support spends locating your error logs. The best approach is to capture the ID immediately after the error occurs, enable verbose logging only during active troubleshooting, and always include the ID along with the exact timestamp and user context. This practice turns a vague error report into a precise diagnostic tool for both you and the support team.