This topic provides details on how to capture Microsoft Office 365 Email and Calendar messages via Collect.
- Information captured
- Setup instructions
Before using this data source, note the following license requirements, version support, and special considerations.
The following licenses are required to use this data source:
- Microsoft 365 E3 or higher is required.
- If you are using Microsoft 365 E3, you also need to add the Compliance module.
We support Microsoft 365 Enterprise 3 and above.
Note the following considerations about this data source:
- The connector only supports accessing active mailboxes.
- The connector does NOT support collection from Archive mailboxes
- You can collect from unlicensed custodians, but the mailbox must still be active in the case where the user is unlicensed.
- The connector can access data regardless of the geographic location the data resides in when Microsoft Multi-Geo capabilities have been implemented.
- Guest mailboxes can only be collected if they are active & licensed.
- Shared mailboxes can only be captured if they are active.
The Microsoft O365 Mail Archive Mailbox data source should always be enabled alongside the Microsoft O365 Email and Calendar data source to ensure holistic collection is performed. Without Microsoft O365 Mail Archive Mailbox data source enabled you may miss data that is quickly archived either by a rule or manual action.
- The connector collects all items in visible folders within Outlook’s inbox and custom folders.
- Deleted items can be collected.
- Deleted items from deleted folder (deleted and purged items) can be collected. Users must set their “Deleted items retention” to at least 14 days (Microsoft default).
- Hidden folders cannot be collected.
- Formatted text is captured as plain text.
- Numbered rows are captured as a single line.
- Emojis are collected as plain text.
- There are two levels of filtering data:
- Data Source - only data linked to a Data Source Monitored Individuals will be captured.
- Data Batch - only messages which have “Date Received” within Data Batch collection period will be captured.
This section lists what activities and, if applicable, metadata are captured when you use this data source.
The following table lists activities captured by this data source:
|Messages with attachments||A participant is only captured if they wrote a message.|
|Meeting request||A team meeting request is captured as a message placeholder.|
|Calendar events (vCalendar)|
|Deleted items||Users must set their Deleted items retention to at least 14 days (MSFT default). If this is not set, Trace cannot collect data that has been triple deleted by user.|
|Permanently deleted items|
|Distribution list emails||A copy of any email sent to a distribution list is captured from each mailbox that is on the distribution list. A distribution list itself is not a mailbox.|
The following table lists activities not captured by this data source:
|Activity not captured||Notes|
|Participant removed from channel||A participant who leaves or is removed from a channel event is not captured. The participant is captured only if they wrote a message|
|Distribution lists||A distribution list itself is not a mailbox.|
This section provides details on the prerequisites and steps for setting up this data source.
You must have the following in order to complete the setup instructions for this data source.
You must have Collect installed in the workspace to set up this data source, since Collect will be used for data retrieval.
For details on installing Collect, see Using Relativity Collect.
You must have the following company-provided information to complete the authentication steps that precede setting up the data source:
- Access to the Azure portal and an active account
- A Client Secret
- An O365 domain name
- An Application / Client ID
You must have the following information to complete the data transfer.
- An application ID
- A Client secret
- An O365 domain name
Before configuring the data source complete the following authentication steps.
We strongly recommend registering a separate Azure Application for each Data Source.
To register your app:
- Open your Azure Portal.
- Click More Services.
- Search for and select Azure Active Directory.
- In the left-navigation menu, click App registrations.
- Click New Registration. This will open the Register an application page.
- Enter an application name in the Name field.
- Select Accounts in this organizational directory only as the supported account type.
- Enter the redirect URL, http://localhost/ or https://localhost/, as the sign-on URL.
- Click Register. For more information on registering an application in Azure, see Microsoft’s documentation.
From the app’s page, add permissions to the web API:
- Click API Permissions.
- Click Add a permission.
- Click Microsoft Graph.
- Select Application Permissions.
- Select the following options from the Application Permissions section:
- Mail - Read.
- User - Read.All
- Calendars - Read. For the Email only option, this permission is not needed
- Click Add permissions.
- Click Grant Permission.
Grant Admin consent for the API:
- Click the API Permissions tab.
- Click Grant admin consent for [tenant].
- In the pop-up window, click Accept. If you do not have the ability to grant Admin consent for application permissions, you will need to find an Admin that can consent.
- Once clicked, the window will show all permissions granted.
- Verify all permissions have been granted.
- Click Accept to grant the permissions.
Generate Client Secret:
- In the left navigation menu, select Certificates & secrets.
- Select New client secret.
- Enter a description in the Description text box.
- Set the expiration time frame to Never.
- Click Add.
- Click on the clipboard and copy secret to clipboard to paste in your text document. Save this secret, as you will need it to set up your data sources in Trace.
Microsoft will only show this secret this one time; there is no way to recover a secret if it is forgotten or lost. Make a note of the Application ID that Microsoft assigned to the app registration. This ID is also required for setup of data sources in Trace.
You will need the following information to complete setup of the data source from the Trace front end:
- Application ID
- Client Secret (copy the Value field)
- Domain (mycompanydomain.com)
Make sure you copy the Value field item for your Client Secret. Do not accidentally copy the Secret ID item as this is not the your Client Secret.
Limit the access of Relativity Collect to specific Microsoft user accounts and mailboxes by using the New-ApplicationAccessPolicy Powershell cmdlet. For more information, see Microsoft documentation.
The following sections provide the steps for installing Collect and configuring the data source.
Prior to creating the Data Source, install the Collect application and configure the appropriate instance settings by following the Using Relativity Collect page.
Most parameters work the same for all Collect Data Sources. Follow the instructions from common_collect_data_source_functionality section.
O365 Mail and Calendar specific parameters:
- Data Source Type: Select Microsoft O365 Mail or Calendar.
- Application Secret: The Client Secret provided by the client (see Authentication for more details).
- Data Source Specific Fields section
- Collect Draft items: If set to
FALSE(default), then only emails that were sent (non-Draft) are collected. If set to
TRUE, then both sent emails (non-draft) and drafts emails are collected. Since draft emails are not actually communication, most customers elect to set this to
FALSEand ignore the collection of draft emails to reduce false-positive alerts.
- Domain: The O365 domain name provided by the client.
- Application Id: Application / Client ID provided by the client.
- Use Quick Discovery: True
- Frequency in Minutes: 60
- Number of Monitored Individual Per job: 100
- Collection Period Offset in Minutes: 0
- Collect Draft items: If set to