Search <book_title>...

Enterprise Vault™ Setting up Microsoft Teams Archiving

Last Published: 2024-09-02

Product(s): Enterprise Vault (15.1)

About this guide
1. Introducing this guide
2. Where to get more information about Enterprise Vault
  1. Enterprise Vault training modules
Introducing Microsoft Teams Archiving
1. About Enterprise Vault Microsoft Teams Archiving
  1. Microsoft Teams Archiving Overview
  2. Microsoft Teams Archiving Components
Configuring Microsoft Teams Archiving

Preparing to configure a Microsoft 365 connection

The New Connection wizard enables you to add a connection and perform the following actions:

Connect to the Azure Active Directory
Configure Importers for collection of Microsoft Teams data

Prerequisites: Information required from the Microsoft Azure administrator

Ensure that you have the following information available with you from your Microsoft Azure administrator:

Application ID and Tenant ID which you have copied at step 5 in Assigning the permissions required for exporting data from Microsoft Teams.
X509 certificate's thumbprint or X509 certificate and its password

Prerequisites: Information required from the Veritas Merge1 administrator

Ensure that you have the following information available with you from your Veritas Merge1 administrator:

Note:

To learn how to collect the Merge1 information, see Collecting Merge1 information.

Merge1 instance URL
API Client Application ID associated with the Merge1 server
API Client Secret associated with the Merge1 server

Prerequisites: Acquiring a certificate thumbprint

Merge1 requires an SSL certificate to use in the authentication flow. This certificate must be generated by the customer and the certificate thumbprint must be entered in the "X509 Certificate Thumbprint" field of Connector Configuration.

Note:

If you want to generate your own X.509 certificate, see Steps to generate a self-signed certificate (X.509) for the Merge1 server.

You can also use the same certificate used by Merge1 Web Application, to do this launch PowerShell and run the following command, which might return several certificates. Choose the one depending on your requirements and copy the thumbprint.

Get-ChildItem -path cert:\LocalMachine\My

Prerequisites: Setting up the Data Access Account

To be able to create a connection, the Data Access Account must be set on the Directory properties. You must create an Enterprise Vault anonymous user. For more information about creating an anonymous user, see https://www.veritas.com/support/en_US/article.100022472.

If you already have a Data Access Account user created, you can use the same account. You must re-enter the credentials associated with the account at Directory properties > Data Access Account, so that the user account is configured in the IIS Merge1WebHook application.

Prerequisites: Installing the Enterprise Vault site certificate from IIS on the Merge1 server

You must install the Enterprise Vault site certificate from IIS on the Merge1 server under Trusted Root Certification Authorities.

Prerequisites: Installing the Enterprise Vault site certificate from IIS on the Merge1 agent

You must install the Enterprise Vault site certificate from IIS on the Merge1 agent under Trusted Root Certification Authorities.

Prerequisites: Installing the Merge1 server certificate on the Merge1 agent

You must install the Merge1 server certificate from IIS on the Merge1 agent under the Trusted Root Certification Authorities.

Prerequisites: Installing the Merge1 server certificate on the Enterprise Vault server

Install the Merge1 server self-signed certificate or X509 certificate of the Merge1 server (uploaded on the Microsoft Azure portal) under the local machine's trusted root on the Enterprise Vault server.

Prerequisites: Installing the Merge1 agent certificate on the Enterprise Vault server

You must install the Merge1 agent certificate from IIS on the Enterprise Vault server.