Cloud Applications | Additional Application for SharePoint

 

The Additional O365 Application for SharePoint capability allows administrators to add a secondary, dedicated SharePoint application to an existing Microsoft 365 / O365 Cloud DLP integration.

This additional application is used to increase available Microsoft API capacity for SharePoint file monitoring. It is intended for large or high-activity Microsoft 365 tenants where Cloud DLP processing may be delayed due to API quota limits.

This capability is not required for every customer. It is recommended for customers with large SharePoint environments, typically above 50,000 users, or customers experiencing ingestion latency, delayed file processing, or Microsoft API quota-related errors.

 

Why Use an Additional SharePoint Application?

Large Microsoft 365 tenants can generate a high volume of SharePoint file activity. In some cases, the primary O365 application may reach Microsoft API quota limits, which can delay event ingestion and file processing in Cloud DLP.

Adding a dedicated SharePoint application provides additional API capacity for SharePoint file monitoring. This helps reduce the likelihood of processing delays caused by API throttling or quota constraints.

Common indicators that this capability may be useful include:

  • Delays in SharePoint file event ingestion

  • Delayed classification or processing of SharePoint files

  • API quota or throttling errors observed in Microsoft audit or application logs

 

What the Additional SharePoint Application Does

The additional application is dedicated to SharePoint file monitoring. It supplements the existing O365 Cloud DLP integration and helps Cloud DLP process SharePoint file activity more efficiently.

The additional application does not replace the main O365 integration. The primary O365 application remains connected and continues to support the existing integration.

The additional SharePoint application uses a minimal permission set required for SharePoint file monitoring.

 

Required Permissions

During the Microsoft consent flow, the additional SharePoint application requests only the required permissions for this capability.

The expected permissions are:

  • Read files

  • Read site collections

  • Sign in and read user profile

The exact Microsoft permission names will be displayed in the Microsoft consent screen.

 

Important Requirements

The additional SharePoint application must be connected to the same Microsoft 365 tenant as the existing O365 Cloud DLP integration.

The Microsoft user performing the consent flow may be different, but the Microsoft tenant must be the same tenant used by the primary O365 application. If the additional application is connected to a different Microsoft tenant, the connection will fail.

The administrator approving the application must have the required Microsoft permissions to grant consent for the requested scopes.

 

When to Use This Capability

Use the additional SharePoint application when a customer has a large or high-activity Microsoft 365 environment and is experiencing, or is at risk of experiencing, processing delays caused by Microsoft API quota limits.

This capability is especially relevant when:

  • The tenant has more than 50,000 users

  • SharePoint file activity volume is high

  • Cloud DLP event processing is delayed

  • File monitoring latency is observed

  • Microsoft API throttling or quota errors are visible

  • The customer is onboarding a large Microsoft 365 tenant and wants to reduce quota-related risk

This capability is not mandatory for all Microsoft 365 customers.

 

How to Add the Additional SharePoint Application

  1. Go to Administration.

  2. Select Integrations.

  3. Open Cloud Applications.

  4. Select the existing O365 Cloud DLP integration.

  5. Click Add SharePoint.

  6. Complete the Microsoft consent flow.

  7. Approve the requested permissions.

  8. Return to the Cloud Applications page.

  9. Verify that the additional SharePoint application status is displayed as connected.

After approval, the connection status may take several minutes to update.

 

Status and Monitoring

The Cloud Applications page displays the status of the additional SharePoint application.

Possible states include:

  • Connected

    The additional SharePoint application was successfully connected and is available for SharePoint file monitoring.

  • Not Connected

    No additional SharePoint application is currently connected.

  • Pending

    The application was approved and the connection is being processed. This state may take up to approximately 15 minutes to complete.

  • Error

    The connection failed. Where available, the UI displays the reason for the failure.

    Common causes include:

    • The application was approved for a different Microsoft 365 tenant than the primary O365 integration

    • The approving administrator did not have sufficient permissions

    • Required Microsoft scopes were not granted

    • The Microsoft consent flow was not completed successfully

 

Removing the Additional SharePoint Application

Administrators can remove the additional SharePoint application without disconnecting the main O365 Cloud DLP integration.

Removing the additional SharePoint application stops the extra SharePoint API capacity provided by this application, but the primary O365 integration remains connected.

Administrators can also remove the entire O365 integration if they want to disconnect Cloud DLP from Microsoft 365 completely.

 

Removing the additional SharePoint application does not remove or disable the primary O365 integration.
To fully disconnect Microsoft 365 from Cloud DLP, remove the main O365 integration.

 

Troubleshooting

If the additional SharePoint application does not connect successfully, check the following:

  • Confirm the Microsoft Tenant

    Verify that the additional SharePoint application was approved for the same Microsoft 365 tenant as the primary O365 Cloud DLP integration.

  • Confirm Admin Permissions

    Verify that the administrator completing the Microsoft consent flow has permission to approve the requested application scopes.

  • Review the UI Status

    Check the application status in the Cloud Applications page. If an error reason is shown, use it to determine the next step.

  • Retry the Connection

    If the consent flow failed or was interrupted, retry the connection by selecting Add SharePoint again.

  • Wait for Pending Status to Complete

    If the application is in Pending status, allow up to approximately 15 minutes for the connection to complete.

  • Contact Support

    If the application remains in an error state after retrying, contact Proofpoint Support and provide the displayed error reason, if available.