Overview
- M365 Teams is used by organizations for internal communications. Teams data carries important conversations and documents which need to be frequently backed up.
- Using the LegacyFlo Teams-S3-ZIP or Teams-S3-PST request types, you can now backup Teams conversations into emails which are saved on a S3 bucket in your account
Step 1: Getting access to the Teams data
This is a one-time process, in which you generate the Graph API access key and register with LegacyFlo.
Follow the steps given here.
Step 2: Register the S3 bucket with LegacyFlo
The S3 bucket has to be registered with LegacyFlo (this is a one time activity). For the steps on registration, refer to this article.
Step 3: Submitting a LegacyFlo request
You can submit requests to back up Teams communication data using the LegacyFlo interface.
The request type to be used is Teams-S3-ZIP or Teams-S3-PST.
Source Information
| FIELD NAME | DESCRIPTION | SAMPLE VALUE |
|---|---|---|
| User ID | User id on M365 domain whose data needs to be retrieved (Note: The id should not contain the domain name.) | "john" |
| Domain | Source domain on M365 | "baya.com" |
| Operation Type | There are three options to choose from 1. OneOnOne 2. Group 3. Both If you choose OneOnOne, all the Teams one on one chats for the user will be retrieved. If you choose Group, all the Teams group chats for the user will be retrieved. If you choose Both, then one on one and group chats for the user will be retrieved. | OneOnOne |
| Include JSON Response | By default, all chat communications are converted to email in the HTML format and any documents shared are attached to the mail. The Include JSON Response option should be enabled if you wish to add the RAW JSON returned by the Graph API as an additional attachment. |
Date Filter
| FIELD NAME | DESCRIPTION | SAMPLE VALUE |
|---|---|---|
| Since (YYYY-MM-DD) | Start date from which to copy/move content. All content created/modified ON or AFTER the start date and BEFORE the end date will be copied/moved. This is an optional parameter and if left blank, all contents before the Before date will be moved or copied. | 2019-01-01 |
| Before (YYYY-MM-DD) | End date before which to copy/move content. The content created/modified ON or AFTER the start date and BEFORE the end date will be copied/moved. This is an optional parameter and if left blank, all contents added or modified ON or AFTER the Since date will be copied/moved. | 2019-02-01 |
Destination Information
| FIELD NAME | DESCRIPTION |
|---|---|
| S3 bucket name | The S3 bucket for the destination file. Select the S3 bucket name from the drop-down list. The list will show all the registered S3 buckets including the S3 buckets which host the Vaultastic Open and Deep stores. |
| S3 folder path | If the file has to be created on the Vaultastic Open or Deep Stores, then this parameter will have to start with the name of your Vaultastic domain. Example: baya-com.vaultastic.com For example, if you want to create a file on the root of the Vaultastic domain baya-com.vaultastic.com, then enter "baya-com.vaultastic.com". If the file has to be created in a sub-folder called 'Files", then enter "baya-com.vaultastic.com/Files" If the file is to be created on your own bucket, give the folder which will contain the file. Leave this value empty if the destination file has to be created on the root of the S3 bucket. NOTE: S3 folder path should not start or end with a "/" |
| File name | The destination filename. The file that will contain the results of the LegacyFlo command NOTE: Filenames should not start or end with a "/" |
Step 4 (optional): Submitting multiple LegacyFlo requests to backup data for multiple users
To upload multiple jobs using a CSV, create a CSV file with a list of all the users and other details required to upload data.