Set up a connector to archive Twitter data (preview)
Use a Veritas connector in the Microsoft Purview compliance portal to import and archive data from the Twitter platform to user mailboxes in your Microsoft 365 organization. Veritas provides a Twitter connector that is configured to capture items from a third-party data source and import those items to Microsoft 365. The connector converts content such as tweets, retweets, and comments from Twitter to an email message format and then imports those items to the user mailboxes in Microsoft 365.
After Twitter data is stored in user mailboxes, you can apply Microsoft Purview features such as Litigation Hold, eDiscovery, retention policies and retention labels. Using a Twitter connector to import and archive data in Microsoft 365 can help your organization stay compliant with government and regulatory policies.
If you're not an E5 customer, use the 90-day Microsoft Purview solutions trial to explore how additional Purview capabilities can help your organization manage data security and compliance needs. Start now at the Microsoft Purview compliance portal trials hub. Learn details about signing up and trial terms.
Overview of archiving Twitter data
The following overview explains the process of using a connector to archive Twitter data in Microsoft 365.
Your organization works with Twitter to set up and configure a Twitter site. Your organization also works with Veritas to set up a Merge1 site.
Once every 24 hours, Twitter items are copied to the Veritas Merge1 site. The connector also converts Twitter items to an email message format.
The Twitter connector that you create in the compliance portal connects to the Veritas Merge1 site every day, and transfers the Twitter content to a secure Azure Storage location in the Microsoft cloud.
The connector imports the converted items to the mailboxes of specific users using the value of the Email property of the automatic user mapping as described in Step 3. A subfolder in the Inbox folder named Twitter is created in the user mailboxes, and items are imported to that folder. The connector determines which mailbox to import items to by using the value of the Email property. Every Twitter item contains this property, which is populated with the email address of every participant of the item.
Before you set up a connector
Create a Merge1 account for Microsoft connectors. To create this account, contact Veritas Customer Support. You need to sign into this account when you create the connector in Step 1.
Create a Twitter application at https://developer.twitter.com to fetch data from your Twitter account. For step-by step instructions about creating the application, see Merge1 Third-Party Connectors User Guide.
The user who creates the YouTube connector in Step 1 (and completes it in Step 3) must be assigned the Data Connector Admin role. This role is required to add connectors on the Data connectors page in the compliance portal. This role is added by default to multiple role groups. For a list of these role groups, see Roles in Microsoft Defender for Office 365 and Microsoft Purview compliance. Alternatively, an admin in your organization can create a custom role group, assign the Data Connector Admin role, and then add the appropriate users as members. For instructions, see the "Create a custom Microsoft Purview role group" section in Permissions in the Microsoft Purview compliance portal.
This Veritas data connector is in public preview in GCC environments in the Microsoft 365 US Government cloud. Third-party applications and services might involve storing, transmitting, and processing your organization's customer data on third-party systems that are outside of the Microsoft 365 infrastructure and therefore aren't covered by the Microsoft Purview and data protection commitments. Microsoft makes no representation that use of this product to connect to third-party applications implies that those third-party applications are FEDRAMP compliant.
Step 1: Set up the Twitter connector
The first step is to access to the Data Connectors page in the compliance portal and create a connector for Twitter data.
Go to https://compliance.microsoft.com and then select Data connectors > Twitter.
On the Twitter product description page, select Add connector.
On the Terms of service page, select Accept.
Enter a unique name that identifies the connector, and then select Next.
Sign in to your Merge1 account to configure the connector.
Step 2: Configure the Twitter on the Veritas Merge1 site
The second step is to configure the Twitter connector on the Veritas Merge1 site. For information about how to configure the Twitter connector, see Merge1 Third-Party Connectors User Guide.
After you select Save & Finish, the User mapping page in the connector wizard in the compliance portal is displayed.
Step 3: Map users and complete the connector setup
To map users and complete the connector setup in the compliance portal, follow these steps:
On the Map Twitter users to Microsoft 365 users page, enable automatic user mapping. The Twitter items include a property called Email, which contains email addresses for users in your organization. If the connector can associate this address with a Microsoft 365 user, the items are imported to that user's mailbox.
Select Next, review your settings, and then go to the Data connectors page to see the progress of the import process for the new connector.
Step 4: Monitor the Twitter connector
After you create the Twitter connector, you can view the connector status in the compliance portal.
Go to https://compliance.microsoft.com/ and select Data connectors in the left nav.
Select the Connectors tab and then select the Twitter connector to display the flyout page, which contains the properties and information about the connector.
Under Connector status with source, select the Download log link to open (or save) the status log for the connector. This log contains information about the data that's been imported to the Microsoft cloud. For more information, see View admin logs for data connectors.
- At this time, we don't support importing attachments or items that are larger than 10 MB. Support for larger items will be available at a later date.