Skip to main content

Instructor, no.

Incydr Professional, Enterprise, Gov F2, and Horizon, no.

Incydr Basic, Advanced, and Gov F1, no.

CrashPlan Cloud, no.

Retired product plans, no.

CrashPlan for Small Business, no.

HOME
GETTING STARTED
RELEASE NOTES
FAQs
APIs
SYSTEM STATUS
Code42 Support

Deauthorize and resume monitoring a cloud or email service

...

This article explains how to deauthorize those data

connectionssources so that
ParseError: EOF expected (click for details)
Callstack:
    at (Article_Update_Log/2021-07-01/Deauthorize_and_resume_monitoring_a_cloud_or_email_service), /content/body/span, line 1, column 10
no longer has access to user data in those cloud or email services. You can also resume monitoring those data connectionssources to resolve errors, reconfigure cloud service scoping, or restart the collection of file activity from data connectionssources after a pause.

For information about disconnecting an automated integration, see
ParseError: EOF expected (click for details)
Callstack:
    at (Article_Update_Log/2021-07-01/Deauthorize_and_resume_monitoring_a_cloud_or_email_service), /content/body/ins[4]/span, line 1, column 10
.
 

...

Deauthorize a cloud or email servicedata source

Deauthorize a

servicedata source to stop monitoring for new event activity. Once deauthorized, you have 90 days to resume monitoring that servicethe data source. After 90 days,
ParseError: EOF expected (click for details)
Callstack:
    at (Article_Update_Log/2021-07-01/Deauthorize_and_resume_monitoring_a_cloud_or_email_service), /content/body/div[1]/span[1], line 1, column 10
removes the cloud or email servicedata source's configuration and authorization information (the events you have collected remain searchable in
ParseError: EOF expected (click for details)
Callstack:
    at (Article_Update_Log/2021-07-01/Deauthorize_and_resume_monitoring_a_cloud_or_email_service), /content/body/div[1]/span[2], line 1, column 10
). 
  1. Sign in to the
    ParseError: EOF expected (click for details)
    Callstack:
        at (Article_Update_Log/2021-07-01/Deauthorize_and_resume_monitoring_a_cloud_or_email_service), /content/body/div[1]/ol/li[1]/a/span, line 1, column 10
    
    .
  2. Select Administration
    ParseError: EOF expected (click for details)
    Callstack:
        at (Article_Update_Log/2021-07-01/Deauthorize_and_resume_monitoring_a_cloud_or_email_service), /content/body/div[1]/ol/li[2]/strong/del/span, line 1, column 10
    
     > Integrations > Data ConnectionsDataSources
  3. Locate the
  4. servicedata source to deauthorize in the table, then click View details View details.
  5. Click Deauthorize.  
  6. When
  7. the dialog box opens, readprompted, enter DEAUTHORIZE.  the information and then clickClick Deauthorize.
    At this point,
    ParseError: EOF expected (click for details)
    Callstack:
        at (Article_Update_Log/2021-07-01/Deauthorize_and_resume_monitoring_a_cloud_or_email_service), /content/body/div[1]/ol/em/span, line 1, column 10
    
    stops collecting new file activity from the data connectionsource.
  8. If you do not plan to resume monitoring the
  9. cloud service, remove 
    ParseError: EOF expected (click for details)
    Callstack:
        at (Article_Update_Log/2021-07-01/Deauthorize_and_resume_monitoring_a_cloud_or_email_service), /content/body/div[1]/ol/span, line 1, column 10
    
    's access in the external console as well. 

...

Resume monitoring a cloud or email servicedata source

You can resume monitoring a

cloud or email servicedata source for up to 90 days after you deauthorized the initial connection.
ParseError: EOF expected (click for details)
Callstack:
    at (Article_Update_Log/2021-07-01/Deauthorize_and_resume_monitoring_a_cloud_or_email_service), /content/body/div[2]/span, line 1, column 10
removes servicesdata sources that have been deactivated for over 90 days. 
  1. Sign in to the
    ParseError: EOF expected (click for details)
    Callstack:
        at (Article_Update_Log/2021-07-01/Deauthorize_and_resume_monitoring_a_cloud_or_email_service), /content/body/div[2]/ol/li[1]/a/span, line 1, column 10
    
    .
  2. Select Administration
    ParseError: EOF expected (click for details)
    Callstack:
        at (Article_Update_Log/2021-07-01/Deauthorize_and_resume_monitoring_a_cloud_or_email_service), /content/body/div[2]/ol/li[2]/strong/del/span, line 1, column 10
    
     > Integrations > Data ConnectionsDataSources
  3. Locate the
  4. servicedata source to resume monitoring in the table, then click View details View details.
  5. Click Resume Monitoring.
    You can resume monitoring only servicesdata sources with a status of Deauthorized.
  6. Follow the prompts to authorize
    ParseError: EOF expected (click for details)
    Callstack:
        at (Article_Update_Log/2021-07-01/Deauthorize_and_resume_monitoring_a_cloud_or_email_service), /content/body/div[2]/ol/li[5]/span, line 1, column 10
    
    to monitor file events on that
  7. servicedata source.
    Option to update administrator email address
    If you are resuming monitoring of a Google Drive or Gmail 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.

...

You can deauthorize and then resume monitoring a

cloud servicedata source  to update the scoping used by a cloud service  or resolve errors. In most cases, errors caused by permissions or licensing issues within the cloud servicedata source 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 servicedata source  are detailed below.

...

  • ParseError: EOF expected (click for details)
    Callstack:
        at (Article_Update_Log/2021-07-01/Deauthorize_and_resume_monitoring_a_cloud_or_email_service), /content/body/div[2]/ul/li[1]/span, line 1, column 10
    
     
  • ParseError: EOF expected (click for details)
    Callstack:
        at (Article_Update_Log/2021-07-01/Deauthorize_and_resume_monitoring_a_cloud_or_email_service), /content/body/div[2]/ul/li[2]/span, line 1, column 10
    
     
  • ParseError: EOF expected (click for details)
    Callstack:
        at (Article_Update_Log/2021-07-01/Deauthorize_and_resume_monitoring_a_cloud_or_email_service), /content/body/div[2]/ul/li[3]/span, line 1, column 10
    
     
  • ParseError: EOF expected (click for details)
    Callstack:
        at (Article_Update_Log/2021-07-01/Deauthorize_and_resume_monitoring_a_cloud_or_email_service), /content/body/div[2]/ul/ins/span, line 1, column 10
    
     
  • Was this article helpful?