Allow Code42 access to OneDrive

Step 1: Verify audit is enabled for OneDrive

1. Sign in to the Microsoft 365 compliance center using your Microsoft global administrator username and password.
2. Click Show all in the left navigation pane, then click Audit.
   If audit is not enabled in your environment, the banner at the top of the Search tab prompts you to start recording user and admin activity. This banner does not appear if audit is already enabled.
   
3. If prompted, click the banner at the top of the Search tab to enable audit.
   The banner updates to indicate that audit is enabled and you can search for user and admin activity within 24 hours.

Step 2: Authorize the Code42 connection

1. Sign in to the Code42 console. 
2. Select Administration > Integrations > Data Connections.
3. Click Add Data Connection.
   The Add Data Connection dialog displays.
4. From Data Connection, select Microsoft OneDrive for Business under Cloud Services.
5. Enter a display name. This name must be unique.
6. Code42 prompts you to verify that audit is enabled in your Microsoft environment. You completed this verification in step 1, so click Continue.
7. Select the scope of users in your OneDrive environment to monitor:
   • All
     Monitors all OneDrive users in your environment.
   • Specific Users
     Monitors only the OneDrive users you designate.
     1. Click Upload .CSV File.
     2. Select a .csv file containing a list of only those OneDrive users you want to monitor.
        For details, see Upload a .csv file listing OneDrive users below.
   • Specific Groups
     Monitors only the users in the OneDrive groups you designate.
     1. Click Upload .CSV File.
     2. Select a .csv file containing a list of OneDrive groups whose users you want to monitor. 
        For details, see Upload a .csv file listing OneDrive groups below.
8. Click Authorize. 
   The Microsoft OneDrive for Business sign in screen appears.
9. Enter your OneDrive administrator credentials. 
10. Review the terms and agreements, and click Accept. 
    Microsoft OneDrive is added as a data connection and Code42 begins the initial indexing process.
    Permissions can be delayed in Microsoft Azure
    The permissions you accept during the authorization process can take up to 1 hour to flow through your Microsoft Azure environment. During this time, Code42 may report an error with the new connection in the Data Connections list. This error clears automatically as soon as Code42 is able to access the Microsoft audit log.

Next Steps

Now that you have added OneDrive as a data connection, learn more about:

• Common use cases for investigating security incidents with Forensic Search
• How to use Forensic Search
• Adding trusted domains to easily identify when files are shared with users not on your list of approved domains

Upload a .csv file listing OneDrive users

To export a list of all OneDrive users to a .csv file, see the Microsoft documentation. You can also use PowerShell or Active Directory to obtain a user list and place it in a .csv file. Create a .csv file from this list that contains only the users you want to monitor.

In the .csv file, you can specify either email addresses or display names to identify the users to monitor in your OneDrive environment.

• If identifying users by their email address, list those email addresses under a column header labeled either Email or Email Address. Click to download an example of users identified by email address.
• Alternately, you can identify users who do not have email addresses by their display names. OneDrive does not require users to be associated with an email address, so some users are identified by their display name instead. List these display names under a column header labeled either DisplayName or Owner. Click to download an example of users identified by display name. 

If no valid username entries are found for a user in the .csv file or an invalid column header label is present, the upload produces an error.

Upload a .csv file listing OneDrive groups

To create a OneDrive group, see the Microsoft documentation. The OneDrive group list supports all Office 365 group types:

• Office 365 Group
• Security Group
• Mail-Enabled Security Group
• Distribution Groups

To monitor users in OneDrive groups, create a .csv file that contains only the groups you want to monitor. In this file, use column headers to identify either the name or the email addresses of those groups.

• Code42 reads the display name of groups from the column header labeled Display Name or Groups. In the .csv file, specify this name exactly as it appears in OneDrive or Azure Active Directory. Click to download an example of groups identified by display name.
• Alternately, Code42 reads the email addresses of a group from the column header labeled Email or Email Address. In the .csv file, specify the email address associated with each group. Click to download an example of groups identified by email address.

If the .csv file does not contain at least one of these column headers, the upload produces an error.

Code42 looks for users associated with OneDrive groups as follows:

• When a group's name or email address is provided, Code42 attempts to look up users associated with that group name or group email address.
• If neither the the group name nor the email address can be found in OneDrive, Code42 proceeds to the next entry in the .csv file. Code42 looks for that group or email address again every 8 hours.

As users are added and removed from the monitored groups, Code42 detects these changes within 24 hours and adjusts monitoring of user drives accordingly.

Users that are removed from monitored groups have their event history preserved so that it remains searchable in Forensic Search. When an unmonitored user in your Code42 organization shares a file with a monitored user, the events associated with that file are not captured because the unmonitored user is the owner of the file.

Groups that are nested in a monitored group are also monitored.  

Maximum user drive number exceeded

Data connection is already registered or the email address is not valid

Reconfigure scoping for user and group monitoring