Skip to main content

Who is this article for?
Find your product plan in the Code42 console on the Account menu.

Incydr Professional and Enterprise
Incydr Basic and Advanced
Other product plans

Incydr Professional and Enterprise, yes.

Incydr Basic and Advanced, yes.

CrashPlan Cloud, yes.

Other product plans, yes.

CrashPlan for Small Business, no.

This article applies to Code42 cloud environments.

HOME
GETTING STARTED
RELEASE NOTES
FAQs
APIs
SYSTEM STATUS
Code42 Support

Deauthorize and resume monitoring a data connection

Who is this article for?
Find your product plan in the Code42 console on the Account menu.

Incydr Professional and Enterprise
Incydr Basic and Advanced
Other product plans

Incydr Professional and Enterprise, yes.

Incydr Basic and Advanced, yes.

CrashPlan Cloud, yes.

Other product plans, yes.

CrashPlan for Small Business, no.

This article applies to Code42 cloud environments.

Overview

To help protect you from data loss, you can use Code42 to monitor files moving to and from users' cloud storage environments, such as Google Drive or Microsoft OneDrive, or emailed as attachments through Gmail or Office 365. 

This article explains how to deauthorize those data connections so that Code42 no longer has access to user data in those cloud storage or email service environments. You can also resume monitoring cloud storage connections to resolve errors, reconfigure cloud storage scoping, or restart the collection of file activity from data connections after a pause.

For information about disconnecting an automated integration, see Configure Incydr Flows

Considerations

  • You cannot deauthorize a cloud storage connection (Google Drive, OneDrive, or Box, for example) or email service connection (such as Gmail or Office 365) ;while the status is Initializing. Wait for the connection to indicate that it has a status of Monitoring or Error before attempting to deauthorize.
  • If needed, you can use this process to reconfigure scoping for monitoring a cloud storage connection's users or groups.
  • Google Workspace administrators must have the Super Admin role in order to share file activity data with Code42 without errors. See Resolve "Data source is not sending security data" errors for more information.
  • Cloud storage and email service connections are not available in the Code42 federal environment.

Deauthorize a cloud storage or email service connection

Deauthorize a connection to stop monitoring it for new event activity.

For most cloud storage and email service connections, you can resume monitoring that connection for up to 90 days after you deauthorize it. After 90 days, Code42 removes the cloud storage or email service's configuration and authorization information. To resume monitoring that connection again after 90 days have elapsed, you must set it up as a new connection.

For Gmail and Microsoft Office 365 email services, Code42 removes the email service's configuration and authorization information immediately after deauthorization. To resume monitoring a Gmail or Microsoft Office 365 email service again, you must set it up as a new connection.

For all connections, events that have been collected prior to deauthorization remain searchable in Forensic Search for up to 90 days.

  1. Sign in to the Code42 console.
  2. Select Administration > Integrations > Data Connections
  3. Locate the connection to deauthorize in the table, then click View details View details.
  4. Clic Deauthorize.
  5. When the dialog box opens, read the information and then click Deauthorize.
    At this point, Code42 stops collecting new file activity from the data connection.
  6. If you do not plan to resume monitoring the connection, remove Code42's access in the external console as well. 

Remove Code42's access in Box

Remove Code42's access in Google Drive or Gmail

Remove Code42's access in Microsoft OneDrive or Office 365 email

Resume monitoring a cloud storage or email service connection

You can resume monitoring most cloud storage connections for up to 90 days after you deauthorized the initial connection. Code42 removes connections that have been deactivated for over 90 days. To resume monitoring a Gmail or Microsoft Office 365 email service after deauthorization, set it up as a new connection.

  1. Sign in to the Code42 console.
  2. Select Administration > Integrations > Data Connections
  3. Locate the connection to resume monitoring in the table, then click View details View details.
  4. Click Resume Monitoring.
    You can resume monitoring only connections with a status of Deauthorized. You cannot resume monitoring a Gmail or Microsoft Office 365 email service. Instead, set it up as a new connection to monitor that service again.
  5. Follow the prompts to authorize Code42 to monitor file events on that connection.
    Option to update administrator email address
    If you are resuming monitoring of a Google Drive environment, you can change the administrator's email address if needed. When doing so, you can change the username in the email address, but the domain used (such as "@example.com") must remain the same. This new email address must be associated with a Google Workspace administrator that has the Super Admin role.

Use cases

You can deauthorize and then resume monitoring a cloud storage connection to update the scoping used or resolve errors. In most cases, errors caused by permissions or licensing issues within the cloud storage environment can be resolved by deauthorizing the connection and then immediately resuming its monitoring.

Some use cases for using the deauthorization and resume monitoring processes for a cloud storage connection are detailed below.

Reconfigure cloud storage scoping for user or group monitoring

If needed, you can reconfigure the cloud storage's scoping to add new users or groups or switch from monitoring specific users to monitoring specific groups.

  1. Deauthorize the cloud storage connection.
    You do not need to remove the Code42 application from the cloud storage environment. The app registration remains valid even if it is deauthorized.
  2. Resume monitoring the cloud storage connection.
    You are prompted to set up the cloud storage connection again.
  3. In the Add Users step of the reauthorization process, select the appropriate monitoring option, and then upload a new .csv file containing the updated users or groups you want to monitor.

Resolve "Data connection is not sending security data" errors

In certain situations, Code42 may be unable to access your Google Drive environment to monitor its file activity. When Code42 is unable to gather data from your Google Drive environment, the following message appears at the top of the Data Connections screen after the Google Drive connection is authorized: "Data connection <ConnectionName> is not sending security data."

"Data connection is not sending security data" message

To resolve this issue, try the following solutions in the order listed.

  1. Make sure that your Google Workspace administrator has the Super Admin role.
    1. If needed, update permissions in the Google Admin console to give your administrator the Super Admin role. 
    2. After updating administrator permissions, deauthorize the Google Drive cloud storage data connection in the Code42 console. 
    3. Resume monitoring the Google Drive cloud storage data connection again using the email address of the administrator with the Super Admin role.
      The authorization process must be completed by someone who holds the Super Admin role in your Google Workspace. No other administrator levels are valid.
  2. Verify that the permissions (or scopes) required by the Code42 service account have been added to your Google Workspace correctly.
  3. Verify that Drive and Docs is turned on for everyone in your Google Workspace (or for everyone in the Google Workspace organizational unit that you want to monitor).
    Code42 can only monitor file activity for the organizational units with Drive and Docs enabled.
  4. Verify that third-party apps have access to Drive files. Code42 cannot monitor your Google Drive environment if this setting is disabled.

Resolve "Number of user drives exceeded" errors

Code42 can monitor a maximum number of drives in your cloud storage environment, depending on vendor:

  • Box: 500,000 drives
  • Google Drive and OneDrive: 55,000 drives

If Code42 detects more than the maximum number of drives, the following error appears at the top of the Data Connections screen: "The number of supported user drives (<DriveMaximum>) for this connector has been exceeded. Deauthorize the connector and reauthorize with fewer than <DriveMaximum> drives."

"Number of supported user drives exceeded" message

If you receive this message:

  1. Deauthorize the cloud storage data connection.
  2. Resume monitoring the cloud storage data connection.
    You are prompted to set up the cloud storage data connection again.
  3. In the Add Users step of the reauthorization process, select the Specific Users or Specific Groups option and ensure that the total number of drives included is below the maximum limit.