Import non-Office 365 content for Advanced eDiscovery analysis

Not all documents that you may need to analyze with Office 365 Advanced eDiscovery will live in Office 365. With the Non-Office 365 content import feature in Advanced eDiscovery you can upload documents that don't live in Office 365 (except PST files) into a case linked, Azure storage blob and analyze them with Advanced eDiscovery. This procedure shows you how to bring your non-Office 365 documents into Advanced eDiscovery for analysis.

Note: Advanced eDiscovery requires an Office 365 E3 with the Advanced Compliance add-on or an E5 subscription for your organization. If you don't have that plan and want to try Advanced eDiscovery, you can sign up for a trial of Office 365 Enterprise E5.

Note: You can purchase an Office 365Advanced eDiscovery data storage add-on subscription for your non-Office 365 content. This is exclusively available for content that is to be analyzed with Advanced eDiscovery. Follow the steps in Buy or edit and add-on for Office 365 for business and purchase the Office 365 Advanced eDiscovery storage add-on.

Before you begin

Using the upload Non-Office 365 feature as described in this procedure requires that you have:

  • An Office 365 E3 with Advanced Compliance add-on or E5 subscription

  • All custodians whose non-Office 365 content will be uploaded must have E3 with Advanced Compliance add-on or E5 licenses

  • An existing eDiscovery case

  • All the files for uploading gathered into folders where there is one folder per custodian and the folders' name is in this format alias@domainname. The alias@domainname must be users Office 365 alias and domain.

  • An account that is either an eDiscovery Manager or eDiscovery Administrator

  • Microsoft Azure Storage Explorer installed on a computer that has access to the non-Office 365 content folder structure. Optionally, any Azure content upload tool will work.

Upload non-Office 365 content into Advanced eDiscovery

  1. As an eDiscovery Manager or eDiscovery Administrator, open eDiscovery, and open the case that the non-Office 365 data will be uploaded to. If you need to create a case, see Manage eDiscovery cases in the Office 365 Security & Compliance Center

  2. Click Switch to Advanced eDiscovery

  3. Under Source type select Non-Office 365 data.

  4. Click Add container. Name the container and add a description.

  5. Select the newly added container from the container list and copy the URL that appears in the container details pane and then close the pane

  6. Expand the Explorer pane in Azure Storage Explorer (click toggle Explorer window )and expand (Local and Attached).

  7. Right click Storage Accounts and select Connect to Azure storage...

  8. In the Connect to Azure Storage window, select Use a shared access signature (SAS) URI or connection string and click Next.

  9. In the Attach using SAS window, select Use a SAS URI and paste the URI in. Click Next.

  10. Review the information in the Connection Summary window and click Connect.

  11. If you have multiple folders, upload the non-Office 365 content folder structure by dragging and dropping them into Azure Storage Explorer or if you have just one or a few, through the Upload >Upload Folder option.

    Important: There must be one root folder per user and the folder name must be in the alias@domainname format.

  12. Once the folders have finished uploading, switch back to Advanced eDiscovery. The content in the folders you uploaded is now ready to be processed in Advanced eDiscovery. Select the container and click the Process button. For more details on Advanced eDiscovery Processing see, Run the Process module and load data in Office 365 Advanced eDiscovery

    Important: Once the container is successfully processed in Advanced eDiscovery, you will no longer be able to add new content to the SAS storage in Azure. If you collect additional content and you want to add it to the case for Advanced eDiscovery analysis, you must create a new Non-Office 365 data container and repeat this procedure.

    Note: If the container does not process successfully due to folder naming issues and you then fix the issues, note that while the container will still be available, the URL/SAS token will have changed, so you will need to reconnect using the new URL/SAS token.

Connect with an expert
Contact us
Expand your skills
Explore training

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×