Collaborative Authoring Error Log

Vault allows you to track Microsoft Graph API errors generated while using collaborative authoring in the Admin > Logs > Collaborative Authoring Error Log. You can review these error logs and export the full stack trace to troubleshoot the error or send it to Microsoft Support.

Reviewing the Error Log

The Collaborative Authoring Error Log shows the most recent errors by default. The following columns are included in the log:

Username
Document ID
Major Version
Minor Version
Timestamp
Request ID
Collaborative Authoring Action
Error

To sort by the Document ID and Timestamp columns, click on the column heading. You can apply filters to find errors from specific dates, specific document IDs, or an individual user. To apply additional filters, click Add filter; to remove them, click Subtract (-) next to the added filters.

Exporting the Error Log

While viewing the errors, select Actions > Export to CSV to download the full API error log. You can also download the full stack trace of an error by clicking Download full trace on the specific entry in the Error column.

Escalating to Microsoft Support

When the diagnostic points at a Microsoft-side failure (for example, a 400 Bad Request token-endpoint error), open a ticket with Microsoft Support and provide the following information:

Request ID
Timestamp
Endpoint
Request Body Params
Response

Microsoft Support retains API trace data for 30 days only, so ensure that you escalate issues within 30 days. Microsoft will be unable to trace Request IDs older than 30 days.

Diagnostic Strings

This section contains known diagnostic strings that can be displayed in the Collaborative Authoring Error Log.

400: Bad Request

Error: 400 Bad Request during token retrieval

Cause Fix

Cause	Fix
Token exchange fails when Vault calls Microsoft’s `/oauth2/v2.0/token` endpoint. The exact backend cause is highly variable on the tenant side, including malformed scope, app misconfiguration, conditional access at the token endpoint, throttling, and so on. It is not always inferable from the Vault-side error alone.	Complete the following steps: Double check the directory ID and application ID settings. Generate a new client secret in Entra ID. Enter the client secret Value in Checkout Settings, then click Authorize. If the error is not resolved, open a Veeva support ticket.

Token exchange fails when Vault calls Microsoft’s /oauth2/v2.0/token endpoint. The exact backend cause is highly variable on the tenant side, including malformed scope, app misconfiguration, conditional access at the token endpoint, throttling, and so on. It is not always inferable from the Vault-side error alone.

Complete the following steps:

Double check the directory ID and application ID settings.
Generate a new client secret in Entra ID. Enter the client secret Value in Checkout Settings, then click Authorize.
If the error is not resolved, open a Veeva support ticket.

403: Forbidden

Error: 403 Forbidden: Sharing has been disabled on this site.

Cause	Fix
SharePoint is not configured to support external users. Microsoft returns this error when Vault attempts to add SharePoint document permissions for an external user.	Enable external collaboration at both the tenant and site collection level. External sharing must be set to Existing Guests or more permissive; setting it to Only people in your organization blocks collaborative authoring. Supply the Request ID from the error log entry to Microsoft Support if further investigation is needed.
External sharing is enabled in SharePoint, but the SharePoint setting Allow only users in specific security groups to share externally is enabled.	Microsoft does not support Entra ID app sharing with the Allow only users in specific security groups to share externally setting. Use a different security mechanism to limit external sharing.

Access to the Collaborative Authoring Error Log is controlled by the Admin: Logs: Collab Auth Error Logs permission. This permission is enabled automatically for System Administrators, Business Administrators, and Vault Owners.