Capturing Proprietary Content into Microsoft Purview for Copilot

17a-4’s DataParser supports capture of over 30 different types of messaging and collaboration data.  These include the main interfaces like Slack, Webex, Symphony and Zoom and extend to industry standard sources such as mailboxes and databases.  These connectors directly collect from the source to format, filter and deliver the messages, files, texts and images directly into M365.  However, certain clients also have proprietary content that they would like to manage in Microsoft Purview.  Some of this content will also be useful in Copilot.  Rather than developing these as dedicated connections, 17a-4 has developed an API in DataParser Hub that offers a formatted schema for ingestion, relieving clients of the complexity of developing an integration with M365. 

“We’ve already developed the necessary interfaces with M365 so any data our clients want to send into Hub can appear in their users’ Outlook, be available to Purview’s Communications Compliance and eDiscovery and be incorporated into Copilot.” offers Tom Sinistore, VP of Sales. 

“Working with large financial and regulated clients,” continues Mr. Sinistore, “we find some have no solution to capturing outlier content, it could be from a custom, internal system or maybe it’s an export of JSON data from Agentic AI.  With Hub, clients can now feed that data in for the delivery to their Purview, Copilot or just to store in Azure Blob.  There are a lot of possibilities.” 

“Of course, there’s a regulatory requirement to archive all forms of client messaging,” adds Douglas Weeden, Director of Compliance and eDiscovery, “but now we’re also seeing requests to incorporate content into Copilot.  Often clients don’t want to expose an entire database or server that might include PII [Personally Identifiable Information] or IP [Intellectual Property] but would like to allow certain data elements of a system that could add value to their Copilot capabilities.” 

DataParser Hub output may be integrated with a client’s Active Directory and use attributes to determine destination. Metadata can be included to indicate data type, classification, or other search criteria.

DataParser Hub now provides the extension to Copilot across all messaging and data in the organization. 

Request a free trial of DataParser Hub.