Set up a connector to archive Fuze data
Use the Fuze DataParser from 17a-4 LLC to import and archive data from Fuze to user mailboxes in your Microsoft 365 organization. The DataParser includes a Fuze connector that's configured to capture items from a third-party data source and import those items to Microsoft 365. The Fuze DataParser connector converts Fuze data to an email message format and then imports those items to user mailboxes in Microsoft 365.
After Fuze data is stored in user mailboxes, you can apply Microsoft 365 compliance features such as Litigation Hold, eDiscovery, retention policies and retention labels, and communication compliance. Using a Fuze connector to import and archive data in Microsoft 365 can help your organization stay compliant with government and regulatory policies.
Overview of archiving Fuze data
The following overview explains the process of using a data connector to archive Fuze data in Microsoft 365.
Your organization works with 17a-4 to set up and configure the Fuze DataParser.
On a regular basis, Fuze items are collected by the DataParser. The DataParser also converts the content of a message to an email message format.
The Fuze DataParser connector that you create in the Microsoft 365 compliance center connects to DataParser and transfers the messages to a secure Azure Storage location in the Microsoft cloud.
A subfolder in the Inbox folder named Fuze DataParser is created in the user mailboxes, and the Fuze items are imported to that folder. The connector determines which mailbox to import items to by using the value of the Email property. Every Fuze item contains this property, which is populated with the email address of every participant.
Before you set up a connector
Create a DataParser account for Microsoft connectors. To do this, contact 17a-4 LLC. You need to sign into this account when you create the connector in Step 1.
The user who creates the Fuze DataParser connector in Step 1 (and completes it in Step 3) must be assigned to the Mailbox Import Export role in Exchange Online. This role is required to add connectors on the Data connectors page in the Microsoft 365 compliance center. By default, this role is not assigned to a role group in Exchange Online. You can add the Mailbox Import Export role to the Organization Management role group in Exchange Online. Or you can create a role group, assign the Mailbox Import Export role, and then add the appropriate users as members. For more information, see the Create role groups or Modify role groups sections in the article "Manage role groups in Exchange Online".
Step 1: Set up a Fuze DataParser connector
The first step is to access to the Data connectors page in the Microsoft 365 compliance center and create a 17a-4 connector for Fuze data.
Go to https://compliance.microsoft.com and then click Data connectors > Fuze DataParser.
On the Fuze DataParser product description page, click Add connector.
On the Terms of service page, click Accept.
Enter a unique name that identifies the connector and then click Next.
Sign in to your 17a-4 account and complete the steps in the Fuze DataParser connection wizard.
Step 2: Configure the Fuze DataParser connector
Work with 17a-4 Support to configure the Fuze DataParser connector.
Step 3: Map users
The Fuze DataParser connector will automatically map users to their Microsoft 365 email addresses before importing data to Microsoft 365.
Step 4: Monitor the Fuze DataParser connector
After you create a Fuze DataParser connector, you can view the connector status in the Microsoft 365 compliance center.
Go to https://compliance.microsoft.com and click Data connectors in the left nav.
Click the Connectors tab and then select the Fuze DataParser connector that you created to display the flyout page, which contains the properties and information about the connector.
Under Connector status with source, click the Download log link to open (or save) the status log for the connector. This log contains data that has been imported to the Microsoft cloud.
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.