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

Allow Code42 access to Microsoft Office 365 DLP email

...

You can set up data loss prevention policies in the Microsoft Office 365 Security & Compliance Center that identify when a user emails an attachment that matches those rules. When you add

Microsoft Office 365 DLP as a email serviceOffice365emailas a data connection for 
ParseError: EOF expected (click for details)
Callstack:
    at (Article_Update_Log/2021-07-01/Allow_Code42_access_to_Microsoft_Office_365_DLP_email), /content/body/span[1], line 1, column 10
, information about those attachments becomes available in
ParseError: EOF expected (click for details)
Callstack:
    at (Article_Update_Log/2021-07-01/Allow_Code42_access_to_Microsoft_Office_365_DLP_email), /content/body/span[2], line 1, column 10
 for investigation.   

This article explains how to add

Microsoft Office 365 DLPOffice365 email as a data connection.

...

The following considerations apply to

the Microsoft Office 365 DLP connectionOffice365email. See also the considerations applicable to all email services.

...

Before adding

Microsoft Office 365 DLPOffice365email  as a data connection:

...

Connect to Microsoft Office 365 DLPOffice365 email 

...

The next time that an attachment is emailed that is detected by a data loss prevention policy in the Microsoft Office 365 Security & Compliance Center, information about that file is recorded as an event by

ParseError: EOF expected (click for details)
Callstack:
    at (Article_Update_Log/2021-07-01/Allow_Code42_access_to_Microsoft_Office_365_DLP_email), /content/body/div[1]/p[2]/span, line 1, column 10
. For details, see AttachmentOffice 365 attachment metadata below.

...

Now that you have added

Microsoft Office 365 DLPOffice365email as a data connection, learn more about:

...

AttachmentOffice 365 attachment metadata

...

RequiredOffice 365 email permissions 

...

Other changes:

  1. /body/ul[2]/li/a/@href:
  2. "/Administrator/Cloud/Configuring/Configure_Forensic_File_Search""/Administrator/Cloud/Configuring/Enable_endpoint_monitoring_and_file_metadata_collection"
  3. /body/ul[2]/li/a/@title: nothing ⇒
  4. "Enable endpoint monitoring and file metadata collection"
  5. /body/ol[2]/li[8]/a/@href:
  6. "/Administrator/Cloud/Configuring/Allow_Code42_access_to_Microsoft_Office_365_DLP_email#Office_365_email_permissions""/Administrator/Cloud/Configuring/Allow_Code42_access_to_Microsoft_Office_365_DLP_email#Required_permissions"
  7. /body/ol[2]/li[8]/a/@title:
  8. "Allow Code42 Forensic File Search access to Office 365 email""Allow Code42 access to Office 365 email"
  9. /body/p[8]/a/@href:
  10. "/Administrator/Cloud/Configuring/Allow_Code42_access_to_Microsoft_Office_365_DLP_email#Office_365_attachment_metadata""/Administrator/Cloud/Configuring/Allow_Code42_access_to_Microsoft_Office_365_DLP_email#Attachment_metadata"
  11. /body/p[8]/a/@title:
  12. "DOC-10625 Allow Code42 Forensic File Search access to Office 365 email""Allow Code42 access to Office 365 email"
  13. /body/ul[7]/li[3]/p[2]/a[3]/@href:
  14. "/Administrator/Cloud/Configuring/Allow_Code42_access_to_Microsoft_Office_365_DLP_email#Connect_to_Office_365_email""/Administrator/Cloud/Configuring/Allow_Code42_access_to_Microsoft_Office_365_DLP_email#Connect_to_Microsoft_Office_365_DLP_email"
  15. /body/div[5]/@data-section:
  16. "Data source is already registered or the\u00a0email address is not valid""Data source is already registered or the email address is not valid"
  • Was this article helpful?