Set up a connector to archive Pivot data

Note

Microsoft 365 compliance is now called Microsoft Purview and the solutions within the compliance area have been rebranded. For more information about Microsoft Purview, see the blog announcement.

Use a Veritas connector in the Microsoft Purview compliance portal to import and archive data from the Pivot platform to user mailboxes in your Microsoft 365 organization. Veritas provides you with a Pivot connector that is configured to capture items from the third-party data source (on a regular basis) and then import those items to Microsoft 365. Pivot is an instant messaging platform that allows collaboration with financial market participants. The connector converts items such as chat messages, from a users' Pivot accounts to an email message format and then imports those items to the user mailboxes in Microsoft 365.

After Pivot data is stored in user mailboxes, you can apply Microsoft Purview features such as Litigation Hold, eDiscovery, retention policies and retention labels, and communication compliance. Using a Pivot connector to import and archive data in Microsoft 365 can help your organization stay compliant with government and regulatory policies.

Overview of archiving Pivot data

The following overview explains the process of using a connector to archive the Pivot data in Microsoft 365.

Archiving workflow for Pivot data.

  1. Your organization works with Pivot to set up and configure a Pivot source site.

  2. Once every 24 hours, Pivot items are copied to the Veritas Merge1 site. The connector also converts the Pivot items to an email message format.

  3. The Pivot connector that you create in the compliance portal, connects to the Veritas Merge1 site every day and transfers the Pivot items to a secure Azure Storage location in the Microsoft cloud.

  4. The connector imports the Pivot items to the mailboxes of specific users by using the value of the Email property of the automatic user mapping as described in Step 3. A subfolder in the Inbox folder named Pivot is created in the user mailboxes, and the items are imported to that folder. The connector does this by using the value of the Email property. Every Pivot item contains this property, which is populated with the email address of every participant of the item.

Before you begin

  • Create a Veritas Merge1 account for Microsoft connectors. To create this account, contact Veritas Customer Support. You will sign into this account when you create the connector in Step 1.

  • The user who creates the Pivot 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 the "Roles in the security and compliance centers" section in Permissions in the Security & Compliance Center. 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 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 are not 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 Pivot connector

The first step is to access to the Data Connectors page in the Microsoft compliance center and create a connector for Pivot data.

  1. Go to https://compliance.microsoft.com and then click Data connectors > Pivot.

  2. On the Pivot product description page, click Add connector.

  3. On the Terms of service page, click Accept.

  4. Enter a unique name that identifies the connector and then click Next.

  5. Sign in to your Merge1 account to configure the connector.

Step 2: Configure the Pivot connector on the Veritas Merge1 site

The second step is to configure the Pivot connector on the Merge1 site. For information about how to configure the Pivot connector on the Veritas Merge1 site, see Merge1 Third-Party Connectors User Guide.

After you click 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 Microsoft 356 compliance center, follow these steps:

  1. On the Map Pivot users to Microsoft 365 users page, enable automatic user mapping. The Pivot 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.

  2. Click Next, review your settings, and go to the Data connectors page to see the progress of the import process for the new connector.

Step 4: Monitor the Pivot connector

After you create the Pivot connector, you can view the connector status in the compliance portal.

  1. Go to https://compliance.microsoft.com and click Data connectors in the left nav.

  2. Click the Connectors tab and then select the Pivot connector to display the flyout page. This page contains the properties and information about the connector.

  3. Under Connector status with source, click 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.

Known issues

  • 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.