Microsoft 365 - Inactive OneDrive data source

The Microsoft 365 Inactive OneDrive data source enables Collect to retrieve OneDrive content belonging to custodian accounts that have been deactivated or removed. This provides a direct and defensible alternative to manual exports and re-ingestion workflows.

OneDrive data becomes inactive, or inaccessible, to users when a user account is deleted, even if a preservation hold exists. Microsoft does not permanently delete the OneDrive content while a retention policy or hold is in place.

After all retention policies or holds are removed, the OneDrive continues through its standard deletion lifecycle and is permanently deleted according to the configured retention period.

This topic provides details on how to capture Microsoft 365 inactive OneDrive data with Collect.

Considerations

Note the following considerations about Microsoft 365 inactive OneDrive data sources:

• The inactive OneDrive connector uses Microsoft's Purview API.
• Purview Cases will be created in your Microsoft Purview instance to facilitate the search and export of inactive OneDrive.
• Relativity collects all available files including preserved files.
  • You do not need to take extra steps to collect preserved files as they are automatically included in the collection.
  • For more information on preserving data, see Preservation in-place.
• Delegated permissions are mandatory.
  • App-only authentication is not supported for inactive OneDrive collections.
  • Inactive OneDrive exports require an account with the eDiscovery Manager role and an Azure AD app registration that has the required delegated permissions.
• Microsoft APIs do not support verifying that an inactive OneDrive exists prior to collection. You will see failed collections in cases where the OneDrive no longer exists.
• Relativity collects inactive OneDrive data as .zip files.

Collection size

Microsoft 365 collections can be large. When collection jobs become too large, performance decreases.

Large collections	Best practices
200 GB per search	Reduce search size
Multi‑TB exports	Limit the number of custodians per job. Collect max 30 custodians per job.
Long date ranges with many OneDrivees	Using smaller date ranges.

Inactive OneDrive data

Inactive OneDrive collections differ from active Microsoft 365 data sources:

• Content is exported from Microsoft Purview eDiscovery, not Microsoft Graph file APIs.
• A temporary Purview hold is applied to the OneDrive site during export to prevent deletion.
• OneDrive content is exported as ZIP packages, then downloaded and ingested into RelativityOne.
• Temporary holds and export artifacts are removed after collection completes.

These behaviors are specific to OneDrive and do not mirror inactive mailbox collection behavior.

Task checklist

The table lists the order to perform the necessary tasks for setting up the data source for Collect.

Separate Microsoft data sources inside Collect can use the same Microsoft Azure app registration.
This means you only need to create one Microsoft Graph application and provide one Client ID and one Client Secret. You can then enter that same set of credentials for Microsoft data sources within Collect.

Order	Application	Task
1	Azure	Registering the Collect application
2	Azure	Obtaining a client secret
3	Azure	Setting API permissions
4	Azure	Adding a redirect URI
5	Collect	Creating the data source in Collect
6	Collect	Configuring the data source in Collect

Accessing Microsoft 365 tenants

Register the Collect application to access Microsoft 365.

When registering the application, the Microsoft 365 administrator creates a Microsoft Application ID and secret. Relativity uses this ID and secret to configure data sources in Collect and provides access to the Microsoft 365 tenants.

You can register the application through Azure Portal or by registering the delegated permissions through the Microsoft App Registration Portal. After registering the application, request administrator consent. From there, it is possible to revoke application access.

Use this information to create a Microsoft integration point. For more information, see Importing data through Integration Points.

Depending on your RelativityOne license, commercial or government, and your Microsoft tenant, Microsoft 365 or Microsoft 365 Government, you will be able to collect from either Microsoft 365 or both Microsoft 365 and Microsoft 365 Government data sources. Commercial users can only collect from Microsoft 365 tenants. Government users can collect from Microsoft 365 and Government 365 tenants. These data sources act the same, but have different icons within Collect.

Registering the Collect application

Start with registering your application in the Azure portal by following the steps below.

For more information on registering an application in Azure, see Microsoft's documentation or Microsoft's authentication documentation.

These steps must be completed by a Microsoft 365 administrator.

1. Open your Azure Portal.
2. Click Microsoft Entra ID (formerly known as Azure Active Directory).
3. Click App registrations.
4. Click New Registration to display the Register an application page.
5. Enter an application name in the Name field.
6. Accept the default setting, Accounts in this organizational directory only, as the supported account type.
7. Click Register.
8. Once the application is registered, make note of the Application (client) ID and Directory (tenant) ID for use later when configuring the data source in RelativityOne Collect.

Obtaining a client secret

Next, obtain the client secret for the registered application in the Azure portal. For more information, see relevant Microsoft documentation on the Microsoft site.

These steps must be completed by a Microsoft 365 administrator.

1. From the registered application's page, click the Certificates & secrets option in the left navigation bar.
2. Click the Client secrets tab.
3. Click New client secret.
   
4. Enter a description for the client secret in the Description text box.
5. Select 730 days (24 months) from the Expires list. The client secret will expire after this time frame.
   • Once the client secret expires, you must create a new client secret in the Azure portal as described in these steps.
   • Then you must update your Microsoft 365 Collect data sources with it. For more information, see Expired Azure client secrets.
   • For any additional assistance with client secrets, please contact the Azure Admin in your organization.
6. Click Add to create a new secret.
7. Copy the Secret Value to the clipboard by clicking the copy icon and paste it to a safe location. You will use the Secret Value later when creating the data source in Collect.
   Microsoft will only show this secret this one time, and there is no way to recover a secret.
8. Give your Relativity Admin the Application ID and the Client Secret for setup of Collect. This application secret is also needed for setting up a Microsoft Entra ID integration point. For more information, see Importing from Microsoft Entra ID.

Expired Azure client secrets

If your Azure client secret expires, follow these steps:

1. Get a new secret as outlined in the steps above.
2. Go to Collect Admin in RelativityOne.
3. Select the desired data source that has expired, and click Edit.
4. Input the new client secret value in the Application Secret field.
5. Click Save.

You must repeat these steps for all Microsoft data sources that you have set up.

Setting API permissions

Each data source has its own set of permissions necessary to allow access to the tenants.

To add the correct permissions based on your selected Microsoft 365 data source, follow the steps below.

These steps must be completed by a Microsoft 365 administrator.

1. From the registered application's page, click the Manage > API permissions option in the left navigation bar.
   
   The User.Read permission is automatically added by default.
2. Click Add a permission.
3. Click Graph API.
4. Select Delegated Permissions.
5. Select the eDiscovery.ReadWrite.All permission from the Permission list.
6. Click Add permissions.
7. Click Grant Permission.
   The window will show all permissions granted. 
   • 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 Collect.
8. Click Add a permission.
9. Select APIs my organization uses.
10. Search for MicrosoftPurviewEDiscovery.
11. Select Application Permissions.
12. Select the eDiscovery.Download.Read permission from the Permission list.
13. Click Add permissions.
14. Click Grant Permission.
    The window will show all permissions granted. 
    • 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 Collect.
15. Verify that all permissions have been granted.
16. Click Add permissions.
17. Click Grant Permission.
18. Click Accept to grant the permissions.

All API permissions have been granted and you can start creating the data source in RelativityOne.

Adding a redirect URI

After setting up API permissions, you must add a Redirect URI to the Azure Application Registration. Add the Redirect URI with the following steps:

1. In the left-side menu console, click Authentication.
   
   It may appear as Authentication (Preview).
2. Click Add Redirect URI.
3. Click Web.
4. Enter your Redirect URI.
   • Your Redirect URI is your RelativityOne tenant domain URL plus /collect-services/api/v1/Authentication/ms-auth-response.
   • For example, https://acme.corp.relativity.one/collect-services/api/v1/Authentication/ms-auth-response

Finding Azure credentials

If an application is already created and you need to find the application information to complete the Source Connection step, follow the steps below in the Azure Portal. For more information, see relevant Microsoft documentation on the Microsoft site.

1. Open your Azure Portal.
2. Click Microsoft Entra ID (formerly known as Azure Active Directory).
3. Navigate to Enterprise applications.
4. In the list of applications, locate and click on your application.The application page displays.
5. Navigate to Properties.
6. Click the copy icon next to the Application ID. The ID is copied to your clipboard to use as needed.
   

Limiting application registration access to accounts

Limit the access of Collect to specific Microsoft user accounts and mailboxes by using New-ServicePrincipal -AppId <Client Application ID in AAD> -ObjectId <Service principal object ID in AAD> -DisplayName <name>. For more information, see Microsoft documentation.

Revoking application access

Revoke the application from the Azure portal or by using a PowerShell script. For more information, see Microsoft's documentation.

Revoking access via Azure Portal

To revoke access from the Azure portal:

1. Open your Azure Portal.
2. Navigate to Enterprise Application.
3. Under All applications, search for your application and click its link.
4. Under Manage > Properties, click Delete.

Collect no longer has access.

Revoking access via Powershell

Revoke access in Powershell using the Remove-MsolServicePrincipal script. See the Powershell example below of retrieving and deleting an application registration.

Creating the data source in Collect

The Collection Admin tab is where you create, edit, and remove data sources from your workspace. You need to setup each data source once. You must create your data sources prior to setting up your custodian targets.

In RelativityOne, navigate to Collect.

1. Click the New Collection Source Instance button.
2. Enter in a unique name for the data source.
3. Select a Microsoft 365 Inactive OneDrive data source.
   Collect automatically collects any data that is preserved due to an in-place hold or litigation hold. Data on a hold is stored in a preservation library and separate folders. For more information, see Microsoft Retention Policies.
4. Enter the required information in Settings. For more information, see Settings fields
5. Click Save.

After clicking Save, Relativity verifies the parameters and connectivity to the Microsoft 365 data source.

If successful, Relativity saves the data source. If the connection fails, a message appears indicating that the connection failed. If verification fails, verify that the values are correct. The data source will save when it is corrected and is verified.

Once the set up is complete, the data source information on the Collect Admin page.

Settings fields

To connect Relativity to the Inactive OneDrive data source, you need to gather and enter the information for the following fields:

• Tenant ID—enter the Tenant ID or Primary domain of the Microsoft 365 tenant the collection is intended for. The domain name usually ends with .onmicrosoft.com. To locate the tenant ID or primary domain name, see Microsoft documentation.
• Application Id—enter the Application ID created during registering the Collect application in Microsoft 365.
• Application secret—enter the Application secret created during registering the Collect application in Microsoft 365. For more information, see Accessing Microsoft 365 tenants.
• Refresh token—after entering in the three pieces of information, click Generate Refresh Token.
  •  An authentication window appears.
  • In the authentication window, you must get a refresh token from a Microsoft account with the Microsoft eDiscovery Manager role assigned.
  • For long-running export jobs, the refresh token may be rotated. Monitor job logs and be prepared to re-authenticate if a token expiration error occurs.

Data source details

Each data source details page includes an Action console. Each data source has different actions.

On the Microsoft Inactive OneDrive data source page, click Validate Connection in the Actions console to validate the client ID, certificate, and other credentials with Microsoft 365.

Configuring the data source in Collect

In RelativityOne, configure the data sources chosen in the Collection Details step.

Data source criteria

Add criteria to collect specific data. To configure the data sources, complete the following fields:

• Select and unselected tabs—choose the data sources to collect from by moving unselected data sources to the selected list.
• Field—choose the field to filter on within the data source.
  
• Operator—choose an operator, such as equals, contains, greater than, or less than.
• Value—enter a value to find in the selected field.

After selecting field options, you must click Add Criteria.

Details to know about criteria:

• Each criteria is then separated by an AND operator.
• Leave the data source criteria empty to collect all data from the sources.

Criteria

Filter a data source's data that you want to collect by adding criteria. This section covers the different criteria for each data source. It also includes what can be searched within each data source.

Inactive OneDrive criteria

The following table lists the filter criteria supported for OneDrive collections.

You must register Relativity in Microsoft 365 before using this data source. For information on registering Relativity in Microsoft 365, see Accessing Microsoft 365 tenants.

The following table lists the filter criteria support for Inactive OneDrive collections.

You must register Relativity in Microsoft 365 before using this data source. For information on registering Relativity in Microsoft 365, see Microsoft 365 - Inactive OneDrive data source.

When using search criteria to filter for Microsoft 365 OneDrive, different operators can return different results. Knowing the search operators is crucial.

The keyword search criteria uses the Search In operator. When using the Search In operator:

• Search for a phrase by entering the phrase without any OR operators into the Value text box.
  Example: acme corp contract
• Search for individual keywords by entering the keywords and separating them with an OR in the Value text box.
  Example: cat OR dog OR mouse
  Enter the OR operator with all capital letters. You should add keywords and phrases in lower case only.
• Keywords hit on matches and if a word is prefixed with a keyword.
  Example: "Work" will return "workday" and "workplace"

Inactive OneDrive filtering is file-based. Email-specific criteria such as sender, recipient, or message headers are not applicable to this data source.

Criteria	Operators	Description	Example
Creation Date	Equals, Does Not Equal, Greater Than, Greater Than or Equals, Less Than, Less Than or Equals	When you use the Creation Date property in a query, the search returns all messages that equal/doesn’t equal, greater/less than the date entered.	If you search “Greater Than 1/1/2001,” your results include all messages created after January 1, 2001.
File Extension	Equal, Does Not Equal, Contains	When you use the File Extension property in a query, the search returns all files that contain the entered file extension.	If you search “Contains docx,” your results include all Microsoft Word files saved with that extension.
File Name	Equal, Does Not Equal, Contains	When you use the File Name property in a query, the search returns all files that equals/does not equal or contain the value entered.	If you search “Equals Important_Document,” your results include all files with that text in the filename.
File Path	Equal, Does Not Equal, Contains	When you use the File Path property in a query, the search returns all messages equals/does not equal or contain the folder path entered.	If you search “Contains documents/Relativity,” your results include all files within the listed folder and any folder beyond the file path entered.
Keyword Search	Search In	When you use the Keyword Search property in a query, the search returns all files containing the searched text.	If you search “Relativity,” your results include all files that contain the searched text in the file.
Modification Date	Equals, Does Not Equal, Greater Than, Greater Than or Equals, Less Than, Less Than or Equals	When you use the Modification Date property in a query, the search returns all updated files that equal/doesn’t equal, greater/less than the date entered.	If you search “Less Than 1/1/2020,” your results include all files modified before January 1, 2020.

Troubleshooting

Common issues during inactive OneDrive collections include:

• Refresh token expiration during long‑running exports.
• Partial success where some files export successfully and others fail.
• Cleanup issues, such as temporary holds not being removed.
• File‑level errors rather than custodian‑level failures.

Job results and logs should be reviewed to identify which files were successfully collected and which encountered errors.