| Category | Microsoft Docs article | Related commit history on GitHub | Change details |
|---|---|---|---|
| admin | Yammer Device Usage Report Ww | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/admin/activity-reports/yammer-device-usage-report-ww.md | The **Yammer device usage** report can be viewed for trends over the last 7 days |Android phone <br/> |Indicates if the user has used Yammer on an Android phone. <br/>| |iphone <br/> | Indicates if the user has used Yammer on an iPhone. <br/> | |ipad <br/> |Indicates if the user has used Yammer on an iPad. <br/>|-|other <br/> |Indicates if the user has used Yammer on another device, not listed previously. <br/>| -||| +|other <br/> |Indicates if the user has used Yammer on another client, not listed previously. This includes Yammer Embed, SharePoint Web Part, Viva Engage, and select Outlook emails. <br/>| +||| |
| admin | Admin Mobile App | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/admin/admin-overview/admin-mobile-app.md | You must be an administrator in a Microsoft 365 organization to use the admin mo [Google Play Store](https://play.google.com/store/apps/details?id=com.ms.office365admin&referrer=utm_source%3Ddocsaboutadminapp%26utm_campaign%25docsaboutadminapp). +## Watch: Install and use the admin mobile app ++[!VIDEO https://www.microsoft.com/videoplayer/embed/05c1d439-9ec2-415f-9178-250f64dec64c] + ## Frequently asked questions Below are answers to frequently asked questions. |
| admin | Adoption Score | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/admin/adoption/adoption-score.md | We provide metrics, insights, and recommendations in two areas: For each of the mentioned categories, we look at public research to identify some best practices and associated benefits in the form of organizational effectiveness. For example, Forrester research has shown that when people collaborate and share content in the cloud (instead of emailing attachments), they can save up to 100 minutes a week. Furthermore, we quantify the use of these best practices in your organization to help you see where you are on your digital transformation journey. -- **Technology experiences:** Your organization depends on reliable and well-performing technology, as well as the efficient use of Microsoft 365. [Endpoint analytics](https://aka.ms/endpointanalytics) helps you understand how your organization can be impacted by performance and health issues with your hardware and software. Microsoft 365 apps health helps you understand whether the devices in your organization are running Microsoft 365 apps on recommended channels.+- **Technology experiences:** Your organization depends on reliable and well-performing technology, as well as the efficient use of Microsoft 365. [Endpoint analytics](https://aka.ms/endpointanalytics) helps you understand how your organization can be impacted by performance and health issues with your hardware and software. [Network connectivity](../../enterprise/microsoft-365-networking-overview.md) helps you understand Exchange, SharePoint, and Microsoft Teams performance on your network architecture. You can review and update network settings to improve connectivity. Microsoft 365 apps health helps you understand whether the devices in your organization are running Microsoft 365 apps on recommended channels. -## Before you begin +> [!NOTE] +> All insights are calculated using data at the organizational level, not the individual level. ++## How to turn on Adoption Score -See [What is Endpoint Analytics](/mem/analytics/overview) for an overview and prerequisite details. To learn more about Microsoft 365 network connectivity insights, read [the network connectivity overview](../../enterprise/microsoft-365-networking-overview.md). +To enable Adoption Score: -For people experiences data, you need a Microsoft 365 for business or Office 365 for enterprise subscription. For endpoint analytics data for your tenant, you need to add Microsoft Intune to your subscription. Intune helps protect your organization's data by managing devices and apps. Once you have Intune, you can turn on endpoint analytics within the Intune experience. To learn more about Microsoft Intune, see the [Microsoft Intune documentation](/mem/intune/). +1. Login to the Microsoft 365 admin center as a Global Administrator and go to **Reports** > **Adoption Score** +2. Select **Enable Adoption Score**. It can take up to 24 hours for insights to become available. > [!NOTE]-> A license to Workplace Analytics is not required to get the Adoption Score features. +> Only an IT professional with the Global Administrator role can opt-in for Adoption Score. ++Visit [privacy controls for Adoption Score](privacy.md) to understand more about options to configure people experiences for your organization. ++## Adoption Score Prerequisites ++For people experiences data, you need a Microsoft 365 for business or Office 365 for enterprise subscription. For endpoint analytics data for your tenant, you need to add Microsoft Intune to your subscription. Intune helps protect your organization's data by managing devices and apps. Once you have Intune, you can turn on endpoint analytics within the Intune experience. To learn more about Microsoft Intune, see the [Microsoft Intune documentation](/mem/intune/). ++> [!NOTE] +> A license to Viva Insights is not required to get the Adoption Score features. Adoption Score is only available in the Microsoft 365 admin center and can only be accessed by IT professionals who have one of the following roles: Adoption Score is only available in the Microsoft 365 admin center and can only - Global Reader - Reports Reader - Usage Summary Reports Reader--> [!NOTE] -> Only an IT professional with the Global Administrator role can sign up or opt in a tenant for Adoption Score. +- User Experience Success Manager The role-based access control model for Adoption Score helps organizations further digital transformation efforts with Microsoft 365 by providing the flexibility to assign roles to IT professionals within an organization. You can access the experience from Microsoft 365 Admin home under **Reports** > Your Adoption Score is based on the combined scores of your people and technology experiences categories. Each category is weighted equally, with a total of 100 points. The highest possible Adoption Score is 800. -### Score categories +### Score categories - Communication (100 points) - Meetings (100 points) |
| admin | Meetings New | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/admin/adoption/meetings-new.md | ++ + Title: "Microsoft Adoption Score - Meetings (New)" +f1.keywords: NOCSH +++++audience: Admin +++ms.localizationpriority: medium ++- M365-subscription-management +- scotvorg +- highpri ++search.appverid: MET150 +description: "Details of new Meetings insights score - people experiences Adoption Score." +++# Meetings insights score ΓÇô People experiences (New) ++Adoption Score provides insights into your organization's digital transformation journey through its use of Microsoft 365 and the technology experiences that support it. Your organization's score reflects people and technology experience measurements and can be compared to benchmarks from organizations similar to yours. The meetings category is part of the people experiences measures. To learn more, check out the [Adoption Score overview](adoption-score.md) and read [Microsoft's Privacy Statement](https://privacy.microsoft.com/privacystatement). ++## Prerequisites ++To get started with Meetings insights, people in your organization need to be licensed for: ++- Microsoft Teams ++For more information, seeΓÇ»[assign licenses to users](../manage/assign-licenses-to-users.md). ++After people have been active in Teams at least once in the last 28 days, you will start to see the insights. ++## Why your organization's meetings score matters ++Meetings, where people explore ideas, plan, solve problems, and make decisions, are a fundamental pillar for organizational productivity. Research indicates that when people use online meeting tools effectively, they tend to save up to 104 minutes per week. ++## How we calculate the meetings score ++Microsoft Teams integrates with Outlook calendar and provides a host of capabilities to make your meetings more engaging and effective. We provide an overall score for Meetings and then sub scores for each of the best practices in the Set up, Meet up and Follow up sections. ++## Overall score ++The overall meeting score is calculated by averaging out the scores across the three phases i.e., Set up, Meet up and Follow up. We take into account the number of attendees and the duration of the meeting when tallying the final averaged scores. ++For each meeting: ++1. We compute the three sub-scores (Pre, During, Post), by averaging the features, for each meeting. For example, Set Up: 30, Meet up: 40, Follow up: 20 +1. We then compute the average of the three sub-scores for the meeting. From the above example, 30+40+20/3 = 30 +1. We compute the weight of each meeting based on the meeting duration and meeting size. The longer or bigger a meeting, the more impact it has in the final score. +1. We then perform a weighted sum average on scores from all meetings of the tenant based on meeting weights to compute the final meeting score for the tenant. +++1. **Header**: Shows the score, out of 100, based on the average of Set Up, Meet Up and Follow Up phases for online meetings on Microsoft Teams held in the past 28 days. +1. **Body**: Provides more information on how using online meeting tools effectively can make meetings more effective. +1. **Visualization (current state)**: In this horizontal bar chart, the blue (colored) portion represents the score (out of 100) shown in the header. ++## Trend visualization of the score ++The following chart shows the trend-line of score over the selected period. Each data point on the line chart is an aggregate of activity for the last 28 days. +++## What makes up my score? ++We provide you with supporting data on each of the Set Up, Meet up and Follow Up phases. The score for each insight is calculated out of 100. ++## Set up ++This represents the phase that involves scheduling and sharing the details of the meeting and participants joining the meeting. +++- **Communication shared ahead of time**: This represents the score for Microsoft Teams meetings that had a Teams conversation meeting chat started before conducting the meeting. For this to be tracked, a user must go to the meeting chat with the participants and send a message to the participants, before the scheduled meeting time. +- **Scheduled with at least 24 hours notice**: This represents the score for Microsoft Teams meetings that were scheduled at least 24 hours earlier than their start time. +- **Invitation accepted at a high rate (>50%)**: This represents the score for Microsoft Teams meetings that had more than 50% of invited participants accept the meeting invite. +- **Joined within 5 minutes of start time (>50%)**: This represents the score for Microsoft Teams meetings that had more than 50% of invited participants join the meeting within 5 minutes of the start time. ++## Meet up ++This represents the phase of when attendees are in the meeting. +++- **Used at least one interactive feature**: This represents the score for Microsoft Teams meetings that had attendees use at least one interactive feature. These interactive features include raising hand, sending a meeting chat message, or sending a reaction in the meeting. The score is calculated out of 100. +- **Participated with audio or chat at a high rate (>33%)**: This represents the score for Microsoft Teams meetings that had more than 33% of the participants either speak in a meeting, send a meeting chat, or both. The score is calculated out of 100. +- **Shared visual content**: This represents the score for Microsoft Teams meetings that had attendees share any visual content in the meeting by either turning on their video, sharing screen, or both. The score is calculated out of 100. ++## Follow up +++- **Created recording**: This represents the score for Microsoft Teams meetings that had the meeting recorded. The score is calculated out of 100. +- **Sent out post-meeting communication**: This represents the score for Microsoft Teams meetings that had attendee(s) share any chat messages on the meeting chat thread after the conclusion of that meeting. The score is calculated out of 100. ++## How can I impact my score? ++This section helps understand two insights for the organization: ++1. **Most significant growth**: This section depicts the part of the score that had the highest growth in the past 28 days. +1. **Biggest area for improvement**: This section depicts the part of the score that has the biggest room to improve and impact the org's Adoption Score in the future. ++## Dig deeper into meetings ++This section consists of three sub-sections: ++1. **Additional insights**: Here we provide additional insights which help organizations identify trends and user behaviors across meetings. +1. **Interesting findings**: Here we provide some interesting facts about meetings being conducted in the organization. +1. **Microsoft Research**: Here we reference Microsoft blogs and public research which provide recommended practices and their impacts to have effective meetings. ++> [!NOTE] +> The 'Dig deeper into meetings' section does not contribute to the overall score of the Meetings Page in Adoption Score People Experiences, however some insights in this section may expand on a primary insight used to calculate a score. ++## Related content ++[Microsoft 365 apps health ΓÇô Technology experiences](apps-health.md) (article)\ +[Communication ΓÇô People experiences](communication.md) (article)\ +[Content collaboration ΓÇô People experiences](content-collaboration.md) (article)\ +[Mobility ΓÇô People experiences](mobility.md) (article)\ +[Privacy controls for Adoption Score](privacy.md) (article)\ +[Teamwork ΓÇô People experiences](teamwork.md) (article) |
| admin | Privacy | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/admin/adoption/privacy.md | Your privacy is important to Microsoft. To learn how we protect your privacy, se Within the people experiences area, metrics are available at the organizational level only. This area looks at how people use Microsoft 365 by looking at the categories of content collaboration, mobility, meetings, teamwork, and communication. We enable you with several levels of controls to help you meet your internal privacy policy needs. The controls give you: -- Flexible admin roles to control who can see the information in Adoption Score.-- The capability to opt out of the people experiences area.+- Flexible admin roles to control who can see the information in Adoption Score +- The capability to remove users and groups from people experience calculations +- The capability to opt out of the people experiences area ## Flexible admin roles to control who can see the information in Adoption Score To view the entire Adoption Score, you need be one of the following admin roles: - Global Reader - Reports Reader - Usage Summary Reports Reader+- User Experience Success Manager -Assign the Reports Reader or the Usage Summary Reports Reader role to anyone who's responsible for change management and adoption, but not necessarily an IT administrator. This role gives them access to the complete Adoption Score experience in the Microsoft 365 admin Center. +Global admin can assign the Reports Reader role, Usage Summary Reports Reader role, or User Experience Success Manager role to anyone who's responsible for change management and adoption, but not necessarily an IT administrator. ++Users with the Reports Reader role can view usage reporting data and the reports dashboard in Microsoft 365 admin center and the adoption context pack in Power BI. Users with Usage Summary Reports Reader role can see only tenant level aggregates and group level aggregates in Microsoft 365 Usage Analytics and Adoption Score. The User Experience Success Manager role includes the permissions of the Usage Summary Reports Reader role, and can get access to more Adoption-related information such as Message Center, Product Feedback, and Service Health. See [Azure AD built-in roles](/azure/active-directory/roles/permissions-reference) to learn more about different roles. ++## Capability to choose specific users or certain groups ++You can choose the users and groups whose data will be used to determine your org's people experiences insights. Omitting some groups will affect the insights calculations. You have to be a Global admin to opt your organization out of the people experiences reports. It can take up to 24 hours for change to apply. ++To omit certain groups: ++1. In the admin center, go to **Settings** > **Org Settings** > **Adoption Score**. +2. Select **Exclude specific users via group**. +3. Choose one or multiple Admin Center AAD groups to omit. +4. Select **Save changes**. + ## Capability to opt out of people experiences -You can also opt out of the people experiences area of Adoption Score. If you opt out, no one from your organization will be able to view these metrics, and your organization will be removed from any calculations that involve communication, meetings, teamwork, content collaboration, and mobility. You have to be a Global admin to opt your organization out of the people experiences reports. +You can also opt out of the people experiences area of Adoption Score. If you opt out, no one from your organization will be able to view these metrics, and your organization will be removed from any calculations that involve communication, meetings, teamwork, content collaboration, and mobility. You have to be a Global admin to opt your organization out of the people experiences reports. It can take up to 24 hours for change to apply. You can revert your change before the end of the day in UTC time to keep historical data. To opt out: 1. In the admin center, go to **Settings** > **Org Settings** > **Adoption Score**.-2. Select **No users (people experience insights wonΓÇÖt be calculated)**. +2. Select **Don't calculate for any users**. 3. On the **Do you want to remove data from people experiences?** confirmation screen, select **Remove Data**. 4. Select **Save**. |
| admin | Capabilities | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/admin/basic-mobility-security/capabilities.md | The following option can block users from accessing their Microsoft 365 email if ||||| |Block video conferences on device<sup>1</sup>|Yes|No|No| |Block access to application store<sup>1</sup>|Yes|No|Yes|-|Require password when accessing application store|No|Yes|Yes| +|Require password when accessing application store|Yes|No|No| <sup>1</sup>To function, these settings require supervised iOS devices. |
| admin | Create Device Security Policies | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/admin/basic-mobility-security/create-device-security-policies.md | When you apply a policy to user devices, the impact on each device varies somewh |**Security Policy**|**Android**|**Samsung KNOX**|**iOS**|**Notes**| |:--|:--|:--|:--|:--| |Require encrypted backup|No|Yes|Yes|iOS encrypted backup required.|-|Block cloud backup|Yes|Yes|Yes|Block Google backup on Android (grayed out), cloud backup on iOS.| -|Block document synchronization|No|No|Yes|iOS: Block documents in the cloud.| +|Block cloud backup|Yes|Yes|Yes|Block Google backup on Android (grayed out), cloud backup on supervised iOS.| +|Block document synchronization|No|No|Yes|iOS: Block documents in the cloud on supervised iOS devices.| |Block photo synchronization |No|No|Yes|iOS (native): Block Photo Stream.| |Block screen capture |No|Yes|Yes|Blocked when attempted.|-|Block video conference |No|No|Yes|FaceTime blocked on iOS, not on Skype or others.| +|Block video conference |No|No|Yes|FaceTime blocked on supervised iOS devices, not on Skype or others.| |Block sending diagnostic data |No|Yes|Yes|Block sending Google crash report on Android.|-|Block access to app store |No|Yes|Yes|App store icon missing on Android home page, disabled on Windows, missing on iOS.| +|Block access to app store |No|Yes|Yes|App store icon missing on Android home page, disabled on Windows, and supervised iOS devices.| |Require password for app store |No|No|Yes|iOS: Password required for iTunes purchases.| |Block connection to removable storage |No|Yes|N/A|Android: SD card is grayed out in settings, Windows notifies user, apps installed aren't available| |Block Bluetooth connection |See notes|See notes|Yes|We can't disable BlueTooth as a setting on Android. Instead, we disable all of the transactions that require BlueTooth: Advanced Audio Distribution, Audio/Video Remote Control, hands-free devices, headset, Phone Book Access, and Serial Port. A small toast message appears at the bottom of the page when any of these are used.| |
| admin | Release Options In Office 365 | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/admin/manage/release-options-in-office-365.md | description: "Learn how to set up the release option for new product and feature # Set up the Standard or Targeted release options > [!IMPORTANT]-> The Microsoft 365 updates described in this article apply to Microsoft 365, SharePoint Online, and Exchange Online. These release options are targeted, best effort ways to release changes to Microsoft 365 but cannot be guaranteed at all times or for all updates. They do not apply to Microsoft 365 Apps, Skype for Business, Microsoft Teams, and related services. For information about release options for Microsoft 365 Apps, see [Overview of update channels for Microsoft 365 Apps](/deployoffice/overview-update-channels). +> The Microsoft 365 updates described in this article apply to OneDrive for Business, SharePoint Online, Office for the web, Microsoft 365 admin center and some components of Exchange Online. These release options are targeted, best effort ways to release changes to Microsoft 365 but cannot be guaranteed at all times or for all updates. They do not currently apply to services other than those listed previously. For information about release options for Microsoft 365 Apps, see [Overview of update channels for Microsoft 365 Apps](/deployoffice/overview-update-channels). With Microsoft 365, you receive new product updates and features as they become available instead of doing costly updates every few years. You can manage how your organization receives these updates. For example, you can sign up for an early release so that your organization receives updates first. You can designate that only certain individuals receive the updates. Or, you can remain on the default release schedule and receive the updates later. This article explains the different release options and how you can use them for your organization. ## How it works - release validation -Any new release is first tested and validated by the feature team, then by the entire Microsoft 365 feature team, followed by all of Microsoft. After internal testing and validation, the next step is a **Targeted release** (formerly known as First release) to customers who opt in. At each release ring, Microsoft collects feedback and further validates quality by monitoring key usage metrics. This series of progressive validation is in place to make sure the worldwide-release is as robust as possible. The releases are pictured in the following figure. +Any new release is first tested and validated by the feature team, then by the entire Microsoft 365 feature team, followed by all of Microsoft. After internal testing and validation, the next step is a **Targeted release** (formerly known as First release) to customers who opt in. At each release ring, Microsoft collects feedback and further validates quality by monitoring key usage metrics. This series of progressive validation is in place to make sure the worldwide-release is as robust as possible. The releases are pictured in the following figure.  For significant updates, customers are initially notified by the [Microsoft 365 This is the default option where you and your users receive the latest updates when they're released broadly to all customers. -A good practice is to leave the majority of users in **Standard release** and IT Pros and power users in **Targeted release** to evaluate new features and prepare teams to support business users and executives. +A good practice is to leave the majority of users in **Standard release** and IT Pros and power users in **Targeted release** to evaluate new features and prepare teams to support business users and executives. > [!NOTE]-> If you switch from targeted release back to standard release track, your users may lose access to features that haven't reached standard release yet. +> If you switch from targeted release back to standard release track, your users may lose access to features that haven't reached standard release yet. ## Targeted release With this option, you and your users can be the first to see the latest updates and help shape the product by providing early feedback. You can choose to have individuals or the entire organization receive updates early. > [!IMPORTANT]-> - Large or complex updates may take longer than others so that no users are adversely affected. There is no guarantee on the exact timeline of a release. -> - Targeted release is not currently available for customers with either the Office 365 GCC plan or the Office 365 GCC High and DoD plan. +> Large or complex updates may take longer than others so that no users are adversely affected. There is no guarantee on the exact timeline of a release. Targeted release is not currently available for customers with either the Office 365 GCC plan or the Office 365 GCC High and DoD plan. ### Targeted release for entire organization -If you [Set up the release option in the admin center](#set-up-the-release-option-in-the-admin-center) for this option, all your users will get the Targeted release experience. For organizations with more than 300 users, we recommend using a test subscription for this option. For test subscription information, please reach out to your Microsoft contact. +If you [Set up the release option in the admin center](#set-up-the-release-option-in-the-admin-center) for this option, all your users will get the Targeted release experience. For organizations with more than 300 users, we recommend using a test subscription for this option. For test subscription information, please reach out to your Microsoft contact. ### Targeted release for selected users If you [Set up the release option in the admin center](#set-up-the-release-optio Targeted release allows admins, change managers, or anyone else responsible for Microsoft 365 updates to prepare for the upcoming changes by letting them: - Test and validate new updates before they are released to all the users in the organization.- + - Prepare user notification and documentation before updates are released worldwide.- + - Prepare internal help-desk for upcoming changes.- + - Go through compliance and security reviews.- + - Use feature controls, where applicable, to control the release of updates to end users.- + ## Set up the release option in the admin center You can change how your organization receives Microsoft 365 updates by following these steps. You have to be a global admin in Microsoft 365 to opt in. > [!IMPORTANT]-> It can take up to 24 hours for the below changes to take effect in Microsoft 365. If you opt out of targeted release after enabling it, your users may lose access to features that haven't reached the scheduled release yet. +> It can take up to 24 hours for the below changes to take effect in Microsoft 365. If you opt out of targeted release after enabling it, your users may lose access to features that haven't reached the scheduled release yet. 1. In the admin center, go to the **Settings** > **Org Setting**, and under the <a href="https://go.microsoft.com/fwlink/p/?linkid=2067339" target="_blank">**Organization profile** tab</a>, choose **Release preferences**. -5. To disable targeted release, select **Standard release**, then select **Save changes**. - -6. To enable targeted release for all users in your organization, select **Targeted release for everyone**, then select **Save changes**. +5. To disable targeted release, select **Standard release**, then select **Save changes**. -7. To enable targeted release for some people in your organization, select **Targeted release for selected users**, then select **Save changes**. +6. To enable targeted release for all users in your organization, select **Targeted release for everyone**, then select **Save changes**. +7. To enable targeted release for some people in your organization, select **Targeted release for selected users**, then select **Save changes**. + 8. Choose **Select users** to add users one at a time, or **Upload users** to add them in bulk.- + 9. When you're done adding users, select **Save changes**. ## Next steps |
| admin | Set Password Expiration Policy | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/admin/manage/set-password-expiration-policy.md | Follow the steps below if you want to set user passwords to expire after a speci 1. Type how often passwords should expire. Choose a number of days from 14 to 730. > [!IMPORTANT]-> Password expiration notifications are no longer supported in Office web apps or the [admin center](https://portal.office.com). +> Password expiration notifications are no longer supported in the Microsoft 365 admin center and the Office apps or Office web apps. ## Important things you need to know about the password expiration feature |
| admin | Message Center Conformance | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/admin/misc/message-center-conformance.md | + + Title: "Conformance metadata for Message Center posts" +f1.keywords: +- CSH ++++audience: Admin +++ms.localizationpriority: medium +++description: "Get an overview of conformance metadata for Message center posts" +++# Conformance metadata for Message Center posts ++> [!IMPORTANT] +> This private document is only for Change Management: Conformance metadata users. Don't share this document beyond those who are directly involved in the pilot. ++When planning for new features or service deployments, you would like to understand and assess the changes for conformance to your industry, region and country. We've heard your feedback when there's insufficient conformance information about a new or changing feature, you have to conduct your own research about the feature or reach out to the Compliance Program with questions. ++In this pilot program, we want to proactively provide metadata for new and updated Microsoft 365 features and services. Our goal is to help you efficiently assess your compliance requirements and help you with adoption and change management decisions. ++For example, if for a feature the metadata has the following values, feature adoption decision should be quick. ++- Customer data is stored? **No** ++- Change to customer data storage? **No** ++- Changes to existing data flow? **No** ++- Feature integrates with third party services? **No** ++> [!NOTE] +> The above list is slightly different from what you previously saw in the pilot conformance posts. We've updated the list based on feedback we've received from pilot customers. ++For features where the metadata is different from the list above, the Message center post may provide you with documentation. ++## Understanding conformance metadata ++|**Metadata name**|**Values**|**Definition and questions asked**|**Example: Yes**|**Example: No**| +||||| +|**Customer data is stored**|Yes/No|Does this change store or process any net new data (classified as customer or personal data) which wasn't previously stored or processed by the service/previous version of this feature?|Teams Meetings recordings capturing and collecting customer data and is now stored in.|Message Center Service monthly active users (MAU) feature shows the aggregated service monthly active users for a tenant ID which isn't classified as customer or personal data.| +|**Change to customer data storage**|Yes/No|Does this change use a new or different service to store data|Teams Meetings Recordings capturing/collecting customer data/content and is now stored in.|Expanded reactions in Teams. Expanding message reactions in Teams to a larger set. The newer reactions being stored are customer data, however, there's no change in how data is stored or processed.| +|**Changes to existing data flow**|Yes/No|Does this feature process data via a new or different processing pipeline? <br> Or <br> Is the feature just extending an existing processing pipeline to newer data or exposing data already exposed on one surface to another surface? (**Answer = No**).|When Bing for Business started using text from Word to send to Bing then bring data back to Word, the flow of data changed.|Productivity score being used on the Experience Insights page in admin center, the data is shown on a new surface, but storage and processing is the same. <br> Suggested Reply in Group Chats on Teams Desktop (an extension of 1:1 chats) doesn't have any net new data. It's an extension of the pipeline already set up for Suggested Reply in 1:1 chats.| +|**Feature integrates with third party services**|Yes/No|Does this feature utilize a net new service or app (first party or third party) that customer data could potentially be stored or processed outside of Microsoft 365?|Bing for Business may receive customer content in the form of "search" data to present a user with potentially relevant information/content.|Message Center Service monthly active users (MAU) feature shows the service monthly active users using Usage Report Graph API which is within Microsoft 365 boundary.| +| ++## Join the pilot program ++You can join by completing this [questionnaire](https://go.microsoft.com/fwlink/p/?linkid=2211581). ++When a Message center post is delivered, you'll receive an additional Message Center post that says: **Additional Conformance Information for MC######**. This post contains more conformance metadata. You can provide feedback directly on the extra post or you can email: MCSHDPMS@Microsoft.com. You can also send feedback on the [Teams channel](https://go.microsoft.com/fwlink/p/?linkid=2211676). ++> [!NOTE] +> WeΓÇÖll start with features from Microsoft Teams, OneDrive for Business and SharePoint Online. |
| admin | Password Policy Recommendations | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/admin/misc/password-policy-recommendations.md | Good password practices fall into a few broad categories: The primary goal of a more secure password system is password diversity. You want your password policy to contain lots of different and hard to guess passwords. Here are a few recommendations for keeping your organization as secure as possible. -- Maintain a fourteen-character minimum length requirement+- Maintain a 14-character minimum length requirement - Don't require character composition requirements. For example, \*&(^%$ |
| business | Mam And Mdm | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/business/ui/mam-and-mdm.md | description: "Learn the differences between mobile device management and mobile # Difference between MDM and MAM -Microsoft 365 Business Premium offers a number of ways for you to protect your business data. See [Overview of Microsoft 365 Business Premium](../../admin/admin-overview/what-is-microsoft-365.md) for more about the various protections that are automatically set up, and what you can set up yourself to further protect your business. You can also set up policies that protect your Windows 10 devices and the data in your mobile devices. -[Set application protection settings for Windows 10 devices](../../business-premium/m365bp-protection-settings-for-windows-10-devices.md). +Microsoft 365 Business Premium offers a number of ways for you to protect your business data. See [Overview of Microsoft 365 Business Premium](../../admin/admin-overview/what-is-microsoft-365.md) for more about the various protections that are automatically set up, and what you can set up yourself to further protect your business. You can also onboard devices to Microsoft Defender for Business to protect your Windows devices and the data in your mobile devices. For more information, see [Onboard enrolled devices to Microsoft Defender for Business](/microsoft-365/business-premium/m365bp-onboard-devices-mdb). ## Mobile device management or MDM -Microsoft 365 Business Premium lets you set up policies that protect data on your Windows 10 devices. When a device is under mobile device management, you control the entire device, and can wipe data from it, and also reset it to factory settings. For more information, see [Set device protection settings for Windows 10 PCs](../../business-premium/m365bp-protection-settings-for-windows-10-devices.md). +Microsoft 365 Business Premium lets you set up policies that protect data on your Windows 10 and 11 devices. When a device is under mobile device management, you control the entire device, and can wipe data from it, and also reset it to factory settings. For more information, see [Choose the device management solution that's right for you](/mem/intune/fundamentals/what-is-device-management#choose-the-device-management-solution-thats-right-for-you) and [Set up and secure managed devices](/microsoft-365/business-premium/m365bp-protect-devices). ## Mobile application management or MAM -Mobile application management lets you control your business data in your users' personal devices, such as iPhones and Androids, and their personal Win 10 computers. You can use application management policies to prevent your users from copying business data from Office apps to their personal apps. You can also remove all data from the Office apps on their personal devices. For more information, see [Set app protection settings for Android or iOS devices](../../business-premium/m365bp-app-protection-settings-for-android-and-ios.md) and [Set application protection settings for Windows 10 devices](../../business-premium/m365bp-app-protection-settings-for-android-and-ios.md). +Mobile application management lets you control your business data in your users' personal devices, such as iPhones and Androids, and their personal Windows computers. You can use application management policies to prevent your users from copying business data from Office apps to their personal apps. You can also remove all data from the Office apps on their personal devices. For more information, see [Choose the device management solution that's right for you](/mem/intune/fundamentals/what-is-device-management#choose-the-device-management-solution-thats-right-for-you) and [Set up and secure managed devices](/microsoft-365/business-premium/m365bp-protect-devices). |
| commerce | View Your Bill Or Invoice | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/commerce/billing-and-payments/view-your-bill-or-invoice.md | Check out this video and others on our [YouTube channel](https://go.microsoft.co ::: moniker-end -2. On the **Invoices** tab, select a date range from the drop-down list, and then choose the order that you want to view. -3. On the summary page, you can see the items, quantity, price, discount, and total for all items in the invoice. +2. On the **Invoices** tab, choose the invoice that you want to view. If you don't see an invoice, use the date filter and select **Past 3 months**, **Past 6 months**, or **Specify date range**. +3. On the **Invoice summary** page, you see invoice details including the list of items, the price for each item, and the total cost for all items in the invoice. 4. To print or save a PDF copy of the invoice, select **Download PDF**. If you want to receive a copy of your billing statement in email, see [Manage billing notifications and invoice attachments](manage-billing-notifications.md). |
| commerce | Allowselfservicepurchase Powershell | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/commerce/subscriptions/allowselfservicepurchase-powershell.md | search.appverid: - MET150 description: "Learn how to use the AllowSelfServicePurchase PowerShell cmdlet to turn self-service purchase on or off." Previously updated : 4/7/2022 Last updated : 10/10/2022 # Use AllowSelfServicePurchase for the MSCommerce PowerShell module The **MSCommerce** PowerShell module is now available on [PowerShell Gallery](ht You can use the **MSCommerce** PowerShell module to: -- View the default state of the **AllowSelfServicePurchase** parameter value ΓÇö whether it's enabled or disabled-- View a list of applicable products and whether self-service purchase is enabled or disabled+- View the default state of the **AllowSelfServicePurchase** parameter valueΓÇöwhether it's enabled, disabled, or allows trials without a payment method +- View a list of applicable products and whether self-service purchase is enabled, disabled, or allows trials without a payment method - View or modify the current setting for a specific product to either enable or disable it+- View or modify the setting for trials without payment methods ## Requirements To connect to the PowerShell module with your credentials, run the following com Connect-MSCommerce ``` -This command connects the current PowerShell session to an Azure Active Directory tenant. The command prompts you for a username and password for the tenant you want to connect to. If multi-factor authentication is enabled for your credentials, you use the interactive option to log in. +This command connects the current PowerShell session to an Azure Active Directory tenant. The command prompts you for a username and password for the tenant you want to connect to. If multi-factor authentication is enabled for your credentials, you use the interactive option to sign in. ## View details for AllowSelfServicePurchase To view a list of all available self-service purchase products and the status of Get-MSCommerceProductPolicies -PolicyId AllowSelfServicePurchase ``` -The following table lists the available products and their **ProductId**. --| Product | ProductId | -|--|--| -| Power Apps per user* | CFQ7TTC0LH2H | -| Power Automate per user | CFQ7TTC0KP0N | -| Power Automate RPA | CFQ7TTC0KXG6 | -| Power BI Premium (standalone) | CFQ7TTC0KXG7 | -| Power BI Pro | CFQ7TTC0L3PB | -| Project Plan 1* | CFQ7TTC0HDB1 | -| Project Plan 3* | CFQ7TTC0HDB0 | -| Visio Plan 1* | CFQ7TTC0HD33 | -| Visio Plan 2* | CFQ7TTC0HD32 | -| Windows 365 Enterprise | CFQ7TTC0HHS9 | -| Windows 365 Business | CFQ7TTC0J203 | -| Windows 365 Business with Windows Hybrid Benefit | CFQ7TTC0HX99 | -| Microsoft 365 F3 | CFQ7TTC0LH05 | -| Dynamics 365 Marketing | CFQ7TTC0LH3N | -| Dynamics 365 Marketing Attach | CFQ7TTC0LHWP | -| Dynamics 365 Marketing Additional Application | CFQ7TTC0LHVK | -| Dynamics 365 Marketing Additional Non-Prod Application | CFQ7TTC0LHWM | --*These IDs have changed. If you previously blocked products using the old IDs, they are automatically blocked using the new IDs. No additional work is required. +The following table lists the available products and their **ProductId**. It also indicates which products have a trial available and don't require a payment method. If applicable, all other trials require a payment method. For the products that have trial without payment method enabled, you can enable the trial, while keeping the ability to purchase the product disabled. For sample commands, see View or set the status for **AllowSelfServicePurchase**. ++| Product | ProductId | Is trial without payment method enabled? | +|--|--|--| +| Power Apps per user* | CFQ7TTC0LH2H | No | +| Power Automate per user | CFQ7TTC0KP0N | No | +| Power Automate RPA | CFQ7TTC0KXG6 | No | +| Power BI Premium (standalone) | CFQ7TTC0KXG7 | No | +| Power BI Pro | CFQ7TTC0L3PB | No | +| Project Plan 1* | CFQ7TTC0HDB1 | Yes | +| Project Plan 3* | CFQ7TTC0HDB0 | No | +| Visio Plan 1* | CFQ7TTC0HD33 | No | +| Visio Plan 2* | CFQ7TTC0HD32 | No | +| Windows 365 Enterprise | CFQ7TTC0HHS9 | No | +| Windows 365 Business | CFQ7TTC0J203 | No | +| Windows 365 Business with Windows Hybrid Benefit | CFQ7TTC0HX99 | No | +| Microsoft 365 F3 | CFQ7TTC0LH05 | No | +| Dynamics 365 Marketing | CFQ7TTC0LH3N | No | +| Dynamics 365 Marketing Attach | CFQ7TTC0LHWP | No | +| Dynamics 365 Marketing Additional Application | CFQ7TTC0LHVK | No | +| Dynamics 365 Marketing Additional Non-Prod Application | CFQ7TTC0LHWM | No | ++*These IDs have changed. If you previously blocked products using the old IDs, they're automatically blocked using the new IDs. No other work is required. ## View or set the status for AllowSelfServicePurchase -After you view the list of products available for self-service purchase, you can view or modify the setting for a specific product. +You can set the **Value** parameter for **AllowSelfServicePurchase** to allow or prevent users from making a self-service purchase. You can also use the **OnlyTrialsWithoutPaymentMethod** value to allow users to try products that have no payment required trials. Refer to the product list above to see which products have these trials enabled. Users can only buy the product after the trial is over if **AllowSelfServicePurchase** is enabled. ++> [!NOTE] +> Changing the value for **AllowSelfServicePurchase** or **OnlyTrialsWithoutPaymentMethod** only impacts trials or purchases made for the specified product from that point forward. Existing trials or purchases for the specified product aren't affected. ++The following table describes the settings for the **Value** parameter. ++| **Setting** | **Impact** | +||| +| Enabled | Users can make self-service purchases and acquire trials for the product. | +| OnlyTrialsWithoutPaymentMethod | Users can't make self-service purchases but can acquire free trials for products that don't require them to add a payment method. After the trial expires, a user can't buy the paid version of the product. | +| Disabled | Users can't make self-service purchases or acquire trials for the product. | To get the policy setting for a specific product, run the following command: Get-MSCommerceProductPolicy -PolicyId AllowSelfServicePurchase -ProductId CFQ7TT To enable the policy setting for a specific product, run the following command: ```powershell-Update-MSCommerceProductPolicy -PolicyId AllowSelfServicePurchase -ProductId CFQ7TTC0KP0N -Enabled $True +Update-MSCommerceProductPolicy -PolicyId AllowSelfServicePurchase -ProductId CFQ7TTC0KP0N -Value "Enabled" ``` To disable the policy setting for a specific product, run the following command: ```powershell-Update-MSCommerceProductPolicy -PolicyId AllowSelfServicePurchase -ProductId CFQ7TTC0KP0N -Enabled $False +Update-MSCommerceProductPolicy -PolicyId AllowSelfServicePurchase -ProductId CFQ7TTC0KP0N -Value "Disabled" +``` ++To allow users to try a specific product without a payment method, run the following command: ++```powershell +Update-MSCommerceProductPolicy -PolicyId AllowSelfServicePurchase -ProductId CFQ7TTC0KP0N -Value "OnlyTrialsWithoutPaymentMethod" ``` ## Example script to disable AllowSelfServicePurchase The following example walks you through how to import the **MSCommerce** module, Import-Module -Name MSCommerce Connect-MSCommerce #sign-in with your global or billing administrator account when prompted $product = Get-MSCommerceProductPolicies -PolicyId AllowSelfServicePurchase | where {$_.ProductName -match 'Power Automate per user'}-Update-MSCommerceProductPolicy -PolicyId AllowSelfServicePurchase -ProductId $product.ProductID -Enabled $false +Update-MSCommerceProductPolicy -PolicyId AllowSelfServicePurchase -ProductId $product.ProductID -Value "Disabled" ``` If there are multiple values for the product, you can run the command individually for each value as shown in the following example: ```powershell-Update-MSCommerceProductPolicy -PolicyId AllowSelfServicePurchase -ProductId $product[0].ProductID -Enabled $false -Update-MSCommerceProductPolicy -PolicyId AllowSelfServicePurchase -ProductId $product[1].ProductID -Enabled $false +Update-MSCommerceProductPolicy -PolicyId AllowSelfServicePurchase -ProductId $product[0].ProductID -Value "Disabled" +Update-MSCommerceProductPolicy -PolicyId AllowSelfServicePurchase -ProductId $product[1].ProductID -Value "Disabled" ``` ## Troubleshooting You see the following error message: > HandleError : Failed to retrieve policy with PolicyId 'AllowSelfServicePurchase', ErrorMessage - The underlying connection was closed: An unexpected error occurred on a send. -This may be due to an older version of Transport Layer Security (TLS). To connect this service you need to use TLS 1.2 or greater +This may be due to an older version of Transport Layer Security (TLS). When you connect to this service, you must use TLS 1.2 or greater ### Solution Upgrade to TLS 1.2. The following syntax updates the ServicePointManager Security Protocol to allow TLS1.2: ```powershell- [Net.ServicePointManager]::SecurityProtocol = [Net.ServicePointManager]::SecurityProtocol -bor [Net.SecurityProtocolType]::Tls12 +[Net.ServicePointManager]::SecurityProtocol = [Net.ServicePointManager]::SecurityProtocol -bor [Net.SecurityProtocolType]::Tls12 ``` To learn more, see [How to enable TLS 1.2](/mem/configmgr/core/plan-design/security/enable-tls-1-2). Uninstall-Module -Name MSCommerce ## Related content -[Manage self-service purchases (Admin)](manage-self-service-purchases-admins.md) (article) -+[Manage self-service purchases (Admin)](manage-self-service-purchases-admins.md) (article)\ [Self-service purchase FAQ](self-service-purchase-faq.yml) (article) |
| compliance | Apply Retention Labels Automatically | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/apply-retention-labels-automatically.md | Title: "Automatically apply a retention label" + Title: "Automatically apply a retention label to Microsoft 365 items" f1.keywords: - NOCSH To consider when auto-applying retention labels to cloud attachments: - The following items aren't supported as cloud attachments that can be retained: - SharePoint sites, pages, lists, forms, folders, document sets, and OneNote pages.- - Files shared by users who don't have access to those files. + - Files shared by users who don't have access to those files at the time of sharing. - Files that are deleted or moved before the cloud attachment is sent. For example, a user copies and pastes a previously shared attachment from another message, without first confirming that the file is still available. Or, somebody forwards an old message when the file is now deleted. - Files that are shared by guests or users outside your organization. - Files in draft emails and messages that aren't sent. |
| compliance | Archive 17A 4 Blackberry Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-17a-4-blackberry-data.md | The following overview explains the process of using a data connector to archive 1. Your organization works with 17a-4 to set up and configure the BlackBerry DataParser. -2. On a regular basis, BlackBerry items are collected by the DataParser. The DataParser also converts the content of a message to an email message format. +2. Regularly, BlackBerry items are collected by the DataParser. The DataParser also converts the content of a message to an email message format. 3. The BlackBerry 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. The following overview explains the process of using a data connector to archive - The user who creates the BlackBerry 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 security and compliance centers" section in [Permissions in the Security & Compliance Center](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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 compliance portal](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- 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 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.+- 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 BlackBerry DataParser connector The first step is to access to the Data connectors page in the compliance portal and create a 17a-4 connector for BlackBerry data. -1. Go to <https://compliance.microsoft.com> and then click **Data connectors** > **BlackBerry DataParser**. +1. Go to <https://compliance.microsoft.com> and then select **Data connectors** > **BlackBerry DataParser**. -2. On the **BlackBerry DataParser** product description page, click **Add connector**. +2. On the **BlackBerry DataParser** product description page, select **Add connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. Enter a unique name that identifies the connector and then click **Next**. +4. Enter a unique name that identifies the connector and then select **Next**. 5. Sign in to your 17a-4 account and complete the steps in the BlackBerry DataParser connection wizard. The BlackBerry DataParser connector will automatically map users to their Micros After you create a BlackBerry DataParser 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. +1. Go to <https://compliance.microsoft.com> and select **Data connectors** in the left nav. -2. Click the **Connectors** tab and then select the BlackBerry DataParser connector that you created to display the flyout page, which contains the properties and information about the connector. +2. Select the **Connectors** tab and then select the BlackBerry DataParser connector that you created to display the flyout page, which 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. +3. 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. ## Known issues |
| compliance | Archive 17A 4 Bloomberg Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-17a-4-bloomberg-data.md | The following overview explains the process of using a data connector to archive 1. Your organization works with 17a-4 to set up and configure the Bloomberg DataParser. -2. On a regular basis, Bloomberg items are collected by the DataParser. The DataParser also converts the content of a message to an email message format. +2. Regularly, Bloomberg items are collected by the DataParser. The DataParser also converts the content of a message to an email message format. 3. The Bloomberg 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. The following overview explains the process of using a data connector to archive - The user who creates the Bloomberg 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 security and compliance centers" section in [Permissions in the Security & Compliance Center](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- 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 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.+- 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 Bloomberg DataParser connector The first step is to access to the Data connectors page in the compliance portal and create a 17a-4 connector for Bloomberg data. -1. Go to <https://compliance.microsoft.com> and then click **Data connectors** > **Bloomberg DataParser**. +1. Go to <https://compliance.microsoft.com> and then select **Data connectors** > **Bloomberg DataParser**. -2. On the **Bloomberg DataParser** product description page, click **Add connector**. +2. On the **Bloomberg DataParser** product description page, select **Add connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. Enter a unique name that identifies the connector and then click **Next**. +4. Enter a unique name that identifies the connector and then select **Next**. 5. Sign in to your 17a-4 account and complete the steps in the Bloomberg DataParser connection wizard. The Bloomberg DataParser connector will automatically map users to their Microso After you create a Bloomberg DataParser 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. +1. Go to <https://compliance.microsoft.com> and select **Data connectors** in the left nav. -2. Click the **Connectors** tab and then select the Bloomberg DataParser connector that you created to display the flyout page, which contains the properties and information about the connector. +2. Select the **Connectors** tab and then select the Bloomberg DataParser connector that you created to display the flyout page, which 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](data-connector-admin-logs.md). +3. 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](data-connector-admin-logs.md). ## Known issues |
| compliance | Archive 17A 4 Cisco Jabber Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-17a-4-cisco-jabber-data.md | The following overview explains the process of using a data connector to archive - The user who creates the Cisco Jabber 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 security and compliance centers" section in [Permissions in the Security & Compliance Center](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- 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 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.+- 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 Cisco Jabber DataParser connector The first step is to access to the Data connectors page in the compliance portal and create a 17a-4 connector for Cisco Jabber data. -1. Go to <https://compliance.microsoft.com> and then click **Data connectors** > **Cisco Jabber DataParser**. +1. Go to <https://compliance.microsoft.com> and then select **Data connectors** > **Cisco Jabber DataParser**. -2. On the **Cisco Jabber DataParser** product description page, click **Add connector**. +2. On the **Cisco Jabber DataParser** product description page, select **Add connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. Enter a unique name that identifies the connector and then click **Next**. +4. Enter a unique name that identifies the connector and then select **Next**. 5. Sign in to your 17a-4 account and complete the steps in the Cisco Jabber DataParser connection wizard. The Cisco Jabber DataParser connector will automatically map users to their Micr After you create a Cisco Jabber DataParser 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. +1. Go to <https://compliance.microsoft.com> and select **Data connectors** in the left nav. -2. Click the **Connectors** tab and then select the Cisco Jabber DataParser connector that you created to display the flyout page, which contains the properties and information about the connector. +2. Select the **Connectors** tab and then select the Cisco Jabber DataParser connector that you created to display the flyout page, which 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](data-connector-admin-logs.md). +3. 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](data-connector-admin-logs.md). ## Known issues |
| compliance | Archive 17A 4 Factset Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-17a-4-factset-data.md | The following overview explains the process of using a data connector to archive 1. Your organization works with 17a-4 to set up and configure the FactSet DataParser. -2. On a regular basis, FactSet items are collected by the DataParser. The DataParser also converts the content of a message to an email message format. +2. Regularly, FactSet items are collected by the DataParser. The DataParser also converts the content of a message to an email message format. 3. The FactSet 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. The following overview explains the process of using a data connector to archive - The user who creates the FactSet 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 security and compliance centers" section in [Permissions in the Security & Compliance Center](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- 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 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.+- 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 FactSet DataParser connector The first step is to access to the Data connectors page in the compliance portal and create a 17a-4 connector for FactSet data. -1. Go to <https://compliance.microsoft.com> and then click **Data connectors** > **FactSet DataParser**. +1. Go to <https://compliance.microsoft.com> and then select **Data connectors** > **FactSet DataParser**. -2. On the **FactSet DataParser** product description page, click **Add connector**. +2. On the **FactSet DataParser** product description page, select **Add connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. Enter a unique name that identifies the connector and then click **Next**. +4. Enter a unique name that identifies the connector and then select **Next**. 5. Sign in to your 17a-4 account and complete the steps in the FactSet DataParser connection wizard. The FactSet DataParser connector will automatically map users to their Microsoft After you create a FactSet DataParser 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. +1. Go to <https://compliance.microsoft.com> and select **Data connectors** in the left nav. -2. Click the **Connectors** tab and then select the FactSet DataParser connector that you created to display the flyout page, which contains the properties and information about the connector. +2. Select the **Connectors** tab and then select the FactSet DataParser connector that you created to display the flyout page, which 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](data-connector-admin-logs.md). +3. 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](data-connector-admin-logs.md). ## Known issues |
| compliance | Archive 17A 4 Fuze Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-17a-4-fuze-data.md | The following overview explains the process of using a data connector to archive 1. Your organization works with 17a-4 to set up and configure the Fuze DataParser. -2. 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. +2. Regularly, Fuze items are collected by the DataParser. The DataParser also converts the content of a message to an email message format. 3. The Fuze 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. The following overview explains the process of using a data connector to archive - The user who creates the Fuze 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 security and compliance centers" section in [Permissions in the Security & Compliance Center](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- 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 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.+- 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 Fuze DataParser connector The first step is to access to the Data connectors page in the compliance portal and create a 17a-4 connector for Fuze data. -1. Go to <https://compliance.microsoft.com> and then click **Data connectors** > **Fuze DataParser**. +1. Go to <https://compliance.microsoft.com> and then select **Data connectors** > **Fuze DataParser**. -2. On the **Fuze DataParser** product description page, click **Add connector**. +2. On the **Fuze DataParser** product description page, select **Add connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. Enter a unique name that identifies the connector and then click **Next**. +4. Enter a unique name that identifies the connector and then select **Next**. 5. Sign in to your 17a-4 account and complete the steps in the Fuze DataParser connection wizard. The Fuze DataParser connector will automatically map users to their Microsoft 36 After you create a Fuze DataParser 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. +1. Go to <https://compliance.microsoft.com> and select **Data connectors** in the left nav. -2. 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. +2. Select 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. -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](data-connector-admin-logs.md). +3. 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](data-connector-admin-logs.md). ## Known issues |
| compliance | Archive 17A 4 Fxconnect Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-17a-4-fxconnect-data.md | The following overview explains the process of using a data connector to archive 1. Your organization works with 17a-4 to set up and configure the FX Connect DataParser. -2. On a regular basis, FX Connect items are collected by the DataParser. The DataParser also converts the content of a message to an email message format. +2. Regularly, FX Connect items are collected by the DataParser. The DataParser also converts the content of a message to an email message format. 3. The FX Connect 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. The following overview explains the process of using a data connector to archive - The user who creates the FX Connect 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 security and compliance centers" section in [Permissions in the Security & Compliance Center](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- 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 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.+- 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 FX Connect DataParser connector The first step is to access to the Data connectors page in the compliance portal and create a 17a-4 connector for FX Connect data. -1. Go to <https://compliance.microsoft.com> and then click **Data connectors** > **FX Connect DataParser**. +1. Go to <https://compliance.microsoft.com> and then select **Data connectors** > **FX Connect DataParser**. -2. On the **FX Connect DataParser** product description page, click **Add connector**. +2. On the **FX Connect DataParser** product description page, select **Add connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. Enter a unique name that identifies the connector and then click **Next**. +4. Enter a unique name that identifies the connector and then select **Next**. 5. Sign in to your 17a-4 account and complete the steps in the FX Connect DataParser connection wizard. The FX Connect DataParser connector will automatically map users to their Micros After you create a FX Connect DataParser 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. +1. Go to <https://compliance.microsoft.com> and select **Data connectors** in the left nav. -2. Click the **Connectors** tab and then select the FX Connect DataParser connector that you created to display the flyout page, which contains the properties and information about the connector. +2. Select the **Connectors** tab and then select the FX Connect DataParser connector that you created to display the flyout page, which 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](data-connector-admin-logs.md). +3. 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](data-connector-admin-logs.md). ## Known issues |
| compliance | Archive 17A 4 Ice Im Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-17a-4-ice-im-data.md | The following overview explains the process of using a data connector to archive 1. Your organization works with 17a-4 to set up and configure the ICE DataParser. -2. On a regular basis, ICE Connect Chat items are collected by the DataParser. The DataParser also converts the content of a message to an email message format. +2. Regularly, ICE Connect Chat items are collected by the DataParser. The DataParser also converts the content of a message to an email message format. 3. The ICE 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. The following overview explains the process of using a data connector to archive - The user who creates the ICE 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 security and compliance centers" section in [Permissions in the Security & Compliance Center](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- 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 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.+- 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 an ICE DataParser connector The first step is to access to the Data connectors page in the compliance portal and create a 17a-4 connector for ICE Connect Chat data. -1. Go to <https://compliance.microsoft.com> and then click **Data connectors** > **ICE DataParser**. +1. Go to <https://compliance.microsoft.com> and then select **Data connectors** > **ICE DataParser**. -2. On the **ICE DataParser** product description page, click **Add connector**. +2. On the **ICE DataParser** product description page, select **Add connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. Enter a unique name that identifies the connector and then click **Next**. +4. Enter a unique name that identifies the connector and then select **Next**. 5. Sign in to your 17a-4 account and complete the steps in the ICE DataParser connection wizard. The ICE DataParser connector will automatically map users to their Microsoft 365 After you create an ICE DataParser 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. +1. Go to <https://compliance.microsoft.com> and select **Data connectors** in the left nav. -2. Click the **Connectors** tab and then select the ICE DataParser connector that you created to display the flyout page, which contains the properties and information about the connector. +2. Select the **Connectors** tab and then select the ICE DataParser connector that you created to display the flyout page, which 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](data-connector-admin-logs.md). +3. 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](data-connector-admin-logs.md). ## Known issues |
| compliance | Archive 17A 4 Investedge Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-17a-4-investedge-data.md | The following overview explains the process of using a data connector to archive 1. Your organization works with 17a-4 to set up and configure the InvestEdge DataParser. -2. On a regular basis, InvestEdge items are collected by the DataParser. The DataParser also converts the content of a message to an email message format. +2. Regularly, InvestEdge items are collected by the DataParser. The DataParser also converts the content of a message to an email message format. 3. The InvestEdge 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. The following overview explains the process of using a data connector to archive - The user who creates the InvestEdge 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 security and compliance centers" section in [Permissions in the Security & Compliance Center](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- 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 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.+- 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 InvestEdge DataParser connector The first step is to access to the Data connectors page in the compliance portal and create a 17a-4 connector for InvestEdge data. -1. Go to <https://compliance.microsoft.com> and then click **Data connectors** > **InvestEdge DataParser**. +1. Go to <https://compliance.microsoft.com> and then select **Data connectors** > **InvestEdge DataParser**. -2. On the **InvestEdge DataParser** product description page, click **Add connector**. +2. On the **InvestEdge DataParser** product description page, select **Add connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. Enter a unique name that identifies the connector and then click **Next**. +4. Enter a unique name that identifies the connector and then select **Next**. 5. Sign in to your 17a-4 account and complete the steps in the InvestEdge DataParser connection wizard. The InvestEdge DataParser connector will automatically map users to their Micros After you create a InvestEdge DataParser 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. +1. Go to <https://compliance.microsoft.com> and select **Data connectors** in the left nav. -2. Click the **Connectors** tab and then select the InvestEdge DataParser connector that you created to display the flyout page, which contains the properties and information about the connector. +2. Select the **Connectors** tab and then select the InvestEdge DataParser connector that you created to display the flyout page, which 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](data-connector-admin-logs.md). +3. 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](data-connector-admin-logs.md). ## Known issues |
| compliance | Archive 17A 4 Liveperson Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-17a-4-liveperson-data.md | The following overview explains the process of using a data connector to archive 1. Your organization works with 17a-4 to set up and configure the the LivePerson Conversational Cloud DataParser. -2. On a regular basis, LivePerson Conversational Cloud items are collected by the DataParser. The DataParser also converts the content of a message to an email message format. +2. Regularly, LivePerson Conversational Cloud items are collected by the DataParser. The DataParser also converts the content of a message to an email message format. 3. The LivePerson Conversational Cloud 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. The following overview explains the process of using a data connector to archive - The user who creates the LivePerson Conversational Cloud 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 security and compliance centers" section in [Permissions in the Security & Compliance Center](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- 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 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.+- 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 LivePerson Conversational Cloud DataParser connector The first step is to access to the Data connectors page in the compliance portal and create a 17a-4 connector for LivePerson Conversational Cloud data. -1. Go to <https://compliance.microsoft.com> and then click **Data connectors** > **LivePerson Conversational Cloud DataParser**. +1. Go to <https://compliance.microsoft.com> and then select **Data connectors** > **LivePerson Conversational Cloud DataParser**. -2. On the **LivePerson Conversational Cloud DataParser** product description page, click **Add connector**. +2. On the **LivePerson Conversational Cloud DataParser** product description page, select **Add connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. Enter a unique name that identifies the connector and then click **Next**. +4. Enter a unique name that identifies the connector and then select **Next**. 5. Sign in to your 17a-4 account and complete the steps in the LivePerson Conversational Cloud DataParser connection wizard. The LivePerson Conversational Cloud DataParser connector will automatically map After you create a LivePerson Conversational Cloud DataParser 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. +1. Go to <https://compliance.microsoft.com> and select **Data connectors** in the left nav. -2. Click the **Connectors** tab and then select the LivePerson Conversational Cloud DataParser connector that you created to display the flyout page, which contains the properties and information about the connector. +2. Select the **Connectors** tab and then select the LivePerson Conversational Cloud DataParser connector that you created to display the flyout page, which 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](data-connector-admin-logs.md). +3. 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](data-connector-admin-logs.md). ## Known issues |
| compliance | Archive 17A 4 Quip Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-17a-4-quip-data.md | The following overview explains the process of using a data connector to archive 1. Your organization works with 17a-4 to set up and configure the Quip DataParser. -2. On a regular basis, Quip items are collected by the DataParser. The DataParser also converts the content of a message to an email message format. +2. Regularly, Quip items are collected by the DataParser. The DataParser also converts the content of a message to an email message format. 3. The Quip 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. The following overview explains the process of using a data connector to archive - The user who creates the Quip 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 security and compliance centers" section in [Permissions in the Security & Compliance Center](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- 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 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.+- 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 Quip DataParser connector The first step is to access to the Data connectors page in the compliance portal and create a 17a-4 connector for Quip data. -1. Go to <https://compliance.microsoft.com> and then click **Data connectors** > **Quip DataParser**. +1. Go to <https://compliance.microsoft.com> and then select **Data connectors** > **Quip DataParser**. -2. On the **Quip DataParser** product description page, click **Add connector**. +2. On the **Quip DataParser** product description page, select **Add connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. Enter a unique name that identifies the connector and then click **Next**. +4. Enter a unique name that identifies the connector and then select **Next**. 5. Sign in to your 17a-4 account and complete the steps in the Quip DataParser connection wizard. The Quip DataParser connector will automatically map users to their Microsoft 36 After you create a Quip DataParser 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. +1. Go to <https://compliance.microsoft.com> and select **Data connectors** in the left nav. -2. Click the **Connectors** tab and then select the Quip DataParser connector that you created to display the flyout page, which contains the properties and information about the connector. +2. Select the **Connectors** tab and then select the Quip DataParser connector that you created to display the flyout page, which 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](data-connector-admin-logs.md). +3. 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](data-connector-admin-logs.md). ## Known issues |
| compliance | Archive 17A 4 Refinitiv Messenger Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-17a-4-refinitiv-messenger-data.md | The following overview explains the process of using a data connector to archive - The user who creates the Refinitiv Eikon Messenger 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 security and compliance centers" section in [Permissions in the Security & Compliance Center](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- 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 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.+- 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 Refinitiv Eikon Messenger DataParser connector The first step is to access to the Data connectors page in the compliance portal and create a 17a-4 connector for Refinitiv Eikon Messenger data. -1. Go to <https://compliance.microsoft.com> and then click **Data connectors** > **Refinitiv Eikon Messenger DataParser**. +1. Go to <https://compliance.microsoft.com> and then select **Data connectors** > **Refinitiv Eikon Messenger DataParser**. -2. On the **Refinitiv Eikon Messenger DataParser** product description page, click **Add connector**. +2. On the **Refinitiv Eikon Messenger DataParser** product description page, select **Add connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. Enter a unique name that identifies the connector and then click **Next**. +4. Enter a unique name that identifies the connector and then select **Next**. 5. Sign in to your 17a-4 account and complete the steps in the Refinitiv Eikon Messenger DataParser connection wizard. The Refinitiv Eikon Messenger DataParser connector will automatically map users After you create a Refinitiv Eikon Messenger DataParser 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. +1. Go to <https://compliance.microsoft.com> and select **Data connectors** in the left nav. -2. Click the **Connectors** tab and then select the Refinitiv Eikon Messenger DataParser connector that you created to display the flyout page, which contains the properties and information about the connector. +2. Select the **Connectors** tab and then select the Refinitiv Eikon Messenger DataParser connector that you created to display the flyout page, which 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](data-connector-admin-logs.md). +3. 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](data-connector-admin-logs.md). ## Known issues |
| compliance | Archive 17A 4 Servicenow Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-17a-4-servicenow-data.md | The following overview explains the process of using a data connector to archive 1. Your organization works with 17a-4 to set up and configure the ServiceNow DataParser. -2. On a regular basis, ServiceNow items are collected by the DataParser. The DataParser also converts the content of a message to an email message format. +2. Regularly, ServiceNow items are collected by the DataParser. The DataParser also converts the content of a message to an email message format. 3. The ServiceNow 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. The following overview explains the process of using a data connector to archive - The user who creates the ServiceNow 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 security and compliance centers" section in [Permissions in the Security & Compliance Center](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- 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 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.+- 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 ServiceNow DataParser connector The first step is to access to the Data connectors page in the compliance portal and create a 17a-4 connector for ServiceNow data. -1. Go to <https://compliance.microsoft.com> and then click **Data connectors** > **ServiceNow DataParser**. +1. Go to <https://compliance.microsoft.com> and then select **Data connectors** > **ServiceNow DataParser**. -2. On the **ServiceNow DataParser** product description page, click **Add connector**. +2. On the **ServiceNow DataParser** product description page, select **Add connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. Enter a unique name that identifies the connector and then click **Next**. +4. Enter a unique name that identifies the connector and then select **Next**. 5. Sign in to your 17a-4 account and complete the steps in the ServiceNow DataParser connection wizard. The ServiceNow DataParser connector will automatically map users to their Micros After you create a ServiceNow DataParser 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. +1. Go to <https://compliance.microsoft.com> and select **Data connectors** in the left nav. -2. Click the **Connectors** tab and then select the ServiceNow DataParser connector that you created to display the flyout page, which contains the properties and information about the connector. +2. Select the **Connectors** tab and then select the ServiceNow DataParser connector that you created to display the flyout page, which 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](data-connector-admin-logs.md). +3. 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](data-connector-admin-logs.md). ## Known issues |
| compliance | Archive 17A 4 Skype For Business Server Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-17a-4-skype-for-business-server-data.md | The following overview explains the process of using a data connector to archive 1. Your organization works with 17a-4 to set up and configure the Skype for Business Server DataParser. -2. On a regular basis, Skype for Business Server items are collected by the DataParser. The DataParser also converts the content of a message to an email message format. +2. Regularly, Skype for Business Server items are collected by the DataParser. The DataParser also converts the content of a message to an email message format. 3. The Skype for Business Server 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. The following overview explains the process of using a data connector to archive - The user who creates the Skype for Business Server 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 security and compliance centers" section in [Permissions in the Security & Compliance Center](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- 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 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.+- 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 Skype for Business Server DataParser connector The first step is to access to the Data connectors page in the compliance portal and create a 17a-4 connector for Skype for Business Server data. -1. Go to <https://compliance.microsoft.com> and then click **Data connectors** > **Skype for Business Server DataParser**. +1. Go to <https://compliance.microsoft.com> and then select **Data connectors** > **Skype for Business Server DataParser**. -2. On the **Skype for Business Server DataParser** product description page, click **Add connector**. +2. On the **Skype for Business Server DataParser** product description page, select **Add connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. Enter a unique name that identifies the connector and then click **Next**. +4. Enter a unique name that identifies the connector and then select **Next**. 5. Sign in to your 17a-4 account and complete the steps in the Skype for Business Server DataParser connection wizard. The Skype for Business Server DataParser connector will automatically map users After you create a Skype for Business Server DataParser 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. +1. Go to <https://compliance.microsoft.com> and select **Data connectors** in the left nav. -2. Click the **Connectors** tab and then select the Skype for Business Server DataParser connector that you created to display the flyout page, which contains the properties and information about the connector. +2. Select the **Connectors** tab and then select the Skype for Business Server DataParser connector that you created to display the flyout page, which 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](data-connector-admin-logs.md). +3. 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](data-connector-admin-logs.md). ## Known issues |
| compliance | Archive 17A 4 Slack Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-17a-4-slack-data.md | The following overview explains the process of using a data connector to archive 1. Your organization works with 17a-4 to set up and configure the Slack DataParser. -2. On a regular basis, Slack items are collected by the DataParser. The DataParser also converts the content of a message to an email message format. +2. Regularly, Slack items are collected by the DataParser. The DataParser also converts the content of a message to an email message format. 3. The Slack 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. The following overview explains the process of using a data connector to archive - The user who creates the Slack 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 security and compliance centers" section in [Permissions in the Security & Compliance Center](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- 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 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.+- 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 Slack DataParser connector The first step is to access to the Data connectors page in the compliance portal and create a 17a-4 connector for Slack data. -1. Go to <https://compliance.microsoft.com> and then click **Data connectors** > **Slack DataParser**. +1. Go to <https://compliance.microsoft.com> and then select **Data connectors** > **Slack DataParser**. -2. On the **Slack DataParser** product description page, click **Add connector**. +2. On the **Slack DataParser** product description page, select **Add connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. Enter a unique name that identifies the connector and then click **Next**. +4. Enter a unique name that identifies the connector and then select **Next**. 5. Sign in to your 17a-4 account and complete the steps in the Slack DataParser connection wizard. The Slack DataParser connector will automatically map users to their Microsoft 3 After you create a Slack DataParser 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. +1. Go to <https://compliance.microsoft.com> and select **Data connectors** in the left nav. -2. Click the **Connectors** tab and then select the Slack DataParser connector that you created to display the flyout page, which contains the properties and information about the connector. +2. Select the **Connectors** tab and then select the Slack DataParser connector that you created to display the flyout page, which 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](data-connector-admin-logs.md). +3. 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](data-connector-admin-logs.md). ## Known issues |
| compliance | Archive 17A 4 Sql Database Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-17a-4-sql-database-data.md | The following overview explains the process of using a data connector to archive 1. Your organization works with 17a-4 to set up and configure the SQL DataParser. -2. On a regular basis, SQL items are collected by the DataParser. The DataParser also converts the content of a message to an email message format. +2. Regularly, SQL items are collected by the DataParser. The DataParser also converts the content of a message to an email message format. 3. 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. The following overview explains the process of using a data connector to archive - 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 security and compliance centers" section in [Permissions in the Security & Compliance Center](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- 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 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.+- 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. -1. Go to <https://compliance.microsoft.com> and then click **Data connectors** > **SQL DataParser**. +1. Go to <https://compliance.microsoft.com> and then select **Data connectors** > **SQL DataParser**. -2. On the **SQL DataParser** product description page, click **Add connector**. +2. On the **SQL DataParser** product description page, select **Add connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. Enter a unique name that identifies the connector and then click **Next**. +4. Enter a unique name that identifies the connector and then select **Next**. 5. Sign in to your 17a-4 account and complete the steps in the SQL DataParser connection wizard. The SQL DataParser connector will automatically map users to their Microsoft 365 After you create a SQL DataParser 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. +1. Go to <https://compliance.microsoft.com> and select **Data connectors** in the left nav. -2. Click 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. +2. 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. -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](data-connector-admin-logs.md). +3. 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](data-connector-admin-logs.md). ## Known issues |
| compliance | Archive 17A 4 Symphony Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-17a-4-symphony-data.md | The following overview explains the process of using a data connector to archive 1. Your organization works with 17a-4 to set up and configure the Symphony DataParser. -2. On a regular basis, Symphony items are collected by the DataParser. The DataParser also converts the content of a message to an email message format. +2. Regularly, Symphony items are collected by the DataParser. The DataParser also converts the content of a message to an email message format. 3. The Symphony 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. The following overview explains the process of using a data connector to archive - The user who creates the Symphony 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 security and compliance centers" section in [Permissions in the Security & Compliance Center](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- 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 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.+- 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 Symphony DataParser connector The first step is to access to the Data connectors page in the compliance portal and create a 17a-4 connector for Symphony data. -1. Go to <https://compliance.microsoft.com> and then click **Data connectors** > **Symphony DataParser**. +1. Go to <https://compliance.microsoft.com> and then select **Data connectors** > **Symphony DataParser**. -2. On the **Symphony DataParser** product description page, click **Add connector**. +2. On the **Symphony DataParser** product description page, select **Add connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. Enter a unique name that identifies the connector and then click **Next**. +4. Enter a unique name that identifies the connector and then select **Next**. 5. Sign in to your 17a-4 account and complete the steps in the Symphony DataParser connection wizard. The Symphony DataParser connector will automatically map users to their Microsof After you create a Symphony DataParser 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. +1. Go to <https://compliance.microsoft.com> and select **Data connectors** in the left nav. -2. Click the **Connectors** tab and then select the Symphony DataParser connector that you created to display the flyout page, which contains the properties and information about the connector. +2. Select the **Connectors** tab and then select the Symphony DataParser connector that you created to display the flyout page, which 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](data-connector-admin-logs.md). +3. 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](data-connector-admin-logs.md). ## Known issues |
| compliance | Archive 17A 4 Webex Teams Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-17a-4-webex-teams-data.md | The following overview explains the process of using a data connector to archive 1. Your organization works with 17a-4 to set up and configure the Cisco Webex DataParser. -2. On a regular basis, Cisco Webex items are collected by the DataParser. The DataParser also converts the content of a message to an email message format. +2. Regularly, Cisco Webex items are collected by the DataParser. The DataParser also converts the content of a message to an email message format. 3. The Cisco Webex 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. The following overview explains the process of using a data connector to archive - The user who creates the Cisco Webex 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 security and compliance centers" section in [Permissions in the Security & Compliance Center](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- 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 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.+- 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 Cisco Webex DataParser connector The first step is to access to the Data connectors page in the compliance portal and create a 17a-4 connector for Cisco Webex data. -1. Go to <https://compliance.microsoft.com> and then click **Data connectors** > **Cisco Webex DataParser**. +1. Go to <https://compliance.microsoft.com> and then select **Data connectors** > **Cisco Webex DataParser**. -2. On the **Cisco Webex DataParser** product description page, click **Add connector**. +2. On the **Cisco Webex DataParser** product description page, select **Add connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. Enter a unique name that identifies the connector and then click **Next**. +4. Enter a unique name that identifies the connector and then select **Next**. 5. Sign in to your 17a-4 account and complete the steps in the Cisco Webex DataParser connection wizard. The Cisco Webex DataParser connector will automatically map users to their Micro After you create a Cisco Webex DataParser 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. +1. Go to <https://compliance.microsoft.com> and select **Data connectors** in the left nav. -2. Click the **Connectors** tab and then select the Cisco Webex DataParser connector that you created to display the flyout page, which contains the properties and information about the connector. +2. Select the **Connectors** tab and then select the Cisco Webex DataParser connector that you created to display the flyout page, which 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](data-connector-admin-logs.md). +3. 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](data-connector-admin-logs.md). ## Known issues |
| compliance | Archive 17A 4 Zoom Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-17a-4-zoom-data.md | The following overview explains the process of using a data connector to archive 1. Your organization works with 17a-4 to set up and configure the Zoom DataParser. -2. On a regular basis, Zoom items are collected by the DataParser. The DataParser also converts the content of a message to an email message format. +2. Regularly, Zoom items are collected by the DataParser. The DataParser also converts the content of a message to an email message format. 3. The Zoom 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. The following overview explains the process of using a data connector to archive - The user who creates the Zoom 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 security and compliance centers" section in [Permissions in the Security & Compliance Center](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- 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 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.+- 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 Zoom DataParser connector The first step is to access to the Data connectors page in the compliance portal and create a 17a-4 connector for Zoom data. -1. Go to <https://compliance.microsoft.com> and then click **Data connectors** > **Zoom DataParser**. +1. Go to <https://compliance.microsoft.com> and then select **Data connectors** > **Zoom DataParser**. -2. On the **Zoom DataParser** product description page, click **Add connector**. +2. On the **Zoom DataParser** product description page, select **Add connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. Enter a unique name that identifies the connector and then click **Next**. +4. Enter a unique name that identifies the connector and then select **Next**. 5. Sign in to your 17a-4 account and complete the steps in the Zoom DataParser connection wizard. The Zoom DataParser connector will automatically map users to their Microsoft 36 After you create a Zoom DataParser 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. +1. Go to <https://compliance.microsoft.com> and select **Data connectors** in the left nav. -2. Click the **Connectors** tab and then select the Zoom DataParser connector that you created to display the flyout page, which contains the properties and information about the connector. +2. Select the **Connectors** tab and then select the Zoom DataParser connector that you created to display the flyout page, which 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](data-connector-admin-logs.md). +3. 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](data-connector-admin-logs.md). ## Known issues |
| compliance | Archive Android Archiver Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-android-archiver-data.md | Some of the implementation steps required to archive Android communication data - The user who creates a Android Archiver connector 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](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- This TeleMessage 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 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.+- This TeleMessage 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. ## Create an Android Archiver connector The last step is to create an Android Archiver connector in the compliance portal. The connector uses the information you provide to connect to the TeleMessage site and transfer Android communication to the corresponding user mailbox boxes in Microsoft 365. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com) and click **Data connectors** > **Android Archiver**. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com) and select **Data connectors** > **Android Archiver**. -2. On the **Android Archiver** product description page, click **Add connector**. +2. On the **Android Archiver** product description page, select **Add connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. On the **Login to TeleMessage** page, under Step 3, enter the required information in the following boxes and then click **Next**. +4. On the **Login to TeleMessage** page, under Step 3, enter the required information in the following boxes and then select **Next**. - **Username:** Your TeleMessage username. - **Password:** Your TeleMessage password. -5. After the connector is created, close the pop-up window and click **Next**. +5. After the connector is created, close the pop-up window and select **Next**. -6. On the **User mapping** page, enable automatic user mapping and click **Next**. In case you need custom mapping upload a CSV file, and click **Next**. +6. On the **User mapping** page, enable automatic user mapping and select **Next**. In case you need custom mapping upload a CSV file, and select **Next**. -7. Review your settings, and then click **Finish** to create the connector. +7. Review your settings, and then select **Finish** to create the connector. 8. Go to the Connectors tab in **Data connectors** page to see the progress of the import process for the new connector. |
| compliance | Archive Att Network Archiver Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-att-network-archiver-data.md | Some of the implementation steps required to archive AT&T Network data are exter - The user who creates a AT&T Network connector 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](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- This TeleMessage 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 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.+- This TeleMessage 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. ## Create a AT&T Network connector After you've completed the prerequisites described in the previous section, you can create an AT&T Network connector in the compliance portal. The connector uses the information you provide to connect to the TeleMessage site and transfer SMS and MMS messages to the corresponding user mailbox boxes in Microsoft 365. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and then click **Data connectors** \ **AT&T Network**. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and then select **Data connectors** \ **AT&T Network**. -2. On the **AT&T Network product** description page, click **Add connector** +2. On the **AT&T Network product** description page, select **Add connector** -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. On the **Login to TeleMessage** page, under Step 3, enter the required information in the following boxes and then click **Next**. +4. On the **Login to TeleMessage** page, under Step 3, enter the required information in the following boxes and then select **Next**. - **Username:** Your TeleMessage username. After you've completed the prerequisites described in the previous section, you 5. After the connector is created, you can close the pop-up window and go to the next page. -6. On the **User mapping** page, enable automatic user mapping. To enable custom mapping, upload a CSV file that contains the user mapping information, and then click **Next**. +6. On the **User mapping** page, enable automatic user mapping. To enable custom mapping, upload a CSV file that contains the user mapping information, and then select **Next**. -7. Review your settings, and then click **Finish** to create the connector. +7. Review your settings, and then select **Finish** to create the connector. 8. Go to the **Connectors** tab on the **Data connectors** page in the compliance center to see the progress of the import process for the new connector. |
| compliance | Archive Bell Network Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-bell-network-data.md | Some of the implementation steps required to archive Bell Network data are exter - The user who creates a Bell Network connector 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](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- This TeleMessage 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 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.+- This TeleMessage 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. ## Create a Bell Network connector The last step is to create a Bell Network connector in the compliance portal. The connector uses the information you provide to connect to the TeleMessage site and transfer SMS/ MMS messages to the corresponding user mailbox boxes in Microsoft 365. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com) and then click **Data connectors** > **Bell SMS/MMS Network Archiver**. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com) and then select **Data connectors** > **Bell SMS/MMS Network Archiver**. -2. On the **Bell Network** product description page, click **Add connector** +2. On the **Bell Network** product description page, select **Add connector** -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. On the **Login to TeleMessage** page, under Step 3, enter the required information in the following boxes and then click **Next**. +4. On the **Login to TeleMessage** page, under Step 3, enter the required information in the following boxes and then select **Next**. - **Username:** Your TeleMessage username. The last step is to create a Bell Network connector in the compliance portal. Th 5. After the connector is created, you can close the pop-up window and go to the next page. -6. On the **User mapping** page, enable automatic user mapping. To enable custom mapping, upload a CSV file that contains the user mapping information, and then click **Next**. +6. On the **User mapping** page, enable automatic user mapping. To enable custom mapping, upload a CSV file that contains the user mapping information, and then select **Next**. -7. Review your settings, and then click **Finish** to create the connector. +7. Review your settings, and then select **Finish** to create the connector. 8. Go to the **Connectors** tab on the **Data connectors** page in the compliance center to see the progress of the import process for the new connector. |
| compliance | Archive Bloomberg Message Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-bloomberg-message-data.md | The steps in this section show you how to set up a Bloomberg Message connector u The first step is to obtain a copy of the PGP and SSH public keys. You use these keys in Step 2 to configure the Bloomberg SFTP site to allow the connector (that you create in Step 3) to connect to the SFTP site and transfer the Bloomberg Message email data to Microsoft 365 mailboxes. You also obtain an IP address in this step, which you use when configuring the Bloomberg SFTP site. -1. Go to <https://compliance.microsoft.com> and click **Data connectors** in the left nav. +1. Go to <https://compliance.microsoft.com> and select **Data connectors** in the left nav. -2. On the **Data connectors** page under **Bloomberg Message**, click **View**. +2. On the **Data connectors** page under **Bloomberg Message**, select **View**. -3. On the **Bloomberg Message** product description page, click **Add connector** +3. On the **Bloomberg Message** product description page, select **Add connector** -4. On the **Terms of service** page, click **Accept**. +4. On the **Terms of service** page, select **Accept**. -5. On the **Add credentials for content source** page, click **I want to use PGP and SSH public keys provided by Microsoft**. +5. On the **Add credentials for content source** page, select **I want to use PGP and SSH public keys provided by Microsoft**.  -6. Under step 1, click the **Download SSH key**, **Download PGP key**, and **Download IP address** links to save a copy of each file to your local computer. +6. Under step 1, select the **Download SSH key**, **Download PGP key**, and **Download IP address** links to save a copy of each file to your local computer.  The first step is to obtain a copy of the PGP and SSH public keys. You use these - IP address: The Bloomberg SFTP site is configured to accept connection requests from this IP address. The same IP address is used by the Bloomberg Message connector to connect to the SFTP site and transfer Bloomberg Message data to Microsoft 365. -7. Click **Cancel** to close the wizard. You come back to this wizard in Step 3 to create the connector. +7. Select **Cancel** to close the wizard. You come back to this wizard in Step 3 to create the connector. ### Step 2: Configure the Bloomberg SFTP site The next step is to use the PGP and SSH public keys and the IP address that you The last step is to create a Bloomberg Message connector in the compliance portal. The connector uses the information you provide to connect to the Bloomberg SFTP site and transfer email messages to the corresponding user mailbox boxes in Microsoft 365. -1. Go to <https://compliance.microsoft.com> and click **Data connectors** in the left nav. +1. Go to <https://compliance.microsoft.com> and select **Data connectors** in the left nav. -2. On the **Data connectors** page under **Bloomberg Message**, click **View**. +2. On the **Data connectors** page under **Bloomberg Message**, select **View**. -3. On the **Bloomberg Message** product description page, click **Add connector** +3. On the **Bloomberg Message** product description page, select **Add connector** -4. On the **Terms of service** page, click **Accept**. +4. On the **Terms of service** page, select **Accept**. -5. On the **Add credentials for content source** page, click **I want to use PGP and SSH public keys provided by Microsoft**. +5. On the **Add credentials for content source** page, select **I want to use PGP and SSH public keys provided by Microsoft**. -6. Under Step 3, enter the required information in the following boxes and then click **Validate connection**. +6. Under Step 3, enter the required information in the following boxes and then select **Validate connection**. - **Name:** The name for the connector. It must be unique in your organization. The last step is to create a Bloomberg Message connector in the compliance porta - **SFTP port:** The port number for the Bloomberg SFTP site. The connector uses this port to connect to the SFTP site. -7. After the connection is successfully validated, click **Next**. +7. After the connection is successfully validated, select **Next**. 8. On the **Define user** page, specify the users to import data for. The last step is to create a Bloomberg Message connector in the compliance porta > [!NOTE] > The connector imports message items to the mailbox of a specific user. A new folder named **BloombergMessage** is created in the specific user's mailbox and the items will be imported to it. The connector does by using the value of the *CorporateEmailAddress* property. Every chat message contains this property, and the property is populated with the email address of every participant of the chat message. In addition to automatic user mapping using the value of the *CorporateEmailAddress* property, you can also define custom mapping by uploading a CSV mapping file. The mapping file should contain the Bloomberg UUID and corresponding Microsoft 365 mailbox address for each user. If you enable automatic user mapping and provide a custom mapping, for every message item the connector will first look at custom mapping file. If it doesn't find a valid Microsoft 365 user that corresponds to a user's Bloomberg UUID, the connector will use the *CorporateEmailAddress* property of the chat item. If the connector doesn't find a valid Microsoft 365 user in either the custom mapping file or the *CorporateEmailAddress* property of the message item, the item won't be imported. -10. Click **Next**, review your settings, and then click **Finish** to create the connector. +10. Select **Next**, review your settings, and then select **Finish** to create the connector. -11. Go to the **Data connectors** page to see the progress of the import process for the new connector. Click the connector to display the flyout page, which contains information about the connector. +11. Go to the **Data connectors** page to see the progress of the import process for the new connector. Select the connector to display the flyout page, which contains information about the connector. ## Set up a connector using private keys If your organization has used PGP and SSH private keys to set up a Bloomberg SFT To obtain the IP address: -1. Go to <https://compliance.microsoft.com> and click **Data connectors** in the left nav. +1. Go to <https://compliance.microsoft.com> and select **Data connectors** in the left nav. -2. On the **Data connectors** page under **Bloomberg Message**, click **View**. +2. On the **Data connectors** page under **Bloomberg Message**, select **View**. -3. On the **Bloomberg Message** product description page, click **Add connector** +3. On the **Bloomberg Message** product description page, select **Add connector** -4. On the **Terms of service** page, click **Accept**. +4. On the **Terms of service** page, select **Accept**. -5. On the **Add credentials for content source** page, click **I want to use PGP and SSH private keys**. +5. On the **Add credentials for content source** page, select **I want to use PGP and SSH private keys**. -6. Under step 1, click **Download IP address** to save a copy of the IP address file to your local computer. +6. Under step 1, select **Download IP address** to save a copy of the IP address file to your local computer.  -7. Click **Cancel** to close the wizard. You come back to this wizard in Step 2 to create the connector. +7. Select **Cancel** to close the wizard. You come back to this wizard in Step 2 to create the connector. You need to work with Bloomberg customer support to configure your Bloomberg SFTP site to accept connection requests from this IP address. Contact [Bloomberg customer support](https://service.bloomberg.com/portal/sessions/new?utm_source=bloomberg-menu&utm_medium=csc) for assistance. You need to work with Bloomberg customer support to configure your Bloomberg SFT After your Bloomberg SFTP site is configured, the next step is to create a Bloomberg Message connector in the compliance portal. The connector uses the information you provide to connect to the Bloomberg SFTP site and transfer email messages to the corresponding user mailbox boxes in Microsoft 365. To complete this step, be sure to have copies of the same private keys and key passphrases that you used to set up your Bloomberg SFTP site. -1. Go to <https://compliance.microsoft.com> and click **Data connectors** in the left nav. +1. Go to <https://compliance.microsoft.com> and select **Data connectors** in the left nav. -2. On the **Data connectors** page under **Bloomberg Message**, click **View**. +2. On the **Data connectors** page under **Bloomberg Message**, select **View**. -3. On the **Bloomberg Message** product description page, click **Add connector** +3. On the **Bloomberg Message** product description page, select **Add connector** -4. On the **Terms of service** page, click **Accept**. +4. On the **Terms of service** page, select **Accept**. -5. On the **Add credentials for content source** page, click **I want to use PGP and SSH private keys**. +5. On the **Add credentials for content source** page, select **I want to use PGP and SSH private keys**.  -6. Under Step 3, enter the required information in the following boxes and then click **Validate connection**. +6. Under Step 3, enter the required information in the following boxes and then select **Validate connection**. - **Name:** The name for the connector. It must be unique in your organization. After your Bloomberg SFTP site is configured, the next step is to create a Bloom - **SSH key passphrase:** The passphrase for the SSH private key. -7. After the connection is successfully validated, click **Next**. +7. After the connection is successfully validated, select **Next**. 8. On the **Define user** page, specify the users to import data for After your Bloomberg SFTP site is configured, the next step is to create a Bloom > [!NOTE] > The connector imports message items to the mailbox of a specific user. A new folder named **BloombergMessage** is created in the specific user's mailbox and the items will be imported to it. The connector does by using the value of the *CorporateEmailAddress* property. Every chat message contains this property, and the property is populated with the email address of every participant of the chat message. In addition to automatic user mapping using the value of the *CorporateEmailAddress* property, you can also define custom mapping by uploading a CSV mapping file. The mapping file should contain the Bloomberg UUID and corresponding Microsoft 365 mailbox address for each user. If you enable automatic user mapping and provide a custom mapping, for every message item the connector will first look at custom mapping file. If it doesn't find a valid Microsoft 365 user that corresponds to a user's Bloomberg UUID, the connector will use the *CorporateEmailAddress* property of the chat item. If the connector doesn't find a valid Microsoft 365 user in either the custom mapping file or the *CorporateEmailAddress* property of the message item, the item won't be imported. -10. Click **Next**, review your settings, and then click **Finish** to create the connector. +10. Select **Next**, review your settings, and then select **Finish** to create the connector. -11. Go to the **Data connectors** page to see the progress of the import process for the new connector. Click the connector to display the flyout page, which contains information about the connector. +11. Go to the **Data connectors** page to see the progress of the import process for the new connector. Select the connector to display the flyout page, which contains information about the connector. ## Known issues |
| compliance | Archive Celltrust Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-celltrust-data.md | The following overview explains the process of using a connector to archive Cell - The user who creates the CellTrust 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](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- 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.+- 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 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 the CellTrust connector The first step is to access to the **Data Connectors** in the compliance portal and create a connector for CellTrust data. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and then click **Data connectors** \> **CellTrust**. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and then select **Data connectors** \> **CellTrust**. -2. On the **CellTrust** product description page, click **Add connector**. +2. On the **CellTrust** product description page, select **Add connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. Enter a unique name that identifies the connector and then click **Next**. +4. Enter a unique name that identifies the connector and then select **Next**. 5. Sign in to your Merge1 account to configure the connector. The first step is to access to the **Data Connectors** in the compliance portal The second step is to configure the CellTrust connector on the Veritas Merge1 site. For information about how to configure the CellTrust connector, see [Merge1 Third-Party Connectors User Guide](https://docs.ms.merge1.globanetportal.com/Merge1%20Third-Party%20Connectors%20CellTrust%20User%20Guide%20.pdf). -After you click **Save & Finish**, the **User mapping** page in the connector wizard in the compliance portal is displayed. +After you select **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 set up in the compliance portal, follow 1. On the **Map CellTrust users to Microsoft 365 users** page, enable automatic user mapping. The CellTrust 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. +2. Select **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 CellTrust connector After you create the CellTrust connector, you can view the connector status in the compliance portal. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and click **Data connectors** in the left nav. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and select **Data connectors** in the left nav. -2. Click the **Connectors** tab and then select the **CellTrust** connector to display the flyout page, which contains the properties and information about the connector. +2. Select the **Connectors** tab and then select the **CellTrust** connector to display the flyout page, which 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](data-connector-admin-logs.md). +3. 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](data-connector-admin-logs.md). ## Known issues |
| compliance | Archive Ciscojabberonmssql Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-ciscojabberonmssql-data.md | The following overview explains the process of using a connector to archive Cisc - The user who creates the Cisco Jabber 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](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- 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.+- 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 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 the Cisco Jabber on MS SQL connector The first step is to access to the **Data Connectors** in the compliance portal and create a connector for Cisco Jabber on MS SQL data. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/)and then click **Data connectors** > **Cisco Jabber on MS SQL**. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/)and then select **Data connectors** > **Cisco Jabber on MS SQL**. -2. On the **Cisco Jabber on MS SQL** product description page, click **Add connector**. +2. On the **Cisco Jabber on MS SQL** product description page, select **Add connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. Enter a unique name that identifies the connector and then click **Next**. +4. Enter a unique name that identifies the connector and then select **Next**. 5. Sign in to your Merge1 account to configure the connector. The first step is to access to the **Data Connectors** in the compliance portal The second step is to configure the Cisco Jabber on MS SQL connector on the Veritas Merge1 site. For information about how to configure the Cisco Jabber on MS SQL connector, see [Merge1 Third-Party Connectors User Guide](https://docs.ms.merge1.globanetportal.com/Merge1%20Third-Party%20Connectors%20Cisco%20Jabber%20on%20MS%20SQL%20User%20Guide%20.pdf). -After you click **Save & Finish**, the **User mapping** page in the connector wizard in the compliance portal is displayed. +After you select **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 set up in the compliance portal, follow 1. On the **Map Cisco Jabber on MS SQL users to Microsoft 365 users** page, enable automatic user mapping. The Cisco Jabber on MS SQL 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. +2. Select **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 Cisco Jabber connector After you create the Cisco Jabber on MS SQL connector, you can view the connector status in the compliance portal. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com) and click **Data connectors** in the left nav. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com) and select **Data connectors** in the left nav. -2. Click the **Connectors** tab and then select the **Cisco Jabber on MS SQL** connector to display the flyout page. This page contains the properties and information about the connector. +2. Select the **Connectors** tab and then select the **Cisco Jabber on MS SQL** 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](data-connector-admin-logs.md). +3. 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](data-connector-admin-logs.md). ## Known issues |
| compliance | Archive Ciscojabberonoracle Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-ciscojabberonoracle-data.md | The following overview explains the process of using a connector to archive the - The user who creates the Cisco Jabber on Oracle 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](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- 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.+- 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 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 the Cisco Jabber on Oracle connector The first step is to access to the **Data Connectors** page in the compliance portal and create a connector for Jabber data. -1. Go to <https://compliance.microsoft.com> and then click **Data connectors** > **Cisco Jabber on Oracle**. +1. Go to <https://compliance.microsoft.com> and then select **Data connectors** > **Cisco Jabber on Oracle**. -2. On the **Cisco Jabber on Oracle** product description page, click **Add connector**. +2. On the **Cisco Jabber on Oracle** product description page, select **Add connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. Enter a unique name that identifies the connector, and then click **Next**. +4. Enter a unique name that identifies the connector, and then select **Next**. 5. Sign in to your Merge1 account to configure the connector. The first step is to access to the **Data Connectors** page in the compliance po The second step is to configure the Cisco Jabber on Oracle connector on the Veritas Merge1 site. For information about how to configure the Cisco Jabber on Oracle connector, see [Merge1 Third-Party Connectors User Guide](https://docs.ms.merge1.globanetportal.com/Merge1%20Third-Party%20Connectors%20Cisco%20Jabber%20on%20Oracle%20User%20Guide.pdf). -After you click **Save & Finish**, the **User mapping** page in the connector wizard in the compliance portal is displayed. +After you select **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 compliance portal, follow t 1. On the **Map Cisco Jabber on Oracle users to Microsoft 365 users** page, enable automatic user mapping. The Cisco Jabber on Oracle 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 then go to the **Data connectors** page to see the progress of the import process for the new connector. +2. Select **Next**, review your settings, and then go to the **Data connectors** page to see the progress of the import process for the new connector. ## Step 4: Monitor the Cisco Jabber on Oracle connector After you create the Cisco Jabber on Oracle 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. +1. Go to <https://compliance.microsoft.com/> and select **Data connectors** in the left nav. -2. Click the **Connectors** tab and then select the **Cisco Jabber on Oracle** connector to display the flyout page, which contains the properties and information about the connector. +2. Select the **Connectors** tab and then select the **Cisco Jabber on Oracle** connector to display the flyout page, which 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](data-connector-admin-logs.md). +3. 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](data-connector-admin-logs.md). ## Known issues |
| compliance | Archive Ciscojabberonpostgresql Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-ciscojabberonpostgresql-data.md | The following overview explains the process of using a connector to archive the - The user who creates the Cisco Jabber on PostgreSQL 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](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- 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.+- 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 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 the Cisco Jabber on PostgreSQL connector The first step is to access to the **Data Connectors** page in the compliance portal and create a connector for Jabber data. -1. Go to <https://compliance.microsoft.com> and then click **Data connectors** > **Cisco Jabber on PostgreSQL**. +1. Go to <https://compliance.microsoft.com> and then select **Data connectors** > **Cisco Jabber on PostgreSQL**. -2. On the **Cisco Jabber on PostgreSQL** product description page, click **Add connector**. +2. On the **Cisco Jabber on PostgreSQL** product description page, select **Add connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. Enter a unique name that identifies the connector, and then click **Next**. +4. Enter a unique name that identifies the connector, and then select **Next**. 5. Sign in to your Merge1 account to configure the connector. The first step is to access to the **Data Connectors** page in the compliance po The second step is to configure the Cisco Jabber on PostgreSQL connector on the Veritas Merge1 site. For information about how to configure the Cisco Jabber on PostgreSQL connector, see [Merge1 Third-Party Connectors User Guide](https://docs.ms.merge1.globanetportal.com/Merge1%20Third-Party%20Connectors%20Cisco%20Jabber%20on%20PostgreSQL%20User%20Guide.pdf). -After you click **Save & Finish**, the **User mapping** page in the connector wizard in the compliance portal is displayed. +After you select **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 compliance portal, follow t 1. On the **Map Cisco Jabber on PostgreSQL users to Microsoft 365 users** page, enable automatic user mapping. The Cisco Jabber on PostgreSQL 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 then go to the **Data connectors** page to see the progress of the import process for the new connector. +2. Select **Next**, review your settings, and then go to the **Data connectors** page to see the progress of the import process for the new connector. ## Step 4: Monitor the Cisco Jabber on PostgreSQL connector After you create the Cisco Jabber on PostgreSQL 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. +1. Go to <https://compliance.microsoft.com/> and select **Data connectors** in the left nav. -2. Click the **Connectors** tab and then select the **Cisco Jabber on PostgreSQL** connector to display the flyout page, which contains the properties and information about the connector. +2. Select the **Connectors** tab and then select the **Cisco Jabber on PostgreSQL** connector to display the flyout page, which 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](data-connector-admin-logs.md). +3. 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](data-connector-admin-logs.md). ## Known issues |
| compliance | Archive Data From Celltrustsl2 | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-data-from-celltrustsl2.md | CellTrust's SL2 platform captures communication data from multiple sources. SL2 - The user who creates the CellTrust SL2 data 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 Microsoft Purview 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](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- This CellTrust 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 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.+- This CellTrust 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: Create a CellTrust SL2 connector The first step is to create a data connector in the compliance portal. -1. Go to <https://compliance.microsoft.com> and click **Data connectors** on the left navigation pane. +1. Go to <https://compliance.microsoft.com> and select **Data connectors** on the left navigation pane. -2. On the **Overview** tab, click **Filter** and select **By CellTrust**, and then apply the filter. +2. On the **Overview** tab, select **Filter** and select **By CellTrust**, and then apply the filter.  -3. Click **CellTrust SL2 (preview)**. +3. Select **CellTrust SL2 (preview)**. -4. On the **CellTrust SL2 (preview)** product description page, click **Add connector**. +4. On the **CellTrust SL2 (preview)** product description page, select **Add connector**. -5. On the **Terms of service** page, click **Accept**. +5. On the **Terms of service** page, select **Accept**. -6. Enter a unique name that identifies the connector and then click **Next**. The name you enter will identify the connector on the **Data connectors** page after you create it. +6. Enter a unique name that identifies the connector and then select **Next**. The name you enter will identify the connector on the **Data connectors** page after you create it. -7. On the **Sign in to your CellTrust account** page, click **Sign into CellTrust**. You'll be redirected to the **CellTrust Portal for Microsoft 365** in a new browser window. +7. On the **Sign in to your CellTrust account** page, select **Sign into CellTrust**. You'll be redirected to the **CellTrust Portal for Microsoft 365** in a new browser window. ## Step 2: Select the domains or OUs to archive The last step is to map users and complete the connector setup in the compliance 1. On the **User mapping** page, select **Enable automatic user mapping** if the email address for users is the same in both SL2 and Microsoft 365. Otherwise, you should manually user email addresses by uploading a CSV file that maps users' SL2 address to their Microsoft 365 address. -2. Click **Next**, review your settings, and then click **Finish** to create the connector. +2. Select **Next**, review your settings, and then select **Finish** to create the connector. The new connector is added to the list on the **Data connectors** page. |
| compliance | Archive Eml Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-eml-data.md | The following overview explains the process of using a connector to archive EML - The user who creates the EML 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](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- 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.+- 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 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 an EML Connector The first step is to access to the **Data Connectors** page in the compliance portal and create a connector for EML data. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and then click **Data connectors** > **EML**. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and then select **Data connectors** > **EML**. -2. On the **EML** product description page, click **Add connector**. +2. On the **EML** product description page, select **Add connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. Enter a unique name that identifies the connector, and then click **Next**. +4. Enter a unique name that identifies the connector, and then select **Next**. 5. Sign in to your Merge1 account to configure the connector. The first step is to access to the **Data Connectors** page in the compliance po The second step is to configure the EML connector on the Veritas Merge1 site. For information about configuring the EML connector, see [Merge1 Third-Party Connectors User Guide](https://docs.ms.merge1.globanetportal.com/Merge1%20Third-Party%20Connectors%20EML%20User%20Guide%20.pdf). -After you click **Save & Finish**, the **User mapping** page in the connector wizard in the compliance portal is displayed. +After you select **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 compliance portal, follow t 1. On the **Map external users to Microsoft 365 users** page, enable automatic user mapping. The EML source 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 EML items are imported to that userΓÇÖs mailbox. -2. Click **Next**, review your settings, and then go to the **Data connectors** page to see the progress of the import process for the new connector. +2. Select **Next**, review your settings, and then go to the **Data connectors** page to see the progress of the import process for the new connector. ## Step 4: Monitor the EML connector After you create the EML connector, you can view the connector status in the compliance portal. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com) and click **Data connectors** in the left nav. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com) and select **Data connectors** in the left nav. -2. Click the **Connectors** tab and then select the **EML** connector to display the flyout page. This page contains the properties and information about the connector. +2. Select the **Connectors** tab and then select the **EML** 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](data-connector-admin-logs.md). +3. 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](data-connector-admin-logs.md). ## Known issues |
| compliance | Archive Enterprise Number Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-enterprise-number-data.md | Some of the implementation steps required to archive Enterprise Number Archiver - The user who creates a Enterprise Number Archiver connector 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](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- This TeleMessage 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 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.+- This TeleMessage 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. ## Create an Enterprise Number Archiver connector After you've completed the prerequisites described in the previous section, you can create an Enterprise Number Archiver connector in the compliance portal. The connector uses the information you provide to connect to the TeleMessage site and transfer SMS, MMS, and voice call messages to the corresponding user mailbox boxes in Microsoft 365. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and then click **Data connectors** \> **Enterprise Number Archiver**. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and then select **Data connectors** \> **Enterprise Number Archiver**. -2. On the **Enterprise Number Archiver** product description page, click **Add connector** +2. On the **Enterprise Number Archiver** product description page, select **Add connector** -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. On the **Login to TeleMessage** page, under Step 3, enter the required information in the following boxes and then click **Next**. +4. On the **Login to TeleMessage** page, under Step 3, enter the required information in the following boxes and then select **Next**. - **Username:** Your TeleMessage username. After you've completed the prerequisites described in the previous section, you 5. After the connector is created, you can close the pop-up window and go to the next page. -6. On the **User mapping** page, enable automatic user mapping. To enable custom mapping, upload a CSV file that contains the user mapping information, and then click **Next**. +6. On the **User mapping** page, enable automatic user mapping. To enable custom mapping, upload a CSV file that contains the user mapping information, and then select **Next**. -7. Review your settings, and then click **Finish** to create the connector. +7. Review your settings, and then select **Finish** to create the connector. 8. Go to the Connectors tab in **Data connectors** page to see the progress of the import process for the new connector. |
| compliance | Archive Fxconnect Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-fxconnect-data.md | The following overview explains the process of using a connector to archive the - The user who creates the FX Connect 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](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- 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.+- 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 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 the FX Connect connector The first step is to access to the **Data Connectors** page in the compliance portal and create a connector for FX Connect data. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and then click **Data connectors** > **FX Connect**. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and then select **Data connectors** > **FX Connect**. -2. On the **FX Connect** product description page, click **Add connector**. +2. On the **FX Connect** product description page, select **Add connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. Enter a unique name that identifies the connector, and then click **Next**. +4. Enter a unique name that identifies the connector, and then select **Next**. 5. Sign in to your Merge1 account to configure the connector. The first step is to access to the **Data Connectors** page in the compliance po The second step is to configure the FX Connect connector on the Merge1 site. For information about how to configure the FX Connect connector, see [Merge1 Third-Party Connectors User Guide](https://docs.ms.merge1.globanetportal.com/Merge1%20Third-Party%20Connectors%20FX%20Connect%20User%20Guide%20.pdf). -After you click **Save & Finish**, the **User mapping** page in the connector wizard in the compliance portal is displayed. +After you select **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 compliance portal, follow t 1. On the **Map FX Connect users to Microsoft 365 users** page, enable automatic user mapping. The FX Connect 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 then go to the **Data connectors** page to see the progress of the import process for the new connector. +2. Select **Next**, review your settings, and then go to the **Data connectors** page to see the progress of the import process for the new connector. ## Step 4: Monitor the FX Connect connector After you create the FX Connect 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. +1. Go to <https://compliance.microsoft.com/> and select **Data connectors** in the left nav. -2. Click the **Connectors** tab and then select the **FX Connect** connector to display the flyout page. This page contains the properties and information about the connector. +2. Select the **Connectors** tab and then select the **FX Connect** 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](data-connector-admin-logs.md). +3. 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](data-connector-admin-logs.md). ## Known issues |
| compliance | Archive Icechat Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-icechat-data.md | The steps in this section show you how to set up an ICE Chat connector using the The first step is to obtain a copy of the public keys for Pretty Good Privacy (PGP) and Secure Shell (SSH). You use these keys in Step 2 to configure the ICE Chat SFTP site to allow the connector (that you create in Step 3) to connect to the SFTP site and transfer the ICE Chat data to Microsoft 365 mailboxes. You will also obtain an IP address in this step, which you use when configuring the ICE Chat SFTP site. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com) and click **Data connectors** in the left nav. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com) and select **Data connectors** in the left nav. -2. On the **Data connectors** page under **ICE Chat**, click **View**. +2. On the **Data connectors** page under **ICE Chat**, select **View**. -3. On the **ICE Chat** page, click **Add connector**. +3. On the **ICE Chat** page, select **Add connector**. -4. On the **Terms of service** page, click **Accept**. +4. On the **Terms of service** page, select **Accept**. -5. On the **Add credentials for content source** page, click **I want to use PGP and SSH public keys provided by Microsoft**. +5. On the **Add credentials for content source** page, select **I want to use PGP and SSH public keys provided by Microsoft**.  -6. Under step 1, click the **Download SSH key**, **Download PGP key**, and **Download IP address** links to save a copy of each file to your local computer. +6. Under step 1, select the **Download SSH key**, **Download PGP key**, and **Download IP address** links to save a copy of each file to your local computer.  The first step is to obtain a copy of the public keys for Pretty Good Privacy (P - IP address: The ICE Chat SFTP site is configured to accept a connection request only from this IP address, which is used by the ICE Chat connector that you create in Step 3. -7. Click **Cancel** to close the wizard. You come back to this wizard in Step 3 to create the connector. +7. Select **Cancel** to close the wizard. You come back to this wizard in Step 3 to create the connector. ### Step 2: Configure the ICE Chat SFTP site The next step is to use the PGP and SSH public keys and the IP address that you The last step is to create an ICE Chat connector in the compliance portal. The connector uses the information you provide to connect to the ICE Chat SFTP site and transfer chat messages to the corresponding user mailbox boxes in Microsoft 365. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com) and click **Data connectors** in the left nav. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com) and select **Data connectors** in the left nav. -2. On the **Data connectors** page under **ICE Chat**, click **View**. +2. On the **Data connectors** page under **ICE Chat**, select **View**. -3. On the **ICE Chat** page, click **Add connector**. +3. On the **ICE Chat** page, select **Add connector**. -4. On the **Terms of service** page, click **Accept**. +4. On the **Terms of service** page, select **Accept**. -5. On the **Add credentials for content source** page, click **I want to use PGP and SSH public keys**. +5. On the **Add credentials for content source** page, select **I want to use PGP and SSH public keys**. -6. Under Step 3, enter the required information in the following boxes and then click **Validate connection**. +6. Under Step 3, enter the required information in the following boxes and then select **Validate connection**. - **Firm code:** The ID for your organization, which is used as the username for the ICE Chat SFTP site. The last step is to create an ICE Chat connector in the compliance portal. The c - **SFTP port:** The port number for the ICE Chat SFTP site. The connector uses this port to connect to the SFTP site. -7. After the connection is successfully validated, click **Next**. +7. After the connection is successfully validated, select **Next**. 8. On the **Define user** page, specify the users to import data for. The last step is to create an ICE Chat connector in the compliance portal. The c > [!NOTE] > As previously explained, custom mapping file CSV file contains the ICE Chat imid and corresponding Microsoft 365 mailbox address for each user. If you enable automatic user mapping and provide a custom mapping, for every chat item, the connector will first look at custom mapping file. If it doesn't find a valid Microsoft 365 user that corresponds to a user's ICE Chat imid, the connector will import the item to the mailboxes for the users specified in the *SenderEmail* and *RecipientEmail* properties of the chat item. If the connector doesn't find a valid Microsoft 365 user by either automatic or custom user mapping, the item won't be imported. -10. Click **Next**, review your settings, and then click **Finish** to create the connector. +10. Select **Next**, review your settings, and then select **Finish** to create the connector. 11. Go to the **Data connectors** page to see the progress of the import process for the new connector. If your organization has used PGP and SSH private keys to set up an ICE Chat SFT To obtain the IP address: -1. Go to <https://compliance.microsoft.com> and click **Data connectors** in the left nav. +1. Go to <https://compliance.microsoft.com> and select **Data connectors** in the left nav. -2. On the **Data connectors** page under **ICE Chat**, click **View**. +2. On the **Data connectors** page under **ICE Chat**, select **View**. -3. On the **ICE Chat** product description page, click **Add connector** +3. On the **ICE Chat** product description page, select **Add connector** -4. On the **Terms of service** page, click **Accept**. +4. On the **Terms of service** page, select **Accept**. -5. On the **Add credentials for content source** page, click **I want to use PGP and SSH private keys**. +5. On the **Add credentials for content source** page, select **I want to use PGP and SSH private keys**.  -6. Under step 1, click **Download IP address** to save a copy of the IP address file to your local computer. +6. Under step 1, select **Download IP address** to save a copy of the IP address file to your local computer.  -7. Click **Cancel** to close the wizard. You come back to this wizard in Step 2 to create the connector. +7. Select **Cancel** to close the wizard. You come back to this wizard in Step 2 to create the connector. You need to work with ICE Chat customer support to configure your ICE Chat SFTP site to accept connection requests from this IP address. You need to work with ICE Chat customer support to configure your ICE Chat SFTP After your ICE Chat SFTP site is configured, the next step is to create an ICE Chat connector in the compliance portal. The connector uses the information you provide to connect to the ICE Chat SFTP site and transfer email messages to the corresponding user mailbox boxes in Microsoft 365. To complete this step, be sure to have copies of the same private keys and key passphrases that you used to set up your ICE Chat SFTP site. -1. Go to <https://compliance.microsoft.com> and click **Data connectors** in the left nav. +1. Go to <https://compliance.microsoft.com> and select **Data connectors** in the left nav. -2. On the **Data connectors** page under **ICE Chat**, click **View**. +2. On the **Data connectors** page under **ICE Chat**, select **View**. -3. On the **ICE Chat** product description page, click **Add connector** +3. On the **ICE Chat** product description page, select **Add connector** -4. On the **Terms of service** page, click **Accept**. +4. On the **Terms of service** page, select **Accept**. -5. On the **Add credentials for content source** page, click **I want to use PGP and SSH private keys**. +5. On the **Add credentials for content source** page, select **I want to use PGP and SSH private keys**. -6. Under Step 3, enter the required information in the following boxes and then click **Validate connection**. +6. Under Step 3, enter the required information in the following boxes and then select **Validate connection**. - **Name:** The name for the connector. It must be unique in your organization. After your ICE Chat SFTP site is configured, the next step is to create an ICE C - **SSH key passphrase:** The passphrase for the SSH private key. -7. After the connection is successfully validated, click **Next**. +7. After the connection is successfully validated, select **Next**. 8. On the **Define user** page, specify the users to import data for. After your ICE Chat SFTP site is configured, the next step is to create an ICE C > [!NOTE] > As previously explained, custom mapping file CSV file contains the ICE Chat imid and corresponding Microsoft 365 mailbox address for each user. If you enable automatic user mapping and provide a custom mapping, for every chat item, the connector will first look at custom mapping file. If it doesn't find a valid Microsoft 365 user that corresponds to a user's ICE Chat imid, the connector will import the item to the mailboxes for the users specified in the *SenderEmail* and *RecipientEmail* properties of the chat item. If the connector doesn't find a valid Microsoft 365 user by either automatic or custom user mapping, the item won't be imported. -10. Click **Next**, review your settings, and then click **Finish** to create the connector. +10. Select **Next**, review your settings, and then select **Finish** to create the connector. -11. Go to the **Data connectors** page to see the progress of the import process for the new connector. Click the connector to display the flyout page, which contains information about the connector. +11. Go to the **Data connectors** page to see the progress of the import process for the new connector. Select the connector to display the flyout page, which contains information about the connector. |
| compliance | Archive Instant Bloomberg Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-instant-bloomberg-data.md | The steps in this section show you how to set up an Instant Bloomberg connector The first step is to obtain a copy of the public keys for Pretty Good Privacy (PGP) and Secure Shell (SSH). You use these keys in Step 2 to configure the Bloomberg SFTP site to allow the connector (that you create in Step 3) to connect to the SFTP site and transfer the Instant Bloomberg chat data to Microsoft 365 mailboxes. You also obtain an IP address in this step, which you use when configuring the Bloomberg SFTP site. -1. Go to <https://compliance.microsoft.com> and click **Data connectors** in the left nav. +1. Go to <https://compliance.microsoft.com> and select **Data connectors** in the left nav. -2. On the **Data connectors** page under **Instant Bloomberg**, click **View**. +2. On the **Data connectors** page under **Instant Bloomberg**, select **View**. -3. On the **Instant Bloomberg** product description page, click **Add connector** +3. On the **Instant Bloomberg** product description page, select **Add connector** -4. On the **Terms of service** page, click **Accept**. +4. On the **Terms of service** page, select **Accept**. -5. On the **Add credentials for content source** page, click **I want to use PGP and SSH public keys provided by Microsoft**. +5. On the **Add credentials for content source** page, select **I want to use PGP and SSH public keys provided by Microsoft**.  -6. Under step 1, click the **Download SSH key**, **Download PGP key**, and **Download IP address** links to save a copy of each file to your local computer. +6. Under step 1, select the **Download SSH key**, **Download PGP key**, and **Download IP address** links to save a copy of each file to your local computer.  The first step is to obtain a copy of the public keys for Pretty Good Privacy (P - IP address: The Bloomberg SFTP site is configured to accept connection requests from this IP address. The same IP address is used by the Instant Bloomberg connector to connect to the SFTP site and transfer Instant Bloomberg data to Microsoft 365. -7. Click **Cancel** to close the wizard. You come back to this wizard in Step 3 to create the connector. +7. Select **Cancel** to close the wizard. You come back to this wizard in Step 3 to create the connector. ### Step 2: Configure the Bloomberg SFTP site The next step is to use the PGP and SSH public keys and the IP address that you The last step is to create an Instant Bloomberg connector in the compliance portal. The connector uses the information you provide to connect to the Bloomberg SFTP site and transfer chat messages to the corresponding user mailbox boxes in Microsoft 365. -1. Go to <https://compliance.microsoft.com> and then click **Data connectors** > **Instant Bloomberg**. +1. Go to <https://compliance.microsoft.com> and then select **Data connectors** > **Instant Bloomberg**. -2. On the **Instant Bloomberg** product description page, click **Add connector** +2. On the **Instant Bloomberg** product description page, select **Add connector** -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. On the **Add credentials for Bloomberg SFTP site** page, under Step 3, enter the required information in the following boxes and then click **Next**. +4. On the **Add credentials for Bloomberg SFTP site** page, under Step 3, enter the required information in the following boxes and then select **Next**. - **Firm code:** The ID for your organization that is used as the username for the Bloomberg SFTP site. The last step is to create an Instant Bloomberg connector in the compliance port > [!NOTE] > The connector imports the chat message items to the mailbox of a specific user. A new folder named **InstantBloomberg** is created in the specific user's mailbox and the items will be imported to it. The connector does by using the value of the *CorporateEmailAddress* property. Every chat message contains this property, and the property is populated with the email address of every participant of the chat message. In addition to automatic user mapping using the value of the *CorporateEmailAddress* property, you can also define custom mapping by uploading a CSV mapping file. The mapping file should contain the Bloomberg UUID and corresponding Microsoft 365 mailbox address for each user. If you enable automatic user mapping and provide a custom mapping, for every chat item the connector will first look at custom mapping file. If it doesn't find a valid Microsoft 365 user that corresponds to a user's Bloomberg UUID, the connector will use the *CorporateEmailAddress* property of the chat item. If the connector doesn't find a valid Microsoft 365 user in either the custom mapping file or the *CorporateEmailAddress* property of the chat item, the item won't be imported. -7. Click **Next**, review your settings, and then click **Finish** to create the connector. +7. Select **Next**, review your settings, and then select **Finish** to create the connector. -8. Go to the **Data connectors** page to see the progress of the import process for the new connector. Click the connector to display the flyout page, which contains information about the connector. +8. Go to the **Data connectors** page to see the progress of the import process for the new connector. Select the connector to display the flyout page, which contains information about the connector. ## Set up a connector using private keys If your organization has used PGP and SSH private keys to set up a Bloomberg SFT To obtain the IP address: -1. Go to <https://compliance.microsoft.com> and click **Data connectors** in the left nav. +1. Go to <https://compliance.microsoft.com> and select **Data connectors** in the left nav. -2. On the **Data connectors** page under **Instant Bloomberg**, click **View**. +2. On the **Data connectors** page under **Instant Bloomberg**, select **View**. -3. On the **Instant Bloomberg** product description page, click **Add connector** +3. On the **Instant Bloomberg** product description page, select **Add connector** -4. On the **Terms of service** page, click **Accept**. +4. On the **Terms of service** page, select **Accept**. -5. On the **Add credentials for content source** page, click **I want to use PGP and SSH private keys**. +5. On the **Add credentials for content source** page, select **I want to use PGP and SSH private keys**. -6. Under step 1, click **Download IP address** to save a copy of the IP address file to your local computer. +6. Under step 1, select **Download IP address** to save a copy of the IP address file to your local computer.  -7. Click **Cancel** to close the wizard. You come back to this wizard in Step 2 to create the connector. +7. Select **Cancel** to close the wizard. You come back to this wizard in Step 2 to create the connector. You need to work with Bloomberg customer support to configure your Bloomberg SFTP site to accept connection requests from this IP address. Contact [Bloomberg customer support](https://service.bloomberg.com/portal/sessions/new?utm_source=bloomberg-menu&utm_medium=csc) for assistance. You need to work with Bloomberg customer support to configure your Bloomberg SFT After your Bloomberg SFTP site is configured, the next step is to create an Instant Bloomberg connector in the compliance portal. The connector uses the information you provide to connect to the Bloomberg SFTP site and transfer email messages to the corresponding user mailbox boxes in Microsoft 365. To complete this step, be sure to have copies of the same private keys and key passphrases that you used to set up your Bloomberg SFTP site. -1. Go to <https://compliance.microsoft.com> and click **Data connectors** in the left nav. +1. Go to <https://compliance.microsoft.com> and select **Data connectors** in the left nav. -2. On the **Data connectors** page under **Instant Bloomberg**, click **View**. +2. On the **Data connectors** page under **Instant Bloomberg**, select **View**. -3. On the **Instant Bloomberg** product description page, click **Add connector** +3. On the **Instant Bloomberg** product description page, select **Add connector** -4. On the **Terms of service** page, click **Accept**. +4. On the **Terms of service** page, select **Accept**. -5. On the **Add credentials for content source** page, click **I want to use PGP and SSH private keys**. +5. On the **Add credentials for content source** page, select **I want to use PGP and SSH private keys**.  -6. Under Step 3, enter the required information in the following boxes and then click **Validate connection**. +6. Under Step 3, enter the required information in the following boxes and then select **Validate connection**. - **Name:** The name for the connector. It must be unique in your organization. After your Bloomberg SFTP site is configured, the next step is to create an Inst - **SSH key passphrase:** The passphrase for the SSH private key. -7. After the connection is successfully validated, click **Next**. +7. After the connection is successfully validated, select **Next**. 8. On the **Define user** page, select one of the following options to specify the users whose data you want to import. After your Bloomberg SFTP site is configured, the next step is to create an Inst > [!NOTE] > The connector imports the chat message items to the mailbox of a specific user. A new folder named **InstantBloomberg** is created in the specific user's mailbox and the items will be imported to it. The connector does by using the value of the *CorporateEmailAddress* property. Every chat message contains this property, and the property is populated with the email address of every participant of the chat message. In addition to automatic user mapping using the value of the *CorporateEmailAddress* property, you can also define custom mapping by uploading a CSV mapping file. The mapping file should contain the Bloomberg UUID and corresponding Microsoft 365 mailbox address for each user. If you enable automatic user mapping and provide a custom mapping, for every chat item the connector will first look at custom mapping file. If it doesn't find a valid Microsoft 365 user that corresponds to a user's Bloomberg UUID, the connector will use the *CorporateEmailAddress* property of the chat item. If the connector doesn't find a valid Microsoft 365 user in either the custom mapping file or the *CorporateEmailAddress* property of the chat item, the item won't be imported. -10. Click **Next**, review your settings, and then click **Finish** to create the connector. +10. Select **Next**, review your settings, and then select **Finish** to create the connector. -11. Go to the **Data connectors** page to see the progress of the import process for the new connector. Click the connector to display the flyout page, which contains information about the connector. +11. Go to the **Data connectors** page to see the progress of the import process for the new connector. Select the connector to display the flyout page, which contains information about the connector. |
| compliance | Archive Linkedin Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-linkedin-data.md | After the LinkedIn Company page data is stored in a mailbox, you can apply Micro ## Create a LinkedIn connector -1. Go to <https://compliance.microsoft.com> and then click **Data connectors** > **LinkedIn Company pages**. +1. Go to <https://compliance.microsoft.com> and then select **Data connectors** > **LinkedIn Company pages**. -2. On the **LinkedIn company pages** product page, click **Add connector**. +2. On the **LinkedIn company pages** product page, select **Add connector**. 3. On the **Terms of service** page, select **Accept**. -4. On the **Sign in with LinkedIn** page, click **Sign in with LinkedIn**. +4. On the **Sign in with LinkedIn** page, select **Sign in with LinkedIn**. The LinkedIn sign-in page is displayed.  -5. On the LinkedIn sign in page, enter the email address (or phone number) and password for the LinkedIn account associated with the company page that you want to archive, and then click **Sign in**. +5. On the LinkedIn sign in page, enter the email address (or phone number) and password for the LinkedIn account associated with the company page that you want to archive, and then select **Sign in**. A wizard page is displayed with a list of all LinkedIn Company Pages associated with the account that you signed in to. A connector can only be configured for one company page. If your organization has multiple LinkedIn Company Pages, you have to create a connector for each one.  -6. Select the company page that you want to archive items from, and then click **Next**. +6. Select the company page that you want to archive items from, and then select **Next**. -7. On the **Choose storage location** page, click in the box, select the email address of a Microsoft 365 mailbox that the LinkedIn items will be imported to, and then click **Next**. Items are imported to the inbox folder in this mailbox. The mailbox used must have an Exchange Online Plan 1 or Plan 2 license. +7. On the **Choose storage location** page, select in the box, select the email address of a Microsoft 365 mailbox that the LinkedIn items will be imported to, and then select **Next**. Items are imported to the inbox folder in this mailbox. The mailbox used must have an Exchange Online Plan 1 or Plan 2 license. -8. Click **Next** to review the connector settings and then click **Finish** to complete the connector setup. +8. Select **Next** to review the connector settings and then select **Finish** to complete the connector setup. After you create the connector, you can go back to the **Data connectors** page to see the progress of the import process for the new connector (select **Refresh** if necessary to update the list of connectors). The value in the **Status** column is **Waiting to start**. It takes up to 24 hours for the initial import process to be started. After the first time the connector runs and imports the LinkedIn items, the connector will run once every 24 hours and import any new items that are created on the LinkedIn Company Page in the previous 24 hours. |
| compliance | Archive Mssqldatabaseimporter Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-mssqldatabaseimporter-data.md | The following overview explains the process of using a connector to archive MS S - The user who creates the MS SQL Database Importer 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](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- 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.+- 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 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 the MS SQL Database Importer connector The first step is to access to the **Data Connectors** page in the compliance portal and create a connector for the MS SQL Database. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com) and then click **Data connectors** > **MS SQL Database Importer**. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com) and then select **Data connectors** > **MS SQL Database Importer**. -2. On the **MS SQL Database Importer** product description page, click **Add new connector**. +2. On the **MS SQL Database Importer** product description page, select **Add new connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. Enter a unique name that identifies the connector, and then click **Next**. +4. Enter a unique name that identifies the connector, and then select **Next**. 5. Sign in to your Merge1 account to configure the connector. The first step is to access to the **Data Connectors** page in the compliance po The second step is to configure the MS SQL Database Importer connector on the Merge1 site. For information about how to configure the MS SQL Database Importer, see [Merge1 Third-Party Connectors User Guide](https://docs.ms.merge1.globanetportal.com/Merge1%20Third-Party%20Connectors%20MS%20SQL%20Database%20Importer%20User%20Guide%20.pdf). -After you click **Save & Finish**, the **User mapping** page in the connector wizard in the compliance portal is displayed. +After you select **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, follow these steps: 1. On the **Map MS SQL Database Importer users to Microsoft 365 users** page, enable automatic user mapping. The MS SQL Database 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. +2. Select **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 MS SQL Database Importer connector After you create the MS SQL Database Importer 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. +1. Go to <https://compliance.microsoft.com/> and select **Data connectors** in the left nav. -2. Click the **Connectors** tab and then select the **MS SQL Database** **Importer** connector to display the flyout page, which contains the properties and information about the connector. +2. Select the **Connectors** tab and then select the **MS SQL Database** **Importer** connector to display the flyout page, which 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](data-connector-admin-logs.md). +3. 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](data-connector-admin-logs.md). ## Known issues |
| compliance | Archive O2 Network Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-o2-network-data.md | Some of the implementation steps required to archive O2 Network data are externa - The user who creates an O2 Network connector 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](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- This TeleMessage 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 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.+- This TeleMessage 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. ## Create an O2 Network connector After you've completed the prerequisites described in the previous section, you can create an O2 Network connector in the compliance portal. The connector uses the information you provide to connect to the TeleMessage site and transfer SMS messages and voice calls to the corresponding user mailbox boxes in Microsoft 365. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and then click **Data connectors** \> **O2 Network**. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and then select **Data connectors** \> **O2 Network**. -2. On the **O2 Network** product description page, click **Add connector** +2. On the **O2 Network** product description page, select **Add connector** -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. On the **Login to TeleMessage** page, under Step 3, enter the required information in the following boxes and then click **Next**. +4. On the **Login to TeleMessage** page, under Step 3, enter the required information in the following boxes and then select **Next**. - **Username:** Your TeleMessage username. After you've completed the prerequisites described in the previous section, you 5. After the connector is created, you can close the pop-up window and go to the next page. -6. On the **User mapping** page, enable automatic user mapping and click **Next**. In case you need custom mapping upload a CSV file, and click **Next**. +6. On the **User mapping** page, enable automatic user mapping and select **Next**. In case you need custom mapping upload a CSV file, and select **Next**. -7. Review your settings, and then click **Finish** to create the connector. +7. Review your settings, and then select **Finish** to create the connector. 8. Go to the Connectors tab in **Data connectors** page to see the progress of the import process for the new connector. |
| compliance | Archive Pivot Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-pivot-data.md | The following overview explains the process of using a connector to archive the - 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](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- 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.+- 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 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 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](https://compliance.microsoft.com/) and then click **Data connectors** > **Pivot**. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and then select **Data connectors** > **Pivot**. -2. On the **Pivot** product description page, click **Add connector**. +2. On the **Pivot** product description page, select **Add connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. Enter a unique name that identifies the connector and then click **Next**. +4. Enter a unique name that identifies the connector and then select **Next**. 5. Sign in to your Merge1 account to configure the connector. The first step is to access to the **Data Connectors** page in the Microsoft com 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](https://docs.ms.merge1.globanetportal.com/Merge1%20Third-Party%20Connectors%20Pivot%20User%20Guide%20.pdf). -After you click **Save & Finish**, the **User mapping** page in the connector wizard in the compliance portal is displayed. +After you select **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 ce 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. +2. Select **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](https://compliance.microsoft.com) and click **Data connectors** in the left nav. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com) and select **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. +2. Select 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](data-connector-admin-logs.md). +3. 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](data-connector-admin-logs.md). ## Known issues |
| compliance | Archive Redtailspeak Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-redtailspeak-data.md | The following overview explains the process of using a connector to archive the - The user who creates the Redtail Speak Importer 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](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- 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.+- 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 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 the Redtail Speak connector |
| compliance | Archive Reutersdealing Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-reutersdealing-data.md | The following overview explains the process of using a connector to archive the - The user who creates the Reuters Dealing 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](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- 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.+- 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 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 the Reuters Dealing connector The first step is to access to the **Data Connectors** page in the Microsoft 365 and create a connector for Reuters Dealing data. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and then click **Data connectors** > **Reuters Dealing**. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and then select **Data connectors** > **Reuters Dealing**. -2. On the **Reuters Dealing** product description page, click **Add connector**. +2. On the **Reuters Dealing** product description page, select **Add connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. Enter a unique name that identifies the connector, and then click **Next**. +4. Enter a unique name that identifies the connector, and then select **Next**. 5. Sign to your Merge1 account to configure the connector. The first step is to access to the **Data Connectors** page in the Microsoft 365 The second step is to configure the Reuters Dealing connector on Veritas the Merge1 site. For information about configuring the Reuters Dealing connector, see [Merge1 Third-Party Connectors User Guide](https://docs.ms.merge1.globanetportal.com/Merge1%20Third-Party%20Connectors%20Reuters%20Dealing%20User%20Guide%20.pdf). -After you click **Save & Finish**, the **User mapping** page in the connector wizard in the compliance portal is displayed. +After you select **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 compliance portal, follow t Reuters Dealing 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. +2. Select **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 Reuters Dealing connector After you create the Reuters Dealing connector, you can view the connector status in the compliance portal. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and click **Data connectors** in the left nav. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and select **Data connectors** in the left nav. -2. Click the **Connectors** tab and then select the **Reuters Dealing** connector to display the flyout page, which contains the properties and information about the connector. +2. Select the **Connectors** tab and then select the **Reuters Dealing** connector to display the flyout page, which 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](data-connector-admin-logs.md). +3. 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](data-connector-admin-logs.md). ## Known issues |
| compliance | Archive Reuterseikon Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-reuterseikon-data.md | The following overview explains the process of using a connector to archive Reut - The user who creates the Reuters Eikon 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](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- 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.+- 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 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 the Reuters Eikon connector The first step is to access to the **Data Connectors** page in the compliance portal and create a connector for Reuters Eikon data. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and then click **Data connectors** > **Reuters Eikon**. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and then select **Data connectors** > **Reuters Eikon**. -2. On the **Reuters Eikon** product description page, click **Add connector**. +2. On the **Reuters Eikon** product description page, select **Add connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. Enter a unique name that identifies the connector, and then click **Next**. +4. Enter a unique name that identifies the connector, and then select **Next**. 5. Sign in to your Merge1 account to configure the connector. The first step is to access to the **Data Connectors** page in the compliance po The second step is to configure the Reuters Eikon connector on the Merge1 site. For information about how to configure the Reuters Eikon connector on the Veritas Merge1 site, see [Merge1 Third-Party Connectors User Guide](https://docs.ms.merge1.globanetportal.com/Merge1%20Third-Party%20Connectors%20Reuters%20Eikon%20User%20Guide%20.pdf). -After you click **Save & Finish**, the **User mapping** page in the connector wizard in the compliance portal is displayed. +After you select **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 compliance portal, follow t 1. On the **Map external users to Microsoft 365 users** page, enable automatic user mapping. The Reuters Eikon 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 then go to the **Data connectors** page to see the progress of the import process for the new connector. +2. Select **Next**, review your settings, and then go to the **Data connectors** page to see the progress of the import process for the new connector. ## Step 4: Monitor the Reuters Eikon connector After you create the Reuters Eikon connector, you can view the connector status in the compliance portal. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com) and click **Data connectors** in the left nav. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com) and select **Data connectors** in the left nav. -2. Click the **Connectors** tab and then select the **Reuters Eikon** connector to display the flyout page. This page contains the properties and information about the connector. +2. Select the **Connectors** tab and then select the **Reuters Eikon** 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](data-connector-admin-logs.md). +3. 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](data-connector-admin-logs.md). ## Known issues |
| compliance | Archive Reutersfx Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-reutersfx-data.md | The following overview explains the process of using a connector to archive Reut - The user who creates the Reuters FX 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](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- 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.+- 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 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 the Reuters FX connector The first step is to access to the **Data Connectors** page in the Microsoft 365 and create a connector for Reuters FX data. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and then click **Data connectors** > **Reuters FX**. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and then select **Data connectors** > **Reuters FX**. -2. On the **Reuters FX** product description page, click **Add connector**. +2. On the **Reuters FX** product description page, select **Add connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. Enter a unique name that identifies the connector, and then click **Next**. +4. Enter a unique name that identifies the connector, and then select **Next**. 5. Sign to your Merge1 account to configure the connector. The first step is to access to the **Data Connectors** page in the Microsoft 365 The second step is to configure the Reuters FX connector on the Veritas Merge1 site. For information about configuring the Reuters FX connector, see [Merge1 Third-Party Connectors User Guide](https://docs.ms.merge1.globanetportal.com/Merge1%20Third-Party%20Connectors%20Reuters%20FX%20User%20Guide%20.pdf). -After you click **Save & Finish**, the **User mapping** page in the connector wizard in the compliance portal is displayed. +After you select **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 compliance portal, follow t Reuters FX 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. +2. Select **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 Reuters FX connector After you create the Reuters FX 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. +1. Go to <https://compliance.microsoft.com/> and select **Data connectors** in the left nav. -2. Click the **Connectors** tab and then select the **Reuters FX** connector to display the flyout page, which contains the properties and information about the connector. +2. Select the **Connectors** tab and then select the **Reuters FX** connector to display the flyout page, which 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](data-connector-admin-logs.md). +3. 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](data-connector-admin-logs.md). ## Known issues |
| compliance | Archive Ringcentral Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-ringcentral-data.md | The following overview explains the process of using a connector to archive the - The user who creates the RingCentral 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](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- 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.+- 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 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 the RingCentral connector The first step is to access to the **Data Connectors** page in the compliance portal and create a connector for RingCentral data. -1. Go to <https://compliance.microsoft.com> and then click **Data connectors** > **RingCentral**. +1. Go to <https://compliance.microsoft.com> and then select **Data connectors** > **RingCentral**. -2. On the **RingCentral** product description page, click **Add connector**. +2. On the **RingCentral** product description page, select **Add connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. Enter a unique name that identifies the connector, and then click **Next**. +4. Enter a unique name that identifies the connector, and then select **Next**. 5. Sign in to your Merge1 account to configure the connector. The first step is to access to the **Data Connectors** page in the compliance po The second step is to configure the RingCentral connector on the Veritas Merge1 site. For information about how to configure the RingCentral connector, see [Merge1 Third-Party Connectors User Guide](https://docs.ms.merge1.globanetportal.com/Merge1%20Third-Party%20Connectors%20RingCentral%20User%20Guide.pdf). -After you click **Save & Finish,** the **User mapping** page in the connector wizard in the compliance portal is displayed. +After you select **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 compliance portal, follow t 1. On the **Map RingCentral users to Microsoft 365 users** page, enable automatic user mapping. The RingCentral 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 then go to the **Data connectors** page to see the progress of the import process for the new connector. +2. Select **Next**, review your settings, and then go to the **Data connectors** page to see the progress of the import process for the new connector. ## Step 4: Monitor the RingCentral connector After you create the RingCentral 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. +1. Go to <https://compliance.microsoft.com/> and select **Data connectors** in the left nav. -2. Click the **Connectors** tab and then select the **RingCentral** connector to display the flyout page, which contains the properties and information about the connector. +2. Select the **Connectors** tab and then select the **RingCentral** connector to display the flyout page, which 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](data-connector-admin-logs.md). +3. 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](data-connector-admin-logs.md). ## Known issues |
| compliance | Archive Rogers Network Archiver Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-rogers-network-archiver-data.md | The following overview explains the process of using a connector to archive Roge - The user who creates a Rogers Network Archiver connector 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](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- This TeleMessage 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 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.+- This TeleMessage 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. ## Create a Rogers Network Archiver connector After you've completed the prerequisites described in the previous section, you can create the Rogers Network Archiver connector in the compliance portal. The connector uses the information you provide to connect to the TeleMessage site and transfer Rogers SMS/MMS data to the corresponding user mailbox boxes in Microsoft 365. -1. Go to <https://compliance.microsoft.com> and then click **Data connectors** > **Rogers Network Archiver**. +1. Go to <https://compliance.microsoft.com> and then select **Data connectors** > **Rogers Network Archiver**. -2. On the **Rogers Network Archiver** product description page, click **Add connector**. +2. On the **Rogers Network Archiver** product description page, select **Add connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. On the **Login to TeleMessage** page, under Step 3, enter the required information in the following boxes and then click **Next**. +4. On the **Login to TeleMessage** page, under Step 3, enter the required information in the following boxes and then select **Next**. - **Username:** Your TeleMessage username. After you've completed the prerequisites described in the previous section, you 5. After the connector is created, you can close the pop-up window and go to the next page. -6. On the **User mapping** page, enable automatic user mapping. To enable custom mapping, upload a CSV file that contains the user mapping information, and then click **Next**. +6. On the **User mapping** page, enable automatic user mapping. To enable custom mapping, upload a CSV file that contains the user mapping information, and then select **Next**. -7. Review your settings, and then click **Finish** to create the connector. +7. Review your settings, and then select **Finish** to create the connector. 8. Go to the Connectors tab in **Data connectors** page to see the progress of the import process for the new connector. |
| compliance | Archive Salesforcechatter Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-salesforcechatter-data.md | The following overview explains the process of using a connector to archive the - The user who creates the Salesforce Chatter 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](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- 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.+- 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 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 the Salesforce Chatter connector The first step is to access to the **Data Connectors** page in the compliance portal and create a connector for Chatter data. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and then click **Data connectors** > **Salesforce Chatter**. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and then select **Data connectors** > **Salesforce Chatter**. -2. On the **Salesforce Chatter** product description page, click **Add connector**. +2. On the **Salesforce Chatter** product description page, select **Add connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. Enter a unique name that identifies the connector, and then click **Next**. +4. Enter a unique name that identifies the connector, and then select **Next**. 5. Sign in to your Merge1 account to configure the connector. The first step is to access to the **Data Connectors** page in the compliance po The second step is to configure the Salesforce Chatter connector on the Veritas Merge1 site. For information about how to configure the Salesforce Chatter connector, see [Merge1 Third-Party Connectors User Guide](https://docs.ms.merge1.globanetportal.com/Merge1%20Third-Party%20Connectors%20SalesForce%20Chatter%20User%20Guide%20.pdf). -After you click **Save & Finish,** the **User mapping** page in the connector wizard in the compliance portal is displayed. +After you select **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 compliance portal, follow t 1. On the **Map Salesforce Chatter users to Microsoft 365 users** page, enable automatic user mapping. The Salesforce Chatter 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 then go to the **Data connectors** page to see the progress of the import process for the new connector. +2. select **Next**, review your settings, and then go to the **Data connectors** page to see the progress of the import process for the new connector. ## Step 4: Monitor the Salesforce Chatter connector After you create the Salesforce Chatter connector, you can view the connector status in the compliance portal. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and click **Data connectors** in the left nav. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and select **Data connectors** in the left nav. -2. click the **Connectors** tab and then click the **Salesforce Chatter** connector to display the flyout page, which contains the properties and information about the connector. +2. select the **Connectors** tab and then select the **Salesforce Chatter** connector to display the flyout page, which 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 data that's been imported to the Microsoft cloud. +3. Under **Connector status with source**, select the **Download log** link to open (or save) the status log for the connector. This log contains data that's been imported to the Microsoft cloud. ## Known issues |
| compliance | Archive Servicenow Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-servicenow-data.md | The following overview explains the process of using a connector to archive the - The user who creates the ServiceNow 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](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- 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.+- 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 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 the ServiceNow connector The first step is to access to the **Data Connectors** page in the compliance portal and create a connector for ServiceNow data. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and then click **Data connectors** > **ServiceNow**. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and then select **Data connectors** > **ServiceNow**. -2. On the **ServiceNow** product description page, click **Add connector**. +2. On the **ServiceNow** product description page, select **Add connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. Enter a unique name that identifies the connector, and then click **Next**. +4. Enter a unique name that identifies the connector, and then select **Next**. 5. Sign in to your Merge1 account to configure the connector. The first step is to access to the **Data Connectors** page in the compliance po The second step is to configure the ServiceNow connector on the Veritas Merge1 site. For information about how to configure the ServiceNow connector, see [Merge1 Third-Party Connectors User Guide](https://docs.ms.merge1.globanetportal.com/Merge1%20Third-Party%20Connectors%20ServiceNow%20User%20Guide%20.pdf). -After you click **Save & Finish,** the **User mapping** page in the connector wizard in the compliance portal is displayed. +After you select **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 compliance portal, follow t 1. On the **Map ServiceNow users to Microsoft 365 users** page, enable automatic user mapping. The ServiceNow 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 then go to the **Data connectors** page to see the progress of the import process for the new connector. +2. Select **Next**, review your settings, and then go to the **Data connectors** page to see the progress of the import process for the new connector. ## Step 4: Monitor the ServiceNow connector After you create the ServiceNow connector, you can view the connector status in the compliance portal. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and click **Data connectors** in the left nav. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and select **Data connectors** in the left nav. -2. Click the **Connectors** tab and then select the **ServiceNow** connector to display the flyout page, which contains the properties and information about the connector. +2. Select the **Connectors** tab and then select the **ServiceNow** connector to display the flyout page, which 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](data-connector-admin-logs.md). +3. 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](data-connector-admin-logs.md). ## Known issues |
| compliance | Archive Signal Archiver Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-signal-archiver-data.md | The following overview explains the process of using a connector to archive Sign - The user who creates a Signal Archiver connector 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](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- This TeleMessage 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 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.+- This TeleMessage 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. ## Create a Signal Archiver connector After you've completed the prerequisites described in the previous section, you can create the Signal Archiver connector in the compliance portal. The connector uses the information you provide to connect to the TeleMessage site and transfers Signal communications data to the corresponding user mailbox boxes in Microsoft 365. -1. Go to <https://compliance.microsoft.com> and then click **Data connectors** > **Signal Archiver**. +1. Go to <https://compliance.microsoft.com> and then select **Data connectors** > **Signal Archiver**. -2. On the **Signal Archiver** product description page, click **Add connector.** +2. On the **Signal Archiver** product description page, select **Add connector.** -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. On the **Login to TeleMessage** page, under Step 3, enter the required information in the following boxes and then click **Next**. +4. On the **Login to TeleMessage** page, under Step 3, enter the required information in the following boxes and then select **Next**. - **Username:** Your TeleMessage username. After you've completed the prerequisites described in the previous section, you 5. After the connector is created, you can close the pop-up window and go to the next page. -6. On the **User mapping** page, enable automatic user mapping. To enable custom mapping, upload a CSV file that contains the user mapping information, and then click **Next**. +6. On the **User mapping** page, enable automatic user mapping. To enable custom mapping, upload a CSV file that contains the user mapping information, and then select **Next**. -7. Review your settings, and then click **Finish** to create the connector. +7. Review your settings, and then select **Finish** to create the connector. 8. Go to the Connectors tab in **Data connectors** page to see the progress of the import process for the new connector. |
| compliance | Archive Skypeforbusiness Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-skypeforbusiness-data.md | The following overview explains the process of using a connector to archive the - The user who creates the Skype for Business 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](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- 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.+- 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 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 the Skype for Business connector The first step is to access to the **Data Connectors** page in the compliance portal and create a connector for Skype for Business data. -1. Go to <https://compliance.microsoft.com> and click **Data connectors** > **Skype for Business**. +1. Go to <https://compliance.microsoft.com> and select **Data connectors** > **Skype for Business**. -2. On the **Skype for Business** product description page, click **Add connector**. +2. On the **Skype for Business** product description page, select **Add connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. Enter a unique name that identifies the connector, and then click **Next**. +4. Enter a unique name that identifies the connector, and then select **Next**. 5. Sign in to your Merge1 account to configure the connector. The first step is to access to the **Data Connectors** page in the compliance po The second step is to configure the Skype for Business connector on the Veritas Merge1 site. For information about how to configure the Skype for Business connector, see [Merge1 Third-Party Connectors User Guide](https://docs.ms.merge1.globanetportal.com/Merge1%20Third-Party%20Connectors%20Skype%20for%20Business%20%20User%20Guide.pdf). -After you click **Save & Finish**, the **User mapping** page in the connector wizard in the compliance portal is displayed. +After you select **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 compliance portal, follow t 1. On the **Map Skype for Business users to Microsoft 365 users** page, enable automatic user mapping. The Skype for Business 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 then go to the **Data connectors** page to see the progress of the import process for the new connector. +2. Select **Next**, review your settings, and then go to the **Data connectors** page to see the progress of the import process for the new connector. ## Step 4: Monitor the Skype for Business connector After you create the Skype for Business 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. +1. Go to <https://compliance.microsoft.com/> and select **Data connectors** in the left nav. -2. Click the **Connectors** tab and then select the **Skype for Business** connector to display the flyout page, which contains the properties and information about the connector. +2. Select the **Connectors** tab and then select the **Skype for Business** connector to display the flyout page, which 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](data-connector-admin-logs.md). +3. 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](data-connector-admin-logs.md). ## Known issues |
| compliance | Archive Slack Data Microsoft | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-slack-data-microsoft.md | The following overview explains the process of using a Microsoft data connector ## Step 1: Create a Slack eDiscovery connector -1. Go to <https://compliance.microsoft.com> and click **Data connectors** on the left navigation pane. +1. Go to <https://compliance.microsoft.com> and select **Data connectors** on the left navigation pane. -2. On the **Overview** tab, click **Filter** and select **By Microsoft**, and then apply the filter. +2. On the **Overview** tab, select **Filter** and select **By Microsoft**, and then apply the filter. -3. Click **Slack eDiscovery (preview)**. +3. Select **Slack eDiscovery (preview)**. -4. On the **Slack eDiscovery (preview)** product description page, click **Add connector**. +4. On the **Slack eDiscovery (preview)** product description page, select **Add connector**. -5. On the **Terms of service** wizard page, click **Accept**. +5. On the **Terms of service** wizard page, select **Accept**. -6. Enter a unique name that identifies the connector and then click **Next**. The name you enter will identify the connector on the **Data connectors** page after you create it. +6. Enter a unique name that identifies the connector and then select **Next**. The name you enter will identify the connector on the **Data connectors** page after you create it. ## Step 2: Sign into your Slack organization -1. On the **Sign into Slack** wizard page, click **Sign into Slack** to sign into your organization's Slack workspace. +1. On the **Sign into Slack** wizard page, select **Sign into Slack** to sign into your organization's Slack workspace. -2. On the Slack **Sign into your workspace** page, type the name of the workspace that you want to archive data from, and then click **Continue**. +2. On the Slack **Sign into your workspace** page, type the name of the workspace that you want to archive data from, and then select **Continue**. A page is displayed with the name of your Slack workspace and a prompt to sign in. -3. Click the link in the string **Org Owners can also sign in here**. +3. Select the link in the string **Org Owners can also sign in here**. -4. On the workspace sign-in page, enter the email address and password for your organization's Slack enterprise account, and then click **Sign in**. +4. On the workspace sign-in page, enter the email address and password for your organization's Slack enterprise account, and then select **Sign in**. After you successfully sign in, a page is displayed that requests permission to access your Slack organization by the connector app. -5. Click **Allow** to allow the app to administer your organization. +5. Select **Allow** to allow the app to administer your organization. - After you click **Allow**, the Slack page closes and the **Map Slack eDiscovery users to Microsoft 365 users** page in the connector wizard is displayed. + After you select **Allow**, the Slack page closes and the **Map Slack eDiscovery users to Microsoft 365 users** page in the connector wizard is displayed. ## Step 3: Specify the users to import data for Select one of the following options to specify which users whose Slack eDiscover - **Automatic user mapping**. Select this option to automatically map Slack user names to Microsoft 365 mailboxes. The connector does by using the value of the *Email* property, which every Slack message or item contains. This property is populated with an email address of every participant of the message. If the connector can associate the email addresses with corresponding Microsoft 365 users, the item is imported to the Microsoft 365 mailbox of those users. To use this option, you must have SSO configured for your Slack organization. - - **Custom user mapping**. You also have the option to use custom user mapping instead of (or in addition to) automatic user mapping. With this option, you have to create and then upload a CSV file that maps users' Slack member ID to their Microsoft 365 email address. To do this, click **Download CSV mapping template**, populate the CSV file with the Slack member ID and Microsoft 365 email address for all users in your organization, then select and upload the CSV file to the wizard. Be sure not to change the column headings in the CSV file. Here's an example of the CSV mapping file: + - **Custom user mapping**. You also have the option to use custom user mapping instead of (or in addition to) automatic user mapping. With this option, you have to create and then upload a CSV file that maps users' Slack member ID to their Microsoft 365 email address. To do this, select **Download CSV mapping template**, populate the CSV file with the Slack member ID and Microsoft 365 email address for all users in your organization, then select and upload the CSV file to the wizard. Be sure not to change the column headings in the CSV file. Here's an example of the CSV mapping file: |**ExternalUserId** | **O365UserMailbox** | |:-|:--| Select one of the following options to specify which users whose Slack eDiscover ||| > [!TIP]- > Member IDs for users can be obtained by clicking the ... More button in a user's profile and then selecting **Copy member ID**. Alternatively, you can use the Slack [users.list API method](https://api.slack.com/methods/users.list) to obtain the IDs for all members of a Slack team. + > Member IDs for users can be obtained by selecting the ... More button in a user's profile and then selecting **Copy member ID**. Alternatively, you can use the Slack [users.list API method](https://api.slack.com/methods/users.list) to obtain the IDs for all members of a Slack team. If you enable automatic user mapping and provide a custom mapping file, the connector will first look at the custom mapping file to map the Slack user to a Microsoft 365 mailbox. If the connector doesn't find a valid Microsoft 365 user that corresponds to the Slack user, the connector will use the *Email* property of the Slack item. If the connector doesn't find a valid Microsoft 365 user in either the custom mapping file or the *Email* property of the message item, the item won't be imported. Select one of the following options to specify which users whose Slack eDiscover In addition to Slack messages, you can also specify other types of Slack content to import to Microsoft 365. -3. After you configure the data types to import, click **Next**, review the connector settings, and then click **Finish** to create the connector. +3. After you configure the data types to import, select **Next**, review the connector settings, and then select **Finish** to create the connector. ## Step 5: Monitor the Slack eDiscovery connector After you create the Slack eDiscovery connector, you can view the connector status in the compliance portal. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and click **Data connectors** in the left nav. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and select **Data connectors** in the left nav. -2. Click the **Connectors** tab and then select the **Slack eDiscovery** connector to display the flyout page, which contains the properties and information about the connector. +2. Select the **Connectors** tab and then select the **Slack eDiscovery** connector to display the flyout page, which 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](data-connector-admin-logs.md). +3. 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](data-connector-admin-logs.md). ## Known issues |
| compliance | Archive Slack Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-slack-data.md | The following overview explains the process of using a connector to archive the - The user who creates the Slack eDiscovery 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](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- 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.+- 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 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 the Slack eDiscovery connector The first step is to access to the **Data Connectors** page in the compliance portal and create a connector for Slack data. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and then click **Data connectors** > **Slack eDiscovery**. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and then select **Data connectors** > **Slack eDiscovery**. -2. On the **Slack eDiscovery** product description page, click **Add connector**. +2. On the **Slack eDiscovery** product description page, select **Add connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. Enter a unique name that identifies the connector, and then click **Next**. +4. Enter a unique name that identifies the connector, and then select **Next**. 5. Sign in to your Merge1 account to configure the connector. The first step is to access to the **Data Connectors** page in the compliance po The second step is to configure the Slack eDiscovery connector on the Merge1 site. For more information about how to configure the Slack eDiscovery connector on the Veritas Merge1 site, see [Merge1 Third-Party Connectors User Guide](https://docs.ms.merge1.globanetportal.com/Merge1%20Third-Party%20Connectors%20Slack%20eDiscovery%20User%20Guide.pdf). -After you click **Save & Finish**, the **User mapping** page in the connector wizard in the compliance portal is displayed. +After you select **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 After you click **Save & Finish**, the **User mapping** page in the connector wi Slack eDiscovery 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. +2. Select **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 Slack eDiscovery connector After you create the Slack eDiscovery connector, you can view the connector status in the compliance portal. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com) and click **Data connectors** in the left nav. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com) and select **Data connectors** in the left nav. -2. Click the **Connectors** tab and then select the **Slack eDiscovery** connector to display the flyout page. This page contains the properties and information about the connector. +2. Select the **Connectors** tab and then select the **Slack eDiscovery** 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](data-connector-admin-logs.md). +3. 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](data-connector-admin-logs.md). ## Known issues |
| compliance | Archive Symphony Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-symphony-data.md | The following overview explains the process of using a data connector to archive - The user who creates the Symphony 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](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- 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.+- 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 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 the Symphony connector The first step is to access to the **Data Connectors** page in the compliance portal and create a connector for Symphony data. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and then click **Data connectors** > **Symphony**. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and then select **Data connectors** > **Symphony**. -2. On the **Symphony** product description page, click **Add connector**. +2. On the **Symphony** product description page, select **Add connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. Enter a unique name that identifies the connector, and then click **Next**. +4. Enter a unique name that identifies the connector, and then select **Next**. 5. Sign in to your Merge1 account to configure the connector. The first step is to access to the **Data Connectors** page in the compliance po The second step is to configure the Symphony connector on the Merge1 site. For information about configuring the Symphony connector on the Veritas Merge1 site, see [Merge1 Third-Party Connectors User Guide](https://docs.ms.merge1.globanetportal.com/Merge1%20Third-Party%20Connectors%20Symphony%20User%20Guide%20.pdf). -After you click **Save & Finish**, the **User mapping** page in the connector wizard in the compliance portal is displayed. +After you select **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 compliance portal, follow t 1. On the **Map external users to Microsoft 365 users** page, enable automatic user mapping. The Symphony 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 then go to the **Data connectors** page to see the progress of the import process for the new connector. +2. Select **Next**, review your settings, and then go to the **Data connectors** page to see the progress of the import process for the new connector. ## Step 4: Monitor the Symphony connector After you create the Symphony connector, you can view the connector status in the compliance portal. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com) and click **Data connectors** in the left nav. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com) and select **Data connectors** in the left nav. -2. Click the **Connectors** tab and then select the **Symphony** connector to display the flyout page. This page contains the properties and information about the connector. +2. Select the **Connectors** tab and then select the **Symphony** 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](data-connector-admin-logs.md). +3. 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](data-connector-admin-logs.md). ## Known issues |
| compliance | Archive Telegram Archiver Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-telegram-archiver-data.md | The following overview explains the process of using a connector to archive Tele - The user who creates a Telegram Archiver connector 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](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- This TeleMessage 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 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.+- This TeleMessage 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. ## Create a Telegram Archiver connector After you've completed the prerequisites described in the previous section, you can create the Telegram Archiver connector in the compliance portal. The connector uses the information you provide to connect to the TeleMessage site and transfers Telegram communications data to the corresponding user mailbox boxes in Microsoft 365. -1. Go to <https://compliance.microsoft.com> and then click **Data connectors** > T**elegram Archiver**. +1. Go to <https://compliance.microsoft.com> and then select **Data connectors** > T**elegram Archiver**. -2. On the **Telegram Archiver** product description page, click **Add connector**. +2. On the **Telegram Archiver** product description page, select **Add connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. On the **Login to TeleMessage** page, under Step 3, enter the required information in the following boxes and then click **Next**. +4. On the **Login to TeleMessage** page, under Step 3, enter the required information in the following boxes and then select **Next**. - **Username:** Your TeleMessage username. After you've completed the prerequisites described in the previous section, you 5. After the connector is created, you can close the pop-up window and go to the next page. -6. On the **User mapping** page, enable automatic user mapping. To enable custom mapping, upload a CSV file that contains the user mapping information, and then click **Next**. +6. On the **User mapping** page, enable automatic user mapping. To enable custom mapping, upload a CSV file that contains the user mapping information, and then select **Next**. -7. Review your settings, and then click **Finish** to create the connector. +7. Review your settings, and then select **Finish** to create the connector. 8. Go to the Connectors tab in **Data connectors** page to see the progress of the import process for the new connector. |
| compliance | Archive Telus Network Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-telus-network-data.md | Some of the implementation steps required to archive TELUS Network data are exte - The user who creates a TELUS Network connector 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](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- This TeleMessage 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 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.+- This TeleMessage 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. ## Create a TELUS Network connector After you've completed the prerequisites described in the previous section, you can create TELUS Network connector in the compliance portal. The connector uses the information you provide to connect to the TeleMessage site and transfer SMS messages to the corresponding user mailbox boxes in Microsoft 365. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and then click **Data connectors** > **TELUS Network**. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and then select **Data connectors** > **TELUS Network**. -2. On the **TELUS Network** product description page, click **Add connector** +2. On the **TELUS Network** product description page, select **Add connector** -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. On the **Login to TeleMessage** page, under Step 3, enter the required information in the following boxes and then click **Next**. +4. On the **Login to TeleMessage** page, under Step 3, enter the required information in the following boxes and then select **Next**. - **Username:** Your TeleMessage username. After you've completed the prerequisites described in the previous section, you 5. After the connector is created, you can close the pop-up window and go to the next page. -6. On the **User mapping** page, enable automatic user mapping and click **Next**. In case you need custom mapping upload a CSV file, and click **Next**. +6. On the **User mapping** page, enable automatic user mapping and select **Next**. In case you need custom mapping upload a CSV file, and select **Next**. -7. Review your settings, and then click **Finish** to create the connector. +7. Review your settings, and then select **Finish** to create the connector. 8. Go to the Connectors tab in **Data connectors** page to see the progress of the import process for the new connector. |
| compliance | Archive Text Delimited Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-text-delimited-data.md | The following overview explains the process of using a connector to archive text - The user who creates the text-delimited 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](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- 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.+- 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 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 the text-delimited connector The first step is to access to the **Data Connectors** page in the compliance portal and create a connector for text-delimited data. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and then click **Data connectors** > **Text-Delimited**. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and then select **Data connectors** > **Text-Delimited**. -2. On the **text-delimited** product description page, click **Add connector**. +2. On the **text-delimited** product description page, select **Add connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. Enter a unique name that identifies the connector, and then click **Next**. +4. Enter a unique name that identifies the connector, and then select **Next**. 5. Sign in to your Merge1 account to configure the connector. The first step is to access to the **Data Connectors** page in the compliance po The second step is to configure the text-delimited connector on the Merge1 site. For information about configuring the text-delimited connector on the Veritas Merge1 site, see [Merge1 Third-Party Connectors User Guide](https://docs.ms.merge1.globanetportal.com/Merge1%20Third-Party%20Connectors%20text-delimited%20User%20Guide%20.pdf). -After you click **Save & Finish**, the **User mapping** page in the connector wizard in the compliance portal is displayed. +After you select **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 compliance portal, follow t 1. On the **Map external users to Microsoft 365 users** page, enable automatic user mapping. The Text- Delimited source 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 then go to the **Data connectors** page to see the progress of the import process for the new connector. +2. Select **Next**, review your settings, and then go to the **Data connectors** page to see the progress of the import process for the new connector. ## Step 4: Monitor the text-delimited connector After you create the Text- Delimited connector, you can view the connector status in the compliance portal. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com) and click **Data connectors** in the left nav. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com) and select **Data connectors** in the left nav. -2. Click the **Connectors** tab and then select the **Text- Delimited** connector to display the flyout page. This page contains the properties and information about the connector. +2. Select the **Connectors** tab and then select the **Text- Delimited** 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](data-connector-admin-logs.md). +3. 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](data-connector-admin-logs.md). ## Known issues |
| compliance | Archive Twitter Data With Sample Connector | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-twitter-data-with-sample-connector.md | To deploy the source code for the Twitter connector app: 1. Go to [this GitHub site](https://github.com/microsoft/m365-sample-twitter-connector-csharp-aspnet). -2. Click **Deploy to Azure**. +2. Select **Deploy to Azure**. For step-by-step instructions, see [Deploy the connector web service from GitHub to your Azure account](deploy-twitter-connector.md#step-2-deploy-the-connector-web-service-from-github-to-your-azure-account). |
| compliance | Archive Veritas Twitter Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-veritas-twitter-data.md | The following overview explains the process of using a connector to archive Twit - The user who creates the YouTube 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](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- 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.+- 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 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 the Twitter connector The first step is to access to the **Data Connectors** page in the compliance portal and create a connector for Twitter data. -1. Go to <https://compliance.microsoft.com> and then click **Data connectors** > **Twitter**. +1. Go to <https://compliance.microsoft.com> and then select **Data connectors** > **Twitter**. -2. On the **Twitter** product description page, click **Add connector**. +2. On the **Twitter** product description page, select **Add connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. Enter a unique name that identifies the connector, and then click **Next**. +4. Enter a unique name that identifies the connector, and then select **Next**. 5. Sign in to your Merge1 account to configure the connector. The first step is to access to the **Data Connectors** page in the compliance po The second step is to configure the Twitter connector on the Veritas Merge1 site. For information about how to configure the Twitter connector, see [Merge1 Third-Party Connectors User Guide](https://docs.ms.merge1.globanetportal.com/Merge1%20Third-Party%20Connectors%20Twitter%20User%20Guide.pdf). -After you click **Save & Finish,** the **User mapping** page in the connector wizard in the compliance portal is displayed. +After you select **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 compliance portal, follow t 1. On the **Map Twitter users to Microsoft 365 users** page, enable automatic user mapping. The Twitter 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 then go to the **Data connectors** page to see the progress of the import process for the new connector. +2. Select **Next**, review your settings, and then go to the **Data connectors** page to see the progress of the import process for the new connector. ## Step 4: Monitor the Twitter connector After you create the Twitter 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. +1. Go to <https://compliance.microsoft.com/> and select **Data connectors** in the left nav. -2. Click the **Connectors** tab and then select the **Twitter** connector to display the flyout page, which contains the properties and information about the connector. +2. Select the **Connectors** tab and then select the **Twitter** connector to display the flyout page, which 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](data-connector-admin-logs.md). +3. 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](data-connector-admin-logs.md). ## Known issues |
| compliance | Archive Verizon Network Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-verizon-network-data.md | Some of the implementation steps required to archive Verizon Network data are ex - The user who creates a Verizon Network connector 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](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- This TeleMessage 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 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.+- This TeleMessage 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. ## Create a Verizon Network connector After you've completed the prerequisites described in the previous section, you can create Verizon Network connector in the compliance portal. The connector uses the information you provide to connect to the TeleMessage site and transfer SMS and MMS messages to the corresponding user mailbox boxes in Microsoft 365. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com) and then click **Data connectors** > **Verizon Network**. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com) and then select **Data connectors** > **Verizon Network**. -2. On the **Verizon Network** product description page, click **Add connector** +2. On the **Verizon Network** product description page, select **Add connector** -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. On the **Login to TeleMessage** page, under Step 3, enter the required information in the following boxes and then click **Next**. +4. On the **Login to TeleMessage** page, under Step 3, enter the required information in the following boxes and then select **Next**. - **Username:** Your TeleMessage username. After you've completed the prerequisites described in the previous section, you 5. After the connector is created, you can close the pop-up window and go to the next page. -6. On the **User mapping** page, enable automatic user mapping and click **Next**. In case you need custom mapping upload a CSV file, and click **Next**. +6. On the **User mapping** page, enable automatic user mapping and select **Next**. In case you need custom mapping upload a CSV file, and select **Next**. -7. Review your settings, and then click **Finish** to create the connector. +7. Review your settings, and then select **Finish** to create the connector. 8. Go to the Connectors tab in **Data connectors** page to see the progress of the import process for the new connector. |
| compliance | Archive Webexteams Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-webexteams-data.md | The following overview explains the process of using a connector to archive Webe - The user who creates the Webex Teams 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](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- 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.+- 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 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 the Webex Teams connector The first step is to gain access to the **Data Connectors** and set up the [Webex Teams](https://globanet.com/webex-teams/) connector. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and then click **Data connectors** > **Webex Teams**. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and then select **Data connectors** > **Webex Teams**. -2. On the **Webex Teams** product description page, click **Add connector**. +2. On the **Webex Teams** product description page, select **Add connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. Enter a unique name that identifies the connector, and then click **Next**. +4. Enter a unique name that identifies the connector, and then select **Next**. 5. Sign in to your Merge1 account to configure the connector. The first step is to gain access to the **Data Connectors** and set up the [Webe The second step is to configure the Webex Teams connector on the Merge1 site. For information about how to configure the Webex Teams connector, see [Merge1 Third-Party Connectors User Guide](https://docs.ms.merge1.globanetportal.com/Merge1%20Third-Party%20Connectors%20Webex%20Teams%20User%20Guide%20.pdf). -After you click **Save & Finish**, the **User mapping** page in the connector wizard in the compliance portal is displayed. +After you select **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 compliance portal, follow t 1. On the **Map Webex Teams users to Microsoft 365 users** page, enable automatic user mapping. The Webex Teams 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 then go to the **Data connectors** page to see the progress of the import process for the new connector. +2. Select **Next**, review your settings, and then go to the **Data connectors** page to see the progress of the import process for the new connector. ## Step 4: Monitor the Webex Teams connector After you create the Webex Teams connector, you can view the connector status in the compliance portal. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com) and click **Data connectors** in the left nav. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com) and select **Data connectors** in the left nav. -2. Click the **Connectors** tab and then select the **Webex Teams** connector to display the flyout page. This page contains the properties and information about the connector. +2. Select the **Connectors** tab and then select the **Webex Teams** 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](data-connector-admin-logs.md). +3. 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](data-connector-admin-logs.md). ## Known issues |
| compliance | Archive Webpagecapture Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-webpagecapture-data.md | The following overview explains the process of using a connector to archive webp - The user who creates the Webpage Capture 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](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- 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.+- 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 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 the Webpage Capture connector The first step is to access to the **Data Connectors** and create a connector for Web Page source data. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and then click **Data connectors** > **Webpage Capture**. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and then select **Data connectors** > **Webpage Capture**. -2. On the **Webpage Capture** product description page, click **Add connector**. +2. On the **Webpage Capture** product description page, select **Add connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. Enter a unique name that identifies the connector, and then click **Next**. +4. Enter a unique name that identifies the connector, and then select **Next**. 5. Sign in to your Merge1 account to configure the connector. The first step is to access to the **Data Connectors** and create a connector fo The second step is to configure the Webpage Capture connector on the Veritas Merge1 site. For information about how to configure the Webpage Capture connector, see [Merge1 Third-Party Connectors User Guide](https://docs.ms.merge1.globanetportal.com/Merge1%20Third-Party%20Connectors%20Web%20Page%20Capture%20User%20Guide%20.pdf). -After you click **Save & Finish**, the **User mapping** page in the connector wizard in the compliance portal is displayed. +After you select **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 compliance portal, follow t 1. On the **Map Webpage Capture users to Microsoft 365 users** page, enable automatic user mapping. The Webpage Capture 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. +2. Select **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 Webpage Capture connector After you create the Webpage Capture connector, you can view the connector status in the compliance portal. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com) and click **Data connectors** in the left nav. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com) and select **Data connectors** in the left nav. -2. Click the **Connectors** tab and then select the **Webpage Capture** connector to display the flyout page. This page contains the properties and information about the connector. +2. Select the **Connectors** tab and then select the **Webpage Capture** 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](data-connector-admin-logs.md). +3. 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](data-connector-admin-logs.md). ## Known issues |
| compliance | Archive Wechat Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-wechat-data.md | The following overview explains the process of using a connector to archive WeCh - The user who creates a WeChat Archiver connector in the compliance portal 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](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- This TeleMessage 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 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.+- This TeleMessage 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. ## Create a WeChat Archiver connector Follow the steps in this section to create a WeChat Archiver connector in the compliance portal. The connector uses the information you provide to connect to the TeleMessage site and transfer WeChat communications data to the corresponding user mailboxes in Microsoft 365. -1. Go to <https://compliance.microsoft.com> and then click **Data connectors** > **WeChat Archiver**. +1. Go to <https://compliance.microsoft.com> and then select **Data connectors** > **WeChat Archiver**. -2. On the **WeChat Archiver** product description page, click **Add connector** +2. On the **WeChat Archiver** product description page, select **Add connector** -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. On the **Login to TeleMessage** page, under Step 3, enter the required information in the following boxes and then click **Next**. +4. On the **Login to TeleMessage** page, under Step 3, enter the required information in the following boxes and then select **Next**. - **Username**: Your TeleMessage user name. Follow the steps in this section to create a WeChat Archiver connector in the co 6. On the **User mapping** page, enable automatic user mapping. You can also upload a custom user mapping CSV file. -7. Click **Next**, review your settings, and then click **Finish** to create the connector. +7. Select **Next**, review your settings, and then select **Finish** to create the connector. 8. Go to the **Connectors** tab on **Data connectors** page to see the progress of the import process for the new connector. |
| compliance | Archive Whatsapp Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-whatsapp-data.md | Some of the implementation steps required to archive WhatsApp communication data - The user who creates a Verizon Network connector 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](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- This TeleMessage 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 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.+- This TeleMessage 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. ## Create a WhatsApp Archiver connector After you've completed the prerequisites described in the previous section, you can create the WhatsApp connector in the compliance portal. The connector uses the information you provide to connect to the TeleMessage site and transfer the WhatsApp data to the corresponding user mailbox boxes in Microsoft 365. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and then click **Data connectors** > **WhatsApp Archiver**. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and then select **Data connectors** > **WhatsApp Archiver**. -2. On the **WhatsApp Archiver** product description page, click **Add connector** +2. On the **WhatsApp Archiver** product description page, select **Add connector** -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. On the **Login to TeleMessage** page, under Step 3, enter the required information in the following boxes and then click **Next**. +4. On the **Login to TeleMessage** page, under Step 3, enter the required information in the following boxes and then select **Next**. - **Username:** Your TeleMessage username. After you've completed the prerequisites described in the previous section, you 5. After the connector is created, you can close the pop-up window and go to the next page. -6. On the **User mapping** page, enable automatic user mapping and click **Next**. In case you need custom mapping upload a CSV file, and click **Next**. +6. On the **User mapping** page, enable automatic user mapping and select **Next**. In case you need custom mapping upload a CSV file, and select **Next**. -7. Review your settings, and then click **Finish** to create the connector. +7. Review your settings, and then select **Finish** to create the connector. 8. Go to the Connectors tab in **Data connectors** page to see the progress of the import process for the new connector. |
| compliance | Archive Workplacefromfacebook Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-workplacefromfacebook-data.md | The following overview explains the process of using a connector to archive Work - The user who creates the Workplace from Facebook 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](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- 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.+- 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 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 the Workplace from Facebook connector The first step is to access to the **Data Connectors** page in the compliance portal and create a connector for Workplace data. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and then click **Data connectors** > **Workplace from Facebook**. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and then select **Data connectors** > **Workplace from Facebook**. -2. On the **Workplace from Facebook** product description page, click **Add connector**. +2. On the **Workplace from Facebook** product description page, select **Add connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. Enter a unique name that identifies the connector, and then click **Next**. +4. Enter a unique name that identifies the connector, and then select **Next**. 5. Sign in to your Merge1 account to configure the connector. The first step is to access to the **Data Connectors** page in the compliance po The second step is to configure the Workplace from Facebook connector on the Merge1 site. For information about how to configure the Workplace from Facebook connector, see [Merge1 Third-Party Connectors User Guide](https://docs.ms.merge1.globanetportal.com/Merge1%20Third-Party%20Connectors%20Workplace%20from%20Facebook%20User%20Guide%20.pdf). -After you click **Save & Finish**, the **User mapping** page in the connector wizard in the compliance portal is displayed. +After you select **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 compliance portal, follow t 1. On the **Map external users to Microsoft 365 users** page, enable automatic user mapping. The Workplace items include a property called *Email* that 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 then go to the **Data connectors** page to see the progress of the import process for the new connector. +2. Select **Next**, review your settings, and then go to the **Data connectors** page to see the progress of the import process for the new connector. ## Step 4: Monitor the Workplace from Facebook connector After you create the Workplace from Facebook connector, you can view the connector status in the compliance portal. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com) and click **Data connectors** in the left nav. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com) and select **Data connectors** in the left nav. -2. Click the **Connectors** tab and then select the **Workplace from Facebook** connector to display the flyout page. This page contains the properties and information about the connector. +2. Select the **Connectors** tab and then select the **Workplace from Facebook** 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](data-connector-admin-logs.md). +3. 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](data-connector-admin-logs.md). ## Known issues |
| compliance | Archive Xip Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-xip-data.md | The following overview explains the process of using a connector to archive the - The user who creates the XIP 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](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- 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.+- 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 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 the XIP connector The first step is to access to the **Data Connectors** page in the compliance portal and create a connector for the XIP source data. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and then click **Data connectors** \> **XIP**. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and then select **Data connectors** \> **XIP**. -2. On the **XIP** product description page, click **Add new connector**. +2. On the **XIP** product description page, select **Add new connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. Enter a unique name that identifies the connector, and then click **Next**. +4. Enter a unique name that identifies the connector, and then select **Next**. 5. Sign in to your Merge1 account to configure the connector. The first step is to access to the **Data Connectors** page in the compliance po The second step is to configure the XIP connector on the Merge1 site. For information about how to configure the XIP connector, see [Merge1 Third-Party Connectors User Guide](https://docs.ms.merge1.globanetportal.com/Merge1%20Third-Party%20Connectors%20XIP%20User%20Guide%20.pdf). -After you click **Save & Finish**, the **User mapping** page in the connector wizard in the compliance portal is displayed. +After you select **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, follow these steps: 1. On the **Map XIP users to Microsoft 365 users** page, enable automatic user mapping. The XIP source 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. +2. Select **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 XIP connector After you create the XIP connector, you can view the connector status in the compliance portal. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and click **Data connectors** in the left nav. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and select **Data connectors** in the left nav. -2. Click the **Connectors** tab and then select the **XIP** connector to display the flyout page, which contains the properties and information about the connector. +2. Select the **Connectors** tab and then select the **XIP** connector to display the flyout page, which 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](data-connector-admin-logs.md). +3. 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](data-connector-admin-logs.md). ## Known issues |
| compliance | Archive Xslt Xml Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-xslt-xml-data.md | The following overview explains the process of using a connector to archive XSLT - The user who creates the XSLT/XML 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](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- 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.+- 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 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 an XSLT/XML connector The first step is to access to the **Data Connectors** in the compliance portal and create a connector for XSLT/XML data. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and then click **Data connectors** > **XSLT/XML**. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and then select **Data connectors** > **XSLT/XML**. -2. On the **XSLT/XML** product description page, click **Add new connector**. +2. On the **XSLT/XML** product description page, select **Add new connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. Enter a unique name that identifies the connector, and then click **Next**. +4. Enter a unique name that identifies the connector, and then select **Next**. 5. Sign in to your Merge1 account to configure the connector. The first step is to access to the **Data Connectors** in the compliance portal The second step is to configure the XSLT/XML connector on the Merge1 site. For information about how to configure the XSLT/XML connector on the Veritas Merge1 site, see [Merge1 Third-Party Connectors User Guide](https://docs.ms.merge1.globanetportal.com/Merge1%20Third-Party%20Connectors%20XSLT-XML%20User%20Guide%20.pdf). -After you click **Save & Finish**, the **User mapping** page in the connector wizard in the compliance portal is displayed. +After you select **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 After you click **Save & Finish**, the **User mapping** page in the connector wi 2. On the **Map XSLT/XML users to Microsoft 365 users** page, enable automatic user mapping. The XSLT/XML 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. -3. Click **Next**, review your settings, and go to the **Data connectors** page to see the progress of the import process for the new connector. +3. Select **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 XSLT/XML connector After you create the XSLT/XML connector, you can view the connector status in the compliance portal. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com) and click **Data connectors** in the left nav. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com) and select **Data connectors** in the left nav. -2. Click the **Connectors** tab and then select the **XSLT/XML** connector to display the flyout page. This page contains the properties and information about the connector. +2. Select the **Connectors** tab and then select the **XSLT/XML** 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](data-connector-admin-logs.md). +3. 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](data-connector-admin-logs.md). ## Known issues |
| compliance | Archive Yieldbroker Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-yieldbroker-data.md | The following overview explains the process of using a connector to archive the - The user who creates the Yieldbroker 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](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- 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.+- 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 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 the Yieldbroker connector The first step is to access to the **Data Connectors** page in the compliance portal and create a connector for the Yieldbroker. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and then click **Data connectors** > **Yieldbroker**. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and then select **Data connectors** > **Yieldbroker**. -2. On the **Yieldbroker** product description page, click **Add new connector**. +2. On the **Yieldbroker** product description page, select **Add new connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. Enter a unique name that identifies the connector, and then click **Next**. +4. Enter a unique name that identifies the connector, and then select **Next**. 5. Sign in to your Merge1 account to configure the connector. The first step is to access to the **Data Connectors** page in the compliance po The second step is to configure the Yieldbroker connector on the Merge1 site. For information about how to configure the Yieldbroker, see [Merge1 Third-Party Connectors User Guide](https://docs.ms.merge1.globanetportal.com/Merge1%20Third-Party%20Connectors%20Yieldbroker%20User%20Guide%20.pdf). -After you click **Save & Finish**, the **User mapping** page in the connector wizard in the compliance portal is displayed. +After you select **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, follow these steps: 1. On the **Map Yieldbroker users to Microsoft 365 users** page, enable automatic user mapping. The Yieldbroker 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. +2. Select **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 Yieldbroker connector After you create the Yieldbroker connector, you can view the connector status in the compliance portal. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and click **Data connectors** in the left nav. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and select **Data connectors** in the left nav. -2. Click the **Connectors** tab and then select the **Yieldbroker** connector to display the flyout page, which contains the properties and information about the connector. +2. Select the **Connectors** tab and then select the **Yieldbroker** connector to display the flyout page, which 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](data-connector-admin-logs.md). +3. 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](data-connector-admin-logs.md). ## Known issues |
| compliance | Archive Youtube Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-youtube-data.md | The following overview explains the process of using a connector to archive the The first step is to access to the **Data Connectors** page in the compliance portal and create a connector for YouTube data. -1. Go to <https://compliance.microsoft.com> and then click **Data connectors** > **YouTube**. +1. Go to <https://compliance.microsoft.com> and then select **Data connectors** > **YouTube**. -2. On the **YouTube** product description page, click **Add connector**. +2. On the **YouTube** product description page, select **Add connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. Enter a unique name that identifies the connector, and then click **Next**. +4. Enter a unique name that identifies the connector, and then select **Next**. 5. Sign in to your Merge1 account to configure the connector. The first step is to access to the **Data Connectors** page in the compliance po The second step is to configure the YouTube connector on the Veritas Merge1 site. For information about how to configure the YouTube connector, see [Merge1 Third-Party Connectors User Guide](https://docs.ms.merge1.globanetportal.com/Merge1%20Third-Party%20Connectors%20YouTube%20User%20Guide.pdf). -After you click **Save & Finish,** the **User mapping** page in the connector wizard in the compliance portal is displayed. +After you select **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 compliance portal, follow t 1. On the **Map YouTube users to Microsoft 365 users** page, enable automatic user mapping. The YouTube 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 then go to the **Data connectors** page to see the progress of the import process for the new connector. +2. Select **Next**, review your settings, and then go to the **Data connectors** page to see the progress of the import process for the new connector. ## Step 4: Monitor the YouTube connector After you create the YouTube 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. +1. Go to <https://compliance.microsoft.com/> and select **Data connectors** in the left nav. -2. Click the **Connectors** tab and then select the **YouTube** connector to display the flyout page, which contains the properties and information about the connector. +2. Select the **Connectors** tab and then select the **YouTube** connector to display the flyout page, which 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](data-connector-admin-logs.md). +3. 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](data-connector-admin-logs.md). ## Known issues |
| compliance | Archive Zoommeetings Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/archive-zoommeetings-data.md | The following overview explains the process of using a connector to archive Zoom - The user who creates the Zoom Meetings 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](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). -- 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.+- 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 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 the Zoom Meetings connector The first step is to access the **Data Connectors** in the compliance portal and create a Zoom Meetings connector. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and then click **Data connectors** > **Zoom Meetings**. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com/) and then select **Data connectors** > **Zoom Meetings**. -2. On the **Zoom Meetings** product description page, click **Add connector**. +2. On the **Zoom Meetings** product description page, select **Add connector**. -3. On the **Terms of service** page, click **Accept**. +3. On the **Terms of service** page, select **Accept**. -4. Enter a unique name that identifies the connector, and then click **Next**. +4. Enter a unique name that identifies the connector, and then select **Next**. 5. Sign in to your Merge1 account to configure the connector. The first step is to access the **Data Connectors** in the compliance portal and The second step is to configure the Zoom Meetings connector on the Merge1 site. For more information about how to configure the Zoom Meetings connector on the Veritas Merge1 site, see [Merge1 Third-Party Connectors User Guide](https://docs.ms.merge1.globanetportal.com/Merge1%20Third-Party%20Connectors%20Zoom%20Meetings%20User%20Guide%20.pdf). -After you click **Save & Finish**, the **User mapping** page in the connector wizard in the compliance portal is displayed. +After you select **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 After you click **Save & Finish**, the **User mapping** page in the connector wi Zoom Meetings items include a property called *Email* that 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. +2. Select **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 Zoom Meetings connector After you create the Zoom Meetings connector, you can view the connector status in the compliance portal. -1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com) and click **Data connectors** in the left nav. +1. Go to [https://compliance.microsoft.com](https://compliance.microsoft.com) and select **Data connectors** in the left nav. -2. Click the **Connectors** tab and then select the **Zoom Meetings** connector to display the flyout page. This page contains the properties and information about the connector. +2. Select the **Connectors** tab and then select the **Zoom Meetings** 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](data-connector-admin-logs.md). +3. 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](data-connector-admin-logs.md). ## Known issues |
| compliance | Communication Compliance Case Study | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/communication-compliance-case-study.md | search.appverid: # Case study - Contoso quickly configures an inappropriate text policy for Microsoft Teams, Exchange, and Yammer communications +>[!IMPORTANT] +>Microsoft Purview Communication Compliance provides the tools to help organizations detect regulatory compliance violations (for example SEC or FINRA), such as sensitive or confidential information, harassing or threatening language, and sharing of adult content. Built with privacy by design, usernames are pseudonymized by default, role-based access controls are built in, investigators are opted in by an admin, and audit logs are in place to ensure user-level privacy. + [Microsoft Purview Communication Compliance](/microsoft-365/compliance/communication-compliance) helps minimize communication risks by helping you detect, capture, and act on messages with inappropriate text in your organization. inappropriate text may include profanity, threats, harassment, and inappropriate images. Pre-defined and custom [policies](/microsoft-365/compliance/communication-compliance-policies) allow you to scan internal and external communications for policy matches so they can be examined by designated reviewers. Reviewers can [investigate alerts](/microsoft-365/compliance/communication-compliance-investigate-remediate#investigate-alerts) for email, Microsoft Teams, Yammer, or third-party communications in your organization and take appropriate [remediation actions](/microsoft-365/compliance/communication-compliance-investigate-remediate#remediate-alerts) to make sure they're compliant with your organization's message standards. The Contoso Corporation is a fictional organization that needs to quickly configure a policy to detect inappropriate text. They have been using Microsoft 365 primarily for email, Microsoft Teams, and Yammer support for their users but have new requirements to enforce company policy around workplace harassment. Contoso IT administrators and compliance specialists have a basic understanding of the fundamentals of working with Microsoft 365 and are looking for end-to-end guidance for how to quickly get started with communication compliance. Contoso IT administrators take the following steps to verify the licensing suppo ### Permissions for communication compliance -There are five role groups used to configure permissions to manage communication compliance features. To make **Communication compliance** available as a menu option in Microsoft Purview compliance portal and to continue with these configuration steps, Contoso administrators are assigned the *Communication Compliance Admin* role. +There are five role groups used to configure permissions to manage communication compliance features. To make **Communication compliance** available as a menu option in Microsoft Purview compliance portal and to continue with these configuration steps, Contoso administrators are assigned the *Communication Compliance Admins* role. Contoso decides to use the *Communication Compliance* role group assign all the communication compliance administrators, analysts, investigators, and viewers to the group. This role group configuration makes it easier for Contoso to get started quickly and best fits their compliance management requirements. |**Role**|**Role permissions**| |:--|:--| | **Communication Compliance** | Use this role group to manage communication compliance for your organization in a single group. By adding all user accounts for designated administrators, analysts, investigators, and viewers, you can configure communication compliance permissions in a single group. This role group contains all the communication compliance permission roles. This role group configuration is the easiest way to quickly get started with communication compliance and is a good fit for organizations that don't need separate permissions defined for separate groups of users. |-| **Communication Compliance Admin** | Use this role group to initially configure communication compliance and later to segregate communication compliance administrators into a defined group. Users assigned to this role group can create, read, update, and delete communication compliance policies, global settings, and role group assignments. Users assigned to this role group can't view message alerts. | -| **Communication Compliance Analyst** | Use this group to assign permissions to users that will act as communication compliance analysts. Users assigned to this role group can view policies where they're assigned as Reviewers, view message metadata (not message content), escalate to additional reviewers, or send notifications to users. Analysts can't resolve pending alerts. | -| **Communication Compliance Investigator** | Use this group to assign permissions to users that will act as communication compliance investigators. Users assigned to this role group can view message metadata and content, escalate to additional reviewers, escalate to an eDiscovery (Premium) case, send notifications to users, and resolve the alert. | -| **Communication Compliance Viewer** | Use this group to assign permissions to users that will manage communication reports. Users assigned to this role group can access all reporting widgets on the communication compliance home page and can view all communication compliance reports. | +| **Communication Compliance Admins** | Use this role group to initially configure communication compliance and later to segregate communication compliance administrators into a defined group. Users assigned to this role group can create, read, update, and delete communication compliance policies, global settings, and role group assignments. Users assigned to this role group can't view message alerts. | +| **Communication Compliance Analysts** | Use this group to assign permissions to users that will act as communication compliance analysts. Users assigned to this role group can view policies where they're assigned as Reviewers, view message metadata (not message content), escalate to additional reviewers, or send notifications to users. Analysts can't resolve pending alerts. | +| **Communication Compliance Investigators** | Use this group to assign permissions to users that will act as communication compliance investigators. Users assigned to this role group can view message metadata and content, escalate to additional reviewers, escalate to an eDiscovery (Premium) case, send notifications to users, and resolve the alert. | +| **Communication Compliance Viewers** | Use this group to assign permissions to users that will manage communication reports. Users assigned to this role group can access all reporting widgets on the communication compliance home page and can view all communication compliance reports. | 1. Contoso IT administrators sign into the [Microsoft Purview compliance portal](https://compliance.microsoft.com/permissions) permissions page using credentials for a global administrator account and select the link to view and manage roles in Microsoft 365. 2. In the Microsoft Purview compliance portal, they go to <a href="https://go.microsoft.com/fwlink/p/?linkid=2173597" target="_blank">**Permissions**</a> and select the link to view and manage roles in Office 365. |
| compliance | Communication Compliance Channels | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/communication-compliance-channels.md | search.appverid: # Detect channel signals with communication compliance +>[!IMPORTANT] +>Microsoft Purview Communication Compliance provides the tools to help organizations detect regulatory compliance violations (for example SEC or FINRA), such as sensitive or confidential information, harassing or threatening language, and sharing of adult content. Built with privacy by design, usernames are pseudonymized by default, role-based access controls are built in, investigators are opted in by an admin, and audit logs are in place to ensure user-level privacy. + With communication compliance policies, you can choose to scan messages in one or more of the following communication platforms as a group or as standalone sources. Original messages captured across these platforms are retained in the original platform location in accordance with your organization's [retention and hold policies](/microsoft-365/compliance/information-governance). Copies of messages used by communication compliance policies for analysis and investigation are retained for as long as policy is in place, even if users leave your organization and their mailboxes are deleted. When a communication policy is deleted, copies of messages associated with the policy are also deleted. [!INCLUDE [purview-preview](../includes/purview-preview.md)] |
| compliance | Communication Compliance Configure | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/communication-compliance-configure.md | search.appverid: # Get started with communication compliance +>[!IMPORTANT] +>Microsoft Purview Communication Compliance provides the tools to help organizations detect regulatory compliance violations (for example SEC or FINRA), such as sensitive or confidential information, harassing or threatening language, and sharing of adult content. Built with privacy by design, usernames are pseudonymized by default, role-based access controls are built in, investigators are opted in by an admin, and audit logs are in place to ensure user-level privacy. + Use communication compliance policies to identify user communications for examination by internal or external reviewers. For more information about how communication compliance policies can help you detect communications in your organization, see [communication compliance policies](/microsoft-365/compliance/communication-compliance-policies). If you'd like to review how Contoso quickly configured a communication compliance policy to detect inappropriate content in Microsoft Teams, Exchange Online, and Yammer communications, check out this [case study](/microsoft-365/compliance/communication-compliance-case-study). [!INCLUDE [purview-preview](../includes/purview-preview.md)] There are six role groups used to configure initial permissions to manage commun - Microsoft Purview compliance portal [*Organization Management*](/microsoft-365/security/office-365-security/permissions-in-the-security-and-compliance-center) role group - Microsoft Purview compliance portal [*Compliance Administrator*](/microsoft-365/security/office-365-security/permissions-in-the-security-and-compliance-center) role group - *Communication Compliance* role group-- *Communication Compliance Admin* role group+- *Communication Compliance Admins* role group -Members of the following roles have the same solution permissions included with the *Communication Compliance Admin* role group: +Members of the following roles have the same solution permissions included with the *Communication Compliance Admins* role group: - Azure Active Directory *Global Administrator* - Azure Active Directory *Compliance Administrator* Members of the following roles have the same solution permissions included with - Microsoft Purview compliance portal *Compliance Administrator* > [!IMPORTANT]-> Make sure you always have at least one user in the *Communication Compliance* or *Communication Compliance Admin* role groups (depending on the option you choose) so that your communication compliance configuration doesn't get in to a 'zero administrator' scenario if specific users leave your organization. +> Make sure you always have at least one user in the *Communication Compliance* or *Communication Compliance Admins* role groups (depending on the option you choose) so that your communication compliance configuration doesn't get in to a 'zero administrator' scenario if specific users leave your organization. Depending on how you wish to manage communication compliance policies and alerts, you'll need to assign users to specific role groups to manage different sets of communication compliance features. You have the option to assign users with different compliance responsibilities to specific role groups to manage different areas of communication compliance features. Or you may decide to assign all user accounts for designated administrators, analysts, investigators, and viewers to the *Communication Compliance* role group. Use a single role group or multiple role groups to best fit your compliance management requirements. Choose from these solution role group options when configuring and managing comm | Role | Role permissions | |:--|:--| | **Communication Compliance** | Use this role group to manage communication compliance for your organization in a single group. By adding all user accounts for designated administrators, analysts, investigators, and viewers, you can configure communication compliance permissions in a single group. This role group contains all the communication compliance permission roles. This configuration is the easiest way to quickly get started with communication compliance and is a good fit for organizations that don't need separate permissions defined for separate groups of users. Users that create policies as a communication compliance administrator must have their mailbox hosted on Exchange Online.|-| **Communication Compliance Admin** | Use this role group to initially configure communication compliance and later to segregate communication compliance administrators into a defined group. Users assigned to this role group can create, read, update, and delete communication compliance policies, global settings, and role group assignments. Users assigned to this role group can't view message alerts. Users that create policies as a communication compliance administrator must have their mailbox hosted on Exchange Online.| -| **Communication Compliance Analyst** | Use this group to assign permissions to users that will act as communication compliance analysts. Users assigned to this role group can view policies where they're assigned as Reviewers, view message metadata (not message content), escalate to additional reviewers, or send notifications to users. Analysts can't resolve pending alerts. | -| **Communication Compliance Investigator** | Use this group to assign permissions to users that will act as communication compliance investigators. Users assigned to this role group can view message metadata and content, escalate to additional reviewers, escalate to an eDiscovery (Premium) case, send notifications to users, and resolve the alert. | -| **Communication Compliance Viewer** | Use this group to assign permissions to users that will manage communication reports. Users assigned to this role group can access all reporting widgets on the communication compliance home page and can view all communication compliance reports. | +| **Communication Compliance Admins** | Use this role group to initially configure communication compliance and later to segregate communication compliance administrators into a defined group. Users assigned to this role group can create, read, update, and delete communication compliance policies, global settings, and role group assignments. Users assigned to this role group can't view message alerts. Users that create policies as a communication compliance administrator must have their mailbox hosted on Exchange Online.| +| **Communication Compliance Analysts** | Use this group to assign permissions to users that will act as communication compliance analysts. Users assigned to this role group can view policies where they're assigned as Reviewers, view message metadata (not message content), escalate to additional reviewers, or send notifications to users. Analysts can't resolve pending alerts. | +| **Communication Compliance Investigators** | Use this group to assign permissions to users that will act as communication compliance investigators. Users assigned to this role group can view message metadata and content, escalate to additional reviewers, escalate to an eDiscovery (Premium) case, send notifications to users, and resolve the alert. | +| **Communication Compliance Viewers** | Use this group to assign permissions to users that will manage communication reports. Users assigned to this role group can access all reporting widgets on the communication compliance home page and can view all communication compliance reports. | ### Option 1: Assign all compliance users to the Communication Compliance role group |
| compliance | Communication Compliance Investigate Remediate | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/communication-compliance-investigate-remediate.md | search.appverid: # Investigate and remediate communication compliance alerts +>[!IMPORTANT] +>Microsoft Purview Communication Compliance provides the tools to help organizations detect regulatory compliance violations (for example SEC or FINRA), such as sensitive or confidential information, harassing or threatening language, and sharing of adult content. Built with privacy by design, usernames are pseudonymized by default, role-based access controls are built in, investigators are opted in by an admin, and audit logs are in place to ensure user-level privacy. + After you've configured your [communication compliance policies](/microsoft-365/compliance/communication-compliance-policies), you'll start to receive alerts in the [Microsoft Purview compliance portal](https://compliance.microsoft.com) for message issues that match your policy conditions. To view and act on alerts, users must have the following permissions: - Be assigned to the *Communication Compliance Analysts* or the *Communication Compliance Investigators* role group After reviewing the message basics, it's time to open a message to examine the d - **Attachments**: This option allows you to examine Modern attachments that match policy conditions. Modern attachments content is extracted as text and is viewable on the Pending alerts dashboard for a policy. For more information, see the [Communication compliance feature reference](/microsoft-365/compliance/communication-compliance-channels). - **Source**: This view is the standard message view commonly seen in most web-based messaging platforms. The header information is formatted in the normal style and the message body supports imbedded graphic files and word-wrapped text. If [optical character recognition (OCR)](/microsoft-365/compliance/communication-compliance-policies#optical-character-recognition-ocr) is enabled for the policy, images containing printed or handwritten text that match policy conditional are viewed as a child item for the associated message in this view.-- **Plain text**: Text view that displays a line-numbered text-only view of the message and includes keyword highlighting in messages and attachments for sensitive info type terms, terms identified by built-in classifiers assigned to a policy, or for terms included in a dedicated keyword dictionary assigned to a policy. Keyword highlighting can help direct you to the area of interest in long messages and attachments. In some cases, highlighted text might be only in attachments for messages matching policy conditions. Embedded files aren't displayed and the line numbering in this view is helpful for referencing pertinent details among multiple reviewers.+- **Plain text**: Text view that displays a line-numbered text-only view of the message and includes keyword highlighting in messages and attachments for sensitive info type terms, terms identified by built-in classifiers assigned to a policy, or for terms included in a dedicated keyword dictionary assigned to a policy. Keyword highlighting, which is currently available for English language only, can help direct you to the area of interest in long messages and attachments. In some cases, highlighted text might be only in attachments for messages matching policy conditions. Embedded files aren't displayed and the line numbering in this view is helpful for referencing pertinent details among multiple reviewers. - **Conversation (preview)**: Available for Microsoft Teams chat messages, this view displays up to five messages before and after an alert message to help reviewers view the activity in the conversational context. This context helps reviewers to quickly evaluate messages and make more informed message resolution decisions. Real-time message additions to conversations are displayed, including all inline images, emojis, and stickers available in Teams. Image or text file attachments to messages aren't displayed. Notifications are automatically displayed for messages that have been edited or for messages that have been deleted from the conversation window. When a message is resolved, the associated conversational messages aren't retained with the resolved message. Conversation messages are available for up to 60 days after the alert message is identified. - **User history**: User history view displays all other alerts generated by any communication compliance policy for the user sending the message. - **Pattern detected notification**: Many harassing and bullying actions over time and involve reoccurring instances of the same behavior by a user. The *Pattern detected* notification is displayed in the alert details and raises attention to the alert. Detection of patterns is on a per-policy basis and evaluates behavior over the last 30 days when at least two messages are sent to the same recipient by a sender. Investigators and reviewers can use this notification to identify repeated behavior to evaluate the alert as appropriate. When messages are resolved, they're removed from the **Pending** tab view and di To unresolve messages, complete the following steps: -1. Sign into the [Microsoft Purview compliance portal](https://compliance.microsoft.com) using credentials for a user assigned to the *Communication Compliance Analyst* or *Communication Compliance Investigator* role groups in your Microsoft 365 organization. +1. Sign into the [Microsoft Purview compliance portal](https://compliance.microsoft.com) using credentials for a user assigned to the *Communication Compliance Analysts* or *Communication Compliance Investigators* role groups in your Microsoft 365 organization. 2. In the Microsoft Purview compliance portal, go to **Communication compliance**. 3. Select the **Policies** tab and then select a policy that contains the resolved alert message, double-click to open the **Policy** page. 4. On the **Policy** page, select the **Resolved** tab. |
| compliance | Communication Compliance Plan | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/communication-compliance-plan.md | search.appverid: # Plan for communication compliance +>[!IMPORTANT] +>Microsoft Purview Communication Compliance provides the tools to help organizations detect regulatory compliance violations (for example SEC or FINRA), such as sensitive or confidential information, harassing or threatening language, and sharing of adult content. Built with privacy by design, usernames are pseudonymized by default, role-based access controls are built in, investigators are opted in by an admin, and audit logs are in place to ensure user-level privacy. + Before getting started with [communication compliance](/microsoft-365/compliance/communication-compliance) in your organization, there are important planning activities and considerations that should be reviewed by your information technology and compliance management teams. Thoroughly understanding and planning for deployment in the following areas will help ensure that your implementation and use of communication compliance features goes smoothly and is aligned with the best practices for the solution. For more information and an overview of the planning process to address compliance and risky activities in your organization, see [Starting an insider risk management program](https://download.microsoft.com/download/b/2/0/b208282a-2482-4986-ba07-15a9b9286df0/pwc-starting-an-insider-risk-management-program-with-pwc-and-microsoft.pdf). There are six role groups used to configure initial permissions to manage commun - Microsoft Purview compliance portal [*Organization Management*](/microsoft-365/security/office-365-security/permissions-in-the-security-and-compliance-center) role group - Microsoft Purview compliance portal [*Compliance Administrator*](/microsoft-365/security/office-365-security/permissions-in-the-security-and-compliance-center) role group - *Communication Compliance* role group-- *Communication Compliance Admin* role group+- *Communication Compliance Admins* role group -Members of the following roles have the same solution permissions included with the *Communication Compliance Admin* role group: +Members of the following roles have the same solution permissions included with the *Communication Compliance Admins* role group: - Azure Active Directory *Global Administrator* - Azure Active Directory *Compliance Administrator* Members of the following roles have the same solution permissions included with - Microsoft Purview compliance portal *Compliance Administrator* > [!IMPORTANT]-> Make sure you always have at least one user in the *Communication Compliance* or *Communication Compliance Admin* role groups (depending on the option you choose) so that your communication compliance configuration doesn't get in to a 'zero administrator' scenario if specific users leave your organization. +> Make sure you always have at least one user in the *Communication Compliance* or *Communication Compliance Admins* role groups (depending on the option you choose) so that your communication compliance configuration doesn't get in to a 'zero administrator' scenario if specific users leave your organization. Depending on how you wish to manage communication compliance policies and alerts, you'll need to assign users to specific role groups to manage different sets of communication compliance features. You have the option to assign users with different compliance responsibilities to specific role groups to manage different areas of communication compliance features. Or you may decide to assign all user accounts for designated administrators, analysts, investigators, and viewers to the *Communication Compliance* role group. Use a single role group or multiple role groups to best fit your compliance management requirements. Choose from these solution role group options when configuring and managing comm |**Role**|**Role permissions**| |:--|:--| | **Communication Compliance** | Use this role group to manage communication compliance for your organization in a single group. By adding all user accounts for designated administrators, analysts, investigators, and viewers, you can configure communication compliance permissions in a single group. This role group contains all the communication compliance permission roles. This configuration is the easiest way to quickly get started with communication compliance and is a good fit for organizations that don't need separate permissions defined for separate groups of users. Users that create policies as a communication compliance administrator must have their mailbox hosted on Exchange Online. |-| **Communication Compliance Admin** | Use this role group to initially configure communication compliance and later to segregate communication compliance administrators into a defined group. Users assigned to this role group can create, read, update, and delete communication compliance policies, global settings, and role group assignments. Users assigned to this role group can't view message alerts. Users that create policies as a communication compliance administrator must have their mailbox hosted on Exchange Online. | -| **Communication Compliance Analyst** | Use this group to assign permissions to users that will act as communication compliance analysts. Users assigned to this role group can view policies where they're assigned as Reviewers, view message metadata (not message content), escalate to additional reviewers, or send notifications to users. Analysts can't resolve pending alerts. | -| **Communication Compliance Investigator** | Use this group to assign permissions to users that will act as communication compliance investigators. Users assigned to this role group can view message metadata and content, escalate to additional reviewers, escalate to an eDiscovery (Premium) case, send notifications to users, and resolve the alert. | -| **Communication Compliance Viewer** | Use this group to assign permissions to users that will manage communication reports. Users assigned to this role group can access all reporting widgets on the communication compliance home page and can view all communication compliance reports. | +| **Communication Compliance Admins** | Use this role group to initially configure communication compliance and later to segregate communication compliance administrators into a defined group. Users assigned to this role group can create, read, update, and delete communication compliance policies, global settings, and role group assignments. Users assigned to this role group can't view message alerts. Users that create policies as a communication compliance administrator must have their mailbox hosted on Exchange Online. | +| **Communication Compliance Analysts** | Use this group to assign permissions to users that will act as communication compliance analysts. Users assigned to this role group can view policies where they're assigned as Reviewers, view message metadata (not message content), escalate to additional reviewers, or send notifications to users. Analysts can't resolve pending alerts. | +| **Communication Compliance Investigators** | Use this group to assign permissions to users that will act as communication compliance investigators. Users assigned to this role group can view message metadata and content, escalate to additional reviewers, escalate to an eDiscovery (Premium) case, send notifications to users, and resolve the alert. | +| **Communication Compliance Viewers** | Use this group to assign permissions to users that will manage communication reports. Users assigned to this role group can access all reporting widgets on the communication compliance home page and can view all communication compliance reports. | ### Supervised users Before you start using communication compliance, you must determine who needs th ### Reviewers -When you create a communication compliance policy, you must determine who reviews the messages of the supervised users. In the policy, user email addresses identify individuals or groups of people to review supervised communications. All reviewers must have mailboxes hosted on Exchange Online, must be assigned to either the *Communication Compliance Analyst* or *Communication Compliance Investigator* role groups, and must be assigned in the policy they need to investigate. When reviewers are added to a policy, they automatically receive an email message that notifies them of the assignment to the policy and provides links to information about the review process. +When you create a communication compliance policy, you must determine who reviews the messages of the supervised users. In the policy, user email addresses identify individuals or groups of people to review supervised communications. All reviewers must have mailboxes hosted on Exchange Online, must be assigned to either the *Communication Compliance Analysts* or *Communication Compliance Investigators* role groups, and must be assigned in the policy they need to investigate. When reviewers are added to a policy, they automatically receive an email message that notifies them of the assignment to the policy and provides links to information about the review process. ### Groups for supervised users and reviewers Protecting the privacy of users that have policy matches is important and can he For users with a communication compliance match, you can choose one of the following settings in **Communication compliance settings**: -- **Show anonymized versions of usernames**: User names are anonymized to prevent users in *Communication Compliance Analyst* role group from seeing who is associated with policy alerts. Users in the *Communication Compliance Investigator* role group will always see user names, not the anonymized versions. For example, a user 'Grace Taylor' would appear with a randomized pseudonym such as 'AnonIS8-988' in all areas of the communication compliance experience. Choosing this setting anonymizes all users with current and past policy matches and applies to all policies. User profile information in the communication compliance alert details won't be available when this option is chosen. However, user names are displayed when adding new users to existing policies or when assigning users to new policies. If you choose to turn off this setting, user names are displayed for all users that have current or past policy matches.+- **Show anonymized versions of usernames**: User names are anonymized to prevent users in *Communication Compliance Analysts* role group from seeing who is associated with policy alerts. Users in the *Communication Compliance Investigators* role group will always see user names, not the anonymized versions. For example, a user 'Grace Taylor' would appear with a randomized pseudonym such as 'AnonIS8-988' in all areas of the communication compliance experience. Choosing this setting anonymizes all users with current and past policy matches and applies to all policies. User profile information in the communication compliance alert details won't be available when this option is chosen. However, user names are displayed when adding new users to existing policies or when assigning users to new policies. If you choose to turn off this setting, user names are displayed for all users that have current or past policy matches. - **Do not show anonymized versions of usernames**: User names are displayed for all current and past policy matches for communication compliance alerts. User profile information (the name, title, alias, and organization or department) is displayed for the user for all communication compliance alerts. ## Plan for policies |
| compliance | Communication Compliance Policies | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/communication-compliance-policies.md | search.appverid: # Create and manage communication compliance policies +>[!IMPORTANT] +>Microsoft Purview Communication Compliance provides the tools to help organizations detect regulatory compliance violations (for example SEC or FINRA), such as sensitive or confidential information, harassing or threatening language, and sharing of adult content. Built with privacy by design, usernames are pseudonymized by default, role-based access controls are built in, investigators are opted in by an admin, and audit logs are in place to ensure user-level privacy. + [!INCLUDE [purview-preview](../includes/purview-preview.md)] ## Policies search.appverid: > [!IMPORTANT] > Using PowerShell to create and manage communication compliance policies is not supported. To create and manage these policies, you must use the policy management controls in the [communication compliance solution](https://compliance.microsoft.com/supervisoryreview). -You create communication compliance policies for Microsoft 365 organizations in the Microsoft Purview compliance portal. Communication compliance policies define which communications and users are subject to review in your organization, define which custom conditions the communications must meet, and specify who should do reviews. Users assigned the *Communication Compliance Admin* role can set up policies, and anyone who has this role assigned can access the **Communication compliance** page and global settings in the Microsoft Purview compliance portal. If needed, you can export the history of modifications to a policy to a .csv (comma-separated values) file that also includes the status of alerts pending review, escalated items, and resolved items. Policies can't be renamed and can be deleted when no longer needed. +You create communication compliance policies for Microsoft 365 organizations in the Microsoft Purview compliance portal. Communication compliance policies define which communications and users are subject to review in your organization, define which custom conditions the communications must meet, and specify who should do reviews. Users assigned the *Communication Compliance Admins* role can set up policies, and anyone who has this role assigned can access the **Communication compliance** page and global settings in the Microsoft Purview compliance portal. If needed, you can export the history of modifications to a policy to a .csv (comma-separated values) file that also includes the status of alerts pending review, escalated items, and resolved items. Policies can't be renamed and can be deleted when no longer needed. ## Policy templates The *Report a concern* option is enabled by default and can be controlled via Te >[!IMPORTANT] >If you're using PowerShell to turn on or turn off the **End user reporting** option in the Teams Admin Center, you must use [Microsoft Teams cmdlets module version 4.2.0](/MicrosoftTeams/teams-powershell-release-notes) or later. +## Policy for insider risk management integration (preview) ++When users experience employment stressors, they may become disgruntled. This feeling may lead to uncharacteristic or malicious behavior by some users that could surface as potentially inappropriate behavior on your organization's messaging systems. Communication compliance can provide disgruntlement signals detected in applicable messages to [insider risk management](/microsoft-365/compliance/insider-risk-management) disgruntlement policies by using a dedicated [Detect inappropriate text](#policy-templates) policy. This policy is automatically created (if selected as an option) during configuration of a [Data leaks by disgruntled employees](/microsoft-365/compliance/insider-risk-management-policies#data-leaks-by-disgruntled-users-preview) or [Security policy violations by disgruntled employees](/microsoft-365/compliance/insider-risk-management-policies#security-policy-violations-by-disgruntled-users-preview) policy in insider risk management. ++When configured for an insider risk management disgruntlement policy, a dedicated policy named *Disgruntlement in messages - (date created)* is created in communication compliance and automatically includes all organization users in the policy. This policy starts detecting disgruntlement behavior in messages by using the built-in [Threat, Harassment, and Discrimination classifiers](#classifiers) and automatically sends these signals to insider risk management. If needed, this policy can be edited to update the scope of included users and the policy conditions and classifiers. ++Users that send 5 or more messages classified as disgruntled within 24 hours are automatically brought in-scope for insider risk management policies that include this option. Once in-scope, the insider risk management detect risky activities configured in the policy and generate alerts as applicable. It may take up to 48 hours from the time disgruntlement messages are sent until the time a user is brought in-scope in an insider risk management policy. If an alert is generated for a risky activity detected by the insider risk management policy, the triggering event for the alert is identified as being sourced from the communication compliance disgruntlement activity. ++All users assigned to the [Insider Risk Management Investigators](/microsoft-365/compliance/insider-risk-management-plan#plan-for-the-review-and-investigation-workflow) role group are automatically assigned as reviewers in the dedicated communication compliance policy. If inside risk management investigators need to review the associated disgruntlement alert directly on the communication compliance alerts page (linked from the insider risk management alert details), they must be manually added to the *Communication Compliance Investigators* role group. ++Before integrating communication compliance with insider risk management, you should also consider the following guidance when detecting messages containing potentially inappropriate text: ++- **For organizations without an existing *Detect inappropriate text* policy**. The new *Disgruntlement in messages - (date created)* policy will be automatically created by the insider risk management policy wizard. In most cases, no further actions are needed. +- **For organizations with an existing *Detect inappropriate text* policy**. The new *Disgruntlement in messages - (date created)* policy will be automatically created by the insider risk management policy wizard. Although you'll have two communication compliance policies for potentially inappropriate text in messages, investigators will not see duplicate alerts for the same activity. Insider risk management investigators will only see alerts for the dedicated integration policy and communication compliance investigators will only see the alerts for the existing policy. If needed, you can edit the dedicated policy to change the in-scope users or individual policy conditions as applicable. + ## Pause a policy -After you've created a communication compliance policy, the policy may be temporarily paused if needed. Pausing a policy may be used for testing or troubleshooting policy matches, or for optimizing policy conditions. Instead of deleting a policy in these circumstances, pausing a policy also preserves existing policy alerts and messages for ongoing investigations and reviews. Pausing a policy prevents inspection and alert generation for all user message conditions defined in the policy for the time the policy is paused. To pause or restart a policy, users must be a member of the *Communication Compliance Admin* role group. +After you've created a communication compliance policy, the policy may be temporarily paused if needed. Pausing a policy may be used for testing or troubleshooting policy matches, or for optimizing policy conditions. Instead of deleting a policy in these circumstances, pausing a policy also preserves existing policy alerts and messages for ongoing investigations and reviews. Pausing a policy prevents inspection and alert generation for all user message conditions defined in the policy for the time the policy is paused. To pause or restart a policy, users must be a member of the *Communication Compliance Admins* role group. To pause a policy, navigate to the **Policy** page, select a policy, and then select **Pause policy** from the actions toolbar. On the **Pause policy** pane, confirm you'd like to pause the policy by selecting **Pause**. In some cases, it may take up to 24 hours for a policy to be paused. Once the policy is paused, alerts for messages matching the policy aren't created. However, messages associated with alerts that were created prior to pausing the policy remain available for investigation, review, and remediation. For organizations with existing communication compliance policies, there may be - **Detect and review inappropriate messages for different groups of users**: Some organizations may prefer to create multiple policies with the same configuration but include different in-scope users and different reviewers for each policy. - **Similar policies with small changes**: For policies with complex configurations or conditions, it may save time to create a new policy from a similar policy. -To copy a policy, users must be a member of the *Communication Compliance* or *Communication Compliance Admin* role groups. After a new policy is created from an existing policy, it may take up to 24 hours to view messages that match the new policy configuration. +To copy a policy, users must be a member of the *Communication Compliance* or *Communication Compliance Admins* role groups. After a new policy is created from an existing policy, it may take up to 24 hours to view messages that match the new policy configuration. To copy a policy and create a new policy, complete the following steps: To identify an older policy, review *Last policy scan* column on the **Policy** ## Storage limit notification (preview) -Each communication compliance policy has a storage limit size of 100 GB or 1 million messages, whichever is reached first. As the policy approaches these limits, notification emails are automatically sent to users assigned to the *Communication Compliance* or *Communication Compliance Admin* role groups. Notifications messages are sent when the storage size or message count reach 80, 90, and 95 percent of the limit. When the policy limit is reached, the policy is automatically deactivated, and the policy stops processing messages for alerts. +Each communication compliance policy has a storage limit size of 100 GB or 1 million messages, whichever is reached first. As the policy approaches these limits, notification emails are automatically sent to users assigned to the *Communication Compliance* or *Communication Compliance Admins* role groups. Notifications messages are sent when the storage size or message count reach 80, 90, and 95 percent of the limit. When the policy limit is reached, the policy is automatically deactivated, and the policy stops processing messages for alerts. >[!IMPORTANT] >If a policy is deactivated due to reaching the storage and message limits, be sure to evaluate how to manage the deactivated policy. If you delete the policy, all messages, associated attachments, and message alerts will be permanently deleted. If you need to maintain these items for future use, do not delete the deactivated policy. The following table explains more about each condition. |:--|:--| | **Content matches any of these classifiers** | Apply to the policy when any classifiers are included or excluded in a message. Some classifiers are pre-defined in your organization, and custom classifiers must be configured separately before they're available for this condition. Only one classifier can be defined as a condition in a policy. For more information about configuring classifiers, see [Learn about trainable classifiers (preview)](/microsoft-365/compliance/classifier-learn-about). | | **Content contains any of these sensitive info types** | Apply to the policy when any sensitive information types are included or excluded in a message. Some classifiers are pre-defined in your tenant, and custom classifiers can be configured separately or as part of the condition assignment process. Each sensitive information type you choose is applied separately and only one of these sensitive information types must apply for the policy to apply to the message. For more information about custom sensitive information types, see [Learn about sensitive information types](/microsoft-365/compliance/sensitive-information-type-learn-about). |-| **Message is received from any of these domains** <br><br> **Message is not received from any of these domains** | Apply the policy to include or exclude specific domains or email addresses in received messages. Enter each domain or email address and separate multiple domains or email addresses with a comma. Each domain or email address entered is applied separately, only one domain or email address must apply for the policy to apply to the message. <br><br> If you want to scan all email from a specific domain, but want to exclude messages that don't need review (newsletters, announcements, and so on), you must configure a **Message is not received from any of these domains** condition that excludes the email address (example "newsletter@contoso.com"). | +| **Message is received from any of these domains** <br><br> **Message is not received from any of these domains** | Apply the policy to include or exclude specific domains in received messages. Enter each domain and separate multiple domains with a comma. Each domain entered is applied separately, only one domain must apply for the policy to apply to the message. If you want to use **Message is received from any of these domains** to look for messages from specific emails address you need to combine this with another condition like **Message contains any of these words** or **Content matches any of these classifiers** or you might get unexpected results. <br><br> If you want to scan all email from a specific domain, but want to exclude messages that don't need review (newsletters, announcements, and so on), you must configure a **Message is not received from any of these domains** condition that excludes the email address (example newsletter@contoso.com). | | **Message is sent to any of these domains** <br><br> **Message is not sent to any of these domains** | Apply the policy to include or exclude specific domains in sent messages. Enter each domain and separate multiple domains with a comma. Each domain is applied separately, only one domain must apply for the policy to apply to the message. <br><br> If you want to exclude all emails sent to two specific domains, you'd configure the **Message is not sent to any of these domains** condition with the two domains (example 'contoso.com,wingtiptoys.com'). | | **Message is classified with any of these labels** <br><br> **Message is not classified with any of these labels** | To apply the policy when certain retention labels are included or excluded in a message. Retention labels must be configured separately and configured labels are chosen as part of this condition. Each label you choose is applied separately (only one of these labels must apply for the policy to apply to the message). For more information about retention labels, see [Learn about retention policies and retention labels](/microsoft-365/compliance/retention).| | **Message contains any of these words** <br><br> **Message contains none of these words** | To apply the policy when certain words or phrases are included or excluded in a message, enter each word separated with a comma. For phrases of two words or more, use quotation marks around the phrase. Each word or phrase you enter is applied separately (only one word must apply for the policy to apply to the message). For more information about entering words or phrases, see the next section [Matching words and phrases to emails or attachments](#matching-words-and-phrases-to-emails-or-attachments).| |
| compliance | Communication Compliance Reports Audits | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/communication-compliance-reports-audits.md | search.appverid: # Use communication compliance reports and audits +>[!IMPORTANT] +>Microsoft Purview Communication Compliance provides the tools to help organizations detect regulatory compliance violations (for example SEC or FINRA), such as sensitive or confidential information, harassing or threatening language, and sharing of adult content. Built with privacy by design, usernames are pseudonymized by default, role-based access controls are built in, investigators are opted in by an admin, and audit logs are in place to ensure user-level privacy. + [!INCLUDE [purview-preview](../includes/purview-preview.md)] ## Reports In some instances, you must provide information to regulatory or compliance audi > [!IMPORTANT] > Auditing must be enabled for your organization before communication compliance events will be recorded. To enable auditing, see [Enable the audit log](/microsoft-365/compliance/communication-compliance-configure#step-2-required-enable-the-audit-log). When activities trigger events that are captured in the Microsoft 365 Audit log, it may take up to 48 hours before these events can be viewed in communication compliance policies. -To view communication compliance policy update activities, select the **Export policy updates** control on the main page for any policy. You must be assigned the *Global Admin* or *Communication Compliance Admin* roles to export update activities. This action generates an audit file in the .csv format that contains the following information: +To view communication compliance policy update activities, select the **Export policy updates** control on the main page for any policy. You must be assigned the *Global Admin* or *Communication Compliance Admins* roles to export update activities. This action generates an audit file in the .csv format that contains the following information: |Field|Details| ||| To view communication compliance policy update activities, select the **Export p | **Operations** | The update operations performed on the policy. | | **AuditData** | This field is the main data source for all policy update activities. All update activities are recorded and separated by comma delimiters. | -To view communication compliance review activities for a policy, select the **Export review activities** control on the **Overview** page for a specific policy. You must be assigned the *Global Admin* or *Communication Compliance Admin* roles to export review activities. This action generates an audit file in the .csv format that contains the following information: +To view communication compliance review activities for a policy, select the **Export review activities** control on the **Overview** page for a specific policy. You must be assigned the *Global Admin* or *Communication Compliance Admins* roles to export review activities. This action generates an audit file in the .csv format that contains the following information: |Field|Details| ||| |
| compliance | Communication Compliance Siem | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/communication-compliance-siem.md | search.appverid: # Use communication compliance with SIEM solutions +>[!IMPORTANT] +>Microsoft Purview Communication Compliance provides the tools to help organizations detect regulatory compliance violations (for example SEC or FINRA), such as sensitive or confidential information, harassing or threatening language, and sharing of adult content. Built with privacy by design, usernames are pseudonymized by default, role-based access controls are built in, investigators are opted in by an admin, and audit logs are in place to ensure user-level privacy. + [Communication compliance](/microsoft-365/compliance/communication-compliance) is an insider risk solution in Microsoft Purview that helps minimize communication risks by helping you detect, capture, and act on inappropriate messages in your organization. Security information and event management (SIEM) solutions such as [Microsoft Sentinel](https://azure.microsoft.com/services/azure-sentinel) or [Splunk](https://www.splunk.com/) are commonly used to aggregate and track threats within an organization. A common need for organizations is to integrate communication compliance alerts and these SIEM solutions. With this integration, organizations can view communication compliance alerts in their SIEM solution and then remediate alerts within the communication compliance workflow and user experience. For example, an employee sends an offensive message to another employee and that message is detected by a communication compliance policy for inappropriate content. These events are tracked in Microsoft 365 Audit (also known as "unified audit log") by the communication compliance solution and imported into the SIEM solution. An alert is then triggered in the SIEM solution for the organization from events included in Microsoft 365 Audit that are associated with communication compliance alerts. Investigators are notified of the alert in the SIEM solutions and then they investigate and remediate the alert in the communication compliance solution. |
| compliance | Communication Compliance Solution Overview | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/communication-compliance-solution-overview.md | +>[!IMPORTANT] +>Microsoft Purview Communication Compliance provides the tools to help organizations detect regulatory compliance violations (for example SEC or FINRA), such as sensitive or confidential information, harassing or threatening language, and sharing of adult content. Built with privacy by design, usernames are pseudonymized by default, role-based access controls are built in, investigators are opted in by an admin, and audit logs are in place to ensure user-level privacy. + Protecting sensitive information and detecting and acting on workplace harassment incidents is an important part of compliance with internal policies and standards. Microsoft Purview Communication Compliance helps minimize these risks by helping you quickly detect, capture, and take remediation actions for email and Microsoft Teams communications. These include inappropriate communications containing profanity, threats, and harassment and communications that share sensitive information inside and outside of your organization. [!INCLUDE [purview-preview](../includes/purview-preview.md)] |
| compliance | Communication Compliance | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/communication-compliance.md | search.appverid: # Learn about communication compliance +>[!IMPORTANT] +>Microsoft Purview Communication Compliance provides the tools to help organizations detect regulatory compliance violations (for example SEC or FINRA), such as sensitive or confidential information, harassing or threatening language, and sharing of adult content. Built with privacy by design, usernames are pseudonymized by default, role-based access controls are built in, investigators are opted in by an admin, and audit logs are in place to ensure user-level privacy. + Microsoft Purview Communication Compliance is an insider risk solution that helps minimize communication risks by helping you detect, capture, and act on inappropriate messages in your organization. Pre-defined and custom policies allow you to scan internal and external communications for policy matches so they can be examined by designated reviewers. Reviewers can investigate scanned email, Microsoft Teams, Yammer, or third-party communications in your organization and take appropriate actions to make sure they're compliant with your organization's message standards. Communication compliance policies in Microsoft 365 help you overcome many modern challenges associated with compliance and internal and external communications, including: Communication compliance policies scan and capture messages across several commu To learn more about messaging channel support in communication compliance policies, see [Detect channel signals with communication compliance](/microsoft-365/compliance/communication-compliance-channels). +## Integration with insider risk management (preview) ++Communication compliance can provide disgruntlement signals detected in messages to insider risk management disgruntlement policies. Using a dedicated [Detect inappropriate text](/microsoft-365/compliance/communication-compliance-policies#policy-templates) policy in communication compliance, you can choose to add this policy to a [Data leaks by disgruntled employees](/microsoft-365/compliance/insider-risk-management-policies#data-leaks-by-disgruntled-users-preview) or [Security policy violations by disgruntled employees](/microsoft-365/compliance/insider-risk-management-policies#security-policy-violations-by-disgruntled-users-preview) policy in insider risk management. Disgruntlement detected in messages by the communication compliance policy act as a triggering event to bring users into scope for the insider risk management policies. ++To learn more about integration with insider risk management, see [Create and manage communication compliance policies](/microsoft-365/compliance/communication-compliance-policies#integration-with-insider-risk-management-preview). +To learn more about insider risk management, see [Learn about insider risk management](/microsoft-365/compliance/insider-risk-management). + ## Get started with recommended actions (preview) Whether you're setting up communication compliance for the first time or getting started with creating new policies, the new [recommended actions](/microsoft-365/compliance/communication-compliance-configure#recommended-actions-preview) experience can help you get the most out of communication compliance capabilities. Recommended actions include setting up permissions, creating distribution groups, creating a policy, and more In this workflow step, you identify your compliance requirements and configure a You can choose from the following policy templates in the Microsoft Purview compliance portal: -- **Monitor for inappropriate text**: Use this template to quickly create a policy that uses built-in classifiers to automatically detect text in messages that may be considered inappropriate, abusive, or offensive.-- **Monitor for inappropriate images**: Use this template to quickly create a policy that uses built-in classifiers to automatically detect content that contains adult and racy images that may be considered as inappropriate in your organization.+- **Detect inappropriate text**: Use this template to quickly create a policy that uses built-in classifiers to automatically detect text in messages that may be considered inappropriate, abusive, or offensive. +- **Detect inappropriate images**: Use this template to quickly create a policy that uses built-in classifiers to automatically detect content that contains adult and racy images that may be considered as inappropriate in your organization. - **Monitor for sensitive information**: Use this template to quickly create a policy to scan communications containing defined sensitive information types or keywords to help make sure that important data isn't shared with people that shouldn't have access. - **Monitor for financial regulatory compliance**: Use this template to quickly create a policy to scan communications for references to standard financial terms associated with regulatory standards. - **Monitor for conflict of interest**: Use this template to quickly create a policy to detect communications between two groups or two users to help avoid conflicts of interest. |
| compliance | Dlp Configure Endpoint Settings | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/dlp-configure-endpoint-settings.md | You can use this logic to construct your exclusion paths for Windows 10 devices: - Valid file path that ends with `\`, which means only files directly under folder. <br/>For example: `C:\Temp\` -- Valid file path that ends with `\*`, which means only files under subfolders. Files directly under the folder are not excluded. <br/>For example: `C:\Temp\*`+- Valid file path that ends with `\*`, which means only files under subfolders. Files directly under the folder aren't excluded. <br/>For example: `C:\Temp\*` - Valid file path that ends without `\` or `\*`, which means all files directly under folder and all subfolders. <br/>For example: `C:\Temp` Similar to Windows 10 devices you can add your own exclusions for macOS devices. - Wildcard values are supported. So a path definition can contain a `*` in the middle of the path or at the end of the path. For example: `/Users/*/Library/Application Support/Microsoft/Teams/*` -##### Recommended file path exclusions (preview) +##### Recommended file path exclusions (preview) For performance reasons, Endpoint DLP includes a list of recommended file path exclusions for macOS devices. These exclusions are turned on by default. You can disable them if you want by toggling the **Include recommended file path exclusions for Mac** toggle. The list includes: When **Access by restricted apps** is selected in a policy and a user uses an ap #### File activities for apps in restricted app groups -Restricted app groups are collections of apps that you create in DLP settings and then add to a rule in a policy. When you add a restricted app group to a policy you can take the actions defined in this table. +Restricted app groups are collections of apps that you create in DLP settings and then add to a rule in a policy. When you add a restricted app group to a policy, you can take the actions defined in this table. |Restricted App group option |What it allows you to do | ||| The configurations of **Restricted app activities** and **File activities for al Here's an example: -If Notepad.exe is added to **Restricted appss** and **File activities for all apps** is configured to **Apply restrictions to specific activity** and both are configure like this: +If Notepad.exe is added to **Restricted apps** and **File activities for all apps** is configured to **Apply restrictions to specific activity** and both are configured like this: |Setting in policy |App name |User activity |DLP action to take | ||||| User A opens a DLP protected file using Notepad. DLP allows the access and audit ##### File activities for all apps only -If an app is not in **File activities for apps in restricted app groups** or is not in the **Restricted app activities** list or is in the **Restricted app activities** list with an action of `Audit only`, or 'Block with override`, any restrictions defined in the **File activities for all apps** are applied in the same rule. +If an app isn't in **File activities for apps in restricted app groups** or isn't in the **Restricted app activities** list or is in the **Restricted app activities** list with an action of `Audit only`, or 'Block with override`, any restrictions defined in the **File activities for all apps** are applied in the same rule. #### macOS devices Restrict sensitive files that match your policies from being shared with unrestr #### Unallowed browsers -For Windows devices you add browsers, identified by their executable names, that will be blocked from accessing files that match the conditions of an enforced a DLP policy where the upload to cloud services restriction is set to block or block override. When these browsers are blocked from accessing a file, the end users will see a toast notification asking them to open the file through Microsoft Edge. +For Windows devices, you add browsers, identified by their executable names, that will be blocked from accessing files that match the conditions of an enforced a DLP policy where the upload to cloud services restriction is set to block or block override. When these browsers are blocked from accessing a file, the end users will see a toast notification asking them to open the file through Microsoft Edge. For macOS devices, you must add the full file path. To find the full path of Mac apps: For macOS devices, you must add the full file path. To find the full path of Mac You can control whether sensitive files protected by your policies can be uploaded to specific service domains from Microsoft Edge. -If the list mode is set to **Block**, then user will not be able to upload sensitive items to those domains. When an upload action is blocked because an item matches a DLP policy, DLP will either generate a warning or block the upload of the sensitive item. +If the list mode is set to **Block**, then user won't be able to upload sensitive items to those domains. When an upload action is blocked because an item matches a DLP policy, DLP will either generate a warning or block the upload of the sensitive item. If the list mode is set to **Allow**, then users will be able to upload sensitive items ***only*** to those domains, and upload access to all other domains isn't allowed. For example: | Input | URL matching behavior | |||-| **CONTOSO.COM** |**Matches the specified domain name, and any subsite**: <p>*://contoso.com<p>*://contoso.com/ <p>*://contoso.com/anysubsite1 <p>*://contoso.com/anysubsite1/anysubsite2 (etc) <p>**Does not match sub-domains or unspecified domains**: <p>*://anysubdomain.contoso.com <p>*://anysubdomain.contoso.com.AU | -| ***.CONTOSO.COM** |**Matches the specified domain name, any subdomain, and any site**: <p>*://contoso.com <p>*://contoso.com/anysubsite <p>*://contoso.com/anysubsite1/anysubsite2 <p>*://anysubdomain.contoso.com/ <p>*://anysubdomain.contoso.com/anysubsite/ <p>*://anysubdomain1.anysubdomain2.contoso.com/anysubsite/ <p>*://anysubdomain1.anysubdomain2.contoso.com/anysubsite1/anysubsite2 (etc) <p>**Does not match unspecified domains** <p>*://anysubdomain.contoso.com.AU/ | +| **CONTOSO.COM** |**Matches the specified domain name, and any subsite**: <p>*://contoso.com<p>*://contoso.com/ <p>*://contoso.com/anysubsite1 <p>*://contoso.com/anysubsite1/anysubsite2 (etc.) <p>**Does not match sub-domains or unspecified domains**: <p>*://anysubdomain.contoso.com <p>*://anysubdomain.contoso.com.AU | +| ***.CONTOSO.COM** |**Matches the specified domain name, any subdomain, and any site**: <p>*://contoso.com <p>*://contoso.com/anysubsite <p>*://contoso.com/anysubsite1/anysubsite2 <p>*://anysubdomain.contoso.com/ <p>*://anysubdomain.contoso.com/anysubsite/ <p>*://anysubdomain1.anysubdomain2.contoso.com/anysubsite/ <p>*://anysubdomain1.anysubdomain2.contoso.com/anysubsite1/anysubsite2 (etc.) <p>**Does not match unspecified domains** <p>*://anysubdomain.contoso.com.AU/ | | **`www.contoso.com`** |**Matches the specified domain name**: <p>`www.contoso.com` <p>**Does not match unspecified domains or subdomains** <p>*://anysubdomain.contoso.com/, in this case, you have to put the FQDN domain name itself `www.contoso.com`| #### Sensitive service domains When you list a website in Sensitive services domains you can audit, block with - print from a website - copy data from a website - save a website as local files+- upload a sensitive file to an excluded website (this is configured in the policy) -Each website must be listed in a website group and the user must be accessing the website through Microsoft Edge. Sensitive service domains is used in conjunction with a DLP policy for Devices. See, [Scenario 6 Monitor or restrict user activities on sensitive service domains](endpoint-dlp-using.md#scenario-6-monitor-or-restrict-user-activities-on-sensitive-service-domains) for more information. +For the print, copy data and save actions, each website must be listed in a website group and the user must be accessing the website through Microsoft Edge. For the upload action, the user can be using Microsoft Edge or Google Chrome with the Purview extension. Sensitive service domains is used in conjunction with a DLP policy for Devices. You can also define website groups that you want to assign policy actions to that are different from the global website group actions. See, [Scenario 6 Monitor or restrict user activities on sensitive service domains](endpoint-dlp-using.md#scenario-6-monitor-or-restrict-user-activities-on-sensitive-service-domains) for more information. ### Additional settings for endpoint DLP By default, when devices are onboarded, activity for Office, PDF, and CSV files File activity will always be audited for onboarded devices, regardless of whether they're included in an active policy. +> [!IMPORTANT] +> Before you can use [Printer groups (preview)](#printer-groups-preview), [Removable storage device groups](#removable-storage-device-groups-preview), [Network share groups](#network-share-groups-preview), and [VPN settings](#vpn-settings-preview) you must register [here](https://forms.office.com/r/GNVTFvxuZv). ++### Printer groups (preview) ++Use this setting to define groups of printers that you want to assign policy actions to that are different from the global printing actions. For example, say you want your DLP policy to block printing of contracts to all printers, except for printers that are in the legal department. ++This feature is available for devices running any of the following Windows versions : ++- Windows 10 and later (20H2, 21H1, 21H2) +- Win 11 21H2, 22H2 +- Windows Server 2022 ++You define a printer by these parameters: ++- Friendly printer name - Get the Friendly printer name value from the printer device property details in device manager. +- USB product ID - Get the Device Instance path value from the printer device property details in device manager. Convert it to Product ID and Vendor ID format, see [Standard USB identifiers](/windows-hardware/drivers/install/standard-usb-identifiers). +- USB vendor ID - Get the Device Instance path value from the printer device property details in device manager. Convert it to Product ID and Vendor ID format, see [Standard USB identifiers](/windows-hardware/drivers/install/standard-usb-identifiers). +- IP range +- Print to file - For example Microsoft Print to PDF or Microsoft XPS Document Writer. +- Universal print deployed on a printer - See, [Set up Universal Print](/universal-print/fundamentals/universal-print-getting-started.md) for more information on universal printers +- Corporate printer - is a print queue shared through on-premises Windows print server in your domain. Its path might look like \\print-server\contoso.com\legal_printer_001 +- Print to local ++You assign each printer in the group a **Display name**. The name only appears in the Purview console. So, continuing with the example, you would create a printer group named **Legal printers** and add individual printers (with an alias) by their friendly name, like `legal_printer_001`, `legal_printer_002` and `legal_color_printer`. ++You can multi-select the parameters to help you unambiguously identify a specific printer. ++You can assign these policy actions to the group in a DLP policy: ++- Allow (audit with no user notifications or alerts) +- Audit only (you can add notifications and alerts) +- Block with override (blocks the action, but the user can override) +- Block (blocks no matter what) ++#### Create a Printer group ++1. Open [Microsoft Purview compliance portal](https://compliance.microsoft.com) > **Data loss prevention** > **Endpoint DLP settings** > **Printer groups**. +1. Select **Create printer group**. +1. Give the group a name. +1. Select **Add printer**. +1. Give the printer an **Alias that will only appear here. +1. Select the parameters and provide the values to unambiguously identify the specific printer. +1. Select **Add**. +1. Add other printers as needed. +1. Select **Close**. ++The most common use case is to use printers groups as an allowlist as in the above example for allowing the printing of contracts only to printers that are in the legal department. After you define a printer group here, it's available to be used in your policies that are scoped to **Devices**. See, [Scenario 7 Authorization groups](endpoint-dlp-using.md#scenario-7-authorization-groups-preview) for more information on configuring policy actions to use authorization groups. ++### Removable storage device groups (preview) ++Use this setting to define groups of removable storage devices, like USB thumb drives, that you want to assign policy actions to that are different from the global printing actions. For example, say you want your DLP policy to block copying of items with engineering specifications to all removeable storage devices, except for USB connected hard drives that are used to back up data and are then sent offsite. ++This feature is available for devices running any of the following Windows versions : ++- Windows 10 and later (20H2, 21H1, 21H2) +- Win 11 21H2, 22H2 +- Windows 10 RS5 (KB 5006744) and Windows Server 2022 ++You can define removeable storage devices by these parameters: ++- Storage device friendly name - Get the Friendly name value from the storage device property details in device manager. +- USB product ID - Get the Device Instance path value from the printer device property details in device manager. Convert it to Product ID and Vendor ID format, see [Standard USB identifiers](/windows-hardware/drivers/install/standard-usb-identifiers). +- USB vendor ID - Get the Device Instance path value from the printer device property details in device manager. Convert it to Product ID and Vendor ID format, see [Standard USB identifiers](/windows-hardware/drivers/install/standard-usb-identifiers). +- Serial number ID - Get the serial number ID value from the storage device property details in device manager. +- Device ID - Get the device ID value from the storage device property details in device manager. +- Instance path ID - Get the device ID value from the storage device property details in device manager. +- Hardware ID - Get the hardware ID value from the storage device property details in device manager. ++You assign each removable storage device in the group an **Alias**. The alias is a name that only appears in the Purview console. So, continuing with the example, you would create a removable storage device group named **Backup** and add individual devices (with an alias) by their friendly name, like `backup_drive_001`, and `backup_drive_002`. ++You can multi-select the parameters and the printer group will include all devices that satisfy those parameters. ++You can assign these policy actions to the group in a DLP policy: ++- Allow (audit with no user notifications or alerts) +- Audit only (you can add notifications and alerts) +- Block with override (blocks the action, but the user can override) +- Block (blocks no matter what) ++#### Create a Removable storage device group ++1. Open [Microsoft Purview compliance portal](https://compliance.microsoft.com) > **Data loss prevention** > **Endpoint DLP settings** > **Removable storage device groups**. +1. Select **Create removable storage device group**. +1. Provide a **Group name**. +1. Select **Add removable storage device**. +1. Provide an **Alias**. +1. Select the parameters and provide the values to unambiguously identify the specific device. +1. Select **Add**. +1. Add other devices to the group as needed. +1. Select **Close**. ++The most common use case is to use removable storage devices groups as an allowlist as in the above example for allowing the copying of files only to devices that are in the **Backup** group. After you define a removable storage device group here, it's available to be used in your policies that are scoped to **Devices**. See, [Scenario 7 Authorization groups](endpoint-dlp-using.md#scenario-7-authorization-groups-preview) for more information on configuring policy actions to use authorization groups. While scenario 7 uses printer authorization groups as an example, the principles are identical. The only thing that changes are the names of the groups and the actions you select. ++### Network share groups (preview) ++Use this setting to define groups of network share paths that you want to assign policy actions to that are different from the global network share path actions. For example, say you want your DLP policy to block when users attempt to save or copy protected files to network shares except the network shares in this group. +++This feature is available for devices running any of the following Windows versions: ++- Windows 10 and later (20H2, 21H1, 21H2) +- Win 11 21H2, 22H2 +- Windows 10 RS5 (KB 5006744) and Windows Server 2022 +++You include network share paths by defining the prefix that they all start with. For example: ++- '\\Library' will match: + - \Library folder and all its subfolders. ++- You can use Wildcards, for example '\\Users\*\Desktop' will match: + - '\\USers\user1\Desktop' + - '\\USers\user1\user2\Desktop' + - '\\Users\*\Desktop' ++- You can use Environmental variables, for example: + - %AppData%\app123 ++You can assign these policy actions to the group in a DLP policy: ++- Allow (audit with no user notifications or alerts) +- Audit only (you can add notifications and alerts) +- Block with override (blocks the action, but the user can override) +- Block (blocks no matter what) ++#### Create a Network Share group ++1. Open [Microsoft Purview compliance portal](https://compliance.microsoft.com) > **Data loss prevention** > **Endpoint DLP settings** > **Network share groups**. +1.Select **Create network share group**. +1. Provide a **Group name**. +1. Add the file path to the share. +1. Select **Add**. +1. Add other share paths to the group as needed. +1. Select **Close**. +++The most common use case is to use network share group as an allowlist as in the above example for allowing users to save or copy protected files only to the network shares that are defined in the group. After you define a networks share group here, it's available to be used in your policies that are scoped to **Devices**. See, [Scenario 7 Authorization groups](endpoint-dlp-using.md#scenario-7-authorization-groups-preview) for more information on configuring policy actions to use authorization groups. ++### VPN settings (preview) ++Use the VPN list to control only those actions that are being carried out over that VPN. ++This feature is available for devices running any of these versions of Windows: + +- Windows 10 and later (20H2, 21H1, 21H2) +- Windows 11 21H2, 22H2 +- Windows 10 RS5 (KB 5006744) ++When you list a VPN in **VPN Settings** you can assign these policy actions to them: ++- Allow (audit with no user notifications or alerts) +- Audit only (you can add notifications and alerts) +- Block with override (blocks the action, but the user can override) +- Block (blocks no matter what) ++These actions can be applied individually or collectively to these user activities: ++- Copy to clipboard +- Copy to a USB removable device +- Copy to a network share +- Print +- Copy or move using unallowed Bluetooth app +- Copy or move using RDP ++When configuring a DLP policy to restrict activity on devices, you can control what happens to each activity performed when users are connected to your organization within any of the VPNs listed. ++You define VPN by these parameters **Server address** or **Network address**. ++#### Get the Server address or Network address ++1. On a DLP monitored Windows device, open a **Windows PowerShell** window as an administrator. +1. Run this cmdlet ++```powershell-interactive +Get-VpnConnection +``` +3. Running this cmdlet returns multiple fields and values. +1. Find the **ServerAddress** field and record that value. You'll use this when you create a VPN entry in the VPN list. +1. Find the **Name** field and record that value. The **Name** field maps to the **Network address** field when you create a VPN entry in the VPN list. ++#### Add a VPN ++1. Open [Microsoft Purview compliance portal](https://compliance.microsoft.com) > **Data loss prevention** > **Endpoint DLP settings** > **VPN settings**. +1. Select **Add or edit VPN addresses**. +1. Provide either the **Server address** or **Network address** from running Get-VpnConnection. +1. Select **Save**. +1. Close the item. ++> [!IMPORTANT] +> When you use the VPN list in defining the actions of a policy, you will also see **Corporate network** as an option. **Corporate network** connections are are all connections to your organizations resources.These connections can include VPNs. ++See, [Scenario 8 Network exceptions](endpoint-dlp-using.md#scenario-8-network-exceptions-preview)for more information on configuring policy actions to use network exceptions. + ## See also - [Learn about Endpoint data loss prevention](endpoint-dlp-learn-about.md) |
| compliance | Endpoint Dlp Using | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/endpoint-dlp-using.md | These scenarios require that you already have devices onboarded and reporting in ## Scenario 4: Avoid looping DLP notifications from cloud synchronization apps with auto-quarantine (preview) -#[!INCLUDE [purview-preview](../includes/purview-preview.md)] --## Before you begin +## Before you begin scenario 4 In this scenario, synchronizing files with the **Highly Confidential** sensitivity label to OneDrive is blocked. This is a complex scenario with multiple components and procedures. You will need: There are three procedures. ## Scenario 5: Restrict unintentional sharing to unallowed cloud apps and services -With Endpoint DLP and Microisoft Edge Web browser, you can restrict unintentional sharing of sensitive items to unallowed cloud apps and services. Edge understands when an item is restricted by an Endpoint DLP policy and enforces access restrictions. +With Endpoint DLP and Microsoft Edge Web browser, you can restrict unintentional sharing of sensitive items to unallowed cloud apps and services. Edge understands when an item is restricted by an Endpoint DLP policy and enforces access restrictions. When you select **Devices** as a location in a properly configured DLP policy and use the Microsoft Edge browser, the unallowed browsers that you've defined in these settings will be prevented from accessing the sensitive items that match your DLP policy controls. Instead, users will be redirected to use Microsoft Edge which, with its understanding of DLP imposed restrictions, can block or restrict activities when the conditions in the DLP policy are met. Here are some examples: 1. Select **Save**. 1. Select **Policies**. 1. Create and scope a policy that is applied only to **Devices**. See, [Create, test, and tune a DLP policy](create-test-tune-dlp-policy.md) for more information on how to create a policy.-1. Create a rule that uses the **the user accessed a sensitive site from Edge**, and the action **Audit or restrict activities when users access sensitive sites in Microsoft Edge browser on Windows devices**. -1. In the action select **Add or remove Sensitive site groups**. +1. Create a rule that uses the **The user accessed a sensitive site from Edge**, and the action **Audit or restrict activities on devices**. +1. In **Service domain and browser activities** select **Upload to a restricted cloud service domain or access from an unallowed browser** and set the action to **Audit only**. This sets the overall action for all the site groups. 1. Select the **Sensitive site groups** you want. 1. Select **Add**.+1. OPTIONAL: If you want to create an exception (usually an allowlist) to the overall action for one or more site groups, select **Configure sensitive service domain exceptions**, add the site group you want the exception for, configure the desired action and **Save** the configuration. 1. Select the user activities you want to monitor or restrict and the actions you DLP to take in response to those activities. 1. Finish configuring the rule and policy and apply it. +## Scenario 7 Authorization groups (preview) ++> [!IMPORTANT] +> Before you can use **Printer groups**, **Removable storage device groups**, **Network share groups**, and **Network exceptions/VPN** you must register [here](https://forms.office.com/r/GNVTFvxuZv). ++These scenarios require that you already have devices onboarded and reporting into Activity explorer. If you haven't onboarded devices yet, see [Get started with Endpoint data loss prevention](endpoint-dlp-getting-started.md). ++Authorization groups are mostly used as allow lists. You assigned policy actions to the group that are different than the global policy actions. In this scenario, we'll go through defining a printer group and then configuring a policy with block actions for all print activities except for the printers in the group. These procedures are essentially the same for **Removeable storage device groups**, and **Network share groups**. ++In this scenario, we'll define a group of printers that the legal department uses for printing contracts. Printing contracts to any other printers is blocked. ++### Create and use printer groups ++1. In the Microsoft Purview compliance portal open **Data loss prevention** > **Endpoint DLP settings** > **Printer groups**. +1. Select **Create printer group** and give the group a name. In this scenarion, we'll use `Legal printers`. +1. Select **Add printer** and provide a name. You can define printers by: + 1. Friendly printer name + 1. USB product ID + 1. USB vendor ID + 1. IP range + 1. Print to file + 1. Universal print deployed on a printer + 1. Corporate printer + 1. Print to local +1. Select **Close**. ++### Configure policy printing actions ++1. Open the **Policies** tab. ++1. Select **Create policy** and select the custom policy template. +1. Scope the location to only **Devices**. ++1. Create a rule where: + 1. **Content contains** = **Trainable classifiers**, **Legal Affairs** + 1. **Actions** = **Audit or restrict activities on devices** + 1. Then pick **File activities on all apps** + 1. The select **Apply restrictions to specific activity** + 1. Select **Print** = **Block** +1. Select **Choose different print restrictions** +1. Under **Printer group restrictions**, select **Add group** and select **Legal printers**. +1. Set **Action** = **Allow**. + > [!TIP] + > The **Allow** action wil record and audit event to the audit log, but not generate an alert or notification. +10. Save. +11. Accept the default **I'd like to test it out first** value and choose **Show policy tips while in test mode**. Choose **Next**. ++12. Review your settings and choose **Submit**. ++13. The new DLP policy will appear in the policy list. ++## Scenario 8 Network exceptions (preview) ++> [!IMPORTANT] +> Before you can use **Printer groups**, **Removable storage device groups**, **Network share groups**, and **Network exceptions/VPN** you must register [here](https://forms.office.com/r/GNVTFvxuZv). ++These scenarios require that you already have devices onboarded and reporting into Activity explorer. If you haven't onboarded devices yet, see [Get started with Endpoint data loss prevention](endpoint-dlp-getting-started.md). ++In this scenario, we'll define a list of VPNs that hybrid workers use for accessing organization resources. +### Create and use a Network exception ++Network exceptions enables you to configure Allow, Audit only, Block with override, and Block actions to the file activities based on the network that users are accessing the file from. You can select from the [VPN settings](dlp-configure-endpoint-settings.md#vpn-settings-preview) list you defined and **Corporate network** option. The actions can be applied individually or collectively to these user activities: ++- Copy to clipboard +- Copy to a USB removable device +- Copy to a network share +- Print +- Copy or move using unallowed Bluetooth app +- Copy or move using RDP ++#### Get the Server address or Network address ++1. On a DLP monitored Windows device, open a **Windows PowerShell** window as an administrator. +1. Run this cmdlet ++```powershell-interactive +Get-VpnConnection +``` ++3. Running this cmdlet returns multiple fields and values. +1. Find the **ServerAddress** field and record that value. You'll use this when you create a VPN entry in the VPN list. +1. Find the **Name** field and record that value. The **Name** field maps to the **Network address** field when you create a VPN entry in the VPN list. ++#### Add a VPN ++1. Open [Microsoft Purview compliance portal](https://compliance.microsoft.com) > **Data loss prevention** > **Endpoint DLP settings** > **VPN settings**. +1. Select **Add or edit VPN addresses**. +1. Provide either the **Server address** or **Network address** from running Get-VpnConnection. +1. Select **Save**. +1. Close the item. ++#### Configure policy actions ++1. Open the **Policies** tab. ++1. Select **Create policy** and select the custom policy template. +1. Scope the location to only **Devices**. ++1. Create a rule where: + 1. **Content contains** = **Trainable classifiers**, **Legal Affairs** + 1. **Actions** = **Audit or restrict activities on devices** + 1. Then pick **File activities on all apps** + 1. The select **Apply restrictions to specific activity** + 1. Select the actions that you want to configure **Network exceptions** for. +1. Select **Copy to clipboard** and the **Audit only** action +1. Select **Choose different copy to clipboard restrictions**. +1. Select **VPN** and set the action to **Block with override**. ++> [!IMPORTANT] +> When you want to control the activities of a user when they're connected through a VPN *you must* select the VPN and make the VPN the top priority in the **Network exceptions** configuration. Otherwise, if the **Corporate network** option is selected, then that action defined for the **Corporate network** entry will be enforced. ++> [!CAUTION] +> The **Apply to all activities** option will copy the network exceptions that are defined here and apply them to all the other configured specific activities, like **Print**, and **Copy to a network share**. ***This will overwrite the network exceptions on the other activities The last saved configuration wins.*** ++8. Save. +1. Accept the default **I'd like to test it out first** value and choose **Show policy tips while in test mode**. Choose **Next**. ++1. Review your settings and choose **Submit**. ++1. The new DLP policy will appear in the policy list. + + ## See also - [Learn about Endpoint data loss prevention](endpoint-dlp-learn-about.md) |
| compliance | File Plan Manager | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/file-plan-manager.md | All columns except the label **Name** can be displayed or hidden by selecting th - Yes - Yes(Regulatory) -- **Is unlocked by default**ΓÇöcurrently rolling outΓÇöidentifies if the item marked as a record is unlocked when the label is applied. Valid values:+- **Is unlocked by default** identifies if the item marked as a record is unlocked when the label is applied. Valid values: - No - Yes -- **Relabel to**ΓÇöcurrently rolling outΓÇöidentifies if the label is configured to apply another label at the end of the retention period. Valid values:+- **Relabel to** identifies if the label is configured to apply another label at the end of the retention period. Valid values: - Blank or the selected label name - **Retention duration** identifies the retention period. Valid values: |
| compliance | Get Started With Sensitivity Labels | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/get-started-with-sensitivity-labels.md | description: "Prescriptive steps for admins, licensing requirements, and common For information about what sensitivity labels are and how they can help you protect your organization's data, see [Learn about sensitivity labels](sensitivity-labels.md). -If you have [Azure Information Protection](/azure/information-protection/what-is-information-protection) and are still using Azure Information Protection labels that were managed from the Azure portal, you must migrate these labels to the [unified labeling platform](/azure/information-protection/faqs#how-can-i-determine-if-my-tenant-is-on-the-unified-labeling-platform). For Windows computers, you can then [choose which labeling client to use](/azure/information-protection/rms-client/use-client#choose-which-labeling-client-to-use-for-windows-computers) for your published sensitivity labels. +If you have [Azure Information Protection](/azure/information-protection/what-is-information-protection) and are still using Azure Information Protection labels that were managed from the Azure portal, you must migrate these labels to the [unified labeling platform](/azure/information-protection/faqs#how-can-i-determine-if-my-tenant-is-on-the-unified-labeling-platform). We then recommend you disable the AIP add-in for Office apps, to benefit from the newer, built-in labeling experience. For more information, see [Migrate the Azure Information Protection (AIP) add-in to built-in labeling for Office apps](sensitivity-labels-aip.md). When you're ready to start protecting your organization's data by using sensitivity labels: |
| compliance | Import Epic Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/import-epic-data.md | The following table lists the fields that are required to enable insider risk ma The next step is to create an Epic connector in the compliance portal. After you run the script in Step 4, the text file that you created in Step 2 will be processed and pushed to the API endpoint you set up in Step 1. In this step, be sure to copy the JobId that's generated when you create the connector. You'll use the JobId when you run the script. -1. Go to <https://compliance.microsoft.com> and then click **Data connectors** in the left nav. +1. Go to <https://compliance.microsoft.com> and then select **Data connectors** in the left nav. -2. On the **Data connectors** page under **Epic connector**, click **View**. +2. On the **Data connectors** page under **Epic connector**, select **View**. -3. On the **Epic connector** page, click **Add connector**. +3. On the **Epic connector** page, select **Add connector**. -4. On the **Setup the connection** page, do the following and then click **Next**: +4. On the **Setup the connection** page, do the following and then select **Next**: 1. Type or paste the Azure AD application ID for the Azure app that you created in Step 2. 2. Type a name for the Epic connector. -5. On the **Review** page, review your settings and then click **Finish** to create the connector. +5. On the **Review** page, review your settings and then select **Finish** to create the connector. A status page is displayed that confirms the connector was created. This page contains two important things that you need to complete the next step to run the sample script to upload your Epic EHR audit records data. The next step is to create an Epic connector in the compliance portal. After you 2. **Reference schema.** Refer to the schema to understand which fields from your Epic system are accepted by connector. This will help you create a file with all the required Epic database fields. - 3. **Link to sample script.** Click the **here** link to go to the GitHub site to access the sample script (the link opens a new window). Keep this window open so that you can copy the script in Step 4. Alternatively, you can bookmark the destination or copy the URL so you can access it again when you run the script. This link is also available on the connector flyout page. + 3. **Link to sample script.** Select the **here** link to go to the GitHub site to access the sample script (the link opens a new window). Keep this window open so that you can copy the script in Step 4. Alternatively, you can bookmark the destination or copy the URL so you can access it again when you run the script. This link is also available on the connector flyout page. -6. Click **Done**. +6. Select **Done**. The new connector is displayed in the list on the **Connectors** tab. -7. Click the Epic connector that you just created to display the flyout page, which contains properties and other information about the connector. +7. Select the Epic connector that you just created to display the flyout page, which contains properties and other information about the connector. If you haven't already done so, you can copy the values for the **Azure App ID** and **Connector job ID**. You'll need these to run the script in the next step. You can also download the script from the flyout page (or download it using the link in the next step.) -You can also click **Edit** to change the Azure App ID or the column header names that you defined on the **File mapping** page. +You can also select **Edit** to change the Azure App ID or the column header names that you defined on the **File mapping** page. ## Step 4: Run the sample script to upload your Epic EHR audit records The last step in setting up an Epic connector is to run a sample script that wil 1. Go to window that you left open from the previous step to access the GitHub site with the sample script. Alternatively, open the bookmarked site or use the URL that you copied. You can also access the script [here](https://github.com/microsoft/m365-compliance-connector-sample-scripts/blob/main/sample_script.ps1). -2. Click the **Raw** button to display the script in text view. +2. Select the **Raw** button to display the script in text view. 3. Copy all the lines in the sample script and then save them to a text file. If the upload is successful, the script displays the **Upload Successful** messa After you create the Epic connector and push your EHR audit records, you can view the connector and upload status in the compliance portal. If you schedule the script to run automatically on a regular basis, you can also view the current status after the last time the script ran. -1. Go to <https://compliance.microsoft.com> and click **Data connectors** in the left nav. +1. Go to <https://compliance.microsoft.com> and select **Data connectors** in the left nav. -2. Click the **Connectors** tab and then select the Epic connector to display the flyout page. This page contains the properties and information about the connector. +2. Select the **Connectors** tab and then select the Epic connector to display the flyout page. This page contains the properties and information about the connector. -3. Under **Last import**, click the **Download log** link to open (or save) the status log for the connector. This log contains information about each time the script runs and uploads the data from the text file to the Microsoft cloud. +3. Under **Last import**, select the **Download log** link to open (or save) the status log for the connector. This log contains information about each time the script runs and uploads the data from the text file to the Microsoft cloud. Epic connector log file displays number rows from text file that were uploaded To make sure the latest audit records from your Epic EHR system are available to You can use the Task Scheduler app in Windows to automatically run the script every day. -1. On your local computer, click the Windows **Start** button and then type **Task Scheduler**. +1. On your local computer, select the Windows **Start** button and then type **Task Scheduler**. -2. Click the **Task Scheduler** app to open it. +2. Select the **Task Scheduler** app to open it. -3. In the **Actions** section, click **Create Task**. +3. In the **Actions** section, select **Create Task**. 4. On the **General** tab, type a descriptive name for the scheduled task; for example, **Epic connector script**. You can also add an optional description. You can use the Task Scheduler app in Windows to automatically run the script ev 2. Make sure that the **Run with the highest privileges** checkbox is selected. -6. Select the **Triggers** tab, click **New**, and then do the following things: +6. Select the **Triggers** tab, select **New**, and then do the following things: 1. Under **Settings**, select the **Daily** option, and then choose a date and time to run the script for the first time. The script will run every day at the same specified time. 2. Under **Advanced settings**, make sure the **Enabled** checkbox is selected. - 3. Click **Ok**. + 3. Select **Ok**. -7. Select the **Actions** tab, click **New**, and then do the following things: +7. Select the **Actions** tab, select **New**, and then do the following things:  1. In the **Action** dropdown list, make sure that **Start a program** is selected. - 2. In the **Program/script** box, click **Browse**, and go to the following location and select it so the path is displayed in the box: C:.0.exe. + 2. In the **Program/script** box, select **Browse**, and go to the following location and select it so the path is displayed in the box: C:.0.exe. 3. In the **Add arguments (optional)** box, paste the same script command that you ran in Step 4. For example, `.\EpicConnector.ps1 -tenantId "d5723623-11cf-4e2e-b5a5-01d1506273g9" -appId "c12823b7-b55a-4989-faba-02de41bb97c3" -appSecret "MNubVGbcQDkGCnn" -jobId "e081f4f4-3831-48d6-7bb3-fcfab1581458" -filePath "C:\Epic\audit\records.txt"` 4. In the **Start in (optional)** box, paste the folder location of the script that you ran in Step 4. For example, C:\Epic\audit. - 5. Click **Ok** to save the settings for the new action. + 5. Select **Ok** to save the settings for the new action. -8. In the **Create Task** window, click **Ok** to save the scheduled task. You might be prompted to enter your user account credentials. +8. In the **Create Task** window, select **Ok** to save the scheduled task. You might be prompted to enter your user account credentials. The new task is displayed in the Task Scheduler Library.  - The last time the script ran and the next time it's scheduled to run is displayed. You can double-click the task to edit it. + The last time the script ran and the next time it's scheduled to run is displayed. You can double-select the task to edit it. You can also verify the last time the script ran on the flyout page of the corresponding Epic connector in the compliance center. |
| compliance | Import Healthcare Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/import-healthcare-data.md | The following table lists the fields that are required to enable insider risk ma The next step is to create a Healthcare connector in the compliance portal. After you run the script in Step 4, the text file that you created in Step 2 will be processed and pushed to the API endpoint you set up in Step 1. In this step, be sure to copy the JobId that's generated when you create the connector. You'll use the JobId when you run the script. -1. Go to <https://compliance.microsoft.com> and then click **Data connectors** in the left nav. +1. Go to <https://compliance.microsoft.com> and then select **Data connectors** in the left nav. -2. On the **Overview** tab, click **Healthcare (preview)**. +2. On the **Overview** tab, select **Healthcare (preview)**. -3. On the **Healthcare (preview)** page, click **Add connector**. +3. On the **Healthcare (preview)** page, select **Add connector**. 4. Accept the terms of service. -5. On the **Authentication credentials** page, do the following and then click **Next**: +5. On the **Authentication credentials** page, do the following and then select **Next**: 1. Type or paste the Azure AD application ID for the Azure app that you created in Step 1. 2. Type a name for the healthcare connector. -6. On the **File mapping method** page, select one of the following options and then click **Next**. +6. On the **File mapping method** page, select one of the following options and then select **Next**. - - **Upload a sample file**. If you select this option, click **Upload sample file** to upload the file that you prepared in Step 2. This option allows you to quickly select column names in your text file from a drop-down list to map the columns to the required schema for the healthcare connector. + - **Upload a sample file**. If you select this option, select **Upload sample file** to upload the file that you prepared in Step 2. This option allows you to quickly select column names in your text file from a drop-down list to map the columns to the required schema for the healthcare connector. Or The next step is to create a Healthcare connector in the compliance portal. Afte - For each field, type the column name from the file that you prepared in Step 2 that corresponds to the field for the healthcare connector. -8. On the **Review** page, review your settings and then click **Finish** to create the connector. +8. On the **Review** page, review your settings and then select **Finish** to create the connector. A status page is displayed that confirms the connector was created. This page contains two important things that you need to complete the next step to run the sample script to upload your healthcare EHR auditing data. - **Job ID.** You'll need this job ID to run the script in the next step. You can copy it from this page or from the connector flyout page. - - **Link to sample script.** Click the **here** link to go to the GitHub site to access the sample script (the link opens a new window). Keep this window open so that you can copy the script in Step 4. Alternatively, you can bookmark the destination or copy the URL so you can access it again when you run the script. This link is also available on the connector flyout page. + - **Link to sample script.** Select the **here** link to go to the GitHub site to access the sample script (the link opens a new window). Keep this window open so that you can copy the script in Step 4. Alternatively, you can bookmark the destination or copy the URL so you can access it again when you run the script. This link is also available on the connector flyout page. -9. Click **Done**. +9. Select **Done**. The new connector is displayed in the list on the **Connectors** tab. -10. Click the Healthcare connector that you just created to display the flyout page, which contains properties and other information about the connector. +10. Select the Healthcare connector that you just created to display the flyout page, which contains properties and other information about the connector. If you haven't already done so, you can copy the values for the **Azure App ID** and **Connector job ID**. You'll need these to run the script in the next step. You can also download the script from the flyout page (or download it using the link in the next step.) -You can also click **Edit** to change the Azure App ID or the column header names that you defined on the **File mapping** page. +You can also select **Edit** to change the Azure App ID or the column header names that you defined on the **File mapping** page. ## Step 4: Run the sample script to upload your healthcare EHR auditing data The last step in setting up a Healthcare connector is to run a sample script tha 1. Go to window that you left open from the previous step to access the GitHub site with the sample script. Alternatively, open the bookmarked site or use the URL that you copied. You can also access the script [here](https://github.com/microsoft/m365-compliance-connector-sample-scripts/blob/main/sample_script.ps1). -2. Click the **Raw** button to display the script in text view. +2. Select the **Raw** button to display the script in text view. 3. Copy all the lines in the sample script and then save them to a text file. If the upload is successful, the script displays the **Upload Successful** messa After you create the Healthcare connector and push your EHR auditing data, you can view the connector and upload status in the compliance portal. If you schedule the script to run automatically on a regular basis, you can also view the current status after the last time the script ran. -1. Go to <https://compliance.microsoft.com> and click **Data connectors** in the left nav. +1. Go to <https://compliance.microsoft.com> and select **Data connectors** in the left nav. -2. Click the **Connectors** tab and then select the Healthcare connector to display the flyout page. This page contains the properties and information about the connector. +2. Select the **Connectors** tab and then select the Healthcare connector to display the flyout page. This page contains the properties and information about the connector. -3. Under **Last import**, click the **Download log** link to open (or save) the status log for the connector. This log contains information about each time the script runs and uploads the data from the text file to the Microsoft cloud. +3. Under **Last import**, select the **Download log** link to open (or save) the status log for the connector. This log contains information about each time the script runs and uploads the data from the text file to the Microsoft cloud. The `RecordsSaved` field indicates the number of rows in the text file that uploaded. For example, if the text file contains four rows, then the value of the `RecordsSaved` fields is 4, if the script successfully uploaded all the rows in the text file. To make sure the latest auditing data from your healthcare EHR system are availa You can use the Task Scheduler app in Windows to automatically run the script every day. -1. On your local computer, click the Windows **Start** button and then type **Task Scheduler**. +1. On your local computer, select the Windows **Start** button and then type **Task Scheduler**. -2. Click the **Task Scheduler** app to open it. +2. Select the **Task Scheduler** app to open it. -3. In the **Actions** section, click **Create Task**. +3. In the **Actions** section, select **Create Task**. 4. On the **General** tab, type a descriptive name for the scheduled task; for example, **Healthcare connector script**. You can also add an optional description. You can use the Task Scheduler app in Windows to automatically run the script ev 2. Make sure that the **Run with the highest privileges** checkbox is selected. -6. Select the **Triggers** tab, click **New**, and then do the following things: +6. Select the **Triggers** tab, select **New**, and then do the following things: 1. Under **Settings**, select the **Daily** option, and then choose a date and time to run the script for the first time. The script will run every day at the same specified time. 2. Under **Advanced settings**, make sure the **Enabled** checkbox is selected. - 3. Click **Ok**. + 3. Select **Ok**. -7. Select the **Actions** tab, click **New**, and then do the following things: +7. Select the **Actions** tab, select **New**, and then do the following things:  1. In the **Action** dropdown list, make sure that **Start a program** is selected. - 2. In the **Program/script** box, click **Browse**, and go to the following location and select it so the path is displayed in the box: C:.0.exe. + 2. In the **Program/script** box, select **Browse**, and go to the following location and select it so the path is displayed in the box: C:.0.exe. 3. In the **Add arguments (optional)** box, paste the same script command that you ran in Step 4. For example, `.\HealthcareConnector.ps1 -tenantId "d5723623-11cf-4e2e-b5a5-01d1506273g9" -appId "c12823b7-b55a-4989-faba-02de41bb97c3" -appSecret "MNubVGbcQDkGCnn" -jobId "e081f4f4-3831-48d6-7bb3-fcfab1581458" -filePath "C:\Healthcare\audit\records.txt"` 4. In the **Start in (optional)** box, paste the folder location of the script that you ran in Step 4. For example, C:\Healthcare\audit. - 5. Click **Ok** to save the settings for the new action. + 5. Select **Ok** to save the settings for the new action. -8. In the **Create Task** window, click **Ok** to save the scheduled task. You might be prompted to enter your user account credentials. +8. In the **Create Task** window, select **Ok** to save the scheduled task. You might be prompted to enter your user account credentials. The new task is displayed in the Task Scheduler Library.  - The last time the script ran and the next time it's scheduled to run is displayed. You can double-click the task to edit it. + The last time the script ran and the next time it's scheduled to run is displayed. You can double-select the task to edit it. You can also verify the last time the script ran on the flyout page of the corresponding Healthcare connector in the compliance center. |
| compliance | Import Hr Data US Government | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/import-hr-data-US-government.md | The next step is to create an HR connector in the compliance portal. After you r 1. Go to the compliance portal, and select <a href="https://go.microsoft.com/fwlink/p/?linkid=2173865" target="_blank">**Data connectors** page</a>. -2. On the **Data connectors** page under **HR**, click **View**. +2. On the **Data connectors** page under **HR**, select **View**. -3. On the **HR** page, click **Add connector**. +3. On the **HR** page, select **Add connector**. -4. On the **Authentication credentials** page, do the following and then click **Next**: +4. On the **Authentication credentials** page, do the following and then select **Next**: 1. Type or paste the Azure AD application ID for the Azure app that you created in Step 1. The next step is to create an HR connector in the compliance portal. After you r  -6. On the **Review** page, review your settings and then click **Finish** to create the connector. +6. On the **Review** page, review your settings and then select **Finish** to create the connector. A status page is displayed that confirms the connector was created. This page contains two important things that you need to complete the next step to run the sample script to upload your HR data. The next step is to create an HR connector in the compliance portal. After you r 1. **Job ID.** You'll need this job ID to run the script in the next step. You can copy it from this page or from the connector flyout page. - 1. **Link to sample script.** Click the **here** link to go to the GitHub site to access the sample script (the link opens a new window). Keep this window open so that you can copy the script in Step 4. Alternatively, you can bookmark the destination or copy the URL so you can access it again in Step 4. This link is also available on the connector flyout page. + 1. **Link to sample script.** Select the **here** link to go to the GitHub site to access the sample script (the link opens a new window). Keep this window open so that you can copy the script in Step 4. Alternatively, you can bookmark the destination or copy the URL so you can access it again in Step 4. This link is also available on the connector flyout page. -7. Click **Done**. +7. Select **Done**. The new connector is displayed in the list on the **Connectors** tab. -8. Click the HR connector that you just created to display the flyout page, which contains properties and other information about the connector. +8. Select the HR connector that you just created to display the flyout page, which contains properties and other information about the connector.  If you haven't already done so, you can copy the values for the **Azure App ID** and **Connector job ID**. You'll need these to run the script in the next step. You can also download the script from the flyout page (or download it using the link in the next step.) - You can also click **Edit** to change the Azure App ID or the column header names that you defined on the **File mapping** page. + You can also select **Edit** to change the Azure App ID or the column header names that you defined on the **File mapping** page. ## Step 4: Run the sample script to upload your HR data The last step in setting up an HR connector is to run a sample script that will 1. Go to window that you left open from the previous step to access the GitHub site with the sample script. Alternatively, open the bookmarked site or use the URL that you copied. -2. Click the **Raw** button to display the script in text view. +2. Select the **Raw** button to display the script in text view. 3. Copy all the lines in the sample script and then save them to a text file. After you create the HR connector and run the script to upload your HR data, you 1. Go to the compliance portal, and select <a href="https://go.microsoft.com/fwlink/p/?linkid=2173865" target="_blank">**Data connectors**</a>. -2. Click the **Connectors** tab and then select the HR connector to display the flyout page. This page contains the properties and information about the connector. +2. Select the **Connectors** tab and then select the HR connector to display the flyout page. This page contains the properties and information about the connector.  -3. Under **Progress**, click the **Download log** link to open (or save) the status log for the connector. This log contains information about each time the script runs and uploads the data from the CSV file to the Microsoft cloud. +3. Under **Progress**, select the **Download log** link to open (or save) the status log for the connector. This log contains information about each time the script runs and uploads the data from the CSV file to the Microsoft cloud.  To make sure the latest HR data from your organization is available to tools lik You can use the Task Scheduler app in Windows to automatically run the script every day. -1. On your local computer, click the Windows **Start** button and then type **Task Scheduler**. +1. On your local computer, select the Windows **Start** button and then type **Task Scheduler**. -2. Click the **Task Scheduler** app to open it. +2. Select the **Task Scheduler** app to open it. -3. In the **Actions** section, click **Create Task**. +3. In the **Actions** section, select **Create Task**. 4. On the **General** tab, type a descriptive name for the scheduled task; for example, **HR Connector Script**. You can also add an optional description. You can use the Task Scheduler app in Windows to automatically run the script ev 1. Make sure that the **Run with the highest privileges** checkbox is selected. -6. Select the **Triggers** tab, click **New**, and then do the following things: +6. Select the **Triggers** tab, select **New**, and then do the following things: 1. Under **Settings**, select the **Daily** option, and then choose a date and time to run the script for the first time. The script will run every day at the same specified time. 1. Under **Advanced settings**, make sure the **Enabled** checkbox is selected. - 1. Click **Ok**. + 1. Select **Ok**. -7. Select the **Actions** tab, click **New**, and then do the following things: +7. Select the **Actions** tab, select **New**, and then do the following things:  1. In the **Action** dropdown list, make sure that **Start a program** is selected. - 1. In the **Program/script** box, click **Browse**, and go to the following location and select it so the path is displayed in the box: `C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe`. + 1. In the **Program/script** box, select **Browse**, and go to the following location and select it so the path is displayed in the box: `C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe`. 1. In the **Add arguments (optional)** box, paste the same script command that you ran in Step 4. For example, `.\HRConnector.ps1 -tenantId "d5723623-11cf-4e2e-b5a5-01d1506273g9" -appId "c12823b7-b55a-4989-faba-02de41bb97c3" -appSecret "MNubVGbcQDkGCnn" -jobId "e081f4f4-3831-48d6-7bb3-fcfab1581458" -csvFilePath "C:\Users\contosoadmin\Desktop\Data\employee_termination_data.csv"` 1. In the **Start in (optional)** box, paste the folder location of the script that you ran in Step 4. For example, `C:\Users\contosoadmin\Desktop\Scripts`. - 1. Click **Ok** to save the settings for the new action. + 1. Select **Ok** to save the settings for the new action. -8. In the **Create Task** window, click **Ok** to save the scheduled task. You might be prompted to enter your user account credentials. +8. In the **Create Task** window, select **Ok** to save the scheduled task. You might be prompted to enter your user account credentials. The new task is displayed in the Task Scheduler Library.  - The last time the script ran and the next time it's scheduled to run is displayed. You can double-click the task to edit it. + The last time the script ran and the next time it's scheduled to run is displayed. You can double-select the task to edit it. You can also verify the last time the script ran on the flyout page of the corresponding HR connector in the compliance center. |
| compliance | Import Hr Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/import-hr-data.md | You can set up a data connector in the Microsoft Purview compliance portal to im Setting up a connector for HR data that insider risk management policies can use to generate risk indicators consists of creating a CSV file that contains that contains the HR data, creating an app in Azure Active Directory that's used for authentication, creating an HR data connector in the compliance portal, and then running a script (on a scheduled basis) that ingests the HR data in CSV files to the Microsoft cloud so it's available to the insider risk management solution. > [!IMPORTANT]-> A new version of the HR connector is now available for public preview. To create a new HR connector or to import data for the [new employee profile scenario](#csv-file-for-employee-profile-data-preview) for the healthcare policy scenario for insider risk management, go to the **Data connectors** page in the compliance portal, select the **Connectors** tab, and then click **Add a connector > HR (preview)** to start the set up. Existing HR connectors will continue to work without any disruption. +> A new version of the HR connector is now available for public preview. To create a new HR connector or to import data for the [new employee profile scenario](#csv-file-for-employee-profile-data-preview) for the healthcare policy scenario for insider risk management, go to the **Data connectors** page in the compliance portal, select the **Connectors** tab, and then select **Add a connector > HR (preview)** to start the set up. Existing HR connectors will continue to work without any disruption. [!INCLUDE [purview-preview](../includes/purview-preview.md)] Setting up a connector for HR data that insider risk management policies can use - Determine which HR scenarios and data to import to Microsoft 365. This will help you determine how many CSV files and HR connectors you'll need to create, and how to generate and structure the CSV files. The HR data that you import is determined by the insider risk management policies that you want to implement. For more information, see Step 1. -- Determine how to retrieve or export the data from your organization's HR system (and on a regular basis) and add it to the CSV files that you create in Step 1. The script that you run in Step 4 will upload the HR data in the CSV files to the Microsoft cloud.+- Determine how to retrieve or export the data from your organization's HR system (and regularly) and add it to the CSV files that you create in Step 1. The script that you run in Step 4 will upload the HR data in the CSV files to the Microsoft cloud. - The user who creates the HR connector 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](../security/office-365-security/permissions-in-the-security-and-compliance-center.md#roles-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](microsoft-365-compliance-center-permissions.md#create-a-custom-role-group). - The sample script that you run in Step 4 will upload your HR data to the Microsoft cloud so that it can be used by the insider risk management solution. This sample script isn't supported under any Microsoft standard support program or service. The sample script is provided AS IS without warranty of any kind. Microsoft further disclaims all implied warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample script and documentation remains with you. In no event shall Microsoft, its authors, or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample scripts or documentation, even if Microsoft has been advised of the possibility of such damages. -- This 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 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. For step-by-step instructions for setting up an HR connector in a GCC environment, see [Set up a connector to import HR data in US Government](import-hr-data-US-government.md).+- This 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. For step-by-step instructions for setting up an HR connector in a GCC environment, see [Set up a connector to import HR data in US Government](import-hr-data-US-government.md). ## Step 1: Prepare a CSV file with your HR data The following table describes each column in the CSV file for performance review ### CSV file for employee profile data (preview) > [!NOTE]-> The capability to create an HR connector for employee profile data is in public preview. To create an HR connector that supports employee profile data, go to the **Data connectors** page in the compliance portal, select the **Connectors** tab, and then click **Add a connector** > **HR (preview)**. Follow the steps to create a connector in [Step 3: Create the HR connector](#step-3-create-the-hr-connector). +> The capability to create an HR connector for employee profile data is in public preview. To create an HR connector that supports employee profile data, go to the **Data connectors** page in the compliance portal, select the **Connectors** tab, and then select **Add a connector** > **HR (preview)**. Follow the steps to create a connector in [Step 3: Create the HR connector](#step-3-create-the-hr-connector). Here's an example of a CSV file for the data for the employee profile data. Performance improvement plan,pillarp@contoso.com,,,2019-04-23T15:18:02.4675041+0 ### Adding the HRScenario column to a CSV file that contains a single data type -Based on your organization's HR systems and how you will export HR data to CSV file, you might have to create multiple CSV files that contain a single HR data type. In this case, you can still create a single HR connector to import data from different CSV files. To do this, you'll just have to add an HRScenario column to the CSV file and specify the HR data type. Then you can run the script for each CSV file, but use the same job ID for the connector. See [Step 4](#step-4-run-the-sample-script-to-upload-your-hr-data). +Based on your organization's HR systems and how you'll export HR data to CSV file, you might have to create multiple CSV files that contain a single HR data type. In this case, you can still create a single HR connector to import data from different CSV files. To do this, you'll just have to add an HRScenario column to the CSV file and specify the HR data type. Then you can run the script for each CSV file, but use the same job ID for the connector. See [Step 4](#step-4-run-the-sample-script-to-upload-your-hr-data). ## Step 2: Create an app in Azure Active Directory The next step is to create and register a new app in Azure Active Directory (Azure AD). The app will correspond to the HR connector that you create in Step 3. Creating this app will allow Azure AD to authenticate the HR connector when it runs and attempts to access your organization. This app will also be used to authenticate the script that you run in Step 4 to upload your HR data to the Microsoft cloud. During the creation of this Azure AD app, be sure to save the following information. These values will be used in Step 3 and Step 4. -- Azure AD application ID (also called the *app Id* or *client Id*)+- Azure AD application ID (also called the *app ID* or *client ID*) - Azure AD application secret (also called the *client secret*) -- Tenant Id (also called the *directory Id*)+- Tenant ID (also called the *directory Id*) For step-by-step instructions for creating an app in Azure AD, see [Register an application with the Microsoft identity platform](/azure/active-directory/develop/quickstart-register-app). After you complete this step, be sure to copy the job ID that's generated when y 1. Go to the compliance portal, and select <a href="https://go.microsoft.com/fwlink/p/?linkid=2173865" target="_blank">**Data connectors**</a>. -2. On the **Data connectors** page, click **HR (preview)**. +2. On the **Data connectors** page, select **HR (preview)**. -3. On the **HR (preview)** page, click **Add connector**. +3. On the **HR (preview)** page, select **Add connector**. -4. On the **Setup the connection** page, do the following and then click **Next**: +4. On the **Setup the connection** page, do the following and then select **Next**: 1. Type or paste the Azure AD application ID for the Azure app that you created in Step 2. 2. Type a name for the HR connector. -5. On the HR scenarios page, select one or more HR scenarios that you want to import data for and then click **Next**. +5. On the HR scenarios page, select one or more HR scenarios that you want to import data for and then select **Next**.  -6. On the file mapping method page, select a file type if necessary, and then select one of the following options and then click **Next**. +6. On the file mapping method page, select a file type if necessary, and then select one of the following options and then select **Next**. - - **Upload a sample file**. If you select this option, click **Upload sample file** to upload the CSV file that you prepared in Step 1. This option allows you to quickly select column names in your CSV file from a drop-down list to map them to the data types for the HR scenarios that you previously selected. + - **Upload a sample file**. If you select this option, select **Upload sample file** to upload the CSV file that you prepared in Step 1. This option allows you to quickly select column names in your CSV file from a drop-down list to map them to the data types for the HR scenarios that you previously selected. OR After you complete this step, be sure to copy the job ID that's generated when y 7. On the File mapping details page, do one of the following, depending on whether you uploaded a sample CSV file and whether you're configuring the connector for a single HR scenario or for multiple scenarios. If you uploaded a sample file, you don't have to type the column names. You pick them from a dropdown list. - - If you selected a single HR scenario in the previous step, then type the column header names (also called *parameters*) from the CSV file that you created in Step 1 in each of the appropriate boxes. The column names that you type are not case-sensitive, but be sure to include spaces if the column names in your CSV file include spaces. As previously explained, the names you type in these boxes must match the parameter names in your CSV file. For example, the following screenshot shows the parameter names from the sample CSV file for the employee resignation HR scenario shown in Step 1. + - If you selected a single HR scenario in the previous step, then type the column header names (also called *parameters*) from the CSV file that you created in Step 1 in each of the appropriate boxes. The column names that you type aren't case-sensitive, but be sure to include spaces if the column names in your CSV file include spaces. As previously explained, the names you type in these boxes must match the parameter names in your CSV file. For example, the following screenshot shows the parameter names from the sample CSV file for the employee resignation HR scenario shown in Step 1. - If you selected multiple data types in step above, then you need to enter identifier column name that will identify the HR data type in your CSV file. After entering the identifier column name, type the value that identifies this HR data type, and type the column header names for selected data types from the CSV file(s) that you created in Step 1 in each of the appropriate boxes for each selected data type. As previously explained, the names that you type in these boxes must match the column names in your CSV file. -8. On the **Review** page, review your settings and then click **Finish** to create the connector. +8. On the **Review** page, review your settings and then select **Finish** to create the connector. A status page is displayed that confirms the connector was created. This page contains two important things that you need to complete the next step to run the sample script to upload your HR data. After you complete this step, be sure to copy the job ID that's generated when y 1. **Job ID.** You'll need this job ID to run the script in the next step. You can copy it from this page or from the connector flyout page. - 2. **Link to sample script.** Click the **here** link to go to the GitHub site to access the sample script (the link opens a new window). Keep this window open so that you can copy the script in Step 4. Alternatively, you can bookmark the destination or copy the URL so you can access it again when you run the script. This link is also available on the connector flyout page. + 2. **Link to sample script.** Select the **here** link to go to the GitHub site to access the sample script (the link opens a new window). Keep this window open so that you can copy the script in Step 4. Alternatively, you can bookmark the destination or copy the URL so you can access it again when you run the script. This link is also available on the connector flyout page. -9. Click **Done**. +9. Select **Done**. The new connector is displayed in the list on the **Connectors** tab. -10. Click the HR connector that you just created to display the flyout page, which contains properties and other information about the connector. +10. Select the HR connector that you just created to display the flyout page, which contains properties and other information about the connector.  If you haven't already done so, you can copy the values for the **Azure App ID** and **Connector job ID**. You'll need these to run the script in the next step. You can also download the script from the flyout page (or download it using the link in the next step.) -You can also click **Edit** to change the Azure App ID or the column header names that you defined on the **File mapping** page. +You can also select **Edit** to change the Azure App ID or the column header names that you defined on the **File mapping** page. ## Step 4: Run the sample script to upload your HR data The last step in setting up an HR connector is to run a sample script that will 1. Go to window that you left open from the previous step to access the GitHub site with the sample script. Alternatively, open the bookmarked site or use the URL that you copied. You can also access the script [here](https://github.com/microsoft/m365-compliance-connector-sample-scripts/blob/main/sample_script.ps1). -2. Click the **Raw** button to display the script in text view. +2. Select the **Raw** button to display the script in text view. 3. Copy all the lines in the sample script and then save them to a text file. The last step in setting up an HR connector is to run a sample script that will | Parameter | Description | |:--|:--|:--|- |`tenantId`|This is the Id for your Microsoft 365 organization that you obtained in Step 2. You can also obtain the tenant Id for your organization on the **Overview** blade in the Azure AD admin center. This is used to identify your organization.| - |`appId` |This is the Azure AD application Id for the app that you created in Azure AD in Step 2. This is used by Azure AD for authentication when the script attempts to access your Microsoft 365 organization. | + |`tenantId`|This is the ID for your Microsoft 365 organization that you obtained in Step 2. You can also obtain the tenant ID for your organization on the **Overview** blade in the Azure AD admin center. This is used to identify your organization.| + |`appId` |This is the Azure AD application ID for the app that you created in Azure AD in Step 2. This is used by Azure AD for authentication when the script attempts to access your Microsoft 365 organization. | |`appSecret`|This is the Azure AD application secret for the app that you created in Azure AD in Step 2. This also used for authentication.| |`jobId`|This is the job ID for the HR connector that you created in Step 3. This is used to associate the HR data that is uploaded to the Microsoft cloud with the HR connector.| |`filePath`|This is the file path for the file (stored on the same system as the script) that you created in Step 1. Try to avoid spaces in the file path; otherwise use single quotation marks.| The last step in setting up an HR connector is to run a sample script that will ## Step 5: Monitor the HR connector -After you create the HR connector and run the script to upload your HR data, you can view the connector and upload status in the compliance portal. If you schedule the script to run automatically on a regular basis, you can also view the current status after the last time the script ran. +After you create the HR connector and run the script to upload your HR data, you can view the connector and upload status in the compliance portal. If you schedule the script to run automatically regularly, you can also view the current status after the last time the script ran. 1. Go to the compliance portal, and select <a href="https://go.microsoft.com/fwlink/p/?linkid=2173865" target="_blank">**Data connectors**</a>. -2. Click the **Connectors** tab and then select the HR connector to display the flyout page. This page contains the properties and information about the connector. +2. Select the **Connectors** tab and then select the HR connector to display the flyout page. This page contains the properties and information about the connector.  -3. Under **Progress**, click the **Download log** link to open (or save) the status log for the connector. This log contains information about each time the script runs and uploads the data from the CSV file to the Microsoft cloud. +3. Under **Progress**, select the **Download log** link to open (or save) the status log for the connector. This log contains information about each time the script runs and uploads the data from the CSV file to the Microsoft cloud.  To make sure the latest HR data from your organization is available to tools lik You can use the Task Scheduler app in Windows to automatically run the script every day. -1. On your local computer, click the Windows **Start** button and then type **Task Scheduler**. +1. On your local computer, select the Windows **Start** button and then type **Task Scheduler**. -2. Click the **Task Scheduler** app to open it. +2. Select the **Task Scheduler** app to open it. -3. In the **Actions** section, click **Create Task**. +3. In the **Actions** section, select **Create Task**. 4. On the **General** tab, type a descriptive name for the scheduled task; for example, **HR Connector Script**. You can also add an optional description. You can use the Task Scheduler app in Windows to automatically run the script ev 1. Make sure that the **Run with the highest privileges** checkbox is selected. -6. Select the **Triggers** tab, click **New**, and then do the following things: +6. Select the **Triggers** tab, select **New**, and then do the following things: 1. Under **Settings**, select the **Daily** option, and then choose a date and time to run the script for the first time. The script will run every day at the same specified time. 1. Under **Advanced settings**, make sure the **Enabled** checkbox is selected. - 1. Click **Ok**. + 1. Select **Ok**. -7. Select the **Actions** tab, click **New**, and then do the following things: +7. Select the **Actions** tab, select **New**, and then do the following things:  1. In the **Action** dropdown list, make sure that **Start a program** is selected. - 1. In the **Program/script** box, click **Browse**, and go to the following location and select it so the path is displayed in the box: `C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe`. + 1. In the **Program/script** box, select **Browse**, and go to the following location and select it so the path is displayed in the box: `C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe`. 1. In the **Add arguments (optional)** box, paste the same script command that you ran in Step 4. For example, `.\HRConnector.ps1 -tenantId "d5723623-11cf-4e2e-b5a5-01d1506273g9" -appId "c12823b7-b55a-4989-faba-02de41bb97c3" -appSecret "MNubVGbcQDkGCnn" -jobId "e081f4f4-3831-48d6-7bb3-fcfab1581458" -filePath "C:\Users\contosoadmin\Desktop\Data\employee_termination_data.csv"` 1. In the **Start in (optional)** box, paste the folder location of the script that you ran in Step 4. For example, `C:\Users\contosoadmin\Desktop\Scripts`. - 1. Click **Ok** to save the settings for the new action. + 1. Select **Ok** to save the settings for the new action. -8. In the **Create Task** window, click **Ok** to save the scheduled task. You might be prompted to enter your user account credentials. +8. In the **Create Task** window, select **Ok** to save the scheduled task. You might be prompted to enter your user account credentials. The new task is displayed in the Task Scheduler Library.  - The last time the script ran and the next time it's scheduled to run is displayed. You can double-click the task to edit it. + The last time the script ran and the next time it's scheduled to run is displayed. You can double-select the task to edit it. You can also verify the last time the script ran on the flyout page of the corresponding HR connector in the compliance center. +## (Optional) Step 7: Upload data using Power Automate templates ++You can upload HR data using Power Automate templates and define triggers. For example, you can configure a Power Automate template to trigger when new HR connector files are available in SharePoint or OneDrive locations. You can also streamline this process by storing confidential information like Azure AD application secret (created in **Step 2**) in Azure Key Vault and using it with Power Automate for authentication. ++Complete the following steps to automatically upload HR data when new files become available on OneDrive for Business: ++1. Download the *ImportHRDataforIRM.zip* package from the [GitHub site](https://github.com/microsoft/m365-compliance-connector-sample-scripts/blob/main/ImportHRDataforIRM.zip). +2. In [Power Automate](https://make.preview.powerautomate.com), navigate to **My flows**. +3. Select **Import** and upload the *ImportHRDataforIRM.zip* package. +4. After the package gets uploaded, update the content (name & OneDrive for Business connection), and select **Import**. ++  ++5. Select **Open flow** and update the parameters. The following table describes the parameters to use in this Power Automate Flow and their required values. The information you obtained in the previous steps is used in the values for these parameters. ++ |**Parameter**|**Description**| + |:|:--| + | App ID | This is the Azure AD application ID for the app that you created in Azure AD in **Step 2**. This is used by Azure AD for authentication when the script attempts to access your Microsoft 365 organization. | + | App Secret | This is the Azure AD application secret for the app that you created in Azure AD in **Step 2**. This used for authentication. | + | File location | This is the OneDrive for Business location where Power Automate monitors for 'new file created' activities to trigger this flow.| + | Job ID | Identifier for the HR connector created in **Step 3**. This is used to associate the HR data uploaded to the Microsoft cloud with the HR connector. | + | Tenant ID | Identifier for your Microsoft 365 organization obtained in **Step 2**. You can also obtain the tenant ID for your organization on the **Overview** blade in the Azure AD admin center. This is used to identify your organization. | + | URI | Verify that the value for this parameter is *https://webhook.ingestion.office.com/api/signals* | ++  ++6. Select **Save**. +7. Navigate to **Flow overview** and select **Turn on**. ++  ++8. Test the flow manually by uploading a new file to your OneDrive for Business folder and verify that it ran successfully. This may take a few minutes after the upload before the flow is triggered. ++  ++9. You can now monitor the HR connector as described in **Step 5**. ++If needed, you can update the flow to create triggers based on file availability and modification events on SharePoint and other data sources supported by Power Automate Flows. + ## Existing HR connectors -On December 13, 2021, we released the employee profile data scenario for HR connectors. If you created an HR connector before this date, we will migrate the existing instances or your organization's HR connectors so your HR data continues to be imported to the Microsoft cloud. You don't have to do anything to maintain this functionality. You can keep using these connectors without disruption. +On December 13, 2021, we released the employee profile data scenario for HR connectors. If you created an HR connector before this date, we'll migrate the existing instances or your organization's HR connectors so your HR data continues to be imported to the Microsoft cloud. You don't have to do anything to maintain this functionality. You can keep using these connectors without disruption. If you want to implement the employee profile data scenario, you create a new HR connector and configure it as required. After you create a new HR connector, run the script using the job ID of the new connector and CSV files with [employee profile data](#csv-file-for-employee-profile-data-preview) previously described in this article. |
| compliance | Import Physical Badging Data | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/import-physical-badging-data.md | The next step is to create a physical badging connector in the compliance portal 1. Go to the compliance portal, and select <a href="https://go.microsoft.com/fwlink/p/?linkid=2173865" target="_blank">**Data connectors**</a>. -2. On the **Data connectors** page under **Physical badging**, click **View**. +2. On the **Data connectors** page under **Physical badging**, select **View**. -3. On the **Physical badging** page, click **Add connector**. +3. On the **Physical badging** page, select **Add connector**. -4. On the **Authentication credentials** page, do the following and then click **Next**: +4. On the **Authentication credentials** page, do the following and then select **Next**: 1. Type or paste the Azure AD application ID for the Azure app that you created in Step 1. The next step is to create a physical badging connector in the compliance portal 3. Type a unique name for the physical badging connector. -5. On the **Review** page, review your settings and then click **Finish** to create the connector. +5. On the **Review** page, review your settings and then select **Finish** to create the connector. 6. A status page is displayed that confirms the connector was created. This page also contains the job ID. You can copy job ID from this page or from the flyout page for the connector. You need this job ID when running the script. The status page also contains a link to the script. Refer to this script to understand how to post the JSON file to the API endpoint. -7. Click **Done**. +7. Select **Done**. The new connector is displayed in the list on the **Connectors** tab. -8. Click the physical badging connector that you just created to display the flyout page, which contains properties and other information about the connector. +8. Select the physical badging connector that you just created to display the flyout page, which contains properties and other information about the connector. ## Step 4: Run the script to POST your JSON file containing physical badging data After you run the script, the JSON file containing the physical badging data is 1. Go to [this GitHub site](https://github.com/microsoft/m365-physical-badging-connector-sample-scripts/blob/master/push_physical_badging_records.ps1) to access the sample script. -2. Click the **Raw** button to display the script in text view +2. Select the **Raw** button to display the script in text view 3. Copy all the lines in the sample script and then save them to a text file. After you create the physical badging connector and push your physical badging d 1. Go to the compliance portal, and select <a href="https://go.microsoft.com/fwlink/p/?linkid=2173865" target="_blank">**Data connectors**</a>. -2. Click the **Connectors** tab and then select the physical badging connector to display the flyout page. This page contains the properties and information about the connector. +2. Select the **Connectors** tab and then select the physical badging connector to display the flyout page. This page contains the properties and information about the connector.  -3. Under **Last import**, click the **Download log** link to open (or save) the status log for the connector. This log contains information about each time the script runs and uploads the data from the JSON file to the Microsoft cloud. +3. Under **Last import**, select the **Download log** link to open (or save) the status log for the connector. This log contains information about each time the script runs and uploads the data from the JSON file to the Microsoft cloud.  To make sure the latest physical badging data from your organization is availabl You can use the Task Scheduler app in Windows to automatically run the script every day. -1. On your local computer, click the Windows **Start** button and then type **Task Scheduler**. +1. On your local computer, select the Windows **Start** button and then type **Task Scheduler**. -2. Click the **Task Scheduler** app to open it. +2. Select the **Task Scheduler** app to open it. -3. In the **Actions** section, click **Create Task**. +3. In the **Actions** section, select **Create Task**. 4. On the **General** tab, type a descriptive name for the scheduled task; for example, **physical badging connector Script**. You can also add an optional description. You can use the Task Scheduler app in Windows to automatically run the script ev 2. Make sure that the **Run with the highest privileges** checkbox is selected. -6. Select the **Triggers** tab, click **New**, and then do the following things: +6. Select the **Triggers** tab, select **New**, and then do the following things: 1. Under **Settings**, select the **Daily** option, and then choose a date and time to run the script for the first time. The script will run every day at the same specified time. 2. Under **Advanced settings**, make sure the **Enabled** checkbox is selected. - 3. Click **Ok**. + 3. Select **Ok**. -7. Select the **Actions** tab, click **New**, and then do the following things: +7. Select the **Actions** tab, select **New**, and then do the following things:  1. In the **Action** dropdown list, make sure that **Start a program** is selected. - 2. In the **Program/script** box, click **Browse**, and go to the following location and select it so the path is displayed in the box: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe. + 2. In the **Program/script** box, select **Browse**, and go to the following location and select it so the path is displayed in the box: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe. 3. In the **Add arguments (optional)** box, paste the same script command that you ran in Step 4. For example, .\PhysicalBadging.ps1-tenantId "d5723623-11cf-4e2e-b5a5-01d1506273g9" -appId "c12823b7-b55a-4989-faba-02de41bb97c3" -appSecret "MNubVGbcQDkGCnn" -jobId "e081f4f4-3831-48d6-7bb3-fcfab1581458" -jsonFilePath "C:\Users\contosoadmin\Desktop\Data\physical_badging_data.json" 4. In the **Start in (optional)** box, paste the folder location of the script that you ran in Step 4. For example, C:\Users\contosoadmin\Desktop\Scripts. - 5. Click **Ok** to save the settings for the new action. + 5. Select **Ok** to save the settings for the new action. -8. In the **Create Task** window, click **Ok** to save the scheduled task. You might be prompted to enter your user account credentials. +8. In the **Create Task** window, select **Ok** to save the scheduled task. You might be prompted to enter your user account credentials. The new task is displayed in the Task Scheduler Library.  -The last time the script ran and the next time it's scheduled to run is displayed. You can double-click the task to edit it. +The last time the script ran and the next time it's scheduled to run is displayed. You can double-select the task to edit it. You can also verify the last time the script ran on the flyout page of the corresponding physical badging connector in the compliance center. |
| compliance | Insider Risk Management Activities | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/insider-risk-management-activities.md | +>[!IMPORTANT] +>Microsoft Purview Insider Risk Management correlates various signals to identify potential malicious or inadvertent insider risks, such as IP theft, data leakage and security violations. Insider risk management enables customers to create policies to manage security and compliance. Built with privacy by design, users are pseudonymized by default, and role-based access controls and audit logs are in place to help ensure user-level privacy. + Investigating risky user activities is an important first step in minimizing insider risks for your organization. These risks may be activities that generate alerts from insider risk management policies, or risks from activities that are detected by policies but don't immediately create an insider risk management alert for users. You can investigate these types of activities by using the **User activity reports (preview)** or with the **Alert dashboard**. [!INCLUDE [purview-preview](../includes/purview-preview.md)] Use the following sections and tabs on the Alert detail page for more informatio This section contains general information about the user and alert. This information is available for context while reviewing detailed information about the detected activity included in the alert for the user: - **Activity that generated this alert**: Displays the top risk activity and policy match during the activity evaluation period that led to the alert being generated.-- **Triggering event**: Displays the most recent triggering event that prompted the policy to start assigning risk scores to the user's activity.+- **Triggering event**: Displays the most recent triggering event that prompted the policy to start assigning risk scores to the user's activity. If you've configured [integration with communication compliance](/microsoft-365/compliance/communication-compliance-policies#integration-with-insider-risk-management-preview) for *Data leaks by disgruntled users* or *Security policy violations by disgruntled users* policies, the triggering event for these alerts will be scoped to communication compliance activity. - **User profile**: Displays general information about the user assigned to the alert. If anonymization is enabled, the username, email address, alias, and organization fields are anonymized. - **User alert history**: Displays a list of alerts for the user for the last 30 days. Includes a link to view the complete alert history for the user. +Alerts generated from policies scoped to only activities that include [priority content](/microsoft-365/compliance/insider-risk-management-policies#prioritize-content-in-policies) include the *Only activity with priority content was scored for this alert* notification in this section. + ### All risk factors This tab opens the summary of risk factors for the user's alert activity. Risk factors can help you determine how risky this user's activity is during your review. The risk factors include summaries for: The **User activity** chart is one of the most powerful tools for internal risk - **Risk category**: Filter activities by the following risk categories: *Activities with risk scores > 15 (unless in a sequence)* and *Sequence activities*. - **Activity Type**: Filter activities by the following types: *Access*, *Deletion*, *Collection*, *Exfiltration*, *Infiltration*, *Obfuscation*, and *Security*. - **Sort by**: List the timeline activities by *Date occurred* or *Risk score*.-4. **Risk sequence**: The chronological order of risky activities is an important aspect of risk investigation and identifying these related activities is an important part of evaluating overall risk for your organization. Alert activities that are related are displayed with connecting lines to highlight that these activities are associated with a larger risk area. This view of activities can help investigators literally 'connect the dots' for risk activities that could have been viewed as isolated or one-off events. Select any bubble in the sequence to display details for all the associated risk activities. Details include: +4. **Risk sequence**: The chronological order of risky activities is an important aspect of risk investigation and identifying these related activities is an important part of evaluating overall risk for your organization. Alert activities that are related are displayed with connecting lines to highlight that these activities are associated with a larger risk area. Sequences are also identified in this view by an icon positioned above the sequence activities relative to the risk score for the sequence. Hover over the icon to see the date and time of the risky activity associated with this sequence. This view of activities can help investigators literally 'connect the dots' for risk activities that could have been viewed as isolated or one-off events. Select the icon or any bubble in the sequence to display details for all the associated risk activities. Details include: - **Name** of the sequence. - **Date** or **Date range** of the sequence. Becoming overwhelmed with the number of alerts produced by your insider risk man - **Adjust your insider risk policies**: Selecting and configuring the correct insider risk policy is the most basic method to address the type and volume of alerts. Starting with the appropriate [policy template](insider-risk-management-policies.md#policy-templates) helps focus the types of risk activities and alerts you'll see. Other factors that may impact alert volume are the size of the in-scope user and groups and the content and [channels that are prioritized](insider-risk-management-policies.md#prioritize-content-in-policies). Consider adjusting policies to refine these areas to what is most important for your organization. - **Modify your insider risk settings**: Insider risk settings include a wide variety of configuration options that can impact the volume and types of alerts you'll receive. These include settings for [policy indicators](insider-risk-management-settings.md#indicators), [indicator thresholds](insider-risk-management-settings.md#indicator-level-settings-preview), and [policy timeframes](insider-risk-management-settings.md#policy-timeframes). Consider configuring [intelligent detections](insider-risk-management-settings.md#intelligent-detections) options to exclude specific file types, define minimum thresholds before activity alerts are reported by your policies, and changing the alert volume configuration to a lower setting.+- **Enable inline alert customization (preview)**: Enabling [inline alert customization](/microsoft-365/compliance/insider-risk-management-settings#inline-alert-customization-preview) allows analysts and investigators to quickly edit policies when reviewing alerts. They can update thresholds for activity detection with Microsoft recommendations, configure custom thresholds, or choose to ignore the type of activity that created the alert. If this is not enabled, then only users assigned to the *Insider Risk Management* role group can use inline alert customization. - **Bulk deletion of alerts where applicable**: It may help save triage time for your analysts and investigators to immediately [dismiss multiple alerts](insider-risk-management-activities.md#dismiss-multiple-alerts-preview) at once. You can select up to 400 alerts to dismiss at one time. ### Not familiar with the alert triage process |
| compliance | Insider Risk Management Audit Log | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/insider-risk-management-audit-log.md | +>[!IMPORTANT] +>Microsoft Purview Insider Risk Management correlates various signals to identify potential malicious or inadvertent insider risks, such as IP theft, data leakage and security violations. Insider risk management enables customers to create policies to manage security and compliance. Built with privacy by design, users are pseudonymized by default, and role-based access controls and audit logs are in place to help ensure user-level privacy. + The insider risk management audit log enables you to stay informed on the actions that were taken on insider risk management features. This log allows independent review of the actions taken by users assigned to one or more insider risk management role groups. The insider risk management audit log is automatically enabled in your organization and cannot be disabled.  |
| compliance | Insider Risk Management Browser Support | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/insider-risk-management-browser-support.md | +>[!IMPORTANT] +>Microsoft Purview Insider Risk Management correlates various signals to identify potential malicious or inadvertent insider risks, such as IP theft, data leakage and security violations. Insider risk management enables customers to create policies to manage security and compliance. Built with privacy by design, users are pseudonymized by default, and role-based access controls and audit logs are in place to help ensure user-level privacy. + Web browsers are often used by users to access both sensitive and non-sensitive files within an organization. Insider risk management allows your organization to detect and act on browser exfiltration signals for all non-executable files viewed in [Microsoft Edge](https://www.microsoft.com/edge) and [Google Chrome](https://www.google.com/chrome) browsers. With these signals, analysts and investigators can quickly act when any of the following activities are performed by in-scope policy users when using these browsers: - Files copied to personal cloud storage |
| compliance | Insider Risk Management Cases | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/insider-risk-management-cases.md | +>[!IMPORTANT] +>Microsoft Purview Insider Risk Management correlates various signals to identify potential malicious or inadvertent insider risks, such as IP theft, data leakage and security violations. Insider risk management enables customers to create policies to manage security and compliance. Built with privacy by design, users are pseudonymized by default, and role-based access controls and audit logs are in place to help ensure user-level privacy. + Cases are the heart of insider risk management and allow you to deeply investigate and act on issues generated by risk indicators defined in your policies. Cases are manually created from alerts in situations where further action is needed to address a compliance-related issue for a user. Each case is scoped to a single user and multiple alerts for the user can be added to an existing case or to a new case. After investigating the details of a case, you can take action by: |
| compliance | Insider Risk Management Configure | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/insider-risk-management-configure.md | +>[!IMPORTANT] +>Microsoft Purview Insider Risk Management correlates various signals to identify potential malicious or inadvertent insider risks, such as IP theft, data leakage and security violations. Insider risk management enables customers to create policies to manage security and compliance. Built with privacy by design, users are pseudonymized by default, and role-based access controls and audit logs are in place to help ensure user-level privacy. + Use insider risk management policies to identify risky activities and management tools to act on risk alerts in your organization. Complete the following steps to set up prerequisites and configure an insider risk management policy. > [!IMPORTANT] Insider risk management policies include assigned users and define which types o 4. Select **Next** to continue. 5. On the **Name and description** page, complete the following fields:- - **Name (required)**: Enter a friendly name for the policy. This name canΓÇÖt be changed after the policy is created. + - **Name (required)**: Enter a friendly name for the policy. This name can't be changed after the policy is created. - **Description (optional)**: Enter a description for the policy. 6. Select **Next** to continue. Insider risk management policies include assigned users and define which types o 8. Select **Next** to continue. 9. On the **Content to prioritize** page, you can assign (if needed) the sources to prioritize, which increases the chance of generating a high severity alert for these sources. Select one of the following choices: - - **I want to specify SharePoint sites, sensitivity labels, sensitive information types and/or file extensions as priority content**. Selecting this option will enable detail pages in the wizard to configure these channels. - - **I don't want to specify priority content right now (you'll be able to do this after the policy is created)**. Selecting this option will skip the channel detail pages in the wizard. + - **I want to prioritize content**. Selecting this option will enable you to prioritize *SharePoint sites*, *Sensitivity labels*, *Sensitive info types*, and *File extensions* content types. If you choose this option, you must select at least one priority content type. + - **I don't want to specify priority content right now**. Selecting this option will skip the priority content detail pages in the wizard. 10. Select **Next** to continue. -11. If you've selected **I want to specify SharePoint sites, sensitivity labels, sensitive information types and/or file extensions as priority content** in the previous step, you'll see the detail pages for *SharePoint sites*, *sensitive info types*, *sensitivity labels* and *file extensions*. Use these detail pages to define the SharePoint, sensitive info types, sensitivity labels, and file extensions to prioritize in the policy. +11. If you've selected **I want to prioritize content** in the previous step, you'll see the detail pages for *SharePoint sites*, *sensitive info types*, *sensitivity labels*, *file extensions*, and *Scoring*. Use these detail pages to define the SharePoint, sensitive info types, sensitivity labels, and file extensions to prioritize in the policy. The *Scoring* detail page allows you to scope the policy to only assign risk scores and generate alerts for specified activities that include priority content. - **SharePoint sites**: Select **Add SharePoint site** and select the SharePoint sites you have access to and want to prioritize. For example, *"group1@contoso.sharepoint.com/sites/group1"*. - **Sensitive info type**: Select **Add sensitive info type** and select the sensitivity types you want to prioritize. For example, *"U.S. Bank Account Number"* and *"Credit Card Number"*. - **Sensitivity labels**: Select **Add sensitivity label** and select the labels you want to prioritize. For example, *"Confidential"* and *"Secret"*.- - File extensions: Add up to 50 file extensions. You can include or omit the '.' with the file extension. For example, *.py* or *py* would prioritize Python files. + - **File extensions**: Add up to 50 file extensions. You can include or omit the '.' with the file extension. For example, *.py* or *py* would prioritize Python files. + - **Scoring**: Decide whether to assign risk scores to all activities detected by this policy or only for activities that include priority content. Choose **Get alerts for all activity** or **Get alerts only for activity that includes priority content**. > [!NOTE] > Users configuring the policy and selecting priority SharePoint sites can select SharePoint sites that they have permission to access. If SharePoint sites aren't available for selection in the policy by the current user, another user with the required permissions can select the sites for the policy later or the current user should be given access to the required sites. 12. Select **Next** to continue.-13. If you've selected the *General data leaks* or *Data leaks by priority users* templates, you'll see options on the **Triggers** for this policy page for custom-triggering events and policy indicators. You have the choice to select a DLP policy or indicators for triggering events that bring users assigned to the policy in-scope for activity scoring. If you select the **User matches a data loss prevention (DLP) policy triggering event** option, you must select a DLP policy from the DLP policy dropdown list to enable triggering indicators for the DLP Policy for this insider risk management policy. If you select the **User performs an exfiltration activity triggering event** option, you must select one or more of the listed indicators for the policy triggering event. +13. If you've selected the *General data leaks* or *Data leaks by priority users* templates, you'll see options on the **Triggers for this policy** page for custom-triggering events and policy indicators. You have the choice to select a DLP policy or indicators for triggering events that bring users assigned to the policy in-scope for activity scoring. If you select the **User matches a data loss prevention (DLP) policy triggering event** option, you must select a DLP policy from the DLP policy dropdown list to enable triggering indicators for the DLP Policy for this insider risk management policy. If you select the **User performs an exfiltration activity triggering event** option, you must select one or more of the listed indicators for the policy triggering event. > [!IMPORTANT]- > If you're unable to select a listed indicator, it's because they aren't enabled for your organization. To make them available to select and assign to the policy, enable the indicators in **Insider risk management** > **Settings** > **Policy indicators**. + > If you're unable to select a listed indicator or sequence, it's because they aren't currently enabled for your organization. To make them available to select and assign to the policy, select the **Turn on indicators** prompt. If you've selected other policy templates, custom triggering events aren't supported. The built-in policy triggering events apply and you'll continue to Step 23 without defining policy attributes. -14. Select **Next** to continue. -15. If you've selected the *General data leaks* or *Data leaks by priority users* templates and have selected the **User performs an exfiltration activity and associated indicators**, you can choose custom or default thresholds for the indicator triggering events that you've selected. Choose either the **Use default thresholds (Recommended)** or **Use custom thresholds for the triggering events**. -16. Select **Next** to continue. -17. If you've selected **Use custom thresholds for the triggering events**, for each triggering event indicator that you selected in Step 13, choose the appropriate level to generate the desired level of activity alerts. You can use the recommended thresholds, custom thresholds, or thresholds based on anomalous activities (for certain indicators) above the daily norm for users. -18. Select **Next** to continue. -19. On the **Policy indicators** page, you'll see the [indicators](insider-risk-management-settings.md#indicators) that you've defined as available on the **Insider risk settings** > **Indicators** page. Select the indicators you want to apply to the policy. +14. If you've selected the *Data leaks by disgruntled users* or *Security policy violations by disgruntled users* templates, you'll see options on the **Triggers for this policy** page for integration with communication compliance and HR data connector events. You have the choice to assign risk scores when users send messages that contain potentially threatening, harassing, or discriminatory language or to bring users into the the policy scope after disgruntlement events are reported in your HR system. If you select the **Disgruntlement triggers from communication compliance (preview)** option, you can accept the default communication compliance policy (automatically created), choose a previously created policy scope for this trigger, or create another scoped policy. If you select **HR data connector events**, you must configure a HR data connector for your organization. +15. Select **Next** to continue. +16. If you've selected the *General data leaks* or *Data leaks by priority users* templates and have selected the **User performs an exfiltration activity and associated indicators**, you can choose custom or default thresholds for the indicator triggering events that you've selected. Choose either the **Use default thresholds (Recommended)** or **Use custom thresholds for the triggering events**. +17. Select **Next** to continue. +18. If you've selected **Use custom thresholds for the triggering events**, for each triggering event indicator that you selected in Step 13, choose the appropriate level to generate the desired level of activity alerts. You can use the recommended thresholds, custom thresholds, or thresholds based on anomalous activities (for certain indicators) above the daily norm for users. +19. Select **Next** to continue. +20. On the **Policy indicators** page, you'll see the [indicators](insider-risk-management-settings.md#indicators) that you've defined as available on the **Insider risk settings** > **Indicators** page. Select the indicators you want to apply to the policy. > [!IMPORTANT] > If indicators on this page can't be selected, you'll need to select the indicators you want to enable for all policies. You can use the **Turn on indicators** button in the wizard or select indicators on the **Insider risk management** > **Settings** > **Policy indicators** page. Insider risk management policies include assigned users and define which types o If you've selected a *Data theft* or *Data leaks* policy template, select one or more **Sequence detection** methods and a **Cumulative exfiltration detection** method to apply to the policy. If you've selected the *Risky browser usage* policy template, select one or more of the **Browsing indicators**. -20. Select **Next** to continue. -21. On the **Decide whether to use default or custom indicator thresholds** page, choose custom or default thresholds for the policy indicators that you've selected. Choose either the **Use default thresholds for all indicators** or **Specify custom thresholds** for the selected policy indicators. If you've selected Specify custom thresholds, choose the appropriate level to generate the desired level of activity alerts for each policy indicator. -22. Select **Next** to continue. -23. On the **Review** page, review the settings you've chosen for the policy and any suggestions or warnings for your selections. Select **Edit** to change any of the policy values or select **Submit** to create and activate the policy. +21. Select **Next** to continue. +22. On the **Decide whether to use default or custom indicator thresholds** page, choose custom or default thresholds for the policy indicators that you've selected. Choose either the **Use default thresholds for all indicators** or **Specify custom thresholds** for the selected policy indicators. If you've selected Specify custom thresholds, choose the appropriate level to generate the desired level of activity alerts for each policy indicator. +23. Select **Next** to continue. +24. On the **Review** page, review the settings you've chosen for the policy and any suggestions or warnings for your selections. Select **Edit** to change any of the policy values or select **Submit** to create and activate the policy. ## Next steps |
| compliance | Insider Risk Management Content Explorer | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/insider-risk-management-content-explorer.md | +>[!IMPORTANT] +>Microsoft Purview Insider Risk Management correlates various signals to identify potential malicious or inadvertent insider risks, such as IP theft, data leakage and security violations. Insider risk management enables customers to create policies to manage security and compliance. Built with privacy by design, users are pseudonymized by default, and role-based access controls and audit logs are in place to help ensure user-level privacy. + The insider risk management **Content explorer** allows users assigned the *Insider Risk Management Investigators* role to examine the context and details of content associated with activity in alerts. The case data in Content explorer is refreshed daily to include new activity. For all alerts that are confirmed to a case, copies of data and message files are archived as a snapshot in time of the items, while maintaining the original files and messages in the storage sources. If needed, case data files may be exported as a portable document file (PDF) or in the original file format. For new cases, it usually takes about an hour for content to populate in Content explorer. For cases with large amounts of content, it may take longer to create a snapshot. If content is still loading in Content explorer, you will see a progress indicator that displays the completion percentage. |
| compliance | Insider Risk Management Notices | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/insider-risk-management-notices.md | +>[!IMPORTANT] +>Microsoft Purview Insider Risk Management correlates various signals to identify potential malicious or inadvertent insider risks, such as IP theft, data leakage and security violations. Insider risk management enables customers to create policies to manage security and compliance. Built with privacy by design, users are pseudonymized by default, and role-based access controls and audit logs are in place to help ensure user-level privacy. + Insider risk management notice templates allow you to automatically send email messages to users when a case is created for activities that have generated a policy match and confirmed alert. For most alerts that generate cases, user actions are the result of mistakes or inadvertent activities without ill intent. Notices serve as simple reminders to users to be more careful, to provide links to information for refresher training, or to corporate policy resources. Notices can be an important part of your internal compliance training program and can help create a documented audit trail for users with recurring risk activities. Create notice templates if you want to send users an email reminder notice for policy matches as part of the case resolution process. Notices can only be sent to the user email address associated with the specific case being reviewed. When selecting a notice template to apply to a policy match, you can choose to accept the field values defined in the template or overwrite the fields as needed |
| compliance | Insider Risk Management Plan | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/insider-risk-management-plan.md | +>[!IMPORTANT] +>Microsoft Purview Insider Risk Management correlates various signals to identify potential malicious or inadvertent insider risks, such as IP theft, data leakage and security violations. Insider risk management enables customers to create policies to manage security and compliance. Built with privacy by design, users are pseudonymized by default, and role-based access controls and audit logs are in place to help ensure user-level privacy. + Before getting started with [insider risk management](insider-risk-management.md) in your organization, there are important planning activities and considerations that should be reviewed by your information technology and compliance management teams. Thoroughly understanding and planning for deployment in the following areas will help ensure that your implementation and use of insider risk management features goes smoothly and is aligned with the best practices for the solution. For more information and an overview of the planning process to address risky activities in your organization, see [Starting an insider risk management program](https://download.microsoft.com/download/b/2/0/b208282a-2482-4986-ba07-15a9b9286df0/pwc-starting-an-insider-risk-management-program-with-pwc-and-microsoft.pdf). |
| compliance | Insider Risk Management Policies | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/insider-risk-management-policies.md | As with the **General data leaks template**, you can choose a DLP policy to trig ### Data leaks by disgruntled users (preview) -When users experience employment stressors, they may become disgruntled, which may increase the chances of insider risk activity. This template starts scoring security and compliance related user activity when an indicator associated with disgruntlement is identified. Examples include system signals performance improvement notifications, poor performance reviews, or changes to job level status. Data leaks for disgruntled users may include downloading files from SharePoint Online and copying data to personal cloud messaging and storage services near employment stressor events. +When users experience employment stressors, they may become disgruntled, which may increase the chances of insider risk activity. This template starts scoring user activity when an indicator associated with disgruntlement is identified. Examples may include performance improvement notifications, poor performance reviews, changes to job level status, or email and other messages that may signal disgruntlement. Data leaks for disgruntled users may include downloading files from SharePoint Online and copying data to personal cloud messaging and storage services near employment stressor events. -When using this template, you must also configure a Microsoft 365 HR connector to periodically import performance improvement notifications, poor performance review status, or job level change information for users in your organization. See the [Import data with the HR connector](import-hr-data.md) article for step-by-step guidance to configure the Microsoft 365 HR connector for your organization. +When using this template, you must either configure a HR connector, select the option to [integrate communication compliance disgruntlement signals](/microsoft-365/compliance/communication-compliance-policies#policy-for-insider-risk-management-integration-preview) from user messages, or choose both. The HR connector enables the periodic import of performance improvement notifications, poor performance review statuses, or job level change information for users in your organization. Communication compliance disgruntlement integration imports signals for user messages that may contain potentially threatening, harassing, or discriminatory text content. Associated alerts generated in Communication Compliance do not need to be triaged, remediated, or changed in status to be integrated with the insider risk management policy. ++To configure a HR connector, see the [Import data with the HR connector](import-hr-data.md) article. To configure integration with communication compliance, you'll select this option in the wizard when you configure the policy. ### General security policy violations (preview) You'll need to have Microsoft Defender for Endpoint configured in your organizat ### Security policy violations by disgruntled users (preview) -Users that experience employment stressors may be at a higher risk for inadvertent or malicious security policy violations. These stressors may include the user being placed on a performance improvement plan, poor performance review status, or being demoted from their current position. This policy template starts risk scoring based on these indicators and activities associated with these events for these users. +Users that experience employment stressors may be at a higher risk for inadvertent or malicious security policy violations. These stressors may result in behaviors that result in the user being placed on a performance improvement plan, a poor performance review status, being demoted from their current position, or the user sending email and other messages that may signal disgruntlement. This policy template starts risk scoring based on these indicators and activities associated with these events for these users. -When using this template, you must also configure a Microsoft HR connector to periodically import system signals related to performance improvement notifications, poor performance review status, or job level change information for users in your organization. See the [Import data with the HR connector](import-hr-data.md) article for step-by-step guidance to configure the Microsoft HR connector for your organization. +When using this template, you must configure a HR connector, or select the option to [integrate communication compliance disgruntlement signals](/microsoft-365/compliance/communication-compliance-policies#policy-for-insider-risk-management-integration-preview) from user messages, or both. The HR connector enables the periodic import of performance improvement notifications, poor performance review statuses, or job level change information for users in your organization. Communication compliance disgruntlement integration imports signals for user messages that may contain potentially threatening, harassing, or discriminatory text content. Associated alerts generated in Communication Compliance do not need to be triaged, remediated, or changed in status to be integrated with the insider risk management policy. To configure a HR connector, see the [Import data with the HR connector](import-hr-data.md) article. To configure integration with communication compliance, you'll select this option in wizard when you configure the policy. You'll also need to have Microsoft Defender for Endpoint configured in your organization and enable Defender for Endpoint for insider risk management integration in the Defender Security Center to import security violation alerts. For more information on configuring Defender for Endpoint for insider risk management integration, see [Configure advanced features in Defender for Endpoint](/windows/security/threat-protection/microsoft-defender-atp/advanced-features#share-endpoint-alerts-with-microsoft-compliance-center). The following table lists the triggering events and prerequisites for policies c | **Data theft by departing users** | Resignation or termination date indicator from HR connector or Azure Active Directory account deletion | (optional) Microsoft 365 HR connector configured for termination and resignation date indicators | | **General data leaks** | Data leak policy activity that creates a *High severity* alert or built-in exfiltration event triggers | DLP policy configured for *High severity* alerts <br><br> OR <br><br> Customized triggering indicators | | **Data leaks by priority users** | Data leak policy activity that creates a *High severity* alert or built-in exfiltration event triggers | DLP policy configured for *High severity* alerts <br><br> OR <br><br> Customized triggering indicators <br><br> Priority user groups configured in insider risk settings |-| **Data leaks by disgruntled users** | Performance improvement, poor performance, or job level change indicators from HR connector | Microsoft HR connector configured for disgruntlement indicators | +| **Data leaks by disgruntled users** | - Performance improvement, poor performance, or job level change indicators from HR connector. <br> - Messages containing potentially threatening, harassing, or discriminatory language | Microsoft 365 HR connector configured for disgruntlement indicators <br><br> AND/OR <br><br> Communication Compliance integration and dedicated disgruntlement policy | | **General security policy violations** | Defense evasion of security controls or unwanted software detected by Microsoft Defender for Endpoint | Active Microsoft Defender for Endpoint subscription <br><br> Microsoft Defender for Endpoint integration with Microsoft Purview compliance portal configured | | **General patient data misuse** | Defense evasion of security controls from EMR systems <br><br> User and patient address matching indicators from HR systems | Healthcare access indicators selected in policy or insider risk settings <br><br> Microsoft 365 HR connector configured for address matching <br><br> Microsoft Healthcare or Epic connector configured | | **General risky browser usage** | User browsing activity related to security that matches at least one selected *Browsing indicator* | See the complete list of prerequisites in the [browser signal detection article](/microsoft-365/compliance/insider-risk-management-browser-support) | | **Security policy violations by departing users** | Resignation or termination date indicators from HR connector or Azure Active Directory account deletion | (optional) Microsoft 365 HR connector configured for termination and resignation date indicators <br><br> Active Microsoft Defender for Endpoint subscription <br><br> Microsoft Defender for Endpoint integration with Microsoft Purview compliance portal configured | | **Security policy violations by priority users** | Defense evasion of security controls or unwanted software detected by Microsoft Defender for Endpoint | Active Microsoft Defender for Endpoint subscription <br><br> Microsoft Defender for Endpoint integration with Microsoft Purview compliance portal configured <br><br> Priority user groups configured in insider risk settings |-| **Security policy violations by disgruntled user** | Performance improvement, poor performance, or job level change indicators from HR connector | Microsoft 365 HR connector configured for disgruntlement indicators <br><br> Active Microsoft Defender for Endpoint subscription <br><br> Microsoft Defender for Endpoint integration with Microsoft Purview compliance portal configured | +| **Security policy violations by disgruntled user** | - Performance improvement, poor performance, or job level change indicators from HR connector. <br> - Messages containing potentially threatening, harassing, or discriminatory language | Microsoft 365 HR connector configured for disgruntlement indicators <br><br> AND/OR <br><br> Communication Compliance integration and dedicated disgruntlement policy <br><br> AND <br><br> Active Microsoft Defender for Endpoint subscription <br><br> Microsoft Defender for Endpoint integration with Microsoft Purview compliance portal configured | ## Prioritize content in policies -Insider risk management policies support specifying a higher priority for content depending on where it's stored, the type of content, or how it's classified. Specifying content as a priority increases the risk score for any associated activity, which in turn increases the chance of generating a high severity alert. However, some activities won't generate an alert at all unless the related content contains built-in or custom sensitive info types or was specified as a priority in the policy. +Insider risk management policies support specifying a higher priority for content depending on where it's stored, the type of content, or how it's classified. You can also choose whether to assign risk scores to all activities detected by a policy or only activities that include priority content. Specifying content as a priority increases the risk score for any associated activity, which in turn increases the chance of generating a high severity alert. However, some activities won't generate an alert at all unless the related content contains built-in or custom sensitive info types or was specified as a priority in the policy. For example, your organization has a dedicated SharePoint site for a highly confidential project. Data leaks for information in this SharePoint site could compromise the project and would have a significant impact on its success. By prioritizing this SharePoint site in a Data leaks policy, risk scores for qualifying activities are automatically increased. This prioritization increases the likelihood that these activities generate an insider risk alert and raises the severity level for the alert. +Additionally, you can choose to focus this policy for SharePoint site activity that only includes priority content for this project. Risk scores will be assigned and alerts will be generated only when specified activities include priority content. Activities without priority content won't be scored, but you'll still be able to review them if an alert is generated. ++>[!NOTE] +>If you configure a policy to generate alerts only for activity that includes priority content, no changes are applied to risk score boosters. + When you create an insider risk management policy in the policy wizard, you can choose from the following priorities: - **SharePoint sites**: Any activity associated with all file types in defined SharePoint sites is assigned a higher risk score. Users configuring the policy and selecting priority SharePoint sites can select SharePoint sites that they have permission to access. If SharePoint sites aren't available for selection in the policy by the current user, another user with the required permissions can select the sites for the policy later, or the current user should be given access to the required sites. When you create an insider risk management policy in the policy wizard, you can ## Sequence detection (preview) -Risky activities may not occur as isolated events. These risks are frequently part of a larger sequence of events. A sequence is a group of two or more user activities performed one after the other that might suggest an elevated risk. Identifying these related activities is an important part of evaluating overall risk. When sequence detection is enabled for data theft or data leaks policies, insights from sequence information activities are displayed on the **User activity** tab within an insider risk management case. The following policy templates support sequence detection: +Risky activities may not occur as isolated events. These risks are frequently part of a larger sequence of events. A sequence is a group of two or more user activities performed one after the other that might suggest an elevated risk. Identifying these related activities is an important part of evaluating overall risk. When sequence detection is selected for data theft or data leaks policies, insights from sequence information activities are displayed on the **User activity** tab within an insider risk management case. The following policy templates support sequence detection: - Data theft by departing users - General data leaks - Data leaks by priority users - Data leaks by disgruntled users -These insider risk management policies can use specific indicators and the order that they occur to detect each step in a sequence of risk. File names are used when mapping activities across a sequence. These risks are organized into four main categories of activity: +These insider risk management policies can use specific indicators and the order that they occur to detect each step in a sequence of risk. For policies created from the *General data leaks* and *Data leaks by priority user* templates, you can also select which sequences trigger the policy. File names are used when mapping activities across a sequence. These risks are organized into four main categories of activity: - **Collection**: These category signals focus on download activities by in-scope policy users. Some example activities in this category would be downloading files from SharePoint sites or moving files into a compressed folder. - **Exfiltration**: These category signals focus on sharing or extraction activities to internal and external sources by in-scope policy users. An example activity in this category would be sending emails with attachments from your organization to external recipients. These insider risk management policies can use specific indicators and the order - **Clean-up**: These category signals focus on deletion activities by in-scope policy users. An example activity in this category would be deleting files from a device. > [!NOTE]-> Sequence detection uses indicators that are enabled in the global settings for insider risk management and indicators that are selected in a policy. If appropriate indicators are not selected, sequence detection will not work. +> Sequence detection uses indicators that are enabled in the global settings for insider risk management. If appropriate indicators are not selected, you'll be able to turn on these indicators in the sequence detection step in the policy wizard. You can customize individual threshold settings for each sequence detection type when configured in the policy. These threshold settings adjust alerts based on the volume of files associated with the sequence. Complete the following steps to create a new policy using the policy wizard: 8. Select **Next** to continue. 9. On the **Content to prioritize** page, you can assign (if needed) the sources to prioritize, which increases the chance of generating a high severity alert for these sources. Select one of the following choices: - - **I want to specify SharePoint sites, sensitivity labels, and/or sensitive information types as priority content**. Selecting this option will enable detail pages in the wizard to configure these channels. - - **I don't want to specify priority content right now (you'll be able to do this after the policy is created)**. Selecting this option will skip the channel detail pages in the wizard. + - **I want to prioritize content**. Selecting this option will enable you to prioritize *SharePoint sites*, *Sensitivity labels*, *Sensitive info types*, and *File extensions* content types. If you choose this option, you must select at least one priority content type. + - **I don't want to specify priority content right now**. Selecting this option will skip the priority content detail pages in the wizard. 10. Select **Next** to continue. -11. If you've selected **I want to specify SharePoint sites, sensitivity labels, sensitive information types, and/or file extensions as priority content** in the previous step, you'll see the detail pages for *SharePoint sites*, *sensitive info types*, *sensitivity labels* and *file extensions*. Use these detail pages to define the SharePoint, sensitive info types, and sensitivity labels to prioritize in the policy. +11. If you've selected **I want to prioritize content** in the previous step, you'll see the detail pages for *SharePoint sites*, *sensitive info types*, *sensitivity labels*, *file extensions*, and *Scoring*. Use these detail pages to define the SharePoint, sensitive info types, sensitivity labels, and file extensions to prioritize in the policy. The *Scoring* detail page allows you to scope the policy to only assign risk scores to priority content. - **SharePoint sites**: Select **Add SharePoint site** and select the SharePoint sites you have access to and want to prioritize. For example, *"group1@contoso.sharepoint.com/sites/group1"*. - **Sensitive info type**: Select **Add sensitive info type** and select the sensitivity types you want to prioritize. For example, *"U.S. Bank Account Number"* and *"Credit Card Number"*. - **Sensitivity labels**: Select **Add sensitivity label** and select the labels you want to prioritize. For example, *"Confidential"* and *"Secret"*. - **File extensions**: Add up to 50 file extensions. You can include or omit the '.' with the file extension. For example, *.py* or *py* would prioritize Python files.+ - **Scoring**: Decide whether to assign risk scores to all activities detected by this policy or only for activities that include priority content. Choose **Get alerts for all activity** or **Get alerts only for activity that includes priority content**. >[!NOTE] >Users configuring the policy and selecting priority SharePoint sites can select SharePoint sites that they have permission to access. If SharePoint sites aren't available for selection in the policy by the current user, another user with the required permissions can select the sites for the policy later or the current user should be given access to the required sites. 12. Select **Next** to continue.-13. If you've selected the *General data leaks* or *Data leaks by priority users* templates, you'll see options on the **Triggers** for this policy page for custom triggering events and policy indicators. You have the choice to select a DLP policy or indicators for triggering events that bring users assigned to the policy in-scope for activity scoring. If you select the **User matches a data loss prevention (DLP) policy triggering event** option, you must select a DLP policy from the DLP policy dropdown list to enable triggering indicators for the DLP Policy for this insider risk management policy. If you select the **User performs an exfiltration activity triggering event** option, you must select one or more of the listed indicators for the policy triggering event. +13. If you've selected the *General data leaks* or *Data leaks by priority users* templates, you'll see options on the **Triggers for this policy** page for custom triggering events and policy indicators. You have the choice to select a DLP policy or indicators for triggering events that bring users assigned to the policy in-scope for activity scoring. If you select the **User matches a data loss prevention (DLP) policy triggering event** option, you must select a DLP policy from the DLP policy dropdown list to enable triggering indicators for the DLP Policy for this insider risk management policy. If you select the **User performs an exfiltration activity triggering event** option, you must select one or more of the listed indicators for the policy triggering event. >[!IMPORTANT] >If you're unable to select a listed indicator, it's because they aren't enabled for your organization. To make them available to select and assign to the policy, enable the indicators in **Insider risk management** > **Settings** > **Policy indicators**. If you've selected other policy templates, custom triggering events aren't supported. The built-in policy triggering events apply and you'll continue to Step 23 without defining policy attributes. -14. Select **Next** to continue. -15. If you've selected the *General data leaks* or *Data leaks by priority users* templates and have selected the **User performs an exfiltration activity and associated indicators**, you can choose custom or default thresholds for the indicator triggering events that you've selected. Choose either the **Use default thresholds (Recommended)** or **Use custom thresholds for the triggering events**. -16. Select **Next** to continue. -17. If you've selected **Use custom thresholds for the triggering events**, for each triggering event indicator that you selected in Step 13, choose the appropriate level to generate the desired level of activity alerts. -18. Select **Next** to continue. -19. On the **Policy indicators** page, you'll see the [indicators](insider-risk-management-settings.md#indicators) that you've defined as available on the **Insider risk settings** > **Indicators** page. Select the indicators you want to apply to the policy. +14. If you've selected the *Data leaks by disgruntled users* or *Security policy violations by disgruntled users* templates, you'll see options on the **Triggers for this policy** page for integration with communication compliance and HR data connector events. You have the choice to assign risk scores when users send messages that contain potentially threatening, harassing, or discriminatory language or to bring users into the the policy scope after disgruntlement events are reported in your HR system. If you select the **Disgruntlement triggers from communication compliance (preview)** option, you can accept the default communication compliance policy (automatically created), choose a previously created policy scope for this trigger, or create another scoped policy. If you select **HR data connector events**, you must configure a HR data connector for your organization. +15. Select **Next** to continue. +16. If you've selected the *General data leaks* or *Data leaks by priority users* templates and have selected the **User performs an exfiltration activity and associated indicators**, you can choose custom or default thresholds for the indicator triggering events that you've selected. Choose either the **Use default thresholds (Recommended)** or **Use custom thresholds for the triggering events**. +17. Select **Next** to continue. +18. If you've selected **Use custom thresholds for the triggering events**, for each triggering event indicator that you selected in Step 13, choose the appropriate level to generate the desired level of activity alerts. +19. Select **Next** to continue. +20. On the **Policy indicators** page, you'll see the [indicators](insider-risk-management-settings.md#indicators) that you've defined as available on the **Insider risk settings** > **Indicators** page. Select the indicators you want to apply to the policy. > [!IMPORTANT] > If indicators on this page can't be selected, you'll need to select the indicators you want to enable for all policies. You can use the **Turn on indicators** button in the wizard or select indicators on the **Insider risk management** > **Settings** > **Policy indicators** page. Complete the following steps to create a new policy using the policy wizard: If you've selected a *Data theft* or *Data leaks* policy template, select one or more **Sequence detection** methods and a **Cumulative exfiltration detection** method to apply to the policy. If you've selected the *General risky browser usage* policy template, select one or more of the **Browsing indicators**. -20. Select **Next** to continue. -21. On the **Decide whether to use default or custom indicator thresholds** page, choose custom or default thresholds for the policy indicators that you've selected. Choose either the **Use default thresholds for all indicators** or **Specify custom thresholds** for the selected policy indicators. If you've selected Specify custom thresholds, choose the appropriate level to generate the desired level of activity alerts for each policy indicator. -22. Select **Next** to continue. -23. On the **Review** page, review the settings you've chosen for the policy and any suggestions or warnings for your selections. Select **Edit** to change any of the policy values or select **Submit** to create and activate the policy. +21. Select **Next** to continue. +22. On the **Decide whether to use default or custom indicator thresholds** page, choose custom or default thresholds for the policy indicators that you've selected. Choose either the **Use default thresholds for all indicators** or **Specify custom thresholds** for the selected policy indicators. If you've selected Specify custom thresholds, choose the appropriate level to generate the desired level of activity alerts for each policy indicator. +23. Select **Next** to continue. +24. On the **Review** page, review the settings you've chosen for the policy and any suggestions or warnings for your selections. Select **Edit** to change any of the policy values or select **Submit** to create and activate the policy. ## Update a policy Complete the following steps to manage an existing policy: 8. Select **Next** to continue. 9. On the **Content to prioritize** page, you can assign (if needed) the sources to prioritize, which increases the chance of generating a high severity alert for these sources. Select one of the following choices: - - **I want to specify SharePoint sites, sensitivity labels, sensitive information types, and/or file extensions as priority content**. Selecting this option will enable detail pages in the wizard to configure these channels. - - **I don't want to specify priority content right now (you'll be able to do this after the policy is created)**. Selecting this option will skip the channel detail pages in the wizard. + - **I want to prioritize content**. Selecting this option will enable you to prioritize *SharePoint sites*, *Sensitivity labels*, *Sensitive info types*, and *File extensions* content types. If you choose this option, you must select at least one priority content type. + - **I don't want to specify priority content right now**. Selecting this option will skip the priority content detail pages in the wizard. 10. Select **Next** to continue. -11. If you've selected **I want to specify SharePoint sites, sensitivity labels, and/or sensitive information types as priority content** in the previous step, you'll see the detail pages for *SharePoint sites*, *sensitive info types*, and *sensitivity labels*. Use these detail pages to define the SharePoint, sensitive info types, and sensitivity labels to prioritize in the policy. +11. If you've selected **I want to prioritize content** in the previous step, you'll see the detail pages for *SharePoint sites*, *sensitive info types*, *sensitivity labels*, *file extensions*, and *Scoring*. Use these detail pages to define the SharePoint, sensitive info types, sensitivity labels, and file extensions to prioritize in the policy. The *Scoring* detail page allows you to scope the policy to only assign risk scores to priority content. - **SharePoint sites**: Select **Add SharePoint site** and select the SharePoint sites you have access to and want to prioritize. For example, *"group1@contoso.sharepoint.com/sites/group1"*. - **Sensitive info type**: Select **Add sensitive info type** and select the sensitivity types you want to prioritize. For example, *"U.S. Bank Account Number"* and *"Credit Card Number"*. - **Sensitivity labels**: Select **Add sensitivity label** and select the labels you want to prioritize. For example, *"Confidential"* and *"Secret"*. - **File extensions**: Add up to 50 file extensions. You can include or omit the '.' with the file extension. For example, *.py* or *py* would prioritize Python files.+ - **Scoring**: Decide whether to assign risk scores to all activities detected by this policy or only for activities that include priority content. Choose **Get alerts for all activity** or **Get alerts only for activity that includes priority content**. >[!NOTE] >Users configuring the policy and selecting priority SharePoint sites can select SharePoint sites that they have permission to access. If SharePoint sites aren't available for selection in the policy by the current user, another user with the required permissions can select the sites for the policy later or the current user should be given access to the required sites. 12. Select **Next** to continue.-13. If you've selected the *General data leaks* or *Data leaks by priority users* templates, you'll see options on the **Triggers** for this policy page for custom triggering events and policy indicators. You have the choice to select a DLP policy or indicators for triggering events that bring users assigned to the policy in-scope for activity scoring. If you select the **User matches a data loss prevention (DLP) policy triggering event** option, you must select a DLP policy from the DLP policy dropdown list to enable triggering indicators for the DLP Policy for this insider risk management policy. If you select the **User performs an exfiltration activity triggering event** option, you must select one or more of the listed indicators for the policy triggering event. +13. If you've selected the *General data leaks* or *Data leaks by priority users* templates, you'll see options on the **Triggers for this policy** page for custom triggering events and policy indicators. You have the choice to select a DLP policy or indicators for triggering events that bring users assigned to the policy in-scope for activity scoring. If you select the **User matches a data loss prevention (DLP) policy triggering event** option, you must select a DLP policy from the DLP policy dropdown list to enable triggering indicators for the DLP Policy for this insider risk management policy. If you select the **User performs an exfiltration activity triggering event** option, you must select one or more of the listed indicators for the policy triggering event. >[!IMPORTANT] >If you're unable to select a listed indicator, it's because they aren't enabled for your organization. To make them available to select and assign to the policy, enable the indicators in **Insider risk management** > **Settings** > **Policy indicators**. If you've selected other policy templates, custom triggering events aren't supported. The built-in policy triggering events apply and you'll continue to Step 23 without defining policy attributes. -14. Select **Next** to continue. -15. If you've selected the *General data leaks* or *Data leaks by priority users* templates and have selected the **User performs an exfiltration activity and associated indicators**, you can choose custom or default thresholds for the indicator triggering events that you've selected. Choose either the **Use default thresholds (Recommended)** or **Use custom thresholds for the triggering events**. -16. Select **Next** to continue. -17. If you've selected **Use custom thresholds for the triggering events**, for each triggering event indicator that you selected in Step 13, choose the appropriate level to generate the desired level of activity alerts. -18. Select **Next** to continue. -19. On the **Policy indicators** page, you'll see the [indicators](insider-risk-management-settings.md#indicators) that you've defined as available on the **Insider risk settings** > **Indicators** page. Select the indicators you want to apply to the policy. +14. If you've selected the *Data leaks by disgruntled users* or *Security policy violations by disgruntled users* templates, you'll see options on the **Triggers for this policy** page for [integration with communication compliance](/microsoft-365/compliance/communication-compliance-policies#policy-for-insider-risk-management-integration-preview) and HR data connector events. You have the choice to assign risk scores when users send messages that contain potentially threatening, harassing, or discriminatory language or to bring users into the the policy scope after disgruntlement events are reported in your HR system. If you select the **Disgruntlement triggers from communication compliance (preview)** option, you can accept the default communication compliance policy (automatically created), choose a previously created policy scope for this trigger, or create another scoped policy. If you select **HR data connector events**, you must configure a HR data connector for your organization. +15. Select **Next** to continue. +16. If you've selected the *General data leaks* or *Data leaks by priority users* templates and have selected the **User performs an exfiltration activity and associated indicators**, you can choose custom or default thresholds for the indicator triggering events that you've selected. Choose either the **Use default thresholds (Recommended)** or **Use custom thresholds for the triggering events**. +17. Select **Next** to continue. +18. If you've selected **Use custom thresholds for the triggering events**, for each triggering event indicator that you selected in Step 13, choose the appropriate level to generate the desired level of activity alerts. +19. Select **Next** to continue. +20. On the **Policy indicators** page, you'll see the [indicators](insider-risk-management-settings.md#indicators) that you've defined as available on the **Insider risk settings** > **Indicators** page. Select the indicators you want to apply to the policy. > [!IMPORTANT] > If indicators on this page can't be selected, you'll need to select the indicators you want to enable for all policies. You can use the **Turn on indicators** button in the wizard or select indicators on the **Insider risk management** > **Settings** > **Policy indicators** page. Complete the following steps to manage an existing policy: If you've selected at least one *Office* or *Device* indicator, select the **Risk score boosters** as appropriate. Risk score boosters are only applicable for selected indicators. If you've selected a *Data theft* or *Data leaks* policy template, select one or more **Sequence detection** methods and a **Cumulative exfiltration detection** method to apply to the policy. -20. Select **Next** to continue. -21. On the **Decide whether to use default or custom indicator thresholds** page, choose custom or default thresholds for the policy indicators that you've selected. Choose either the **Use default thresholds for all indicators** or **Specify custom thresholds** for the selected policy indicators. If you've selected Specify custom thresholds, choose the appropriate level to generate the desired level of activity alerts for each policy indicator. -22. Select **Next** to continue. -23. On the **Review** page, review the settings you've chosen for the policy and any suggestions or warnings for your selections. Select **Edit** to change any of the policy values or select **Submit** to create and activate the policy. +21. Select **Next** to continue. +22. On the **Decide whether to use default or custom indicator thresholds** page, choose custom or default thresholds for the policy indicators that you've selected. Choose either the **Use default thresholds for all indicators** or **Specify custom thresholds** for the selected policy indicators. If you've selected Specify custom thresholds, choose the appropriate level to generate the desired level of activity alerts for each policy indicator. +23. Select **Next** to continue. +24. On the **Review** page, review the settings you've chosen for the policy and any suggestions or warnings for your selections. Select **Edit** to change any of the policy values or select **Submit** to create and activate the policy. ## Copy a policy |
| compliance | Insider Risk Management Settings | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/insider-risk-management-settings.md | +>[!IMPORTANT] +>Microsoft Purview Insider Risk Management correlates various signals to identify potential malicious or inadvertent insider risks, such as IP theft, data leakage and security violations. Insider risk management enables customers to create policies to manage security and compliance. Built with privacy by design, users are pseudonymized by default, and role-based access controls and audit logs are in place to help ensure user-level privacy. + Insider risk management settings apply to all insider risk management policies, regardless of the template you choose when creating a policy. Settings are configured using the **Insider risk settings** control located at the top of all insider risk management pages. These settings control policy components for the following areas: - [Privacy](#privacy) Signals are collected and alerts are triggered by policies when users perform ac - **Global settings indicators**: Indicators enabled in global settings for insider risk management define both the indicators available for configuration in policies and the types of user activity signals collected by insider risk management. For example, if a user copies data to personal cloud storage services or portable storage devices and these indicators are selected only in global settings, this activity will be available for review in the Activity explorer. However, since this activity wasn't defined in an insider risk management policy, the activity won't be assigned a risk score or generate an alert. - **Policy indicators**: Indicators included in insider risk management policies are used to determine a risk score for an in-scope user. Policy indicators are enabled from indicators defined in global settings and are only activated after a triggering event occurs for a user. Some examples of policy indicators are when a user copies data to personal cloud storage services or portable storage devices, if a user account is removed from Azure Active Directory, or if a user shares internal files and folders with unauthorized external parties. -Certain policy indicators may also be used for customizing triggering events for specific policy templates. When configured in the policy wizard for the *General data leaks* or *Data leaks by priority users* templates, these indicators allow you more flexibility and customization for your policies and when users are in-scope for a policy. Additionally, you can define individual activity thresholds for these triggering indicators for more fine-grained control in a policy. +Certain policy indicators and sequences may also be used for customizing triggering events for specific policy templates. When configured in the policy wizard for the *General data leaks* or *Data leaks by priority users* templates, these indicators or sequences allow you more flexibility and customization for your policies and when users are in-scope for a policy. Additionally, you can define individual activity thresholds for these triggering indicators for more fine-grained control in a policy. Policy indicators are segmented into the following areas. You can choose the indicators to activate and customize indicator event limits for each indicator level when creating an insider risk policy: If you prefer to disable admin and analytics notifications, complete the followi - **Send an email notification when Analytics is turned off** 4. Select **Save** to configure and exit.++## Inline alert customization (preview) ++Inline alert customization allows you to quickly tune an insider risk management policy directly from the **Alert dashboard** while reviewing the alert. Alerts are generated when an activity meets the thresholds configured in the related policy. To reduce the number of alerts you get from this activity, you can change the activity's thresholds or remove the activity from the policy altogether. ++You can enable inline alert customization to allow users assigned to the *Insider Risk Management Analysts* and *Insider Risk Management Investigators* role groups to edit policy thresholds and to disable specific indicators. If inline alert customization isn't enabled, only users assigned to the *Insider Risk Management Admin* or *Insider Risk Management* role groups can edit these policy conditions. Inline alert customization is supported for alerts regardless of the current alert status, allowing analysts and investigators to update policies for *Dismissed* and *Resolved* alerts if needed. ++Complete the following steps to enable inline alert customization: ++1. In the [Microsoft Purview compliance portal](https://compliance.microsoft.com), go to **Insider risk management** > **Insider risk settings**. +2. Select the **Inline alert customization (preview)** page. +3. Enable inline alert customization for insider risk management. +4. Select **Save** to configure and exit. ++> [!NOTE] +> Enabling inline alert customization will take approximately one hour before being available in new and existing policy alerts. ++When enabled, analysts and investigators can select **Reduce alerts for this activity** for an alert on the **Alert dashboard** and can view details about the activity and indicators associated with the alert. Additionally, the current policy thresholds are displayed for the number of events used to create low, medium, and high severity alerts. If **Reduce alerts for this activity** is selected and a previous policy edit has been made that changes the threshold or has removed the associated indicator, you'll see a notification message detailing previous changes to the policy. ++Analysts and investigators can choose from the following options on the **Reduce alerts for this activity** pane to quickly edit the policy that created the alert: ++- **Reduce alerts using Microsoft's recommended thresholds**: We'll automatically increase the thresholds in the policy for you. You'll be able to review the new recommended threshold settings before changing the policy. +- **Reduce alerts by choosing your own thresholds**: You can manually increase the thresholds for this type of activity for the current and future alerts. You'll be able to review the current threshold settings and configure the new threshold settings before changing the policy. +- **Stop getting alerts for this activity**: This removes this indicator from the policy and this activity will no longer be detected by the policy. This applies to all indicators, regardless of if the indicator is threshold-based. ++After choosing an option, analysts and investigators can choose two options to update the policy: ++- **Save and dismiss alert**: Saves the changes to the policy and updates the alert status to *Resolved*. +- **Save only**: Saves the changes to the policy, but the alert status remains the same. |
| compliance | Insider Risk Management Solution Overview | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/insider-risk-management-solution-overview.md | +>[!IMPORTANT] +>Microsoft Purview Insider Risk Management correlates various signals to identify potential malicious or inadvertent insider risks, such as IP theft, data leakage and security violations. Insider risk management enables customers to create policies to manage security and compliance. Built with privacy by design, users are pseudonymized by default, and role-based access controls and audit logs are in place to help ensure user-level privacy. + Increasingly, employees have more access to create, manage, and share data across a broad spectrum of platforms and services. In most cases, organizations have limited resources and tools to identify and mitigate organization-wide risks while also meeting compliance requirements and employee privacy standards. These risks may include data theft by departing employees and data leaks of information outside your organization by accidental oversharing or malicious intent. Microsoft Purview Insider Risk Management uses the full breadth of service and 3rd-party indicators to help you quickly identify, triage, and act on risky user activity. By using logs from Microsoft 365 and Microsoft Graph, insider risk management allows you to define specific policies to identify risk indicators. After identifying the risks, you can take action to mitigate these risks. |
| compliance | Insider Risk Management Users | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/insider-risk-management-users.md | +>[!IMPORTANT] +>Microsoft Purview Insider Risk Management correlates various signals to identify potential malicious or inadvertent insider risks, such as IP theft, data leakage and security violations. Insider risk management enables customers to create policies to manage security and compliance. Built with privacy by design, users are pseudonymized by default, and role-based access controls and audit logs are in place to help ensure user-level privacy. + The **Users dashboard** is an important tool in the insider risk management workflow and helps investigators and analysts have a more complete understanding of risk activities. This dashboard offers views and management features to meet administrative needs between the creating insider risk management policies and managing insider risk management cases. After users are added to insider risk management policies, background processes are automatically evaluating user activities for [triggering indicators](insider-risk-management-settings.md#indicators). After triggering indicators are present, user activities are assigned risk scores. Some of these activities may result in an insider risk alert, but some activities may not meet a minimum risk score level and an insider risk alert won't be created. The **Users dashboard** allows you to view users with these types of indicators and risk scores, as well users that have active insider risk alerts. |
| compliance | Insider Risk Management | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/insider-risk-management.md | +>[!IMPORTANT] +>Microsoft Purview Insider Risk Management correlates various signals to identify potential malicious or inadvertent insider risks, such as IP theft, data leakage and security violations. Insider risk management enables customers to create policies to manage security and compliance. Built with privacy by design, users are pseudonymized by default, and role-based access controls and audit logs are in place to help ensure user-level privacy. + Microsoft Purview Insider Risk Management is a compliance solution that helps minimize internal risks by enabling you to detect, investigate, and act on malicious and inadvertent activities in your organization. Insider risk policies allow you to define the types of risks to identify and detect in your organization, including acting on cases and escalating cases to Microsoft eDiscovery (Premium) if needed. Risk analysts in your organization can quickly take appropriate actions to make sure users are compliant with your organization's compliance standards. For more information and an overview of the planning process to address risky activities in your organization, see [Starting an insider risk management program](https://download.microsoft.com/download/b/2/0/b208282a-2482-4986-ba07-15a9b9286df0/pwc-starting-an-insider-risk-management-program-with-pwc-and-microsoft.pdf). For organizations in the healthcare industry, recent studies have found a very h ### Actions and behaviors by disgruntled users (preview) -Employment stresses events can impact user behavior in several ways that relate to insider risks. These stressors may be a poor performance review, a position demotion, or the user being placement on a performance review plan. Though most users don't respond maliciously to these events, the stress of these actions may result in some users to behave in ways they may not normally consider during normal circumstances. To help identify these types of risky activities, the following insider risk management policy templates use the Microsoft 365 HR connector and starts scoring risk indicators relating to behaviors that may occur near employment stressor events: +Employment stressor events can impact user behavior in several ways that relate to insider risks. These stressors may be a poor performance review, a position demotion, or the user being placement on a performance review plan. Stressors may also result in potentially inappropriate behavior such as users sending potentially threatening, harassing, or discriminatory language in email and other messages. Though most users don't respond maliciously to these events, the stress of these actions may result in some users to behave in ways they may not normally consider during normal circumstances. To help identify these types of risky activities, the following insider risk management policy templates can use the HR connector and/or integration with a [dedicated communication compliance policy](/microsoft-365/compliance/communication-compliance-policies#integration-with-insider-risk-management-preview) to bring users into scope for insider risk management policies and start scoring risk indicators relating to behaviors that may occur near employment stressor events: - [Data leaks by disgruntled users (preview)](insider-risk-management-policies.md#data-leaks-by-disgruntled-users-preview) - [Security policy violations by disgruntled users (preview)](insider-risk-management-policies.md#security-policy-violations-by-disgruntled-users-preview) |
| compliance | Limits For Content Search | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/limits-for-content-search.md | The following table describes the indexing limits that might result in an email ## Jobs limits -> [!NOTE] -> eDiscovery (Premium) jobs are counted toward the eDiscovery (Standard) limits. For example, if you have 50 jobs running in eDiscovery (Premium) you will be unable to start jobs in eDiscovery (Standard). eDiscovery (Standard) jobs do not count toward eDiscovery (Premium) limits. - |Description|Limit| ||| |Maximum number of concurrent jobs in your organization.|50| |
| compliance | Office 365 Encryption In Microsoft Dynamics 365 | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/office-365-encryption-in-microsoft-dynamics-365.md | Microsoft uses encryption technology to protect customer data in Dynamics 365 wh Dynamics 365 uses standard Microsoft SQL Server cell level encryption for a set of default entity attributes that contain sensitive information, such as user names and email passwords. This feature can help organizations meet the compliance requirements associated with FIPS 140-2. Field-level data encryption is especially important in scenarios that leverage the [Microsoft Dynamics CRM Email Router](/previous-versions/dynamicscrm-2016/administering-dynamics-365/hh699800(v=crm.8)), which must store user names and passwords to enable integration between a Dynamics 365 instance and an email service. -All instances of Dynamics 365 use [Microsoft SQL Server Transparent Data Encryption](/sql/relational-databases/security/encryption/transparent-data-encryption) (TDE) to perform real-time encryption of data when written to disk (at rest). TDE encrypts SQL Server, Azure SQL Database, and Azure SQL Data Warehouse data files. By default, Microsoft stores and manages the database encryption keys for your instances of Dynamics 365. (The keys that are used by Dynamics 365 for Financials are generated by the .NET Framework Data Protection API.) -The manage keys feature in the Dynamics 365 Administration Center gives administrators the ability to self-manage the database encryption keys that are associated with instances of Dynamics 365. (Self-managed database encryption keys are only available in the January 2017 update for Microsoft Dynamics 365 and may not be made available for later versions. For more information, see [Manage the encryption keys for your Dynamics 365 (online) instance](/dynamics365/customer-engagement/admin/manage-encryption-keys-instance).) The key management feature supports both PFX and BYOK encryption key files, such as those stored in an HSM. (For more information about generating and transferring an HSM-protected key over the Internet, see [How to generate and transfer HSM-protected keys for Azure Key Vault](/azure/key-vault/key-vault-hsm-protected-keys).) +All instances of Dynamics 365 use [Microsoft SQL Server Transparent Data Encryption](/sql/relational-databases/security/encryption/transparent-data-encryption) (TDE) to perform real-time encryption of data when written to disk (at rest). TDE encrypts SQL Server, Azure SQL Database, and Azure SQL Data Warehouse data files. By default, Microsoft stores and manages the database encryption keys for your instances of Dynamics 365. (The keys that are used by Dynamics 365 for Financials are generated by the .NET Framework Data Protection API.) ++The manage keys feature in the Power Platform Administration Center gives administrators the ability to self-manage the database encryption keys that are associated with instances of Dynamics 365. See [Manage the encryption keys for your Dynamics 365 (online) instance](/dynamics365/customer-engagement/admin/manage-encryption-keys-instance). The key management feature supports both PFX and BYOK encryption key files, such as those stored in an HSM. (For more information about generating and transferring an HSM-protected key over the Internet, see [How to generate and transfer HSM-protected keys for Azure Key Vault](/azure/key-vault/key-vault-hsm-protected-keys).) To use the upload encryption key option, you need both the public and private encryption key. |
| compliance | Retention Policies Sharepoint | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/retention-policies-sharepoint.md | For retention policies and auto-apply label policies: SharePoint sites must be i To store content that needs to be retained, SharePoint and OneDrive create a Preservation Hold library if one doesn't exist for the site. The Preservation Hold library isn't designed to be used interactively but instead, automatically stores files when this is needed for compliance reasons. It works in the following way: -When a user changes or deletes an item that's subject to retention, a check is made whether the content has been changed since the retention settings were applied. If this is the first change since the retention settings were applied, the content is copied to the Preservation Hold library, which allows the user to change or delete the original content. +When a user changes an item that's subject to retention from a retention policy or a retention label that marks items as a record, or deletes any item subject to retention, the original content is copied to the Preservation Hold library. This behavior lets the user to change or delete the content in their app, while keeping a copy of the original for compliance reasons. A timer job periodically runs on the Preservation Hold library. For content that has been in the Preservation Hold library for more than 30 days, this job compares the content to all queries used by the retention settings for that content. Content that is older than their configured retention period is then deleted from the Preservation Hold library, and from the original location if it is still there. This timer job runs every seven days, which means that together with the minimal 30 days, it can take up to 37 days for content to be deleted from the Preservation Hold library. Users also see an error message if they try to delete a labeled item in any of t - The retention label marks items as a [regulatory record](records-management.md#compare-restrictions-for-what-actions-are-allowed-or-blocked), which always prevents the item from being edited or deleted. -After retention settings are assigned to content in a OneDrive account or SharePoint site, the paths the content takes depend on whether the retention settings are to retain and delete, to retain only, or delete only. +After retention settings are assigned to content in a OneDrive account or SharePoint site, the paths the content takes depend on whether the retention settings are to retain and delete, to retain only, or delete only. In the explanations that follow, modified content is moved to the Preservation Hold library for retention policies, and retention labels that mark items as records (and the content is unlocked). Items that are modified with retention labels that don't mark items as records don't create copies in the Preservation Hold library, but do when items are deleted. When the retention settings are to retain and delete: |
| compliance | Retention Settings | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/retention-settings.md | The **Exchange public folders** location applies retention settings to all publi When you configure an auto-apply policy that uses sensitive information types and select the **Exchange email** location: -- Microsoft 365 group mailboxes are included.--- All mailboxes are automatically included, even if you configure an adaptive scope to identify specific mailboxes. If you've chosen a static policy scope, you won't be able to specify recipients to include or exclude.+- See the important callout for [Auto-apply labels to content with specific types of sensitive information](apply-retention-labels-automatically.md#auto-apply-labels-to-content-with-specific-types-of-sensitive-information). ### Configuration information for SharePoint sites and OneDrive accounts Before you configure retention, first familiarize yourself with capacity and sto #### Relabeling at the end of the retention period -> [!NOTE] -> This option is in preview and subject to change. - When you configure a retention label to automatically apply a different retention label at the end of the retention period, the item is then subject to the retention settings of the newly selected retention label. This option lets you automatically change the retention settings for the item. You can change the replacement label after you've created and saved the primary retention label. For items that already have the primary retention label applied and within the configured retention period, the change of replacement label will synchronize to these items. As with other label changes, allow up to 7 days for this synchronization period. |
| compliance | Sensitive Information Type Entity Definitions | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sensitive-information-type-entity-definitions.md | This article is a list of all sensitive information type (SIT) entity definition > - High confidence: 85 - [ABA routing number](sit-defn-aba-routing.md)+- [All credentials](sit-defn-all-creds.md) - [All full names](sit-defn-all-full-names.md) - [All medical terms and conditions](sit-defn-all-medical-terms-conditions.md) - [All Physical Addresses](sit-defn-all-physical-addresses.md)-- [Amazon S3 Client Secret Access Key (preview)](sit-defn-amazon-s3-client-secret-access-key.md)+- [Amazon S3 Client Secret Access Key](sit-defn-amazon-s3-client-secret-access-key.md) - [Argentina national identity (DNI) number](sit-defn-argentina-national-identity-numbers.md) - [Argentina Unique Tax Identification Key (CUIT/CUIL)](sit-defn-argentina-unique-tax-identification-key.md)-- [ASP.NET machine Key (preview)](sit-defn-asp-net-machine-key.md) +- [ASP.NET machine Key](sit-defn-asp-net-machine-key.md) - [Australia bank account number](sit-defn-australia-bank-account-number.md) - [Australia business number](sit-defn-australia-business-number.md) - [Australia company number](sit-defn-australia-business-number.md) This article is a list of all sensitive information type (SIT) entity definition - [Austria social security number](sit-defn-austria-social-security-number.md) - [Austria tax identification number](sit-defn-austria-tax-identification-number.md) - [Austria value added tax](sit-defn-austria-value-added-tax.md)-- [Azure AD client access token (preview)](sit-defn-azure-ad-client-access-token.md) -- [Azure AD client secret (preview)](sit-defn-azure-ad-client-secret.md)-- [Azure AD User Credentials (preview)](sit-defn-azure-ad-user-credentials.md)-- [Azure App Service deployment password (preview)](sit-defn-azure-app-service-deployment-password.md)-- [Azure Batch shared access key (preview)](sit-defn-azure-batch-shared-access-key.md)-- [Azure Bot Framework secret key (preview)](sit-defn-azure-bot-framework-secret-key.md)-- [Azure Bot service app secret (preview)](sit-defn-azure-bot-service-app-secret.md)-- [Azure Cognitive Search API key (preview)](sit-defn-azure-cognitive-search-api-key.md)-- [Azure Cognitive Service key (preview)](sit-defn-azure-cognitive-service-key.md)-- [Azure Container Registry access key (preview)](sit-defn-azure-container-registry-access-key.md)-- [Azure COSMOS DB account access key (preview)](sit-defn-azure-cosmos-db-account-access-key.md) -- [Azure Databricks personal access token (preview)](sit-defn-azure-databricks-personal-access-token.md)-- [Azure DevOps app secret (preview)](sit-defn-azure-devops-app-secret.md)-- [Azure DevOps personal access token (preview)](sit-defn-azure-devops-personal-access-token.md)+- [Azure AD client access token](sit-defn-azure-ad-client-access-token.md) +- [Azure AD client secret](sit-defn-azure-ad-client-secret.md) +- [Azure AD User Credentials](sit-defn-azure-ad-user-credentials.md) +- [Azure App Service deployment password](sit-defn-azure-app-service-deployment-password.md) +- [Azure Batch shared access key](sit-defn-azure-batch-shared-access-key.md) +- [Azure Bot Framework secret key](sit-defn-azure-bot-framework-secret-key.md) +- [Azure Bot service app secret](sit-defn-azure-bot-service-app-secret.md) +- [Azure Cognitive Search API key](sit-defn-azure-cognitive-search-api-key.md) +- [Azure Cognitive Service key](sit-defn-azure-cognitive-service-key.md) +- [Azure Container Registry access key](sit-defn-azure-container-registry-access-key.md) +- [Azure COSMOS DB account access key](sit-defn-azure-cosmos-db-account-access-key.md) +- [Azure Databricks personal access token](sit-defn-azure-databricks-personal-access-token.md) +- [Azure DevOps app secret](sit-defn-azure-devops-app-secret.md) +- [Azure DevOps personal access token](sit-defn-azure-devops-personal-access-token.md) - [Azure DocumentDB auth key](sit-defn-azure-document-db-auth-key.md)-- [Azure EventGrid access key (preview)](sit-defn-azure-eventgrid-access-key.md) -- [Azure Function Master / API key (preview)](sit-defn-azure-function-master-api-key.md) +- [Azure EventGrid access key](sit-defn-azure-eventgrid-access-key.md) +- [Azure Function Master / API key](sit-defn-azure-function-master-api-key.md) - [Azure IAAS database connection string and Azure SQL connection string](sit-defn-azure-iaas-database-connection-string-azure-sql-connection-string.md) - [Azure IoT connection string](sit-defn-azure-iot-connection-string.md)-- [Azure IoT shared access key (preview)](sit-defn-azure-iot-shared-access-key.md)-- [Azure Logic app shared access signature (preview)](sit-defn-azure-logic-app-shared-access-signature.md) -- [Azure Machine Learning web service API key (preview)](sit-defn-azure-machine-learning-web-service-api-key.md) -- [Azure Maps subscription key (preview)](sit-defn-azure-maps-subscription-key.md) +- [Azure IoT shared access key](sit-defn-azure-iot-shared-access-key.md) +- [Azure Logic app shared access signature](sit-defn-azure-logic-app-shared-access-signature.md) +- [Azure Machine Learning web service API key](sit-defn-azure-machine-learning-web-service-api-key.md) +- [Azure Maps subscription key](sit-defn-azure-maps-subscription-key.md) - [Azure publish setting password](sit-defn-azure-publish-setting-password.md) - [Azure Redis cache connection string](sit-defn-azure-redis-cache-connection-string.md)-- [Azure Redis cache connection string password (preview)](sit-defn-azure-redis-cache-connection-string-password.md)+- [Azure Redis cache connection string password](sit-defn-azure-redis-cache-connection-string-password.md) - [Azure SAS](sit-defn-azure-sas.md) - [Azure service bus connection string](sit-defn-azure-service-bus-connection-string.md)-- [Azure service bus shared access signature (preview)](sit-defn-azure-service-bus-shared-access-signature.md) -- [Azure Shared Access key / Web Hook token (preview)](sit-defn-azure-shared-access-key-web-hook-token.md) -- [Azure SignalR access key (preview)](sit-defn-azure-signalr-access-key.md)-- [Azure SQL connection string (preview)](sit-defn-azure-sql-connection-string.md)-- [Azure storage account access key (preview)](sit-defn-azure-storage-account-access-key.md)+- [Azure service bus shared access signature](sit-defn-azure-service-bus-shared-access-signature.md) +- [Azure Shared Access key / Web Hook token](sit-defn-azure-shared-access-key-web-hook-token.md) +- [Azure SignalR access key](sit-defn-azure-signalr-access-key.md) +- [Azure SQL connection string](sit-defn-azure-sql-connection-string.md) +- [Azure storage account access key](sit-defn-azure-storage-account-access-key.md) - [Azure storage account key](sit-defn-azure-storage-account-key.md) - [Azure Storage account key (generic)](sit-defn-azure-storage-account-key-generic.md)-- [Azure Storage account shared access signature (preview)](sit-defn-azure-storage-account-shared-access-signature.md)-- [Azure Storage account shared access signature for high risk resources (preview)](sit-defn-azure-storage-account-shared-access-signature-high-risk-resources.md)-- [Azure subscription management certificate (preview)](sit-defn-azure-subscription-management-certificate.md)+- [Azure Storage account shared access signature](sit-defn-azure-storage-account-shared-access-signature.md) +- [Azure Storage account shared access signature for high risk resources](sit-defn-azure-storage-account-shared-access-signature-high-risk-resources.md) +- [Azure subscription management certificate](sit-defn-azure-subscription-management-certificate.md) - [Belgium driver's license number](sit-defn-belgium-drivers-license-number.md) - [Belgium national number](sit-defn-belgium-national-number.md) - [Belgium passport number](sit-defn-belgium-passport-number.md) This article is a list of all sensitive information type (SIT) entity definition - [Canada social insurance number](sit-defn-canada-social-insurance-number.md) - [Chile identity card number](sit-defn-chile-identity-card-number.md) - [China resident identity card (PRC) number](sit-defn-china-resident-identity-card-number.md)-- [Client secret / API key (preview)](sit-defn-client-secret-api-key.md)+- [Client secret / API key](sit-defn-client-secret-api-key.md) - [Credit card number](sit-defn-credit-card-number.md) - [Croatia driver's license number](sit-defn-croatia-drivers-license-number.md) - [Croatia identity card number](sit-defn-croatia-identity-card-number.md) This article is a list of all sensitive information type (SIT) entity definition - [France social security number (INSEE)](sit-defn-france-social-security-number.md) - [France tax identification number](sit-defn-france-tax-identification-number.md) - [France value added tax number](sit-defn-france-value-added-tax-number.md)-- [General password (preview)](sit-defn-general-password.md)-- [General Symmetric key (preview)](sit-defn-general-symmetric-key.md)+- [General password](sit-defn-general-password.md) +- [General Symmetric key](sit-defn-general-symmetric-key.md) - [Generic medication names](sit-defn-generic-medication-names.md) - [Germany driver's license number](sit-defn-germany-drivers-license-number.md) - [Germany identity card number](sit-defn-germany-identity-card-number.md) This article is a list of all sensitive information type (SIT) entity definition - [Germany physical addresses](sit-defn-germany-physical-addresses.md) - [Germany tax identification number](sit-defn-germany-tax-identification-number.md) - [Germany value added tax number](sit-defn-germany-value-added-tax-number.md)-- [GitHub Personal Access Token (preview)](sit-defn-github-personal-access-token.md) -- [Google API key (preview)](sit-defn-google-api-key.md)+- [GitHub Personal Access Token](sit-defn-github-personal-access-token.md) +- [Google API key](sit-defn-google-api-key.md) - [Greece driver's license number](sit-defn-greece-drivers-license-number.md) - [Greece national ID card](sit-defn-greece-national-id-card.md) - [Greece passport number](sit-defn-greece-passport-number.md) This article is a list of all sensitive information type (SIT) entity definition - [Greece Social Security Number (AMKA)](sit-defn-greece-social-security-number.md) - [Greece tax identification number](sit-defn-greece-tax-identification-number.md) - [Hong Kong identity card (HKID) number](sit-defn-hong-kong-identity-card-number.md)-- [Http authorization header (preview)](sit-defn-http-authorization-header.md)+- [Http authorization header](sit-defn-http-authorization-header.md) - [Hungary driver's license number](sit-defn-hungary-drivers-license-number.md) - [Hungary passport number](sit-defn-hungary-passport-number.md) - [Hungary personal identification number](sit-defn-hungary-personal-identification-number.md) This article is a list of all sensitive information type (SIT) entity definition - [Medical specialities](sit-defn-medical-specialities.md) - [Medicare Beneficiary Identifier (MBI) card](sit-defn-medicare-beneficiary-Identifier-card.md) - [Mexico Unique Population Registry Code (CURP)](sit-defn-mexico-unique-population-registry-code.md)-- [Microsoft Bing maps key (preview)](sit-defn-microsoft-bing-maps-key.md)+- [Microsoft Bing maps key](sit-defn-microsoft-bing-maps-key.md) - [Netherlands citizen's service (BSN) number](sit-defn-netherlands-citizens-service-number.md) - [Netherlands driver's license number](sit-defn-netherlands-drivers-license-number.md) - [Netherlands passport number](sit-defn-netherlands-passport-number.md) This article is a list of all sensitive information type (SIT) entity definition - [Russia passport number international](sit-defn-russia-passport-number-international.md) - [Saudi Arabia National ID](sit-defn-saudi-arabia-national-id.md) - [Singapore national registration identity card (NRIC) number](sit-defn-singapore-national-registration-identity-card-number.md)-- [Slack access token (preview)](sit-defn-slack-access-token.md)+- [Slack access token](sit-defn-slack-access-token.md) - [Slovakia driver's license number](sit-defn-slovakia-drivers-license-number.md) - [Slovakia passport number](sit-defn-slovakia-passport-number.md) - [Slovakia personal number](sit-defn-slovakia-personal-number.md) This article is a list of all sensitive information type (SIT) entity definition - [U.S./U.K. passport number](sit-defn-us-uk-passport-number.md) - [Ukraine passport domestic](sit-defn-ukraine-passport-domestic.md) - [Ukraine passport international](sit-defn-ukraine-passport-international.md)-- [User login credentials (preview)](sit-defn-user-login-credentials.md)-- [X.509 certificate private key (preview)](sit-defn-x-509-certificate-private-key.md)+- [User login credentials](sit-defn-user-login-credentials.md) +- [X.509 certificate private key](sit-defn-x-509-certificate-private-key.md) |
| compliance | Sensitivity Labels Aip | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sensitivity-labels-aip.md | Title: "Choose Microsoft Purview Information Protection built-in labeling for Office apps over the Azure Information Protection (AIP) add-in" + Title: "Migrate the Azure Information Protection (AIP) add-in to Microsoft Purview Information Protection built-in labeling for Office apps" f1.keywords: - CSH -description: When you use the Azure Information Protection (AIP) unified labeling client, understand the advantages of using built-in labeling for Office apps rather than the AIP add-in. +description: For Office 365 apps, understand the migration of the Azure Information Protection (AIP) add-in to built-in labeling to protect sensitive data. -# Why choose built-in labeling over the AIP add-in for Office apps +# Migrate the Azure Information Protection (AIP) add-in to built-in labeling for Office apps >*[Microsoft 365 licensing guidance for security & compliance](/office365/servicedescriptions/microsoft-365-service-descriptions/microsoft-365-tenantlevel-services-licensing-guidance/microsoft-365-security-compliance-licensing-guidance).* -When you use [sensitivity labels](sensitivity-labels.md) in Microsoft 365 Apps on Windows computers, you have a choice of using labeling that's built into Office apps, or an add-in from the [Azure Information Protection (AIP) unified labeling client](/azure/information-protection/rms-client/aip-clientv2). +When you use [sensitivity labels](sensitivity-labels.md) in Microsoft 365 Apps on Windows computers, we recommend you use you labeling that's built into Office apps, even if you have the [Azure Information Protection (AIP) unified labeling client](/azure/information-protection/rms-client/aip-clientv2) installed. Moving forward, the AIP add-in will be disabled by default in the latest versions of Office apps. -Built-in labeling forms the cornerstone of a [Microsoft Purview information protection deployment](information-protection-solution.md) because this labeling technology extends across platforms (Windows, macOS, iOS, Android, and web), as well as across Microsoft apps and services, and beyond. Built-in labeling is also designed to work with other Microsoft Purview capabilities, such as data classification and Microsoft Purview data loss prevention (DLP). +To prepare for this change, use this article to understand the benefits of using built-in labeling, which main features have parity, and how to control the migration from the AIP add-in to the newer labeling experience. -Because built-in labels don't use an Office Add-in, they benefit from more stability and better performance. They also support the latest Microsoft Purview features, such as advanced classifiers. ++## Built-in labeling vs. the AIP client ++Built-in labeling forms the cornerstone of a [Microsoft Purview Information Protection deployment](information-protection-solution.md) because this labeling technology extends across platforms (Windows, macOS, iOS, Android, and web), as well as across Microsoft apps and services, and beyond. Built-in labeling is also designed to work with other Microsoft Purview capabilities, such as data classification and Microsoft Purview Data Loss Prevention (DLP). ++Because built-in labels don't use an Office add-in, they benefit from more stability and better performance. They also support the latest Microsoft Purview features, such as advanced classifiers. -By default, built-in labeling is turned off in Office for Windows apps when the AIP client is installed. You can change this default behavior by using the instructions in the following section, [How to disable the AIP add-in to use built-in labeling for Office apps](#how-to-disable-the-aip-add-in-to-use-built-in-labeling-for-office-apps). +Up until recently, built-in labeling was turned off by default in Office for Windows apps when the AIP client was installed. This default will no longer be the case for newer versions of Office. You can control the default behavior by using the instructions in the following section, [How to disable the AIP add-in to use built-in labeling for Office apps](#how-to-disable-the-aip-add-in-to-use-built-in-labeling-for-office-apps). For example, disable the add-in for initial testing on a couple of computers, and then move onto a pilot for a few users. When you're ready, migrate all users to the newer labeling experience. When you keep the AIP client installed but disabled in Office apps, the other capabilities of the AIP client remain supported: For more information about these capabilities that extend labeling beyond Office Independently from labeling, you can continue to use the [AIPService](/powershell/module/aipservice) PowerShell module for tenant-level management of the encryption service. For example, configure super user access when you need to remove encryption for data recovery, track and revoke documents that have been opened by the AIP client, and configure the use license validity period for offline access. For more information, see [Administering protection from Azure Information Protection by using PowerShell](/azure/information-protection/administer-powershell). +> [!NOTE] +> Built-in labels require a subscription edition of Office apps. If you have standalone editions of Office, sometimes called "Office Perpetual", upgrade to Microsoft 365 Apps for Enterprise to benefit from the latest labeling capabilities. -## Decide whether to use built-in labeling for Office apps or the AIP add-in +## Benefits of using built-in labeling for Office apps vs. the AIP add-in -Now that the AIP client is in [maintenance mode](https://techcommunity.microsoft.com/t5/security-compliance-and-identity/announcing-aip-unified-labeling-client-maintenance-mode-and/ba-p/3043613), we don't recommend you use the AIP add-in for Office apps for the following reasons: +The AIP client is in [maintenance mode](https://techcommunity.microsoft.com/t5/security-compliance-and-identity/announcing-aip-unified-labeling-client-maintenance-mode-and/ba-p/3043613) and we don't recommend you use the AIP add-in for Office apps for the following reasons: - No new labeling features will be supported. - Add-ins are less stable because they can conflict with other add-ins that can result in Office apps hanging, crashing, or automatically disabling the add-in.-- As an add-in, it runs more slowly, and can be disabled by users to bypass labeling requirements.+- As an add-in, it runs [more slowly](/deployoffice/fieldnotes/performance-recommendations#office-add-ins), and can be disabled by users to bypass labeling requirements. - Any bug fixes will require reinstalling the Azure Information Protection client. - The labeling experience for users is slightly different from built-in labels that users have on their other devices (macOS, iOS, Android), and when they use Office for the web. This difference can increase costs for training and support.-- There are already new Office labeling features released that are [only supported by built-in labeling](#features-supported-only-by-built-in-labeling-for-office-apps), and the list is growing all the time.+- There are new Office labeling features released that are [only supported by built-in labeling](#features-supported-only-by-built-in-labeling-for-office-apps), and the list is growing all the time. -Use the AIP add-in for your Windows Office apps only if you've already deployed it to users and you need time to migrate them to built-in labeling. Or, users need a feature that isn't supported by built-in labeling. Use the [feature parity information](#feature-parity-for-built-in-labeling-and-the-aip-add-in-for-office-apps) on this page to help you identify these features. +Use the AIP add-in for your Windows Office apps only if you've already deployed it to users and you need time to migrate them to built-in labeling. Or, if there's a key feature that users need that isn't yet available for their Office update channel. ## Features supported only by built-in labeling for Office apps Some features are only supported by built-in labeling for Office apps, and won't - Access to intelligent classification services that include [trainable classifiers](classifier-learn-about.md), [exact data match (EDM)](sit-learn-about-exact-data-match-based-sits.md), and [named entities](named-entities-learn.md) - Detection of sensitive information as users type - In Word, users can review and remove the identified sensitive content-- [Sensitivity bar](sensitivity-labels-office-apps.md#sensitivity-bar) is integrated into existing user workflows+- [Sensitivity bar](sensitivity-labels-office-apps.md#sensitivity-bar) that is integrated into existing user workflows - [PDF support](sensitivity-labels-office-apps.md#pdf-support) - For labels that let users assign permissions, different permissions (Read or Change) can be granted to users or groups - Encrypt-Only for emails-- Visibility of labels on the status bar (Will be replaced with the sensitivity bar on the window title.) - Support for account switching - Users can't disable labeling -Example showing how users can review and optionally remove identified sensitive content in Word: -- --Example showing how sensitivity labels are integrated into user workflows: +Watch a short demo to see some of these features in action: - +> [!VIDEO https://www.microsoft.com/en-us/videoplayer/embed/RE58yhH] To keep informed when new labeling capabilities become available for built-in labeling, see [What's new in Microsoft Purview](whats-new.md) and the **Sensitivity labels** sections. ## How to disable the AIP add-in to use built-in labeling for Office apps -When you've installed the AIP client to extend labeling beyond Office apps but want to prevent the client's add-in from loading in Office apps, use the Group Policy setting **List of managed add-ins** as documented in [No Add-ins loaded due to group policy settings for Office 2013 and Office 2016 programs](https://support.microsoft.com/help/2733070/no-add-ins-loaded-due-to-group-policy-settings-for-office-2013-and-off). +For the latest Office apps, the AIP add-in is disabled by default, so there's nothing for you to configure: ++- **Build 16.0.15716.0+**: Currently in [Beta Channel](https://office.com/insider) +- **Current Channel** and **Monthly Enterprise Channel**: Version 2211+ (not yet released) +- **Semi-Annual Channel**: Version 2301+ (not yet released) ++If you have one of these versions, and need to use the AIP add-in rather than built-in labeling, you have to [configure a new setting to override the default](#how-to-configure-newer-versions-of-office-to-enable-the-aip-add-in). ++> [!IMPORTANT] +> If youΓÇÖve previously used the AIP add-in as the default labeling client in Office apps and use Office versions listed in this section, the AIP add-in is automatically disabled and replaced by built-in labeling. ++To disable the AIP add-in for older versions, see the next section. ++Remember, when the AIP add-in is disabled, you can still use the AIP client to extend labeling beyond Office apps. ++### How to configure older versions of Office to disable the AIP add-in ++For Office apps older than the versions listed in the previous section, to prevent the AIP add-in from loading in Office apps, use the Group Policy setting **List of managed add-ins** as documented in [No Add-ins loaded due to group policy settings for Office 2013 and Office 2016 programs](https://support.microsoft.com/help/2733070/no-add-ins-loaded-due-to-group-policy-settings-for-office-2013-and-off). For your Windows Office apps that support built-in labeling, use the configuration for Microsoft Word 2016, Excel 2016, PowerPoint 2016, and Outlook 2016, specify the following programmatic identifiers (ProgID) for the AIP client, and set the option to **0: The add-in is always disabled (blocked)** Alternatively, you can interactively disable or remove the **Microsoft Azure Inf Whichever method you choose, the changes take effect when Office apps restart. -If after making these changes the **Sensitivity** button doesn't display on the Office ribbon, check whether sensitivity labeling has been [turned off](sensitivity-labels-office-apps.md#if-you-need-to-turn-off-built-in-labeling-in-office-apps-on-windows). Although this isn't the default configuration, an administrator might have explicitly set this configuration by using Group Policy or by directly editing the registry. +If after making these changes the **Sensitivity** button doesn't display on the Office ribbon, check whether sensitivity labeling has been [turned off](sensitivity-labels-office-apps.md#if-you-need-to-turn-off-built-in-labeling-in-office-apps-on-windows) with the **Use the Sensitivity feature in Office to apply and view sensitivity labels** setting. Although this isn't the default configuration for Office apps, an administrator might have explicitly set this configuration by using Group Policy or by directly editing the registry. -> [!NOTE] -> Built-in labels require a subscription edition of Office apps. If you have standalone editions of Office, sometimes called "Office Perpetual", we recommend you upgrade to Microsoft 365 Apps for Enterprise to benefit from the [latest labeling capabilities](sensitivity-labels-office-apps.md#support-for-sensitivity-label-capabilities-in-apps). +### How to configure newer versions of Office to enable the AIP add-in -Remember, when you use this method to disable the AIP add-in, you can still use the AIP client to extend labeling beyond Office apps. +> [!CAUTION] +> If you've previously set the value of **Use the Sensitivity feature in Office to apply and view sensitivity labels** to **0** (or used the equivalent registry key of **UseOfficeForLabelling**ΓÇï) to disable built-in labeling because you wanted to use the AIP add-in: Going forward, if you don't configure the new setting that's described in this section, you won't be able to use sensitivity labeling with either the AIP add-in or built-in labeling. -## Feature parity for built-in labeling and the AIP add-in for Office apps +In the [newer versions of Office](#how-to-disable-the-aip-add-in-to-use-built-in-labeling-for-office-apps), the AIP add-in is disabled by default. To enable it, you must configure a new Office setting under **User Configuration/Administrative Templates/Microsoft Office 2016/Security Settings**: ++- **Use the Azure Information Protection add-in for sensitivity labeling**. Set the value to **1**. ++Deploy this setting by using Group Policy, or by using the [Office cloud policy service](/DeployOffice/overview-office-cloud-policy-service). ++Additional Office settings you might need to configure: ++1. The security setting **Use the Sensitivity feature in Office to apply and view sensitivity labels**, must be **0**, or not configured. -Many of the labeling features supported by the AIP add-in are now supported by built-in labeling. For a more detailed list of capabilities, minimum versions that might be needed, and configuration information, see [Manage sensitivity labels in Office apps](sensitivity-labels-office-apps.md). +2. If the list of managed add-ins block the AIP add-in, as described in the previous section, you'll need to either remove these entries for the AIP add-in, or set their value to **1: The add-in is always enabled.** +## Feature parity for built-in labeling and the AIP add-in for Office apps ++Many of the labeling features supported by the AIP add-in are now supported by built-in labeling. For a more detailed list of available capabilities, minimum versions that might be needed, and configuration information, see [Manage sensitivity labels in Office apps](sensitivity-labels-office-apps.md). To support a specific feature, you might need to change your [Office update channel](/deployoffice/overview-update-channels). + More features are planned and in development. If there's a specific feature that you're interested in, check the [Microsoft 365 roadmap](https://www.microsoft.com/microsoft-365/roadmap?filters=Microsoft%20Information%20Protection&searchterms=label) and consider joining the [Microsoft Information Protection in Office Private Preview](https://aka.ms/MIP/PreviewRing). -Use the following information to help you identify if you're using a feature from the AIP add-in that isn't yet supported by built-in labeling: +Use the following information to help you identify if the features you use with the AIP add-in is currently available with built-in labeling. Features that aren't yet available but in planning or deployment might delay your final migration for users, but you can begin testing the other features now to expedite a later migration. |AIP add-in feature or capability|Built-in labeling | |:-|:-:| |**Category: General** || |Central reporting and auditing| | |Government Cloud||-|Admin can disable labeling <br> - All apps| | -|Admin can disable labeling <br> - Per app| In planning or development| +|Admin can disable labeling for all apps| | |**Category: User Experience** || |Labeling button on the ribbon|| |Multilanguage support for label names and tooltips|  |-|Visibility of labels on a toolbar|  | -|Label colors|  | +|Visibility of labels on a toolbar| [In preview](sensitivity-labels-office-apps.md#sensitivity-bar) | +|Label colors| [In preview](sensitivity-labels-office-apps.md#label-colors) | |**Category: Labeling actions** || |Manual labeling |  <br>[Learn more](https://support.microsoft.com/office/apply-sensitivity-labels-to-your-files-and-email-in-office-2f96e7cd-d5a4-403b-8bd7-4cc636bae0f9) | |Mandatory labeling | | Use the following information to help you identify if you're using a feature fro |User-defined permissions <br> - Do Not Forward for Outlook <br> - User and group custom permissions for Word, Excel, PowerPoint| | |User-defined permissions <br> - Organization-wide custom permissions by specifying domains for Word, Excel, PowerPoint | [In preview](encryption-sensitivity-labels.md#support-for-organization-wide-custom-permissions) | |Co-authoring and AutoSave |  |-|Double key encryption | In planning or development | -|Document revocation for users | Under review | | | | +Remember to use the [Microsoft 365 roadmap](https://www.microsoft.com/microsoft-365/roadmap?filters=Microsoft%20Information%20Protection&searchterms=label) to identify and track new features in development. + ### Support for PowerShell advanced settings -The AIP client supports many customizations by using [PowerShell advanced settings](/azure/information-protection/rms-client/clientv2-admin-guide-customizations#configuring-advanced-settings-for-the-client-via-powershell). Some of these advanced settings are now supported by built-in labeling, as documented in [New-Label](/powershell/module/exchange/new-label) or [Set-Label](/powershell/module/exchange/set-label), and [New-LabelPolicy](/powershell/module/exchange/new-labelpolicy) or [Set-LabelPolicy](/powershell/module/exchange/set-labelpolicy). +The AIP client supports many customizations by using [PowerShell advanced settings](/azure/information-protection/rms-client/clientv2-admin-guide-customizations#configuring-advanced-settings-for-the-client-via-powershell). For the advanced settings applicable to Office apps that are also supported by built-in labeling, see the list in [New-Label](/powershell/module/exchange/new-label) or [Set-Label](/powershell/module/exchange/set-label), and [New-LabelPolicy](/powershell/module/exchange/new-labelpolicy) or [Set-LabelPolicy](/powershell/module/exchange/set-labelpolicy). -However, you might find you don't need to use PowerShell to configure the supported settings because they're included in the standard configuration from the Microsoft Purview compliance portal. For example, the ability to turn off mandatory labeling for Outlook and set a different default label. +However, you might find you don't need to use PowerShell to configure the supported settings because they're included in the standard configuration from the Microsoft Purview compliance portal. For example, UI configuration to choose label colors, and turn off mandatory labeling for Outlook. -The following configurations from the AIP add-in aren't yet supported by built-in labeling include: +The following configurations from the AIP add-in that aren't yet supported by built-in labeling include: - [Label inheritance from email attachments](/azure/information-protection/rms-client/clientv2-admin-guide-customizations#for-email-messages-with-attachments-apply-a-label-that-matches-the-highest-classification-of-those-attachments) - [S/MIME for Outlook](/azure/information-protection/rms-client/clientv2-admin-guide-customizations#configure-a-label-to-apply-smime-protection-in-outlook) The following configurations from the AIP add-in aren't yet supported by built-i ## Features not planned to be supported by built-in labeling for Office apps -Although new capabilities for built-in labeling are being added all the time, the AIP Office Add-in supports the following capabilities that aren't planned to be available in future releases for built-in labeling: +Although new capabilities for built-in labeling are being added all the time, the AIP Office add-in supports the following capabilities that aren't planned to be available in future releases for built-in labeling: - Application of labels to Microsoft Office 97-2003 formats, such as .doc files - Local usage logging to the Windows event log - Permanently disconnected computers - Standalone editions of Office (sometimes called "Office Perpetual") rather than subscription-based -## Next steps +## Migration planning for the AIP add-in for Office apps ++To smoothly transition to using built-in labeling for Office apps, use the information on this page to prepare a migration plan that includes the following tasks: ++- Identify the features that you currently use, and test them with built-in labeling to ensure you understand the configuration and user experience. ++- Identify any new features that you want to use, and decide whether to include them in the migration or at a later stage. ++- Make sure all dependencies are in place, such as Microsoft 365 Apps for Enterprise is deployed with the correct update channel and the AIP add-in disabled, and the correct [licenses are assigned to users](/office365/servicedescriptions/microsoft-365-service-descriptions/microsoft-365-tenantlevel-services-licensing-guidance/microsoft-365-security-compliance-licensing-guidance#microsoft-purview-information-protection-sensitivity-labeling). -For instructions to create and configure these labeling capabilities, see [Create and configure sensitivity labels and their policies](create-sensitivity-labels.md). +- Update any internal documentation and training, and prepare your help desk and users for change. -> [!TIP] -> If you already have sensitivity labels in the Microsoft Purview compliance portal, you won't be eligible for the automatic creation of default labels. However, you might still find it useful to reference their configuration: [Default sensitivity labels](mip-easy-trials.md#default-sensitivity-labels). +To help you with your migration journey, we recommend the [migration guidance and playbook from Microsoft Purview Customer Experience Engineering (CxE)](https://microsoft.github.io/ComplianceCxE/playbooks/AIP2MIPPlaybook). |
| compliance | Sensitivity Labels Coauthoring | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sensitivity-labels-coauthoring.md | Make sure you understand the following prerequisites before you turn on this fea - **Azure Information Protection unified labeling client and scanner:** - Minimum version [2.12.62.0](/information-protection/rms-client/unifiedlabelingclient-version-release-history#version-212620) that you can install from the [Microsoft Download Center](https://www.microsoft.com/en-us/download/details.aspx?id=53018) - For Office apps, requires minimum versions listed for Microsoft 365 Apps for enterprise+ - Additionally, you're not using [Double Key Encryption](double-key-encryption.md) in the same tenant - **OneDrive sync app for Windows or macOS:** - Minimum version of 19.002.0121.0008 Before you enable the tenant setting for co-authoring for files encrypted with s Specific to Excel: Metadata for a sensitivity label that doesn't apply encryption can be deleted from a file if somebody edits and saves that file by using a version of Excel that doesn't support the metadata changes for sensitivity labels. -- Co-authoring and AutoSave aren't supported and don't work for labeled and encrypted Office documents that use any of the following [configurations for encryption](encryption-sensitivity-labels.md#configure-encryption-settings):+- Co-authoring and AutoSave aren't supported and don't work for labeled and encrypted Office documents that use either of the following [configurations for encryption](encryption-sensitivity-labels.md#configure-encryption-settings): - **Let users assign permissions when they apply the label** and the checkbox **In Word, PowerPoint, and Excel, prompt users to specify permissions** is selected. This configuration is sometimes referred to as "user-defined permissions". - **User access to content expires** is set to a value other than **Never**.- - **Double Key Encryption** is selected. - For labels with any of these encryption configurations, the labels display in Office apps. However, when users select these labels and nobody else is editing the document, they're warned that co-authoring and AutoSave won't be available. If somebody else is editing the document, users see a message that the labels can't be applied. + For labels with either of these encryption configurations, the labels display in Office apps. However, when users select these labels and nobody else is editing the document, they're warned that co-authoring and AutoSave won't be available. If somebody else is editing the document, users see a message that the labels can't be applied. - If you use the Azure Information Protection unified labeling client: Check the documentation for this labeling client for [more requirements or limitations](/azure/information-protection/known-issues#known-issues-for-co-authoring). > [!NOTE] |
| compliance | Sensitivity Labels Office Apps | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sensitivity-labels-office-apps.md | Use the information in this article to help you successfully manage sensitivity To use sensitivity labels that are built into Office desktop apps for Windows and Mac, you must use a subscription edition of Office. This labeling client doesn't support standalone editions of Office, sometimes called "Office Perpetual". -If you can't upgrade to Microsoft 365 Apps for enterprise for the subscription versions of Office, for Windows computers only, you can use the [Azure Information Protection (AIP) unified labeling client](/azure/information-protection/rms-client/aip-clientv2). However, this client is now in [maintenance mode](https://techcommunity.microsoft.com/t5/security-compliance-and-identity/announcing-aip-unified-labeling-client-maintenance-mode-and/ba-p/3043613) and we don't recommend you use the AIP add-in for Office apps unless you have to. For more information, see [Why choose built-in labeling over the AIP add-in for Office apps](sensitivity-labels-aip.md). +The [Azure Information Protection (AIP) unified labeling client](/azure/information-protection/rms-client/aip-clientv2) is now in [maintenance mode](https://techcommunity.microsoft.com/t5/security-compliance-and-identity/announcing-aip-unified-labeling-client-maintenance-mode-and/ba-p/3043613). If you currently use this client for labeling in Office apps, we recommend you move to built-in labeling. For more information, see [Migrate the Azure Information Protection (AIP) add-in to built-in labeling for Office apps](sensitivity-labels-aip.md). ## Support for sensitivity label capabilities in apps -The following tables list the minimum Office version that introduced specific capabilities for sensitivity labels that are built in to Office apps. Or, if the label capability is in public preview or under review for a future release. Use the [Microsoft 365 roadmap](https://www.microsoft.com/microsoft-365/roadmap?filters=Microsoft%20Information%20Protection&searchterms=label) for details about new capabilities that are planned for future releases. +The following tables list the minimum Office version that introduced specific capabilities for sensitivity labels that are built in to Office apps. Or, if the label capability is in public preview or under review for a future release: ++- Table: [Sensitivity label capabilities in Word, Excel, and PowerPoint](#sensitivity-label-capabilities-in-word-excel-and-powerpoint) +- Table: [Sensitivity label capabilities in Outlook](#sensitivity-label-capabilities-in-outlook) ++Use the [Microsoft 365 roadmap](https://www.microsoft.com/microsoft-365/roadmap?filters=Microsoft%20Information%20Protection&searchterms=label) for details about new capabilities that are planned for future releases. New versions of Office apps are made available at different times for different update channels. For Windows, you'll get the new capabilities earlier when you are on the Current Channel or Monthly Enterprise Channel, rather than Semi-Annual Enterprise Channel. The minimum version numbers can also be different from one update channel to the next. For more information, see [Overview of update channels for Microsoft 365 Apps](/deployoffice/overview-update-channels) and [Update history for Microsoft 365 Apps](/officeupdates/update-history-microsoft365-apps-by-date). -New capabilities that are in private preview are not included in the table but you might be able to join these previews by nominating your organization for the [Microsoft Information Protection private preview program](https://aka.ms/mip-preview). +New capabilities that are in private preview are not included in the tables but you might be able to join these previews by nominating your organization for the [Microsoft Information Protection private preview program](https://aka.ms/mip-preview). Office for iOS and Office for Android: Sensitivity labels are built into the [Office app](https://www.microsoft.com/en-us/microsoft-365/blog/2020/02/19/new-office-app-android-ios-available/). The numbers listed are the minimum Office application versions required for each |Capability |Windows |Mac |iOS |Android |Web | |--|-:|-|-|--|-|+|[AIP add-in disabled by default](sensitivity-labels-aip.md#how-to-configure-newer-versions-of-office-to-enable-the-aip-add-in)| Preview: Rolling out to [Beta Channel](https://office.com/insider) | Not relevant | Not relevant | Not relevant| Not relevant | |[Manually apply, change, or remove label](https://support.microsoft.com/en-us/office/apply-sensitivity-labels-to-your-files-and-email-in-office-2f96e7cd-d5a4-403b-8bd7-4cc636bae0f9)| Current Channel: 1910+ <br /><br> Monthly Enterprise Channel: 1910+ <br /><br> Semi-Annual Enterprise Channel: 2002+ | 16.21+ | 2.21+ | 16.0.11231+ | [Yes - opt-in](sensitivity-labels-sharepoint-onedrive-files.md) | |[Multi-language support](create-sensitivity-labels.md#additional-label-settings-with-security--compliance-powershell)| Current Channel: 1910+ <br /><br> Monthly Enterprise Channel: 1910+ <br /><br> Semi-Annual Enterprise Channel: 2002+ | 16.21+ | 2.21+ | 16.0.11231+ | Under review | |[Apply a default label](sensitivity-labels.md#what-label-policies-can-do) to new documents | Current Channel: 1910+ <br /><br> Monthly Enterprise Channel: 1910+ <br /><br> Semi-Annual Enterprise Channel: 2002+ | 16.21+ | 2.21+ | 16.0.11231+ | [Yes - opt-in](sensitivity-labels-sharepoint-onedrive-files.md) | The numbers listed are the minimum Office application versions required for each |Capability |Outlook for Windows |Outlook for Mac |Outlook on iOS |Outlook on Android |Outlook on the web | |--|-:|-||-|-|+|[AIP add-in disabled by default](sensitivity-labels-aip.md#how-to-configure-newer-versions-of-office-to-enable-the-aip-add-in)| Preview: Rolling out to [Beta Channel](https://office.com/insider) | Not relevant | Not relevant | Not relevant| Not relevant | |[Manually apply, change, or remove label](https://support.microsoft.com/en-us/office/apply-sensitivity-labels-to-your-files-and-email-in-office-2f96e7cd-d5a4-403b-8bd7-4cc636bae0f9)| Current Channel: 1910+ <br /><br> Monthly Enterprise Channel: 1910+ <br /><br> Semi-Annual Enterprise Channel: 2002+ | 16.21+ | 4.7.1+ | 4.0.39+ | Yes | |[Multi-language support](create-sensitivity-labels.md#additional-label-settings-with-security--compliance-powershell)| Current Channel: 1910+ <br /><br> Monthly Enterprise Channel: 1910+ <br /><br> Semi-Annual Enterprise Channel: 2002+ | 16.21+ | 4.7.1+ | 4.0.39+ | Yes | |[Apply a default label](sensitivity-labels.md#what-label-policies-can-do) | Current Channel: 1910+ <br /><br> Monthly Enterprise Channel: 1910+ <br /><br> Semi-Annual Enterprise Channel: 2002+ | 16.21+ | 4.7.1+ | 4.0.39+ | Yes | Requires the [new Outlook for Mac](https://support.microsoft.com/office/the-new- ## Office built-in labeling client and the Azure Information Protection client -If users have the [Azure Information Protection (AIP) client](/azure/information-protection/rms-client/aip-clientv2) installed on their Windows computers, by default, built-in labels are turned off in [Windows Office apps that support them](#labeling-client-for-desktop-apps). Because built-in labels don't use an Office add-in, as used by the AIP client, they have the benefit of more stability and better performance. They also support the latest features, such as advanced classifiers. +If users have the [Azure Information Protection (AIP) client](/azure/information-protection/rms-client/aip-clientv2) installed on their Windows computers, built-in labels are the new default for the latest Windows Office apps that [support labeling](#labeling-client-for-desktop-apps). Because built-in labels don't use an Office add-in, as used by the AIP client, they have the benefit of more stability and better performance. They also support the latest features, such as advanced classifiers. > [!NOTE]-> If you're not seeing the labeling features you expect on Windows computers, despite confirming the minimum supported versions for your Office update channel, it might be because you need to [disable the AIP add-in](sensitivity-labels-aip.md#how-to-disable-the-aip-add-in-to-use-built-in-labeling-for-office-apps). +> If you're not seeing the labeling features you expect on Windows computers, despite confirming the minimum supported versions for your Office update channel, it might be because you need to [disable the AIP add-in](sensitivity-labels-aip.md#how-to-disable-the-aip-add-in-to-use-built-in-labeling-for-office-apps) for older versions of Office. -To learn more about labeling support with the AIP client, and how to disable this client just in Office apps, see [Why choose built-in labeling over the AIP add-in for Office apps](sensitivity-labels-aip.md). +To learn more about labeling support with the AIP client, and how to disable this client just in Office apps, see [Migrate the Azure Information Protection (AIP) add-in to built-in labeling for Office apps](sensitivity-labels-aip.md). ## If you need to turn off built-in labeling in Office apps on Windows Because this setting is specific to Windows Office apps, it has no impact on oth ## Office file types supported -Office apps that have built-in labeling for Word, Excel, and PowerPoint files support the Open XML format (such as .docx and .xlsx) but not the Microsoft Office 97-2003 format (such as .doc and .xls), Open Document Format (such as .odt and .ods), or other formats. When a file type is not supported for built-in labeling, the **Sensitivity** button is not available in the Office app. +Generally, Office apps that have built-in labeling for Word, Excel, and PowerPoint files support the Open XML format (such as .docx and .xlsx) but not the Microsoft Office 97-2003 format (such as .doc and .xls), Open Document Format (such as .odt and .ods), or other formats. When a file type is not supported for built-in labeling, the **Sensitivity** button is not available in the Office app. ++For specific file types supported for SharePoint and OneDrive when these services are enabled for sensitivity labels, see [Enable sensitivity labels for Office files in SharePoint and OneDrive](sensitivity-labels-sharepoint-onedrive-files.md#supported-file-types). The Azure Information Protection unified labeling client supports both the Open XML format and the Microsoft Office 97-2003 format. For more information, see [File types supported by the Azure Information Protection unified labeling client](/azure/information-protection/rms-client/clientv2-admin-guide-file-types) from that client's admin guide. As part of this high visibility, these labels also support colors. For more info Newly created labels don't have a color by default. If your labels were [migrated from Azure Information Protection](/azure/information-protection/configure-policy-migrate-labels) or you configured label colors for the Azure Information Protection unified labeling client, these label colors are now displayed in apps that support them. -Use the Microsoft Purview compliance portal to select one of 10 standard colors for sensitivity labels. This configuration is on the first page of the label configuration after the label name and description. +Use the Microsoft Purview compliance portal to select one of 10 standard colors for sensitivity labels. The **Label color** configuration is on the first page of the label configuration after the label name and description. You can't select colors for sublabels because they automatically inherit the label color from their parent label. -If the label is configured for a different color from one of the 10 colors, you see a **Custom color** option selected and the standard color options aren't available: -- +If a label is configured for a different color from one of the 10 default colors, you see a **Use previously assigned customer color** checkbox selected, and the standard color options aren't available. You can change the custom color to one of the standard colors by first clearing the checkbox, and then you can select one of the standard colors. -You can change the custom color to one of the standard colors by first removing the custom color selection, and then selecting one of the standard colors. But you can't use the compliance portal to configure a different custom color. Instead, use PowerShell, as described in the next section. +You can't use the compliance portal to configure a different custom color. Instead, use PowerShell, as described in the next section. #### Configuring custom colors by using PowerShell -You can use the [Security & Compliance Center PowerShell](/powershell/exchange/scc-powershell) advanced setting **color** to set a color for a sensitivity label. This configuration supports colors that you can't configure in the Microsoft Purview compliance portal. +You can use the [Security & Compliance PowerShell](/powershell/exchange/scc-powershell) advanced setting **color** to set a color for a sensitivity label. This configuration supports colors that you can't configure in the Microsoft Purview compliance portal. To specify your choice of color, use a hex triplet code for the red, green, and blue (RGB) components of the color. For example, #40e0d0 is the RGB hex value for turquoise. |
| compliance | Sensitivity Labels Sharepoint Onedrive Files | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sensitivity-labels-sharepoint-onedrive-files.md | These new capabilities work with [sensitivity labels](sensitivity-labels.md) onl Use the OneDrive sync app version 19.002.0121.0008 or later on Windows, and version 19.002.0107.0008 or later on Mac. Both these versions were released January 28, 2019, and are currently released to all rings. For more information, see the [OneDrive release notes](https://support.office.com/article/845dcf18-f921-435e-bf28-4e24b95e5fc0). After you enable sensitivity labels for Office files in SharePoint and OneDrive, users who run an older version of the sync app are prompted to update it. +## Supported file types ++After you've enabled sensitivity labels for SharePoint and OneDrive, the following file types are supported for sensitivity labeling scenarios. ++Applying a sensitivity label in Office on the web or in SharePoint: ++- **Word**: .docx, .docm +- **Excel**: .xlsx, .xlsm, .xlsb +- **PowerPoint**: .pptx, .ppsx ++Uploading a labeled document, and then extracting and displaying that sensitivity label: ++- **Word**: doc, .docx, .docm, .dot, .dotx, .dotm +- **Excel**: .xls, .xlt, .xla, .xlc, .xlm, .xlw, .xlsx, .xltx, .xlsm, .xltm, .xlam, .xlsb +- **PowerPoint**: .ppt, .pot, .pps, .ppa, .pptx, .ppsx, .ppsxm, .potx, .ppam, .pptm, .potm, .ppsm + ## Limitations - SharePoint and OneDrive can't process some files that are labeled and encrypted from Office desktop apps when these files contain PowerQuery data, data stored by custom add-ins, or custom XML parts such as Cover Page Properties, content type schemas, custom Document Information Panel, and Custom XSN. This limitation also applies to files that include a [bibliography](https://support.microsoft.com/en-us/office/create-a-bibliography-citations-and-references-17686589-4824-4940-9c69-342c289fa2a5), and to files that have a [Document ID](https://support.microsoft.com/office/enable-and-configure-unique-document-ids-ea7fee86-bd6f-4cc8-9365-8086e794c984) added when they are uploaded. |
| compliance | Sensitivity Labels Teams Groups Sites | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sensitivity-labels-teams-groups-sites.md | In addition to using [sensitivity labels](sensitivity-labels.md) to protect docu - External user access - External sharing from SharePoint sites - Access from unmanaged devices-- Authentication contexts (in preview)+- Authentication contexts - Default sharing link for a SharePoint site (PowerShell-only configuration)-- In preview: Site sharing settings (PowerShell-only configuration)+- Site sharing settings (PowerShell-only configuration) > [!IMPORTANT] > The settings for unmanaged devices and authentication contexts work in conjunction with Azure Active Directory Conditional Access. You must configure this dependent feature if you want to use a sensitivity label for these settings. Additional information is included in the instructions that follow. After sensitivity labels are enabled for containers as described in the previous For additional configuration information, see [More information about the dependencies for the unmanaged devices option](#more-information-about-the-dependencies-for-the-unmanaged-devices-option) at the end of this section. - - **Choose an existing authentication context**: Currently in preview, this option lets you enforce more stringent access conditions when users access SharePoint sites that have this label applied. These conditions are enforced when you select an existing authentication context that has been created and published for your organization's Conditional Access deployment. If users don't meet the configured conditions or if they use apps that don't support authentication contexts, they are denied access. + - **Choose an existing authentication context**: This option lets you enforce more stringent access conditions when users access SharePoint sites that have this label applied. These conditions are enforced when you select an existing authentication context that has been created and published for your organization's Conditional Access deployment. If users don't meet the configured conditions or if they use apps that don't support authentication contexts, they are denied access. For additional configuration information, see [More information about the dependencies for the authentication context option](#more-information-about-the-dependencies-for-the-authentication-context-option) at the end of this section. Not all apps support authentication contexts. If a user with an unsupported app - iOS: Rolling out in 12.30 - Android: Not yet supported -Known limitations for this preview: +Known limitations: - For the OneDrive sync app, supported for OneDrive only and not for other sites. For more information and instructions, see [Use sensitivity labels to configure ### Configure site sharing permissions by using PowerShell advanced settings -> [!NOTE] -> This label setting is currently in preview. - Another PowerShell advanced setting that you can configure for the sensitivity label to be applied to a SharePoint site is **MembersCanShare**. This setting is the equivalent configuration that you can set from the SharePoint admin center > **Site permissions** > **Site Sharing** > **Change how members can share** > **Sharing permissions**. The three options are listed with the equivalent values for the PowerShell advanced setting **MembersCanShare**: |
| compliance | Sensitivity Labels | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sensitivity-labels.md | Similarly for users in the legal department, who are assigned the third policy w ## Sensitivity labels and Azure Information Protection -The sensitivity labels that are built into Microsoft 365 Apps on Windows, macOS, iOS, and Android look and behave very similarly across these devices to provide users with a consistent labeling experience. However, on Windows computers, you can also use the [Azure Information Protection (AIP) client](/azure/information-protection/rms-client/aip-clientv2). This client is now in [maintenance mode](https://techcommunity.microsoft.com/t5/security-compliance-and-identity/announcing-aip-unified-labeling-client-maintenance-mode-and/ba-p/3043613). +The sensitivity labels that are built into Microsoft 365 Apps on Windows, macOS, iOS, and Android look and behave very similarly across these devices to provide users with a consistent labeling experience. However, on Windows computers, you can also use the [Azure Information Protection (AIP) client](/azure/information-protection/rms-client/aip-clientv2). This client is now in [maintenance mode](https://techcommunity.microsoft.com/t5/security-compliance-and-identity/announcing-aip-unified-labeling-client-maintenance-mode-and/ba-p/3043613) and when installed, is no longer the default labeling client for the latest Office apps. -If you're using the AIP client, see [Why choose built-in labeling over the AIP add-in for Office apps](sensitivity-labels-aip.md) to understand and manage your labeling choices for Windows computers. +If you're using the AIP client for labeling in Office apps, we recommend you move to built-in labeling. For more information, see [Migrate the Azure Information Protection (AIP) add-in to built-in labeling for Office apps](sensitivity-labels-aip.md). ### Azure Information Protection labels |
| compliance | Sit Defn All Creds | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sit-defn-all-creds.md | + + Title: "All credentials entity definition" +f1.keywords: +- CSH +++ Last updated :+audience: Admin +search.appverid: MET150 ++f1_keywords: +- 'ms.o365.cc.UnifiedDLPRuleContainsSensitiveInformation' ++ms.localizationpriority: medium ++- tier3 +- purview-compliance +hideEdit: true +feedback_system: None +recommendations: false +description: "All credentials sensitive information type entity definition." +++# All credential sensitive information types ++All credentials is a bundled entity sensitive information type (SIT). It detects credentials from all supported services and environments, which include Amazon, Azure, GitHub, Google, Microsoft general, Slack and more. +++## Format ++Various ++## Pattern ++Various ++## Checksum ++No ++## Description ++The All credentials SIT is a bundled SIT that scans for individual credential types. This includes checksum evaluated values and keyword/pattern combinations. The All credential entity scans for any of the underlying credential information type checksums and/or patterns are detected in a document. ++## Contains ++This bundled entity SIT contains these individual SITs: ++- [Amazon S3 Client Secret Access Key](sit-defn-amazon-s3-client-secret-access-key.md) +- [ASP.NET Machine Key](sit-defn-asp-net-machine-key.md) +- [Azure AD Client Access Token](sit-defn-azure-ad-client-access-token.md) +- [Azure AD Client Secret](sit-defn-azure-ad-client-secret.md) +- [Azure AD User Credentials](sit-defn-azure-ad-user-credentials.md) +- [Azure App Service Deployment Password](sit-defn-azure-app-service-deployment-password.md) +- [Azure Batch Shared Access Key](sit-defn-azure-batch-shared-access-key.md) +- [Azure Bot Framework Secret Key](sit-defn-azure-bot-framework-secret-key.md) +- [Azure Bot Service App Secret](sit-defn-azure-bot-service-app-secret.md) +- [Azure Cognitive Search API Key](sit-defn-azure-cognitive-search-api-key.md) +- [Azure Cognitive Service Key](sit-defn-azure-cognitive-service-key.md) +- [Azure Container Registry Access Key](sit-defn-azure-container-registry-access-key.md) +- [Azure COSMOS DB Account Access Key](sit-defn-azure-cosmos-db-account-access-key.md) +- [Azure Databricks Personal Access Token](sit-defn-azure-databricks-personal-access-token.md) +- [Azure DevOps App Secret](sit-defn-azure-devops-app-secret.md) +- [Azure DevOps Personal Access Token](sit-defn-azure-devops-personal-access-token.md) +- [Azure EventGrid Access Key](sit-defn-azure-eventgrid-access-key.md) +- [Azure Function Master / API Key](sit-defn-azure-function-master-api-key.md) +- [Azure IoT Shared Access Key](sit-defn-azure-iot-shared-access-key.md) +- [Azure Logic App Shared Access Signature](sit-defn-azure-logic-app-shared-access-signature.md) +- [Azure Machine Learning Web Service API Key](sit-defn-azure-machine-learning-web-service-api-key.md) +- [Azure Maps Subscription Key](sit-defn-azure-maps-subscription-key.md) +- [Azure Redis Cache Connection String Password](sit-defn-azure-redis-cache-connection-string-password.md) +- [Azure Service Bus Shared Access Signature](sit-defn-azure-service-bus-shared-access-signature.md) +- [Azure Shared Access Key / Web Hook Token](sit-defn-azure-shared-access-key-web-hook-token.md) +- [Azure SignalR Access Key](sit-defn-azure-signalr-access-key.md) +- [Azure SQL Connection String](sit-defn-azure-sql-connection-string.md) +- [Azure Storage Account Access Key](sit-defn-azure-storage-account-access-key.md) +- [Azure Storage Account Shared Access Signature](sit-defn-azure-storage-account-shared-access-signature.md) +- [Azure Storage Account Shared Access Signature for High Risk Resources](sit-defn-azure-storage-account-shared-access-signature-high-risk-resources.md) +- [Azure Subscription Management Certificate](sit-defn-azure-subscription-management-certificate.md) +- [Client Secret / API Key](sit-defn-client-secret-api-key.md) +- [General Password](sit-defn-general-password.md) +- [General Symmetric Key](sit-defn-general-symmetric-key.md) +- [GitHub Personal Access Token](sit-defn-github-personal-access-token.md) +- [Google API key](sit-defn-google-api-key.md) +- [Http Authorization Header](sit-defn-http-authorization-header.md) +- [Microsoft Bing Maps Key](sit-defn-google-api-key.md) +- [Slack Access Token](sit-defn-slack-access-token.md) +- [User Login Credentials](sit-defn-user-login-credentials.md) +- [X.509 Certificate Private Key](sit-defn-x-509-certificate-private-key.md) ++## Supported languages ++- English +- Bulgarian +- Chinese +- Croatian +- Czech +- Danish +- Estonian +- Finnish +- French +- German +- Hungarian +- Icelandic +- Irish +- Italian +- Japanese +- Latvian +- Lithuanian +- Maltese +- Dutch +- Norwegian +- Polish +- Portuguese +- Romanian +- Slovak +- Slovenian +- Spanish +- Swedish +- Turkish |
| compliance | Sit Defn Amazon S3 Client Secret Access Key | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sit-defn-amazon-s3-client-secret-access-key.md | Title: "Amazon S3 client secret access key entity definition (preview)" + Title: "Amazon S3 client secret access key entity definition" f1.keywords: - CSH recommendations: false description: "Amazon S3 client secret access key sensitive information type entity definition." -# Amazon S3 client secret access key (preview) +# Amazon S3 client secret access key [!INCLUDE [purview-preview](../includes/purview-preview.md)] -## Format +This SIT is also included in the [All credentials](sit-defn-all-creds.md) bundled SIT. ++ ## Format A combination of 40 characters consisting of letters, digits, and special characters. A combination of 40 characters consisting of: for example: +`abcdefghijklmnopqrst0123456789/+ABCDEFGH;` ++## Credential example + `AWS Secret: abcdefghijklmnopqrst0123456789/+ABCDEFGH;` ## Checksum No +SITs that have checksums use a unique calculation to check if the information is valid. This means when the **Checksum** value is **Yes**, the service can make a positive detection based on the sensitive data alone. When the **Checksum** value is **No** additional (secondary) elements must also be detected for the service to make a positive detection. + ## Definition This SIT is designed to match the security information that's used to access [Amazon Web Services.](/toolkit-for-eclipse/v1/user-guide/setup-credentials.html) |
| compliance | Sit Defn Asp Net Machine Key | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sit-defn-asp-net-machine-key.md | Title: "ASP.NET machine key entity definition (preview)" + Title: "ASP.NET machine key entity definition" f1.keywords: - CSH recommendations: false description: "ASP.NET machine key sensitive information type entity definition." -# ASP.NET machine key (preview) +# ASP.NET machine key [!INCLUDE [purview-preview](../includes/purview-preview.md)] -## Format +This SIT is also included in the [All credentials](sit-defn-all-creds.md) bundled SIT. ++ ## Format Symmetric keys in XML configuration. Various symmetric key formats in XML, for example: <machineKey decryptionKey="******** </br> <machineKey validationKey="******** ```+## Credential example ++`<machineKey validationKey="ABCDEF0123456789ABCDEF0123456789ABCDEF0123456789" decryptionKey="ABCDEF0123456789ABCDEF0123456789ABCDEF0123456789"` + ## Checksum No +SITs that have checksums use a unique calculation to check if the information is valid. This means when the **Checksum** value is **Yes**, the service can make a positive detection based on the sensitive data alone. When the **Checksum** value is **No** additional (secondary) elements must also be detected for the service to make a positive detection. + ## Definition |
| compliance | Sit Defn Azure Ad Client Access Token | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sit-defn-azure-ad-client-access-token.md | Title: "Azure AD client access token entity definition (preview)" + Title: "Azure AD client access token entity definition" f1.keywords: - CSH recommendations: false description: "Azure AD client access token sensitive information type entity definition." -# Azure AD client access token (preview) +# Azure AD client access token [!INCLUDE [purview-preview](../includes/purview-preview.md)] -## Format +This SIT is also included in the [All credentials](sit-defn-all-creds.md) bundled SIT. ++ ## Format A combination of up to 10,000 characters consisting of letters, digits, and special characters. A combination of up to 1,000 characters consisting for example: -`eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiIsIng1dCI6Ing0Nzh4eU9wbHNNMUg3TlhrN1N4MTd4MXVwYyIsImtpZCI6Ing0Nzh4` +`eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiIsIng1dCI6Ing0Nzh4eU9wbHNNMUg3TlhrN1N4MTd4MX...` ++ +## Credential example +`Authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiIsIng1dCI6Ing0Nzh4eU9wbHNNMUg3TlhrN1N4MTd4MX...` ++> [!IMPORTANT] +> This example has been truncated. ItΓÇÖs not a detectable example of this SIT. ## Checksum Yes +SITs that have checksums use a unique calculation to check if the information is valid. This means when the **Checksum** value is **Yes**, the service can make a positive detection based on the sensitive data alone. When the **Checksum** value is **No** additional (secondary) elements must also be detected for the service to make a positive detection. + ## Definition This SIT is designed to match the security information that's contains claims that one can use in [Azure Active Directory B2C](/azure/active-directory-b2c/active-directory-b2c-access-tokens) (Azure AD B2C) to identify the granted permissions to Azure resources. |
| compliance | Sit Defn Azure Ad Client Secret | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sit-defn-azure-ad-client-secret.md | Title: "Azure AD client secret entity definition (preview)" + Title: "Azure AD client secret entity definition" f1.keywords: - CSH recommendations: false description: "Azure AD client secret sensitive information type entity definition." -# Azure AD client secret (preview) +# Azure AD client secret [!INCLUDE [purview-preview](../includes/purview-preview.md)] -## Format +This SIT is also included in the [All credentials](sit-defn-all-creds.md) bundled SIT. ++ ## Format A combination of up to 40 characters consisting of letters, digits, and special characters. for example: `abc7Q~defghijklmnopqrs0t123456789-_.~` +## Credential example ++`"AppId=01234567-abcd-abcd-abcd-abcdef012345;AppSecret=abc7Q~defghijklmnopqrstuvwxyz-_.~0123"` + ## Checksum Yes +SITs that have checksums use a unique calculation to check if the information is valid. This means when the **Checksum** value is **Yes**, the service can make a positive detection based on the sensitive data alone. When the **Checksum** value is **No** additional (secondary) elements must also be detected for the service to make a positive detection. + ## Definition This SIT is designed to match the security information that's used to secure [Azure Active Directory service principals](/azure/active-directory/fundamentals/service-accounts-principal). |
| compliance | Sit Defn Azure Ad User Credentials | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sit-defn-azure-ad-user-credentials.md | Title: "Azure AD user credentials entity definition (preview)" + Title: "Azure AD user credentials entity definition" f1.keywords: - CSH recommendations: false description: "Azure AD user credentials sensitive information type entity definition." -# Azure AD user credentials (preview) +# Azure AD user credentials [!INCLUDE [purview-preview](../includes/purview-preview.md)] -## Format +This SIT is also included in the [All credentials](sit-defn-all-creds.md) bundled SIT. ++ ## Format A paired username and password related to *.onmicrosoft.com domain. Various password formats in XML, for example: ``` +## Credential example ++`username=user@tenant.onmicrosoft.com;password=ZYXWVU$1;` + ## Checksum No +SITs that have checksums use a unique calculation to check if the information is valid. This means when the **Checksum** value is **Yes**, the service can make a positive detection based on the sensitive data alone. When the **Checksum** value is **No** additional (secondary) elements must also be detected for the service to make a positive detection. + ## Definition This SIT is designed to match the security information that's used as individual user passwords to authenticate against [Azure Active Directory](/azure/active-directory/fundamentals/active-directory-users-reset-password-azure-portal). It uses several primary resources: -- Patterns of Plain-text username and password for Azure AD tenant.+- Patterns of Plain-text username and password for Azure AD tenants. - Patterns of Password context in code. - Patterns of Password context in XML. - Patterns of CredentialName, CredentialFeatures, AccountIdentityName, AccountIdentityValue, ResourceType, ResourceName. |
| compliance | Sit Defn Azure App Service Deployment Password | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sit-defn-azure-app-service-deployment-password.md | Title: "Azure App Service Deployment Password entity definition (preview)" + Title: "Azure App Service Deployment Password entity definition" f1.keywords: - CSH recommendations: false description: "Azure App Service Deployment Password sensitive information type entity definition." -# Azure App Service deployment password (preview) +# Azure App Service deployment password [!INCLUDE [purview-preview](../includes/purview-preview.md)] -## Format +This SIT is also included in the [All credentials](sit-defn-all-creds.md) bundled SIT. ++ ## Format A combination of 60 characters consisting of letters, digits, and special characters. for example: +## Credential example ++`userPWD=abcdefghijklmnopqrstuvwxyz0123456789/+ABCDEFGHIJKLMNOPQRSTUV;` + ## Checksum No +SITs that have checksums use a unique calculation to check if the information is valid. This means when the **Checksum** value is **Yes**, the service can make a positive detection based on the sensitive data alone. When the **Checksum** value is **No** additional (secondary) elements must also be detected for the service to make a positive detection. + ## Definition This SIT is designed to match the security information that's used to secure [Azure App Service deployment](/azure/app-service/deploy-configure-credentials) from a local computer. |
| compliance | Sit Defn Azure Batch Shared Access Key | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sit-defn-azure-batch-shared-access-key.md | Title: "Azure Batch Shared Access Key entity definition (preview)" + Title: "Azure Batch Shared Access Key entity definition" f1.keywords: - CSH recommendations: false description: "Azure Batch Shared Access Key sensitive information type entity definition." -# Azure Batch Shared Access Key (preview) +# Azure Batch Shared Access Key [!INCLUDE [purview-preview](../includes/purview-preview.md)] -## Format +This SIT is also included in the [All credentials](sit-defn-all-creds.md) bundled SIT. ++ ## Format A combination of 43 characters consisting of letters, digits, and special characters ending in an equals (=) sign that isn't part of the pattern. for example: `abcdefghijklmnopqrstuvwxyz0123456789/+ABCDE=` +## Credential example ++`Account=account.batch.azure.net;AccountKey=abcdefghijklmnopqrstuvwxyz0123456789/+ABCDE=;` + ## Checksum No +SITs that have checksums use a unique calculation to check if the information is valid. This means when the **Checksum** value is **Yes**, the service can make a positive detection based on the sensitive data alone. When the **Checksum** value is **No** additional (secondary) elements must also be detected for the service to make a positive detection. + ## Definition This SIT is designed to match the security information that's used to access [Azure Batch accounts.](/azure/batch/security-best-practices) |
| compliance | Sit Defn Azure Bot Framework Secret Key | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sit-defn-azure-bot-framework-secret-key.md | Title: "Azure Bot Framework secret key entity definition (preview)" + Title: "Azure Bot Framework secret key entity definition" f1.keywords: - CSH recommendations: false description: "Azure Bot Framework secret key sensitive information type entity definition." -# Azure Bot Framework secret key (preview) +# Azure Bot Framework secret key [!INCLUDE [purview-preview](../includes/purview-preview.md)] -## Format +This SIT is also included in the [All credentials](sit-defn-all-creds.md) bundled SIT. ++ ## Format A combination of 55 characters consisting of letters, digits, and special characters. for example: `abcdefghijk.lmn.opq.rstuvwxyz0123456789-_ABCDEFGHIJKLMNOPQRSTUV` +## Credential example ++`host: webchat.botframework.com/?s=abcdefghijklmnopqrstuvwxyz.0123456789_ABCDEabcdefghijkl&` + ## Checksum No +SITs that have checksums use a unique calculation to check if the information is valid. This means when the **Checksum** value is **Yes**, the service can make a positive detection based on the sensitive data alone. When the **Checksum** value is **No** additional (secondary) elements must also be detected for the service to make a positive detection. + ## Definition This SIT is designed to match the security information that's used to connect to [WebChat channels from Azure Bot services.](/azure/bot-service/bot-service-channel-connect-webchat?view=azure-bot-service-4.0) |
| compliance | Sit Defn Azure Bot Service App Secret | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sit-defn-azure-bot-service-app-secret.md | Title: "Azure Bot service app secret entity definition (preview)" + Title: "Azure Bot service app secret entity definition" f1.keywords: - CSH recommendations: false description: "Azure Bot service app secret sensitive information type entity definition." -# Azure Bot service app secret (preview) +# Azure Bot service app secret [!INCLUDE [purview-preview](../includes/purview-preview.md)] -## Format +This SIT is also included in the [All credentials](sit-defn-all-creds.md) bundled SIT. ++ ## Format A combination of up to 40 characters consisting of letters, digits, and special characters. for example: `abc7Q~defghijklmnopqrs0t123456789-_.~` +## Credential example ++`"account.azurewebsites.net/api/messages;AppId=01234567-abcd-abcd-abcd-abcdef012345;AppSecret="abcdeFGHIJ0K1234567%;[@"` + ## Checksum Yes +SITs that have checksums use a unique calculation to check if the information is valid. This means when the **Checksum** value is **Yes**, the service can make a positive detection based on the sensitive data alone. When the **Checksum** value is **No** additional (secondary) elements must also be detected for the service to make a positive detection. + ## Definition This SIT is designed to match the security information that's used to establish secure communication between an [Azure Bot, WebChat channels and client applications](/azure/bot-service/bot-builder-concept-authentication-types?view=azure-bot-service-4.0). |
| compliance | Sit Defn Azure Cognitive Search Api Key | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sit-defn-azure-cognitive-search-api-key.md | Title: "Azure Cognitive search API key entity definition (preview)" + Title: "Azure Cognitive search API key entity definition" f1.keywords: - CSH recommendations: false description: "Azure Cognitive search API key sensitive information type entity definition." -# Azure Cognitive Search API key (preview) +# Azure Cognitive Search API key [!INCLUDE [purview-preview](../includes/purview-preview.md)] -## Format +This SIT is also included in the [All credentials](sit-defn-all-creds.md) bundled SIT. ++ ## Format A combination of 32 characters consisting of letters and digits. for example: `abcdef0123456789abcdef0123456789` +## Credential example ++`host: account.search.windows.net; apikey: abcdef0123456789abcdef0123456789;` + ## Checksum No +SITs that have checksums use a unique calculation to check if the information is valid. This means when the **Checksum** value is **Yes**, the service can make a positive detection based on the sensitive data alone. When the **Checksum** value is **No** additional (secondary) elements must also be detected for the service to make a positive detection. + ## Definition This SIT is designed to match the security information that's used to authenticate inbound requests to [Azure Cognitive Search APIs.](/azure/search/search-security-api-keys) |
| compliance | Sit Defn Azure Cognitive Service Key | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sit-defn-azure-cognitive-service-key.md | Title: "Azure Cognitive Service key entity definition (preview)" + Title: "Azure Cognitive Service key entity definition" f1.keywords: - CSH recommendations: false description: "Azure Cognitive Service key sensitive information type entity definition." -# Azure Cognitive Service key (preview) +# Azure Cognitive Service key [!INCLUDE [purview-preview](../includes/purview-preview.md)] -## Format +This SIT is also included in the [All credentials](sit-defn-all-creds.md) bundled SIT. ++ ## Format A combination of 32 characters consisting of letters and digits. for example: `abcdef0123456789abcdef0123456789` +## Credential example ++`cognitiveservices.azure.com...apikey= abcdef0123456789abcdef0123456789;` + ## Checksum No +SITs that have checksums use a unique calculation to check if the information is valid. This means when the **Checksum** value is **Yes**, the service can make a positive detection based on the sensitive data alone. When the **Checksum** value is **No** additional (secondary) elements must also be detected for the service to make a positive detection. + ## Definition This SIT is designed to match the security information that's used to authenticate requests to [Azure Cognitive Services.](/azure/search/search-security-api-keys) |
| compliance | Sit Defn Azure Container Registry Access Key | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sit-defn-azure-container-registry-access-key.md | Title: "Azure Container Registry access key entity definition (preview)" + Title: "Azure Container Registry access key entity definition" f1.keywords: - CSH recommendations: false description: "Azure Container Registry access key sensitive information type entity definition." -# Azure Container Registry access key (preview) +# Azure Container Registry access key [!INCLUDE [purview-preview](../includes/purview-preview.md)] -## Format +This SIT is also included in the [All credentials](sit-defn-all-creds.md) bundled SIT. ++ ## Format A combination of 32 characters consisting of letters, digits, and special characters. for example: `abcdefghijklmnopqr0123456789/+AB` +## Credential example ++`account.azurecr.io/ #docker password: abcdefghijklmnopqr0123456789/+AB;` + ## Checksum No +SITs that have checksums use a unique calculation to check if the information is valid. This means when the **Checksum** value is **Yes**, the service can make a positive detection based on the sensitive data alone. When the **Checksum** value is **No** additional (secondary) elements must also be detected for the service to make a positive detection. + ## Definition This SIT is designed to match the security information that's used to access [Azure Container Registry](/azure/container-registry/container-registry-authentication) services as an admin account. |
| compliance | Sit Defn Azure Cosmos Db Account Access Key | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sit-defn-azure-cosmos-db-account-access-key.md | Title: "Azure COSMOS DB account access key entity definition (preview)" + Title: "Azure COSMOS DB account access key entity definition" f1.keywords: - CSH recommendations: false description: "Azure COSMOS DB account access key sensitive information type entity definition." -# Azure COSMOS DB account access key (preview) +# Azure COSMOS DB account access key [!INCLUDE [purview-preview](../includes/purview-preview.md)] -## Format +This SIT is also included in the [All credentials](sit-defn-all-creds.md) bundled SIT. ++ ## Format A combination of 88 characters consisting of letters, digits, and special characters. for example: `abcdefghijklmnopqrstuvwxyz0123456789/+ABCDEabcdefghijklmnopqrstuvwxyz0123456789/+ABCDE==` +## Credential example ++`AccountEndpoint=https://account.documents.azure.com;AccountKey=abcdefghijklmnopqrstuvwxyz0123456789/+ABCDEabcdefghijklmnopqrstuvwxyz0123456789/+ABCDE==` + ## Checksum No +SITs that have checksums use a unique calculation to check if the information is valid. This means when the **Checksum** value is **Yes**, the service can make a positive detection based on the sensitive data alone. When the **Checksum** value is **No** additional (secondary) elements must also be detected for the service to make a positive detection. + ## Definition This SIT is designed to match the security information that's used to provide access to administrative resources for [Azure COSMOS Database](/azure/cosmos-db/secure-access-to-data) accounts. |
| compliance | Sit Defn Azure Databricks Personal Access Token | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sit-defn-azure-databricks-personal-access-token.md | Title: "Azure Databricks personal access token entity definition (preview)" + Title: "Azure Databricks personal access token entity definition" f1.keywords: - CSH recommendations: false description: "Azure Databricks personal access token sensitive information type entity definition." -# Azure Databricks personal access token (preview) +# Azure Databricks personal access token [!INCLUDE [purview-preview](../includes/purview-preview.md)] -## Format +This SIT is also included in the [All credentials](sit-defn-all-creds.md) bundled SIT. ++ ## Format A combination of 32 characters consisting of letters and digits. for example: `abcdef0123456789abcdef0123456789` +## Credential example ++`account.azuredatabricks.net;PAT=dapiabcdef0123456789abcdef0123456789;` + ## Checksum No +SITs that have checksums use a unique calculation to check if the information is valid. This means when the **Checksum** value is **Yes**, the service can make a positive detection based on the sensitive data alone. When the **Checksum** value is **No** additional (secondary) elements must also be detected for the service to make a positive detection. + ## Definition This SIT is designed to match the security information that's used to authenticate to the [Azure Databricks REST API](/azure/databricks/administration-guide/access-control/tokens). |
| compliance | Sit Defn Azure Devops App Secret | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sit-defn-azure-devops-app-secret.md | Title: "Azure DevOps app secret entity definition (preview)" + Title: "Azure DevOps app secret entity definition" f1.keywords: - CSH recommendations: false description: "Azure DevOps app secret sensitive information type entity definition." -# Azure DevOps app secret (preview) +# Azure DevOps app secret [!INCLUDE [purview-preview](../includes/purview-preview.md)] -## Format +This SIT is also included in the [All credentials](sit-defn-all-creds.md) bundled SIT. ++ ## Format A combination of 52 characters consisting of letters, digits, and special characters. for example: `abcdefghijklmnopqrstuvwxyz234567abcdefghijklmnopqrst` +## Credential example ++`AdoAppId=...;AdoAppSecret=abcdefghijklmnopqrstuvwxyz234567abcdefghijklmnopqrst;` ++> [!IMPORTANT] +> This example has been invalidated. ItΓÇÖs not a detectable example of this SIT. + ## Checksum Yes +SITs that have checksums use a unique calculation to check if the information is valid. This means when the **Checksum** value is **Yes**, the service can make a positive detection based on the sensitive data alone. When the **Checksum** value is **No**, other (secondary) elements must also be detected for the service to make a positive detection. + ## Definition This SIT is designed to match the security information that's used to authenticate web app users for [Azure DevOps REST API access.](/azure/devops/integrate/get-started/authentication/oauth?view=azure-devops) |
| compliance | Sit Defn Azure Devops Personal Access Token | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sit-defn-azure-devops-personal-access-token.md | Title: "Azure DevOps personal access token entity definition (preview)" + Title: "Azure DevOps personal access token entity definition" f1.keywords: - CSH recommendations: false description: "Azure DevOps personal access token sensitive information type entity definition." -# Azure DevOps personal access token (preview) +# Azure DevOps personal access token [!INCLUDE [purview-preview](../includes/purview-preview.md)] -## Format +This SIT is also included in the [All credentials](sit-defn-all-creds.md) bundled SIT. ++ ## Format A combination of 52 characters consisting of letters, digits, and special characters. Any combination of 52 characters consisting of: for example: -`ntpi2ch67ci2vjzcohglogyygwo5fuyl365n2zdowwxhsys6jnoa` +`abcdefghijklmnopqrstuvwxyz234567abcdefghijklmnopqrst` ++## Credential example ++`URL="org.visualstudio.com/proj"; PAT = "abcdefghijklmnopqrstuvwxyz234567abcdefghijklmnopqrst"` ++> [!IMPORTANT] +> This example has been invalidated. ItΓÇÖs not a detectable example of this SIT. ## Checksum Yes +SITs that have checksums use a unique calculation to check if the information is valid. This means when the **Checksum** value is **Yes**, the service can make a positive detection based on the sensitive data alone. When the **Checksum** value is **No**, other (secondary) elements must also be detected for the service to make a positive detection. + ## Definition This SIT is designed to match the security information that's used as an alternate password to authenticate into [Azure DevOps.](/azure/devops/organizations/accounts/use-personal-access-tokens-to-authenticate?view=azure-devops) |
| compliance | Sit Defn Azure Eventgrid Access Key | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sit-defn-azure-eventgrid-access-key.md | Title: "Azure EventGrid access key entity definition (preview)" + Title: "Azure EventGrid access key entity definition" f1.keywords: - CSH recommendations: false description: "Azure EventGrid access key sensitive information type entity definition." -# Azure EventGrid access key (preview) +# Azure EventGrid access key [!INCLUDE [purview-preview](../includes/purview-preview.md)] -## Format +This SIT is also included in the [All credentials](sit-defn-all-creds.md) bundled SIT. ++ ## Format A combination of 43 characters consisting of letters, digits, and special characters ending in an equals sign (=) that isn't part of the pattern. for example: `abcdefghijklmnopqrstuvwxyz0123456789/+ABCDE=` +## Credential example ++`host: account.eventgrid.azure.net; accesskey: abcdefghijklmnopqrstuvwxyz0123456789/+ABCDE=;` + ## Checksum No +SITs that have checksums use a unique calculation to check if the information is valid. This means when the **Checksum** value is **Yes**, the service can make a positive detection based on the sensitive data alone. When the **Checksum** value is **No** additional (secondary) elements must also be detected for the service to make a positive detection. + ## Definition This SIT is designed to match the security information that's used to authenticate an application publishing events to [Azure Event Grid resources (topics and domains).](/azure/event-grid/get-access-keys) |
| compliance | Sit Defn Azure Function Master Api Key | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sit-defn-azure-function-master-api-key.md | Title: "Azure Function Master / API key entity definition (preview)" + Title: "Azure Function Master / API key entity definition" f1.keywords: - CSH recommendations: false description: "Azure Function Master / API key sensitive information type entity definition." -# Azure Function Master / API key (preview) +# Azure Function Master / API key [!INCLUDE [purview-preview](../includes/purview-preview.md)] -## Format +This SIT is also included in the [All credentials](sit-defn-all-creds.md) bundled SIT. ++ ## Format A combination of 56 characters consisting of letters, digits, and special characters. for example: abcdefghijklmnopqrstuvwxyz0123456789%2F%2BABCDEF0123456789%3D%3D +## Credential example ++`https://account.azurewebsites.net/api/function?code=abcdefghijklmnopqrstuvwxyz0123456789%2F%2BABCDEF0123456789%3D%3D` + ## Checksum No +SITs that have checksums use a unique calculation to check if the information is valid. This means when the **Checksum** value is **Yes**, the service can make a positive detection based on the sensitive data alone. When the **Checksum** value is **No** additional (secondary) elements must also be detected for the service to make a positive detection. + ## Definition This SIT is designed to match the security information that's used to request [Azure Function API](/azure/azure-functions/functions-how-to-use-azure-function-app-settings?tabs=portal) when its authorization level is set a value other than anonymous. |
| compliance | Sit Defn Azure Iot Connection String | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sit-defn-azure-iot-connection-string.md | Title: "Azure IoT connection string entity definition (preview)" + Title: "Azure IoT connection string entity definition" f1.keywords: - CSH recommendations: false description: "Azure IoT connection string sensitive information type entity definition." -# Azure IoT connection string (preview) +# Azure IoT connection string -### Format +#This SIT is also included in the [All credentials](sit-defn-all-creds.md) bundled SIT. ++ ## Format The string `HostName` followed by the characters and strings outlined in the pattern below, including the strings `azure-devices.net` and `SharedAccessKey`. The string `HostName` followed by the characters and strings outlined in the pat - any combination of 43 lower- or uppercase letters, digits, forward slash (/), or plus sign (+) - an equal sign (=) +## Credential example ++`HostName=account.azure-devices.net;SharedAccessKeyName=key;SharedAccessKey=abcdefghijklmnopqrstuvwxyz0123456789/+ABCDE=` + ## Checksum No +SITs that have checksums use a unique calculation to check if the information is valid. This means when the **Checksum** value is **Yes**, the service can make a positive detection based on the sensitive data alone. When the **Checksum** value is **No** additional (secondary) elements must also be detected for the service to make a positive detection. + ### Definition A DLP policy has high confidence that it's detected this type of sensitive information if, within a proximity of 300 characters: |
| compliance | Sit Defn Azure Logic App Shared Access Signature | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sit-defn-azure-logic-app-shared-access-signature.md | Title: "Azure Logic App shared access signature entity definition (preview)" + Title: "Azure Logic App shared access signature entity definition" f1.keywords: - CSH recommendations: false description: "Azure Logic App shared access signature sensitive information type entity definition." -# Azure Logic App shared access signature (preview) +# Azure Logic App shared access signature [!INCLUDE [purview-preview](../includes/purview-preview.md)] -## Format +This SIT is also included in the [All credentials](sit-defn-all-creds.md) bundled SIT. ++ ## Format A combination of up to 76 characters consisting of letters, digits, and special characters. for example: `abcdefghijklmnopqrstuvwxyz0123456789%2F%2BABCDE%3D` +## Credential example ++`https://account.logic.azure.com/?...&sig=abcdefghijklmnopqrstuvwxyz0123456789%2F%2BABCDE%3D` + ## Checksum No +SITs that have checksums use a unique calculation to check if the information is valid. This means when the **Checksum** value is **Yes**, the service can make a positive detection based on the sensitive data alone. When the **Checksum** value is **No** additional (secondary) elements must also be detected for the service to make a positive detection. + ## Definition This SIT is designed to match the security information that's used to grant access to a request endpoint on [Azure Logic Apps.](/azure/logic-apps/logic-apps-securing-a-logic-app?tabs=azure-portal) |
| compliance | Sit Defn Azure Machine Learning Web Service Api Key | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sit-defn-azure-machine-learning-web-service-api-key.md | Title: "Azure Machine Learning web service API key entity definition (preview)" + Title: "Azure Machine Learning web service API key entity definition" f1.keywords: - CSH recommendations: false description: "Azure Machine Learning web service API key sensitive information type entity definition." -# Azure Machine Learning web service API key (preview) +# Azure Machine Learning web service API key [!INCLUDE [purview-preview](../includes/purview-preview.md)] -## Format +This SIT is also included in the [All credentials](sit-defn-all-creds.md) bundled SIT. ++ ## Format A combination of 88 characters consisting of letters, digits, and special characters ending in two equals signs (==). for example: `abcdefghijklmnopqrstuvwxyz0123456789/+ABCDEabcdefghijklmnopqrstuvwxyz0123456789/+ABCDE==` +## Credential example ++`host: account.azureml.net/services/01234567-abcd-abcd-abcd-abcdef012345/workspaces/01234567-abcd-abcd-abcd-abcdef012345/; apikey: abcdefghijklmnopqrstuvwxyz0123456789/+ABCDEabcdefghijklmnopqrstuvwxyz0123456789/+ABCDE==;` + ## Checksum No +SITs that have checksums use a unique calculation to check if the information is valid. This means when the **Checksum** value is **Yes**, the service can make a positive detection based on the sensitive data alone. When the **Checksum** value is **No** additional (secondary) elements must also be detected for the service to make a positive detection. + ## Definition This SIT is designed to match the security information that's used to connect to [Azure Machine Learning Web services](/azure/machine-learning/classic/consume-web-services). |
| compliance | Sit Defn Azure Maps Subscription Key | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sit-defn-azure-maps-subscription-key.md | Title: "Azure Maps subscription key entity definition (preview)" + Title: "Azure Maps subscription key entity definition" f1.keywords: - CSH recommendations: false description: "Azure Maps subscription key sensitive information type entity definition." -# Azure Maps subscription key (preview) +# Azure Maps subscription key [!INCLUDE [purview-preview](../includes/purview-preview.md)] -## Format +This SIT is also included in the [All credentials](sit-defn-all-creds.md) bundled SIT. ++ ## Format A combination of 43 characters consisting of letters, digits, and special characters. for example: `abcdefghijklmnopqrstuvwxyz0123456789-_ABCDE` +## Credential example ++`host: atlas.microsoft.com; key: abcdefghijklmnopqrstuvwxyz0123456789-_ABCDE;` + ## Checksum No +SITs that have checksums use a unique calculation to check if the information is valid. This means when the **Checksum** value is **Yes**, the service can make a positive detection based on the sensitive data alone. When the **Checksum** value is **No** additional (secondary) elements must also be detected for the service to make a positive detection. + ## Definition This SIT is designed to match the security information that's used to access resources in [Azure Maps accounts](/azure/azure-maps/how-to-manage-authentication). |
| compliance | Sit Defn Azure Redis Cache Connection String Password | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sit-defn-azure-redis-cache-connection-string-password.md | Title: "Azure Redis cache connection string password entity definition (preview)" + Title: "Azure Redis cache connection string password entity definition" f1.keywords: - CSH recommendations: false description: "Azure Redis cache connection string password sensitive information type entity definition." -# Azure Redis cache connection string password (preview) +# Azure Redis cache connection string password [!INCLUDE [purview-preview](../includes/purview-preview.md)] -## Format +This SIT is also included in the [All credentials](sit-defn-all-creds.md) bundled SIT. ++ ## Format A combination of up to 20,000-characters consisting of letters, digits, and special characters. for example: `abcdefghijklmnopqrstuvwxyz0123456789/+ABCDE=` +## Credential example ++`HostName=account.redis.cache.windows.net;Password=abcdefghijklmnopqrstuvwxyz0123456789/+ABCDE=` + ## Checksum Yes +SITs that have checksums use a unique calculation to check if the information is valid. This means when the **Checksum** value is **Yes**, the service can make a positive detection based on the sensitive data alone. When the **Checksum** value is **No** additional (secondary) elements must also be detected for the service to make a positive detection. + ## Definition This SIT is designed to match the security information thatΓÇÖs used to connect to [Azure Cache for Redis servers](/azure/azure-cache-for-redis/). |
| compliance | Sit Defn Azure Service Bus Shared Access Signature | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sit-defn-azure-service-bus-shared-access-signature.md | Title: "Azure service bus shared access signature entity definition (preview)" + Title: "Azure service bus shared access signature entity definition" f1.keywords: - CSH recommendations: false description: "Azure service bus shared access signature sensitive information type entity definition." -# Azure service bus shared access signature (preview) +# Azure service bus shared access signature [!INCLUDE [purview-preview](../includes/purview-preview.md)] -## Format +This SIT is also included in the [All credentials](sit-defn-all-creds.md) bundled SIT. ++ ## Format A combination of 44-characters consisting of letters, digits, and special characters ending with an equals sign (=) that isn't part of the pattern. for example: `abcdefghijklmnopqrstuvwxyz0123456789%2F%2BABCDE%3D` +## Credential example ++`Endpoint=sb://account.servicebus.windows.net;SharedAccessKey=abcdefghijklmnopqrstuvwxyz0123456789/+ABCDE=` + ## Checksum No +SITs that have checksums use a unique calculation to check if the information is valid. This means when the **Checksum** value is **Yes**, the service can make a positive detection based on the sensitive data alone. When the **Checksum** value is **No** additional (secondary) elements must also be detected for the service to make a positive detection. + ## Definition This SIT is designed to match the security information thatΓÇÖs used to grant a user access to [Azure Service Bus resources](/azure/service-bus-messaging/service-bus-authentication-and-authorization) with specific rights. |
| compliance | Sit Defn Azure Shared Access Key Web Hook Token | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sit-defn-azure-shared-access-key-web-hook-token.md | Title: "Azure Shared Access key / Web Hook token signature entity definition (preview)"+ + Title: "Azure Shared Access key / Web Hook token signature entity definition" f1.keywords: - CSH recommendations: false description: "Azure Shared Access key / Web Hook token sensitive information type entity definition." -# Azure Shared Access key / Web Hook token (preview) +# Azure Shared Access key / Web Hook token [!INCLUDE [purview-preview](../includes/purview-preview.md)] -## Format +This SIT is also included in the [All credentials](sit-defn-all-creds.md) bundled SIT. ++ ## Format A combination of 44 characters consisting of letters, digits, and special characters. for example: `abcdefghijklmnopqrstuvwxyz0123456789%2F%2BABCDE%3D` +## Credential example ++`PrimaryKey=abcdefghijklmnopqrstuvwxyz0123456789/+ABCDE=;` + ## Checksum No +SITs that have checksums use a unique calculation to check if the information is valid. This means when the **Checksum** value is **Yes**, the service can make a positive detection based on the sensitive data alone. When the **Checksum** value is **No** additional (secondary) elements must also be detected for the service to make a positive detection. + ## Definition This SIT is designed to match the security information that's used to access general [Azure resources with restricted permission](/azure/notification-hubs/notification-hubs-push-notification-security). |
| compliance | Sit Defn Azure Signalr Access Key | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sit-defn-azure-signalr-access-key.md | Title: "Azure SignalR access key entity definition (preview)" + Title: "Azure SignalR access key entity definition" f1.keywords: - CSH recommendations: false description: "Azure SignalR access key sensitive information type entity definition." -# Azure SignalR access key (preview) +# Azure SignalR access key [!INCLUDE [purview-preview](../includes/purview-preview.md)] -## Format +This SIT is also included in the [All credentials](sit-defn-all-creds.md) bundled SIT. ++ ## Format A combination of 43 characters consisting of letters, digits, and special characters ending in an equals sign (=) that isn't part of the pattern. for example: `abcdefghijklmnopqrstuvwxyz0123456789/+ABCDE=` +## Credential example ++`host: account.service.signalr.net; accesskey: abcdefghijklmnopqrstuvwxyz0123456789/+ABCDE=;` + ## Checksum No +SITs that have checksums use a unique calculation to check if the information is valid. This means when the **Checksum** value is **Yes**, the service can make a positive detection based on the sensitive data alone. When the **Checksum** value is **No** additional (secondary) elements must also be detected for the service to make a positive detection. + ## Definition This SIT is designed to match the security information that's used to authenticate [Azure SignalR](/azure/azure-signalr/signalr-howto-key-rotation) clients when requests are made to the service. |
| compliance | Sit Defn Azure Sql Connection String | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sit-defn-azure-sql-connection-string.md | Title: "Azure SQL connection string entity definition (preview)" + Title: "Azure SQL connection string entity definition" f1.keywords: - CSH recommendations: false description: "Azure SQL connection string sensitive information type entity definition." -# Azure SQL connection string (preview) +# Azure SQL connection string [!INCLUDE [purview-preview](../includes/purview-preview.md)] -## Format +This SIT is also included in the [All credentials](sit-defn-all-creds.md) bundled SIT. ++ ## Format Up to 20,000-character combination of letters, digits, and special characters. Variant username and password formats, for example: `Service Account=...;Password=********;` <br> +## Credential example ++`server=server.database.windows.net;database=database;user=user;pwd=ZYXWVU_2;` + ## Checksum Yes +SITs that have checksums use a unique calculation to check if the information is valid. This means when the **Checksum** value is **Yes**, the service can make a positive detection based on the sensitive data alone. When the **Checksum** value is **No** additional (secondary) elements must also be detected for the service to make a positive detection. + ## Definition This SIT is designed to match the security information that's used to connect to [Azure SQL Databases](/azure/sql-database/sql-database-aad-authentication-configure). |
| compliance | Sit Defn Azure Storage Account Access Key | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sit-defn-azure-storage-account-access-key.md | Title: "Azure storage account access key entity definition (preview)" + Title: "Azure storage account access key entity definition" f1.keywords: - CSH recommendations: false description: "Azure storage account access key sensitive information type entity definition." -# Azure storage account access key (preview) +# Azure storage account access key [!INCLUDE [purview-preview](../includes/purview-preview.md)] -## Format +This SIT is also included in the [All credentials](sit-defn-all-creds.md) bundled SIT. ++ ## Format A combination of up to 20,000 characters consisting of letters, digits, and special characters. for example: `abcdefghijklmnopqrstuvwxyz0123456789/+ABCDEabcdefghijklmnopqrstuvwxyz0123456789/+ABCDE==` +## Credential example ++`Endpoint=account.table.core.windows.net;AccountName=account;AccountKey=abcdefghijklmnopqrstuvwxyz0123456789/+ABCDEabcdefghijklmnopqrstuvwxyz0123456789/+ABCDE==` + ## Checksum Yes +SITs that have checksums use a unique calculation to check if the information is valid. This means when the **Checksum** value is **Yes**, the service can make a positive detection based on the sensitive data alone. When the **Checksum** value is **No** additional (secondary) elements must also be detected for the service to make a positive detection. + ## Definition This SIT is designed to match the security information that's used to make request against [Azure Storage services](/rest/api/storageservices/authorize-with-shared-key), like Blob, Queue, Table and File services. |
| compliance | Sit Defn Azure Storage Account Shared Access Signature High Risk Resources | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sit-defn-azure-storage-account-shared-access-signature-high-risk-resources.md | description: "Azure Storage account shared access signature for high risk resour [!INCLUDE [purview-preview](../includes/purview-preview.md)] -## Format +This SIT is also included in the [All credentials](sit-defn-all-creds.md) bundled SIT. ++ ## Format A combination of 44 characters consisting of letters, digits, and special characters. for example: `abcdefghijklmnopqrstuvwxyz0123456789%2F%2BABCDE%3D` +## Credential example ++`https://account.blob.core.windows.net/file.cspkg?...&sig=abcdefghijklmnopqrstuvwxyz0123456789%2F%2BABCDE%3D` + ## Checksum No +SITs that have checksums use a unique calculation to check if the information is valid. This means when the **Checksum** value is **Yes**, the service can make a positive detection based on the sensitive data alone. When the **Checksum** value is **No** additional (secondary) elements must also be detected for the service to make a positive detection. + ## Definition This SIT is designed to match the security information that's used to grant restricted access rights to high risk [Azure Storage resources such as certificates, configurations, or deployment packages](/rest/api/storageservices/delegate-access-with-shared-access-signature). |
| compliance | Sit Defn Azure Storage Account Shared Access Signature | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sit-defn-azure-storage-account-shared-access-signature.md | Title: "Azure Storage account shared access signature entity definition (preview)" + Title: "Azure Storage account shared access signature entity definition" f1.keywords: - CSH recommendations: false description: "Azure Storage account shared access signature sensitive information type entity definition." -# Azure Storage account shared access signature (preview) +# Azure Storage account shared access signature [!INCLUDE [purview-preview](../includes/purview-preview.md)] -## Format +This SIT is also included in the [All credentials](sit-defn-all-creds.md) bundled SIT. ++ ## Format A combination of 44 characters consisting of letters, digits, and special characters. for example: `abcdefghijklmnopqrstuvwxyz0123456789%2F%2BABCDE%3D` +## Credential example ++`https://account.blob.core.windows.net/?sr=...&sv=...&st=...&se=...&sp=...&sig=abcdefghijklmnopqrstuvwxyz0123456789%2F%2BABCDE%3D` + ## Checksum No +SITs that have checksums use a unique calculation to check if the information is valid. This means when the **Checksum** value is **Yes**, the service can make a positive detection based on the sensitive data alone. When the **Checksum** value is **No** additional (secondary) elements must also be detected for the service to make a positive detection. + ## Definition This SIT is designed to match the security information that's used to grant restricted access rights to [Azure Storage resources](/rest/api/storageservices/delegate-access-with-shared-access-signature). |
| compliance | Sit Defn Azure Subscription Management Certificate | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sit-defn-azure-subscription-management-certificate.md | Title: "Azure subscription management certificate entity definition (preview)" + Title: "Azure subscription management certificate entity definition" f1.keywords: - CSH recommendations: false description: "Azure subscription management certificate sensitive information type entity definition." -# Azure subscription management certificate (preview) +# Azure subscription management certificate [!INCLUDE [purview-preview](../includes/purview-preview.md)] -## Format +This SIT is also included in the [All credentials](sit-defn-all-creds.md) bundled SIT. ++ ## Format A combination of up to 20,000 characters consisting of letters, digits, and special characters. for example: `MIIKcQIBAzCCCi0GCSqGSIb3DQEHAaCCCh4EggoaMIIKFjCCBg8GCSqGSIb3DQEHAaCCBgAEggX8MIIF+DCCBfQGCyqGSIb3DQEM` +## Credential example ++`<Subscription id="f70163aa-03a8-4f4a-8a30-d38e3f38fde4" ManagementCertificate="MIIPuQIBAzCCD38GCSqGS...` ++> [!IMPORTANT] +> This example has been truncated. ItΓÇÖs not a detectable example of this SIT. + ## Checksum Yes +SITs that have checksums use a unique calculation to check if the information is valid. This means when the **Checksum** value is **Yes**, the service can make a positive detection based on the sensitive data alone. When the **Checksum** value is **No** additional (secondary) elements must also be detected for the service to make a positive detection. + ## Definition This SIT is designed to match the security information that's used to authenticate with the [classic deployment model](/azure/azure-resource-manager/management/deployment-models) provided by Azure. Many programs and tools, like Visual Studio or the Azure SDK, use these certificates to automate configuration and deployment of various [Azure services](/azure/azure-api-management-certs). |
| compliance | Sit Defn Client Secret Api Key | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sit-defn-client-secret-api-key.md | Title: "Client secret / API key entity definition (preview)" + Title: "Client secret / API key entity definition" f1.keywords: - CSH recommendations: false description: "Client secret / API key sensitive information type entity definition." -# Client secret / API key (preview) +# Client secret / API key [!INCLUDE [purview-preview](../includes/purview-preview.md)] -## Format +This SIT is also included in the [All credentials](sit-defn-all-creds.md) bundled SIT. ++ ## Format A client secret or refresh token used in OAuth 2.0 protocol. for example: `abcdefghijklmnopqrstuvwxyz0123456789/+ABCDEabcdefghijklmnopqrstuvwxyz0123456789/+ABCDE==` +## Credential example ++`client_secret=abcdefghijklmnopqrstuvwxyz0123456789/+ABCDE=` + ## Checksum No +SITs that have checksums use a unique calculation to check if the information is valid. This means when the **Checksum** value is **Yes**, the service can make a positive detection based on the sensitive data alone. When the **Checksum** value is **No** additional (secondary) elements must also be detected for the service to make a positive detection. + ## Definition This SIT is designed to match the security information that's known only to the [OAuth application and the authorization server to exchange](/azure/active-directory/develop/active-directory-how-applications-are-added) for an access token at runtime. |
| compliance | Sit Defn General Password | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sit-defn-general-password.md | Title: "General password entity definition (preview)" + Title: "General password entity definition" f1.keywords: - CSH recommendations: false description: "General password sensitive information type entity definition." -# General Password (preview) +# General Password [!INCLUDE [purview-preview](../includes/purview-preview.md)] -## Format +This SIT is also included in the [All credentials](sit-defn-all-creds.md) bundled SIT. ++ ## Format Up to 20,000-character combination of letters, digits, and special characters. for example: `abcdefghijklmnopqrstuvwxyz0123456789/+ABCDEabcdefghijklmnopqrstuvwxyz0123456789/+ABCDE==` +## Credential example ++`<secret>ZYXWVU_3</secret>` + ## Checksum Yes +SITs that have checksums use a unique calculation to check if the information is valid. This means when the **Checksum** value is **Yes**, the service can make a positive detection based on the sensitive data alone. When the **Checksum** value is **No** additional (secondary) elements must also be detected for the service to make a positive detection. + ## Description This SIT is designed to match the security information that's like usernames and passwords used in general sign-in process [user login process](/azure/key-vault/quick-create-portal). It uses several primary resources: |
| compliance | Sit Defn General Symmetric Key | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sit-defn-general-symmetric-key.md | Title: "General Symmetric key entity definition (preview)" + Title: "General Symmetric key entity definition" f1.keywords: - CSH recommendations: false description: "General Symmetric key sensitive information type entity definition." -# General Symmetric key (preview) +# General Symmetric key [!INCLUDE [purview-preview](../includes/purview-preview.md)] -## Format +This SIT is also included in the [All credentials](sit-defn-all-creds.md) bundled SIT. ++ ## Format A combination of 44 characters consisting of letters, digits, and special characters. for example: `abcdefghijklmnopqrstuvwxyz0123456789/+ABCDEabcdefghijklmnopqrstuvwxyz0123456789/+ABCDE==` +## Credential example ++`key=abcdefghijklmnopqrstuvwxyz0123456789/+ABCDE=;` + ## Checksum No +SITs that have checksums use a unique calculation to check if the information is valid. This means when the **Checksum** value is **Yes**, the service can make a positive detection based on the sensitive data alone. When the **Checksum** value is **No** additional (secondary) elements must also be detected for the service to make a positive detection. + ## Definition This SIT is designed to match the security information that's used in [general authentication process.](/dotnet/api/system.security.cryptography.aes?view=net-5.0) |
| compliance | Sit Defn Github Personal Access Token | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sit-defn-github-personal-access-token.md | Title: "GitHub personal access token entity definition (preview)" + Title: "GitHub personal access token entity definition" f1.keywords: - CSH recommendations: false description: "GitHub personal access token sensitive information type entity definition." -# GitHub personal access token (preview) +# GitHub personal access token [!INCLUDE [purview-preview](../includes/purview-preview.md)] -## Format +This SIT is also included in the [All credentials](sit-defn-all-creds.md) bundled SIT. ++ ## Format A combination of 40 characters consisting of letters, digits, and special characters. for example: `abcdef0123456789abcdef0123456789abcdef01` +## Credential example ++`pat=ghp_abcdefghijklmnopqrstuvwxyzABCD012345` + ## Checksum Yes +SITs that have checksums use a unique calculation to check if the information is valid. This means when the **Checksum** value is **Yes**, the service can make a positive detection based on the sensitive data alone. When the **Checksum** value is **No** additional (secondary) elements must also be detected for the service to make a positive detection. + ## Definition This SIT is designed to match the security information that's used as an alternate password for authentication to GitHub when using [GitHub API or the command line](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token). |
| compliance | Sit Defn Google Api Key | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sit-defn-google-api-key.md | Title: "Google API key entity definition (preview)" + Title: "Google API key entity definition" f1.keywords: - CSH recommendations: false description: "Google API key sensitive information type entity definition." -# Google API key (preview) +# Google API key [!INCLUDE [purview-preview](../includes/purview-preview.md)] -## Format +This SIT is also included in the [All credentials](sit-defn-all-creds.md) bundled SIT. ++ ## Format A combination of 39 characters consisting of letters, digits, and special characters. for example: `AIzaefgh0123456789_-ABCDEFGHIJKLMNOPQRS` +## Credential example ++`apiKey=AIzaefgh0123456789_-ABCDEFGHIJKLMNOPQRS;` + ## Checksum No +SITs that have checksums use a unique calculation to check if the information is valid. This means when the **Checksum** value is **Yes**, the service can make a positive detection based on the sensitive data alone. When the **Checksum** value is **No** additional (secondary) elements must also be detected for the service to make a positive detection. + ## Definition This SIT is designed to match the security information that's used as a simple encrypted string that identifies a [Google REST API client](https://cloud.google.com/docs/authentication/api-keys) without any principal that is used to associate API requests with your project for quota and billing. |
| compliance | Sit Defn Http Authorization Header | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sit-defn-http-authorization-header.md | Title: "Http authorization header entity definition (preview)" + Title: "Http authorization header entity definition" f1.keywords: - CSH recommendations: false description: "Http authorization header sensitive information type entity definition." -# Http authorization header (preview) +# Http authorization header [!INCLUDE [purview-preview](../includes/purview-preview.md)] -## Format +This SIT is also included in the [All credentials](sit-defn-all-creds.md) bundled SIT. ++ ## Format An authorization header used in HTTP request. Various authentication header formats for example: `authorization: digest ********` <br> `authorization: negotiate ********` <br> +## Credential example ++`Authorization: Basic ABCDEFGHIJKLMNOPQRS0123456789;` + ## Checksum No +SITs that have checksums use a unique calculation to check if the information is valid. This means when the **Checksum** value is **Yes**, the service can make a positive detection based on the sensitive data alone. When the **Checksum** value is **No** additional (secondary) elements must also be detected for the service to make a positive detection. + ## Definition This SIT is designed to match the security information that's used in the header of an [HTTP request for authentication and authorization.](/dotnet/api/system.net.http.headers.httprequestheaders.authorization?view=netframework-4.8) |
| compliance | Sit Defn Microsoft Bing Maps Key | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sit-defn-microsoft-bing-maps-key.md | Title: "Microsoft Bing maps key entity definition (preview)" + Title: "Microsoft Bing maps key entity definition" f1.keywords: - CSH recommendations: false description: "Microsoft Bing maps key sensitive information type entity definition." -# Microsoft Bing maps key (preview) +# Microsoft Bing maps key [!INCLUDE [purview-preview](../includes/purview-preview.md)] -## Format +This SIT is also included in the [All credentials](sit-defn-all-creds.md) bundled SIT. ++ ## Format A combination of 64 characters consisting of letters, digits, and special characters. for example: `abcdefghijklmnopqrstuvwxyz0123456789-_ABCDEabcdefghijklmnopqrstu` +## Credential example ++`bingMapsKey=abcdefghijklmnopqrstuvwxyz0123456789-_ABCDEabcdefghijklmnopqrstu` + ## Checksum No +SITs that have checksums use a unique calculation to check if the information is valid. This means when the **Checksum** value is **Yes**, the service can make a positive detection based on the sensitive data alone. When the **Checksum** value is **No** additional (secondary) elements must also be detected for the service to make a positive detection. + ## Definition This SIT is designed to match the security information that's used to call [Bing Maps API.](/bingmaps/getting-started/bing-maps-dev-center-help/getting-a-bing-maps-key) |
| compliance | Sit Defn Slack Access Token | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sit-defn-slack-access-token.md | Title: "Slack access token entity definition (preview)" + Title: "Slack access token entity definition" f1.keywords: - CSH recommendations: false description: "Slack access token sensitive information type entity definition." -# Slack access token (preview) +# Slack access token [!INCLUDE [purview-preview](../includes/purview-preview.md)] -## Format +This SIT is also included in the [All credentials](sit-defn-all-creds.md) bundled SIT. ++ ## Format A combination of up to 34 characters consisting of letters, digits, and special characters. for example: `xoxp-abcdef-abcdef-abcdef-abcdef` +## Credential example ++`slack_token= xoxp-abcdef-abcdef-abcdef-abcdef;` + ## Checksum No +SITs that have checksums use a unique calculation to check if the information is valid. This means when the **Checksum** value is **Yes**, the service can make a positive detection based on the sensitive data alone. When the **Checksum** value is **No** additional (secondary) elements must also be detected for the service to make a positive detection. + ## Definition This SIT is designed to match the security information that's used to access [Slack platform functionalities](https://api.slack.com/docs/token-type) (for example Bot tokens, User tokens and App-level tokens). |
| compliance | Sit Defn User Login Credentials | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sit-defn-user-login-credentials.md | Title: "User login credentials entity definition (preview)" + Title: "User login credentials entity definition" f1.keywords: - CSH recommendations: false description: "User login credentials sensitive information type entity definition." -# User login credentials (preview) +# User login credentials [!INCLUDE [purview-preview](../includes/purview-preview.md)] -## Format +This SIT is also included in the [All credentials](sit-defn-all-creds.md) bundled SIT. ++ ## Format A paired username and password used in general authentication process. for example: `abcdefghijklmnopqrstuvwxyz0123456789/+ABCDEabcdefghijklmnopqrstuvwxyz0123456789/+ABCDE==` +## Credential example ++`{ "user": "user_name", "password": "ZYXWVU_2" }` + ## Checksum No +SITs that have checksums use a unique calculation to check if the information is valid. This means when the **Checksum** value is **Yes**, the service can make a positive detection based on the sensitive data alone. When the **Checksum** value is **No** additional (secondary) elements must also be detected for the service to make a positive detection. + ## Definition This SIT is designed to match the security information that's used in general [user login process](/azure/key-vault/quick-create-portal). |
| compliance | Sit Defn X 509 Certificate Private Key | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/sit-defn-x-509-certificate-private-key.md | Title: "X.509 certificate private key entity definition (preview)" + Title: "X.509 certificate private key entity definition" f1.keywords: - CSH description: "X.509 certificate private key sensitive information type entity de [!INCLUDE [purview-preview](../includes/purview-preview.md)] -## Format +This SIT is also included in the [All credentials](sit-defn-all-creds.md) bundled SIT. ++ ## Format A combination of up to 20,000 characters consisting of letters, digits, and special characters. for example: `--BEGIN PRIVATE KEY--` +## Credential example ++`--BEGIN PRIVATE KEY-- MIIPuQIBAzCCD38GCSqGSIb3DQEHAaCCD3AEgg9sMIIPaDCCBZ8GCSqGSIb3DQEHBqCCBZAw...` ++> [!IMPORTANT] +> This example has been truncated. ItΓÇÖs not a detectable example of this SIT. + ## Checksum Yes +SITs that have checksums use a unique calculation to check if the information is valid. This means when the **Checksum** value is **Yes**, the service can make a positive detection based on the sensitive data alone. When the **Checksum** value is **No** additional (secondary) elements must also be detected for the service to make a positive detection. + ## Definition This SIT is designed to match the security information that's used as a private component in [SSL certificates.](/azure/key-vault/certificate-scenarios) |
| compliance | Whats New | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/whats-new.md | Whether it be adding new solutions to the [Microsoft Purview compliance portal]( - [Increase classifier accuracy (preview)](data-classification-increase-accuracy.md) - This article shows you how to confirm whether items matched by a classifier are true positive (a Match) or a false positive (Not a match) and provide Match, or Not a match feedback. You can use that feedback to tune your classifiers to increase accuracy. You can also send redacted versions of the document and the Match, Not a Match feedback to Microsoft if you want to help increase the accuracy of the classifiers that Microsoft provides. +### Data lifecycle management and records management +- In preview: Retention labels now support running a Power Automate flow at the end of the retention period to support custom actions and integration with other solutions. For more information, see [Customize what happens at the end of the retention period](retention-label-flow.md). +- For records management items undergoing disposition review, when you select that item in the Disposition area of the compliance portal, a new Progress column displays the item's status. That status can be "Approved for deletion, "Awaiting deletion from SharePoint/OneDriveΓÇ¥ or ΓÇ£Awaiting deletion from ExchangeΓÇ¥, or "Permanently Deleted". When an item is approved for permanent deletion as part of the disposition review process, that deletion can take up to 15 days to complete and this new column helps you to track its progress. +- The configuration to [enable a mailbox for archiving](enable-archive-mailboxes.md) is moving to the new Exchange admin center (EAC) and instructions have been updated accordingly. +- Currently, trainable classifiers for auto-apply retention labels aren't supported with adaptive scopes. As a workaround, use static scopes for this configuration combination. +- Instructions to [Customize an archive and deletion policy for mailboxes](set-up-an-archive-and-deletion-policy-for-mailboxes.md) are updated to include only retention tags that that have an outcome that can't be achieved with Microsoft 365 retention. + ### Data loss prevention - [Design a data loss prevention policy complex rule design (preview)](dlp-policy-design.md#complex-rule-design-preview) - The DLP rule builder supports boolean logic (AND, OR, NOT) and nested groups. New video and content added that walks you through this new functionality.- ++### Sensitivity labels +- [PDF support](sensitivity-labels-office-apps.md#pdf-support) in Word, Excel, and PowerPoint is now available to Windows Current Channel and Monthly Enterprise Channel. +- Default label for existing documents is now fully rolled out to Mac and Windows in Current Channel and Monthly Enterprise Channel, providing parity with the AIP add-in. +- In preview: The new [sensitivity bar](sensitivity-labels-office-apps.md#sensitivity-bar) and support for [label colors](sensitivity-labels-office-apps.md#label-colors) in Office apps, providing parity with the AIP add-in with additional functionality. +- In preview: [S/MIME support](sensitivity-labels-office-apps.md#configure-a-label-to-apply-smime-protection-in-outlook) for Windows, providing parity with the AIP add-in. Support for Mac and mobile is now fully rolled out. +- In preview: Trainable classifiers for auto-labeling policies (all workloads). + ### Trainable classifiers - [Trainable classifiers definitions](classifier-tc-definitions.md) - more than 20 new classifiers have been added, so the definitions for all trainable classifiers have been broken out into this new article. + ## August 2022 ### Compliance Manager |
| contentunderstanding | Accessibility Mode | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/accessibility-mode.md | Title: Accessibility mode in Microsoft SharePoint Syntex + Title: Accessibility mode in Microsoft Syntex -description: Learn how to use accessibility features mode when training and working with models in SharePoint Syntex. +description: Learn how to use accessibility features mode when training and working with models in Microsoft Syntex. -# Accessibility mode in Microsoft SharePoint Syntex +# Accessibility mode in Microsoft Syntex -In [SharePoint Syntex](index.md), users can turn on accessibility mode in all stages of model training (label, train, test) when working with example documents. Using accessibility mode can help low-sight users to have easier keyboard accessibility as they navigate and label items in the document viewer. +In [Microsoft Syntex](index.md), users can turn on accessibility mode in all stages of model training (label, train, test) when working with example documents. Using accessibility mode can help low-sight users to have easier keyboard accessibility as they navigate and label items in the document viewer. This helps users to use their keyboards to navigate through text in the document viewer and to hear a narration of not only the selected values, but also of actions (such as labeling or removing labeling from selected text), or predicted label values as you train the model with additional example documents. |
| contentunderstanding | Adoption Assessment Tool | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/adoption-assessment-tool.md | Title: Discover opportunities in SharePoint Syntex by using the Microsoft 365 Assessment tool + Title: Discover opportunities in Microsoft Syntex by using the Microsoft 365 Assessment tool -description: Learn how to use the adoption assessment tool to see how your organization can benefit from SharePoint Syntex. +description: Learn how to use the adoption assessment tool to see how your organization can benefit from Microsoft Syntex. -# Discover opportunities in SharePoint Syntex by using the Microsoft 365 Assessment tool +# Discover opportunities in Microsoft Syntex by using the Microsoft 365 Assessment tool > [!NOTE] > The Microsoft 365 Assessment tool can be run only against SharePoint Online. -You can assess how SharePoint Syntex will benefit your organization by using the Microsoft 365 Assessment tool. When you run an assessment, you'll generate a Power BI report that summarizes aspects of your SharePoint information architecture that are indicators for where SharePoint Syntex might be of value. +You can assess how Microsoft Syntex will benefit your organization by using the Microsoft 365 Assessment tool. When you run an assessment, you'll generate a Power BI report that summarizes aspects of your SharePoint information architecture that are indicators for where Syntex might be of value.  The assessment report includes the following information: -- **Libraries with custom columns** ΓÇô Identify libraries where SharePoint Syntex can automatically populate columns, improving consistency. +- **Libraries with custom columns** ΓÇô Identify libraries where Syntex can automatically populate columns, improving consistency. -- **Column usage** ΓÇô Identify patterns of column usage, to target SharePoint Syntex models where they'll have the maximum benefit. +- **Column usage** ΓÇô Identify patterns of column usage, to target Syntex models where they'll have the maximum benefit. -- **Libraries with custom content types** ΓÇô Identify libraries using custom content types, where SharePoint Syntex models can be used to automatically categorize files. +- **Libraries with custom content types** ΓÇô Identify libraries using custom content types, where Syntex models can be used to automatically categorize files. -- **Content type usage** ΓÇô Identify patterns of content type usage, to target SharePoint Syntex models where they'll have the maximum benefit. +- **Content type usage** ΓÇô Identify patterns of content type usage, to target Syntex models where they'll have the maximum benefit. -- **Libraries with retention labels** ΓÇô Identify libraries where retention labels are used, where SharePoint Syntex can be used to automate and improve consistency. +- **Libraries with retention labels** ΓÇô Identify libraries where retention labels are used, where Syntex can be used to automate and improve consistency. - **Library size** ΓÇô Identify large libraries where classification and metadata can improve the content discovery experience. -- **Library modernization status** ΓÇô Identify libraries that might need to be modernized to fully make use of SharePoint Syntex. +- **Library modernization status** ΓÇô Identify libraries that might need to be modernized to fully make use of Syntex. - **Prebuilt model candidates** ΓÇô Identify libraries where names or content types suggest a prebuilt model could be applied. -- **Syntex model usage** ΓÇô Review the current use of SharePoint Syntex models in your sites. +- **Syntex model usage** ΓÇô Review the current use of Syntex models in your sites. - **Assessment overview** ΓÇô Review the assessment results to identify any failures. ## Run the assessment -The SharePoint Syntex assessment is a module in the Microsoft 365 Assessment tool. To run the assessment: +The Syntex assessment is a module in the Microsoft 365 Assessment tool. To run the assessment: 1. Visit the [Microsoft 365 Assessment tool documentation](https://pnp.github.io/pnpassessment/https://docsupdatetracker.net/index.html) to learn more. The SharePoint Syntex assessment is a module in the Microsoft 365 Assessment too 4. [Configure permissions](https://pnp.github.io/pnpassessment/sharepoint-syntex/requirements.html). -5. [Run a SharePoint Syntex assessment](https://pnp.github.io/pnpassessment/sharepoint-syntex/assess.html). +5. [Run a Syntex assessment](https://pnp.github.io/pnpassessment/sharepoint-syntex/assess.html). |
| contentunderstanding | Adoption Getstarted | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/adoption-getstarted.md | Title: Get started driving adoption of Microsoft SharePoint Syntex -description: Learn how to use and implement SharePoint Syntex in your organization to help you streamline your business processes. + Title: Get started driving adoption of Microsoft Syntex +description: Learn how to use and implement Microsoft Syntex in your organization to help you streamline your business processes. search.appverid: ms.localizationpriority: medium -# Get started driving adoption of Microsoft SharePoint Syntex +# Get started driving adoption of Microsoft Syntex -Think of the intelligent content services available in SharePoint Syntex as having three parts: +Think of the intelligent content services available in Microsoft Syntex as having three parts: - **Content understanding:** Create no-code AI models to classify and extract information from content to automatically apply metadata for knowledge discovery and reuse. Learn more about [content understanding](document-understanding-overview.md). - **Content processing:** Automate capture, ingestion, and categorization of content and streamline content-centric processes using Power Automate. Learn more about [content processing](form-processing-overview.md). - **Content compliance:** Control and manage content to improve security and governance with integration to Microsoft Purview Information Protection. -With new AI services and capabilities, you can build content understanding and classification apps directly into the content management flow using SharePoint Syntex. There are two different ways of understanding your content. The model type you use is based on file format and use case. +With new AI services and capabilities, you can build content understanding and classification apps directly into the content management flow using Syntex. There are two different ways of understanding your content. The model type you use is based on file format and use case. | Form processing | Document understanding | |:-|:-|-| Created from document library. | Created in the content center, part of SharePoint Syntex. | +| Created from document library. | Created in the content center, part of Syntex. | | Model created in AI builder. | Model created in native interface. | | Used for semi-structured file formats. | Used for unstructured file formats. | | Settable classifier. | Trainable classifier with optional extractors. | For a more complete comparison of the capabilities, see [Difference between docu ## Identify pilot business scenarios to optimize -To prepare for using SharePoint Syntex in your organization, you first need to understand the scenarios in which it will be useful. The "why" helps determine what model will be needed, and how to structure your org based on where the model will be applied. Here are a few scenarios where document understanding can help your organization: +To prepare for using Syntex in your organization, you first need to understand the scenarios in which it will be useful. The "why" helps determine what model will be needed, and how to structure your org based on where the model will be applied. Here are a few scenarios where document understanding can help your organization: - **Content processing:** Process contracts, statements of work, and other form-like documents. Intake the forms, train the model to understand and map the fields, and then run your forms through to automatically collect the data. For more information, see [Form processing overview](form-processing-overview.md). - **Invoice analysis:** Pull out the relevant details from your invoices and make sure they're complying with policy or are being processed appropriately. -Think about ways that SharePoint Syntex can help your organization: +Think about ways that Syntex can help your organization: - Automate business processes - Improve search accuracy When thinking about which business scenarios to consider, ask yourself the follo Prioritize scenarios based on impact and ease of implementation. Make your initial focus area higher impact scenarios that can also be easily implemented. De-prioritize lower impact scenarios that are hard to implement. -Use the [example scenarios and use cases](adoption-scenarios.md) to prompt ideas about how you can use SharePoint Syntex in your organization. +Use the [example scenarios and use cases](adoption-scenarios.md) to prompt ideas about how you can use Syntex in your organization. ## Identify roles & responsibilities Where will they build and apply the models? Are there existing processes or repo ## Strategic positioning -Work with stakeholders to make sure they are aligned on the strategy for using SharePoint Syntex. Research and provide the following resources to help with this positioning: +Work with stakeholders to make sure they are aligned on the strategy for using Syntex. Research and provide the following resources to help with this positioning: - Business outcomes: - Potential fiscal outcomes Identify the stakeholders for your project. ## Readiness checklist -To get ready for implementing SharePoint Syntex, you need to: +To get ready for implementing Syntex, you need to:  To get ready for implementing SharePoint Syntex, you need to: ## See also -[Scenarios and use cases for SharePoint Syntex](adoption-scenarios.md) +[Scenarios and use cases for Syntex](adoption-scenarios.md) [Manage contracts using a Microsoft 365 solution](solution-manage-contracts-in-microsoft-365.md) |
| contentunderstanding | Adoption Scenarios | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/adoption-scenarios.md | Title: Scenarios and use cases for Microsoft SharePoint Syntex + Title: Scenarios and use cases for Microsoft Syntex -description: Find business scenarios about how to use SharePoint Syntex in your organization. +description: Find business scenarios about how to use Microsoft Syntex in your organization. -# Scenarios and use cases for Microsoft SharePoint Syntex +# Scenarios and use cases for Microsoft Syntex -Use the following example scenarios to prompt ideas about how you can use SharePoint Syntex in your organization. +Use the following example scenarios to prompt ideas about how you can use Microsoft Syntex in your organization. - [Scenario: Track data from invoices with form processing](adoption-scenarios.md#scenario-track-data-from-invoices-with-form-processing) - [Scenario: Track information from contracts with document understanding](adoption-scenarios.md#scenario-track-information-from-contracts-with-document-understanding)-- [Scenario: Avoid risk with records management, document governance, and compliance processes based on SharePoint Syntex](adoption-scenarios.md#scenario-avoid-risk-with-records-management-document-governance-and-compliance-processes-based-on-sharepoint-syntex)+- [Scenario: Avoid risk with records management, document governance, and compliance processes based on Syntex](adoption-scenarios.md#scenario-avoid-risk-with-records-management-document-governance-and-compliance-processes-based-on-syntex) - [Scenario: Capture information from previously inaccessible documents](adoption-scenarios.md#scenario-capture-information-from-previously-inaccessible-documents) - [Scenario: Improve data processing to provide insights and analytics](adoption-scenarios.md#scenario-improve-data-processing-to-provide-insights-and-analytics) - [Scenario: Automate order processing](adoption-scenarios.md#scenario-automate-order-processing) Use the following example scenarios to prompt ideas about how you can use ShareP ## Scenario: Track data from invoices with form processing -For example, you can set up a process using SharePoint Syntex and Power Automate features to track and monitor invoices. +For example, you can set up a process using Syntex and Power Automate features to track and monitor invoices. 1. Set up a library to store the invoice documents. 1. Train the model to recognize fields in the documents. For example, you can set up a process using SharePoint Syntex and Power Automate - An invoice is past its due date. - An invoice is for an amount that's larger than your automatic approval amount. - + When you automate this scenario, you can: As another example, you can set up a process to identify contracts your company 1. When the model is complete, apply the model to a library where you can upload contracts. 1. Apply a retention label to the date field, so that contracts are retained in the library for the required length of time. - + When you automate this scenario, you can: - Save time and money by automatically extracting data from the contracts instead of doing it manually. - Ensure better compliance by using retention labels to ensure that the contracts are retained appropriately. -## Scenario: Avoid risk with records management, document governance, and compliance processes based on SharePoint Syntex +## Scenario: Avoid risk with records management, document governance, and compliance processes based on Syntex Reducing risks is a common goal for most companies. You might need: Reducing risks is a common goal for most companies. You might need: - To audit receipts, contracts, and so on, to ensure compliance with company policies. - To ensure that projects have all the documentation required for compliance. -Set up some processes for compliance with SharePoint Syntex to capture and appropriately classify, audit, and flag documents and forms that need better governance. You can rely on SharePoint Syntex to auto classify content rather than relying on end users to manually tag, or the compliance team to manually apply governance rules and archiving. And you can enable a simplified search experience, manage data volumes, apply records management and retention policies, ensure compliance, and best practice archiving and purging practices. +Set up some processes for compliance with Syntex to capture and appropriately classify, audit, and flag documents and forms that need better governance. You can rely on Syntex to auto classify content rather than relying on end users to manually tag, or the compliance team to manually apply governance rules and archiving. And you can enable a simplified search experience, manage data volumes, apply records management and retention policies, ensure compliance, and best practice archiving and purging practices. When you automate this scenario, you can feel secure that: When you automate this scenario, you can: ## Scenario: Improve data processing to provide insights and analytics -For example, a pharmaceutical company could use SharePoint Syntex to extract information from FDA documents to answer questions that their leaders have. Having the answers more easily accessible can reduce the time needed to produce these answers and increase the availability of data to generate more accurate answers to leadership questions. +For example, a pharmaceutical company could use Syntex to extract information from FDA documents to answer questions that their leaders have. Having the answers more easily accessible can reduce the time needed to produce these answers and increase the availability of data to generate more accurate answers to leadership questions. For example, a project manager needs to quickly provide answers to product-related questions from my leadership team. They need to find information and metrics related to queries in one consolidated dashboard. TheyΓÇÖre looking for a solution that extracts the information they need from product labels, product pamphlets, and other materials and generates a consolidated report that they can use when reporting back to their leadership team. When you automate this scenario, you can: ## Scenario: Automate order processing -With SharePoint Syntex, you can reduce the time of manual processing of customer orders. For example, you can upload orders from fax, email, or paper into SharePoint by using OCR processing and then extract the metadata from those orders so you can fulfill them by using automated processes. +With Syntex, you can reduce the time of manual processing of customer orders. For example, you can upload orders from fax, email, or paper into SharePoint document library by using OCR processing and then extract the metadata from those orders so you can fulfill them by using automated processes. For example, a supply chain manager wants to reduce errors caused by manual data entry. They want to avoid manual review and data entry of inbound customer orders (paper, fax, or e-mail) to reduce errors going into their business systems. They want a solution that applies AI and machine learning techniques to validate incoming order information, extract core data and automa |