Set up a connector to archive SQL data
Use the SQL DataParser from 17a-4 LLC to import and archive data from a SQL database to user mailboxes in your Microsoft 365 organization. The DataParser includes a SQL connector that's configured to capture items from a third-party data source and import those items to Microsoft 365. The SQL DataParser connector converts SQL data to an email message format and then imports those items to user mailboxes in Microsoft 365.
After SQL 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 SQL 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, you can try all the premium features in Microsoft Purview for free. Use the 90-day Purview solutions trial to explore how robust 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 SQL data
The following overview explains the process of using a data connector to archive SQL data in Microsoft 365.
Your organization works with 17a-4 to set up and configure the SQL DataParser.
Regularly, SQL items are collected by the DataParser. The DataParser also converts the content of a message to an email message format.
The SQL DataParser connector that you create in the Microsoft Purview compliance portal connects to DataParser and transfers the messages to a secure Azure Storage location in the Microsoft cloud.
A subfolder in the Inbox folder named SQL DataParser is created in the user mailboxes, and the SQL items are imported to that folder. The connector determines which mailbox to import items to by using the value of the Email property. Every SQL 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 SQL DataParser 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 Defender and compliance portals" section in Roles and role groups in the Microsoft 365 Defender and Microsoft Purview compliance portals. 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 17a-4 data connector is available 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 a SQL DataParser connector
The first step is to access to the Data connectors page in the compliance portal and create a 17a-4 connector for SQL data.
Go to https://compliance.microsoft.com and then select Data connectors > SQL DataParser.
On the SQL DataParser 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 17a-4 account and complete the steps in the SQL DataParser connection wizard.
Step 2: Configure the SQL DataParser connector
Work with 17a-4 Support to configure the SQL DataParser connector.
Step 3: Map users
The SQL DataParser connector will automatically map users to their Microsoft 365 email addresses before importing data to Microsoft 365.
Step 4: Monitor the SQL DataParser connector
After you create a SQL DataParser 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 SQL DataParser connector that you created 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.
Submit and view feedback for