Enterprise Vault™ Setting up Microsoft Teams Archiving
- About this guide
- Introducing Microsoft Teams Archiving
- Configuring Microsoft Teams Archiving
- Steps to configure Microsoft Teams archiving
- Roles-based administration (RBA) and Microsoft Teams Archiving
- Assigning the permissions required for exporting data from Microsoft Teams
- Preparing to configure a Microsoft 365 connection
- Configuring a Microsoft 365 connection
- Configuring a Microsoft Teams policy
- Configuring an Importer
- Managing Teams archives
- Managing Teams archiving tasks
Configuring an Importer
The importer downloads Microsoft Teams data to Veritas Enterprise Vault.
Ensure that the connection to configure the importer is available in Enterprise Vault under .
Ensure that the holding folder in the Enterprise Vault server is available to receive the Microsoft Teams data. The holding folder path must be a local path on the Enterprise Vault server. The holding folder must be a shared folder so that the Merge1 server has access to it.
Be aware of the log folder path of the Merge1 server where the Merge1 importer logs are written. The log folder path must be a local path on the Merge1 server.
Note:
If the Merge1 administrator and Enterprise Vault Service Account user are different, add the Enterprise Vault Service Account user in the Local Administrator Group on the Merge1 server.
Note:
If a user logs on to the Enterprise Vault server using the Microsoft 365 Administrator or Power Administrator RBA role, in that case these RBA role accounts must be the part of Local Administrator group on the Merge1 server.
Ensure that the Merge1 server administrator user that you are using for configuring Teams archiving has been added in the local administrator group on the machine where the holding folder exists.
Be aware of the Vault Store that you want to use for the importer.
It is recommended that you use the Enterprise Vault Service account for your Merge1 server installation and configuration. However, if you have already installed and configured the Merge1 server with another account, you can use that account. You are recommended to add the following permissions for the Merge1 Importer Service account on the Merge1 server:
Local Administrator (must be a member of the Administrators' group)
Log on as Service rights
Log on as a batch job rights
Note:
Active Directory admin should not restrict the Enterprise Vault Service Account to have these permission on Merge1 server where It is used to the Run Importer as the windows service.
Ensure that the teams domain is added to the list of internal SMTP domains for marking correct message direction (internal or external). Navigate to to add the teams domain.
Note:
For collecting legacy data and daily data, it is recommended that you create two separate importers. To collect both legacy data and daily data, the administrator must manually start the Teams Archiving Task. For legacy data collection, the administrator must allow the importer download data for a few days and then start the Teams Archiving Task either in the or mode. For more information about the and modes, see Managing Teams archiving tasks.
The holding folder is the folder where Merge1 will dump the Microsoft Teams data and Enterprise Vault pick that data for the archiving.
The holding folder path must comply with the following conditions:
The folder is recommended to be on a local drive to the EV Server.
The folder should be excluded from virus scanning. Scanning the holding folder can cause the corruption of items, performance issues, and data loss.
The folder must be a shared folder and must be specified in UNC path format where-ever asked.
The maximum permitted length of folder path is (140 - importer's Name length) characters.
The machine to be configured for holding Teams chat data must be in the same domain as that of Enterprise Vault.
Provide shared access to the holding folder for the Vault Service account (VSA) administrator created on a server other than Enterprise Vault.
Perform one of the following actions to grant required permissions to the VSA administrator on the holding folder:
Add the VSA administrator to the local administrator group and ensure that the local administrator group has full control permission (for sharing and security) on the holding folder.
Or,
Provide the VSA administrator full control permission (for sharing and security) on the holding folder.
Add as Identity user in .
Set Application pool identity in .
While creating importer in the Enterprise Vault Administration Console, enter the shared folder path by copying and pasting it in the field.
This configuration allows notification requests to be received correctly from the Merge1 server to the Enterprise Vault server and the chat items segregation process is triggered successfully.
Installing the Merge1 server with the Merge1 server Administrator user instead of Enterprise Vault Service Account user, sets the Merge1 Server administrator user in the application pool of Merge1 Server. That is:
The service account set for an importer, which is created from the Enterprise Vault Admin Console is Domain\VSA administrator.
In this scenario, assign the Merge1 Server Administrator and Domain\VSA administrator full control permission (for sharing and security) on the holding folder while creating the importer.
Add the Domain\VSA administrator user to the local administrators group on the Merge1 server.
This configuration allows notification requests to be received correctly from Merge1 server to Enterprise Vault server and chat items seUse the Vault Service accountgregation process is triggered successfully.
In the left pane of the Enterprise Vault Administration Console, click .
To create a new importer, right-click on and select .
In the wizard, click .
Enter the following details in the corresponding text boxes and click :
Enter an appropriate and unique name for the new importer.
Enter an appropriate description for the new importer.
Select the account under which the importer will run.
: Select this option if you want to configure the Vault Service account as the user account for the importer service account. Then, click and enter the password of the Vault Service account.
: Select this option if you want to configure the importer service account with a user account other than the Vault Service account. From the drop-down list, select the user or browse for the domain user account, and enter the password in the and fields. Click .
The selected user account must have the following permissions:
Local Administrator (must be a member of the Administrators' group) on the Enterprise Vault server
Local Administrator (must be a member of the Administrators' group) on the Merge1 server
Log on as Service rights on the Merge1 server
Log on as a batch job rights on the Merge1 server
db_owner of the Merge1 database
Select the following and click :
: From the dropdown list, select connection.
: Select the Microsoft Teams holding folder path to receive the Microsoft Teams data
: Select the location of the log folder of the Merge1 server where the Merge1 importer logs are written.
Specify the users whose data will be collected by the importer:
To collect data for all users, select .
To collect data for specific users, select .
To manually enter email IDs and display names of specific users, click and enter the user details. Click .
To import specific users from a CSV file, click and select the CSV file. Click .
Entries in the CSV file should be present in the following format:
<Email Address1>,<Username1>
<Email Address2>,<Username2>
...
...
Click .
Specify the Date Range for which importer will collect the Microsoft Teams data.
: Select this option to collect the Microsoft Teams data for all the time without any date filter criteria. It will continuously keep on collecting the Microsoft Teams data whenever data is available.
: Select this option to collect the Microsoft Teams data for the specific date range. If you select this option, you must select at least one of the checkboxes - and - to specify the date range for data collection.
: Select this option to collect the Microsoft Teams data from a specific date only. Team data prior to this date will not be collected.
: Select this option to collect the Microsoft Teams data up to a specific date only. Microsoft Teams data after this date will not be collected.
Note:
Once data for the specific date range is collected we cannot collect the data prior to this date range by modifying it from the importer's properties. Importer will always collect the data from the date where it last collected the data.
Click .
Select the following:
The Teams policy that you want to apply on the importer.
The retention category that you want to use for the importer.
Click .
Select the Vault Store that you want to use for the importer.
Note:
The Microsoft Teams Archive and the Teams Archiving Task for the importer are created on the same machine where the Vault Store is present.
Review the new importer configurations and click .
In the left pane of the Enterprise Vault Administration Console, click .
The right pane of the Administration Console displays the available importers.
Right-click on an importer to perform the following actions:
: Allows you to enable the importer.
: Allows you to disable the importer. This is needed to modify the importer's properties and to delete the importer.
: Allows you to run the importer, which will collect the Microsoft Teams data.
Allows you to delete the importers. Importer should be in the disabled state to perform this operation.
: Allows you to view and update the importer properties. You can double-click on an importer to view and update the properties. For updating the importer properties, importer must be in disabled state. For more information, see the steps below.
To update an importer, double-click on it.
Note:
If you want to update an importer, ensure that the importer is in the disabled state.
The importer properties dialog box is displayed and contains the following tabs:
: The section displays the importer name, description, status, and the Teams archiving task associated with the importer.
The section displays the Teams archive name and the Teams policy applied on the importer. You can update the settings, if required.
The section displays the retention category. You can update the retention category settings, if required.
: Displays the user account for the importer service account. You can update the service account, if required.
: Select this option if you want to configure the Vault Service account as the user account for the importer service account. Then, click and enter the password of the Vault Service account.
: Select this option if you want to configure the importer service account with a user account other than the Vault Service account. From the drop-down list, select the user or browse for the domain user account, and enter the password in the and fields. Click .
The selected user account must have the following permissions:
Local Administrator (must be a member of the Administrators' group) on the Enterprise Vault server
Local Administrator (must be a member of the Administrators' group) on the Merge1 server
Log on as Service rights on the Merge1 server
Log on as a batch job rights on the Merge1 server
db_owner of the Merge1 database
: The section displays the available connections with the Merge1 server on which the importer has been created. You can update the connection, if required.
The section displays the path of the Microsoft Teams holding folder which receives the Microsoft Teams data from the Merge1 server. You can update the holding folder path, if required. Before updating the holding folder location for the importer, perform the following steps:
Step 1: In the Enterprise Vault Administration Console, stop the importer's Teams Archiving task.
Step 2: Copy the existing content of the current holding folder tree to the new location.
The section displays the path of the log folder of the Merge1 server where the Merge1 importer logs are stored. You can update the log folder path, if required.
: Specify the users whose data will be collected by the importer:
To collect data for all users, select .
To collect data for specific users, select .
To manually enter email IDs and displays names of specific users, click and enter the user details. Click .
To import specific users from a CSV file, click and select the CSV file. Click .
Entries in the CSV file should be present in the following format:
<Email Address1>,<Username1>
<Email Address2>,<Username2>
...
...
: Specify the Date Range for which importer will collect the Microsoft Teams data.
: Select this option to collect the Microsoft Teams data for all the time without any date filter criteria. It will continuously keep on collecting the Microsoft Teams data whenever data is available.
: Select this option to collect the Microsoft Teams data for the specific date range. If you select this option, you must select at least one of the checkboxes - and - to specify the date range for data collection.
: Select this option to collect the Microsoft Teams data from a specific date only. Team data prior to this date will not be collected.
: Select this option to collect the Microsoft Teams data up to a specific date only. Microsoft Teams data after this date will not be collected.
Note:
Importer will always collect the data from the date where it last collected the data.
: The configurations to schedule running of the importer.
The Interval section allows you to select 1 hour or 15 minutes to schedule running of the importer.
You can also select specific time slots on specific days of the week to schedule running of the importer by clicking on the time scheduler at the bottom of the dialog box.
: Displays the batch size of the Merge1 notifications. The batch size of the number of copied files initiates Merge1 to send notifications to Enterprise Vault. The default batch size is 50.
Click if you want to change the existing batch.
Click .
If you have updated the holding folder location, perform one of the following actions:
Restart the Merge1WebHookPool in the IIS Manager application pools. Or,
Restart the IIS server.
Enable the importer.
Start the corresponding Teams Archiving task.