გაზიარება არხიდან:


Learn about connectors for third-party data

Microsoft 365 lets administrators use data connectors to import and archive non-Microsoft, third-party data from social media platforms, instant messaging platforms, and document collaboration platforms, to mailboxes in your Microsoft 365 organization. One primary benefit of using data connectors to import and archive third-party data in Microsoft 365 is that you can apply various Microsoft Purview solutions to the data after you import it. This approach helps you ensure that your organization's non-Microsoft data complies with the regulations and standards that affect your organization.

Third-party data connectors

The Microsoft Purview portal provides native third-party data connectors from Microsoft to import data from various data sources, such as LinkedIn, Instant Bloomberg, and Twitter. It also provides data connectors that support the Insider risk management solution.

In addition to these native data connectors, Microsoft works with the following partners to provide many more third-party data connectors in portals. Your organization works with these partners to set up their archiving service before creating a corresponding data connector in one of the portals.

Important

All partner third-party data connector configurations require a provisioned service principal for the partner application. This requirement isn't applicable for native Microsoft third-party data connector configurations.

To provision a service principal using PowerShell, see Provision a service principal for partner third-party data connectors.

The third-party data listed in the next sections (except for HR data and physical badging data that the Microsoft Purview Insider Risk Management solution uses) imports into user mailboxes. The Microsoft Purview solutions that support third-party data apply to the user mailbox where the data is stored.

Important

All Veritas data connectors in Microsoft Purview were retired on June 30, 2024. Non-Veritas data connectors in your organization aren't affected by this change. Contact your Veritas account representative if you have questions about Veritas archiving services.

Microsoft Purview data connectors

The following table lists the native third-party data connectors available in the Microsoft Purview portal. The table also summarizes the compliance solutions that you can apply after you import and archive third-party data in Microsoft 365. For a more detailed description of each compliance solution and how it supports third-party data, see the Overview of compliance solutions that support third-party data section.

Select the link in the Third-party data column to go to the step-by-step instructions for creating a connector for that data type.

Third-party data Litigation Hold eDiscovery Retention settings Records management Communication Compliance Insider Risk Management
Bloomberg Message Check mark. Check mark. Check mark. Check mark. Check mark.
ChatGPT Enterprise AI interactions Check mark. Check mark. Check mark. Check mark. Check mark.
Facebook Check mark. Check mark. Check mark. Check mark. Check mark.
Generic EHR healthcare Check mark.
Human resources (HR) Check mark.
ICE Chat Check mark. Check mark. Check mark. Check mark. Check mark.
Instant Bloomberg Check mark. Check mark. Check mark. Check mark. Check mark.
LinkedIn Check mark. Check mark. Check mark. Check mark.
Physical badging Check mark.
Third-party insider risk detections (preview) Check mark.
Twitter Check mark. Check mark. Check mark. Check mark.

TeleMessage data connectors

Important

All partner third-party data connector configurations require a provisioned service principal for the partner application. This requirement isn't applicable for native Microsoft third-party data connector configurations.

To provision a service principal using PowerShell, see Provision a service principal for partner third-party data connectors.

The following table lists the third-party data connectors available through the partnership with TeleMessage. The table also summarizes the compliance solutions you can apply to third-party data after you import and archive it in Microsoft 365. For more information about each compliance solution and how it supports third-party data, see the Overview of compliance solutions that support third-party data section.

Before you can archive third-party data in Microsoft 365, you need to work with TeleMessage to set up their archiving service for your organization. For more information, select the link in the Third-party data column to go to the step-by-step instructions for creating a connector for that data type.

You can also use TeleMessage data connectors in GCC environments in the Microsoft 365 US Government cloud. For more information, see the Data connectors in the US Government cloud section in this article.

Third-party data Litigation Hold eDiscovery Retention settings Records management Communication Compliance Insider Risk Management
Android Check mark. Check mark. Check mark. Check mark. Check mark.
AT&T Network Check mark. Check mark. Check mark. Check mark. Check mark.
Bell Network Check mark. Check mark. Check mark. Check mark. Check mark.
Enterprise Number Check mark. Check mark. Check mark. Check mark. Check mark.
Hong Kong CSL Network Check mark. Check mark. Check mark. Check mark. Check mark.
O2 Network Check mark. Check mark. Check mark. Check mark. Check mark.
Rogers Network Check mark. Check mark. Check mark. Check mark. Check mark.
Signal Check mark. Check mark. Check mark. Check mark. Check mark.
T-Mobile Check mark. Check mark. Check mark. Check mark. Check mark.
Telegram Check mark. Check mark. Check mark. Check mark. Check mark.
TELUS Network Check mark. Check mark. Check mark. Check mark. Check mark.
Verizon Network Check mark. Check mark. Check mark. Check mark. Check mark.
WeChat Check mark. Check mark. Check mark. Check mark. Check mark.
WhatsApp Check mark. Check mark. Check mark. Check mark. Check mark.

17a-4 data connectors

Important

All partner third-party data connector configurations require a provisioned service principal for the partner application. This requirement isn't applicable for native Microsoft third-party data connector configurations.

To provision a service principal using PowerShell, see Provision a service principal for partner third-party data connectors.

The following table lists the third-party data connectors available through a partnership with 17a-4 LLC. The table also summarizes the compliance solutions you can apply to third-party data after you import and archive it in Microsoft 365. For a detailed description of each compliance solution and how it supports third-party data, see the Overview of compliance solutions that support third-party data section.

Before you can archive third-party data in Microsoft 365, you need to work with 17a-4 LLC to set up their archiving service (called DataParser) for your organization. For more information, select the link in the Third-party data column to go to the step-by-step instructions for creating a connector for that data type.

You can also use 17a-4 data connectors in GCC environments in the Microsoft 365 US Government cloud. For more information, see the Data connectors in the US Government cloud section in this article.

Third-party data Litigation Hold eDiscovery Retention settings Records management Communication Compliance Insider Risk Management
BlackBerry Check mark. Check mark. Check mark. Check mark. Check mark.
Bloomberg Check mark. Check mark. Check mark. Check mark. Check mark.
Cisco Jabber Check mark. Check mark. Check mark. Check mark. Check mark.
Cisco Webex Check mark. Check mark. Check mark. Check mark. Check mark.
FactSet Check mark. Check mark. Check mark. Check mark. Check mark.
Fuze Check mark. Check mark. Check mark. Check mark. Check mark.
FX Connect Check mark. Check mark. Check mark. Check mark. Check mark.
ICE Chat Check mark. Check mark. Check mark. Check mark. Check mark.
InvestEdge Check mark. Check mark. Check mark. Check mark. Check mark.
LivePerson Conversational Cloud Check mark. Check mark. Check mark. Check mark. Check mark.
Quip Check mark. Check mark. Check mark. Check mark. Check mark.
Refinitiv Eikon Messenger Check mark. Check mark. Check mark. Check mark. Check mark.
ServiceNow Check mark. Check mark. Check mark. Check mark. Check mark.
Skype for Business Server Check mark. Check mark. Check mark. Check mark. Check mark.
Slack Check mark. Check mark. Check mark. Check mark. Check mark.
SQL Check mark. Check mark. Check mark. Check mark. Check mark.
Symphony Check mark. Check mark. Check mark. Check mark. Check mark.
Zoom Check mark. Check mark. Check mark. Check mark. Check mark.

CellTrust data connectors

Important

All partner third-party data connector configurations require a provisioned service principal for the partner application. This requirement isn't applicable for native Microsoft third-party data connector configurations.

To provision a service principal using PowerShell, see Provision a service principal for partner third-party data connectors.

The following table lists the third-party data connector available through a partnership with CellTrust. The table also summarizes the compliance solutions you can apply to third-party data after you import and archive it in Microsoft 365. For a more detailed description of each compliance solution and how it supports third-party data, see the Overview of compliance solutions that support third-party data section.

Before you can archive third-party data in Microsoft 365, you need to work with CellTrust to set up their archiving service, CellTrust SL2, for your organization. For more information, select the link in the Third-party data column to go to the step-by-step instructions for creating a CellTrust SL2 connector.

Third-party data Litigation Hold eDiscovery Retention settings Records management Communication Compliance Insider Risk Management
CellTrust SL2 Check mark. Check mark. Check mark. Check mark. Check mark.

The CellTrust SL2 data connector is also available in GCC environments in the Microsoft 365 US Government cloud. For more information, see the Data connectors in the US Government cloud section in this article.

Provision a service principal for third-party data connectors

For partner third-party data connectors, you must configure a service principal. Complete the following steps to configure a service principal for your organization:

  1. Open PowerShell and confirm the Azure CLI is installed:

    az version
    
  2. Sign in with the administrator account for your organization:

    az login
    
  3. Run the following cmdlet to create the service principal for your organization:

    az ad sp create --id <PartnerAppId>
    

Overview of Microsoft Purview solutions that support third-party data

The following sections describe how Microsoft Purview solutions help you manage the third-party data listed in the previous table.

Communication Compliance

Use Microsoft Purview Communication Compliance to examine third-party data to make sure it complies with your organization's data standards. You can detect, capture, and take remediation actions for inappropriate messages in your organization. For example, you can monitor the third-party data that you import for offensive language, sensitive information, and regulatory compliance.

eDiscovery

Microsoft Purview eDiscovery is the primary legal investigation tool in Microsoft 365. Use eDiscovery to add custodians to a case, place a custodian's data on hold, and load a custodian's third-party data into a review set for further analysis such as themes and duplicate detection. After you load third-party data into a review set, you can query and filter it to a narrow result set. Use eDiscovery to manage third-party data that might be relevant to your organization's legal or internal investigations.

You can also use eDiscovery to search for and create query-based holds to preserve third-party data. To search for third-party data imported to user mailboxes, use the kind:externaldata property in your search query. To search for a specific type of third-party data, use the itemclass:ipm.externaldata.<third-party data type> mailbox property. For more information, see Find content in mailboxes and Use Keyword Query Language to create search queries.

Insider Risk Management

By using signals from third-party data, such as selective HR data, Microsoft Purview Insider Risk Management helps you minimize internal risks by detecting, investigating, and acting on risky activities in your organization. For example, data imported by the HR data connector is used as risk indicators to help detect departing user data theft. The healthcare data connector supports risk indicators for patient data misuse, and the third-party insider risk detections connector lets you extend detections to non-Microsoft workloads.

Litigation Hold

Place a Litigation Hold on a user mailbox to retain third-party data. When you create a hold, specify a hold duration (also called a time-based hold) so that deleted and modified third-party data is retained for a specified period and then permanently deleted from the mailbox. Or retain content indefinitely (called an infinite hold) or until the Litigation Hold is removed.

Records management

The Microsoft Purview Records Management solution lets you declare third-party data as a record. Users can manually apply a retention label that marks third-party data in their mailbox as a record. Or you can auto-apply retention labels by identifying sensitive information, keywords, or content types in third-party data.

Retention settings

Apply a retention policy to user mailboxes to retain and then delete third-party data (and other mailbox content) after the retention period expires. Use retention policies to delete third-party data of a certain age or use retention labels to trigger a disposition review when the retention period for third-party data expires.

Data connectors in the US Government cloud

Some data connectors are available in the US Government cloud. The following sections show the specific government environments that support third-party data connectors. For more information about US Government clouds, see Microsoft 365 US Government.

Microsoft data connectors in the US Government cloud

Data connector GCC GCC High DoD
Human resources (HR) Yes Yes Yes

TeleMessage data connectors in the US Government cloud

Data connector GCC GCC High DoD
Android Archiver Yes No No
AT&T SMS/MMS Network Archiver Yes No No
Bell SMS/MMS Network Archiver Yes No No
Enterprise Number Archiver Yes No No
O2 SMS and Voice Network Archiver Yes No No
Rogers Network Archiver Yes No No
Signal Archiver Yes No No
Telegram Archiver Yes No No
TELUS SMS Network Archiver Yes No No
Verizon SMS/MMS Network Archiver Yes No No
WeChat Archiver Yes No No
WhatsApp Archiver Yes No No

17a-4 data connectors in the US Government cloud

Data connector GCC GCC High DoD
BlackBerry DataParser Yes No No
Bloomberg DataParser Yes No No
Cisco Jabber DataParser Yes No No
Cisco Webex DataParser Yes No No
FactSet DataParser Yes No No
Fuze DataParser Yes No No
FX Connect DataParser Yes No No
ICE DataParser Yes No No
InvestEdge DataParser Yes No No
LivePerson Conversational Cloud DataParser Yes No No
Quip DataParser Yes No No
Refinitiv Eikon Messenger DataParser Yes No No
ServiceNow DataParser Yes No No
Skype for Business Server DataParser Yes No No
Slack DataParser Yes No No
SQL DataParser Yes No No
Symphony DataParser Yes No No
Zoom DataParser Yes No No

CellTrust data connectors in the US Government cloud

Data connector GCC GCC High DoD
CellTrust SL2 Yes No No