Updates from: 01/10/2023 02:51:46
Category Microsoft Docs article Related commit history on GitHub Change details
admin Buy A Domain Name https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/admin/get-help-with-domains/buy-a-domain-name.md
We offer a free Domain Privacy Subscription with the purchase of a domain. This
If you want to buy a domain from a domain registrar other than [GoDaddy](https://www.godaddy.com), we recommend you use one below that supports automatic setup (Domain Connect). - [1&1 IONOS](https://www.1and1.com/)-- [WordPress](https://www.wordpress.com)
+- [EuroDNS](https://www.eurodns.com/)
+- [Cloudflare](https://www.cloudflare.com/)
+- [WordPress.com](https://wordpress.com/)
+- [Plesk](https://www.plesk.com/)
+- [MediaTemple](https://mediatemple.net/)
+- SecureServer or WildWestDomains (GoDaddy resellers using SecureServer DNS hosting)
+ - Examples:
+ - [DomainsPricedRight](https://www.domainspricedright.com/products/domain-registration)
+ - [DomainRightNow](https://www.domainrightnow.com/)
## Transfer your domain to a different domain registrar
admin Upgrade Distribution Lists https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/admin/manage/upgrade-distribution-lists.md
description: "Learn how to upgrade one or many distribution lists to Microsoft 3
# Upgrade distribution lists to Microsoft 365 Groups in Exchange Online
+> [!IMPORTANT]
+> This functionality will be deprecated by February 1, 2023. For more information, see [Deprecating Conversion of Distribution Lists to Microsoft 365 Groups - Microsoft Community Hub](https://techcommunity.microsoft.com/t5/exchange-team-blog/deprecating-conversion-of-distribution-lists-to-microsoft-365/ba-p/3668215).
+ Upgrading a distribution list to a Microsoft 365 Group is a great way to improve the features and capabilities of groups in your organization. For more information, see [Why you should upgrade your distribution lists to groups in Outlook](https://support.microsoft.com/office/7fb3d880-593b-4909-aafa-950dd50ce188) You can upgrade distribution lists one at a time, or several at the same time. You can use the Exchange admin center (EAC) or Exchange Online PowerShell. + ## Upgrade one or many distribution list groups to Microsoft 365 Groups You must be a global admin or Exchange admin to upgrade a distribution list. To upgrade to Microsoft 365 Groups, the distribution list must have a designated owner, and that owner must be a mailbox.
You must be a global admin or Exchange admin to upgrade a distribution list. To
![Upgrade to Microsoft 365 Groups icon.](../../media/1e28cb3d-bff3-4be3-8329-1902d2d54720.png)
-1. On the information dialog, select **Yes** to confirm the upgrade. The process begins immediately. Depending on the size and number of distribution lits you're upgrading, the process can take minutes or hours.
+1. On the information dialog, select **Yes** to confirm the upgrade. The process begins immediately. Depending on the size and number of distribution lists you're upgrading, the process can take minutes or hours.
If the distribution list can't be upgraded, a dialog appears saying so. See [Which distribution lists cannot be upgraded?](#which-distribution-lists-cant-be-upgraded).
To upgrade a single distribution list, use the following syntax:
Upgrade-DistributionGroup -DLIdentities <EmailAddress> ```
-This example upgrade the distribution list marketing@contoso.com:
+This example upgrades the distribution list marketing@contoso.com:
```PowerShell Upgrade-DistributionGroup -DLIdentities marketing@contoso.com
People with global admin or Exchange admin rights.
### Why is the contact card still showing a distribution list? What should I do to prevent an upgraded distribution list from showing up in my auto suggest list? -- **Outlook**: After you upgrade a ditribution list to a Microsoft 365 group, the user's local recipient cache (also known as the nick name cache) is not aware of the change. Do the steps in the following article to reset the user's local recipient cache: [Information about the Outlook AutoComplete list](/outlook/troubleshoot/contacts/information-about-the-outlook-autocomplete-list).
+- **Outlook**: After you upgrade a distribution list to a Microsoft 365 group, the user's local recipient cache (also known as the nick name cache) is not aware of the change. Do the steps in the following article to reset the user's local recipient cache: [Information about the Outlook AutoComplete list](/outlook/troubleshoot/contacts/information-about-the-outlook-autocomplete-list).
If you don't update the recipient cache, any email sent to the Microsoft 365 Group will be delivered successfully, but the following issues will remain:
admin Secure Your Business Data https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/admin/security-and-compliance/secure-your-business-data.md
description: "Best practices to protect your small or medium sized business from
Microsoft 365 for business plans, such as Microsoft 365 Business Basic, Standard, and Premium, include security capabilities, such as antiphishing, antispam, and antimalware protection. Microsoft 365 Business Premium includes even more capabilities, such as device security, advanced threat protection, and information protection. This article describes how to secure your data with Microsoft 365 for business. This article also includes information to [compare capabilities across Microsoft 365 for business plans](#comparing-microsoft-365-for-business-plans). - | Step | Task | Description | |:--:|:|:| | 1 | **[Use multi-factor authentication](multi-factor-authentication-microsoft-365.md)**. | [Multi-factor authentication](multi-factor-authentication-microsoft-365.md) (MFA), also known as two-step verification, requires people to use a code or authentication app on their phone to sign into Microsoft 365, and is a critical first step to protecting your business data. Using MFA can prevent hackers from taking over if they know your password.<br/><br/>See [security defaults and MFA](../../business-premium/m365bp-conditional-access.md). |
bookings Bookings Sms https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/bookings/bookings-sms.md
With Microsoft Bookings, you can set up SMS text notifications to be sent to the
The SMS notifications will include the Teams meeting link for virtual booking appointments.
-> [!Note]
-> We'll be providing unlimited SMS notifications through January 31, 2023 (previously November 30th 2022) for customers with Bookings licenses. As we get closer to the end of the promotion period, we'll provide additional details on licensing requirements. Contact your account team or support to receive pricing details after the promotion period.
+> [!NOTE]
+> We'll be providing unlimited SMS notifications through March 1, 2023 (previously January 31, 2023) for customers with Bookings licenses. As we get closer to the end of the promotion period, we'll provide additional details on licensing requirements. Contact your account team or support to receive pricing details after the promotion period.
## Before you begin
You can configure SMS notification in Bookings in a couple of ways:
> [!NOTE] > You need to be a Teams admin to see Teams and Bookings data on the Teams admin center.
-You can track key data on SMS notifications usage in your organization in the Teams admin center. Usage reports include data such as time and date sent, origin number, message type, event type and delivery status. You can use SMS notification telemetry during the promotional period to help forecast and budget for SMS notifications after January 31, 2023.
+You can track key data on SMS notifications usage in your organization in the Teams admin center. Usage reports include data such as time and date sent, origin number, message type, event type and delivery status. You can use SMS notification telemetry during the promotional period to help forecast and budget for SMS notifications after March 1, 2023.
-1. On the Teams admin center, **Virtual Visits SMS notifications**.
+1. On the Teams admin center, go to **SMS notifications usage**.
-2. On the **Analytics & Reports** page, select SMS notifications usage.
+2. On **Analytics & Reports** > **Usage reports**, select SMS notifications usage.
:::image type="content" source="../media/analytics-reporting.png" alt-text="Screenshot: SMS text notifications Analytics and reporting page in the Teams admin center":::
commerce Manage Billing Notifications https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/commerce/billing-and-payments/manage-billing-notifications.md
f1.keywords:
-+ audience: Admin
compliance Ediscovery Create Reports And Delete Multiple Content Searches https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/ediscovery-create-reports-and-delete-multiple-content-searches.md
+
+ Title: "Create, report on, and delete Content Searches"
+description: "Learn how to automate Content Search tasks like creating searches and running reports using Security & Compliance PowerShell."
+f1.keywords:
+- NOCSH
+++
+audience: Admin
+++
+- tier1
+- purview-compliance
+- ediscovery
+ms.localizationpriority: medium
+search.appverid:
+- SPO160
+- MOE150
+- MET150
+++
+# Create, report on, and delete multiple Content Searches
+
+ Quickly creating and reporting discovery searches is often an important step in eDiscovery and investigations when you're trying to learn about the underlying data, and the richness and quality of your searches. To help you do this, Security & Compliance PowerShell offers a set of cmdlets to automate time-consuming Content Search tasks. These scripts provide a quick and easy way to create a number of searches, and then run reports of the estimated search results that can help you determine the quantity of data in question. You can also use the scripts to create different versions of searches to compare the results each one produces. These scripts can help you to quickly and efficiently identify and cull your data.
++
+## Before you create a Content Search
+
+- You have to be a member of the eDiscovery Manager role group in the Microsoft Purview compliance portal to run the scripts that are described in this topic.
+- To collect a list of the URLs for the OneDrive for Business sites in your organization that you can add to the CSV file in Step 1, see [Create a list of all OneDrive locations in your organization](/onedrive/list-onedrive-urls).
+- Be sure to save all the files that you create in this topic to the same folder. That will make it easier to run the scripts.
+- The scripts include minimal error handling. Their primary purpose is to quickly create, report on, and delete multiple Content Searches.
+- The sample scripts provided in this topic aren't supported under any Microsoft standard support program or service. The sample scripts are 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 scripts 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.
+
+## Step 1: Create a CSV file that contains information about the searches you want to run
+
+The comma separated value (CSV) file that you create in this step contains a row for each user that want to search. You can search the user's Exchange Online mailbox (which includes the archive mailbox, if it's enabled) and their OneDrive for Business site. Or you can search just the mailbox or the OneDrive for Business site. You can also search any site in your SharePoint Online organization. The script that you run in Step 3 will create a separate search for each row in the CSV file.
+
+1. Copy and paste the following text into a .txt file using NotePad. Save this file to a folder on your local computer. You'll save the other scripts to this folder as well.
+
+ ```text
+ ExchangeLocation,SharePointLocation,ContentMatchQuery,StartDate,EndDate
+ sarad@contoso.onmicrosoft.com,https://contoso-my.sharepoint.com/personal/sarad_contoso_onmicrosoft_com,(lawsuit OR legal),1/1/2000,12/31/2005
+ sarad@contoso.onmicrosoft.com,https://contoso-my.sharepoint.com/personal/sarad_contoso_onmicrosoft_com,(lawsuit OR legal),1/1/2006,12/31/2010
+ sarad@contoso.onmicrosoft.com,https://contoso-my.sharepoint.com/personal/sarad_contoso_onmicrosoft_com,(lawsuit OR legal),1/1/2011,3/21/2016
+ ,https://contoso.sharepoint.com/sites/contoso,,,3/21/2016
+ ,https://contoso-my.sharepoint.com/personal/davidl_contoso_onmicrosoft_com,,1/1/2015,
+ ,https://contoso-my.sharepoint.com/personal/janets_contoso_onmicrosoft_com,,1/1/2015,
+ ```
+
+ The first row, or header row, of the file lists the parameters that will be used by **New-ComplianceSearch** cmdlet (in the script in Step 3) to create a new Content Searches. Each parameter name is separated by a comma. Make sure there aren't any spaces in the header row. Each row under the header row represents the parameter values for each search. Be sure to replace the placeholder data in the CSV file with your actual data.
+
+2. Open the .txt file in Excel, and then use the information in the following table to edit the file with information for each search.
+
+ ****
+
+ |Parameter|Description|
+ |||
+ |`ExchangeLocation`|The SMTP address of the user's mailbox.|
+ |`SharePointLocation`|The URL for the user's OneDrive for Business site or the URL for any site in your organization. For the URL for OneDrive for Business sites, use this format: ` https://<your organization>-my.sharepoint.com/personal/<user alias>_<your organization>_onmicrosoft_com `. For example, `https://contoso-my.sharepoint.com/personal/sarad_contoso_onmicrosoft_com`.|
+ |`ContentMatchQuery`|The search query for the search. For more information about creating a search query, see [Keyword queries and search conditions for Content Search](ediscovery-keyword-queries-and-search-conditions.md).|
+ |`StartDate`|For email, the date on or after a message was received by a recipient or sent by the sender. For documents on SharePoint or OneDrive for Business sites, the date on or after a document was last modified.|
+ |`EndDate`|For email, the date on or before a message was sent by a sent by the user. For documents on SharePoint or OneDrive for Business sites, the date on or before a document was last modified.|
+ |
+
+3. Save the Excel file as a CSV file to a folder on your local computer. The script that you create in Step 3 will use the information in this CSV file to create the searches.
+
+## Step 2: Connect to Security & Compliance PowerShell
+
+The next step is to connect to Security & Compliance PowerShell for your organization. For step-by-step instructions, see [Connect to Security & Compliance PowerShell](/powershell/exchange/connect-to-scc-powershell).
+
+## Step 3: Run the script to create and start the searches
+
+The script in this step will create a separate Content Search for each row in the CSV file that you created in Step 1. When you run this script, you'll be prompted for two values:
+
+- **Search Group ID** - This name provides an easy way to organize the searches that are created from the CSV file. Each search that's created is named with the Search Group ID, and then a number is appended to the search name. For example, if you enter **ContosoCase** for the Search Group ID, then the searches are named **ContosoCase_1**, **ContosoCase_2**, **ContosoCase_3**, and so on. Note that the name you type is case sensitive. When you use the Search Group ID in Step 4 and Step 5, you have to use the same case as you did when you created it.
+
+- **CSV file** - The name of the CSV file that you created in Step 1. Be sure to include the use the full filename, include the .csv file extension; for example, `ContosoCase.csv`.
+
+To run the script:
+
+1. Save the following text to a Windows PowerShell script file by using a filename suffix of .ps1; for example, `CreateSearches.ps1`. Save the file to the same folder where you saved the other files.
+
+ ```Powershell
+ # Get the Search Group ID and the location of the CSV input file
+ $searchGroup = Read-Host 'Search Group ID'
+ $csvFile = Read-Host 'Source CSV file'
+
+ # Do a quick check to make sure our group name will not collide with other searches
+ $searchCounter = 1
+ import-csv $csvFile |
+ ForEach-Object{
+
+ $searchName = $searchGroup +'_' + $searchCounter
+ $search = Get-ComplianceSearch $searchName -EA SilentlyContinue
+ if ($search)
+ {
+ Write-Error "The Search Group ID conflicts with existing searches. Please choose a search group name and restart the script."
+ return
+ }
+ $searchCounter++
+ }
+
+ $searchCounter = 1
+ import-csv $csvFile |
+ ForEach-Object{
+
+ # Create the query
+ $query = $_.ContentMatchQuery
+ if(($_.StartDate -or $_.EndDate))
+ {
+ # Add the appropriate date restrictions. NOTE: Using the Date condition property here because it works across Exchange, SharePoint, and OneDrive for Business.
+ # For Exchange, the Date condition property maps to the Sent and Received dates; for SharePoint and OneDrive for Business, it maps to Created and Modified dates.
+ if($query)
+ {
+ $query += " AND"
+ }
+ $query += " ("
+ if($_.StartDate)
+ {
+ $query += "Date >= " + $_.StartDate
+ }
+ if($_.EndDate)
+ {
+ if($_.StartDate)
+ {
+ $query += " AND "
+ }
+ $query += "Date <= " + $_.EndDate
+ }
+ $query += ")"
+ }
+
+ # -ExchangeLocation can't be set to an empty string, set to null if there's no location.
+ $exchangeLocation = $null
+ if ( $_.ExchangeLocation)
+ {
+ $exchangeLocation = $_.ExchangeLocation
+ }
+
+ # Create and run the search
+ $searchName = $searchGroup +'_' + $searchCounter
+ Write-Host "Creating and running search: " $searchName -NoNewline
+ $search = New-ComplianceSearch -Name $searchName -ExchangeLocation $exchangeLocation -SharePointLocation $_.SharePointLocation -ContentMatchQuery $query
+
+ # Start and wait for each search to complete
+ Start-ComplianceSearch $search.Name
+ while ((Get-ComplianceSearch $search.Name).Status -ne "Completed")
+ {
+ Write-Host " ." -NoNewline
+ Start-Sleep -s 3
+ }
+ Write-Host ""
+
+ $searchCounter++
+ }
+ ```
+
+2. In Windows PowerShell, go to the folder where you saved the script in the previous step, and then run the script; for example:
+
+ ```Powershell
+ .\CreateSearches.ps1
+ ```
+
+3. At the **Search Group ID** prompt, type a search group name, and then press **Enter**; for example, `ContosoCase`. Remember that this name is case sensitive, so you'll have to type it the same way in the subsequent steps.
+
+4. At the **Source CSV file** prompt, type the name of the CSV file, including the .csv file extension; for example, `ContosoCase.csv`.
+
+5. Press **Enter** to continue running the script.
+
+ The script displays the progress of creating and running the searches. When the script is complete, it returns to the prompt.
+
+ ![Sample output from running the script to create multiple compliance searches.](../media/37d59b0d-5f89-4dbc-9e2d-0e88e2ed7b4c.png)
+
+## Step 4: Run the script to report the search estimates
+
+After you create the searches, the next step is to run a script that displays a simple report of the number of search hits for each search that was created in Step 3. The report also includes the size of results for each search, and the total number of hits and total size of all searches. When you run the reporting script, you'll be prompted for the Search Group ID, and a CSV filename if you want to save the report to a CSV file.
+
+1. Save the following text to a Windows PowerShell script file by using a filename suffix of .ps1; for example, `SearchReport.ps1`. Save the file to the same folder where you saved the other files.
+
+ ```Powershell
+ $searchGroup = Read-Host 'Search Group ID'
+ $outputFile = Read-Host 'Enter a file name or file path to save the report to a .csv file. Leave blank to only display the report'
+ $searches = Get-ComplianceSearch | ?{$_.Name -clike $searchGroup + "_*"}
+ $allSearchStats = @()
+ foreach ($partialObj in $searches)
+ {
+ $search = Get-ComplianceSearch $partialObj.Name
+ $sizeMB = [System.Math]::Round($search.Size / 1MB, 2)
+ $searchStatus = $search.Status
+ if($search.Errors)
+ {
+ $searchStatus = "Failed"
+ }elseif($search.NumFailedSources -gt 0)
+ {
+ $searchStatus = "Failed Sources"
+ }
+ $searchStats = New-Object PSObject
+ Add-Member -InputObject $searchStats -MemberType NoteProperty -Name Name -Value $search.Name
+ Add-Member -InputObject $searchStats -MemberType NoteProperty -Name ContentMatchQuery -Value $search.ContentMatchQuery
+ Add-Member -InputObject $searchStats -MemberType NoteProperty -Name Status -Value $searchStatus
+ Add-Member -InputObject $searchStats -MemberType NoteProperty -Name Items -Value $search.Items
+ Add-Member -InputObject $searchStats -MemberType NoteProperty -Name "Size" -Value $search.Size
+ Add-Member -InputObject $searchStats -MemberType NoteProperty -Name "Size(MB)" -Value $sizeMB
+ $allSearchStats += $searchStats
+ }
+ # Calculate the totals
+ $allItems = ($allSearchStats | Measure-Object Items -Sum).Sum
+ # Convert the total size to MB and round to the nearst 100th
+ $allSize = ($allSearchStats | Measure-Object 'Size' -Sum).Sum
+ $allSizeMB = [System.Math]::Round($allSize / 1MB, 2)
+ # Get the total successful searches and total of all searches
+ $allSuccessCount = ($allSearchStats |?{$_.Status -eq "Completed"}).Count
+ $allCount = $allSearchStats.Count
+ $allStatus = [string]$allSuccessCount + " of " + [string]$allCount
+ # Totals Row
+ $totalSearchStats = New-Object PSObject
+ Add-Member -InputObject $totalSearchStats -MemberType NoteProperty -Name Name -Value "Total"
+ Add-Member -InputObject $totalSearchStats -MemberType NoteProperty -Name Status -Value $allStatus
+ Add-Member -InputObject $totalSearchStats -MemberType NoteProperty -Name Items -Value $allItems
+ Add-Member -InputObject $totalSearchStats -MemberType NoteProperty -Name "Size(MB)" -Value $allSizeMB
+ $allSearchStats += $totalSearchStats
+ # Just get the columns we're interested in showing
+ $allSearchStatsPrime = $allSearchStats | Select-Object Name, Status, Items, "Size(MB)", ContentMatchQuery
+ # Print the results to the screen
+ $allSearchStatsPrime |ft -AutoSize -Wrap
+ # Save the results to a CSV file
+ if ($outputFile)
+ {
+ $allSearchStatsPrime | Export-Csv -Path $outputFile -NoTypeInformation
+ }
+ ```
+
+2. In Windows PowerShell, go to the folder where you saved the script in the previous step, and then run the script; for example:
+
+ ```Powershell
+ .\SearchReport.ps1
+ ```
+
+3. At the **Search Group ID** prompt, type a search group name, and then press **Enter**; for example `ContosoCase`. Remember that this name is case sensitive, so you'll have to type it the same way you did when you ran the script in Step 3.
+
+4. At the **File path to save the report to a CSV file (leave blank to just display the report)** prompt, type a file name of complete filename path (including the .csv file extension) if you want to save the report to a CSV file. name of the CSV file, including the .csv file extension. For example, you could type `ContosoCaseReport.csv` to save it to the current directory or you could type `C:\Users\admin\OneDrive for Business\ContosoCase\ContosoCaseReport.csv` to save it to a different folder. You can also leave the prompt blank to display the report but not save it to a file.
+
+5. Press **Enter**.
+
+ The script displays the progress of creating and running the searches. When the script is complete, the report is displayed.
+
+ ![Run the search report to display the estimates for the search group.](../media/3b5f2595-71d5-4a14-9214-fad156c981f8.png)
+
+> [!NOTE]
+> If the same mailbox or site is specified as a content location in more than one search in a search group, the total results estimate in the report (for both the number of items and the total size) might include results for the same items. That's because the same email message or document will be counted more than once if it matches the query for different searches in the search group.
+
+## Step 5: Run the script to delete the searches
+
+Because you might be creating a lot of searches, this last script just makes it easy to quickly delete the searches you created in Step 3. Like the other scripts, this one also prompts you for the Search Group ID. All searches with the Search Group ID in the search name will be deleted when you run this script.
+
+1. Save the following text to a Windows PowerShell script file by using a filename suffix of .ps1; for example, `DeleteSearches.ps1`. Save the file to the same folder where you saved the other files.
+
+ ```Powershell
+ # Delete all searches in a search group
+ $searchGroup = Read-Host 'Search Group ID'
+ Get-ComplianceSearch |
+ ForEach-Object{
+ # If the name matches the search group name pattern (case sensitive), delete the search
+ if ($_.Name -cmatch $searchGroup + "_\d+")
+ {
+ Write-Host "Deleting search: " $_.Name
+ Remove-ComplianceSearch $_.Name -Confirm:$false
+ }
+ }
+ ```
+
+2. In Windows PowerShell, go to the folder where you saved the script in the previous step, and then run the script; for example:
+
+ ```Powershell
+ .\DeleteSearches.ps1
+ ```
+
+3. At the **Search Group ID** prompt, type a search group name for the searches that you want to delete, and then press **Enter**; for example, `ContosoCase`. Remember that this name is case sensitive, so you'll have to type it the same way you did when you ran the script in Step 3.
+
+ The script displays the name of each search that's deleted.
+
+ ![Run the script to delete the searches in the search group.](../media/9d97b9d6-a539-4d9b-a4e4-e99989144ec7.png)
compliance Ediscovery Teams Workflow https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/ediscovery-teams-workflow.md
+
+ Title: "Teams workflow in eDiscovery (Premium)"
+description: "Learn how to preserve, collect, review, and export content from Microsoft Teams in eDiscovery (Premium)."
+f1.keywords:
+- NOCSH
++++
+audience: Admin
++
+ms.localizationpriority: medium
+search.appverid:
+- MET150
+
+- highpri
+- tier1
+- purview-compliance
++
+# eDiscovery (Premium) workflow for content in Microsoft Teams
+
+This article provides a comprehensive set of procedures, guidelines, and best practices for using Microsoft Purview eDiscovery (Premium) to preserve, collect, review, and export content from Microsoft Teams. The goal of this article is to help you optimize your eDiscovery workflow for Teams content.
+
+There are six categories of Teams content that you can collect and process using eDiscovery (Premium):
+
+- **Teams 1:1 chats**. Chat messages, posts, and attachments shared in a Teams conversation between two people. Teams 1:1 chats are also called *conversations*.
+
+- **Teams group chats**. Chat messages, posts, and attachments shared in a Teams conversation between three or more people. Also called *1:N* chats or *group conversations*.
+
+- **Teams reactions**. Reactions applied to chat messages, posts, and attachments in a Teams conversation.
+
+- **Teams channels**. Chat messages, posts, replies, and attachments shared in a standard Teams channel.
+
+- **Private channels**. Message posts, replies, and attachments shared in a private Teams channel.
+
+- **Shared channels**. Message posts, replies, and attachments shared in a shared Teams channel.
++
+## Where Teams content is stored
+
+A prerequisite to managing Teams content in eDiscovery (Premium) is to understand the type of Teams content that you can collect, process, and review in eDiscovery (Premium) and where that content is stored in Microsoft 365.
+
+Teams data is stored in Azure Cosmos DB. Teams compliance records captured by the substrate are in Exchange Online and are available for ediscovery.
+
+The following table lists Teams content type and where each is stored for complaince purpose. The data stored in Exchange online is hidden from clients. eDiscovery never operates against the real Teams message data, which remains in Azure Cosmos DB.
+
+|&nbsp;|Location of chat messages and posts|Location of files and attachments|
+||||
+|Teams 1:1 chats|Messages in 1:1 chats are stored in the Exchange Online mailbox of all chat participants.|Files shared in a 1:1 chat are stored in the OneDrive for Business account of the person who shared the file.|
+|Teams group chats|Messages in group chats are stored in the Exchange Online mailbox of all chat participants.|Files shared in group chats are stored in the OneDrive for Business account of the person who shared the file.|
+|Teams reactions|Messages in group chats are stored in the Exchange Online mailbox of all chat participants.|Files shared in group chats are stored in the OneDrive for Business account of the person who shared the file.|
+|Teams channels|All channel messages and posts are stored in the Exchange Online mailbox associated with the team.|Files shared in a channel are stored in the SharePoint Online site associated with the team.|
+|Private channels|Messages sent in a private channel are stored in the Exchange Online mailboxes of all members of the private channel.|Files shared in a private channel are stored in a dedicated SharePoint Online site associated with the private channel.|
+|Shared channels|Messages sent in a shared channel are stored in a system mailbox associated with the shared channel.<sup>1</sup>|Files shared in a shared channel are stored in a dedicated SharePoint Online site associated with the shared channel.|
+
+> [!NOTE]
+> <sup>1</sup> To search for (and preserve) messages sent in a shared channel, you have to search or specify the Exchange Online mailbox for the parent Team.
+
+## Create a case for Teams content
+
+The first step to managing Teams content in eDiscovery (Premium) is to create a case using the new case format that's optimized for managing Teams content. Here's the benefits of using the new case format for Teams content:
+
+- Support for conversation threading, in which additional messages in the same conversation that include responsive items are automatically collected and added to review sets.
+
+- Teams chat conversations are automatically added to review sets as an HTML transcript file. Cloud attachments that are shared in conversations are also added to the review set. This helps provides context to the conversations with responsive items and reduce total number of items produced by chat-based content.
+
+- Collections up to 1 TB can be added to review sets, which let you collect and amounts large amounts of Teams content in a case.
+
+For more information about the increased case limits, see [Use the new case format in eDiscovery (Premium)](ediscovery-new-case-format.md).
+
+To create a case:
+
+1. Go to <https://compliance.microsoft.com> and sign in.
+
+2. In the left navigation pane of the Microsoft Purview compliance portal, click **eDiscovery > Premium**.
+
+3. On the **eDiscovery (Premium)** page, click the **Cases** tab, and then click **Create a case**.
+
+ The **New eDiscovery case** flyout page is displayed. The **Case format** section provides the option to create a case using the new case format.
+
+ ![Large case option on the New eDiscovery case page.](..\media\AeDNewCaseFormat1.png)
+
+4. After naming the case, select the **New** option, and then click **Save** to create the case.
+
+## Add Teams custodial data sources and preserve Teams content
+
+The next step is to identify the users who are the data custodians in your investigation and add them and their content locations as custodians to the case you created in the previous section. When you add custodians, you can specify their mailbox and OneDrive account as custodial data sources. You can also specify Teams content locations as custodian data sources to quickly place these locations on legal hold to preserve content during your investigation. It also makes it easy to collect content and add it to a review set.
+
+To add custodians to a case and preserve custodial data sources:
+
+1. Go to the eDiscovery (Premium) case that you created in the previous section, and then click **Data sources**.
+
+2. On the **Data sources** page, click **Add data source** > **Add new custodians**.
+
+3. In the **New custodian** wizard, add one or more users as custodians to the case by typing the first part of the user's name or alias. After you find the correct person, select their name to add them to the list.
+
+4. Expand each custodian to view the primary data sources that have been automatically associated to the custodian, and to select other locations to associate to the custodian.
+
+ ![Custodian data sources.](..\media\TeamsCustodialDataLocations1.png)
+
+5. Follow these guidelines to add custodial data sources for Teams content. Click **Edit** to add a data location.
+
+ - **Mailboxes**. The custodian's mailbox is selected by default. Keep this selected to add (and preserve) 1:1 chats, group chats, and private channel chats as custodial data.
+
+ - **OneDrives**. The custodian's OneDrive account is selected by default. Keep this selected to add (and preserve) files shared in 1:1 chats and group chats as custodial data.
+
+ - **SharePoint**. Add the SharePoint site associated with any private or shared channel the custodian is a member of to add (and preserve) as custodial data the files shared in a channel. Click **Edit** and then add the URL for the SharePoint site associated with a private or shared channel. To learn how to locate the private and shared channels a user is a member of, see [eDiscovery of private and shared channels](/microsoftteams/ediscovery-investigation#ediscovery-of-private-and-shared-channels).
+
+ - **Teams**. Add the teams that the custodian is a member of to add (and preserve) as custodial data all channel messages and all files shared to a Teams channel. This includes adding the mailbox for the parent team of a shared channel the custodian is a member of. When you click **Edit**, the mailbox and site associated with each team the custodian is a member of are displayed in a list. Select the teams that you want to associate to the custodian. You have to select both the corresponding mailbox and site for each team.
+
+ > [!NOTE]
+ > You can also add the mailbox and site of Teams that custodians aren't members of as a custodian data location. You do this by clicking **Edit** next to **Exchange** and **SharePoint** and then adding the mailbox and site associated with the team.
+
+6. After you add custodians and configure the custodial data sources, click **Next** to display the **Hold settings** page.
+
+ A list of the custodians is displayed and the checkbox in the **Hold** column is selected by default. This indicated that a hold will be placed on the data sources that you associated with each custodian. Leave these checkboxes selected to preserve this data.
+
+7. On the **Hold settings** page, click **Next** to review the custodians settings. Click **Submit** to add the custodians to the case.
+
+For more information about adding and preserving data sources in an eDiscovery (Premium) case, see:
+
+- [Add custodians to an eDiscovery (Premium) case](ediscovery-add-custodians-to-case.md)
+
+- [Add non-custodial data sources to an eDiscovery (Premium) case](ediscovery-non-custodial-data-sources.md)
+
+## Collect Teams content and add to review set
+
+After adding custodians to the case and preserving content in custodian data sources, the next step in the workflow is to search for Teams content that's relevant to your investigation and add it to a review set for further review and analysis. Though it's typical to collect Teams content together with content from other Microsoft 365 services such as email in Exchange and documents in SharePoint, this section will specifically focus on collecting Teams content in a collection. You can create additional collections that collect non-Teams content to add to a review set.
+
+When you collect Teams content for a case, there are two steps in the workflow:
+
+1. **Create a collection estimate**. The first step is to create a *collection estimate*, which is an estimate of the items that match your search criteria. You can view information about the results that matched the search query, such as the total number and size of items found, the different data sources where they were found, and statistics about the search query. You can also preview a sample of items that were returned by the collection. Using these statistics, you can change the search query and rerun the collection estimate as many times as is necessary to narrow the results until you're satisfied you're collecting the content relevant to your case.
+
+2. **Commit a collection estimate to a review set**. Once you're satisfied with the results of a collection estimate, you can commit the collection to a review set. When you commit a collection estimate, the items returned by the collection are added to a review set for review, analysis, and export.
+
+You also have the option of not running a collection estimate and adding the collection results directly to a review set when you create and run the collection.
+
+To create a collection of Teams content:
+
+1. Go to the eDiscovery (Premium) case that you added the custodians to in the previous section, and then click **Collections**.
+
+2. On the **Collections** page, select **New collection** > **Standard collection**.
+
+3. Type a name (required) and description (optional) for the collection.
+
+4. On the **Custodial data sources** page, click **Select custodians** to select the custodians that you added to the case.
+
+ The list of the case custodians is displayed on the **Select custodians** flyout page.
+
+5. Select one or more custodians and then click **Add**.
+
+ After you add specific custodians to the collection, a list of specific data sources for each custodian is displayed. These are the data sources that you configured when you added the custodian to the case. All custodian data sources are selected by default. This includes any Teams or channels that you associated with a custodian.
+
+ We recommend doing the following things when collecting Teams content:
+
+ - Remove custodians' OneDrive accounts from the collection scope (by unselecting the checkbox in the **Custodian's OneDrive** column for each custodian). This prevents the collection of duplicate files that were attached to 1:1 chats and group chats. Cloud attachments are automatically collected from each conversation found in the collection when you commit the collection estimate to the review set. By using this method (instead of searching OneDrive accounts as part of the collection), files attached to 1:1 and group chats are grouped in the conversation they were shared in.
+
+ - Unselect the checkbox in the **Additional site** column to remove the SharePoint sites containing files shared in private or shared channels. Doing this eliminates collecting duplicate files that were attached to private or shared channel conversations because these cloud attachments are automatically added to the review set when you commit the collection estimate and grouped in the conversations they were shared in.
+
+6. If you previously followed the steps to add Teams content as custodian data sources, you can skip this step and select **Next**. Otherwise, on the **Non-custodial data sources** wizard page, you can choose non-custodial data sources that contain Teams content that you may have added to the case to search in the collection.
+
+7. If you previously followed the steps to add Teams content as custodian data sources, you can skip this step and select **Next**. Otherwise, on the **Additional locations** wizard page, you can add other data sources to search in the collection. For example, you could add the mailbox and site for a team that wasn't added as a custodial or non-custodial data source. Otherwise, select **Next** and skip this step.
+
+8. On the **Conditions** wizard page, configure the search query to collect Teams content from the data sources that you specified on the previous wizard pages. You can use various keywords and search conditions to narrow the scope of the collection. For more information, see [Build search queries for collections](ediscovery-building-search-queries.md).
+
+ To help ensure the most comprehensive collection of Teams chat conversations (including 1:1, group, and channel chats) use the **Type** condition and select the **Instant messages** option. We also recommend including a date range or several keywords to narrow the scope of the collection to items relevant to your investigation. Here's a screenshot of a sample query using the **Type** and **Date** options:
+
+ ![Query to collect Teams content.](..\media\TeamsConditionsQueryType.png)
+
+9. On the **Save draft or collect** wizard page, do one of the following depending on whether you want to create a collection estimate or commit the collection to a review set.
+
+ ![Save collection estimate or commit collection.](..\media\TeamsDraftCommitCollection.png)
+
+ 1. **Save collection as draft**. Choose this option to create a collection estimate. As previously explained, a collection estimate doesn't add the collection results to a review set. It returns an estimate of the search results that match the search query for the data sources in the collection scope. This gives you the opportunity to view [collection statistics and reports[(ediscovery-collection-statistics-reports.md)] and edit and rerun the collection estimate. When you satisfied with the result of a collection estimate, you can commit it to a review set. For more information, see [Create a collection estimate](ediscovery-create-draft-collection.md).
+
+ 2. **Collect items and add to a review set**. Choose this option to run the collection and then add the results to a review set. You can add the collection to a new or existing review set. The options to collect contextual Teams conversation messages (also called *conversation threading*) and collect cloud attachments are selected by default and can't be unselected. These options are automatically applied because of the new case format that you used when you initially created the case for Teams content. For more information about committing collections to a review set, see [Commit a collection estimate to a review set](ediscovery-commit-draft-collection.md).
+
+10. After you're finished configuring the collection, submit the collection to create a collection estimate or collect items and add them to a review set.
+
+ When the process of adding the collection to the review set is completed, the status value for the collection on the **Collections** tab is set to **Committed**.
+
+## Review Teams content in a review set
+
+After you add collections of Teams content to a review set, the next step is to review the content for its relevance to your investigation and cull it if necessary. An important prerequisite to reviewing Teams content is understanding how eDiscovery (Premium) processes Teams chat conversations and attachments when adding them to a review set. This processing of Teams content results in the following three things:
+
+- **[Grouping](#grouping)**. How messages, posts, and replies Teams conversations are grouped together and presented in the review set. This also includes attachments in chat conversations are extracted and group within the conversation.
+
+- **[Transcript conversation threading](#transcript-conversation-threading)**. How eDiscovery (Premium) determines what additional content from a conversation to collect to provide context around items that matched the collection criteria.
+
+- **[Deduplication](#deduplication-of-teams-content)**. How eDiscovery (Premium) handles duplicate Teams content.
+
+- **[Metadata](#metadata-for-teams-content)**. Metadata properties that eDiscovery (Premium) adds to Teams content after it's collected and added to a review set.
+
+Understand grouping, conversation threading, deduplication, and Teams metadata will help you optimize the review and analysis of Teams content. This section also has [tips for viewing Teams content in a review set](#tips-for-viewing-teams-content-in-a-review-set).
+
+### Grouping
+
+When content from Teams chat conversations is added to a review set, messages, posts, and replies from conversations are aggregated in HTML transcript files. A single chat conversation can have multiple transcript files. An important function of these transcript files is to present Teams content as continuous conversations and not as individual (or separate) messages. This helps provides context for items that matched the search criteria of your collections in the previous step and reduce the number of items collected into the review set. Transcripts and associated items can be grouped by either *family* or *conversation*. Items in the same family will have the same value for the **FamilyId** metadata property. Items in the same conversation will have the same value for the **ConversationId** metadata property.
+
+The following table describes how the different types of Teams chat content are grouped by family and conversation.
+
+|Teams content type|Group by family|Group by conversation|
+||||
+|Teams 1:1 and group chats|A transcript and all of its attachments and extracted items share the same **FamilyId**. Each transcript has a unique **FamilyId**.|All transcript files and their family items within the same conversation share the same **ConversationId**. This includes the following items: <ul><li>All extracted items and attachments of all transcripts that share the same **ConversationId**.</li><li>All transcripts for the same chat conversation</li><li>All custodian copies of each transcript</li><li>Transcripts from subsequent collections from the same chat conversation</li></ul> <br/> For Teams 1:1 and group chat conversations, you might have multiple transcript files, each one corresponding to a different time frame within the conversation. Because these transcript files are from the same conversation with the same participants, they share the same **ConversationId**.|
+|Standard, private, and shared channel chats|Each post and all replies and attachments are saved to its own transcript. This transcript and all of its attachments and extracted items share the same **FamilyId**.|Each post and its attachments and extracted items have a unique **ConversationId**. If there are subsequent collections or new replies from the same post, the delta transcripts resulting from those collections will also have the same **ConversationId**.|
+
+Use the **Group** control in the command bar of a review set to view Teams content grouped by family or conversation.
+
+![Group control in command bar.](..\media\TeamsGroupControl.png)
+
+- Select **Group family attachments** to view Teams content grouped by family. Each transcript file is displayed on a line in the list of review set items. Attachments are nested under the item.
+
+- Select **Group Teams or Yammer conversations** to view Teams content grouped by conversation. Each conversation is displayed on a line in the list of review set items. Transcript files and attachments are nested under the top-level conversation.
+
+> [!NOTE]
+> Cloud attachments are grouped with the conversations they appear in. This grouping is accomplished by assigning the same **FamilyId** as the transcript file of the message the file was attached to and the same **ConversationId** as the conversation the message appeared in. This means multiple copies of cloud attachments may be added to the review set if they were attached to different conversations.
+
+#### Viewing transcript files for conversations
+
+When viewing transcript files in a review set, some of the messages are highlighted in purple. The messages that are highlighted depend on which custodian copy of the transcript you're viewing. For example, in a 1:1 chat between User4 and User2, the messages posted by User4 are highlighted in purple when you view the transcript collected from User4's mailbox. When you view User2's transcript of the same conversation, messages posted by User2 are highlighted in purple. This highlighting behavior is based on the same Teams client experience, where a user's posts are highlighted in purple in the Teams client.
+
+The following screenshots show an example of conversation in the Teams client and the transcript file of the same conversation in the review set. The purple highlighting in the transcript file indicates that the transcript was collected from User2's mailbox.
+
+##### Conversation in Teams client
+
+![Conversation shown in the transcript file in the review set.](..\media\TeamsClient1.png)
+
+##### Conversation in transcript file
+
+![Same conversation shown in Teams client.](..\media\TeamsTranscript1.png)
+
+### Transcript conversation threading
+
+Conversation threading functionality in the new case format in eDiscovery (Premium) helps you identify contextual content related to items that may be relevant to your investigation. This feature produces distinct conversation views that include chat messages that precede and follow the items match the search query during collection. This capability allows you to efficiently and rapidly review complete chat conversations (called *threaded conversations*) in Microsoft Teams. As previous explained, chat conversations are reconstructed in HTML transcript files when eDiscovery (Premium) adds Teams content to a review set.
+
+Here's the logic used by eDiscovery (Premium) to include additional messages and replies transcript files that provide context around the items match the collection query (called *responsive items*) you used when collecting Teams content. Different threading behaviors are based on the types of chats and the search query used to collect the responsive items. There are two common collection scenarios:
+
+- Queries that use search parameters, such as keywords and property:value pairs
+
+- Queries that only use date ranges
+
+|Teams content type|Queries with search parameters|Queries with date ranges|
+||||
+|Teams 1:1 and group chats|Messages that were posted 12 hours before and 12 hours after responsive items are grouped with the responsive item in a single transcript file.|Messages in a 24-hour window are grouped in a single transcript file.|
+|Standard, private, and shared Teams channel chats|Each post that contains responsive items and all corresponding replies are grouped in a single transcript file.|Each post that contains responsive items and all corresponding replies are grouped in a single transcript file.|
+
+### Deduplication of Teams content
+
+The following list describes the deduplication (and duplication) behavior when collecting Teams content into a review set.
+
+- Each transcript file added to a review set should be a one-to-one mapping to content stored in data locations. That means eDiscovery (Premium) doesn't collect any Teams content that has already been added to the review set. If a chat message is already collected in a review set, eDiscovery (Premium) doesn't add the same message from the same data location to the review set in subsequent collections.
+
+- For 1:1 and group chats, copies of messages are stored in the mailbox of each conversation participant. Copies of the same conversation that exist in different participants' mailboxes are collected with different metadata. As a result, each instance of the conversation is treated as unique and brought into the review set in separate transcript files. So if all participants of a 1:1 or group chat are added as custodians in a case and included in the scope of a collection, then copies of each transcript (for the same conservation) are added to the review set and will be grouped together with the same **ConversationId**. Each of these copies is associated with a corresponding custodian. **Tip**: The **Custodian** column in the review set list identifies the custodian for the corresponding transcript file.
+
+- In subsequent collections of items from the same conversation, only the delta content that wasn't previously collected previously is added to the review set and grouped (by sharing the same **ConversationId**) with the previously collected transcripts from the same conversation. Here's an example of this behavior:
+
+ 1. Collection A collects messages in a conversation between User1 and User2 and adds to review set.
+
+ 2. Collection B collects messages from the same conversation, but there are new messages between User1 and User2 since Collection A was run.
+
+ 3. Only the new messages in Collection B are added to the review set. These messages are added to a separate transcript file, but the new transcript is grouped with the transcripts from Collection A by the same **ConversationId**.
+
+ This behavior applies to all the types of Teams chats.
+
+### Metadata for Teams content
+
+In large review sets with thousands or millions of items, it can be difficult to narrow the scope of your review to Teams content. To help you focus your review on Teams content, there are metadata properties that are specific to Teams content. You can use these properties to organize the columns in the review list and [configure filters and queries](ediscovery-review-set-search.md) to optimize the review of Teams content. These metadata properties are also included when you export Teams content from eDiscovery (Premium), to help you organize and view content post-export or in third-party eDiscovery tools.
+
+The following table describes metadata properties for Teams content.
+
+|Metadata property|Description|
+|||
+|ContainsEditedMessage|Indicates whether a transcript file contains an edited message. Edited messages are identified when viewing the transcript file.|
+|ConversationId|A GUID that identifies the conversation that the item is associated with. Transcript files and attachments from the same conversation have the same value for this property.|
+|Conversation name|The name of the conversation the transcript file or attachment is associated with. For Teams 1:1 and group chats, the value of this property is the UPN of all participants of the conversation are concatenated. For example, `User3 <User3@contoso.onmicrosoft.com>,User4 <User4@contoso.onmicrosoft.com>,User2 <User2@contoso.onmicrosoft.com>`. Teams channel (standard, private, and shared) chats use the following format for conversation name: `<Team name>,<Channel name>`. For example, `eDiscovery vNext, General`.|
+|ConversationType|Indicates the type of Team chat. For Teams 1:1 and group chats, the value for this property is `Group`. For standard, private, and shared channel chats, the value is `Channel`.|
+|Date|The time stamp of the first message in the transcript file.|
+|FamilyId|A GUID that identifies the transcript file for a chat conversation. Attachments will have the same value for this property as the transcript file that contains the message the file was attached to.|
+|FileClass|Indicates that type of content. Items from Teams chats have the value `Conversation`. In contrast, Exchange email messages have the value `Email`.|
+|MessageKind|The message kind property. Teams content has the value `microsoftteams , im`.|
+|Recipients|A list of all users who received a message within the transcript conversation.|
+|TeamsChannelName|The Teams channel name of the transcript.|
+
+For descriptions of other eDiscovery (Premium) metadata properties, see [Document metadata fields in eDiscovery (Premium)](ediscovery-document-metadata-fields.md).
+
+## Export Teams content
+
+After you have reviewed and culled Teams content in a review set, you can export the transcript files that contain content that's responsive to your investigation. There aren't any specific export settings for Teams content. Each transcript file is exported as an HTML message file. This file also contains hidden CDATA tags with all metadata for the individual chat messages. The metadata properties discussed in the previous section are included when Teams content is exported.
+
+Each transcript file is referenced in the load file and can be located using the relative path in the Export_native_path field in the load file. Transcript files are located in the Conversations folder in the root export folder.
+
+## Tips for viewing Teams content in a review set
+
+Here are some tips and best practices for viewing Teams content in a review set.
+
+- Use the **Customize columns** control in the command bar to add and organize columns to optimize the review of Teams content.
+
+ ![Use the Edit column flyout page to add, remove, and organize columns.](..\media\EditReviewSetColumns.png)
+
+ You can add and remove columns that are useful for Teams content. You can also sequence the order of columns by dragging and dropping them in the **Edit column** flyout page. You can also sort on columns to group Teams content with similar values for the column you sort on.
+
+- Useful columns that to help you review Teams content include **Custodian**, **Recipients**, and **File type** or **Message kind**.
+
+- Use [filters](ediscovery-review-set-search.md) for Teams-related properties to quickly display Teams content. There are filters for most of the metadata properties described in the previous section.
+
+## Deleting Teams chat messages
+
+You can use eDiscovery (Premium) and the Microsoft Graph Explorer to respond to data spillage incidents, when content containing confidential or malicious information is released through Teams chat messages. Admins in your organization can search for and delete chat messages in Microsoft Teams. This can help you remove sensitive information or inappropriate content in Teams chat messages. For more information, see [Search and purge chat messages in Teams](ediscovery-search-and-delete-teams-chat-messages.md).
+
+## Reference guide
+
+Here's a quick reference guide for using eDiscovery (Premium) for Microsoft Teams. This guide summarizes the keys points for using eDiscovery (Premium) to preserve, collect, review, and export content from Microsoft Teams.
+
+![Thumbnail for reference guide for using eDiscovery (Premium) for Microsoft Teams.](../media/AeDTeamsReferenceGuide-thumbnail.png)
+
+[Download as a PDF file](https://download.microsoft.com/download/9/e/4/9e4eec6f-c476-452f-b414-4bd4b5c39dca/AeDTeamsReferenceGuide.pdf)
compliance Get Started With Service Trust Portal https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/get-started-with-service-trust-portal.md
Title: "Get started with the Microsoft Service Trust Portal"
description: Learn how to access and use the Microsoft Service Trust Portal to help with security, privacy, and compliance practices. f1.keywords: - NOCSH--++ audience: Admin
compliance Insider Risk Management Audit Log https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/insider-risk-management-audit-log.md
Title: Insider risk management audit log
+ Title: Review activities with the insider risk management audit log
description: Learn about the insider risk management audit log in Microsoft Purview keywords: Microsoft 365, Microsoft Purview, insider risk, risk management, compliance ms.localizationpriority: medium
- purview-compliance
-# Insider risk management audit log
+# Review activities with the insider risk management audit log
>[!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.
compliance Insider Risk Management Cases https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/insider-risk-management-cases.md
Title: Insider risk management cases
+ Title: Take action on insider risk management cases
description: Learn about insider risk management cases in Microsoft Purview keywords: Microsoft 365, Microsoft Purview, insider risk, risk management, compliance ms.localizationpriority: medium
-# Insider risk management cases
+# Take action on insider risk management cases
>[!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.
compliance Insider Risk Management Content Explorer https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/insider-risk-management-content-explorer.md
Title: Insider risk management Content explorer
+ Title: Review date with the insider risk management content explorer
description: Learn about insider risk management Content explorer in Microsoft Purview keywords: Microsoft 365, Microsoft Purview, insider risk, risk management, compliance ms.localizationpriority: medium
- purview-compliance
-# Insider risk management Content explorer
+# Review date with the insider risk management content explorer
> [!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.
compliance Insider Risk Management Notices https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/insider-risk-management-notices.md
Title: Insider risk management notice templates
+ Title: Create insider risk management notice templates
description: Learn about insider risk management notice templates in Microsoft Purview keywords: Microsoft 365, Microsoft Purview, insider risk, risk management, compliance ms.localizationpriority: medium
-# Insider risk management notice templates
+# Create insider risk management notice templates
> [!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.
compliance Insider Risk Management Policies https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/insider-risk-management-policies.md
Title: Insider risk management policies
+ Title: Create and manage insider risk management policies
description: Learn about insider risk management policies in Microsoft Purview keywords: Microsoft 365, Microsoft Purview, insider risk, risk management, compliance ms.localizationpriority: medium
-# Insider risk management policies
+# Create and manage insider risk management policies
> [!IMPORTANT] > Microsoft Purview Insider Risk Management correlates various signals to identify potentially 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 the following table to determine the maximum number of in-scope users suppor
To create a new insider risk management policy, you'll generally use the policy wizard in the **Insider risk management** solution in the Microsoft Purview compliance portal. You can also create quick policies for general data leaks and data theft by departing users from Analytics checks if applicable.
-Complete the following steps to create a new policy using the policy wizard:
-
-1. In the [Microsoft Purview compliance portal](https://compliance.microsoft.com), go to **Insider risk management** and select the **Policies** tab.
-2. Select **Create policy** to open the policy wizard.
-3. On the **Policy template** page, choose a policy category and then select the template for the new policy. These templates are made up of conditions and indicators that define the risk activities you want to detect and investigate. Review the template prerequisites, triggering events, and detected activities to confirm this policy template fits your needs.
-
- > [!IMPORTANT]
- > Some policy templates have prerequisites that must be configured for the policy to generate relevant alerts. If you haven't configured the applicable policy prerequisites, see **Step 4** in the [Get started with insider risk management](/microsoft-365/compliance/insider-risk-management-configure).
-
-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.
- - **Description (optional)**: Enter a description for the policy.
-
-6. Select **Next** to continue.
-7. On the **Users and groups** page, select **Include all users and groups** or **Include specific users and groups** to define which users or groups are included in the policy, or if you've chosen a priority users-based template; select **Add or edit priority user groups**. Selecting **Include all users and groups** will look for triggering events for all users and groups in your organization to start assigning risk scores for the policy. Selecting **Include specific users and groups** allows you to define which users and groups to assign to the policy. Guest user accounts aren't supported.
-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 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 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 determining 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 *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. If you've selected the *Data leaks by risky users* or *Security policy violations by risky 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 risky user events are reported in your HR system. If you select the **Risk 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 *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.
-
- 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.
- If you've selected the *Risky browser usage* policy template, select one or more of the **Browsing indicators**.
-
-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.
+Complete [Step 6: Create an insider risk management policy](/microsoft-365/compliance/insider-risk-management-configure#step-6-required-create-an-insider-risk-management-policy) to configure new insider risk policies.
## Update a policy
compliance Insider Risk Management Settings https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/insider-risk-management-settings.md
Title: Insider risk management settings
+ Title: Get started with insider risk management settings
description: Learn about insider risk management settings in Microsoft Purview keywords: Microsoft 365, Microsoft Purview, insider risk, risk management, compliance ms.localizationpriority: medium
compliance Insider Risk Management Users https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/insider-risk-management-users.md
Title: Insider risk management Users dashboard
+ Title: Manage the workflow with the insider risk management users dashboard
description: Learn about insider risk management Users dashboard in Microsoft Purview keywords: Microsoft 365, Microsoft Purview, insider risk, risk management, compliance ms.localizationpriority: medium
-# Insider risk management Users dashboard
+# Manage the workflow with the insider risk management users dashboard
> [!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.
compliance Search For Content https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/search-for-content.md
To help make this easier, we've created several Security & Compliance PowerShell
- [Search specific mailbox and site folders](use-content-search-for-targeted-collections.md) (called a *targeted* collection) when you're confident that items responsive to a case are located in that folder. - [Search the mailbox and OneDrive location](search-the-mailbox-and-onedrive-for-business-for-a-list-of-users.md) for a list of users.-- [Create, report on, and delete multiple searches](ediscovery-create-report-on-and-delete-multiple-content-searches.md) to quickly and efficiently identify and cull search data.
+- [Create, report on, and delete multiple searches](ediscovery-create-reports-and-delete-multiple-content-searches.md) to quickly and efficiently identify and cull search data.
- [Clone a content search](clone-a-content-search.md) and quickly compare the results of different keyword search queries run on the same content locations; or use the script to save time by not having to re-enter a large number of content locations when you create a new search.
frontline Flw Licensing Options https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/frontline/flw-licensing-options.md
With this example, you can mix license types for the two types of workers in you
| Frontline workers can find organization-wide resources, communications, or training with SharePoint, OneDrive, Viva Engage, and Stream. | Information workers create or consume team or organization-wide resources and communications with included Microsoft 365 services (depending on the specific license). | For a detailed comparison of what's included in Microsoft 365 with various licenses, see this [Comparison table](https://go.microsoft.com/fwlink/?linkid=2139145).+
+## Related topics
+
+[Limits and specifications for Microsoft Teams](/microsoftteams/limits-specifications-teams)
includes Microsoft 365 Content Updates https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/includes/microsoft-365-content-updates.md
+## Week of January 02, 2023
++
+| Published On |Topic title | Change |
+|||--|
+| 1/2/2023 | [Get scan history by definition](/microsoft-365/security/defender-endpoint/get-scan-history-by-definition?view=o365-worldwide) | added |
+| 1/2/2023 | [Get scan history by session](/microsoft-365/security/defender-endpoint/get-scan-history-by-session?view=o365-worldwide) | added |
+| 1/2/2023 | [Add, update or delete a scan definition](/microsoft-365/security/defender-endpoint/add-a-new-scan-definition?view=o365-worldwide) | added |
+| 1/2/2023 | [Get all scan agents](/microsoft-365/security/defender-endpoint/get-all-scan-agents?view=o365-worldwide) | added |
+| 1/2/2023 | [Get scan definitions](/microsoft-365/security/defender-endpoint/get-all-scan-definitions?view=o365-worldwide) | added |
+| 1/2/2023 | [Authenticated scan methods and properties](/microsoft-365/security/defender-endpoint/get-authenticated-scan-properties?view=o365-worldwide) | added |
+| 1/2/2023 | [Windows authenticated scan in Defender Vulnerability Management](/microsoft-365/security/defender-vulnerability-management/windows-authenticated-scan?view=o365-worldwide) | added |
+| 1/2/2023 | [Network device discovery and vulnerability management](/microsoft-365/security/defender-endpoint/network-devices?view=o365-worldwide) | modified |
+| 1/3/2023 | [Decryption in Microsoft Purview eDiscovery tools](/microsoft-365/compliance/ediscovery-decryption?view=o365-worldwide) | modified |
+| 1/3/2023 | [Microsoft Defender for Cloud Apps in Microsoft 365 Defender (Preview)](/microsoft-365/security/defender/microsoft-365-security-center-defender-cloud-apps?view=o365-worldwide) | modified |
+| 1/3/2023 | [Use the eDiscovery Export Tool in Microsoft Edge](/microsoft-365/compliance/ediscovery-configure-edge-to-export-search-results?view=o365-worldwide) | modified |
+| 1/3/2023 | [Locations of Microsoft Online Services Personnel with Remote Access to Data](/microsoft-365/enterprise/personnel-loc/m365-personnel-location?view=o365-worldwide) | added |
+| 1/3/2023 | [Top 10 ways to secure your business data](/microsoft-365/admin/security-and-compliance/secure-your-business-data?view=o365-worldwide) | modified |
+| 1/3/2023 | [Learn about communication compliance](/microsoft-365/compliance/communication-compliance?view=o365-worldwide) | modified |
+| 1/3/2023 | [Offboard a device from Microsoft Defender for Business](/microsoft-365/security/defender-business/mdb-offboard-devices?view=o365-worldwide) | modified |
+| 1/3/2023 | [Onboard devices to Microsoft Defender for Business](/microsoft-365/security/defender-business/mdb-onboard-devices?view=o365-worldwide) | modified |
+| 1/4/2023 | [Create indicators](/microsoft-365/security/defender-endpoint/manage-indicators?view=o365-worldwide) | modified |
+| 1/4/2023 | [What's new in Microsoft Purview risk and compliance solutions](/microsoft-365/compliance/whats-new?view=o365-worldwide) | modified |
+| 1/4/2023 | [Service advisories for auto-expanding archive utilization in Exchange Online monitoring](/microsoft-365/enterprise/microsoft-365-exo-archive-advisory?view=o365-worldwide) | added |
+| 1/4/2023 | [Find Microsoft 365 for business support phone numbers by country or region](/microsoft-365/admin/support-contact-info?view=o365-worldwide) | modified |
+| 1/4/2023 | [Learn about auto-expanding archiving](/microsoft-365/compliance/autoexpanding-archiving?view=o365-worldwide) | modified |
+| 1/4/2023 | [Microsoft 365 Multi-Tenant Organization People Search](/microsoft-365/enterprise/multi-tenant-people-search?view=o365-worldwide) | modified |
+| 1/5/2023 | [Performance analyzer for Microsoft Defender Antivirus](/microsoft-365/security/defender-endpoint/tune-performance-defender-antivirus?view=o365-worldwide) | modified |
+| 1/5/2023 | [Overview of Microsoft 365 Lighthouse](/microsoft-365/lighthouse/m365-lighthouse-overview?view=o365-worldwide) | modified |
+| 1/5/2023 | [Create safe sender lists](/microsoft-365/security/office-365-security/create-safe-sender-lists-in-office-365?view=o365-worldwide) | modified |
+| 1/6/2023 | [Understand next-generation protection configuration settings in Microsoft Defender for Business](/microsoft-365/security/defender-business/mdb-next-gen-configuration-settings?view=o365-worldwide) | modified |
+| 1/6/2023 | [Get scan history by definition](/microsoft-365/security/defender-endpoint/get-scan-history-by-definition?view=o365-worldwide) | modified |
+| 1/6/2023 | [Get scan history by session](/microsoft-365/security/defender-endpoint/get-scan-history-by-session?view=o365-worldwide) | modified |
+| 1/6/2023 | [Migrate to Microsoft Defender for Endpoint from non-Microsoft endpoint protection](/microsoft-365/security/defender-endpoint/switch-to-mde-overview?view=o365-worldwide) | modified |
+| 1/6/2023 | [Switch to Microsoft Defender for Endpoint - Prepare](/microsoft-365/security/defender-endpoint/switch-to-mde-phase-1?view=o365-worldwide) | modified |
+| 1/6/2023 | [Common Zero Trust identity and device access policies - Microsoft 365 for enterprise](/microsoft-365/security/office-365-security/identity-access-policies?view=o365-worldwide) | modified |
+| 1/6/2023 | [Top 12 tasks for security teams to support working from home](/microsoft-365/security/top-security-tasks-for-remote-work?view=o365-worldwide) | modified |
++ ## Week of December 26, 2022
security Linux Install Manually https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/defender-endpoint/linux-install-manually.md
Download the onboarding package from Microsoft 365 Defender portal.
- Look at the alert details, machine timeline, and perform your typical investigation steps.
+## Microsoft Defender for Endpoint package external package dependencies
+
+The following external package dependencies exist for the mdatp package:
+
+ - The mdatp RPM package requires "glibc >= 2.17", "audit", "policycoreutils", "selinux-policy-targeted", "mde-netfilter"
+ - For RHEL6 the mdatp RPM package requires "audit", "policycoreutils", "libselinux", "mde-netfilter"
+ - For DEBIAN the mdatp package requires "libc6 >= 2.23", "uuid-runtime", "auditd", "mde-netfilter"
+
+The mde-netfilter package also has the following package dependencies:
+
+ - For DEBIAN the mde-netfilter package requires "libnetfilter-queue1", "libglib2.0-0"
+ - for RPM the mde-netfilter package requires "libmnl", "libnfnetlink", "libnetfilter_queue", "glib2"
+
+If the Microsoft Defender for Endpoint installation fails due to missing dependencies errors, you can manually download the pre-requisite dependencies.
+ ## Installer script Alternatively, you can use an automated [installer bash script](https://github.com/microsoft/mdatp-xplat/blob/master/linux/installation/mde_installer.sh) provided in our [public GitHub repository](https://github.com/microsoft/mdatp-xplat/).
security Linux Whatsnew https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/defender-endpoint/linux-whatsnew.md
This article is updated frequently to let you know what's new in the latest rele
- [What's new in Defender for Endpoint on macOS](mac-whatsnew.md) - [What's new in Defender for Endpoint on iOS](ios-whatsnew.md)
+<details>
+ <summary>Jan-2023 (Build: 101.94.13 | Release version: 30.122112.19413.0)</summary>
+
+&ensp;Released: **January 10, 2023**<br/>
+&ensp;Published: **January 10, 2023**<br/>
+&ensp;Build: **101.94.13**<br/>
+&ensp;Release version: **30.122112.19413.0**<br/>
+&ensp;Engine version: **1.1.19700.3**<br/>
+&ensp;Signature version: **1.377.550.0**<br/>
+
+**What's new**
+
+- There are multiple fixes and new changes in this release
+ - Skip quarantine of threats in passive mode by default.
+ - New config, nonExecMountPolicy, can now be used to specify behavior of RTP on mount point marked as noexec.
+ - Improved performance under high load and in speed test scenarios.
+ - Fixes an issue with accessing SMB shares behind Cisco AnyConnect VPN connections.
+ - Fixes an issue with Network Protection and SMB.
+ - lttng performance tracing support.
+ - TVM, eBPF, auditd, telemetry and mdatp cli improvements.
+ - mdatp health will now report behavior_monitoring
+ - Other fixes.
+
+**Known issues**
+
+- While upgrading from mdatp version 101.75.43 or 101.78.13, you may encounter a kernel hang. Run the following commands before attempting to upgrade to version 101.94.13. More information about the underlying issue can be found at [System hang due to blocked tasks in fanotify code](https://access.redhat.com/solutions/2838901)
+
+There are two ways to mitigate the problem in upgrading.
+
+Use your package manager to uninstall the 101.75.43 or 101.78.13 mdatp version.
+Example:
+```bash
+sudo apt purge mdatp
+sudo apt-get install mdatp
+```
+
+As an alternative to the above, you can follow the instructions to [uninstall](/microsoft-365/security/defender-endpoint/linux-resources#uninstall), then [install](/microsoft-365/security/defender-endpoint/linux-install-manually#application-installation) the latest version of the package.
+
+In case you don't want to uninstall mdatp you can disable rtp and mdatp in sequence before upgrade.
+Caution: Some customers(<1%) are experiencing issues with this method.
+
+ ```bash
+sudo mdatp config real-time-protection --value=disabled
+sudo systemctl disable mdatp
+```
+
+</details>
+ <details> <summary>Nov-2022 (Build: 101.85.27 | Release version: 30.122092.18527.0)</summary>
security Switch To Mde Phase 2 https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/defender-endpoint/switch-to-mde-phase-2.md
As you're making the switch to Defender for Endpoint, you might need to take cer
|Endpoint type|What to do| ||| |Windows clients (such as endpoints running Windows 10 and Windows 11)|In general, you don't need to take any action for Windows clients (unless Microsoft Defender Antivirus has been uninstalled). In general, Microsoft Defender Antivirus should still be installed, but is most likely disabled at this point of the migration process. <br/><br/> When a non-Microsoft antivirus/antimalware solution is installed and the clients aren't yet onboarded to Defender for Endpoint, Microsoft Defender Antivirus is disabled automatically. Later, when the client endpoints are onboarded to Defender for Endpoint, if those endpoints are running a non-Microsoft antivirus solution, Microsoft Defender Antivirus goes into passive mode. <br/><br/> If the non-Microsoft antivirus solution is uninstalled, Microsoft Defender Antivirus goes into active mode automatically.|
-|Windows servers|On Windows Server, you'll need to reinstall Microsoft Defender Antivirus, and set it to passive mode manually. On Windows servers, when a non-Microsoft antivirus/antimalware is installed, Microsoft Defender Antivirus can't run alongside the non-Microsoft antivirus solution. In those cases, Microsoft Defender Antivirus is disabled or uninstalled manually. <br/><br/> To reinstall or enable Microsoft Defender Antivirus on Windows Server, perform the following tasks: <br/>- [Re-enable Defender Antivirus on Windows Server if it was disabled](enable-update-mdav-to-latest-ws.md#re-enable-microsoft-defender-antivirus-on-windows-server-if-it-was-disabled)<br/>- [Re-enable Defender Antivirus on Windows Server if it was uninstalled](enable-update-mdav-to-latest-ws.md#re-enable-microsoft-defender-antivirus-on-windows-server-if-it-was-uninstalled)<br/>- [Set Microsoft Defender Antivirus to passive mode on Windows Server](#set-microsoft-defender-antivirus-to-passive-mode-on-windows-server) <br/><br/>If you run into issues reinstalling or re-enabling Microsoft Defender Antivisrus on Windows Server, see [Troubleshooting: Microsoft Defender Antivirus is getting uninstalled on Windows Server](switch-to-mde-troubleshooting.md#microsoft-defender-antivirus-is-getting-uninstalled-on-windows-server).|
+|Windows servers|On Windows Server, you'll need to reinstall Microsoft Defender Antivirus, and set it to passive mode manually. On Windows servers, when a non-Microsoft antivirus/antimalware is installed, Microsoft Defender Antivirus can't run alongside the non-Microsoft antivirus solution. In those cases, Microsoft Defender Antivirus is disabled or uninstalled manually. <br/><br/> To reinstall or enable Microsoft Defender Antivirus on Windows Server, perform the following tasks: <br/>- [Re-enable Defender Antivirus on Windows Server if it was disabled](enable-update-mdav-to-latest-ws.md#re-enable-microsoft-defender-antivirus-on-windows-server-if-it-was-disabled)<br/>- [Re-enable Defender Antivirus on Windows Server if it was uninstalled](enable-update-mdav-to-latest-ws.md#re-enable-microsoft-defender-antivirus-on-windows-server-if-it-was-uninstalled)<br/>- [Set Microsoft Defender Antivirus to passive mode on Windows Server](#set-microsoft-defender-antivirus-to-passive-mode-on-windows-server) <br/><br/>If you run into issues reinstalling or re-enabling Microsoft Defender Antivirus on Windows Server, see [Troubleshooting: Microsoft Defender Antivirus is getting uninstalled on Windows Server](switch-to-mde-troubleshooting.md#microsoft-defender-antivirus-is-getting-uninstalled-on-windows-server).|
> [!TIP] > To learn more about Microsoft Defender Antivirus states with non-Microsoft antivirus protection, see [Microsoft Defender Antivirus compatibility](microsoft-defender-antivirus-compatibility.md).
security Microsoft Secure Score Improvement Actions https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/defender/microsoft-secure-score-improvement-actions.md
This view is what it will look like if you've included all possible score views:
## Take action to improve your score
-The **recommended actions** tab lists the security recommendations that address possible attack surfaces. It also includes their status (to address, planned, risk accepted, resolved through third party, resolved through alternate mitigation, and completed). You can search, filter, and group all the recommended actions.
+The **recommended actions** tab lists the security recommendations that address possible attack surfaces. It also includes their status (to address, planned, risk accepted, resolved through third party, resolved through alternate mitigation, and completed). You can search, filter, and group all the recommended actions.
+
+Once you have completed an action it can take between 24-48 hours for the changes to be reflected in your secure score.
### Ranking
To complete the action, you have a few options:
Add **Notes** to keep track of progress or anything else you want to comment on. If you add your own **tags** to the recommended action, you can filter by those tags.
-### Choose an recommended action status
+### Choose a recommended action status
Choose any statuses and record notes specific to the recommended action.
security Anti Malware Policies Configure https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/office-365-security/anti-malware-policies-configure.md
Creating a custom anti-malware policy in the Microsoft 365 Defender portal creat
**When these types are found**: Select one of the following values:
- - **Reject the message with a non-delivery report (NDR)** (this is the default value)
- - **Quarantine the message**
+ - **Reject the message with a non-delivery report (NDR)**
+ - **Quarantine the message** (this is the default value)
- **Enable zero-hour auto purge for malware**: If you select this option, ZAP quarantines malware messages that have already been delivered. For more information, see [Zero-hour auto purge (ZAP) in Exchange Online](zero-hour-auto-purge.md).
security Recommended Settings For Eop And Office365 https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/office-365-security/recommended-settings-for-eop-and-office365.md
To create and configure anti-malware policies, see [Configure anti-malware polic
||::|::|::|| |**Protection settings**||||| |**Enable the common attachments filter** <br><br> _EnableFileFilter_|Selected <br><br> `$true`|Selected <br><br> `$true`|Selected <br><br> `$true`|This setting quarantines messages that contain attachments based on file type, regardless of the attachment content. For the list of file types, see [Anti-malware policies](anti-malware-protection-about.md#anti-malware-policies).|
-|Common attachment filter notifications (**When these file types are found**) <br><br> _FileTypeAction_|**Reject the messages with a non-delivery receipt (NDR)** <br><br> `Reject`|**Reject the messages with a non-delivery receipt (NDR)** <br><br> `Reject`|**Reject the messages with a non-delivery receipt (NDR)** <br><br> `Reject`||
+|Common attachment filter notifications (**When these file types are found**) <br><br> _FileTypeAction_|**Quarantine the message** <br><br> `Quarantine`|**Quarantine the message** <br><br> `Quarantine`|**Quarantine the message** <br><br> `Quarantine`||
|**Enable zero-hour auto purge for malware** <br><br> _ZapEnabled_|Selected <br><br> `$true`|Selected <br><br> `$true`|Selected <br><br> `$true`|| |**Quarantine policy**|AdminOnlyAccessPolicy|AdminOnlyAccessPolicy|AdminOnlyAccessPolicy|When you create a new anti-malware policy, a blank value means the default quarantine policy is used to define the historical capabilities for messages that were quarantined as malware (AdminOnlyAccessPolicy with no quarantine notifications). <br><br> Standard and Strict preset security policies use the default quarantine policy (AdminOnlyAccessPolicy with no quarantine notifications) as described in the table [here](quarantine-policies.md#step-2-assign-a-quarantine-policy-to-supported-features). <br><br> Admins can create and select custom quarantine policies that define more capabilities for users in the default or custom anti-malware policies. For more information, see [Quarantine policies](quarantine-policies.md).| |**Admin notifications**|||||
solutions Data Privacy Protection Assess https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/solutions/data-privacy-protection-assess.md
+
+ Title: "Assess personal data and privacy risks ΓÇô Microsoft Priva and Purview"
++
+f1.keywords:
+- NOCSH
+ Last updated : 06/22/2020
+audience: ITPro
++
+ms.localizationpriority: medium
+
+- highpri
+- M365-security-compliance
+- Strat_O365_Enterprise
+- m365solution-infoprotection
+- m365solution-overview
+- zerotrust-solution
+
+description: With Microsoft Priva and Microsoft Purview Compliance Manager, see how much personal data your org has and where, and which data privacy regulations apply.
++
+# Data privacy and protection ΓÇô Assess data and risks
+
+Welcome to **Step 1** of managing data privacy and data protection with Microsoft Priva and Microsoft Purview: **Assess your organization's data and risks**.
+
+![The steps to manage data privacy and data protection with Microsoft Priva and Microsoft Purview](../media/data-privacy-protection/manage-data-privacy-protection-steps-one.png)
+
+When you begin your data privacy journey, you'll want to first understand what types of personal data you have, how much, where it's stored, and how it flows over time. The best place to start understanding your data is with Microsoft Priva. You'll next want to know which regulations you'll need to comply with. Microsoft Purview Compliance Manager helps you identify which data privacy regulations most likely apply to your organization.
+
+## Actions to take
+
+|Action|Description|Get details|
+|:|:-|:|
+|Use Priva to understand your organization's personal data.| Priva evaluates your organization's Microsoft 365 environment to determine the types and amounts of sensitive information types and where they're stored. It then gives you insights and key analytics to help you understand the privacy issues and associated risks in your organization.<br><br>To get started with Priva, check to make sure your users are appropriately licensed and have the roles they need. It's also a good idea to confirm that the [Microsoft 365 audit log is enabled](../compliance/audit-log-enable-disable.md).<br><br> We recommend making some initial settings before you start. Visit Priva settings to turn [anonymization](/privacy/priva/priva-settings#anonymization) **On** for greater protection while reviewing sensitive data, and turn [user notification emails](/privacy/priva/priva-settings#user-notification-emails) **Off** while you're getting familiar with Privacy Risk Management policies. You can turn both on later.| [Learn more about Priva](/privacy/priva/priva-overview) <br><br> [Check Priva licensing guidance](/privacy/priva/priva-setup)<br><br>[Set user permissions for Priva](/privacy/priva/priva-permissions)<br><br>[Check Priva settings](/privacy/priva/priva-settings)<br><br>[Find and visualize personal data in your organization](/privacy/priva/priva-data-profile)|
+|Visit Compliance Manager to get your initial compliance score.| The next step is knowing which data protection regulations apply to your organization so you know what your obligations are.<p><p>Keeping up with new and updated laws and regulations can be a full-time job in itself, and many organizations struggle with manual processes for monitoring, updating, and reporting on their state of compliance. Compliance Manager helps manage the complexities of implementing controls through built-in control mapping, versioning, and continuous control assessments. This automation and continuous monitoring helps you to stay current with regulations and certifications, and eases reporting to auditors. <p><p>Use Compliance Manager to quickly assess your current environment and get an initial compliance score based on the Microsoft data protection baseline assessment. From there, you can provide information about your industry and location so Compliance Manager can recommend assessments for regulations that are most likely to apply to you. | [Learn more about Compliance Manager](../compliance/compliance-manager.md)<br><br>[Start a premium assessments trial for quick setup of recommended assessments](../compliance/compliance-manager-setup.md#start-a-premium-assessments-trial)<br><br>[Understand how your compliance score is calculated](../compliance/compliance-score-calculation.md)|
+
+## Optimizing your initial setup
+
+Within 48-72 hours of starting Microsoft Priva, you'll start to see insights around personal data display for your organization. On the Priva overview page, you'll see insights on the amount of personal data that exists in your organization, where it lives, and how it moves. These insights are dynamically updated as new data comes in. Over time, you can better understand how personal data evolves in your Microsoft 365 environment so you can more quickly spot issues, identify and assess risks, and take action to fix issues. Learn more about [understanding the data presented on the overview page](/privacy/priva/priva-data-profile#explore-the-overview-page).
+
+ ΓÇïSelect **Data profile** underneath **Privacy risk management** on the left navigation of the Purview compliance portal. On this page, you can explore and document all the personal data types detected across repositories. Based on this information, you can decide if all the data types you're concerned about are successfully detected. If you find something missing, you can [create custom sensitive information types (SITs)](../compliance/create-a-custom-sensitive-information-type.md) and come back to the data profile page in the next 24-48 hours.
+
+There are three data handling policies in Priva Privacy Risk Management: data overexposure, data transfers, and data minimization. You can [learn more about the policy types here](/privacy/priva/risk-management), and we'll discuss them further in step 2 of this solution. A default version of each policy type is set up and running when you start using Priva. You'll see them listed with the word **Default** in their names on your **Policies** page.
+
+***We recommend turning off the default policies*** as you get started. This is because the default policies monitor for personal data based on multiple classification groups (sets of data based on privacy regulations), which can involve a broad array of SITs that may not be relevant to your industry or geographic location. You may also experience a high number of false positives. The result may be that an overwhelming amount of data that's less relevant appears in your data profile and gets factored into your insights. To create a more manageable and accurate view of the personal data you're most concerned with, we suggest setting up a customized policy at first. This also gives you time to become familiar with how policies work and watch for false positives. You can run the policy in test mode and continue to fine tune its settings until it's set up to track exactly what you need.
+
+If you felt overwhelmed by the amount of data presented on your overview and data profile pages at the start, turning off the default policies and setting up one or more custom policies may present a more accurate and workable picture of your data estate and current risks.
+
+We'll walk you through setting up your first policy in step 2 of this guidance.
+
+## Next step
+
+Visit [Step 2. Protect and govern your data](data-privacy-protection-protect-govern.md).
solutions Data Privacy Protection Protect Govern https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/solutions/data-privacy-protection-protect-govern.md
+
+ Title: "Protect and govern personal data ΓÇô Microsoft Priva and Purview"
++
+f1.keywords:
+- NOCSH
+ Last updated : 06/22/2020
+audience: ITPro
++
+ms.localizationpriority: medium
+
+- highpri
+- M365-security-compliance
+- Strat_O365_Enterprise
+- m365solution-infoprotection
+- m365solution-overview
+- zerotrust-solution
+
+description: Use the capabilities in Microsoft Priva and Microsoft Purview solutions to help your org protect and govern personal data.
++
+# Data privacy and protection ΓÇô Protect and govern data
+
+Welcome to **Step 2** of managing data privacy and data protection with Microsoft Priva and Microsoft Purview: **Protect and govern your data**.
+
+![The steps to manage data privacy and data protection with Microsoft Priva and Microsoft Purview](../media/data-privacy-protection/manage-data-privacy-protection-steps-two.png)
+
+When you know what personal data you have, where it is, and your regulatory requirements, it's time to put things in place to protect that data. Microsoft provides comprehensive, robust capabilities to help you protect personal data in two ways:
+1. Features that IT admins set up to categorize sensitive items and take protective actions, and
+1. Features that empower your employees to spot and fix data privacy issues quickly and get trained on sound data handling practices.
+
+## Actions to take
+
+|Action|Description|Get details|
+|:|:-|:|
+|Identify sensitive information types so you know what needs protection.| Identifying and categorizing sensitive items managed by your organization is the first step in the Information Protection discipline. <p><p>Microsoft Purview provides three ways of identifying items so that they can be categorized a) manually by users, b) automated pattern recognition, like sensitive information types, and c) machine learning.<p><p>Sensitive information types (SIT) are pattern-based classifiers. They detect sensitive information like social security, credit card, or bank account numbers to identify sensitive items.| [Learn more about sensitive information types](../compliance/sensitive-information-type-learn-about.md)<br><br> [View the full list of sensitive information types](../compliance/sensitive-information-type-entity-definitions.md)|
+|Categorize and label your content so you can apply features to protect it.| Categorizing and labeling content so it can be protected and handled properly is the starting place for the information protection discipline. Microsoft 365 has three ways to classify content.| [Learn more about trainable classifiers](../compliance/classifier-learn-about.md)|
+|Apply sensitivity labels to protect data, even if it roams.| When youΓÇÖve identified your sensitive data, youΓÇÖll want to protect it. ThatΓÇÖs often challenging when people collaborate with others both inside and outside the organization. That data can roam everywhere, across devices, apps, and services. And when it roams, you want it to do so in a secure, protected way that meets your organization's business and compliance policies. <p><p>Sensitivity labels from Microsoft Purview Information Protection let you classify and protect your organization's data, while making sure that user productivity and their ability to collaborate isn't hindered.| [Learn more about sensitivity labels](../compliance/sensitivity-labels.md)|
+|Use data loss prevention policies to prevent the sharing of personal data.| Organizations have sensitive information under their control such as financial data, proprietary data, credit card numbers, health records, or social security numbers. To help protect sensitive information and reduce risk, they need a way to prevent their users from inappropriately sharing it with people who shouldn't have it. This practice is called data loss prevention (DLP).<p><p>Using Microsoft Purview Data Loss Prevention, you implement data loss prevention by defining and applying DLP policies to identify, monitor, and automatically protect sensitive items across Microsoft 365 services such as Teams, Exchange, SharePoint, and OneDrive; Office applications such as Word, Excel, and PowerPoint; Windows 10, Windows 11, and macOS (the current version and the previous two versions of macOS) endpoints; non-Microsoft cloud apps; and on-premises file shares and on-premises SharePoint.<p><p>This DLP solution detects sensitive items by using deep content analysis, not by just a simple text scan. Content is analyzed for primary data matches to keywords, by the evaluation of regular expressions, by internal function validation, and by secondary data matches that are in proximity to the primary data match. Beyond that, DLP also uses machine learning algorithms and other methods to detect content that matches your DLP policies.| [Learn more about data loss prevention](../compliance/dlp-learn-about-dlp.md)|
+|Govern your Microsoft 365 data for compliance or regulatory requirements| Information governance controls can be employed in your environment to help address data privacy compliance needs, including a number that are specific to General Data Protection Regulation (GDPR), HIPAA-HITECH (the United States health care privacy act), California Consumer Protection Act (CCPA), and the Brazil Data Protection Act (LGPD). Microsoft Purview Data Lifecycle Management and Microsoft Purview Records Management provide these controls in the form of retention policies, retention labels, and records management capabilities. | [Learn how to deploy a data governance solution with Microsoft Purview](../compliance/data-governance-solution.md)|
+|Set up secure storage of personal data in Microsoft Teams.| If you plan to store highly sensitive personal data in Teams, you can configure a private team and use a sensitivity label that's specifically configured to secure access to the team and files within it.| [Learn more about configuring a team with security isolation](secure-teams-security-isolation.md)|
+|Empower users to spot potential risks and fix issues.| Create data handling policies in Priva Privacy Risk Management so that your users can immediately identify risks in the data they create and manage.<p><p>Notification emails alert users when they transfer items with personal data within our outside of the organization, make content too broadly accessible, or hold onto personal data for too long. The notifications prompt users to take immediate remediation steps to secure personal data, and contain links to your organization's preferred privacy training.| [Learn more about Privacy Risk Management](/privacy/priva/risk-management)<br><br>[Create a policy to prevent data transfers, overexposure, or hoarding](/privacy/priva/risk-management-policies)<br><br>[Set up notifications for users to fix issues with content they handle](/privacy/priva/risk-management-notifications)|
+|Use records management for high-value items that must be managed for business, legal, or regulatory record-keeping requirements.| A records management system is a solution for organizations to manage regulatory, legal, and business-critical records.<p><p>Microsoft Purview Records Management helps an organization manage their legal obligations, provides the ability to demonstrate compliance with regulations, and increases efficiency with regular disposition of items that are no longer required to be retained, no longer of value, or no longer required for business purposes.| [Learn more about sensitivity labels](../compliance/sensitivity-labels.md)|
+
+## Setting up your strategy for success
+
+Identifying sensitive information types (SITs), categorizing and labeling your content, and deploying data loss prevention (DLP) policies are key steps in an [information protection strategy](../compliance/information-protection-solution.md). The links in the table above take you to detailed guidance for carrying out these essential tasks.
+
+Protecting data is also the responsibility of every user in your organization who views, creates, and handles personal data in the course of the job duties. Each user must know and abide by your organization's internal and regulatory responsibilities to protect personal data wherever it exists in your organization. To that end, Priva helps you empower your users to know their responsibilities, to be informed when they're handling data in risky ways, and take immediate action to minimize privacy risks to the organization.
+
+The three data handling policies available in Priva Privacy Risk Management help your users play a proactive role in your organization's data protection strategy. Email notifications with built-in remediation actions prompt users to apply the necessary protections and take a privacy training designated by your organization. This awareness and ability to act can help to cultivate better habits for preventing future privacy issues.
+
+### Recommendations for your first Priva data handling policy
+
+We recommend deploying policies in a phased approach so you can get to know how they behave and optimize them to suit your needs. For the first phase, we recommend creating one custom policy to serve as a basis of understanding. Let's use the example of creating a [data overexposure policy](/privacy/priva/risk-management-policy-data-overexposure), which identifies content items containing personal data that may be too broadly accessible by other people. You can find [detailed policy creation instructions starting here](/privacy/priva/risk-management-policy-data-overexposure#custom-setup-guided-policy-creation-process).
+
+- When you get to the **Chose data to monitor** step of the policy creation wizard, we recommend selecting the **Individual sensitive information types** option and choosing the SITs that are most relevant to your organization. For example, if you're a financial services company with customers in Europe, you'll likely want to include the EU debit card number as one of your SITs. [Find the list of SIT definitions here](../compliance/sensitive-information-type-entity-definitions.md).
+
+- At the **Choose users and groups covered by this policy** step, we recommend selecting **Specific users or groups** and choosing a small inner circle of users in scope for this policy.
+
+- At the **Choose conditions for the policy** step, we recommend selecting only **External** so that you're tracking data you might consider more at risk while keeping the total amount of data you'll have to monitor at more manageable levels.
+
+- At the **Specify alerts and thresholds** step, we recommend turning alerts **On** so that when admins see alerts when policy matches are detected, they can gauge whether the severity and frequency meet their needs. Note that policies don't work retrospectively, so if you decide to keep alerts off at first and later turn them on, you wouldn't see any alerts for matches that occurred prior to turning on alerts.
+
+- At the **Decide policy mode** state, we recommend [keeping the policy in test mode](/privacy/priva/risk-management-policies#testing-a-policy) and monitoring its performance for at least five days. This allows you to see what kind of matches the policy conditions are picking up, how the alerts will fire.
+
+### Gradually setting up more policies and fine-tuning performance
+
+After setting up and running your first policy, you may want to do the same with the other two policy types. This can be your second phase, where you gradually ramp up on using features as you go and optimize their settings. For example, you may choose not to send [user email notifications](/privacy/priva/risk-management-notifications) at first while you see how many matches your policy detects. Then eventually you may decide to turn email notifications on while the policies are still in test mode (at the **Define outcomes** stage of the policy settings). If users get too many emails, go back into the policy's **Outcomes** settings to adjust the frequency of the notifications. All of this fine-tuning can help you gauge the desired impact on your users before you deploy the policy more broadly throughout your organization.
+
+#### Recommended settings for the other two policy types
+Below are specific recommendations for key settings when creating your first **data transfer** and **data overexposure** policies.
+
+**Data transfer**:
+- For **Data to monitor**, select specific SITs.
+- For **Choose users and groups covered by this policy**, select an inner ring of users.
+- For **Choose conditions for the policy**, choose the condition that matters the most.
+- For **Define outcomes when a policy match is detected**, turn on email notifications.
+- For **Specify alerts and thresholds**, turn alerts on for each time an activity occurs.
+- For **Decide policy mode**, turn the policy mode on (which turns off test mode).
+
+**Data minimization**:
+- For **Data to monitor**, choose specific SITs or classification groups.
+- For **Choose users and groups covered by this policy**, select an inner ring of users.
+- For **Choose conditions for the policy**, choose 30, 60, 90, or 120 days.
+- or **Decide policy mode**, keep the policy in test mode.
+
+### Maximizing policy performance to minimize privacy risks
+
+Allow your policies to run for at least two to four weeks. During this time, you should review and document the following results:
+
+- The matches generated by each policy type and the instances of false positives and false negatives
+- The impact and the feedback from end users and admins
+
+Based on your findings, you can now tune the policy performance by doing the following:
+
+- Including or excluding out-of-the-box and custom SITs or classification groups
+- Creating versions of the policies with conditions and user groups to make targeting more efficient
+- Tweaking the thresholds of the policy, including frequency of emails to users, number of days to monitor, etc.
+
+Think of this as your third phase. You can create more versions of each policy type and deploy them to the whole organization in two rounds: a first round that covers 50% of your users, and a second round that covers 100% of your users.
+
+This is also the stage where you accumulate learnings based on user behavior as noted in Priva and create specific privacy training for your users, which you can include in your policies' user email notifications.
+
+## Next step
+
+Visit [Step 3. Stay on track with privacy regulations](data-privacy-protection-regulations.md).
solutions Data Privacy Protection Regulations https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/solutions/data-privacy-protection-regulations.md
+
+ Title: "Stay on track with data privacy regulations ΓÇô Microsoft Priva and Purview"
++
+f1.keywords:
+- NOCSH
+ Last updated : 06/22/2020
+audience: ITPro
++
+ms.localizationpriority: medium
+
+- highpri
+- M365-security-compliance
+- Strat_O365_Enterprise
+- m365solution-infoprotection
+- m365solution-overview
+- zerotrust-solution
+
+description: Learn how Microsoft Purview Compliance Manager helps you keep up with data privacy regulations through continuous control assessments and regulatory updates.
++
+# Data privacy and protection ΓÇô Stay on track with regulations
+
+Welcome to **Step 3** of managing data privacy and data protection with Microsoft Priva and Microsoft Purview: **Stay on track with privacy regulations**.
+
+![The steps to manage data privacy and data protection with Microsoft Priva and Microsoft Purview](../media/data-privacy-protection/manage-data-privacy-protection-steps-three.png)
+
+Research shows that there are over 250 daily updates to global regulations[*](#reference). Microsoft Purview Compliance Manager helps you keep up with the evolving compliance and risk landscape by providing continuous control assessments and regulatory updates. Choose from a library of 350+ templates that correspond to national, regional, and industry-specific requirements on the collection and use of data. Modify the templates for your needs, or create your own custom template for assessments that meet your unique needs. Explore the links below for detailed guidance on managing your organization's compliance activities with Compliance Manager.
+
+## Actions to take
+
+|Action|Description|Get details|
+|:|:-|:|
+|Monitor progress and improve your compliance score. | Make sure you've set up assessments in Compliance Manger to help you stay on top of new and evolving data privacy regulations and laws that apply to your organization.| [Build and manage assessments in Compliance Manager](../compliance/compliance-manager-assessments.md)<br><br>[Raise your score by completing improvement actions](../compliance/compliance-manager-improvement-actions.md) |
+|Automatically test improvement actions. | To realize the full benefits of continuous control assessment, make sure your settings are configured to enable automatic testing of all eligible improvement actions.| [Set your testing source for automated testing](../compliance/compliance-manager-setup.md#testing-source-for-automated-testing)|
+|Set alerts for changes in Compliance Manager. | Compliance Manager can alert you to changes as soon as they happen so that you can stay on track with your compliance goals. Set up alerts for improvement action changes such as a score increase or decrease, an implementation or test status change, a reassignment, or the addition or removal of evidence.| [Create alert policies](../compliance/compliance-manager-alert-policies.md)|
+|Facilitate the work of assessors and auditors. | Make sure that individuals who oversee compliance activities in the organization have the right roles and can access evidence files and reporting. Compliance Manager allows scoped access to individual assessment for specific users. <br><br>You can upload evidence files to improvement actions that document your implementation and testing work. Assign improvement actions to users serving as assessors so they can determine a pass or fail status.<br><br>Provide reporting on your assessments to compliance stakeholders, auditors, and regulators. Exported reports contain details about control implementation status, test date, and test results.| [Grant user access to individual assessments](../compliance/compliance-manager-assessments.md#grant-user-access-to-individual-assessments)<br><br>[Store evidence documentation](../compliance/compliance-manager-improvement-actions.md#perform-work-and-store-evidence)<br><br>[Assign improvement actions to assessors](../compliance/compliance-manager-improvement-actions.md#assign-improvement-action-to-assessor-for-completion)<br><br>[Export an assessment report](../compliance/compliance-manager-assessments.md#export-an-assessment-report)|
+
+## Next step
+
+Visit [Step 4. Respond to data privacy incidents and subject requests](data-privacy-protection-respond-requests.md).
+
+###### Reference
+*Cost of Compliance 2021, Thomson Reuters, 2021
solutions Data Privacy Protection Respond Requests https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/solutions/data-privacy-protection-respond-requests.md
+
+ Title: "Respond to privacy incidents and subject requests ΓÇô Microsoft Priva and Purview"
++
+f1.keywords:
+- NOCSH
+ Last updated : 06/22/2020
+audience: ITPro
++
+ms.localizationpriority: medium
+
+- highpri
+- M365-security-compliance
+- Strat_O365_Enterprise
+- m365solution-infoprotection
+- m365solution-overview
+- zerotrust-solution
+
+description: Use Microsoft Priva and Microsoft Purview to monitor and investigate data privacy incidents in your organization, including automation of data subject requests.
++
+# Data privacy and protection ΓÇô Respond to incidents and subject requests
+
+Welcome to **Step 4** of managing data privacy and data protection with Microsoft Priva and Microsoft Purview: **Respond to data privacy incidents and subject requests**.
+
+![The steps to manage data privacy and data protection with Microsoft Priva and Microsoft Purview](../media/data-privacy-protection/manage-data-privacy-protection-steps-four.png)
+
+Features in both Purview and Priva can help you monitor, investigate, and respond to data privacy incidents in your organization as you operationalize related capabilities. Having processes, procedures, and other documentation for each incident may also be important to demonstrate compliance to regulatory bodies. These features include:
+
+- Auditing and alert policies
+- Subject rights requests, sometimes referred to as data subject requests
+- More investigative tools and reporting
+
+## Actions to take
+
+|Action|Description|Get details|
+|:|:-|:|
+|Set up alerts for potential incidents.| You can set up alerts to help you respond quickly to an array of privacy incidents, whether they come through Priva, auditing, or other alert policies.| [Priva policy alerts](/privacy/priv)|
+|Manage subject rights requests at scale.| Several privacy regulations around the world grant individualsΓÇöor data subjectsΓÇöthe right to make requests to review or manage the personal data that companies have collected about them. These subject rights requests are also referred to as data subject requests (DSRs), data subject access requests (DSARs), or consumer rights requests.<p><p>For companies that store large amounts of information, finding the relevant data can be a formidable task. Fulfilling the requests, for most organizations, is a highly manual and time consuming process.<p><p>Microsoft Priva Subject Rights Requests is designed to help alleviate the complexity and length of time involved in responding to data subject inquires. This solution provides automation, insights, and workflows to help organizations fulfill requests more confidently and efficiently.| [Learn more about Subject Rights Requests](/privacy/priva/subject-rights-requests)|
+|Use insider risk management as an investigative tool.| Microsoft Purview Insider Risk Management is a compliance solution that helps you minimize internal risk by enabling you detect, investigate, and act on malicious and inadvertent activities in your organization.<p><p>Insider risk policies allow you to define the types of risks to identify and detect in your organization. You can act on cases and escalate 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.| [Learn more about insider risk management](../compliance/insider-risk-management.md)|
+
+## Building your monitoring and response strategy
+
+Most data privacy regulations generally require the type of monitoring and response listed below:
+
+- Auditing, alerting, and reporting for activities related to the storage, sharing, and processing of personal data.
+- The ability to respond to subject requests and, in some cases, perform investigative and other administrative measures to comply with such requests.
+
+Your organization may also wish to perform monitoring and response activities for other purposes, such as other compliance needs or for business reasons. Establishing your monitoring and response scheme for data privacy should be done as part of overall monitoring and response planning, implementation, and management.
+
+Use the links above to explore how Purview capabilities can help you develop a monitoring and response scheme, and answer questions such as:
+
+- What sort of day-to-day monitoring and investigative and reporting techniques are available for the different data types and sources?
+- What mechanisms will be needed to handle subject rights requests and any remedial actions, such as anonymization, redaction, and deletion?
solutions Data Privacy Protection https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/solutions/data-privacy-protection.md
+
+ Title: "Manage data privacy and protection ΓÇô Microsoft Priva and Purview"
++
+f1.keywords:
+- NOCSH
+ Last updated : 06/22/2020
+audience: ITPro
++
+ms.localizationpriority: medium
+
+- highpri
+- M365-security-compliance
+- Strat_O365_Enterprise
+- m365solution-infoprotection
+- m365solution-overview
+- zerotrust-solution
+
+description: Learn how Microsoft Purview and Microsoft Priva provide a unified data privacy and protection platform to help you comply with data privacy regulations.
++
+# Manage data privacy and data protection with Microsoft Priva and Microsoft Purview
+
+At least 71% of countries have passed or introduced data privacy legislation, according to the United Nations. Chances are good that your organization is based in, or has customers or employees in, regions with data privacy laws. A prominent example of a data privacy law with broad impact is the European Union's [General Data Protection Regulation (GDPR)](/compliance/regulatory/gdpr). Many organizations are subject to multiple regulations that themselves are frequently updated. As the regulatory landscape expands, it's never been more critical for organizations to safeguard personal data while staying on top of changes. Failure to comply with data privacy laws and regulations can result in considerable financial penalties, legal and business repercussions, and erosion of your customers' trust.
+
+Data privacy and data protection go hand in hand. You can't have data privacy without data protection. Data protection helps protect personal data stored and managed by your organization from external threats and leakage. Data privacy provides another layer of sophisticated protection, which helps honor the purpose of personal data use and respects a data subject's rights throughout the data lifecycle. To help organizations regardless of size or location fortify their data privacy and protection posture, we offer robust and scalable solutions in Microsoft Priva and Microsoft Purview.
+
+## How Microsoft Priva and Microsoft Purview work together
+
+Microsoft Purview and Microsoft Priva provide a unified platform to help you comply with data privacy regulations. The complementary features in Purview risk and compliance solutions and Priva privacy management solutions help you assess the personal data within your organization, and provide automation and scalability to help reduce the complexity in adequately safeguarding the data.
+
+![How Microsoft Purview and Microsoft Priva work together](../media/data-privacy-protection/purview-priva-together.png)
+
+## How to use this guide
+
+Use the guidance in these articles to help you assess risks and take appropriate action to protect personal data in your Microsoft 365 environment. This guide comprises four overarching steps to help you understand how and when to use the appropriate Microsoft solution for meeting your organization's data privacy obligations.
+
+The steps in this solution are:
+
+![The steps to manage data privacy and data protection with Microsoft Priva and Microsoft Purview](../media/data-privacy-protection/manage-data-privacy-protection-steps.png)
+
+1. [Assess your organization's data and risks](data-privacy-protection-assess.md): Start your journey by understanding your data and possible risks.
+1. [Protect and govern your data](data-privacy-protection-protect-govern.md): Identify, categorize, and manage the data you need to protect.
+1. [Stay on track with privacy regulations](data-privacy-protection-regulations.md): Monitor your progress in completing assessments and stay up-to-date as regulations change.
+1. [Respond to data privacy incidents and subject requests](data-privacy-protection-respond-requests.md): Set up alerts so you can respond to privacy risks and automate your management of data subject requests.
+
+> [!IMPORTANT]
+> Following this guidance will not necessarily make you compliant with any data privacy regulation, especially considering the number of steps required that are outside the context of the features. You are responsible for ensuring your compliance and to consult your legal and compliance teams or to seek guidance and advice from third parties that specialize in compliance.
+
+## Resources
+
+- [Microsoft Privacy](/privacy)
+- [Microsoft Purview risk and compliance solutions](../compliance/purview-compliance.md)
+- [Microsoft compliance offerings](/compliance/regulatory/offering-home)
solutions Information Protection Deploy Assess https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/solutions/information-protection-deploy-assess.md
- Title: "Assess data privacy risks and identify sensitive items with Microsoft 365"---- NOCSH- Previously updated : 07/13/2020----- highpri-- M365-security-compliance-- Strat_O365_Enterprise-- m365solution-infoprotection-- m365solution-scenario-- zerotrust-solution-
-description: Determine the data privacy regulations, the relevant scenarios, your readiness, and the sensitive information types that are in your Microsoft 365 environment.
--
-# Assess data privacy risks and identify sensitive items with Microsoft 365
-
-Assessing the data privacy regulations and risks that your organization is subject to is a first step before implementing any related improvement actions, including actions achievable with Microsoft 365 features and services.
-
-## Potentially applicable data privacy regulations
-
-For a good reference on the broader regulatory framework for data privacy regulations, see the [Microsoft Services Trust Portal](https://servicetrust.microsoft.com/) and the [series of articles on the General Data Protection Regulation (GDPR) regulation](/compliance/regulatory/gdpr). Also review materials on the regulations you may be subject to in your industry or region.
-
-### GDPR
-
-The GDPR is the most well-known and cited of the data privacy regulations. It regulates the collection, storage, processing, and sharing of any personal data that relates to an identified or identifiable natural person that is a resident of the European Union (EU).
-
-According to GDPR Article 4:
--- 'personal data' means any information relating to an identified or identifiable natural person ('data subject'); an identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person.-
-### ISO 27001
-
-Adherence to other standards like ISO 27001 has also been recognized by several European supervisory authorities as a valid proxy of intent across the people, process, and technology spectrum. The standards it specifies overlap and adherence to ISO-27001-driven protection mechanisms may be considered a proxy fulfilling some privacy obligations in certain circumstances.
-
-### Other data privacy regulations
-
-Other prominent data privacy regulations also specify requirements for the handling of personal data.
-
-In the United States, these include the California Consumer Protection Act ([CCPA](/compliance/regulatory/ccpa-faq)), HIPAA-HITECH (United States health care privacy act), and the Graham Leach Bliley Act (GLBA). Other state-specific regulations are also in-place or in development.
-
-Around the world, more examples include Germany's National GDPR Implementation Act (BDSG), the Brazil Data Protection Act (LGPD), and many others.
-
-## Regulation mapping to Microsoft 365 technical control categories
-
-Many of the data privacy-related regulations have overlapping requirements, so you should understand which regulations they're subject to prior to developing any technical control scheme.
-
-For later reference in the articles of this overall solution, this table provides excerpts from a sampling of data privacy regulations.
-
-|Regulation|Article/section|Excerpt|Applicable technical control categories|
-|||||
-|GDPR|Article 5(1)(f)|Personal data shall be processed in a manner that ensures appropriate security of the personal data, including protection against unauthorized or unlawful processing and against accidental loss, destruction or damage, using appropriate technical or organizational measures ('integrity and confidentiality'.|(All) <br> Identity <br> Device <br> Threat Protection <br> Protect information <br> Govern information <br> Discover and respond|
-||Article (32)(1)(a)|Taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of processing as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons, the controller and the processor shall implement appropriate technical and organizational measures to ensure a level of security appropriate to the risk, including inter alia as appropriate: (a) the pseudonymization and encryption of personal data.|Protect information|
-||Article (13)(2)(a)|"...the controller shall, at the time when personal data are obtained, provide the data subject with the following further information necessary to ensure fair and transparent processing: (a) the period for which the personal data will be stored, or if that isn't possible, the criteria used to determine that period.|Govern information|
-||Article (15)(1)(e)|The data subject shall have the right to obtain from the controller confirmation as to whether or not personal data concerning him or her are being processed, and where that is the case, access to the personal data and the following information: (e) the existence of the right to request from the controller rectification or erasure of personal data or restriction of processing of personal data concerning the data subject or to object to such processing|Discover and respond|
-|LGPD|Article 46|Processing agents shall adopt security, technical and administrative measures able to protect personal data from unauthorized accesses and accidental or unlawful situations of destruction, loss, alteration, communication, or any type of improper or unlawful processing.|Protect information <br> Govern information <br> Discover and respond|
-||Article 48|The controller must communicate to the national authority and to the data subject the occurrence of a security incident that may create risk or relevant damage to the data subjects.|Discover and respond|
-|HIPPA-HITECH|45 CFR 164.312(e)(1)|Implement technical security measures to guard against unauthorized access to electronic protected health information that is being transmitted over an electronic communications network.|Protect information|
-||45 C.F.R. 164.312(e)(2)(ii)|Implement a mechanism to encrypt electronic protected health information whenever deemed appropriate.|Protect information|
-||45 CFR 164.312(c)(2)|Implement electronic mechanisms to corroborate that electronic protected health information hasn't been altered or destroyed in an unauthorized manner.|Govern information|
-||45 CFR 164.316(b)(1)(i)|If an action, activity, or assessment is required by this subpart to be documented, maintain a written (which may be electronic) record of the action, activity, or assessment|Govern information|
-||45 CFR 164.316(b)(1)(ii)|Retain the documentation required by paragraph (b)(1) of this section for 6 years from the date of its creation or the date when it last was in effect, whichever is later.|Govern information|
-||45 C.F.R. 164.308(a)(1)(ii)(D)|Implement procedures to regularly review records of information system activity, such as audit logs, access reports, and security incident tracking reports|Discover and respond|
-||45 C.F.R. 164.308(a)(6)(ii)|Identify and respond to suspected or known security incidents; mitigate, to the extent practicable, harmful effects of security incidents that are known to the covered entity or business associate; and document security incidents and their outcomes.|Discover and respond|
-||45 C.F.R. 164.312(b)|Implement hardware, software, and procedural mechanisms that record and examine activity in information systems that contain or use electronic protected health information.|Discover and respond|
-|CCPA|1798.105(c)|A business that receives a verifiable request from a consumer to delete the consumer's personal information pursuant to subdivision (a) of this section shall delete the consumer's personal information from its records and direct any service providers to delete the consumer's personal information from their records|Discover and respond|
-||1798.105(d)|(exceptions to 1798.105(c) <br> A business or a service provider shall not be required to comply with a consumer's request to delete the consumer's personal information if it's necessary for the business or service provider to maintain the consumer's personal information in order to: (refer to the current regulation for additional information).|Discover and respond|
-|||||
-
-> [!IMPORTANT]
-> This is not intended to be an exhaustive list. Refer to [Compliance Manager](../compliance/compliance-manager.md) or your legal or compliance advisor for further information on the applicability of the cited sections to the technical control categories listed.
-
-## Knowing your data
-
-Regardless of the regulations you're subject to, where different user data types inside and outside your organization interact with your systems are all important factors that may impact your overall personal data protection strategy, subject to the industry and government regulations that apply to your organization. This includes where personal data is stored, what type it is, and how much of it there is, and under what circumstances it was collected.
-
-![Knowing your data: What type it is, and how much of it there is, and under what circumstances it was collected.](../media/information-protection-deploy-assess/information-protection-deploy-assess-knowing-data.png)
-
-### Data portability
-
-Data also moves around over time as it is processed, refined, and other versions are derived from it. An initial snapshot is never enough. There needs to be an ongoing process for knowing your data. This represents one of the biggest challenges for large organizations that handle significant volumes of personal data. Organizations that don't address the "know your data" problem could potentially end up with very high risk and possible fines from regulatory agencies.
-
-![The data lifecycle.](../media/information-protection-deploy-assess/information-protection-deploy-assess-data-lifecycle.png)
-
-### Where the personal data is
-
-To address data privacy regulations, you can't rely on general notions of where you think personal data might exist, either now or in the future. Data privacy regulations require that organizations prove that they know where personal data is on an ongoing basis. This makes it important to take an initial snapshot of all your data sources for possible storage of personal information, including your Microsoft 365 environment, and establish mechanisms for ongoing monitoring and detection.
-
-If you haven't already assessed your overall readiness and risk associated with data privacy regulations, use the following 3-step framework to get started.
-
-![Steps to assess your overall readiness and risk associated with data privacy regulations.](../media/information-protection-deploy-assess/information-protection-deploy-assess-grid.png)
-
-> [!NOTE]
-> This article and its content are not meant to take the place of legal advisory services. It just provides some basic guidance and links to tools that may be of assistance in the early stages of your assessment.
-
-## Step 1: Develop a foundational understanding of your organization's personal data scenarios
-
-You need to gauge exposure to data privacy risk based on the type of personal data it currently manages, where it's stored, what protective controls are placed on it, how its lifecycle is managed, and who has access to it.
-
-As a starting point, it's important to inventory what types of personal data exist in your Microsoft 365 environment. Use these categories:
--- Employee data required to carry out day-to-day business functions-- Data the organization has about its business customers, partners, and other relationships in the business-to-business (B2B) scenario-- Data the organization has about consumers who provide information to online services that the organization manages in the business-to-customer (B2C) scenario-
-Here's an example of the different types of data for typical departments of an organization.
-
-![Types of personal data.](../media/information-protection-deploy-assess/information-protection-deploy-assess-data-types.png)
-
-Much of the personal data that is subject to data privacy regulation is typically collected and stored outside of Microsoft 365. Any personal data from consumer-facing web or mobile applications would need to have been exported from such applications to Microsoft 365 in order to be subject to data privacy scrutiny within Microsoft 365.
-
-Your data privacy exposure in Microsoft 365 may be more limited relative to your web applications and CRM systems, which this solution doesn't address.
-
-It's also important to think about the following common data privacy compliance challenges when evaluating your risk profile:
--- **Personal data distribution.** How scattered is information about a given subject? Is it known well enough to convince regulatory bodies that proper controls are in place? Can it be investigated and remediated if needed?-- **Protecting against exfiltration.** How do you protect personal data of a given type or source from being compromised and how to respond if it was?-- **Protection vs. risk.** What information protection mechanisms are appropriate relative to the risk and how to maintain business continuity and productivity and minimize end-user impact if end-user intervention is required? For example, should manual classification or encryption be used?-- **Personal data retention.** How long does information containing personal data need to be kept around for valid business reasons and how to avoid past keep-it-forever practices, balanced with retention needs for business continuity?-- **Handling data subject requests.** What mechanisms will be needed to handle data subject requests (DSRs) and any remedial actions, such as anonymization, redaction, and deletion?-- **Ongoing monitoring and reporting.** What sort of day-to-day monitoring, investigative, and reporting techniques are available for the different data types and sources?-- **Limitations on data processing.** Are there limitations on data use for information collected or stored through these methods that the organization must reflect in privacy controls? For example, commitments that personal data won't be used by sales personnel may require your organization to put mechanisms in place to prevent transfer or storage of that information in systems associated with the sales organization.-
-### Employee data required to carry out day-to-day business functions
-
-Organizations by nature need to collect data on employees for electronic identity and HR purposes, subject to what they agree to in their employee agreements. As long as a person works for a company, this is typically not an issue. The organization may want to put mechanisms in place to prevent malicious actors from exfiltration or leaking employee personal data.
-
-If a person leaves a company, organizations typically have processes, procedures, and retention and deletion schedules for removing user accounts, decommissioning mailboxes and personal drives, and changing the employee status in things like human resources systems. For situations where litigation is involved, an employee or another party to a legal investigation may have valid reasons for obtaining information about personal data stored in the organization's systems. On some occasions, that party may request that such data be removed or anonymized.
-
-To address such needs, organizations should have processes and procedures in place that address preventative, detective, and remedial needs to facilitate such requests, noting that some information about an employee may be reasonably considered crucial for business continuity. For example, information that an individual authored a file or performed a function.
-
-> [!NOTE]
-> For investigative and remediation techniques for personal data in Microsoft 365, see the [monitor and respond article](information-protection-deploy-monitor-respond.md). You may also want to employ automated classification and protection schemes to make sure that personal data is controlled while inside the organization, as well as prevent it from leaving the organization in malicious actor situations. See the [protect information article](information-protection-deploy-protect-information.md) for more information.
-
-### Data the organization has about its business customers in the B2B scenario
-
-Collection of B2B information is also a challenge because your organization might need to keep records of customer names and transactions in its various systems for business continuity purposes yet protect that information from inadvertent or malicious exfiltration. Like employee data, organizations must have policies, procedures, and technical controls in place to protect such data, as well as age it out according to defined retention and deletion schedules.
-
-Typically, contracts with external customers, partners, and the other entities with which the organization does business will have language addressing the handling of such data, including protection, retention, and deletion both during and after the entity has a relationship with the organization.
-
-### Data the organization has about consumers who provide information to online services that the organization manages in the B2C scenario
-
-This category is the one most people think about for data privacy, due to many public instances of customer data leakage. This can be intentional, such as a third party under contract to the provider, or unintentional, such as exfiltration by a malicious actor. Consumer data protection is one of the primary reasons the EU and others enacted these regulations. Data privacy regulations like GDPR and CCPA require you to do planning for:
--- [Action plans](/compliance/regulatory/gdpr-action-plan) and [accountability readiness checklists](/compliance/regulatory/gdpr-arc-Office365)-- [Data Protection Impact Assessments](/compliance/regulatory/gdpr-data-protection-impact-assessments)-- [Breach notifications](/compliance/regulatory/gdpr-breach-Office365)-- [Data subject requests](/compliance/regulatory/gdpr-dsr-Office365)-
-If your organization does not do a lot of direct-from-consumer data collection, this category may be less of an issue. However, you may still need to go through the processes outlined in these articles to achieve compliance.
-
-### Step 1 summary
-
-Understanding your exposure to risk and data privacy regulation is an important first step that is based on a foundational understanding of your organization's personal data scenarios.
-
-If you don't have personal data from consumers in your Microsoft 365 environment or it is confined to certain parts of the environment and the need for a technical control is predicated on there being consumer-type data exposure, then that technical control may only need to be employed in high risk parts of the environment, not everywhere.
-
-While an external organization or standard control set recommendation, such as from Compliance Manager in Microsoft 365, may help inform your control strategy, your choice of implementation should be driven by data inventory awareness to quantify your real risk exposure.
-
-Most organizations will have some exposure to one of the above scenarios. Taking a holistic approach to assessment is important.
-
-## Step 2: Assess your readiness for complying with data privacy regulations
-
-Although specific to GDPR, the questions posed in the free [Microsoft GDPR assessment tool](https://clouddamcdnprodep.azureedge.net/gdc/1863571/original) provide a good start towards understanding your overall data privacy readiness.
-
-Organizations subject to other data privacy regulations, such as CCPA in the United States or Brazil's LGPD, may also benefit from this tool's inventory of readiness due overlapping provisions with the GDPR.
-
-GDPR assessment consists of these sections:
-
-|Section|Description|
-|:-|:--|
-|Governance|<ol><li>Does your privacy policy explicitly state what data information is being processed? </li><li>Do you regularly run Privacy Impact Assessments (PIAs)? </li><li> Do you use a tool to manage personal information (PI)? </li><li> Do you have legal authority to conduct business using PI data on any given individual? Do you track consent for data? </li><li> Do you track, implement, and manage audit controls? Do you monitor for data leaks? </li></ol>|
-|Deletion and notification|<ol><li>Do you give explicit instructions on how users' data can be accessed? </li><li> Do you have documented processes in place for handling opt-out consent? </li><li> Do you have an Automated Deletion process for data? </li><li> Do you have a process to validate identity when engaging with a customer? </li></ol>|
-|Risk mitigation and information security|<ol><li>Do you use tools to scan unstructured data? </li><li>Are all servers up to date, and do you leverage firewalls to protect them? </li><li>Do you run regular backups of your servers? </li><li>Do you actively monitor for data leaks? </li><li>Do you encrypt your data at rest and in transmission? </li></ol>|
-|Policy management|<ol><li>How do you manage your Binding Corporate Rules (BCRs)? </li><li>Do you track consent for data? </li><li> On a scale of 1 to 5, 5 being completely covered, do your contracts cover data classifications and handling requirements? </li><li>Do you have and regularly test an incident response plan? </li><li>What policy do you use to manage access? </li></ol>|
-|||
-
-## Step 3: Identify sensitive information types that occur in your Microsoft 365 environment
-
-This step involves identification of particular sensitive information types that are subject to specific regulatory controls, as well as the occurrence of them in your Microsoft 365 environment.
-
-Finding content in your environment containing personal can be a formidable task, formerly involving a combination of using Compliance Search, eDiscovery, eDiscovery (Premium), DLP, and auditing.
-
-With the new **Data Classification** solution in the Microsoft Purview compliance portal, this has become much easier with the [Content Explorer](../compliance/data-classification-content-explorer.md) capability, which works with either built-in or custom sensitive information types, including those related to personal data.
-
-### Sensitive information types
-
-The Microsoft Purview compliance portal comes pre-loaded with over 100 sensitive information types, most of them related to identifying and locating personal data. These built-in sensitive information types can help identify and protect credit card numbers, bank account numbers, passport numbers, and more, based on patterns that are defined by a regular expression (regex) or a function. To learn more, see [What the sensitive information types look for](../compliance/sensitive-information-type-entity-definitions.md).
-
-If you need to identify and protect an organization-specific or regional type of sensitive items, such as a custom format for employee IDs, or other personal information not already covered by a built-in sensitive information type, you can create a custom sensitive information type with these methods:
--- Security & Compliance PowerShell-- Custom rules with exact data match (EDM)-- Through the Microsoft 365 Purview compliance portal, as highlighted in the [Use Compliance Score and Compliance Manager article](information-protection-deploy-compliance.md)-
-You can also customize an existing, built-in sensitive information type.
-
-See these articles for more information:
--- [Customize a built-in sensitive information type](../compliance/customize-a-built-in-sensitive-information-type.md)-- [Learn about sensitive information types](../compliance/sensitive-information-type-learn-about.md)-- [Create a custom sensitive information type in the Security & Compliance Center](../compliance/create-a-custom-sensitive-information-type.md)-- [Create a custom sensitive information type in Security & Compliance Center PowerShell](../compliance/create-a-custom-sensitive-information-type-in-scc-powershell.md)-- [Create custom sensitive information types with Exact Data Match based classification](/microsoft-365/compliance/sit-get-started-exact-data-match-based-sits-overview)-
-### Content Explorer
-
-An important tool that for determining the occurrence of sensitive items in your environment is the new [Content Explorer](../compliance/data-classification-content-explorer.md) in the Microsoft Purview admin center. It's an automated tool for initial and ongoing scanning of your entire Microsoft 365 subscription for the occurrence of sensitive information types and display of the results.
-
-The new Content Explorer tool allows you to quickly identify the locations of sensitive items in your environment, using either built-in sensitive information types or custom ones. This may involve establishing a process and assigned responsibility to regularly investigate the presence and location of sensitive items.
-
-Along with the other steps highlighted in this article, this provides a starting point for identifying your overall risk exposure, readiness, and location of sensitive items to protect through planned Microsoft 365 configuration and monitoring.
-
-### Other methods to identify personal data in your environment
-
-In addition to the Content Explorer, organizations have access to the Content Search capability to produce custom searches to find personal data in their environment, using advanced search criteria and custom filters.
-
-Detailed guidance on the use of Content Search for discovery of personal data is provided in [this article](/compliance/regulatory/gdpr). Content Search and other discovery techniques are also explored in [DSRs for the GDPR and CCPA](/compliance/regulatory/gdpr-dsr-Office365#introduction-to-dsrs).
-
-Additional insights on investigative and remediation techniques for personal data in Microsoft 365 are provided in the [monitor and respond article](information-protection-deploy-monitor-respond.md).
-
-> [!NOTE]
-> To Find what sensitive information you have in files stored on-premises, please refer to [Azure Information Protection](/azure/information-protection/quickstart-findsensitiveinfo).
solutions Information Protection Deploy Compliance https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/solutions/information-protection-deploy-compliance.md
- Title: "Use Compliance Manager to manage improvement actions"---- NOCSH- Previously updated : 09/29/2020----- highpri-- M365-security-compliance-- Strat_O365_Enterprise-- m365solution-infoprotection-- m365solution-scenario-- zerotrust-solution-
-description: Learn how to use Compliance Score and Compliance Manager to improve your level of protection for personal data.
--
-# Use Compliance Manager to manage improvement actions
-
-Microsoft Purview Compliance Manager can help you manage improvements related to data privacy regulations such as the European Union [General Data Protection Regulation (GDPR)](/compliance/regulatory/gdpr), [California Consumer Protection Act CCPA)](/compliance/regulatory/ccpa-faq), HIPAA-HITECH (US health care privacy act), and the Brazil Data Protection Act (LGPD).
-
-This article provides guidance on the use of this tool for data privacy purposes.
-
-> [!NOTE]
-> Recommendations from Compliance Manager should not be interpreted as a guarantee of compliance. It is up to you to evaluate and validate the effectiveness of customer controls per your regulatory environment. These services are subject to the terms and conditions in the [Online Services Terms](https://go.microsoft.com/fwlink/?linkid=2108910). See also [Microsoft 365 licensing guidance for security and compliance](/office365/servicedescriptions/microsoft-365-service-descriptions/microsoft-365-tenantlevel-services-licensing-guidance/microsoft-365-security-compliance-licensing-guidance#compliance-manager)
-
-## Getting started with Compliance Manager
-
-#### What is Compliance Manager
-
-[Compliance Manager](../compliance/compliance-manager.md) is a workflow-based risk assessment tool in the Microsoft Purview compliance portal for managing regulatory compliance activities related to Microsoft cloud services. As part of your Microsoft 365 or Azure Active Directory (Azure AD) subscription, Compliance Manager helps you manage regulatory compliance within the shared responsibility model for Microsoft cloud services.
-
-**Ready to use assessments**
-
-Compliance Manager provides pre-built templates for [building assessments](../compliance/compliance-manager-assessments.md) that are aligned to data privacy-related regulations, such as GDPR and HIPAA/HITECH. The templates have built-in control mapping to help you take improvement actions for meeting the regulation's requirements. Each assessment provides information about the controls each regulation calls for specific to the target service, broken out by controls you manage and controls Microsoft manages.
-
-Using a pre-built template helps you quickly get started with risk assessments. As you become more proficient in using Compliance Manager, you can customize a pre-built template by adding your own controls and improvement actions, or you can create your own custom assessments to suit your organization's needs.
-
-View the [full list of assessment templates](../compliance/compliance-manager-templates-list.md) provided by Compliance Manager.
-
-**Real-time compliance score**
-
-Compliance Manager also provides you with a compliance score that measures your progress in completing recommended improvement actions within controls. You can use this score to help monitor your progress and prioritize actions based on their potential to reduce risk.
-
-#### Use the Compliance Manager quickstart guide
-
-The [Compliance Manager quickstart](../compliance/compliance-manager-quickstart.md) guide provides graduated steps and links to key resources to help you work with Compliance
--- [First visit: get familiar with Compliance Manager](../compliance/compliance-manager-quickstart.md#first-visit-get-to-know-compliance-manager)
- - Working with your Compliance Manager dashboard
- - Understanding your compliance score
- - Learning about improvement actions
- - Understanding assessments and templates
-- [Ramping up: configure Compliance Manager to manage your compliance activities](../compliance/compliance-manager-quickstart.md#ramping-up-configure-compliance-manager-to-manage-your-compliance-activities)
- - Building and managing your first assessment
- - Performing implementation and testing work on improvement actions to complete controls in your assessments
- - Understanding how different actions impact your compliance score
-- [Scaling up: use advanced functionality to meet your custom needs](../compliance/compliance-manager-quickstart.md#scaling-up-use-advanced-functionality-to-meet-your-custom-needs)
- - Creating your custom assessments to track non-Microsoft 365 products
- - Modifying existing templates to add or remove controls
- - Setting up automated testing of improvement actions
-
-## How your compliance score is calculated
-
-Your compliance score is calculated based on a combination of Microsoft and customer-managed control implementations. See [compliance score calculation](../compliance/compliance-score-calculation.md) for a detailed explanation.
-
-Controls are assigned a score value based on whether they're mandatory or discretionary, and whether they're preventative, detective, or corrective. These collectively represent the risk of not implementing it relative to other controls.
-
-As presented in the compliance score calculation article, preventative controls get a higher score than detective and corrective ones, and mandatory controls get a higher score than discretionary ones.
-
-The Compliance Score admin UI does not list these parameters, nor does it provide the ability to filter by them. However, if you download the associated template from Compliance Manager, the resulting data set does list these parameters for most regulations.
-
-For technical controls, Compliance Manager automatically updates the improvement action score once the action has been successfully implemented and tested. Other, non-technical control actions&mdash;such as those that are operational or related to documentation&mdash;need to be recorded manually as implemented before points count toward your score.
-
-You many also be implementing certain improvement actions for other purposes&mdash;for example using retention labels for reasons other than data privacy regulation compliance&mdash;so you would get credit for using such a feature even if it is being used for other purposes, and not part of a deliberate compliance action.
-
-Your compliance score should be considered a relative measure to track improvement on a broad scale. You should not pursue a perfect score.
-
-## Additional guidance
-
-Here are a few important tips for using Compliance Manager to help you achieve data privacy regulation compliance:
--- Each data privacy regulation has a combination of technical controls, documentation specifications, and operational, process, and reporting requirements. All of these show up in the improvement actions.--- To focus the view of improvement actions to your area of interest, you can filter by action type in the **Solutions** tab in the Compliance Manager admin. Learn more about [filtering your Compliance Manager dashboard view](../compliance/compliance-manager-setup.md#filtering-your-dashboard-view).--- The relative importance and priority of improvement actions identified in Compliance Manager should be considered as part of a broader risk review along with the data privacy risk you've determined your organization needs to manage.--- Even with improvement action aggregation across multiple regulatory requirements, if the regulation assessment templates for GDPR, LGPD, CCPA, and HIPAA-HITECH are selected, for example, almost 400 improvement actions will be listed in Compliance Manager. To better tackle this long list, use the improvement action filter to reduce the result set to a more manageable list.--- The Categories filter provides a means to filter improvement actions by logical grouping, which the Track, Prevent, Protect, Retain, and Investigate articles in this overall solution align to.--- Some of the controls listed in the improvement actions may be considered more directly tied to a specific regulatory article, while other controls may be more indirectly associated with the spirit of a regulation and many times are simply recommended activities or best practices.
solutions Information Protection Deploy Govern https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/solutions/information-protection-deploy-govern.md
- Title: "Govern information subject to data privacy regulation"---- NOCSH- Previously updated : 06/09/2020----- highpri-- M365-security-compliance-- Strat_O365_Enterprise-- m365solution-infoprotection-- m365solution-scenario-- zerotrust-solution-
-description: Use Microsoft 365 retention labels and policies to manage personal data in your Microsoft 365 environment.
--
-# Govern information subject to data privacy regulation
-
-Information governance controls can be employed in your environment to help address data privacy compliance needs, including a number that are specific to General Data Protection Regulation (GDPR), HIPAA-HITECH (the United States health care privacy act), California Consumer Protection Act (CCPA), and the Brazil Data Protection Act (LGPD).
-
-These controls primarily fall into the following solution areas:
--- Retention policies-- Retention labels-- Records management-
-## Data privacy regulations impacting information governance controls
-
-Here is a sample listing of data privacy regulations that may relate to information governance controls:
--- GDPR Article (13)(2)(a)-- GDPR Article (5)(1)(f)-- HIPAA-HITECH (45 CFR 164.312(c)(2))-- HIPAA-HITECH (45 CFR 164.316(b)(1)(i))-- HIPAA-HITECH (45 CFR 164.316(b)(1)(ii))-- LGPD Article 46-
-For more information on these regulations, see the [assess data privacy risks and identify sensitive information article](information-protection-deploy-assess.md).
-
-For information governance, data privacy regulations typically call for the following:
--- You should employ a technical scheme for retention and deletion for personal data stored in Microsoft 365.-- If you're going to store personal data, inform the subject of how long the data will be stored, which is a standard practice now on front-end web systems.-- Personal data should be protected against accidental processing, loss, or alteration using verifiable methods.-- Any action executed against personal data should be documented and that documentation should be retained for a specified period.-
-Because the data privacy regulations are not very specific when it comes to data retention and deletion, other factors need to be taken into consideration that may dictate information governance guidelines for personal information stored in your Microsoft 365 subscription. Here are a few examples:
--- Aging out consumer accounts after 5 years of inactivity and requires deletion or anonymization of account data after that point, requiring orchestration between the system storing the data and workflows related to notifications and other automation.-- Configuring rules for keeping policies and procedures related to GDPR around for three years after they've been superseded, which aligns with the organization's retention schedule for policies and procedures.-- Maintaining a separate subscription for communicating with consumers through its support organization. All email communications were retained and deleted after two weeks to reduce any privacy debt buildup in the system.-
-A key question to answer is:
--- How long does information containing personal data need to be kept around for valid business reasons to avoid "keep it forever" practices? This must be balanced with retention needs for business continuity.-
-Regardless of the legal and business reasons for keeping personal information around or deleting it, Microsoft provides a number of capabilities to implement your data governance scheme in Microsoft 365.
-
-## Managing information governance in Microsoft 365
-
-To begin, see [Govern your data with Microsoft Purview](../compliance/manage-data-governance.md) and [Data Retention, Deletion and Destruction in Microsoft 365](/office365/Enterprise/office-365-data-retention-deletion-and-destruction-overview).
-
-### Develop data retention schedules for containers, email, and content
-
-Keep the following in mind:
--- Establishing a data retention schedule for defined information types should be considered a prerequisite to implementing any retention or deletion scheme.--- Given the number of information types that most organizations consider important and the corresponding large records retention schedules that go along with them, implementing a data retention and records management strategy requires planning. --- The key to establishing an effective data governance strategy of this type is to focus on the highest priority business functions and information types that require more formal management. Examples are legal contracts, financial statements, and regulatory compliance documentation. Try to avoid having a separate retention schedule for every single information type. Try to utilize general categories as much as possible, for example, with retention schedules of 7 years for general business content.--- Once the personal information types in your environment are better known, establish retention and deletion schedules for this type of content and adjust your information architecture to make governance of this sort of information easier. For example, isolate personal information in separate sites, libraries, or folders with controlled access.-
-### Retention policies and retention labels
-
-Use [retention policies and retention labels](../compliance/retention.md) to retain or delete content in Microsoft 365 that contains or is expected to contain personal data.
-
-### Records management
-
-Use retention labels that declare content a record to implement a [records management solution](../compliance/records-management.md) for data in Microsoft 365.
-
-For data privacy, data subject requests (DSRs) received by the legal department are declared a record and can be stored indefinitely or disposed of with proof, to adhere to regulatory activity retention specifications.
solutions Information Protection Deploy Identity Device Threat https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/solutions/information-protection-deploy-identity-device-threat.md
- Title: "Use identity, device, and threat protection for data privacy regulation"---- NOCSH- Previously updated : 06/09/2020----- highpri-- M365-security-compliance-- Strat_O365_Enterprise-- m365solution-infoprotection-- m365solution-scenario-- zerotrust-solution-
-description: Prevent personal data breaches with identity, device, and threat protection services of Microsoft 365.
--
-# Use identity, device, and threat protection for data privacy regulation
-
-Microsoft 365 provides a number of identity, device, and threat protection capabilities that organizations can employ to help comply with data privacy-related compliance regulations. This article describes what the data privacy regulations require in these areas and provides a listing of related Microsoft 365 features and services with links to more information to help you address implementation requirements.
-
-## How identity, device, and threat protection relate to data privacy regulation
-
-While the data privacy regulations vary in their specificity, the essence of what they call for is embodied in the GDPRΓÇÖs Article 5(1)(f), which states that:
--- Personal data shall be processed in a manner that ensures appropriate security of the personal data, including protection against unauthorized or unlawful processing and against accidental loss, destruction or damage, using appropriate technical or organizational measures ('integrity and confidentiality').-
-Because personal data breaches are often caused by administrative or end-user account compromise and malicious system access. For example, an admin account hack can result in exfiltration of customer credit card numbers or other personal information. All the generally advisable identity, device, and threat protection available with Microsoft 365 potentially should be implemented, which will be reflected in your compliance score, found in Compliance Manager.
-
-## Using the results of your assessment work and Compliance Manager
-
-Compliance Manager includes identity, device, and threat protection using these categories:
--- Identity corresponds to the **Control Access** category-- Device corresponds to the **Manage Devices** category-- Threat protection corresponds to the **Protect Against Threats** category
-
-If these are selected across our sample set of four major data privacy regulations, Compliance Manager specifies 90 improvement actions, most of which are scored a "27". Since such a large number are called out by Compliance Manager for these categories, some of the more common ones are listed here, for reference.
-
-Use [Azure Active Directory (Azure AD)](https://azure.microsoft.com/services/active-directory/) for identity and the **Control Access** category, with which you can:
--- Implement replay-resistant authentication (to prevent ΓÇ£Man in the middleΓÇ¥ attacks)-- Block legacy authentication.-- Configure user risk and user sign-in risk policies.-- Enable Conditional Access and multi-factor authentication (MFA) for admins and non-admins.-- Configure and enforce password policies.-- Restrict access to privileged accounts with Azure AD Privileged Identity Management.-- Disable access upon termination.-- Audit user accounts and status changes.-- Review role group and administrative changes.-
-Use [Microsoft Endpoint Manager](https://www.microsoft.com/microsoft-365/microsoft-endpoint-manager) for devices and the **Manage Devices** category, with which you can:
--- Block jail broken and rooted mobile devices.-- Configure Intune for mobile device management.-- Create compliance policies for Android, iOS, macOS and Windows devices.-- Create a device configuration profile for Android, iOS, macOS and Windows devices.-- Create app protection policies for iOS and Windows.-- Conceal information with lock screen.-- Implement password policies for mobile devices.-- Require mobile devices to lock upon inactivity.-- Require mobile devices to wipe on multiple sign-in failures.-
-Use [Exchange Online Protection and Microsoft Defender for Office 365](../security/office-365-security/defender-for-office-365.md) for the **Protect Against Threats** category, with which you can:
--- Enable sender authentication (SPF, DMARC and DKIM).-- Set up Microsoft Defender for Office 365 anti-phishing policies.-- Implement Safe Attachments.-- Implement Safe Links.-- Implement malware detection and response policies.-- Implement outbound and inbound spam policies.-
-### References:
--- [Common identity and device access policies](../security/office-365-security/identity-access-policies.md)-- [Protect against threats in Office 365](https://support.office.com/article/protect-against-threats-in-office-365-b10023f6-f30f-45d3-b3ad-b71aa4aa0d58)-- [Safe Attachments](../security/office-365-security/safe-attachments-about.md)-- [Safe Links](../security/office-365-security/safe-links-about.md)-- [Safe Documents](../security/office-365-security/safe-documents-in-e5-plus-security-about.md)
solutions Information Protection Deploy Monitor Respond https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/solutions/information-protection-deploy-monitor-respond.md
- Title: "Monitor and respond to data privacy incidents in your organization"---- NOCSH- Previously updated : 01/04/2021----- highpri-- M365-security-compliance-- Strat_O365_Enterprise-- m365solution-infoprotection-- m365solution-scenario-- zerotrust-solution-
-description: Use auditing and alert policies and data subject requests to monitor and respond to personal data incidents.
--
-# Monitor and respond to data privacy incidents in your organization
-
-Microsoft 365 features are available to help you monitor, investigate, and respond to data privacy incidents in your organization as you operationalize related capabilities. Having processes, procedures, and other documentation for each of these may also be important to demonstrate compliance to regulatory bodies.
-
-These include:
--- Auditing and alert policies-- Data subject requests (including content search and eDiscovery)-- Additional investigative tools and reporting-
-## Data privacy regulations impacting the use of monitoring and response tools
-
-Here is a sample listing of data privacy regulations that may relate to information governance controls:
--- LGPD Article 46-- LGPD Article 48-- GDPR Article (5)(1)(f)-- GDPR Article (15)(1)(e)-- HIPAA-HITECH (45 C.F.R. 164.308(a)(1)(ii)(D))-- HIPAA-HITECH (45 C.F.R. 164.308(a)(6)(ii)-- HIPAA-HITECH (45 C.F.R. 164.312(b))-- CCPA (1798.105(c))-
-For more information, see [Assess data privacy risks and identify sensitive information](information-protection-deploy-assess.md).
-
-The data privacy regulations generally call for the following for monitoring and response:
--- Auditing, alerting, and reporting for activities related to the storage, sharing and processing of personal data-- The ability to respond to a data subject request (DSR) and in some cases, perform investigative and other administrative measures to comply with such requests.-
-Your organization may also wish to perform monitoring and response activities for other purposes, such as other compliance needs or for business reasons. Establishing your monitoring and response scheme for data privacy should be done as part of overall monitoring and response planning, implementation, and management.
-
-To help you get started with a monitoring and response scheme in Microsoft 365 for data privacy regulations, this article lists useful capabilities in Microsoft 365 to answer questions such as:
--- What sort of day-to-day monitoring, investigative and reporting techniques are available for the different data types and sources?-- What mechanisms will be needed to handle data subject requests (DSRs) and any remedial actions, such as anonymization, redaction, and deletion.-
-## Auditing and Alert Policies in the Microsoft Purview compliance portal
-
-See these articles for setting up auditing, advanced auditing, and alert policies:
--- [Unified auditing](../compliance/search-the-audit-log-in-security-and-compliance.md)-- [Mailbox auditing](../compliance/enable-mailbox-auditing.md)-- [Audit (Premium)](../compliance/advanced-audit.md)-- [Alert policies](../compliance/alert-policies.md)-
-## Data subject requests for the GDPR and CCPA
-
-See [Data Subject Requests for the GDPR and CCPA](/compliance/regulatory/gdpr-dsr-Office365) for information on responding to a DSR in Microsoft 365.
-
-## Manage deleted users in Microsoft Stream
-
-For Microsoft Stream, when a user is deleted from Azure Active Directory (Azure AD), if their name was associated with a posted Stream video prior to that point, their email address remains associated with the video. See [Manage deleted users from Microsoft Stream](/stream/managing-deleted-users) to remove it.
-
-## Insider risk management as an investigative tool
-
-[Insider risk management](../compliance/insider-risk-management.md) is a feature of the Microsoft Purview compliance portal to help you minimize internal risk by enabling you to detect, investigate, and take action on risky activities in your organization.
solutions Information Protection Deploy Protect Information https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/solutions/information-protection-deploy-protect-information.md
- Title: "Protect information subject to data privacy regulation"---- NOCSH- Previously updated : 06/09/2020----- highpri-- M365-security-compliance-- Strat_O365_Enterprise-- m365solution-infoprotection-- m365solution-scenario-- zerotrust-solution-
-description: Deploy Microsoft 365 security and compliance features and protect your personal information.
--
-# Protect information subject to data privacy regulation
-
-A number of information protection controls can be employed in your subscription to help address data privacy compliance needs and regulations. These include General Data Protection Regulation (GDPR), HIPAA-HITECH (the United States health care privacy act), California Consumer Protection Act (CCPA), and the Brazil Data Protection Act (LGPD).
-
-These controls are within following solution areas:
--- Sensitivity labels-- Microsoft Purview Data loss prevention (DLP)-- Microsoft Purview Message Encryption-- Teams and sites access controls-
-![Key services to protect personal information subject to data privacy regulation.](../media/information-protection-deploy-protect-information/information-protection-deploy-protect-information-grid.png)
-
-> [!NOTE]
-> This solution describes security and compliance features to protect information subject to data privacy regulations. For a complete list of security features in Microsoft 365, see [Microsoft 365 security documentation](../security/index.yml). For a complete list of compliance features in Microsoft 365, see [Microsoft Purview documentation](../compliance/index.yml).
-
-## Data privacy regulations that impact information protection controls
-
-Here is a sample list of data privacy regulations that may relate to information protection controls:
--- GDPR Article 5(1)(f))-- GDPR Article (32)(1)(a)-- LGPD Article 46-- HIPAA-HITECH (45 CFR 164.312(e)(1))-- HIPAA-HITECH (45 C.F.R. 164.312(e)(2)(ii))-
-See the [assess data privacy risks and identify sensitive items article](information-protection-deploy-assess.md) for more information on each of the above.
-
-Data privacy regulations for information protection recommend:
--- Protection against loss or unauthorized access, usage and/or transmission.-- Risk-based application of protective mechanisms.-- Use of encryption where appropriate.-
-Your organization may also want to protect Microsoft 365 content for other purposes, such as other compliance needs or for business reasons. Establishing your information protection scheme for data privacy should be done as part of overall information protection planning, implementation, and management.
-
-To help you get started with an information protection scheme in Microsoft 365, the following section includes a short list of related capabilities and improvement actions for Microsoft 365. The list includes capabilities and improvement actions that are applicable to data privacy regulations. However, the list doesn't include older technologies if there's a newer capability that largely supersedes the older one. For example, Information Rights Management (IRM) for SharePoint and OneDrive is not included in the list but sensitivity labels are included.
-
-## Managing information protection in Microsoft 365
-
-Microsoft [information protection solutions](../compliance/information-protection.md) include a number of integrated capabilities across Microsoft 365, Microsoft Azure, and Microsoft Windows. In Microsoft 365, information protection solutions include:
--- [Sensitive information types](../compliance/sensitive-information-type-entity-definitions.md) (described in the [assess data privacy risks and identify sensitive items article](information-protection-deploy-assess.md)-- [Sensitivity labels](../compliance/sensitivity-labels.md)
- - Service/container-level
- - Client-side/content-level
- - Automated for data-at-rest in SharePoint and OneDrive
-- Data Loss Prevention (DLP)-- [Endpoint data loss prevention](../compliance/endpoint-dlp-learn-about.md)-- [Office 365 Message Encryption new capabilities (OME)](../compliance/ome.md) and OME [Advanced Message Encryption](../compliance/ome-advanced-message-encryption.md)-
-In addition, site and library level protection are important mechanisms to include in any protection scheme.
-
-For information on other information protection capabilities outside of Microsoft 365, see:
--- [Microsoft Defender for Cloud Apps](/cloud-app-security/)-- [Azure Information Protection](/azure/information-protection/what-is-information-protection)-- [Microsoft Endpoint Manager](https://www.microsoft.com/microsoft-365/microsoft-endpoint-manager)-- [Windows Information Protection](/windows/security/information-protection/windows-information-protection/protect-enterprise-data-using-wip)-
-## Sensitivity labels
-
-Sensitivity labels from Microsoft Purview Information Protection let you classify and protect your organization's data without hindering the productivity of users and their ability to collaborate.
-
-> [!div class="mx-imgBorder"]
-> ![Sensitivity labels in Microsoft 365.](../media/information-protection-deploy-protect-information/information-protection-deploy-protect-information-labels.png)
-
-### Prerequisites for sensitivity labels
-
-Complete these activities prior to implementing any of the sensitivity label-based capabilities highlighted below:
-
-1. Understand the following:
- - **Business requirements.** Establish the business reasons for applying sensitivity labels in your enterprise. For example, your data privacy requirements for information protection.
- - **Sensitivity label capabilities.** Sensitivity labeling can get complex, so make sure to read the [sensitivity labels documentation](../compliance/sensitivity-labels.md) before getting started.
- - **Key things to remember** Sensitivity labels are managed in the Microsoft Purview compliance portal but the targeting and application options vary significantly.
- - There are sensitivity labels for sites, groups, and Teams at the container level (the settings do not apply to content inside the container). These are published to users and groups who apply them when a site, group or Team is provisioned.
- - There are sensitivity labels for active content. These are also published to user or groups, who either manually apply them, or they get applied automatically when:
- - The file is opened/edited/saved, either to the userΓÇÖs desktop or a SharePoint site.
- - An email is drafted and sent.
- - There are sensitivity labels for automatic application to files at rest in SharePoint and OneDrive in addition to emails in transit through Exchange. These are targeted to either all sites or specific ones and automatically apply to the files at rest in these environments.
-
-2. Rationalize current sensitivity labeling with past or alternative methods
-
- - Azure Information Protection
-
- The current sensitivity labeling scheme may need to be reconciled with any existing [Azure Information Protection](../compliance/sensitivity-labels.md#sensitivity-labels-and-azure-information-protection) labeling implementation.
- - OME
-
- If you are planning to use modern sensitivity labeling for email protection and existing email encryption methods like OME are in place, they can co-exist, but you should understand the scenarios in which either should be applied. See [Office 365 Message Encryption new capabilities (OME)](#office-365-message-encryption-ome-new-capabilities), which includes a table comparing modern sensitivity label-type protection with OME-based protection.
-
-3. Plan for integration into a broader information protection scheme. On top of coexistence with OME, sensitivity labels can be used along-side capabilities like Microsoft Purview Data Loss Prevention (DLP) and Microsoft Defender for Cloud Apps. See [Protect your data with Microsoft Purview](../compliance/information-protection.md) to achieve your data privacy-related information protection goals.
-
-4. Develop a sensitivity label classification and control scheme. See [Data Classification and Sensitivity Label Taxonomy](https://aka.ms/dataclassificationwhitepaper).
-
-### General guidance
-
-1. **Schema definition.** Before using technical capabilities to apply labels and protection, work across your organization to define a classification schema. You might already have a classification schema, which makes it easier to add personal data.
-2. **Getting started.** Begin by deciding on the number and names of labels to implement. Do this activity without worrying about which technology to use and how labels will be applied. Apply this schema universally throughout your organization, including data that resides on premises and in other cloud services.
-3. **Additional recommendations** When designing and implementing policies, labels, and conditions, consider following these recommendations:
-
- - **Use existing classification schema (if any).** Many organizations already are using data classification in some form. Carefully evaluate the existing label schema and if possible, use it as is. Using familiar labels that are recognizable to your end-users will drive adoption.
- - **Start small.** There is virtually no limit to the number of labels that you can create. However, large numbers of labels and sub-labels can slow adoption.
- - **Use scenarios and use cases.** Identify common use cases within your organization and use scenarios derived from the data privacy regulations to which you are subject. Verify if the envisioned label and classification configuration will work in practice.
- - **Question every request for a new label.** Does every scenario or use case really need a new label or can you use what you already have? Keeping the number of labels to a minimum improves adoption.
- - **Use sub-labels for key departments.** Some departments will have specific needs that require specific labels. Define these labels as sub-labels to an existing label and consider using scoped policies that are assigned to user groups instead of globally.
- - **Consider scoped policies.** Policies targeted at subsets of users will prevent label overload. A scoped policy enables assigning role or department specific labels or sub-labels to just employees that work for that specific department.
- - **Use meaningful label names.** Try not to use jargon, standards, or acronyms as label names. Try to use names that resonate with the end user to improve adoption. Instead of using labels like PII, PCI, HIPAA, LBI, MBI and HBI, consider names like Non-Business, Public, General, Confidential and Highly Confidential.
-
-### Create and deploy sensitivity labels for sites, groups, and teams
-
-When you create [sensitivity labels](../compliance/sensitivity-labels-teams-groups-sites.md) in the <a href="https://go.microsoft.com/fwlink/p/?linkid=2077149" target="_blank">Microsoft Purview compliance portal</a>, you can now apply them to these containers:
--- Microsoft Teams sites-- Microsoft 365 groups (formerly Office 365 groups)-- SharePoint sites-
-Use the following label settings to help protect the content in those containers:
--- Privacy (public or private) of Microsoft 365 group-connected Teams sites-- External user access-- Access from unmanaged devices-
-For data privacy, to prevent external sharing for containers that will be used for storing content with sensitive personal data, mark the files containing the data as private, and require managed devices.
-
-### Create and deploy sensitivity labels for content
-
-Sensitivity labels applied to files allow you to encrypt their content, watermark the content, and define other controls for Office applications content, including Outlook and Office on the web.
-
-When you're ready to start protecting your organization's data with sensitivity labels:
-
-1. **Create the labels.** Create and name your sensitivity labels according to your organization's classification taxonomy for different sensitivity levels of content. For more information on developing a classification taxonomy, see the [Data Classification and Sensitivity Label Taxonomy white paper](https://aka.ms/dataclassificationwhitepaper).
-2. **Define what each label can do.** Configure the protection settings you want associated with each label. For example, you might want lower sensitivity content (such as a "General" label) to have just a header or footer applied, while higher sensitivity content (such as a "Confidential" label) should have a watermark and have encryption enabled.
-3. **Publish the labels.** After your sensitivity labels are configured, publish them by using a label policy. Decide which users and groups should have the labels and what policy settings to use. A single label is reusable. You define it once and then you can include it in several label policies assigned to different users.
-
-Once you publish sensitivity labels from the <a href="https://go.microsoft.com/fwlink/p/?linkid=2077149" target="_blank">Microsoft Purview compliance portal</a>, they start to appear in [Office apps](../compliance/sensitivity-labels-office-apps.md) for users to classify and protect content as it's created or edited.
-
-![Sensitivity label deployment flow in Microsoft 365.](../media/information-protection-deploy-protect-information/information-protection-deploy-protect-information-label-flow.png)
-
-For data privacy, you manually apply a sensitivity label with encryption and other rules to email or content containing sensitive personal information.
-
-> [!NOTE]
-> Sensitivity labels with encryption enabled applied to email have some overlapping functionality with OME. See [Secure email scenarios comparison with OME and sensitivity labels](#secure-email-scenarios-comparison-with-ome-and-sensitivity-labels).
-
-### Client-side auto-labeling when users edit documents or compose emails
-
-When you create a sensitivity label, you can [automatically assign that label](../compliance/apply-sensitivity-label-automatically.md) to content including email when it matches conditions that you specify.
-
-The ability to apply sensitivity labels to content automatically is important because:
--- You don't need to train your users when to use each of your classifications.-- You don't need to rely on users to classify all content correctly.-- Users no longer need to know about your policiesΓÇöthey can instead focus on their work.-
-Auto-labeling supports recommending a label to users, as well as automatically applying a label. But in both cases, the user decides whether to accept or reject the label, to help ensure the correct labeling of content.
-
-This client-side labeling has minimal delay for documents because the label can be applied even before the document is saved. However, not all client apps support auto-labeling. This capability is supported by the Azure Information Protection unified labeling client, and [some versions of Office apps](../compliance/sensitivity-labels-office-apps.md#support-for-sensitivity-label-capabilities-in-apps).
-
-For configuration instructions, see [How to configure auto-labeling for Office apps](../compliance/sensitivity-labels-office-apps.md#support-for-sensitivity-label-capabilities-in-apps).
-
-For data privacy, you auto-apply sensitivity labels for content containing sensitive personal information.
-
-### Service-side auto-labeling when content is already saved
-
-This method is referred to as auto classification with sensitivity labels. You might also hear it referred to as auto-labeling for data at rest (for documents in SharePoint and OneDrive) and data in transit (for email that is sent or received by Exchange). For Exchange, it doesn't include emails in mailboxes at rest.
-
-Because this labeling is applied by the service itself rather than by user application, you don't need to worry about what apps users have and what version. As a result, this capability is immediately available throughout your organization and suitable for labeling at scale. Auto-labeling policies don't support recommended labeling because the user doesn't interact with the labeling process. Instead, the administrator runs the policies in simulation mode to help ensure the correct labeling of content before actually applying the label.
-
-For configuration instructions, see [How to configure auto-labeling policies for SharePoint, OneDrive, and Exchange](../compliance/apply-sensitivity-label-automatically.md#how-to-configure-auto-labeling-policies-for-sharepoint-onedrive-and-exchange).
-
-For data privacy within sites of concern, push sensitivity labels for automatic encryption of content containing sensitive personal information.
-
-## Data loss prevention
-
-You can use [data loss prevention (DLP)](../compliance/dlp-learn-about-dlp.md) in Microsoft Purview to detect, warn, and block risky, inadvertent, or inappropriate sharing, such as sharing of data containing personal information, both internally and externally.
-
-DLP allows you to:
--- Identify and monitor risky sharing activities.-- Educate users with in-context guidance to make the right decisions.-- Enforce data use policies upon content without inhibiting productivity.-- Integrate with classification and labeling to detect and protect data when it is shared.-
-### Supported workloads for DLP
-
-With a DLP policy in the <a href="https://go.microsoft.com/fwlink/p/?linkid=2077149" target="_blank">Microsoft Purview compliance portal</a>, you can identify, monitor, and automatically protect sensitive items across many locations in Microsoft 365, such as Exchange Online, SharePoint, OneDrive, and Microsoft Teams.
-
-For example, you can identify any document containing a credit card number that's stored in any OneDrive site, or you can monitor just the OneDrive sites of specific people.
-
-You can also monitor and protect sensitive items in the locally-installed versions of Excel, PowerPoint, and Word, which include the ability to identify sensitive items and apply DLP policies. DLP provides continuous monitoring when people share content from these Office apps.
-
-> [!div class="mx-imgBorder"]
-> ![Supported workloads for DLP.](../media/information-protection-deploy-protect-information/information-protection-deploy-protect-information-supported-workloads.png)
-
-This figure shows an example of DLP protecting personal data.
-
-> [!div class="mx-imgBorder"]
-> ![Example of protecting personal data using DLP.](../media/information-protection-deploy-protect-information/information-protection-deploy-protect-information-dlp-example-use.png)
-
-DLP is used to identify a document or email containing a health record and then automatically blocks access to that document or blocks the email from being sent. DLP then notifies the recipient with a policy tip and sends an alert to the end-user and admin.
-
-### Planning for DLP
-
-See, [Plan for data loss prevention (DLP)](../compliance/dlp-overview-plan-for-dlp.md) for complete guidance on planning your DLP implementation
-
-<!-- Plan your DLP policies for:
--- Your business requirements.--- A risk-based assessment of the organization as described in the [assess data privacy risks and identify sensitive items article](information-protection-deploy-assess.md).--- Other information protection and governance mechanisms in place or in planning for data privacy.--- The sensitive information types that youΓÇÖve identified for personal data based on your assessment work as described in the [assess data privacy risks and identify sensitive items article](information-protection-deploy-assess.md). DLP policy conditions can be based on both sensitive information types and retention labels.--- The retention labels you'll need to specify DLP conditions. See the [govern information subject to data privacy regulation in your organization](information-protection-deploy-govern.md) article for more information.--- Ongoing DLP policy management, which requires someone in the organization to operate and tune policies for changes in sensitive information types, retention labels, regulations, and compliance policies.-
-Although sensitivity labels canΓÇÖt be used in DLP policy conditions, certain protection scenarios to prevent access may be achievable with just sensitivity labels that can be auto-applied based on sensitive information types. If robust sensitivity labeling is in place, consider whether DLP should be used to augment protection because:
-
- - DLP can prevent sharing of files. Sensitivity labels can just prevent access.
-
- - DLP has more granular levels of control in terms of rules, conditions, and actions.
-
- - DLP policies can be applied to Teams chat and channel messages. Sensitivity labels can only be applied to documents and email. -->
--
-### DLP policies
-
-DLP policies are configured in the Microsoft Purview compliance portal and specify the level of protection, the information the policy is looking for, and the target workloads. Every DLP policy requires you to:
-
-1. Choose what you want to monitor.
-1. Choose where to monitor.
-1. Choose the conditions that must be matched for a policy to be applied to an item.
-1. Choose the action to take when the policy conditions are met.
-
-To learn more about DLP policies, and how to design them, see:
--- [Learn about data loss prevention](../compliance/dlp-learn-about-dlp.md)-- [Design a data loss prevention policy](../compliance/dlp-policy-design.md)-- [Data Loss Prevention policy reference](../compliance/dlp-policy-reference.md)--
-<!--
-
-> [!div class="mx-imgBorder"]
-> ![DLP policy configuration in Microsoft 365.](../media/information-protection-deploy-protect-information/information-protection-deploy-protect-information-dlp-config.png)
-
-Here is an example DLP policy for awareness of GDPR.
-
-![Example DLP policy for awareness of GDPR.](../media/information-protection-deploy-protect-information/information-protection-deploy-protect-information-dlp-example-policy.png)
-
-See [this article](../compliance/create-test-tune-dlp-policy.md) for more information about creating and applying DLP policies.-->
-
-### Protection levels for data privacy
-
-The following table lists three configurations of increasing protection using DLP.
-
-![Protection levels of data privacy with DLP.](../media/information-protection-deploy-protect-information/information-protection-deploy-protect-information-dlp-protection-levels.png)
-
-The first configuration, Awareness, can be used as a starting point and minimum level of protection to address compliance needs for data privacy regulations.
-
-> [!NOTE]
-> As the levels of protection increase, the ability of users to share and access information will decrease in some cases and could potentially impact their productivity or ability to complete daily tasks.
-
-To help your employees continue to be productive in a more secure environment when increasing protection levels, take the time to train and educate them on new security policies and procedures.
-
-### Example of using sensitivity labels with DLP
-
-Sensitivity labels can work together with DLP to provide data privacy in a highly regulated environment. Here are the key steps of the integrated deployment:
-
-1. Regulatory and otherwise business requirements for data privacy are documented.
-2. Target data sources, types, and ownership are characterized relative to data privacy concerns.
-3. An overall strategy to address requirements and protect and govern data privacy hotspots is established.
-4. A phased action plan to address the data privacy control strategy is put into place.
-
-Once these elements are determined, you can use sensitive information types, your sensitivity labeling taxonomy, and DLP policies together. This figure shows an example.
-
-> [!div class="mx-imgBorder"]
-> ![Example of sensitivity labels working with DLP.](../media/information-protection-deploy-protect-information/information-protection-deploy-protect-information-sensitivity-lables-dlp.png)
-
-[See a larger version of this image](https://github.com/MicrosoftDocs/microsoft-365-docs/raw/public/microsoft-365/media/information-protection-deploy-protect-information/information-protection-deploy-protect-information-sensitivity-lables-dlp.png)
-
-Here are some data protection scenarios using DLP and sensitivity labels together as shown in the figure.
-
-| Scenario | Process |
-|:-|:--|
-| A | <ol><li>Sensitivity labels for content are published by an administrator to users and groups for manual or automatic application to content and email. </li><li>User A applies the labels manually or automatically when interacting with content, with encryption or other settings applied. </li><li>User A sends a protected email or file to User B, a guest user. </li></ol> |
-| B | DLP policy published by an administrator to User A blocks User A from sending the email and/or file to User B. |
-| C | Sensitivity label with ΓÇ£owner canΓÇÖt invite guestsΓÇ¥ setting is published to User A, who provisions a Teams team or SharePoint site. Another user of the site selectively tries sharing a file with User B, but DLP blocks it. |
-| D | Sensitivity label for auto-application to site content is published to one or more sites, providing another layer of protection, resulting in a protected site. |
-|||
-
-## Office 365 Message Encryption (OME) new capabilities
-
-People often use email to exchange sensitive items, such as patient health information or customer and employee information. Email message encryption helps ensure that only intended recipients can view message content.
-
-With [OME](../compliance/ome.md), you can send and receive encrypted messages between people inside and outside your organization. OME works with Outlook.com, Yahoo!, Gmail, and other email services. OME helps ensure that only intended recipients can view message content.
-
-For data privacy, you use OME to protect internal messages containing sensitive items. Office 365 Message Encryption is an online service that's built on Microsoft Azure Rights Management (Azure RMS) which is part of Azure Information Protection. This includes encryption, identity, and authorization policies to help secure your email. You can encrypt messages by using rights management templates, the Do Not Forward option, and the encrypt-only option.
-
-You can also define mail flow rules to apply this protection. For example, you can create a rule that requires the encryption of all messages addressed to a specific recipient, or that contains specific keywords words in the subject line, and also specify that recipients can't copy or print the contents of the message.
-
-In addition, OME [Advanced Message Encryption](../compliance/ome-advanced-message-encryption.md) helps you meet compliance obligations that require more flexible controls over external recipients and their access to encrypted emails. With OME Advanced Message Encryption in Microsoft 365, you can control sensitive emails shared outside the organization with automatic policies that detect sensitive information types.
-
-For data privacy, if you need to share email with an external party, you can specify an expiration date and revoke messages. You can only revoke and set an expiration date for messages sent to external recipients.
-
-### Secure email scenarios comparison with OME and sensitivity labels
-
-OME and sensitivity labels applied to email with encryption have some overlap, so itΓÇÖs important to understand which scenarios that either might apply to, as shown in this table.
-
-| Scenario | Sensitivity Labels | OME |
-|:-|:--|:-|
-| Internal + partners <br> Securely communicate and collaborate between internal users and trusted partners | Recommend ΓÇô labels with fully customized classification and protection | Yes ΓÇô Encrypt only or Do Not Forward protection with no classification |
-| External parties <br> Securely communicate and collaborate with any external/consumer users | Yes ΓÇô predefine recipients in label | Recommend ΓÇô just-in-time protection based on recipients |
-| Internal + partners, with expiration/revocation <br> Control access of mail and content with internal users and trusted partners with expiration and revocation | Recommend - fully customized protection with access duration, user can manually track and revoke files | No ΓÇô no revocation or expiration for internal mail |
-| External parties with expiration/revocation <br> Control access of mail and content with external/consumer users with expiration and revocation | Yes ΓÇô user can manually track files | Recommend (E5) ΓÇô admin can revoke mail from Security & Compliance Center |
-| Auto-labeling <br> Organization wants to automatically protect mail/attachments with specific sensitive content and/or specific recipients | Recommend (E5) - Auto-labeling in Exchange and Outlook clients, augments mail flow rules and DLP policy | Yes - mail flow rules and DLP policy with Encrypt only or Do Not Forward protection |
-||||
-
-There will also be differences in end-user and admin experiences between these two methods.
-
-## Teams with protection for highly sensitive data
-
-For organizations that plan to store personal data subject to data privacy regulations in Teams, see [Configure a team with security isolation](secure-teams-security-isolation.md), which provides detailed guidance and configuration steps for:
--- Identity and device access-- Creation of a private team-- Lockdown of underlying team site permissions-- A group-based sensitivity label with encryption
solutions Information Protection Deploy https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/solutions/information-protection-deploy.md
- Title: "Deploy information protection for data privacy regulations with Microsoft 365"---- NOCSH- Previously updated : 06/22/2020----- highpri-- M365-security-compliance-- Strat_O365_Enterprise-- m365solution-infoprotection-- m365solution-overview-- zerotrust-solution-
-description: Configure information protection in Microsoft 365 for data privacy regulations like GDPR and the California Consumer Privacy Act (CCPA), including Microsoft Teams, SharePoint, and email.
---
-# Deploy information protection for data privacy regulations with Microsoft 365
-
-Your organization may be subject to regional data privacy regulations that require you to protect, manage, and provide rights and control over personal information stored in your IT infrastructure, including both on-premises and in the cloud. The best example of a data privacy regulation is the European Union's General Data Protection Regulation (GDPR). Failure to comply with data privacy regulations can result in substantial fines.
-
-Examples of the types of data in Microsoft 365 include chat sessions in Microsoft Teams, emails in Exchange, and files in SharePoint and OneDrive. This solution provides guidance on how to assess risks and take appropriate action to protect personal data in Microsoft 365. This includes identifying personal information so you can protect, govern, and respond to data privacy incidents.
-
-![What is information protection for data privacy regulations.](../media/information-protection-deploy/information-protection-data-privacy-regulations-overview.png#lightbox)
-
-Additional information is also provided on the use of Microsoft 365 identity, device, and threat protection controls for your data privacy needs.
-
-Watch this video for an overview of the deployment process.
-<br>
-<br>
-> [!VIDEO https://www.microsoft.com/en-us/videoplayer/embed/RE4NHCQ]
-
-These Microsoft 365 capabilities and features help you meet the criteria for protecting information.
-
-| Capability or feature | Description | Licensing |
-|:-|:--|:-|
-| Compliance Manager | Manage regulatory compliance activities, get an overall score of your current compliance configuration, and find recommendations for improvement. This is a workflow-based risk assessment tool in the Microsoft Purview compliance portal. | Microsoft 365 E3 and E5 |
-| Microsoft Defender for Office 365 | Protect your Microsoft 365 apps and dataΓÇösuch as email messages, Office documents, and collaboration toolsΓÇöfrom attack. | Microsoft 365 E3 and E5 |
-| Sensitivity labels | Classify and protect your organization's data without hindering the productivity of users and their ability to collaborate. Place labels with various levels of protection on email, files, or sites. | Microsoft 365 E3 and E5 |
-| Data Loss Protection (DLP) | Detect, warn, and block risky, inadvertent, or inappropriate sharing of data containing personal information, both internally and externally. | Microsoft 365 E3 and E5 |
-| Data retention labels and policies | Implement information governance controls. These can include determining how long to keep data (such as personal data related to customers) to comply with your organization's policies or data regulations. | Microsoft 365 E3 and E5 |
-| Email encryption | Protect personal data by sending and receiving encrypted email messages between people inside and outside your organization. | Microsoft 365 E3 and E5 |
-||||
-
-## Organization of the guidance in this solution
-
-To help you understand the Microsoft 365 tools available to help you meet one or more privacy-related regulations, this guidance is organized into sections.
-
-![Steps to implement information protection for data privacy regulations.](../media/information-protection-deploy/information-protection-data-privacy-regulations-steps.png)
-
-Each of these sections corresponds to a separate article in this solution.
-
-> [!NOTE]
-> If you are already familiar with your data privacy obligations and are executing against an existing plan, you may want to focus on the Prevent, Protect, Retain, and Investigate guidance.
-
-> [!IMPORTANT]
-> Following this guidance will not necessarily make you compliant with any data privacy regulation, especially considering the number of steps required that are outside the context of the features. You are responsible for ensuring your compliance and to consult your legal and compliance teams or to seek guidance and advice from third parties that specialize in compliance.
-
-## Plan: Assess data privacy risks and identify sensitive items
-
-Assessing data privacy regulations and risks that your organization is subject to is a key first step to take before starting to implement improvements, including configuring capabilities in Microsoft 365. This work can include an overall readiness assessment or identification of particular sensitive information types that are subject to regulatory controls your organization needs to comply with.
-
-For more information, see [Assess data privacy risks and identify sensitive items](information-protection-deploy-assess.md).
-
-## Track: Run risk assessments and check your compliance score
-
-Compliance Manager, available in the <a href="https://go.microsoft.com/fwlink/p/?linkid=2077149" target="_blank">Microsoft Purview compliance portal</a>, provides you with a built-in ability to track and manage improvement actions overall as well as those related to multiple data privacy regulations that apply to you.
-
-You can use built in assessment templates specific to each regulation, where you can track action items for each assessment template selected, as well as view specific regulatory controls, and relate them to specific actions.
-
-For more information, see [Use Compliance Manager to manage improvement actions](information-protection-deploy-compliance.md).
-
-## Prevent: Protect personal data
-
-Microsoft 365 provides identity, device, and threat protection capabilities that you can use to help comply with data privacy regulatory compliance.
-
-For more information, see [Use identity, device, and threat protection for data privacy regulation](information-protection-deploy-identity-device-threat.md).
-
-This article briefly describes what the data privacy regulations generally call for in these areas and provides a listing of related Microsoft 365 solutions, with links to more information to help you address any implementation requirements.
-
-## Protect information subject to data privacy regulation
-
-Data privacy regulations dictate a number of personal information protection controls that can be employed in your environment, including more than 40 controls for protecting information across just the four data privacy regulations in our sample set of GDPR, California Consumer Protection Act (CCPA), HIPAA-HITECH (United States health care privacy act), and the Brazil Data Protection Act (LGPD).
-
-For more information, see [Protect information subject to data privacy regulation in your organization](information-protection-deploy-protect-information.md).
-
-This article lays out the main control schemes that can be used for addressing information protection needs for data privacy in your organization.
-
-## Retain: Govern information subject to data privacy regulation
-
-Data privacy regulations call for personal information governance controls that can be employed in your environment, including more than 24 controls across the four data privacy regulations in our sample set of GDPR, CCPA, HIPAA-HITECH, and LGPD.
-
-For more information, see [Govern information subject to data privacy regulation in your organization](information-protection-deploy-govern.md).
-
-While the data privacy regulations can be vague regarding information governance&mdash;such as purposeful retention, deletion and archiving&mdash;this article lays out the primary control schemes that you can use address information governance needs for data privacy in your organization.
-
-## Investigate: Monitor, investigate, and respond to data privacy incidents
-
-There are Microsoft 365 features available to help you monitor, investigate, and respond to data privacy incidents in your organization as you operationalize related capabilities.
-
-Having processes, procedures, and other documentation for using these features can be important to demonstrate compliance to regulatory bodies.
-
-For more information, see [Monitor and respond to data privacy incidents in your organization](information-protection-deploy-monitor-respond.md).
-
-## Training for administrators
-
-These training modules from Microsoft Learn can help you learn about how capabilities that are important for information protection.
--
-#### Information protection
-
-|Training:|Protect enterprise information with Microsoft 365|
-|:|:|
-|![Teams info protection training icon.](../media/protect-enterprise-information-microsoft-365.svg)|Protecting and securing your organization's information is more challenging than ever. The Protect enterprise information with Microsoft 365 learning path discusses how to protect your sensitive information from accidental oversharing or misuse, how to discover and classify data, how to protect it with sensitivity labels, and how to both monitor and analyze your sensitive information to protect against its loss. This learning path can help you prepare for the Microsoft 365 Certified: Security Administrator Associate and Microsoft 365 Certified: Enterprise Administration Expert certifications..<br><br>1 hr - Learning Path - 5 Modules|
-
-> [!div class="nextstepaction"]
-> [Start >](/training/modules/m365-security-info-overview/introduction/)
-
-#### Identity and access
-
-|Training:|Protect identity and access with Azure Active Directory|
-|:|:|
-|![Identity and access training icon.](../media/protect-identity-and-access-with-microsoft-365.svg)|The Identity and Access learning path covers the latest identity and access technologies, tools for strengthening authentication, and guidance on identity protection within your organization. Microsoft access and identity technologies enable you to secure your organizationΓÇÖs identity, whether it is on-premises or in the cloud, and empower your users to work securely from any location. This learning path can help you prepare for the Microsoft 365 Certified: Security Administrator Associate and Microsoft 365 Certified: Enterprise Administration Expert certifications.<br><br>2 hr 52 min - Learning Path - 6 Modules|
-
-> [!div class="nextstepaction"]
-> [Start >](/training/modules/m365-identity-overview/introduction/)
syntex Accessibility Mode https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/accessibility-mode.md
+
+ Title: Accessibility mode in Microsoft Syntex
++++
+audience: admin
++
+search.appverid:
+
+ - enabler-strategic
+ - m365initiative-syntex
+ms.localizationpriority: medium
+description: Learn how to use accessibility features mode when training and working with models in Microsoft Syntex.
++
+# Accessibility mode in Microsoft Syntex
+
+<sup>**Applies to:** &ensp; &#10003; Unstructured document processing </sup>
+
+In Microsoft Syntex, 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.
+
+![Accessibility mode.](../media/content-understanding/accessibility-mode.png)
+
+## Requirements
+
+To hear the audio of the narration, make sure to turn on the [Narrator App](https://support.microsoft.com/windows/complete-guide-to-narrator-e4397a0d-ef4f-b386-d8ae-c172f109bdb1) in your Narrator settings on your Windows 10 or later system.
+
+![Turn on Narrator.](../media/content-understanding/narrator-settings.png)
+
+## Labeling for keyboard users
+
+For keyboard users using accessibility mode, if you are labeling text in an example document in the viewer, you can use the following keys:
+
+- Tab: Moves you forward and selects the next word.
+- Tab + Shift: Moves you backwards and selects the previous word.
+- Enter: Label or removes a label from the selected word.
+- Right arrow: Moves you forward through individual characters in a selected word.
+- Left arrow: Moves you backward through individual characters in a selected word.
+
+> [!NOTE]
+> If you are labeling multiple words for a single label, you need to label each word.
+
+## Narration
+
+For Narrator users using accessibility mode, use the same keyboard navigation described for keyboard users to go through the example document in the viewer.
+
+As you navigate through the sample documents and label string values, Narrator will give user the following audio prompts:
+
+- When you use the keyboard to navigate through the document viewer, Narrator audio will state the selected string.
+
+- Within a selected string, Narrator audio will state each character in the string as you select them by using the left or right arrow keys.
+
+- If you select a string that has been labeled, Narrator will state the value and then "labeled". For example, if the label value is "Contoso", it will state "Costoso labeled".
+
+- In the training tab, if you select a string in the document viewer that has only been predicted, Narrator audio will state the value, and then "predicted". This occurs when training predicts a value in the file that does not match what has been labeled by the user.
+
+- In the training tab, if you select a string in the document viewer that has been labeled and predicted, Narrator audio will state the value, and then "labeled and predicted". This occurs when training is successful and there is a match between a predicted value and the user label.
+
+After a string is labeled or a label has been removed in the viewer, Narrator audio will warn you to save your changes before you exit.
+
+## See also
+
+[Create an extractor](create-an-extractor.md)
+
+[Create a classifier](create-a-classifier.md)
++++++++++
+
++
+
+
+++
syntex Adoption Assessment Tool https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/adoption-assessment-tool.md
+
+ Title: Discover opportunities in Microsoft Syntex by using the Microsoft 365 Assessment tool
++++ Last updated :
+audience: admin
+++
+- enabler-strategic
+- m365initiative-syntex
+
+- Adopt
+- admindeeplinkMAC
+search.appverid:
+ms.localizationpriority: medium
+description: Learn how to use the adoption assessment tool to see how your organization can benefit from Microsoft Syntex.
++
+# 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 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.
+
+![Image of three sample report pages in the Power BI summary.](../media/content-understanding/assessment-tool-reports.png)
+
+The assessment report includes the following information:
+
+- **Libraries with custom columns** ΓÇô Identify libraries where Syntex can automatically populate columns, improving consistency.
+
+- **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 Syntex models can be used to automatically categorize files.
+
+- **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 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 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 Syntex models in your sites.
+
+- **Assessment overview** ΓÇô Review the assessment results to identify any failures.
+
+## 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.
+
+2. [Download the tool](https://pnp.github.io/pnpassessment/using-the-assessment-tool/download.html).
+
+3. [Decide on an authentication method](https://pnp.github.io/pnpassessment/using-the-assessment-tool/setupauth.html).
+
+4. [Configure permissions](https://pnp.github.io/pnpassessment/sharepoint-syntex/requirements.html).
+
+5. [Run a Syntex assessment](https://pnp.github.io/pnpassessment/sharepoint-syntex/assess.html).
+
syntex Adoption Getstarted https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/adoption-getstarted.md
+
+ Title: Get started driving adoption of Microsoft Syntex
+++ Last updated :
+audience: admin
+++
+- enabler-strategic
+- m365initiative-syntex
+
+search.appverid:
+ms.localizationpriority: medium
+description: Learn how to use and implement Microsoft Syntex in your organization to help streamline your business processes.
++
+# Get started driving adoption of Microsoft Syntex
+
+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 Syntex. For custom model types, there are three different ways of understanding your content. The custom model type you use is based on file format and use case.
+
+| Unstructured document processing | Structured document processing | Freeform document processing |
+| - | - | - |
+| Created in the content center, part of Syntex. | Created from document library. | Created from document library. |
+| Model created in native interface. | Model created in AI builder. | Model created in AI builder. |
+| Used for semi-structured or unstructured file formats. | Used for structured or semi-structured file formats. | Used for unstructured or free-form file formats. |
+| Trainable classifier with optional extractors. | Settable classifier. | Settable classifier. |
+| Can be applied to multiple libraries. | Restricted to a single library. | Restricted to a single library. |
+| Train on 5-10 PDF, Office, or email files, including negative examples. | Train on PDF, JPG, PNG format, total 50 MB/500 pp. | Train on PDF, JPG, PNG format, total 50 MB/500 pp. |
+
+For a more complete comparison of the custom capabilities, see [Compare custom models in Syntex](difference-between-document-understanding-and-form-processing-model.md).
+
+If you don't need to build a custom model, you can use a [prebuilt model](prebuilt-overview.md) that has already been trained for specific structured documents.
+
+## Identify pilot business scenarios to optimize
+
+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 organization based on where the model will be applied. Here are a few scenarios where custom models 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.
+
+- **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 Syntex can help your organization:
+
+- Automate business processes
+- Improve search accuracy
+- Manage compliance risk
+
+When thinking about which business scenarios to consider, ask yourself the following questions:
+
+- Does it solve a real problem?
+- Will it be widely used or have broad impact?
+- Is it obtainable?
+- Can you measure success?
+
+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 Syntex in your organization.
+
+## Identify roles and responsibilities
+
+Determine who in your organization will build and manage the models. The following roles might be involved.
+
+| SharePoint/Knowledge admin | Power Platform admin | Knowledge manager | Model owner |
+|:-|:-|:-|:-|
+| AAD role| AAD role | AAD role | Champions |
+| Configure structured document processing and freeform document processing models | Configure Dataverse environment | Gather use cases | Gather business use cases |
+| Manage content centers and permissions| Purchase and allocate AIB credits | Establish best practices and review model analytics | Create and apply models |
+
+Knowledge manager, business process owner, and content model owner create sample models and champion adoption in the organization. Others who might be involved the compliance admin and taxonomy managers.
+
+Where will they build and apply the models? Are there existing processes or repositories that could be enhanced?
+
+- Unstructured document processing: You can create multiple content centers for different business areas.
+- Structured document processing or freeform document processing: Decide which sites will get this action.
+
+## Strategic 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
+ - Potential agility outcomes
+ - Business outcome template
+- Stakeholders/Exec sponsor buy-in/alignment
+ - Business case decks
+ - Financial models
+ - Company readiness - culture
+
+## Identify stakeholders
+
+Identify the stakeholders for your project.
+
+|Role |Responsibilities |Department |
+|:-|:-|:--|
+| Executive sponsor | Communicate high-level vision and values to the company | Executive leadership |
+| Project lead | Oversee the entire launch execution and rollout process | Project management |
+| Knowledge administrators| Create and manage the content centers | IT or other department|
+| Content managers and model owners| Gather use cases and create and apply models | Any department|
+| Champions | Help evangelize and manage objection handling | Any department (staff) |
+| Tenant administrator | Configure tenant-level settings | IT department|
+| Power Platform administrator| Configure Dataverse environment | IT department|
+
+> [!NOTE]
+> Though we recommend having each of these roles fulfilled throughout your rollout, you might find that you don't require them all to get started with your identified solution.
+
+## Readiness checklist
+
+To get ready for implementing Syntex, you need to:
+
+![Readiness for content understanding.](../media/content-understanding/cu-adoption-readinesschecklist.png)
+
+1. Plan the end state
+ - Models are the means, not the end.
+ - Plan for harnessing the value of extracted metadata with:
+ - Search
+ - Filtering and view formatting
+ - Compliance
+ - Automation
+2. Identify
+ - Understand existing information architecture and content management feature use.
+ - Are any existing content types good candidates for models?
+ - What existing processes would be improved by metadata?
+3. Design
+ - Design your approach to information architecture, managed metadata, and content types.
+ - Design the process for definition, creation, and management.
+
+## Engage your organization
+
+1. Identify stake holders, confirm scenarios, and develop a project plan.
+2. Configure settings and apply licenses.
+3. Begin awareness and training ΓÇô recruit champions.
+4. Roll out in stages.
+5. Gather feedback and iterate.
+6. As usage grows plan for any AI Builder credits as needed.
+
+## See also
+
+[Microsoft Syntex adoption center](https://adoption.microsoft.com/sharepoint-syntex/adoption/)
+
+[Scenarios and use cases for Microsoft Syntex](adoption-scenarios.md)
+
+[Overview of model types in Microsoft Syntex](syntex-overview.md)
syntex Adoption Scenarios https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/adoption-scenarios.md
+
+ Title: Scenarios and use cases for Microsoft Syntex
++++ Last updated :
+audience: admin
+++
+ - enabler-strategic
+ - m365initiative-syntex
+
+search.appverid:
+ms.localizationpriority: medium
+description: Find business scenarios about how to use Microsoft Syntex in your organization.
++
+# Scenarios and use cases for Microsoft Syntex
+
+Use the following example scenarios to prompt ideas about how you can use Microsoft Syntex in your organization.
+
+- [Scenario: Track information from invoices by using the structured document processing model](adoption-scenarios.md#scenario-track-information-from-invoices-by-using-the-structured-document-processing-model)
+- [Scenario: Track information from contracts by using the unstructured document processing model](adoption-scenarios.md#scenario-track-information-from-contracts-by-using-the-unstructured-document-processing-model)
+- [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)
+- [Scenario: Simplify visa renewal process](adoption-scenarios.md#scenario-simplify-visa-renewal-process)
+
+## Scenario: Track information from invoices by using the structured document processing model
+
+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.
+2. Train the model to recognize fields in the documents.
+3. Extract the fields you want to track into a list.
+4. Set up a flow to notify you for specific events, such as:
+ - A new invoice is added.
+ - An invoice is past its due date.
+ - An invoice is for an amount that's larger than your automatic approval amount.
+
+![Track and monitor invoices with Syntex and Power Automate.](../media/content-understanding/process-invoices-flow.png)
+
+When you automate this scenario, you can:
+
+- Save time and money by automatically extracting data from the invoices instead of doing it manually.
+- Reduce potential errors and ensure better compliance by using workflows to check invoices and notify you of any issues.
+
+## Scenario: Track information from contracts by using the unstructured document processing model
+
+As another example, you can set up a process to identify contracts your company has with other companies or individuals. Set up a model to extract key information from those contracts, such as the client name, fees, dates, or other important information, and add the information to the library as fields you can quickly view. Apply a retention label on the document library to ensure that contracts can't be deleted before a specific length of time for appropriate compliance with your business regulations.
+
+1. Start at the content center and create a new unstructured document processing model for contracts.
+2. Upload sample documents for positive and negative examples, then run the training to identify contract documents and review the results.
+3. Train the extractor to identify fields in the contracts, such as the client name, fee, and date, and then test the extractor.
+4. When the model is complete, apply the model to a library where you can upload contracts.
+5. Apply a retention label to the date field, so that contracts are retained in the library for the required length of time.
+
+![Track and monitor contracts with Syntex and retention labels.](../media/content-understanding/process-contracts-flow.png)
+
+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 Syntex
+
+Reducing risks is a common goal for most companies. You might need:
+
+- A better way to provide/enforce information governance across your tenant.
+- To improve the system for classification of documents, emails and other forms of communication considered "records" for projects.
+- 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 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:
+
+- Compliance is upheld and risk is reduced.
+- Taxonomy and records management is consistently and accurately applied.
+- Content volumes are controlled.
+- Employees can easily discover the right information in the right context.
+
+## Scenario: Capture information from previously inaccessible documents
+
+Most organizations have large repositories of legal documents, policies, contracts, HR documents, and governance guidelines. Mine these data stores to extract valuable information such as: projects, sectors, themes, people, geographical areas, and so on.
+
+For example, an HR director needs to quickly access all HR documents ΓÇô including resumes, HR policies, and other forms. And they want to quickly identify necessary information from resumes and other HR-related documents without manually sifting through the documents. TheyΓÇÖre looking for a solution that allows them to quickly find the information they need without having to manually look through thousands of resumes, HR policies, and other documentation that may be spread across several sites.
+
+When you automate this scenario, you can:
+
+- Unlock knowledge from digital content.
+- Classify HR policies, resumes, sales documents, technical blueprints, and account plans, and extract information.
+- Quickly find the correct information or document that youΓÇÖre looking for.
+- Get instant access to the latest information.
+- Reduce search times.
+
+## Scenario: Improve data processing to provide insights and analytics
+
+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:
+
+- Reduce time to produce answers.
+- Increase availability of data.
+- Provide more accurate answers.
+
+## Scenario: Automate order processing
+
+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 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 automatically push it into their ERP system, for order fulfillment and reconciliation.
+
+When you automate this scenario, you can ensure that:
+
+- Order and shipment accuracy increases.
+- Fees or penalties associated to order or shipment errors are reduced.
+- Delays in invoicing or payments decrease.
+- Personnel costs are reduced.
+
+## Scenario: Simplify visa renewal process
+
+Syntex can help you automate reminders and renewals for key contract information. For example, an HR director needs to ensure that employeesΓÇÖ visas are up to date or renewed on time. They want to give people a simple and intuitive process for updating their visas. They need a solution that extracts renewal dates from contracts and automatically sends employees reminders when their renewal dates are approaching.
+
+When you automate this scenario, you can ensure that:
+
+- The levels of non-compliance are reduced.
+- The number of manual reminders is reduced.
+- The number of fines for non-compliance is reduced.
+
+## See also
+
+[Get started driving adoption of Microsoft Syntex](adoption-getstarted.md)
+
+[Manage contracts using a Microsoft 365 solution](solution-manage-contracts-in-microsoft-365.md)
syntex Apply A Model https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/apply-a-model.md
+
+ Title: Apply a model to a document library in Microsoft Syntex
++++
+audience: admin
++
+search.appverid:
+
+ - enabler-strategic
+ - m365initiative-syntex
+ms.localizationpriority: medium
+description: Learn how to apply a published a model to a SharePoint document library in Microsoft Syntex.
++
+# Apply a model to a document library in Microsoft Syntex
+
+<sup>**Applies to:** &ensp; &#10003; All custom models &ensp; | &ensp; &#10003; All prebuilt models</sup>
+
+<!
+</br>
+
+> [!VIDEO https://www.microsoft.com/videoplayer/embed/RE4CSoL]
+
+</br>
+>
+
+After you train an unstructured document processing model, train and publish a freeform or structured document processing model, or create a prebuilt model, you can apply it to one or more SharePoint document libraries in your Microsoft 365 tenant.
+
+This article applies to both *enterprise models* and *local models*. An enterprise model is created and trained in the [content center](create-a-content-center.md), and can be discovered by others to use. A [local model](create-local-model.md) is created and trained locally on your own SharePoint site.
+
+> [!NOTE]
+> You can apply the model only to document libraries to which you have access.
+
+## Apply your model to a document library
+
+You can apply a model to different places, including the model home page or from the list of available models. To apply your model to a SharePoint document library:
+
+1. On model home page, on the **Apply model to libraries** tile, select **Apply model**. Or, in the **Where the model is applied** section, select **Add library**.
+
+ ![Screenshot of Where the model is applied section with the Add library option highlighted.](../media/content-understanding/apply-to-library.png)
+
+2. You can then select the SharePoint site that contains the document library that you want to apply the model to. If the site doesn't show in the list, use the search box to find it.
+
+ ![Select a site.](../media/content-understanding/site-search.png)
+
+ > [!NOTE]
+ > You must have *Manage List* permissions or *Edit* rights to the document library you are applying the model to.
+
+3. After selecting the site, select the document library to which you want to apply the model. In the sample, select the *Documents* document library from the *Contoso Case Tracking* site.
+
+ ![Select a doc library.](../media/content-understanding/select-doc-library.png)
+
+4. Because the model is associated to a content type, when you apply it to the library it will add the content type and update the default view with the labels you extracted showing as columns. However, you can select **Advanced settings** to optionally choose to retain the current library view or to use a new view with model information and file thumbnails. If you choose to keep the current library view, the new views with model information are still available under the library's view menu.
+
+ ![Screenshot of the Advanced settings showing the library views.](../media/content-understanding/library-view.png)
+
+ For more information, see [Choose the view in a document library](choose-library-view.md).
+
+5. Select **Add** to apply the model to the library.
+
+6. On the model home page, in the **Where the model is applied** section, you should see the name of the SharePoint site listed.
+
+7. Go to your document library and make sure you are in the model's document library view. Select **Automate** > **View models**.
+
+8. On the **Review models and apply new ones** page, select the **Applied** tab to see the models that are applied to the document library.
+
+ ![Screenshot showing the Applied tab selected and the applied models.](../media/content-understanding/applied-models.png)
+
+9. Select **View model details** to see information about a model, such as a description of the model, who published the model, and if the model applies retention or sensitivity labels to the files it classifies.
+
+After applying the model to the document library, you can begin uploading documents to the site and see the results.
+
+The model identifies any files and folders with the modelΓÇÖs associated content type and lists them in your view. If your model has any extractors, the view displays columns for the data you're extracting from each file or folder.
+
+> [!NOTE]
+> If two or more unstructured document processing models are applied to the same library, the uploaded file is classified using the model that has the highest average confidence score. The extracted entities will be from the applied model only. <br><br>If a freeform or structured document processing model model and an unstructured document processing model are applied to the same library, the file is classified using the unstructured document processing model and any trained extractors for that model. If there are any empty columns that match the freeform or structured document processing model, the columns will be populated using those extracted values.
+
+## Sync changes to one or more document libraries
+
+When you publish a model to multiple document libraries and then update the model, such as adding or removing an extractor, you need to push the update to all the libraries that the model has been applied.
+
+To sync changes to all applied libraries:
+
+1. On model home page, in the **Where the model is applied** section, select **Sync all**.
+
+ ![Screenshot showing the Where the model is applied section and the Sync all button highlighted.](../media/content-understanding/sync-all-button.png)
+
+To sync changes to one or only selected libraries:
+
+1. On model home page, in the **Where the model is applied** section, select the library or libraries you want to apply the changes to.
+
+2. Select **Sync**.
+
+ ![Screenshot showing the Where the model is applied section and the Sync button highlighted.](../media/content-understanding/sync-button.png)
+
+## Apply the model to files and folder content already in the document library
+
+An applied model processes all files and folder content uploaded to the document library after it's applied. You can also do the following steps to run the model on files and folder content that already exist in the document library prior to the model being applied:
+
+1. In your document library, select the files and folders that you want to be processed by your model.
+
+2. After selecting your files and folders, **Classify and extract** will appear in the document library ribbon. Select **Classify and extract**.
+
+ ![Screenshot showing the Classify and extract option.](../media/content-understanding/extract-classify.png)
+
+3. The files and folders you selected will be added to the queue to be processed.
+
+ > [!NOTE]
+ > If you've selected one or more folders or are migrating a large set of files, classification might take up to 24 hours.
+
+### Classification Date field
+
+When a custom is applied to a document library, the **Classification Date** field is included in the library schema. By default, this field is empty. However, when documents are processed and classified by a model, this field is updated with a date-time stamp of completion.
+
+ ![Screenshot of a document library showing the Classification Date column.](../media/content-understanding/class-date-column.png)
+
+The **Classification Date** field is used by the [**When a file is classified by a content understanding model**](/connectors/sharepointonline/#when-a-file-is-classified-by-a-content-understanding-model) trigger to run a Power Automate flow after a model has finished processing the contents of a file or folder and has updated the **Classification Date** field.
+
+ ![Flow trigger.](../media/content-understanding/trigger.png)
+
+The **When a file is classified by a content understanding model** trigger can then be used to start a flow using any extracted information from the file or folder.
+
+As an example, when a model is stamped with the **Classification Date**, you can use the **Send an email after Syntex processes a file** flow to notify users that a new file has been processed and classified by a model in the SharePoint document library.
+
+To run the flow:
+
+1. Select a file, and then select **Integrate** > **Power Automate** > **Create a flow**.
+
+2. On the **Create a flow** panel, select **Send an email after Syntex processes a file**.
+
+ ![Screenshot showing the Create a flow panel and flow option highlighted.](../media/content-understanding/integrate-create-flow.png)
+
+## See also
+
+[Share an enterprise model](model-discovery.md)
+
+[Discover other trained models](discover-other-trained-models.md)
+
+[Choose the view in a document library](choose-library-view.md)
+
syntex Apply A Retention Label To A Model https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/apply-a-retention-label-to-a-model.md
+
+ Title: Apply a retention label to a model in Microsoft Syntex
++++
+audience: admin
++
+search.appverid:
+
+ - enabler-strategic
+ - m365initiative-syntex
+ms.localizationpriority: medium
+description: Learn how to apply a retention label to a model in Microsoft Syntex.
++
+# Apply a retention label to a model in Microsoft Syntex
+
+<sup>**Applies to:** &ensp; &#10003; Unstructured document processing &ensp; | &ensp; &#10003; Structured document processing &ensp;| &ensp; &#10003; All prebuilt models</sup>
+
+<!
+</br>
+
+> [!VIDEO https://www.microsoft.com/videoplayer/embed/RE4GydO]
+
+</br>
+>
+
+You can easily apply a [retention label](../compliance/retention.md) to a model in Microsoft Syntex.
+
+> [!Note]
+> Retention labels are not yet available for Freeform document processing models.
+
+Retention labels let you apply retention settings to the documents that your models identify. For example, you want your model to not only identify any *Insurance notice* documents that are uploaded to your document library, but to also apply a *Business* retention tag to them so that these documents can't be deleted from the document library for the specified time period (the next five months, for example).
+
+You can apply a pre-existing retention label to your model through your model settings on your model's home page.
+
+## Add a retention label to an unstructured document processing model or a prebuilt model
+
+> [!Important]
+> For retention labels to be available to apply to your unstructured document processing or prebuilt models, they need to be [created](../compliance/file-plan-manager.md#create-retention-labels) and [published](../compliance/create-apply-retention-labels.md#how-to-publish-retention-labels) in the Microsoft Purview compliance portal.
+
+1. From the model home page, select **Model settings**.
+
+2. In **Model settings**, in the **Security and compliance** section, select the **Retention label** menu to see a list of retention labels that are available for you to apply to the model.
+
+ ![Retention label menu.](../media/content-understanding/retention-labels-menu.png)
+
+3. Select the retention label you want to apply to the model, and then select **Save**.
+
+After applying the retention label to your model, you're able to apply it to a:
+
+- New document library
+- Document library to which the model is already applied
+
+### Apply the retention label to a document library to which the model is already applied
+
+If your unstructured document processing model or prebuilt model has already been applied to a document library, you can do the following to sync your retention label update to apply it to the document library:
+
+1. On your model home page, in the **Libraries with this model** section, select the document library to which you want to apply the retention label update.
+
+2. Select **Sync**.
+
+ ![Sync model.](../media/content-understanding/sync-model.png)</br>
+
+After applying the update and syncing it to your model, you can confirm that it has been applied by doing the following steps:
+
+1. In the content center, in the **Libraries with this model** section, select the library to which your updated model was applied.
+
+2. In your document library view, select the information icon to check the model properties.
+
+3. In the **Active models** list, select your updated model.
+
+4. In the **Retention label** section, you'll see the name of the applied retention label.
+
+On your model's view page in your document library, a new **Retention label** column will display. As your model classifies files it identifies as belonging to its content type and lists them in the library view, the **Retention label** column will also display the name of the retention label that has been applied to it through the model.
+
+For example, all *Insurance notice* documents that your model identifies will also have the *Business* retention label applied to them, preventing them from being deleted from the document library for five months. If an attempt is made to delete the file from the document library, an error will display saying it isn't allowed because of the applied retention label.
+
+## Add a retention label to a structured document processing model
+
+> [!Important]
+> For retention labels to be available to apply to your structured document processing models, they need to be [created](../compliance/file-plan-manager.md#create-retention-labels) and [published](../compliance/create-apply-retention-labels.md#how-to-publish-retention-labels) in the Microsoft Purview compliance portal.
+
+You can either apply a retention label to a structured document processing model when you're creating a model, or apply it to an existing model.
+
+### To add a retention label when you create a structured document processing model
+
+1. When you're [creating a new structured document processing model](./create-a-form-processing-model.md), select **Advanced settings**.
+
+2. In **Advanced settings**, in the **Retention label** section, select the menu and then select the retention label you want to apply to the model.
+
+ ![Add to a new structured document processing model.](../media/content-understanding/retention-label-forms.png)
+
+3. After you've completed your remaining model settings, select **Create** to build your model.
+
+### To add a retention label to an existing structured document processing model
+
+You can add a retention label to an existing structured document processing model in different ways:
+
+- Through the **Automate** menu in the document library
+- Through the **Active model** settings in the document library
+
+#### To add a retention label to an existing structured document processing model through the Automate menu
+
+You can add a retention label to an existing structured document processing model that you own through the **Automate** menu in the document library in which the model is applied.
+
+1. In your document library to which the model is applied, select the **Automate** > **AI Builder** > **View model details**.
+
+ ![Automate menu.](../media/content-understanding/automate-menu.png)
+
+2. In the model details, in the **Retention label** section, select the retention label you want to apply, and then select **Save**.
+
+ ![Add to an existing structured document processing model.](../media/content-understanding/retention-label-model-details.png)</br>
+
+#### To add a retention label to an existing structured document processing model in the active model settings
+
+You can add a retention label to an existing structured document processing model that you own through the Active model settings in the document library in which the model is applied.
+
+1. In the SharePoint document library in which the model is applied, select the **View active models** icon, and then select **View active models**.
+
+ ![View active models.](../media/content-understanding/info-du.png)
+
+2. In **Active models**, select the model to which you want to apply the retention label.
+
+ ![Model details.](../media/content-understanding/retention-label-model-details.png)</br>
+
+3. In the model details, in the **Retention label** section, select the retention label you want to apply, and then select **Save**.
+
+> [!NOTE]
+> You must be the model owner for the model settings pane to be editable.
+
+## See also
+
+[Apply a sensitivity label to a model in Microsoft Syntex](create-a-classifier.md)
+++
syntex Apply A Sensitivity Label To A Model https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/apply-a-sensitivity-label-to-a-model.md
+
+ Title: Apply a sensitivity label to a model in Microsoft Syntex
++++
+audience: admin
++
+search.appverid:
+
+ - enabler-strategic
+ - m365initiative-syntex
+ms.localizationpriority: medium
+description: Learn how to apply a sensitivity label to a model in Microsoft Syntex.
++
+# Apply a sensitivity label to a model in Microsoft Syntex
+
+<sup>**Applies to:** &ensp; &#10003; Unstructured document processing </sup>
+
+You can easily apply a [sensitivity label](../compliance/sensitivity-labels.md) to unstructured document processing models in Microsoft Syntex.
+
+> [!Note]
+> Sensitivity labels are not yet available for prebuilt models or for freeform or structured document processing models.
+
+Sensitivity labels let you apply encryption to the documents that your models identify. For example, you want your model to not only identify any financial documents that contain bank account numbers or credit card numbers that are uploaded to your document library, but also to apply a sensitivity label that's configured with encryption settings to restrict who can access that content and how it can be used. Syntex models honor the [label order](../compliance/apply-sensitivity-label-automatically.md#how-multiple-conditions-are-evaluated-when-they-apply-to-more-than-one-label) rules and also don't overwrite an existing label that was manually applied by a user to the file.
+
+You can apply a pre-existing sensitivity label to your model through your model settings on your model's home page. The label must already be published to be available for selection from model settings. Labels apply to Office files for Word (.docx), PowerPoint (.pptx), and Excel (.xlsx).
+
+> [!Important]
+> For sensitivity labels to be available to apply to your models, they need to be [created and published in the Microsoft Purview compliance portal](../admin/security-and-compliance/set-up-compliance.md).
+
+## Add a sensitivity label to a model
+
+1. From the model home page, select **Model settings**.
+
+ ![Screenshot of the Models page with the Model settings option highlighted.](../media/content-understanding/sensitivity-model-settings.png)
+
+2. On **Model settings** pane, in the **Compliance** section, select the **Sensitivity label** menu to see a list of sensitivity labels that are available for you to apply to the model.
+
+ ![Screenshot of the Model settings pane showing the sensitivity label menu.](../media/content-understanding/sensitivity-model-settings-pane.png)
+
+3. Select the sensitivity label you want to apply to the model, and then select **Save**.
+
+After you apply the sensitivity label to your model, you can apply it to a:
+
+- New document library
+- Document library to which the model is already applied
+
+### Apply the sensitivity label to a document library to which the model is already applied
+
+If your model has already been applied to a document library, you can do the following to sync your sensitivity label update to apply it to the document library:
+
+1. On the model home page, in the **Libraries with this model** section, select the document library to which you want to apply the sensitivity label update.
+
+2. Select **Sync**.
+
+ ![Screenshot showing Libraries with this model section with Sync highlighted.](../media/content-understanding/sensitivity-libraries-sync.png)
+
+After you apply the update and sync it to your model, you can confirm that it has been applied by doing the following steps:
+
+1. In the content center, in the **Libraries with this model** section, select the library to which your updated model was applied.
+
+2. In your document library view, select the information icon to check the model properties.
+
+3. In the **Active models** list, select your updated model.
+
+4. In the **Sensitivity label** section, you'll see the name of the applied sensitivity label.
+
+On your model's view page in your document library, a new **Sensitivity label** column will display. As your model classifies files it identifies as belonging to its content type and lists them in the library view, the **Sensitivity label** column will also display the name of the sensitivity label that has been applied to it through the model.
+
+For example, all financial documents that your model identifies also will have the *Encryption* sensitivity label applied to them, preventing them from being accessed by unauthorized people. If an attempt is made to access the file from the document library by an unauthorized person, an error will display saying it isn't allowed because of the applied sensitivity label.
+
+## See also
+
+[Apply a retention label](apply-a-retention-label-to-a-model.md)
+
syntex Automate Document Generation https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/automate-document-generation.md
+
+ Title: Automate document generation with Microsoft Syntex and Power Automate (Preview)
+++
+audience: admin
+++
+search.appverid:
+
+ - enabler-strategic
+ - m365initiative-syntex
+ms.localizationpriority: medium
+description: Learn how to automatically create documents and other content using Microsoft Syntex and Power Automate.
++
+# Automate document generation with Microsoft Syntex and Power Automate (Preview)
+
+Using content assembly in Microsoft Syntex together with Power Automate, you can automate the generation of documents using modern templates.
+
+This preview version is a Power Automate action in a SharePoint connector. The action is named ΓÇ£Generate document using Syntex (Preview)ΓÇ¥ and has limited capabilities for preview.
+
+## Scope of the preview
+
+The current scope of the preview lets you:
+
+- Choose a SharePoint list as a starting point for document generation. That is, you want a document to be generated using the values in the SharePoint list once an item in the list has been added, modified, or deleted.
+
+- Choose a modern template and associate its fields with columns from the chosen SharePoint list.
+
+The preview is created and tested to work for the following three triggers in SharePoint Connector:
+
+- When an item is created
+- When an item is created or modified
+- When an item is deleted
+
+## Automate document generation
+
+Follow these steps to automatically generate documents using a modern template and Power Automate.
+
+1. Sign in to Power Automate.
+
+2. In the left panel, select **Connectors**. In the search box, search for *SharePoint*, and then select the **SharePoint** connector.
+
+3. On the SharePoint connector page, select the trigger that you want to use to start the automated document generation process.
+
+ We recommend starting with any one of the following three triggers:
+
+ - When an item is created
+ - When an item is created or modified
+ - When an item is deleted
+
+4. Next, set up the trigger by entering the SharePoint site address and the name of the SharePoint list. Select **New step**.
+
+ ![Screenshot of the When a document is created or modified trigger showing a sample site address and site name.](../media/content-understanding/document-generation-trigger.png)
+
+5. Select the SharePoint connector again. In the search box, search for and select the action **Generate document using Syntex (preview)**.
+
+ ![Screenshot of the SharePoint connector Actions tab showing Generate document using Syntex (preview) action.](../media/content-understanding/document-generation-action.png)
+
+6. Enter the site information and select the document library that contains the modern template.
+
+7. Once the template is selected, you'll start seeing the template fields. Associate the fields with the columns in the list.
+
+ > [!NOTE]
+ >Data mapping in the template is not supported in this preview. For example, if you have associated a field in your template with a managed metadata column, during automated generation you will be able to associate this field with a column in a list.
+
+8. When done, select **Save** to save the flow.
+
+ > [!NOTE]
+ > We recommend using templates that don't need users to manually add values for document generation. If the template needs manual input for a field, you can specify that value against the field rather than mapping it to a SharePoint list column.<br><br>
+ > Currently, only Word documents (.Docx) are supported using this action.
+
+## See also
+
+ [Overview of content assembly in Microsoft Syntex](content-assembly.md)
syntex Choose Library View https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/choose-library-view.md
+
+ Title: Choose the view in a document library in Microsoft Syntex
++++
+audience: admin
++
+search.appverid:
+
+ - enabler-strategic
+ - m365initiative-syntex
+ms.localizationpriority: medium
+description: Learn how to apply a default view and choose a view a SharePoint document library in Microsoft Syntex.
++
+# Choose the view in a document library in Microsoft Syntex
+
+<sup>**Applies to:** &ensp; &#10003; All custom models &ensp; | &ensp; &#10003; All prebuilt models</sup>
+
+There are multiple ways to view how you see the information in a SharePoint document library. You can choose the default view or change the view in your document library to fit your needs or preferences.
+
+## Choose the default view
+
+When you apply any model to a library, you have the option to set a new default view for the document library.
+
+Because a model is associated to a content type, when you apply it to the library it will add the content type and update the default view with the labels you extracted showing as columns. However, you can select **Advanced settings** to optionally choose to retain the current library view or to use a new view with model information and file thumbnails. If you choose to keep the current library view, the new views with model information are still available under the library's view menu.
+
+ ![Screenshot of the Advanced settings showing the library views.](../media/content-understanding/library-view.png)
+
+## Change the library view
+
+You can change the view in a document library depending on your preferences. To change the view on the library page, select the view dropdown menu to show the options, and then select the view you want to use.
+
+ ![Screenshot of a view dropdown menu showing the view options.](../media/content-understanding/document-library-view-menu.png)
+
+For example, if you select **Tiles** from the list, the page will display as shown.
+
+ ![Screenshot of a document library showing the Tiles view.](../media/content-understanding/document-library-tiles-view.png)
+
+The **Tiles** view displays up to eight user-created fields. If there are fewer than eight, up to four system-generated fields are shown: Sensitivity (if available), Retention (if available), Content type, Modified date, Modified by, and Classification date.
+
+To edit any current view, on the view dropdown menu, select **Edit current view**.
+++
syntex Content Assembly Create Document https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/content-assembly-create-document.md
+
+ Title: Create a document from a modern template in Microsoft Syntex
+++
+audience: admin
+++
+search.appverid:
+
+ - enabler-strategic
+ - m365initiative-syntex
+ms.localizationpriority: medium
+description: Learn how to create documents and other content using a modern template in Microsoft Syntex.
++
+# Create a document from a modern template in Microsoft Syntex
+
+You can use a *published* modern template to quickly create similar documents without having to start from scratch. To create a document using a published template, follow these steps:
+
+1. From a SharePoint document library, select **New**, and then select the modern template you want to use.
+
+ ![Screenshot of document library showing the modern template choices on the New menu.](../media/content-understanding/content-assembly-create-document-1.png)
+
+2. The template opens in the template studio.
+
+3. On the **Create a document from a template** panel, enter the information, and then select **Create document**.
+
+ ![Screenshot of document library showing the Create a document from a template panel.](../media/content-understanding/content-assembly-create-document-2b.png)
+
+ To help reduce time and effort involved in filling values for fields, Syntex provides:
+
+ - Suggestions to help you easily pick values when selecting values from a list.
+ - Autofill field values if able to uniquely identify a record for fields associated with the same list.
syntex Content Assembly Edit Template https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/content-assembly-edit-template.md
+
+ Title: Edit a modern template in Microsoft Syntex
+++
+audience: admin
+++
+search.appverid:
+
+ - enabler-strategic
+ - m365initiative-syntex
+ms.localizationpriority: medium
+description: Learn how to edit a modern template in Microsoft Syntex.
++
+# Edit a modern template in Microsoft Syntex
+
+If you need to edit an existing template or to delete or unpublish a template, follow these steps.
+
+1. From a SharePoint document library, select **New** > **Edit New menu**.
+
+ ![Screenshot of document library with the Edit New menu option highlighted.](../media/content-understanding/content-assembly-edit-template-1.png)
+
+2. On the **Edit New menu** panel, in the **Modern templates** section, select the published or draft template you want to edit.
+
+ ![Screenshot of the Edit New menu panel showing the Modern templates section.](../media/content-understanding/content-assembly-edit-template-2.png)
+
+3. To edit a published template or a draft template:
+
+ - For **Published templates**, select **Edit** to open the template studio where you can edit the published template. You can also choose to delete or unpublish the template.
+
+ ![Screenshot of the Modern templates section showing the published templates.](../media/content-understanding/content-assembly-edit-published.png)
+
+ - For **Draft templates**, select **Edit** to open the template studio where you can edit the draft template. You can also choose to delete or publish the template.
+
+ ![Screenshot of the Modern templates section showing the draft templates.](../media/content-understanding/content-assembly-edit-draft.png)
+
syntex Content Assembly Modern Template https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/content-assembly-modern-template.md
+
+ Title: Create a modern template in Microsoft Syntex
+++
+audience: admin
+++
+search.appverid:
+
+ - enabler-strategic
+ - m365initiative-syntex
+ms.localizationpriority: medium
+description: Learn how to create a modern template in Microsoft Syntex.
++
+# Create a modern template in Microsoft Syntex
+
+## Upload a document to create a modern template
+
+Follow these steps to create a modern template.
+
+1. From a SharePoint document library, select **New** > **Create modern template**.
+
+ ![Screenshot of document library with the Create modern template option highlighted.](../media/content-understanding/content-assembly-create-template-1.png)
+
+2. Select a Word document to upload from your organizationΓÇÖs SharePoint or OneDrive, or from your local storage.
+
+ ![Screenshot of upload page where you select a document.](../media/content-understanding/content-assembly-pick-a-file.png)
+
+3. After you upload the document, the document is displayed in the template studio where you can convert the document to a template by adding fields.
+
+ ![Screenshot of the document in the template viewer.](../media/content-understanding/content-assembly-create-template-3.png)
+
+4. At the upper-left corner of the template studio, select the name for the template. The default name is the name of the document used to create the template. If you want to rename the template, select the default name or the pencil icon next to the name, type the new name, and then select **Enter**.
+
+ ![Screenshot of the template viewer showing the name of the document to select to rename.](../media/content-understanding/content-assembly-create-template-3a.png)
+
+## Create and reuse fields
+
+When you select a document to create a modern template, you can create a new field and map it to multiple occurrences of the content with the same field.
+
+For example, the name of a contractor can occur multiple times in a consulting agreement document. You can create a field named ΓÇ£Contractor NameΓÇ¥ and associate it with all occurrences of the name throughout the document when you generate a modern template.
+
+ ![Screenshot of the document in the template viewer with a field highlighted.](../media/content-understanding/content-assembly-create-and-reuse-fields-1.png)
+
+To create and reuse a field:
+
+1. Select a section of the content, and when it appears on the field panel on the right, select **Confirm**. You can select as many occurrences as required.
+
+2. When the field is created, select **Next** to associate the created field with different data sources.
+
+3. When done, you can see the count of all selections in the field card with the field name and the associated data source.
+
+ ![Screenshot of the Set up the template panel showing the field name and the associated data source.](../media/content-understanding/content-assembly-create-and-reuse-fields-2.png)
+
+## Associate fields with different data sources
+
+You can associate fields by:
+
+- [Entering text or selecting a date](#associate-a-field-by-entering-text-or-selecting-a-date)
+
+- [Selecting from choices in a column of a list or library](#associate-a-field-by-selecting-from-choices-in-a-column-of-a-list-or-library)
+
+- [Selecting from a managed metadata term set or term](#associate-a-field-by-selecting-from-a-managed-metadata-term-set-or-term)
+
+- [Associating a table with a SharePoint list or library](#associate-a-table-with-a-sharepoint-list-or-library)
+
+- [Adding an image field](#add-an-image-field)
+
+### Associate a field by entering text or selecting a date
+
+On the **New field** panel:
+
+1. In the **Name** field, enter a relevant name for the field.
+
+2. In the **How authors fill in this field** section, select **Enter text or select a date**.
+
+ ![Screenshot of the template viewer showing the New field panel for manual input.](../media/content-understanding/content-assembly-create-template-5a.png)
++
+3. In the **Type of info** field, select the data type you want to associate with the field. Currently, there are six options available: **Single line of text**, **Multiple lines of text**, **Number**, **Date and time**, **Email**, and **Hyperlink**.
+
+4. Select **Add**.
+
+ > [!NOTE]
+ > You can configure multiple date formatters such as MM/DD/YYYY, DD/MM/YYYY, YYYY/MM/DD, and Month DD, including setting time in both 12-hour and 24-hour format.
+
+### Associate a field by selecting from choices in a column of a list or library
+
+On the **New field** panel:
+
+1. In the **Name** field, enter a relevant name for the field.
+
+2. In the **How authors fill in this field** section, choose **Select from choices in a column of a list or library**, and then choose **Select**.
+
+ ![Screenshot of the template viewer showing the New field panel for input from a SharePoint list.](../media/content-understanding/content-assembly-create-template-6a.png)
+
+3. On the **Select a list for adding a source column** page, select the list you want to use, and then select **Next**.
+
+ ![Screenshot of the Select a list for adding a source column page showing lists.](../media/content-understanding/content-assembly-create-template-7.png)
+
+4. On the **Select a source column from the existing list** page, select the column name you want to associate with the field, and then select **Save**.
+
+ ![Screenshot of the Select a source column from the existing list page showing column names.](../media/content-understanding/content-assembly-create-template-8.png)
+
+ If you want to see the original page of lists again, select **Go to (list name)** link at the bottom of the list.
+
+5. When you're done, you'll see that the list field has been associated with the field.
+
+ ![Screenshot of the New field panel showing the list field associated with the field.](../media/content-understanding/content-assembly-create-template-9.png)
+
+6. If you want users to be able to add inputs manually, in addition to choosing from a list, select **Allow authors to add new choices**. In this case, the default for the manual input data type is *Single line of text*. Also the values input by the authors will only be used to generate the document. They won't be added to the SharePoint list.
+
+### Associate a field by selecting from a managed metadata term set or term
+
+On the **New field** panel:
+
+1. In the **Name** field, enter a relevant name for the field.
+
+2. In the **How authors fill in this field** section, choose **Select from managed metadata term set or term**, and then choose **Select**.
+
+ ![Screenshot of the template viewer showing the New field panel for input from a term or term set.](../media/content-understanding/content-assembly-create-template-term.png)
+
+3. On the **Select term sets or terms** page, search for or select the term set or term to associate with the field, and then select **Save**.
+
+ ![Screenshot of the Select term sets or terms page.](../media/content-understanding/content-assembly-select-term.png)
+
+4. When youΓÇÖre done, youΓÇÖll see that the selected term set or term has been associated with the field.
+
+ ![Screenshot of the New field panel showing the associated term set or term.](../media/content-understanding/content-assembly-associated-term.png)
+
+5. If you want users to be able to add multiple values corresponding to the term set or term, select **Allow multiple values**. Also, if the term set is configured as an open term set, you can select **Allow new values**. If you enable this option, users who generate documents from the modern template can add new terms to the term set and add those terms as field values.
+
+ > [!TIP]
+ > When you enable the **Allow new values** option (only allowed for open term sets), users are more likely to add redundant terms in the term store. Redundant terms can make it difficult for admins to manage a term set.
+
+### Associate a table with a SharePoint list or library
+
+On the **New field** panel:
+
+1. In the **Name** field, enter a relevant name for the field.
+
+ ![Screenshot of the template viewer showing the New field for associating a table field.](../media/content-understanding/content-assembly-associate-table-1.png)
+
+2. Select the table section in the document you want to create a field for. You can view the table selection in the **Fields** section.
+
+3. Confirm the selection, and then select **Next**.
+
+4. On the **Select a list for adding a source column** page, associate a SharePoint list or library to the table.
+
+ ![Screenshot of the Select a list for adding a source column page.](../media/content-understanding/content-assembly-associate-table-2.png)
+
+5. Once the list is selected, map the list columns to the table columns.
+
+ ![Screenshot of the template viewer showing how to map the list columns to the table columns.](../media/content-understanding/content-assembly-associate-table-3.png)
+
+ The associated list column names that match with the table header columns will be filled in automatically, which you can then modify.
+
+6. Next, map all the table columns to the list columns.
+
+ ![Screenshot of the template viewer showing how to map all the table columns with the list columns.](../media/content-understanding/content-assembly-associate-table-4.png)
+
+7. When all the table columns are mapped, you can see the table selection in the **Fields** section.
+
+ ![Screenshot of the template viewer showing the table selection in the New field panel.](../media/content-understanding/content-assembly-associate-table-5.png)
+
+When users generate documents from the template, they can select relevant list entries to be filled in, and the table rows will increase or decrease based on the number of row selections made.
+
+### Add an image field
+
+On the **New field** panel:
+
+1. In the **Name** field, enter a relevant name for the field.
+
+ ![Screenshot of the template viewer showing the New field for adding an image field.](../media/content-understanding/content-assembly-add-image-field.png)
+
+2. Select the image section in the document you want to create a field for. You can view the image name and the alt text (a description of the image) for the selected image in the **Fields** section.
+
+3. Confirm the selection, and then select **Next**.
+
+4. You can choose to allow authors who will fill in the field to either upload images from any sourceΓÇöOneDrive or SharePoint or from local storageΓÇöor restrict the entries by associating it to an image column in a SharePoint list.
+
+5. You can choose to control how the image selected by the author will be filled in the document. If you select the **Resize** checkbox, then the uploaded image will be scaled to the dimensions of the image selected for templatization. If not selected, then the image dimension of the image uploaded by the author will be persisted.
+
+ > [!TIP]
+ > When you enable the **Resize** option, users are more likely to have favorable results of the image dimensions in the template.
+
+## Save a modern template as a draft
+
+You can create as many fields as you think are necessary. When you're done, you can choose to save the template as a draft.
+
+1. Select **Save draft** to save the template as a draft and you can access it later.
+
+2. To view, edit, or publish saved drafts from the **Draft templates** dropdown menu in the **Modern templates**, select **New** > **Edit New menu** from the document library.
+
+## Publish a modern template
+
+When you have completed adding all relevant fields to the template and you want to make it available for use by other users in the document library, you can publish the template.
+
+1. Select **Publish** to publish the template to be used by other users in the organization to create documents.
+
+2. To view, edit, or unpublish *published* templates from the **Published templates** dropdown menu in the **Modern templates** section, select **New** > **Edit New menu** from the document library.
+
+## See also
+
+[Edit a modern template](content-assembly-edit-template.md)
+
+[Create a document from a modern template](content-assembly-create-document.md)
syntex Content Assembly https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/content-assembly.md
+
+ Title: Overview of content assembly in Microsoft Syntex
+++
+audience: admin
+++
+search.appverid:
+
+ - enabler-strategic
+ - m365initiative-syntex
+ms.localizationpriority: medium
+description: Learn about how to create documents and other content using a modern template in Microsoft Syntex.
++
+# Overview of content assembly in Microsoft Syntex
+
+You can use the content assembly capabilities in Microsoft Syntex to help you automatically generate standard repetitive business documents, such as contracts, statements of work, service agreements, letters of consent, sales pitches, and correspondence. You can do all these actions quicker, more consistently, and with fewer errors by creating modern templates and using those templates to generate documents.
+
+![Diagram of the flow of creating documents from a modern template.](../media/content-understanding/content-assembly-diagram.png)
+
+You upload an existing document to create a modern template, and then use that template to automatically generate new content using SharePoint lists or manual entries as a data source.
+
+> [!NOTE]
+> You must be a licensed Syntex user to access and use content assembly capabilities. You also must have permissions to manage SharePoint lists.
+
+## Requirements and limitations
+
+### Supported file types
+
+Only Microsoft Word documents (.docx/.doc extension) are currently supported for creating a template.
+
+### File limitations
+
+- The Word document you want to use as a modern template shouldn't include comments or have Track Changes enabled.
+
+- Because content controls are used in Word to create fields for the modern template, make sure any text fields for images aren't text-wrapped. If the document already contains content controls, remove them before you use it to create a modern template.
+
+### Current release limitations
+
+- The template and the document are associated with one document library. To use the template in another document library, you'll need to create the template again in that document library.
+
+- The uploaded document that is used to create the modern template will be saved as a separate copy and placed in the /forms directory of the document library. The original file on the disk will be unaffected.
+
+- You can create fields for text, and also fields for text within cells in a table. However, smart art and bulleted lists are currently not supported.
+
+- Once a document is created from a template, it's not associated with the template.
+
+## Differences between modern templates and other document templates
+
+|Feature |Modern templates |Other templates |
+||||
+|Licensing |Syntex license needed to access this offering. |Offered as a part of Microsoft E3 or E5 license. |
+|When to use each | You should use for generating standard transactional documents such as service agreements and statements of work when only specific parts of the document changes. Documents generated from modern templates ensure consistency and fewer chances of manual error and typos that occur when users change sections of the document in free flow. |You should use this method when you want to set a document as a sample for other users to refer. You can consider using regular templates for non-transactional documents such as sales pitches or executive summaries. |
+|Standardizing content generation |You can add fields and then associate with various data sources for only specific sections of the content to make it easy for users to generate documents once template is published. |Once uploaded, the file is kept as-is in the template. Any user using the template have to change the content accordingly. |
+|Data sources supported |You can associate fields with SharePoint lists and term store while creating templates. |Not applicable |
+|Document types supported |Only Microsoft Word documents (.docx/.doc extension) are currently supported for creating a template. |You can use any file to upload as template. |
+|Management of templates |Once template is created, you can edit or manage the template fields, rename the template, and republish for use. |Not applicable |
+|Draft version of templates |You can create draft versions of templates before finally publishing it for use by other users. |There's no capability to create drafts of regular templates. |
+|Workflows |You can automate document generation from templates by [setting up Power Automate workflows](automate-document-generation.md). |Workflows can't be configured with regular templates. |
+
+> [!div class="nextstepaction"]
+> [Get started > Create a modern template](content-assembly-modern-template.md)
+++
+
syntex Create A Classifier https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/create-a-classifier.md
+
+ Title: Create a classifier in Microsoft Syntex
++++
+audience: admin
++
+search.appverid:
+
+ - enabler-strategic
+ - m365initiative-syntex
+
+ms.localizationpriority: medium
+description: Learn how to create a classifier in Microsoft Syntex.
++
+# Create a classifier in Microsoft Syntex
+
+<sup>**Applies to:** &ensp; &#10003; Unstructured document processing </sup>
+
+Follow the instructions in [Create a model in Syntex](create-syntex-model.md) to create an unstructured document processing model in a content center. Or, follow the instructions in [Create a model on a local SharePoint site](create-local-model.md) to create the model on a local site. Then start with this article to begin training your model.
+
+</br>
+
+> [!VIDEO https://www.microsoft.com/videoplayer/embed/RE4CL0R]
+
+</br>
+
+A classifier is a type of model that you can use to automate identification and classification of a document type. For example, you might want to identify all *Contract Renewal* documents that are added to your document library, such as is shown in the following illustration.
+
+![Contract Renewal document.](../media/content-understanding/contract-renewal.png)
+
+Creating a classifier enables you to create a new [SharePoint content type](/sharepoint/governance/content-type-and-workflow-planning#content-type-overview) that will be associated to the model.
+
+When creating the classifier, you need to create *explanations* to define the model. This enables you to note common data that you would expect to consistently find this document type.
+
+Use examples of the document type ("example files") to "train" your model to identify files that have the same content type.
+
+To create a classifier, you need to:
+1. Name your model.
+2. Add your example files.
+3. Label your example files.
+4. Create an explanation.
+5. Test your model.
+
+> [!NOTE]
+> While your model uses a classifier to identify and classify document types, you can also choose to pull specific pieces of information from each file identified by the model. Do this by creating an **extractor** to add to your model. See [Create an extractor](create-an-extractor.md).
+
+## Name your model
+
+The first step to create your model is to give it a name:
+
+1. From the content center, select **New**, and then **Model**.
+
+2. On the **Options for model creation** page, select **Teaching method**.
+
+3. On the **Teaching method: Details** page, select **Next**.
+
+4. On the **Create a model with the teaching method** page, in the **Model name** field, type the name of the model. For example, if you want to identify contract renewal documents, you could name the model *Contract Renewal*.
+
+5. Choose **Create**. This creates a home page for the model.
+
+ ![Classifier model home page.](../media/content-understanding/model-home.png)
+
+When you create a model, you are also creating a new site content type. A content type represents a category of documents that have common characteristics and share a collection of columns or metadata properties for that particular content. SharePoint content types are managed through the [Content types gallery](https://support.microsoft.com/office/create-or-customize-a-site-content-type-27eb6551-9867-4201-a819-620c5658a60f). For this example, when you create the model, you are creating a new *Contract Renewal* content type.
+
+Select **Advanced settings** if you want to map this model to an existing enterprise content type in the SharePoint <a href="https://go.microsoft.com/fwlink/?linkid=2185074" target="_blank">Content type gallery</a> to use its schema. Enterprise content types are stored in the Content Type Hub in the SharePoint admin center and are syndicated to all sites in the tenant. Note that while you can use an existing content type to leverage its schema to help with identification and classification, you still need to train your model to extract information from files it identifies.</br>
+
+![Advanced settings.](../media/content-understanding/advanced-settings.png)
+
+## Add your example files
+
+On the model home page, add your examples files you will need to help train the model to identify your document type.
+
+<!
+</br>
+
+> [!VIDEO https://www.microsoft.com/videoplayer/embed/RE4D0iX]
+
+</br>
+>
+
+> [!NOTE]
+> You should use the same files for both classifier and [extractor training](create-an-extractor.md). You always have the option to add more later, but typically you add a full set of example files. Label some to train your model, and test the remaining unlabeled ones to evaluate model fitness.
+
+For your training set, you want to use both positive and negative examples:
+- Positive example: Documents that represent the document type. These contain strings and information that would always be in this type of document.
+- Negative example: Any other document that does not represent the document you want to classify.
+
+Be sure to use at least five positive examples and at least one negative example to train your model. You want to create additional ones to test your model after the training process.
+
+To add example files:
+
+1. On the model home page, in the **Add example files** tile, click **Add files**.
+2. On the **Select example files for your model** page, select your example files from the Training files library in the content center. If you had not already uploaded them there, choose to upload them now by clicking **Upload** to copy them to the Training files library.
+3. After selecting your example files to use to train the model, click **Add**.
+
+ ![Select example files.](../media/content-understanding/select-sample.png)
+
+## Label your example files
+
+After adding your example files, you need to label them as either positive or negative examples.
+
+1. From the model home page, on the **Classify files and run training** tile, click **Train classifier**.
+ This displays the label page that shows a listing of your example files, with the first file visible in the viewer.
+2. In the viewer on the top of the first example file, you should see text asking if the file is an example of the model you just created. If it is a positive example, select **Yes**. If it is a negative example, select **No**.
+3. From the **Labeled examples** list on the left, select additional files that you want to use as examples, and label them.
+
+ ![Classifier home page.](../media/content-understanding/classifier-home-page.png)
++
+> [!NOTE]
+> Label at least five positive examples. You must also label at least one negative example.
+
+## Create an explanation
+
+The next step is for you to create an explanation on the Train page. An explanation helps the model understand how to recognize the document. For example, the Contract Renewal documents always contain a *Request for additional disclosure* text string.
+
+> [!Note]
+> When used with extractors, an explanation identifies the string that you want to extract from the document.
+
+To create an explanation:
+
+1. From the model home page, select the **Train** tab to go to the Train page.
+2. On the Train page, in the **Trained files** section you should see a list of the sample files that you previously labeled. Select one of the positive files from the list, and it displays in the viewer.
+3. In the Explanation section, select **New** and then **Blank**.
+4. On the **Create an explanation** page:</br>
+ a. Type the **Name** (for example, "Disclosure Block").</br>
+ b. Select the **Type**. For the sample, select **Phrase list**, since you add a text string.</br>
+ c. In the **Type here** box, type the string. For the sample, add "Request for additional disclosure". You can select **Case sensitive** if the string needs to be case sensitive.</br>
+ d. Click **Save**.
+
+ ![Create explanation.](../media/content-understanding/explanation.png)
+
+5. The content center now checks to see if the explanation you created is complete enough to identify the remaining labeled example files correctly, as positive and negative examples. In the **Trained files** section, check the **Evaluation** column after the training has completed to see the results. The files show a value of **Match**, if the explanations you created was enough to match what you labeled as positive or negative.
+
+ ![Match value.](../media/content-understanding/match.png)
+
+ If you receive a **Mismatch** on the labeled files, you might need to create an additional explanation to provide the model more information to identify the document type. If this happens, click on the file to get more information about why the mismatch occurred.
+
+Once you've trained an extractor, that trained extractor can be used as an explanation. In the **Explanations** section, this is shown as a **Model reference**.
+
+![Screenshot of the Explanations section showing the type Model reference.](../media/content-understanding/explanations-model-reference.png)
+
+## Test your model
+
+If you received a match on your labeled sample files, you can now test your model on your remaining unlabeled example files that the model has not seen before. This is optional, but a useful step to evaluate the ΓÇ£fitnessΓÇ¥ or readiness of the model before using it, by testing it on files the model hasnΓÇÖt seen before.
+
+1. From the model home page, select the **Test** tab. This runs the model on your unlabeled sample files.
+2. In the **Test files** list, your example files display and shows if the model predicted them to be positive or negative. Use this information to help determine the effectiveness of your classifier in identifying your documents.
+
+ ![Test of unlabeled files.](../media/content-understanding/test-on-files.png)
+
+## See also
+
+[Create an extractor](create-an-extractor.md)
+
+[Explanation types](explanation-types-overview.md)
+
+[Apply a model](apply-a-model.md)
+
+[Syntex accessibility mode](accessibility-mode.md)
syntex Create A Content Center https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/create-a-content-center.md
+
+ Title: Create a content center in Microsoft Syntex
++++
+audience: admin
++
+search.appverid:
++
+ - enabler-strategic
+ - m365initiative-syntex
+ms.localizationpriority: medium
+description: Learn how to create a content center in Microsoft Syntex.
++
+# Create a content center in Microsoft Syntex
+
+<sup>**Applies to:** &ensp; &#10003; All custom models &ensp; | &ensp; &#10003; All prebuilt models</sup>
+
+<!
+</br>
+
+> [!VIDEO https://www.microsoft.com/videoplayer/embed/RE4CPSF]
+
+</br>
+>
+
+To create and manage enterprise models, you first need a content center. The content center is the model creation interface and also contains information about which document libraries published models have been applied to.
+
+ ![Select a doc library.](../media/content-understanding/content-center-page.png)
+
+You create a default content center during [setup](set-up-content-understanding.md). But a SharePoint admin can also choose to create additional centers as needed. While a single content center might be fine for environments for which you want a roll-up of all model activity, you might want to have additional centers for multiple departments within your organization, which might have different needs and permission requirements for their models.
+
+Additionally, if you want to try Syntex, you can create a content center using the instructions in this article without purchasing licenses. Unlicensed users can create models but can't apply them to a document library.
+
+> [!NOTE]
+> In a [Microsoft 365 Multi-Geo environment](../enterprise/microsoft-365-multi-geo.md), if you have a single default content center in your central location, you can only provide a roll-up of model activity from within that location. You currently cannot get a roll-up of model activity across farm-boundaries in Multi-Geo environment.
+
+## Create a content center
+
+A SharePoint admin can create a content center site like they would [create any other SharePoint site](/sharepoint/create-site-collection) through the admin center site provisioning panel.
+
+To create a new content center:
+
+1. On the Microsoft 365 admin center, go to the <a href="https://go.microsoft.com/fwlink/?linkid=2185220" target="_blank">**SharePoint admin center** > **Active sites**</a>.
+
+2. On the **Active sites** page, select **Create**, and then select **Other options**.
+
+3. On the **Choose a template** menu, select **Content center**.
+
+4. For the new site, provide a **Site name**, **Primary administrator**, and a **Language**.</br>
+
+ > [!NOTE]
+ > You can select a content center site to render in any of the available languages, but note that currently models can only be created for English files. Also note that like other site templates, the default site language isn't editable after the site is created.
+
+5. Select **Finished**.
+
+After you create a content center site, you'll see it listed on <a href="https://go.microsoft.com/fwlink/?linkid=2185220" target="_blank">**Active sites**</a> in the SharePoint admin center.
+
+### Give access to additional users
+
+After you create the site, you can give additional users access to the site through the standard [SharePoint site permissions model](/sharepoint/modern-experience-sharing-permissions).
+
+### Roll up of models in the default content center
+
+In Syntex, the first content center created during setup is the *default content center*. If subsequent content centers are created, their models are shown in the default content center view.
+
+![Screenshot of the Model library in the default content center.](../media/content-understanding/model-library-default-content-center.png)
+
+The **Models** library in the default content center view groups the created models by content center for a summary view of all models that have been created.
+
+> [!NOTE]
+> You can't change the designated default content center. It's always the first content center created during setup.
+
+## See also
+
+[Overview of model types](model-types-overview.md)
++
syntex Create A Form Processing Model https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/create-a-form-processing-model.md
+
+ Title: Train a structured document processing model in Microsoft Syntex
++++
+audience: admin
++
+search.appverid:
+
+ - enabler-strategic
+ - m365initiative-syntex
+
+ms.localizationpriority: medium
+description: Learn how to train a structured document processing model in Microsoft Syntex.
++
+# Train a structured document processing model in Microsoft Syntex
+
+<!
+</br>
+
+> [!VIDEO https://www.microsoft.com/videoplayer/embed/RE4GnhN]
+
+</br>
++
+Using [AI Builder](/ai-builder/overview)ΓÇöa feature in Microsoft Power AppsΓÇöSyntex users can create a [structured document processing](form-processing-overview.md) model directly from a SharePoint document library.
+>
+
+Follow the instructions in [Create a model in Syntex](create-syntex-model.md) to create a structured document processing model in a content center. Or, follow the instructions in [Create a model on a local SharePoint site](create-local-model.md) to create the model on a local site. Then use this article to train your model.
+
+![Diagram of the workflow to train an AI Builder model.](../media/content-understanding/train-aib-model.png)
+
+To train a structured document processing model, follow these steps:
+
+ - [Step 1: Add and analyze documents](#step-1-add-and-analyze-documents)
+ - [Step 2: Tag fields and tables](#step-2-tag-fields-and-tables)
+ - [Step 3: Train and publish your model](#step-3-train-and-publish-your-model)
+ - [Step 4: Use your model](#step-4-use-your-model)
+
+## Step 1: Add and analyze documents
+
+After you create your structured document processing model, the **Choose information to extract** page opens. Here you list all pieces of information that you want the AI model to extract from your documents, such as *Name*, *Address*, or *Amount*.
+
+> [!NOTE]
+> When you look for example files to use, see the [document processing model input document requirements and optimization tips](/ai-builder/form-processing-model-requirements).
+
+1. You first define the fields and tables you want to teach your model to extract on the **Choose information to extract** page. For detailed steps, see [Define fields and tables to extract](/ai-builder/create-form-processing-model#define-fields-and-tables-to-extract).
+
+2. You can create as many collections of document layouts you want your model to process. For detailed steps, see [Group documents by collections](/ai-builder/create-form-processing-model#group-documents-by-collections).
+
+3. After you create your collections and add at least five example files for each, AI Builder on Syntex will examine the uploaded documents to detect the fields and tables. This process usually takes a few seconds. When the analysis is complete, you can proceed with tagging the documents.
+
+## Step 2: Tag fields and tables
+
+You need to tag the documents to teach the model to understand the fields and table data you want to extract. For detailed steps, see [Tag documents](/ai-builder/create-form-processing-model#tag-documents).
+
+## Step 3: Train and publish your model
+
+1. After you create and train your model, you're ready to publish it and use it in SharePoint. To publish the model, select **Publish**. For detailed steps, see [Train and publish your document processing model](/ai-builder/form-processing-train).
+
+ ![Screenshot in showing the model details on the model home page.](../media/content-understanding/ai-builder-create-a-flow-1.png)
+
+2. After the model is published, you will go to the model home page. You'll then have the option to apply the model to a document library.
+
+ ![Screenshot of the model home page to apply the model a library.](../media/content-understanding/ai-builder-apply-model.png)
+
+## Step 4: Use your model
+
+1. In the document library model view, notice that the fields you selected now display as columns.
+
+ ![Document library model applied.](../media/content-understanding/doc-lib-view.png)
+
+2. Notice that the information link next to **Documents** notes that a forms processing model is applied to this document library.
+<!
+ ![Info button.](../media/content-understanding/info-button.png)
+>
+3. Upload files to your document library. Any files that the model identifies as its content type lists the files in your view and displays the extracted data in the columns.
+
+ ![Screenshot showing extracted data.](../media/content-understanding/doc-lib-done.png)
+
+> [!NOTE]
+> If a structured or freeform document processing model and an unstructured document processing model are applied to the same library, the file is classified using the unstructured document processing model and any trained extractors for that model. If there are any empty columns that match the document processing model, the columns will be populated using those extracted values.
+
+### Classification Date field
+
+When any custom model is applied to a document library, the **Classification Date** field is included in the library schema. By default, this field is empty. However, when documents are processed and classified by a model, this field is updated with a date-time stamp of completion.
+
+When a model is stamped with the **Classification Date**, you can use the **Send an email after Syntex processes a file** flow to notify users that a new file has been processed and classified by a model in the SharePoint document library.
+
+To run the flow:
+
+1. Select a file, and then select **Integrate** > **Power Automate** > **Create a flow**.
+
+2. On the **Create a flow** panel, select **Send an email after Syntex processes a file**.
+
+ ![Screenshot showing the Create a flow panel and flow option highlighted.](../media/content-understanding/integrate-create-flow.png)
+
+### Use flows to extract information
+
+> [!IMPORTANT]
+> The information in this section doesn't apply to the latest release of Syntex. It is left as reference only for the form processing models that were created in previous releases. In the latest release, you no longer need to configure the flows to process existing files.
+
+Two flows are available to process a selected file or batch of files in a library where a structured document processing model has been applied.
+
+- **Extract info from an image or PDF file with a document processing model** ΓÇö Use to extract text from a selected image or PDF file by running a document processing model. Supports a single selected file at a time, and supports only PDF files and image files (.png, .jpg, and .jpeg). To run the flow, select a file, and then select **Automate** > **Extract info**.
+
+ ![Screenshot showing the Automate menu with Extract info highlighted.](../media/content-understanding/automate-extract-info.png)
+
+- **Extract info from files with a document processing model** ΓÇö Use with document processing models to read and extract information from a batch of files. Processes up to 5,000 SharePoint files at a time. When you run this flow, there are certain parameters you can set. You can:
+
+ - Choose whether to include previously processed files (the default isn't to include previously processed files).
+ - Select the number of files to process (the default is 100 files).
+ - Specify the order in which to process the files (choices are by file ID, file name, file created time, or last modified time).
+ - Specify how you want the order sorted (ascending or descending order).
+
+ ![Screenshot showing the Run flow panel with parameter options highlighted.](../media/content-understanding/run-flow-panel.png)
+
+> [!NOTE]
+> The **Extract info from an image or PDF file with a document processing model** flow is automatically available for a library with a document processing model associated. The **Extract info from files with a document processing model** flow is a template that must be added to the library if required.
+
+## See also
+
+[Create a model in Microsoft Syntex](create-syntex-model.md)
+
+[Power Automate documentation](/power-automate/)
+
+[Training: Improve business performance with AI Builder](/training/paths/improve-business-performance-ai-builder/?source=learn)
syntex Create An Extractor https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/create-an-extractor.md
+
+ Title: Create an extractor in Microsoft Syntex
++++
+audience: admin
++
+search.appverid:
+
+ - enabler-strategic
+ - m365initiative-syntex
+ms.localizationpriority: medium
+description: Learn how to create an extractor in Microsoft Syntex.
++
+# Create an extractor in Microsoft Syntex
+
+<sup>**Applies to:** &ensp; &#10003; Unstructured document processing </sup>
+
+<br/>
+
+> [!VIDEO https://www.microsoft.com/videoplayer/embed/RE4CL2G]
+
+<br/>
+
+Before or after you create a classifier model to automate identification and classification of specific document types, you can optionally choose to add extractors to your model to pull out specific information from these documents. For example, you might want your model not only to identify all *Contract Renewal* documents added to your document library, but also to display the *Service Start date* for each document as a column value in the document library.
+
+You need to create an extractor for each entity in the document that you want to extract. In our example, we want to extract the **Service Start Date** for each **Contract Renewal** document that is identified by the model. We want to be able to see a view in the document library of all **Contract Renewal** documents, with a column that shows the **Service Start** date value of each document.
+
+> [!NOTE]
+> To create an extractor, you use the same files you previously uploaded to train the classifier.
+
+## Name your extractor
+
+1. From the model home page, in the **Create and train extractors** tile, select **Train extractor**.
+
+2. On the **New entity extractor** screen, type the name of your extractor in the **New extractor name** field. For example, name it **Service Start Date** if you want to extract the service start date from each Contract Renewal document. You can also choose to reuse a previously created column (for example, a managed metadata column).
+
+ By default, the column type is **Single line of text**. If you want to change the column type, select **Advanced settings** > **Column type**, and then select the type you want to use.
+
+ ![Screenshot of the Advanced settings portion of the New entity extractor panel showing the Column type option.](../media/content-understanding/advanced-settings-column-type.png)
+
+ > [!NOTE]
+ > For extractors with the column type **Single line of text**, the maximum character limit is 255. Any characters that you select exceeding the limit get truncated. To select greater than 255 characters, choose the **Multiple lines of text** column type when creating the extractor.
+ >
+ >By default, **Multiple lines of text** columns are created with a limit to the amount of text that can be added. In this case, extracted text might appear truncated. If this occurs, the column setting **Allow unlimited length in document libraries** can be used to remove the limit.
+
+3. When you're done, select **Create**.
+
+## Add a label
+
+The next step is to label the entity you want to extract in your example training files.
+
+Creating the extractor opens the extractor page. Here you see a list of your sample files, with the first file on the list displayed in the viewer.
+
+1. From the viewer, select the data that you want to extract from the files. For example, if you want to extract the *Start Service Date*, you highlight the date value in the first file (*Monday, October 14, 2022*). and then select **Save**. You should see the value display from the file in the Labeled examples list, under the **Label** column.
+2. Select **Next file** to autosave and open the next file in the list in the viewer. Or select **Save** and then select another file from the **Labeled examples** list.
+3. In the viewer, repeat steps 1 and 2, then repeat until you saved the label in all five files.
+
+ ![Advanced settings.](../media/content-understanding/select-service-start-date.png)
+
+Once you labeled five files, a notification banner displays informing you to move to training. You can choose to more label more documents or advance to training.
+
+### Use Find to search your file
+
+You can use the **Find** feature to search for an entity in your document that you want to label.
+
+ ![Find in file.](../media/content-understanding/find-feature.png)
+
+The Find feature is useful if you're searching a large document or if there are multiple instances of the entity in the document. If you find multiple instances, you can select the one you need in the search results to go to that location in the viewer to label it.
+
+## Add an explanation
+
+For our example, we're going to create an explanation that provides a hint about the entity format itself and variations it might have in the sample documents. For example, a date value can be in several different formats, such as:
+
+- 10/14/2022
+- October 14, 2022
+- Monday, October 14, 2022
+
+To help identify the *Service Start Date*, you can create a pattern explanation.
+
+1. In the Explanation section, select **New** and type a name (for example, *Date*).
+2. For Type, select **Pattern list**.
+3. For Value, provide the date variation as they appear in the sample files. For example, if you have date formats that appear as 0/00/0000, you enter any variations that appear in your documents, such as:
+ - 0/0/0000
+ - 0/00/0000
+ - 00/0/0000
+ - 00/00/0000
+4. Select **Save**.
+
+> [!NOTE]
+> For more learn more about explanation types, see [Explanation types](./explanation-types-overview.md).
+
+### Use the explanation library
+
+For creating explanations for items such as dates, it's easier to [use the explanation library](./explanation-types-overview.md) than to manually enter all variations. The explanation library is a set of pre-built phrase and pattern explanations. The library tries to provide all formats for common phrase or pattern lists, such as dates, phone numbers, zip codes, and many others.
+
+For the *Service Start Date* sample, it's more efficient to use the pre-built explanation for *Date* in the explanation library:
+
+1. In the **Explanation section**, select **New**, and then select **From explanation library**.
+2. From the explanation library, select **Date**. You can view all variations of date that are recognized.
+3. Select **Add**.
+
+ ![Explanation library.](../media/content-understanding/explanation-library.png)
+
+4. On the **Create an explanation** page, the *Date* information from the explanation library auto fills the fields. Select **Save**.
+
+ ![Date.](../media/content-understanding/date-explanation-library.png)
+
+## Train the model
+
+Saving your explanation starts the training. If your model has enough information to extract the data from your labeled example files, you'll see each file labeled with **Match**.
+
+![Match.](../media/content-understanding/match2.png)
+
+If the explanation doesn't have enough information to find the data you want to extract, each file will be labeled with **Mismatch**. You can select **Mismatched** files to see more information about why there was a mismatch.
+
+## Add another explanation
+
+Often the mismatch is an indication that the explanation we provided didn't provide enough information to extract the service start date value to match our labeled files. You might need to edit it, or add another explanation.
+
+For our example, notice that the text string *Start Service date of* always precedes the actual value. To help identify the Service Start Date, you need to create a phrase explanation.
+
+1. In the Explanation section, select **New**, and then type a name (for example, *Prefix String*).
+2. For the Type, select **Phrase list**.
+3. Use *Service Start Date of* as the value.
+4. Select **Save**.
+
+ ![Prefix string.](../media/content-understanding/prefix-string.png)
+
+## Train the model again
+
+Saving the explanation starts the training again, this time using both explanations in the example. If your model has enough information to extract the data from the labeled example files, you see each file labeled with **Match**.
+
+If you again receive a **Mismatch** on your labeled files, you likely need to create another explanation to provide the model more information to identify the document type, or consider making changes to your existing ones.
+
+## Test your model
+
+If you receive a match on your labeled sample files, you can now test your model on the remaining unlabeled example files. This step is optional, but useful to evaluate the "fitness" or readiness of the model before using it, by testing it on files the model hasn't seen before.
+
+1. From the model home page, select the **Test** tab. This will run the model on your unlabeled sample files.
+
+2. In the **Test files** list, your example files display to show if the model is able to extract the information you need. Use this information to help determine the effectiveness of your classifier in identifying your documents.
+
+ ![Test on your files.](../media/content-understanding/test-filies-extractor.png)
+
+## Further refine an extractor
+
+If you have duplicate entities and want to extract only one value or a certain number of values, you can set a rule to specify how you want it processed. To add a rule to refine extracted information, follow these steps:
+
+1. From the model home page, in the **Entity extractors** section, select the extractor you want to refine, and then select **Refine extracted info**.
+
+ ![Screenshot of the Entity extractors section showing the Refine extracted info option highlighted.](../media/content-understanding/refine-extracted-info.png)
+
+2. On the **Refine extracted info** page, select one of the following rules:
+
+ - Keep one or more of the first values
+ - Keep one or more of the last values
+ - Remove duplicate values
+ - Keep one or more of the first lines
+ - Keep one or more of the last lines
+
+ ![Screenshot of the Refine extracted info page showing the rules options.](../media/content-understanding/refine-extracted-info-page.png)
+
+3. Enter the number of lines or values you want to use, and then select **Refine**.
+
+4. If you want to edit a rule by changing the number of lines or values, select the extractor you want to edit, select **Refine extracted info**, change the number, and then select **Save**.
+
+5. When you test the extractor, you'll be able to see the refinement in the **Refinement result** column of the **Test Files** list.
+
+ ![Test Files list showing the Refinement result column.](../media/content-understanding/test-filies-extractor-2.png)
+
+6. If you want to delete a refinement rule on an extractor, select the extractor from which you want to remove the rule, select **Refine extracted info**, and then select **Delete**.
+
+## See also
+
+[Create a classifier](create-a-classifier.md)
+
+[Explanation types](explanation-types-overview.md)
+
+[Leverage term store taxonomy when creating an extractor](leverage-term-store-taxonomy.md)
+
+[Syntex accessibility mode](accessibility-mode.md)
syntex Create Local Model https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/create-local-model.md
+
+ Title: Create a model on a local SharePoint site with Microsoft Syntex
++++
+audience: admin
++
+search.appverid:
+
+ - enabler-strategic
+ - m365initiative-syntex
+ms.localizationpriority: medium
+description: Learn how to create a local model on a local SharePoint site with Microsoft Syntex.
++
+# Create a model on a local SharePoint site with Microsoft Syntex
+
+<sup>**Applies to:** &ensp; &#10003; All custom models &ensp; | &ensp; &#10003; All trained models</sup>
+
+Microsoft Syntex provides an option to create and train models locally on your own SharePoint site. These models can be used only on the site where they're created.
+
+> [!NOTE]
+> If you want to make your model discoverable and available for other users, you need to create an *enterprise model*. An enterprise model is a model that is created and trained in the [content center](create-a-content-center.md).
+
+By activating document classification and extraction on your SharePoint site, Syntex lets you classify files in document libraries, extract information from new files, and automate activities based on extracted information.
+
+When you activate local model creation, the following lists and libraries will be added to your site:
+
+- Models document library
+- Training files document library
+- Explanation templates list
+- Model usage list
+
+A model is automatically promoted to the current site only when the model first has been applied to any library in the site. This makes the model discoverable in the list of available site models and available for any other library in the site. Until the model is applied to a library in the site, it is unavailable. Similarly, when a model is removed from all the libraries in the site, it is also removed from the list of available site models.
+
+This feature is available for all [model types](model-types-overview.md).
+
+## Create a model on a local site
+
+1. From a SharePoint document library, select the files you want to analyze, and then select **Classify and extract**.
+
+ ![Screenshot of a SharePoint document library with the Classify and extract option highlighted.](../media/content-understanding/local-model-classify-and-extract-option.png)
+
+2. The first time you use this feature, you're activating Syntex on your site. You'll see the following message.
+
+ ![Screenshot of the Activate document classification and extraction infomation page.](../media/content-understanding/local-model-first-run-activate-message.png)
+
+ > [!NOTE]
+ > You must have the Manage Web Site permission to perform administration tasks and manage content for the site. This would be a site owner. Once the feature is activated, anyone with the Manage Lists permission will be able to create and manage models.
+
+3. Select **Activate** to continue. You'll see the following message.
+
+ ![Screenshot of the Document classification and extraction activated message with the option to Create a model.](../media/content-understanding/local-model-activated-message.png)
+
+4. Select **Create a model**.
+
+5. On the **Create a model** panel, type the name of the model, add a description, and then select **Create**.
+
+ ![Screenshot of the Create a model panel.](../media/content-understanding/local-model-create-a-model.png)
+
+6. Proceed to [train your custom model](apply-a-model.md) or to [configure your trained model](prebuilt-overview.md) using the files that you selected.
+
+7. When done, the **Add to library** panel opens.
+
+ ![Screenshot of the Add to library panel showing the site and libraries applied.](../media/content-understanding/local-model-add-to-library-panel.png)
+
+8. On the **Add to library** panel, you'll see the name of your SharePoint site and the document library that the model will be applied to. If you want to apply the model to a different library, select **Back to libraries**, and choose the library you want to use. Then select **Add**.
+
+9. On the model home page, in the **Where the model is applied on this site** section, you can see the libraries that have the model applied. To apply the model to other libraries on the site, select **Apply model**.
+
+ ![Screenshot of the model home page showing the Where the model is applied on the site section.](../media/content-understanding/local-model-home-page.png)
+
+> [!NOTE]
+> When a local model is applied to a single library, it becomes available for discovery for application to other libraries in same site.
syntex Create Syntex Model https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/create-syntex-model.md
+
+ Title: Create an enterprise model in Microsoft Syntex
++++
+audience: admin
++
+search.appverid:
+
+ - enabler-strategic
+ - m365initiative-syntex
+ms.localizationpriority: medium
+description: Learn how to create a custom or prebuilt model with Microsoft Syntex.
++
+# Create an enterprise model in Microsoft Syntex
+
+<sup>**Applies to:** &ensp; &#10003; All custom models &ensp; | &ensp; &#10003; All prebuilt models</sup>
+
+An enterprise model is created and trained in the [content center](create-a-content-center.md), and can be discovered by others to use. Whether you want to create a custom model or use a prebuilt model, you can do so from any of these places in Microsoft Syntex:
+
+- From the **Models** library
+- From the [content center](create-a-content-center.md) home page
+- From any document library in a site where Syntex has been activated
+
+For this article, we start in the **Models** library. For information about the different model types, see [Overview of model types in Syntex](model-types-overview.md).
+
+If you want to create a local model, see [Create a model on a local SharePoint site](create-local-model.md).
+
+## Create a model
+
+From the **Models** library, select **Create a model**.
+
+![Screenshot of the Models library showing the Create a model button.](../media/content-understanding/create-a-model-from-the-models-page.png)
+
+On the **Options for model creation** page, there are two sections:
+
+- [**Train a custom model**](#train-a-custom-model)
+
+- [**Set up a prebuilt model**](#set-up-a-prebuilt-model)
+
+![Screenshot of the Options for model creation page showing the custom models and prebuilt models.](../media/content-understanding/options-for-model-creation.png)
+
+> [!NOTE]
+> All model options might not be available. These options are configured by your Microsoft 365 admin.
+
+## Train a custom model
+
+The **Train a custom model** section shows the training method for the type of custom models you want to create.
+
+![Screenshot of the Train a custom model section on the Options for model creation page.](../media/content-understanding/build-a-custom-model-section.png)
+
+- **Teaching method** ΓÇô Creates an [unstructured document processing model](document-understanding-overview.md).
+
+- **Freeform selection method** ΓÇô Creates a [freeform document processing model](freeform-document-processing-overview.md).
+
+- **Layout method** ΓÇô Creates a [structured document processing model](form-processing-overview.md).
+
+Select one of the following tabs to continue with the custom model you want to use.
+
+# [Teaching method](#tab/teaching-method)
+
+Use the **Teaching method** to create an [unstructured document processing model](document-understanding-overview.md).
+
+1. Select **Teaching method**.
+
+2. On the **Teaching method: Details** page, you'll find more information about the model. If you want to proceed with creating the model, select **Next**.
+
+3. On the right panel of the **Create a model with the teaching method** page, enter the following information.
+
+ - **Model name** ΓÇô Enter the name of the model, for example *Service agreements*.
+
+ - **Description** ΓÇô Enter information about how this model will be used.
+
+ ![Screenshot of the right panel of the Create a model with the teaching method page.](../media/content-understanding/create-a-model-panel.png)
+
+4. Under **Advanced settings**:
+
+ - In the **Content type** section, choose whether to create a new content type or to use an existing one.
+
+ - In the **Compliance** section, under **Retention labels**, select the retention label you want to add. Under **Sensitivity labels**, select the sensitivity label you want to add. If a compliance label has been already applied to the library where the file is stored, it will be shown.
+
+5. When you're ready to create the model, select **Create**.
+
+6. You're now ready to [train the model](create-a-classifier.md).
+
+# [Freeform selection method](#tab/freeform-selection-method)
+
+Use the **Freeform selection method** to create a [freeform document processing model](freeform-document-processing-overview.md).
+
+1. Select **Freeform selection method**.
+
+2. On the **Freeform selection method: Details** page, you'll find more information about the model. If you want to proceed with creating the model, select **Next**.
+
+3. On the right panel of the **Create a model with the freeform selection method** page, enter the following information.
+
+ - **Model name** ΓÇô Enter the name of the model, for example *Service agreements*.
+
+ - **Description** ΓÇô Enter information about how this model will be used.
+
+ ![Screenshot of the right panel of the Create a model with the Freeform selection method page.](../media/content-understanding/create-a-model-panel.png)
+
+4. Under **Advanced settings**:
+
+ - In the **Content type** section, choose whether to create a new content type or to use an existing one.
+
+ - In the **Compliance** section, under **Retention labels**, select the retention label you want to add. If a compliance label has been already applied to the library where the file is stored, it will be shown.
+
+ > [!NOTE]
+ > Sensitivity labels are not available for **Freeform selection method** (freeform document processing models) at this time.
+
+5. When you're ready to create the model, select **Create**.
+
+6. You're now ready to [train the model](train-freeform-document-processing-model.md).
+
+ > [!NOTE]
+ > When published, this model type is available for reuse by others who do not own the model. Currently, this model can be edited and shared for editing only by the model owner.
+
+# [Layout method](#tab/layout-method)
+
+Use the **Layout method** to create a [structured document processing model](form-processing-overview.md).
+
+1. Select **Layout method**.
+
+2. On the **Layout method: Details** page, you'll find more information about the model. If you want to proceed with creating the model, select **Next**.
+
+3. On the right panel of the **Create a model with the layout method** page, enter the following information.
+
+ - **Model name** ΓÇô Enter the name of the model, for example *Service agreements*.
+
+ - **Description** ΓÇô Enter information about how this model will be used.
+
+ ![Screenshot of the right panel of the Create a model with the layout method page.](../media/content-understanding/create-a-model-panel.png)
+
+4. Under **Advanced settings**:
+
+ - In the **Content type** section, choose whether to create a new content type or to use an existing one.
+
+ - In the **Compliance** section, under **Retention labels**, select the retention label you want to add. If a compliance label has been already applied to the library where the file is stored, it will be shown.
+
+ > [!NOTE]
+ > Sensitivity labels are not available for **Layout method** (structured document processing models) at this time.
+
+5. When you're ready to create the model, select **Create**.
+
+6. You're now ready to [train the model](create-a-form-processing-model.md).
+
+ > [!NOTE]
+ > When published, this model type is available for reuse by others who do not own the model. Currently, this model can be edited and shared for editing only by the model owner.
+++
+## Set up a prebuilt model
+
+The **Set up a prebuilt model** section shows the types of prebuilt models you can use.
+
+![Screenshot of the Use a prebuilt model section on the Set up a prebuilt model page.](../media/content-understanding/use-a-trained-model-section.png)
+
+- **Invoice processing**
+
+- **Receipt processing**
+
+Select one of the following tabs to continue with the prebuilt model you want to use.
+
+# [Invoice processing](#tab/invoice-processing)
+
+1. Select **Invoice processing**.
+
+2. On the **Invoice processing: Details** page, you'll find more information about the model. If you want to proceed with using the model, select **Next**.
+
+3. On the right panel of the **Create an invoice processing model** page, enter the following information.
+
+ - **Model name** ΓÇô Enter the name of the model, for example *Office expenses*.
+
+ - **Description** ΓÇô Enter information about how this model will be used.
+
+ ![Screenshot of the right panel of the Create an invoice processing model page.](../media/content-understanding/create-a-model-panel.png)
+
+4. Under **Advanced settings**:
+
+ - In the **Content type** section, choose whether to create a new content type or to use an existing one.
+
+ - In the **Compliance** section, under **Retention labels**, select the retention label you want to add. If a retention label has been already applied to the library where the file is stored, it will be selected.
+
+ > [!NOTE]
+ > Sensitivity labels are not available for prebuilt models at this time.
+
+5. When you're ready to create the model, select **Create**.
+
+6. You're now ready to [complete setting up the model](prebuilt-model-invoice.md).
+
+# [Receipt processing](#tab/receipt-processing)
++
+1. Select **Receipt processing**.
+
+2. On the **Receipt processing: Details** page, you'll find more information about the model. If you want to proceed with using the model, select **Next**.
+
+2. On the right panel of the **Create a receipt processing model** page, enter the following information.
+
+ - **Model name** ΓÇô Enter the name of the model, for example *Office expenses*.
+
+ - **Description** ΓÇô Enter information about how this model will be used.
+
+ ![Screenshot of the right panel of the Create a model to process receipts page.](../media/content-understanding/create-a-model-panel.png)
+
+3. Under **Advanced settings**:
+
+ - In the **Content type** section, choose whether to create a new content type or to use an existing one.
+
+ - In the **Compliance** section, under **Retention labels**, select the retention label you want to add. If a retention label has been already applied to the library where the file is stored, it will be selected.
+
+ > [!NOTE]
+ > Sensitivity labels are not available for prebuilt models at this time.
+
+4. When you're ready to create the model, select **Create**.
+
+5. You're now ready to [complete setting up the model](prebuilt-model-receipt.md).
+++++
+<!
+### Teaching method
+
+Use the **Teaching method** to create an [unstructured document processing model](document-understanding-overview.md).
+
+1. Select **Teaching method**.
+
+2. On the **Teaching method: Details** page, you'll find more information about the model. If you want to proceed with creating the model, select **Next**.
+
+3. On the right panel of the **Create a model with the teaching method** page, enter the following information.
+
+ - **Model name** ΓÇô Enter the name of the model, for example *Service agreements*.
+
+ - **Description** ΓÇô Enter information about how this model will be used.
+
+ ![Screenshot of the right panel of the Create a model with the teaching method page.](../media/content-understanding/create-a-model-panel.png)
+
+4. Under **Advanced settings**:
+
+ - In the **Content type** section, choose whether to create a new content type or to use an existing one.
+
+ - In the **Compliance** section, under **Retention labels**, select the retention label you want to add. Under **Sensitivity labels**, select the sensitivity label you want to add. If a compliance label has been already applied to the library where the file is stored, it will be shown.
+
+5. When you are ready to create the model, select **Create**.
+
+6. You are now ready to [train the model](create-a-classifier).
+
+### Freeform selection method
+
+Use the **Freeform selection method** to create a [freeform document processing model](freeform-document-processing-overview.md).
+
+1. Select **Freeform selection method**.
+
+2. On the **Freeform selection method: Details** page, you'll find more information about the model. If you want to proceed with creating the model, select **Next**.
+
+3. On the right panel of the **Create a model with the freeform selection method** page, enter the following information.
+
+ - **Model name** ΓÇô Enter the name of the model, for example *Service agreements*.
+
+ - **Description** ΓÇô Enter information about how this model will be used.
+
+ ![Screenshot of the right panel of the Create a model with the Freeform selection method page.](../media/content-understanding/create-a-model-panel.png)
+
+4. Under **Advanced settings**:
+
+ - In the **Content type** section, choose whether to create a new content type or to use an existing one.
+
+ - In the **Compliance** section, under **Retention labels**, select the retention label you want to add. If a compliance label has been already applied to the library where the file is stored, it will be shown.
+
+ > [!NOTE]
+ > Sensitivity labels are not available for **Freeform selection method** (freeform document processing models) at this time.
+
+5. When you are ready to create the model, select **Create**.
+
+6. You are now ready to [train the model](train-freeform-document-processing-model.md).
+
+ > [!NOTE]
+ > When published, this model type is available for reuse by others who do not own the model. Currently, this model can be edited and shared for editing only by the model owner.
+
+### Layout method
+
+Use the **Layout method** to create a [structured document processing model](form-processing-overview.md).
+
+1. Select **Layout method**.
+
+2. On the **Layout method: Details** page, you'll find more information about the model. If you want to proceed with creating the model, select **Next**.
+
+3. On the right panel of the **Create a model with the layout method** page, enter the following information.
+
+ - **Model name** ΓÇô Enter the name of the model, for example *Service agreements*.
+
+ - **Description** ΓÇô Enter information about how this model will be used.
+
+ ![Screenshot of the right panel of the Create a model with the layout method page.](../media/content-understanding/create-a-model-panel.png)
+
+4. Under **Advanced settings**:
+
+ - In the **Content type** section, choose whether to create a new content type or to use an existing one.
+
+ - In the **Compliance** section, under **Retention labels**, select the retention label you want to add. If a compliance label has been already applied to the library where the file is stored, it will be shown.
+
+ > [!NOTE]
+ > Sensitivity labels are not available for **Layout method** (structured document processing models) at this time.
+
+5. When you are ready to create the model, select **Create**.
+
+6. You are now ready to [train the model](create-a-form-processing-model.md).
+
+ > [!NOTE]
+ > When published, this model type is available for reuse by others who do not own the model. Currently, this model can be edited and shared for editing only by the model owner.
+
+## Set up a prebuilt model
+
+1. In the **Set up a prebuilt model** section, view the types of prebuilt models you can use. Select the type of prebuilt model you want to learn more about or to start using.
+
+ ![Screenshot of the Use a prebuilt model section on the Set up a prebuilt model page.](../media/content-understanding/use-a-trained-model-section.png)
+
+ - [**Invoice processing**](#invoice-processing)
+
+ - [**Receipt processing**](#receipt-processing)
+
+2. When you select a prebuilt model, the next page will show you more information about the model. If you want to continue to create the model, select **Next**.
+
+### Invoice processing
+
+1. Select **Invoice processing**.
+
+2. On the **Invoice processing: Details** page, you'll find more information about the model. If you want to proceed with using the model, select **Next**.
+
+3. On the right panel of the **Create an invoice processing model** page, enter the following information.
+
+ - **Model name** ΓÇô Enter the name of the model, for example *Office expenses*.
+
+ - **Description** ΓÇô Enter information about how this model will be used.
+
+ ![Screenshot of the right panel of the Create an invoice processing model page.](../media/content-understanding/create-a-model-panel.png)
+
+4. Under **Advanced settings**:
+
+ - In the **Content type** section, choose whether to create a new content type or to use an existing one.
+
+ - In the **Compliance** section, under **Retention labels**, select the retention label you want to add. If a retention label has been already applied to the library where the file is stored, it will be selected.
+
+ > [!NOTE]
+ > Sensitivity labels are not available for prebuilt models at this time.
+
+5. When you are ready to create the model, select **Create**.
+
+6. You are now ready to [complete setting up the model](prebuilt-model-invoice.md).
+
+### Receipt processing
+
+1. Select **Receipt processing**.
+
+2. On the **Receipt processing: Details** page, you'll find more information about the model. If you want to proceed with using the model, select **Next**.
+
+2. On the right panel of the **Create a receipt processing model** page, enter the following information.
+
+ - **Model name** ΓÇô Enter the name of the model, for example *Office expenses*.
+
+ - **Description** ΓÇô Enter information about how this model will be used.
+
+ ![Screenshot of the right panel of the Create a model to process receipts page.](../media/content-understanding/create-a-model-panel.png)
+
+3. Under **Advanced settings**:
+
+ - In the **Content type** section, choose whether to create a new content type or to use an existing one.
+
+ - In the **Compliance** section, under **Retention labels**, select the retention label you want to add. If a retention label has been already applied to the library where the file is stored, it will be selected.
+
+ > [!NOTE]
+ > Sensitivity labels are not available for prebuilt models at this time.
+
+4. When you are ready to create the model, select **Create**.
+
+5. You are now ready to [complete setting up the model](prebuilt-model-receipt.md).
+>
syntex Delete A Model https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/delete-a-model.md
+
+ Title: Delete a model in Microsoft Syntex
+++
+audience: admin
+++
+search.appverid:
+
+ - enabler-strategic
+ - m365initiative-syntex
+ms.localizationpriority: medium
+description: Learn how to delete a model in Microsoft Syntex.
++
+# Delete a model in Microsoft Syntex
+
+<sup>**Applies to:** &ensp; &#10003; All custom models &ensp; | &ensp; &#10003; All prebuilt models</sup>
+
+At some point, you might want to delete a model. Before you delete the model, you must first remove the model from all of the SharePoint document libraries where it has been applied.
+
+## Remove a model from a library
+
+You can remove a model from a document library either from the model home page, or from the document library (**Automate** > **View applied models** > **Remove from library**).
+
+> [!NOTE]
+> Deleting a model does not delete the associated content type.
+
+## Delete a model
+
+Follow these steps to delete a model.
+
+1. Make sure the model has been [removed](#remove-a-model-from-a-library) from its document library.
+
+2. From the content center, select **Models** to see your models list.
+
+3. On the **Models** page, select the model you want to delete.
+
+4. By using either the ribbon or the **Show actions** button (next to the model name), select **Delete**.
+
+ ![Screenshot of the Models page showing a selected model with the Delete options highlighted.](../media/content-understanding/select-model-delete.png)
+
+5. On the **Delete model** panel, select **Delete**.
+
+## See also
+
+[Rename a model](rename-a-model.md)
+
syntex Difference Between Document Understanding And Form Processing Model https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/difference-between-document-understanding-and-form-processing-model.md
+
+ Title: Compare custom models in Microsoft Syntex
++++
+audience: admin
++
+search.appverid:
+
+ - enabler-strategic
+ - m365initiative-syntex
+ms.localizationpriority: medium
+description: Learn about key differences between custom models in Microsoft Syntex.
++
+# Compare custom models in Microsoft Syntex
+
+Use the following table to see differences in custom models to help identify the most appropriate model to use for your needs.
+
+| Feature | Unstructured document processing | Freeform document processing | Structured document processing |
+| - | - | - | - |
+| Associated with this training method in the UI | ![Tile for teaching method.](../media/content-understanding/teaching-method-tile.png) | ![Tile for freeform seletion method.](../media/content-understanding/freeform-selection-method-tile.png) | ![Tile for layout method.](../media/content-understanding/layout-method-tile.png) |
+| Use for this type of content | Unstructured or semi-structured file formats, for example Office documents where there are differences in the layout, but still similar information to be extracted. | Unstructured and free-form file formats, for example documents that have no set structure such as letters, contracts, and statements of work. | Structured and semi-structured file formats, for example PDFs for forms content such as invoices or purchase orders where the layout and formatting is similar. |
+| Model creation | Model created in SharePoint in a new site, the content center. | Model created in [AI Builder](/ai-builder/overview) with seamless access from SharePoint document library.| Model created in [AI Builder](/ai-builder/overview) with seamless access from SharePoint document library. |
+| Classification type | Trainable classifier with optional extractors using machine teaching to assign document location on what data to extract. | Not applicable | Not applicable |
+| Locations | Can be applied to multiple libraries. | Can be applied to multiple libraries. | Can be applied to multiple libraries. |
+| Supported file types | Train on 5-10 .pdf, Office, or email files, including negative examples.<br>Office files are truncated at 64,000 characters. OCR-scanned files are limited to 20 pages. Supports more than 20 file types. See [supported file types](requirements-and-limitations.md#unstructured-document-processing). | Train on .pdf, .jpg, or .png format, total 50 MB and 500 pages. | Train on .pdf, .jpg, or .png format, total 50 MB and 500 pages. |
+| Integrate with managed metadata | Yes, by training entity extractor referencing a configured managed metadata field. | No | No |
+| Compliance feature integration with Microsoft Purview Information Protection | Set published retention labels.<br>Set published sensitivity labels. | Set retention labels is coming. <br>Set sensitivity labels is coming. | Set published retention labels. <br>Set sensitivity labels is coming. |
+| Supported regions| Available in all regions. | Relies on Power Platform. For information about global availability for Power Platform and AI Builder, see [Power Platform availability](https://dynamics.microsoft.com/geographic-availability/). | Relies on Power Platform. For information about global availability for Power Platform and AI Builder, see [Power Platform availability](https://dynamics.microsoft.com/geographic-availability/). |
+| Transactional cost | Not applicable | Uses AI Builder credits.<br>3,500 credits are included for each Syntex license per month.<br>1 million credits will allow processing of 2,000 file pages. | Uses AI Builder credits.<br>3,500 credits are included for each Syntex license per month.<br>1 million credits will allow processing of 2,000 file pages. |
+| Capacity | No capacity restrictions. | Uses the default Power Platform environment (custom environments with Dataverse database supported). | Uses the default Power Platform environment (custom environments with Dataverse database supported). |
+| Supported languages| Models work on all Latin alphabet languages. In addition to English: German, Swedish, French, Spanish, Italian, and Portuguese. | Current language support is for English. | Language support for [73 languages](/ai-builder/form-processing-model-requirements.md#languages-supported). |
+
+## See also
+
+[Training: Improve business performance with AI Builder](/training/paths/improve-business-performance-ai-builder/?source=learn)
++
syntex Discover Other Trained Models https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/discover-other-trained-models.md
+
+ Title: Discover other trained models in Microsoft Syntex
++++
+audience: admin
++
+search.appverid:
+
+ - enabler-strategic
+ - m365initiative-syntex
+ms.localizationpriority: medium
+description: Learn how to find trained models that have been applied to other content centers in Microsoft Syntex.
++
+# Discover other trained models in Microsoft Syntex
+
+<sup>**Applies to:** &ensp; &#10003; All custom models &ensp; | &ensp; &#10003; All prebuilt models</sup>
+
+Before you create a new model, you might consider whether to reuse an existing one. You can find and evaluate trained models that were created by others in your organization. This might include shared enterprise models trained in a content center or other local models created in the same site. Select the model that is most useful for classifying your files or extracting specific information from them.
+
+## Discover other trained models
+
+To find trained models that might be suitable for your content:
+
+1. In the document library for your model, select **Classify and extract**.
+
+2. On the **Review models and apply new ones** page, you can review the applied models and the models that are available to be applied to your document library.
+
+ ![Screenshot of the Review models and apply new ones page showing the Applied and Available tabs.](../media/content-understanding/review-models-apply-new-ones.png)
+
+ - On the **Applied** tab, see the models that have been applied to your library. Select **View model details** to see information about the model, such as description, extractors, and other settings.
+
+ - On the **Available** tab, see the trained models that are available to be applied to your library.
+
+## Apply a trained model to your library
+
+You can evaluate trained models against your content to help you find the most appropriate one. To select a model that you want to apply to your library:
+
+1. On the **Review models and apply new ones** page, select the **Available** tab to review the models in the list.
+
+ ![Screenshot of the Review models and apply new ones page showing the models on the Available tab.](../media/content-understanding/available-models-to-apply.png)
+
+2. Choose the model that you think will get you the best results, select **View model details**, and then select **Apply to library**.
+
+## Get a recommendation for a trained model
+
+If you're unsure which model is the best fit for your files, you can ask for a recommendation. Your recommendation could include up to 10 models.
+
+1. On the **Review models and apply new ones** page, select the **Available** tab.
+
+2. On the first tile, select **Get recommendation**.
+
+ ![Screenshot of the Review models and apply new ones page showing the Get recommendation option on the Available tab.](../media/content-understanding/get-recommendation.png)
+
+3. On the **Select one or more models for analysis** page, select the models that you think might be the best fit, and then select **Next**.
+
+ ![Screenshot of the Select one or more models page showing the recommended models with two models selected.](../media/content-understanding/recommendation-results.png)
+
+4. On the **Select a file to analyze** page, select a file of the same or similar type that will be stored in your library. Then choose **Select**.
+
+ ![Screenshot of the Select a file to analyze page showing the files available with one file selected.](../media/content-understanding/file-to-analyze.png)
+
+5. On the **Review results and select a model** page, under **Our recommendation**, you'll see the recommended file. You don't have to apply the recommended model. You can choose to apply another model if you think it's a better fit.
+
+ ![Screenshot of the Review results and select a model page showing the recommended models.](../media/content-understanding/review-results.png)
+
+6. For the model you think will get you the best results, select **View model details**, and then select **Apply to library**.
+
+7. If there are no recommended models based on the selected file, you can go back and select another file or select different models.
+
+## Remove an applied model
+
+> [!NOTE]
+> A model has to be removed from all SharePoint document libraries before it can be [deleted](delete-a-model.md) or [renamed](rename-a-model.md).
+
+To remove an applied model from your document library:
+
+1. On the **Review models and apply new ones** page, on the **Applied** tab, see the models that have been applied to your library.
+
+2. On the model you want to remove, select **View model details**, and then select **Remove from library**.
+
+<!
+## Change the view in a document library
+
+>
+
+## See also
+
+[Share an enterprise model](model-discovery.md)
+
+[Choose the view in a document library](choose-library-view.md)
syntex Document Understanding Overview https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/document-understanding-overview.md
+
+ Title: Overview of unstructured document processing in Microsoft Syntex
++++
+audience: admin
+++
+search.appverid:
+
+ - enabler-strategic
+ - m365initiative-syntex
+ms.localizationpriority: medium
+description: Learn about the unstructured document processing model in Microsoft Syntex.
++
+# Overview of unstructured document processing in Microsoft Syntex
+
+> [!NOTE]
+> *Unstructured document processing* was known as *document understanding* in previous releases.
+
+Use the unstructured document processing model ([teaching method](create-syntex-model.md#train-a-custom-model)) to automatically classify files and extract information. It works best for unstructured documents, such as letters or contracts.
+
+The unstructured document processing model (formerly known as *document understanding model*) uses artificial intelligence (AI) to process documents. These documents must have text that can be identified based on phrases or patterns. The identified text designates both the type of file it is (its classification) and what you'd like to extract (its extractors).
+
+</br>
+
+> [!VIDEO https://www.microsoft.com/videoplayer/embed/RE4CSu7]
+
+</br>
+
+> [!NOTE]
+> For more information about how to use Syntex and scenario examples, see [Get started driving adoption of Microsoft Syntex](./adoption-getstarted.md) and [Scenarios and use cases for Microsoft Syntex](./adoption-scenarios.md).
+
+Unstructured document processing models are created and managed in a type of SharePoint site called a [content center](create-a-content-center.md). When applied to a SharePoint document library, the model is associated with a content type has columns to store the information being extracted. The content type you create is stored in the SharePoint content type gallery. You can also choose to use existing content types to use their schema.
+
+> [!NOTE]
+> Read-only or sealed content types can't be updated, so they can't be used in a model.
+
+Add [classifiers](create-a-classifier.md) and [extractors](create-an-extractor.md) to your unstructured document processing models to do the following actions:
+
+- Classifiers are used to identify and classify documents that are uploaded to the document library. For example, a classifier can be "trained" to identify all *contract renewal* documents that are uploaded to the library. The contract renewal content type is defined by you when you create your classifier.
+
+- Extractors pull information from these documents. For example, for each contract renewal document identified in your document library, columns will display that show the *Service Start Date* and *Client* for each document.
+
+You can use example files to train and test your classifiers and extractors in your model. Example files provide your model examples of what to look for when trying to identify and extract data from files. For example, you would train your contract renewal classifiers and extractors with examples of contract renewal documents your company works with. You can also use example files to test the effectiveness of your model.
+
+After publishing your model, use the content center to apply it to any SharePoint document library that you have access to.
+
+## Requirements
+
+For information about requirements to consider when choosing this model, see [Requirements and limitations for models in Microsoft Syntex](requirements-and-limitations.md#unstructured-document-processing).
+
+## See also
+
+[Compare custom models](difference-between-document-understanding-and-form-processing-model.md)
+
syntex Duplicate A Model https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/duplicate-a-model.md
+
+ Title: Duplicate a model in Microsoft Syntex
+++
+audience: admin
+++
+search.appverid:
+
+ - enabler-strategic
+ - m365initiative-syntex
+ms.localizationpriority: medium
+description: Learn how and why to duplicate a model in Microsoft Syntex.
++
+# Duplicate a model in Microsoft Syntex
+
+<sup>**Applies to:** &ensp; &#10003; Unstructured document processing </sup>
+
+Duplicating an unstructured document processing model can save you time and effort if you need to create a new model, and know that an existing model is very similar to what you need.
+
+For example, an existing model named ΓÇ£ContractsΓÇ¥ classifies the same files you need to work with. Your new model will extract some of the existing data, but will need to be updated to extract some additional data. Instead of creating and training a new model from scratch, you can use the duplicate model feature to make a copy of the Contracts model, which will also copy all associated training items, such as example files and entity extractors.
+
+When you duplicate the model, after you rename it (for example, to ΓÇ£Contract RenewalsΓÇ¥), you can then make updates to it. For example, you can choose to remove some of the existing extracted fields that you donΓÇÖt need, and then train the model to extract a new one (for example, ΓÇ£Renewal dateΓÇ¥).
+
+## Duplicate a model
+
+Follow these steps to duplicate an unstructured document processingmodel.
+
+1. From the content center, select **Models** to see your models list.
+
+2. On the **Models** page, select the model you want to duplicate.
+
+3. By using either the ribbon or the **Show actions** button (next to the model name), select **Duplicate**.</br>
+
+ ![Screenshot of the Models page showing a selected model with the Duplicate options highlighted.](../media/content-understanding/select-model-duplicate-both.png) </br>
+
+4. On the **Duplicate model** panel:
+
+ a. Under **Name**, enter the new name of the model that you want to duplicate.</br>
+
+ ![Screenshot showing the Duplicate model panel.](../media/content-understanding/duplicate-model-panel.png) </br>
+
+ b. Under **Description**, add a description of your new model.
+
+ c. (Optional) Under **Advanced settings**, select whether you want to associate an existing [content type](/sharepoint/governance/content-type-and-workflow-planning#content-type-overview).
+
+5. Select **Duplicate**.
+
+## See also
+
+[Rename a model](rename-a-model.md)
+
+[Syntex accessibility mode](accessibility-mode.md)
syntex Explanation Templates https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/explanation-templates.md
+
+ Title: Use explanation templates in Microsoft Syntex
++++
+audience: admin
++
+search.appverid:
+
+ - enabler-strategic
+ - m365initiative-syntex
+ms.localizationpriority: medium
+description: Learn more about how to use and save explanation templates in Microsoft Syntex.
++
+# Use explanation templates in Microsoft Syntex
+
+<sup>**Applies to:** &ensp; &#10003; Unstructured document processing </sup>
+
+While you can manually add various phrase list values for your explanation, it can be easier to use the templates provided to you in the explanation library.
+
+For example, instead of manually adding all the variations for *date*, you can use the phrase list template for *date* because it already includes many phrase lists values:
+
+![Explanation library.](../media/content-understanding/explanation-template.png)
+
+The explanation library includes commonly used *phrase list* explanations, including:
+
+- Date: Calendar dates, all formats. Includes text and numbers (for example, "Dec 9, 2022").
+- Date (numeric): Calendar dates, all formats. Includes numbers (for example, 1-11-2022).
+- Time: 12-hour and 24-hour formats.
+- Number: Positive and negative numbers up to two decimals.
+- Percentage: A list of patterns representing a percentage. For example, 1%, 11%, 100%, or 11.11%.
+- Phone number: Common US and International formats. For example, 000 000 0000, 000-000-0000, (000)000-0000, or (000) 000-0000.
+- Zip code: US Zip code formats. For example, 11111, 11111-1111.
+- First word of sentence: Common patterns for words up to nine characters.
+- End of sentence: Common punctuation for end of a sentence.
+- Credit card: Common credit card number formats. For example, 1111-1111-1111-1111.
+- Social security number: US Social Security Number format. For example, 111-11-1111.
+- Checkbox: A phrase list representing variations on a filled in checkbox. For example, _X_, __X_.
+- Currency: Major international symbols. For example, $.
+- Email CC: A phrase list with the term 'CC:', often found near the names or email addresses of other people or groups the message was sent to.
+- Email date: A phrase list with the term 'Sent on:', often found near the date the email was sent.
+- Email greeting: Common opening lines for emails.
+- Email recipient: A phrase list with the term 'To:', often found near the names or email addresses of people or groups the message was sent to.
+- Email sender: A phrase list with the term 'From:', often found near the sender's name or email address.
+- Email subject: A phrase list with the term 'Subject:', often found near the email's subject.
+
+The explanation library also includes commonly used *regular expression* explanations, including:
+
+- 6-digit to to 17-digit numbers: Matches any number from 6 to 17 digits long. US bank account numbers fit this pattern.
+- Email address: Matches a common type of email address like meganb@contoso.com.
+- US taxpayer ID number: Matches a three-digit number starting with 9 followed by a 6 digit number starting with 7 or 8.
+- Web address (URL): Matches the format of a web address, starting with http:// or https://.
+
+In addition, the explanation library includes three automatic template types that work with the data you've labeled in your example files:
+
+- After label: The words or characters that occur after the labels in the example files.
+- Before label: The words or characters that occur before the labels in the example files.
+- Labels: Up to the first 10 labels from the example files.
+
+To give you an example of how automatic templates work, in the following example file, we'll use the Before label explanation template to help give the model more information to get a more accurate match.
+
+![Example file.](../media/content-understanding/before-label.png)
+
+When you select the Before label explanation template, it will look for the first set of words that appear before the label in your example files. In the example, the set of words that are identified in the first example file is "As of".
+
+![Before label template.](../media/content-understanding/before-label-explanation.png)
+
+You can select **Add** to create an explanation from the template. As you add more example files, additional words will be identified and added to the phrase list.
+
+![Add the label.](../media/content-understanding/before-label-add.png)
+
+## Use a template from the explanation library
+
+1. On the **Explanations** section of your model's **Train** page, select **New**, then select **From a template**.
+
+ ![Add Before Label.](../media/content-understanding/from-template.png)
+
+2. On the **Explanation templates** page, select the explanation you want to use, then select **Add**.
+
+ ![Select a template.](../media/content-understanding/phone-template.png)
+
+3. The information for the template you selected displays on the **Create an explanation** page. If needed, edit the explanation name and add or remove items from the phrase list.
+
+ ![Edit template.](../media/content-understanding/phone-template-live.png)
+
+4. When finished, select **Save**.
+
+## Save a template to the explanation library
+
+You can save an explanation as a template to make it available in the explanation library of a content center to be used with other models. The template will include the basic and advanced settings for the explanation, with the exception of the option to state where the phrases appear in a document.
+
+> [!NOTE]
+> Only phrase list and regular expression explanations can be saved as a template.
+
+1. On the **Explanations** section of your model's **Train** page:
+
+ a. From the list of explanations, select the one you want to save as a template.
+
+ b. Select **Save as template**.
+
+ ![Screenshot of the Explanations section showing the Save as template option.](../media/content-understanding/explanation-save-as-template.png)
+
+2. On the **Save explanation template** page:
+
+ a. In the **Name** section, rename the explanation if needed.
+
+ b. In the **Description** section, add a description to let others know how to use the explanation.
+
+ c. Select **Save**.
+
+ ![Screenshot of the Save explanation template page.](../media/content-understanding/save-explanation-template.png)
+
+### See also
+
+[Explanation types in Microsoft Syntex](explanation-types-overview.md)
syntex Explanation Types Overview https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/explanation-types-overview.md
+
+ Title: Explanation types in Microsoft Syntex
++++
+audience: admin
++
+search.appverid:
+
+ - enabler-strategic
+ - m365initiative-syntex
+ms.localizationpriority: medium
+description: Learn more about phrase list, regular expression, and proximity explanation types in Microsoft Syntex.
++
+# Explanation types in Microsoft Syntex
+
+<sup>**Applies to:** &ensp; &#10003; Unstructured document processing </sup>
+
+Explanations are used to help to define the information you want to label and extract in your unstructured document processing models in Microsoft Syntex. When you create an explanation, you need to select an explanation type. This article helps you understand the different explanation types and how they're used.
+
+![Screenshot of the Create an explanation panel showing the three explanation types.](../media/content-understanding/explanation-types.png)
+
+These explanation types are available:
+
+- [**Phrase list**](#phrase-list): List of words, phrases, numbers, or other characters you can use in the document or information that you're extracting. For example, the text string *referring doctor* is in all Medical Referral documents you're identifying. Or the *phone number* of the referring doctor from all Medical Referral documents that you're identifying.
+
+- [**Regular expression**](#regular-expression): Uses a pattern-matching notation to find specific character patterns. For example, you can use a regular expression to find all instances of an *email address* pattern in a set of documents.
+
+- [**Proximity**](#proximity): Describes how close explanations are to each other. For example, a *street number* phrase list goes right before the *street name* phrase list, with no tokens in between (you'll learn about tokens later in this article). Using the proximity type requires you to have at least two explanations in your model or the option will be disabled.
+
+## Phrase list
+
+A phrase list explanation type is typically used to identify and classify a document through your model. As described in the *referring doctor* label example, it's a string of words, phrases, numbers, or characters that is consistently in the documents that you're identifying.
+
+While not a requirement, you can achieve better success with your explanation if the phrase you're capturing is located in a consistent location in your document. For example, the *referring doctor* label might be consistently located in the first paragraph of the document. You can also use the **[Configure where phrases occur in the document](explanation-types-overview.md#configure-where-phrases-occur-in-the-document)** advanced setting to select specific areas where the phrase is located, especially if there's a chance that the phrase might occur in multiple locations in your document.
+
+If case sensitivity is a requirement in identifying your label, using the phrase list type allows you to specify it in your explanation by selecting the **Only exact capitalization** checkbox.
+
+![Case sensitivity.](../media/content-understanding/case-sensitivity.png)
+
+A phrase type is especially useful when you create an explanation that identifies and extracts information in different formats, such as dates, phone numbers, and credit card numbers. For example, a date can be displayed in many different formats (1/1/2020, 1-1-2020, 01/01/20, 01/01/2020, or Jan 1,2020). Defining a phrase list makes your explanation more efficient by capturing any possible variations in the data that you're trying to identify and extract.
+
+For the *phone number* example, you extract the phone number for each referring doctor from all Medical Referral documents that the model identifies. When you create the explanation, type the different formats a phone number might display in your document so that you're able to capture possible variations.
+
+![Phone number phrase patterns.](../media/content-understanding/pattern-list.png)
+
+For this example, in **Advanced Settings** select the **Any digit from 0-9** checkbox to recognize each "0" value used in your phrase list to be any digit from 0 through 9.
+
+![Any digit from 0-9.](../media/content-understanding/digit-identity.png)
+
+Similarly, if you create a phrase list that includes text characters, select the **Any letter from a-z** checkbox to recognize each "a" character used in the phrase list to be any character from "a" to "z".
+
+For example, if you create a **Date** phrase list and you want to make sure that a date format such as *Jan 1, 2020* is recognized, you need to:
+
+- Add *aaa 0, 0000* and *aaa 00, 0000* to your phrase list.
+- Make sure that **Any letter from a-z** is also selected.
+
+![Any letter from a-z.](../media/content-understanding/any-letter.png)
+
+If you have capitalization requirements in your phrase list, you can select the **Only exact capitalization** checkbox. For the date example, if you require the first letter of the month to be capitalized, you need to:
+
+- Add *Aaa 0, 0000* and *Aaa 00, 0000* to your phrase list.
+- Make sure that **Only exact capitalization** is also selected.
+
+![Only exact capitalization.](../media/content-understanding/exact-caps.png)
+
+> [!NOTE]
+> Instead of manually creating a phrase list explanation, use the [explanation library](explanation-templates.md) to use phrase list templates for a common phrase list, such as *date*, *phone number*, or *credit card number*.
+
+## Regular expression
+
+A regular expression explanation type allows you to create patterns that help find and identify certain text strings in documents. You can use regular expressions to quickly parse large amounts of text to:
+
+- Find specific character patterns.
+- Validate text to ensure that it matches a predefined pattern (such as an email address).
+- Extract, edit, replace, or delete text substrings.
+
+A regular expression type is especially useful when you create an explanation that identifies and extracts information in similar formats, such as email addresses, bank account numbers, or URLs. For example, an email address, such as megan@contoso.com, is displayed in a certain pattern ("megan" is the first part, and "com" is the last part).
+
+The regular expression for an email address is: **[A-Za-z0-9._%-]+@[A-Za-z0-9.-]+.[A-Za-z]{2,6}**.
+
+This expression consists of five parts, in this order:
+
+1. Any amount of the following characters:
+
+ a. Letters from a to z
+
+ b. Numbers from 0-9
+
+ c. Period, underscore, percent, or dash
+
+2. The @ symbol
+
+3. Any amount of the same characters as the first part of the email address
+
+4. A period
+
+5. Two to six letters
+
+To add a regular expression explanation type:
+
+1. From the **Create an explanation** panel, under **Explanation type**, select **Regular expression**.
+
+ ![Screenshot showing the Create an explanation panel with Regular Expression selected.](../media/content-understanding/create-regular-expression.png)
+
+2. You can either type an expression in the **Regular expression** text box or select **Add a regular expression from a template**.
+
+ When you add a regular expression by using a template, it automatically adds the name and the regular expression to the text box. For example, if you choose the **Email address** template, the **Create an explanation** panel will be populated.
+
+ ![Screenshot showing the Create an explanation panel with Email address template applied.](../media/content-understanding/create-regular-expression-email.png)
+
+### Limitations
+
+The following table shows inline character options that currently are not available for use in regular expression patterns.
+
+|Option|State|Current functionality|
+||||
+|Case sensitivity|Currently not supported.|All matches performed are case-insensitive.|
+|Line anchors|Currently not supported.| Unable to specify a specific position in a string where a match must occur.|
+
+## Proximity
+
+The proximity explanation type helps your model identify data by defining how close another piece of data is to it. For example, in your model say you have defined two explanations that label both the customer *street address number* and *phone number*.
+
+Notice that customer phone numbers always appear before the street address number.
+
+Alex Wilburn<br>
+555-555-5555<br>
+One Microsoft Way<br>
+Redmond, WA 98034<br>
+
+Use the proximity explanation to define how far away the phone number explanation is to better identify the street address number in your documents.
+
+![Proximity explanation.](../media/content-understanding/proximity.png)
+
+> [!NOTE]
+> Regular expressions currently can't be used with the proximity explanation type.
+
+#### What are tokens?
+
+To use the proximity explanation type, you need to understand what a token is. The number of tokens is how the proximity explanation measures distance from one explanation to another. A token is a continuous span (not including spaces or punctuation) of letters and numbers.
+
+The following table shows examples for how to determine the number of tokens in a phrase.
+
+|Phrase|Number of tokens|Explanation|
+||||
+|`Dog`|1|A single word with no punctuation or spaces.|
+|`RMT33W`|1|A record locator number. It might include numbers and letters, but doesn't have punctuation.|
+|`425-555-5555`|5|A phone number. Each punctuation mark is a single token, so `425-555-5555` is 5 tokens:<br>`425`<br>`-`<br>`555`<br>`-`<br>`5555`|
+|`https://luis.ai`|7|`https`<br>`:`<br>`/`<br>`/`<br>`luis`<br>`.`<br>`ai`|
+
+#### Configure the proximity explanation type
+
+For the example, configure the proximity setting to define the range of the number of tokens in the *phone number* explanation from the *street address number* explanation. Notice that the minimum range is "0", because there are no tokens between the phone number and street address number.
+
+But some phone numbers in the sample documents are appended with *(mobile)*.
+
+Nestor Wilke<br>
+111-111-1111 (mobile)<br>
+One Microsoft Way<br>
+Redmond, WA 98034<br>
+
+There are three tokens in *(mobile)*:
+
+|Phrase|Token count|
+|--|--|
+|(|1|
+|mobile|2|
+|)|3|
+
+Configure the proximity setting to have a range of 0 through 3.
+
+![Proximity example.](../media/content-understanding/proximity-example.png)
+
+## Configure where phrases occur in the document
+
+When you create an explanation, by default the entire document is searched for the phrase you're trying to extract. However, you can use the **Where these phrases occur** advanced setting to help in isolating a specific location in the document that a phrase occurs. This setting is useful in situations where similar instances of a phrase might appear somewhere else in the document, and you want to make sure that the correct one is selected.
+
+Referring to our Medical Referral document example, the *referring doctor* is always mentioned in the first paragraph of the document. With the **Where these phrases occur** setting, in this example you can configure your explanation to search for this label only in the beginning section of the document, or any other location in which it might occur.
+
+![Where these phrases occur setting.](../media/content-understanding/phrase-location.png)
+
+You can choose the following options for this setting:
+
+- Anywhere in the file: The entire document is searched for the phrase.
+
+- Beginning of the file: The document is searched from the beginning to the phrase location.
+
+ ![Beginning of file.](../media/content-understanding/beginning-of-file.png)
+
+ In the viewer, you can manually adjust the select box to include the location where the phase occurs. The **End position** value will update to show the number of tokens your selected area includes. You can update the **End position** value as well to adjust the selected area.
+
+ ![Beginning of file position box.](../media/content-understanding/beginning-box.png)
+
+- End of the file: The document is searched from the end to the phrase location.
+
+ ![End of file.](../media/content-understanding/end-of-file.png)
+
+ In the viewer, you can manually adjust the select box to include the location where the phase occurs. The **Starting position** value will update to show the number of tokens your selected area includes. You can update the Starting position value as well to adjust the selected area.
+
+ ![End of file end box.](../media/content-understanding/end-box.png)
+
+- Custom range: The document is searched within a specified range for the phrase location.
+
+ ![Custom range.](../media/content-understanding/custom-file.png)
+
+ In the viewer, you can manually adjust the select box to include the location where the phase occurs. For this setting, you need to select a **Start** and an **End** position. These values represent the number of tokens from the beginning of the document. While you can manually enter in these values, it's easier to manually adjust the select box in the viewer.
+
+## Considerations when configuring explanations
+
+When training a classifier there a few things to keep in mind that will produce more predictable results:
+
+- The more documents you train with, the more accurate the classifier will be. When possible, use more than 5 good documents and use more than 1 bad document. If the libraries you're working with have several different document types in it, several of each type lead to more predictable results.
+- Labeling the document plays an important role in the training process. They are used together with explanations to train the model. You may see some anomalies when training a classifier with documents that don't have a lot of content in them. The explanation may not match anything in the document but since it was labeled as a "good" document you may see it be a match during training.
+- When creating explanations, it uses OR logic in combination with the label to determine if it is a match. Regular expression that uses AND logic may be more predictable. Here is a sample regular expression to use on real documents as your training them. Note the text highlighted in red is the phrase(s) you would be looking for.
+
+ <pre>(?=.*network provider)(?=.*participating providers).*</pre>
+
+- Labels and explanations work together and are used in training the model. It's not a series of rules that can be de-coupled and precise weights or prediction applied to each variable that has been configured. The greater the variation of documents used in the training will provide more accuracy in the model.
+
+### See also
+
+[Use explanation templates in Microsoft Syntex](explanation-templates.md)
syntex Form Processing Overview https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/form-processing-overview.md
+
+ Title: Overview of structured document processing in Microsoft Syntex
++++
+audience: admin
++
+search.appverid:
+
+ - enabler-strategic
+ - m365initiative-syntex
+ms.localizationpriority: medium
+description: Learn how to use AI Builder to create structured document processing models in Microsoft Syntex.
++
+# Overview of structured document processing in Microsoft Syntex
+
+> [!NOTE]
+> *Structured document processing* was known as *form processing* in previous releases.
+
+Use the structured document processing model ([layout method](create-syntex-model.md#train-a-custom-model)) to automatically identify field and table values. It works best for structured or semi-structured documents, such as forms and invoices.
+
+Microsoft Syntex uses Microsoft Power Apps [AI Builder](/ai-builder/form-processing-model-overview) document processing (formerly known as form processing) to create structured document processing models within SharePoint document libraries.
+<!
+ ![AI Builder.](../media/content-understanding/ai-builder.png)
+>
+You can use AI Builder document processing to create structured document processing models that use machine learning technology to identify and extract key-value pairs and table data from structured or semi-structured documents, such as forms and invoices.
+
+Organizations often receive invoices in large quantities from various sources, such as mail, fax, and email. Processing these documents and manually entering them into a database can take a considerable amount of time. By using AI to extract the text, key-value pairs, and tables from your documents, Syntex automates this process.
+
+> [!NOTE]
+> For more ideas about how to use these models in your organization, see [Get started driving adoption](adoption-getstarted.md) and [Scenarios and use cases](adoption-scenarios.md).
+
+For example, you can create a structured document processing model that identifies all documents that are uploaded to the document library. From each document, you can then extract and display specific data that is important to you.
+
+![Screenshot showing the document library view.](../media/content-understanding/doc-lib-done.png)
+
+You use example files to train your model and define the information to be extracted from your form. The layout of your document is learned by training your model. You only need five form documents to get started. Syntex will analyze your example files for key-value pairs, and you can also manually identify ones that might not have been detected. AI builder lets you test the accuracy of your model on your example files.
+
+You can only create a structured document processing model in SharePoint document libraries for which it's enabled. If it has been enabled, you're able to see the **Classify and extract** option in your document library.
+
+![Screenshot showing the AI Builder model.](../media/content-understanding/create-ai-builder-model2.png)
+
+If you need it enabled on your document library, contact your Microsoft 365 admin.
+
+## Requirements
+
+For information about requirements to consider when choosing this model, see [Requirements and limitations for models in Microsoft Syntex](requirements-and-limitations.md#structured-document-processing).
+
+## See also
+
+[Compare custom models](difference-between-document-understanding-and-form-processing-model.md)
+
+[Train a structured document processing model](create-a-form-processing-model.md)
+
+[Power Automate documentation](/power-automate/)
+
+[Training: Improve business performance with AI Builder](/training/paths/improve-business-performance-ai-builder/?source=learn)
syntex Freeform Document Processing Overview https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/freeform-document-processing-overview.md
+
+ Title: Overview of freeform document processing in Microsoft Syntex
++++
+audience: admin
++
+search.appverid:
+
+ - enabler-strategic
+ - m365initiative-syntex
+ms.localizationpriority: medium
+description: Learn how to use AI Builder to create freeform document processing models in Microsoft Syntex.
++
+# Overview of freeform document processing in Microsoft Syntex
+
+Use the freeform document processing model ([freeform selection method](create-syntex-model.md#train-a-custom-model)) to automatically extract information from unstructured and freeform documents such as letters and contracts.
+
+Microsoft Syntex uses Microsoft Power Apps [AI Builder](/ai-builder/form-processing-model-overview) document processing (formerly known as form processing) to create freeform document processing models within SharePoint document libraries.
+<!
+ ![AI Builder.](../media/content-understanding/ai-builder.png)
+>
+You can use AI Builder document processing to create freeform document processing models that use machine learning technology to identify and extract key-value pairs and table data from unstructured or freeform documents, such as contracts and correspondence.
+
+Organizations often receive documents that have no structure in large quantities from various sources, such as mail, fax, and email. Processing these documents and manually entering them into a database can take a considerable amount of time. By using AI to extract the text, key-value pairs, and tables from your documents, Syntex automates this process.
+
+> [!NOTE]
+> For more ideas about how to use these models in your organization, see [Get started driving adoption](adoption-getstarted.md) and [Scenarios and use cases](adoption-scenarios.md).
+
+For example, you can create a structured document processing model that identifies all documents that are uploaded to the document library. From each document, you can then extract and display specific data that is important to you.
+
+![Screenshot showing the document library view.](../media/content-understanding/doc-lib-done.png)
+
+You use example files to train your model and define the information to be extracted from your form. The layout of your document is learned by training your model. You only need five form documents to get started. Syntex will analyze your example files for key-value pairs, and you can also manually identify ones that might not have been detected. AI builder lets you test the accuracy of your model on your example files.
+
+You can only create a structured document processing model in SharePoint document libraries for which it's enabled. If it has been enabled, you're able to see the **Classify and extract** option in your document library.
+
+![Screenshot showing the AI Builder model.](../media/content-understanding/create-ai-builder-model2.png)
+
+If you need it enabled on your document library, contact your Microsoft 365 admin.
+
+## Requirements
+
+For information about requirements to consider when choosing this model, see [Requirements and limitations for models in Microsoft Syntex](requirements-and-limitations.md#freeform-document-processing).
+
+## See also
+
+[Compare custom models](difference-between-document-understanding-and-form-processing-model.md)
+
+[Train a freeform document processing model](train-freeform-document-processing-model.md)
syntex Image Tagging https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/image-tagging.md
+
+ Title: Image tagging in Microsoft Syntex
+++
+audience: admin
+++
+search.appverid:
+
+ - enabler-strategic
+ - m365initiative-syntex
+ms.localizationpriority: medium
+
+description: Learn about image tagging in Microsoft Syntex.
++
+# Image tagging in Microsoft Syntex
+
+(Coming soon)
+
+With image tagging in Microsoft Syntex, users can find images through search by searching on image tags, and create workflows based on image tags. By default, basic image tagging is turned on for SharePoint and OneDrive. Images uploaded to either location are automatically scanned and applicable tags are applied, if available, from a list of 37 basic tags. Users can find images through search by searching on the image tags.
+
+When a user uploads an image, the tagging process runs automatically. If an image is edited, the tagging process runs again to update the tags.
+
+Users with permissions to the image file can see and edit the tags in the file information panel or in the search results page. Once a user edits an image's tags, the system no longer auto-tags that image, even if it's edited.
+
+If you turn tagging off, images will no longer be automatically tagged. Existing tags won't be removed.
+
+> [!NOTE]
+> System generated tags may change with updates to the image or our tag technology.
+
+## Configure image tagging
+
+After you [set up Syntex](set-up-content-understanding.md), you can configure image tagging in the Microsoft 365 admin center.
+
+To turn image tagging on or off
+
+1. In the Microsoft 365 admin center, select <a href="https://go.microsoft.com/fwlink/p/?linkid=2171997" target="_blank">**Setup**</a>.
+
+2. Under **Organizational knowledge**, click **Automate content understanding**.
+
+3. Click **Manage**.
+
+4. On the **Image tagging** tab, click **Edit**.
+
+5. Choose to allow **Basic tagging** or turn tagging **Off**.
+
+6. Click **Save**.
+
+ ![Screenshot of image tagging control.](../media/content-understanding/sharepoint-syntex-image-tagging-control.png)
syntex Import Term Set Skos https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/import-term-set-skos.md
+
+ Title: Import a term set using a SKOS-based format
+description: Learn how to Import a term set using a SKOS-based format.
+++
+audience: admin
+++
+- enabler-strategic
+- m365initiative-syntex
+
+search.appverid:
+ms.localizationpriority: high
+++
+# Import a term set using a SKOS-based format
+
+You can import a term set using a SKOS-based format. For details about the format, see [SharePoint taxonomy SKOS format reference](skos-format-reference.md). This feature requires a [Microsoft Syntex license](syntex-licensing.md).
+
+We recommend keeping your import files to less than 20,000 terms. Larger files can increase the time taken for validation and import.
+
+1. In the SharePoint admin center, expand **Content services**, and then select <a href="https://go.microsoft.com/fwlink/?linkid=2185073" target="_blank">**Term store**</a>.
+
+2. Select the term group where you want to import the term set.
+
+3. In the command bar, click **Import term set**.
+
+4. If you want to download a sample file to use as a template, click **sample-metadata.ttl** to get a sample file that uses the SKOS-based format.
+
+5. Create the import file that contains the term sets & terms you wish to import.
+
+6. Under **File format**, select **SKOS (*.ttl)**.
+
+7. Click **Browse** and navigate to and add your import file.
+
+8. Click **Import**. Do not close the panel until the import completes.
+
+On successful import of the file, a success message will be displayed, and the term store will refresh and you can navigate to the newly created term sets.
+
+## See also
+
+[Introduction to managed metadata](/sharepoint/managed-metadata)
+
+[Unstructured document processing overview](document-understanding-overview.md)
+
+[Import term sets (site level)](https://support.microsoft.com/office/168fbc86-7fce-4288-9a1f-b83fc3921c18)
syntex Learn About Document Understanding Models Through The Sample Model https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/learn-about-document-understanding-models-through-the-sample-model.md
+
+ Title: Import a sample model for Microsoft Syntex
++++
+audience: admin
+++
+search.appverid:
+
+ - enabler-strategic
+ - m365initiative-syntex
+ms.localizationpriority: medium
+description: Learn about unstructured document processing models in Microsoft Syntex by using the sample model.
++
+# Import a sample model for Microsoft Syntex
+
+<sup>**Applies to:** &ensp; &#10003; Unstructured document processing </sup>
+
+Microsoft Syntex provides you with a sample unstructured document processing model you can use to examine, giving you a better understanding of how to create your own models. The sample model also allows you to examine model components, such as its classifier, extractors, and explanations. You can also use the sample files to train the model.
+
+## Import the sample model
+
+To access the sample model, you need to first import the model to your content center.
+
+1. From the content center, select **Models** to see your models list.
+
+2. On the **Models** page, select **Import sample model**.
+
+ ![Import sample model.](../media/content-understanding/import-sample-model.png)
+
+3. When the import completes, the **BenefitsChangeNotice** model home page will open. If you need to open the sample model in the future, you can open it from the models list in the content center.
+
+ ![Sample home page.](../media/content-understanding/sample-home-page.png)
+
+Not only can you look through analyze the sample model to get a better understanding of how the model is constructed, but as a working model you can go further and do things such as:
+
+- Add another extractor. For example, add one that extracts the *discount fee*.
+
+- Apply the model to a document library, and upload some of the training files to it to see how the model classifies files and extracts data from them.
+
+## Get sample models
+
+You can access the [Syntex Samples repository](https://github.com/pnp/syntex-samples), which contains community samples that demonstrate different usage patterns of unstructured document processing models. The samples in this repository contain both the model files and the files used to train the model. Once imported, you can use these models to process files and to view and edit the classifier and extractors.
+
+## See also
+
+[Overview of unstructured document processing](document-understanding-overview.md)
+
+[Create a classifier](create-a-classifier.md)
+
+[Create an extractor](create-an-extractor.md)
syntex Leverage Term Store Taxonomy https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/leverage-term-store-taxonomy.md
+
+ Title: Leverage term store taxonomy when creating an extractor in Microsoft Syntex
++++
+audience: admin
++
+search.appverid:
+
+ - enabler-strategic
+ - m365initiative-syntex
+
+ms.localizationpriority: medium
+description: Use term store taxonomy when creating an extractor in your model in Microsoft Syntex.
++
+# Leverage term store taxonomy when creating an extractor in Microsoft Syntex
+
+<sup>**Applies to:** &ensp; &#10003; Unstructured document processing </sup>
+
+<!
+</br>
+
+> [!VIDEO https://www.microsoft.com/videoplayer/embed/RE4GpJJ]
+
+</br>
+>
+
+When you create an extractor in your unstructured document processing model using Microsoft Syntex, you can take advantage of global term sets in the [term store](/sharepoint/managed-metadata) to display preferred terms for data that you extract.
+
+As an example, your model identifies and classifies all **Contract** documents that are uploaded to the document library. Additionally, the model also extracts a **Contract Service** value from each contract, and will display it in a column in your library view. Among the various Contract Services values in the contracts, there are several older values that your company no longer uses and have been renamed. For example, all references to the terms *Design*, *Graphics*, or *Topography* contract services should now be called *Creative*. Whenever your model extracts one of the outdated terms from a contract document, you want it to display the current termΓÇö*Creative*ΓÇöin your library view. In the following example, while training the model we see that one sample document contains the outdated term of *Design*.
+
+ ![Term store.](../media/content-understanding/design.png)</br>
+
+## Use a managed metadata column in your extractor
+
+Term sets are configured in the Managed Metadata services (MMS) term store in the <a href="https://go.microsoft.com/fwlink/?linkid=2185219" target="_blank">SharePoint admin center</a>. In the example below, the *Contract Services* [term set](/sharepoint/managed-metadata#term-set) is configured to include several terms, including *Creative*. The details for it show that the term has three synonyms (*Design*, *Graphics*, and *Topography*) and the synonyms should be translated to *Creative*.
+
+ ![Term set.](../media/content-understanding/term-store.png)</br>
+
+There could be many reasons why you might want to use a synonym in your term set. For example, there could be outdated terms, renamed terms, or variations between your organizations departments on naming.
+
+To make the managed metadata field available to select when you create your extractor in your model, you need to [add it as a managed-metadata site column](https://support.microsoft.com/office/8fad9e35-a618-4400-b3c7-46f02785d27f). After you add the site column, you can select it when you create the extractor for your model.
+
+ ![Contract service.](../media/content-understanding/contract-services.png)</br>
+
+After applying your model to the document library, when documents are uploaded to library, the *Creative Services* column will display the preferred term (*Creative*) when the extractor finds any of the synonym values (*Design*, *Graphics*, and *Topography*).
+
+ ![Contract service column.](../media/content-understanding/creative.png)</br>
+
+> [!NOTE]
+> If the term set is open, then any extracted values that do not match a preferred term or synonym value will be added as a new term to the root of the term set. These new terms can be moved, merged, or made synonyms in the term store where the term set resides.
+
+## See also
+
+[Introduction to managed metadata](/sharepoint/managed-metadata#terms)
+
+[Create an extractor](create-an-extractor.md)
+
+[Create a managed metadata column](https://support.microsoft.com/office/create-a-managed-metadata-column-8fad9e35-a618-4400-b3c7-46f02785d27f?redirectSourcePath=%252farticle%252fc2a06717-8105-4aea-890d-3082853ab7b7&ui=en-US&rs=en-US&ad=US)
syntex Metadata Search https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/metadata-search.md
+
+ Title: Use metadata to find content in document libraries in Microsoft Syntex
++++
+audience: admin
++
+search.appverid:
+
+ - enabler-strategic
+ - m365initiative-syntex
+ms.localizationpriority: high
+description: Learn how to use Syntex content query and search for custom site columns to find items in SharePoint document libraries using Microsoft Syntex.
++
+# Use metadata to find content in document libraries in Microsoft Syntex
+
+Microsoft Syntex gives you the ability to quickly search through your document's metadata with ease. The Syntex content query feature lets you perform specific metadata-based queries on SharePoint document libraries. You can make faster, more precise queries based on specific metadata column values, rather than just searching for keywords.
+
+Syntex content query lets you use the metadata associated with a document to help locate the file in a SharePoint document library. This feature is particularly useful when you have a specific piece of information you want to search for, such as when a document was last modified, a specific person associated with a file, or a specific file type.
+
+> [!NOTE]
+> This feature is available only for licensed Syntex users.
+
+## To use Syntex content query
+
+1. From a SharePoint document library, in the **Search this library** box, select the content query icon (![Screenshot of the metadata search icon.](../media/content-understanding/metadata-search-icon.png)).
+
+ ![Screenshot of a document library page showing the search box with the content query icon highlighted.](../media/content-understanding/metadata-search-box.png)
+
+2. In the content query pane, type the text or select the parameter you want to find in one or more of the search fields.
+
+ ![Screenshot of a document library page showing the content query pane.](../media/content-understanding/metadata-search-pane.png)
+
+ The following metadata search fields are currently available. More fields will be added in the future.
+
+ |Field |Use this field to |
+ |||
+ |Keywords |Search for a string match in metadata or in the full text of a document. |
+ |File name |Search in the **Name** column in the library. |
+ |People |Search for a match on people in any column in the library. |
+ |Modified date |Search by selected date range in the **Modified** column in the library. |
+ |File type |Search by selected file type (for example, Word document or PDF). |
+ |Content type |Search by selected content type. This option will only appear if there's a non-default content type applied to the library. Default content types are *document* and *folder*. |
+
+3. You can also search for custom site columns that are in the current library view. This is especially useful if you have a model running on the library because the metadata extractors automatically populate information into site columns.
+
+ To add a custom site column to your query, select **Add more options**, and then select the name of the site column.
+
+ ![Screenshot of the Add more options menu on the content query pane.](../media/content-understanding/metadata-search-add-more-options.png)
+
+ For numbers, currency, and date columns, you can scope parameters of the queryΓÇöfor example, greater than a specific amount or within a specific period of time. For text columns, you can specify if you want to contain or not contain certain words.
+
+4. Select **Search**. The documents that match your metadata query are shown on the results page.
syntex Model Discovery https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/model-discovery.md
+
+ Title: Share an enterprise model in Microsoft Syntex
+++
+audience: admin
+++
+search.appverid:
+
+ - enabler-strategic
+ - m365initiative-syntex
+ms.localizationpriority: medium
+description: Learn how to make trained models available to other users and how to apply other trained models in Microsoft Syntex.
++
+# Share an enterprise model in Microsoft Syntex
+
+<sup>**Applies to:** &ensp; &#10003; All custom models &ensp; | &ensp; &#10003; All prebuilt models</sup>
+
+You can make your trained enterprise models available for others to view and use directly from a SharePoint document library. Enterprise models are created and trained in the [content center](create-a-content-center.md).
+
+## Share your model with others
+
+To make your trained model available for others to use:
+
+1. On the **Models** page for your model, select **Model settings**.
+
+2. On the **Model settings** panel, in the **Sites where this model is available** section, select **Edit**.
+
+3. At this point, the **Select the sites where this model is available** panel will be different depending on whether or not you're an administrator.
+
+ If you're a SharePoint administrator, you'll see this view.
+
+ ![Screenshot of the Select the sites where this model is available panel showing the options of where you want the model to be available for others.](../media/content-understanding/select-sites.png)
+
+ - **Not available on any sites** ΓÇô The model won't be available for others to use.
+ - **All sites** ΓÇô The model will be available in the content type gallery for others to use.
+ - **Only selected sites** ΓÇô You can choose which site or sites in which the model will be available. Use the text box to search for and choose the sites to which you want the model applied. You'll only see sites for which you have access.
+
+ If you *aren't* a SharePoint administrator, you'll see this view.
+
+ ![Screenshot of the Select the sites where this model is available panel showing the options for end users with only a few available sites.](../media/content-understanding/select-site-user.png)
+
+ You can only add or remove availability to the specific sites to which you already have access.
+
+4. Select the sites where you want the model to be available for other users to apply, and then select **Save**.
+
+## See also
+
+[Discover other trained models](discover-other-trained-models.md)
syntex Model Types Overview https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/model-types-overview.md
+
+ Title: Overview of model types in Microsoft Syntex
++++
+audience: admin
+++
+search.appverid:
+
+ - enabler-strategic
+ - m365initiative-syntex
+ms.localizationpriority: medium
+description: Learn about custom models and prebuilt models in Microsoft Syntex.
++
+# Overview of model types in Microsoft Syntex
+
+<sup>**Applies to:** &ensp; &#10003; All custom models &ensp; | &ensp; &#10003; All prebuilt models</sup>
+
+Content understanding in Microsoft Syntex starts with AI models. Models let you identify and classify documents that are uploaded to SharePoint document libraries, and then to extract the information you need from each file.
+
+When applied to a SharePoint document library, the model is associated with a content type and has columns to store the information being extracted. The content type you create is stored in the SharePoint content type gallery. You can also choose to use existing content types to use their schema.
+
+</br>
+
+> [!VIDEO https://www.microsoft.com/videoplayer/embed/RE4GJXS]
+
+</br>
+
+Syntex uses [custom models](#custom-models) and [prebuilt models](#prebuilt-models).
+
+![Diagram showing the types of Syntex custom and prebuilt models.](../media/content-understanding/syntex-model-types-diagram.png)
+
+Models can be either *enterprise models*, which are created in a [content center](create-a-content-center.md), or *local models*, which are created on your [local SharePoint site](create-local-model.md).
+
+## Custom models
+
+The type of custom model you choose will depend on the types of files you use, the format and structure of the files, and where you want to apply the model.
+
+Custom models include:
+
+- [Unstructured document processing](#unstructured-document-processing)
+- [Freeform document processing](#freeform-document-processing)
+- [Structured document processing](#structured-document-processing)
+
+To view the side-by-side differences in custom models, see [Compare custom models](./difference-between-document-understanding-and-form-processing-model.md).
+
+When you create a custom model, you'll select the training method associated with the model type. For example, if you want to create an unstructured document processing model, on the **Options for model creation** page where you create a model, you will choose the **Teaching method** option. The following table shows the training method associated with each custom model type.
+
+|Unstructured<br> document processing |Freeform<br> document processing |Structured<br> document processing |
+||||
+| ![Tile for teaching method.](../media/content-understanding/teaching-method-tile-2.png) | ![Tile for freeform seletion method.](../media/content-understanding/freeform-selection-method-tile-2.png) | ![Tile for layout method.](../media/content-understanding/layout-method-tile-2.png) |
+
+> [!NOTE]
+> To make the **Freeform selection method** and the **Layout method** options available to users, they first must be configured in the Microsoft 365 admin center.
+
+### Unstructured document processing
+
+Use the unstructured document processing model to automatically classify documents and extract information from them. It works best with unstructured documents, such as letters or contracts. These documents must have text that can be identified based on phrases or patterns. The identified text designates both the type of file it is (its classification) and what you'd like to extract (its extractors).
+
+For example, an unstructured document could be a contract renewal letter that can be written in different ways. However, information exists consistently in the body of each contract renewal document, such as the text string "Service start date of" followed by an actual date.
+
+This model type supports the widest range of file types and only works on files using the Latin alphabet (English characters).
+
+When you create an unstructured document processing model, use the **Teaching method** option.
+
+For more information, see [Overview of unstructured document processing](document-understanding-overview.md).
+
+### Freeform document processing
+
+Use the freeform document processing model to automatically extract information from unstructured and freeform documents such as letters and contracts where the information can appear anywhere in the document.
+
+Freeform document processing models use Microsoft Power Apps [AI Builder](/ai-builder/form-processing-model-overview) to create and train models within Syntex.
+
+> [!NOTE]
+> The freeform document processing model is not yet available in some regions. For more information, see [Feature availability by region](/ai-builder/availability-region).
+
+Because your organization receives letters and documents in large quantities from various sources, such as mail, fax, and email. Processing these documents and manually entering them into a database can take a considerable amount of time. By using AI to extract the text and other information from these documents, this model automates this process.
+
+This model type is the best option for English documents in PDF or image files when you don't require automatic classification of the type of document.
+
+When you create a freeform document processing model, use the **Freeform selection method** option.
+
+For more information, see [Overview of freeform document processing](freeform-document-processing-overview.md).
+
+### Structured document processing
+
+Use the structured document processing model to automatically identify field and table values. It works best for structured or semi-structured documents, such as forms and invoices.
+
+Structured document processing models use Microsoft Power Apps [AI Builder](/ai-builder/form-processing-model-overview) document processing (formerly known as form processing) to create and train models within Syntex.
+
+This model type supports the widest range of languages and is trained to understand the layout of your form from example documents, and then learns to look for the data you need to extract from similar locations. Forms usually have a more structured layout where entities are in the same location (for example, a social security number on a tax form).
+
+When you create a structured document processing model, use the **Layout method** option.
+
+For more information, see [Overview of structured document processing](form-processing-overview.md).
+
+## Prebuilt models
+
+If you don't need to build a custom model, you can use a [prebuilt model](prebuilt-overview.md) that has already been trained for specific structured documents.
+
+Prebuilt models include:
+
+- [Invoice processing](#invoice-processing)
+- [Receipt processing](#receipt-processing)
+
+Prebuilt models are pretrained to recognize documents and the structured information in the documents. Instead of having to create a new custom model from scratch, you can iterate on an existing pretrained model to add specific fields that fit the needs of your organization.
+
+### Invoice processing
+
+The invoice processing model analyzes and extracts key information from sales invoices. The API analyzes invoices in various formats and extracts key invoice information such as customer name, billing address, due date, and amount due.
+
+For more information about prebuilt invoice processing models, see [Use a prebuilt model to extract information from invoices](prebuilt-model-invoice.md).
+
+### Receipt processing
+
+The prebuilt receipt processing model analyzes and extracts key information from sales receipts. The API analyzes printed and handwritten receipts and extracts key receipt information such as merchant name, merchant phone number, transaction date, tax, and transaction total.
+
+For more information about prebuilt receipt processing models, see [Use a prebuilt model to extract information from receipts](prebuilt-model-receipt.md).
+
+## See also
+
+[Compare custom models in Microsoft Syntex](./difference-between-document-understanding-and-form-processing-model.md)
+
+[Training: Improve business performance with AI Builder](/learn/paths/improve-business-performance-ai-builder/?source=learn)
syntex Model Usage Analytics https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/model-usage-analytics.md
+
+ Title: Analyze how your models are used in Microsoft Syntex
++++
+audience: admin
++
+search.appverid:
+
+ - enabler-strategic
+ - m365initiative-syntex
+ms.localizationpriority: medium
+description: Learn how to find more information about how your AI models are performing in Microsoft Syntex.
++
+# Analyze how your models are used in Microsoft Syntex
+
+<sup>**Applies to:** &ensp; &#10003; All custom models &ensp; | &ensp; &#10003; All prebuilt models</sup>
+
+<!
+</br>
+
+> [!VIDEO https://www.microsoft.com/videoplayer/embed/RE4GnhX]
+
+</br>
+>
+
+Your content center in Microsoft Syntex provides you model usage analytics to provide more information about how your models that have been published from the content center are being used. The **How your models are performing in the last 30 days** section of the content center includes a 30 day roll-up of usage analytics data provided in the following charts and lists:
+
+- Classification by model
+- Classification by library
+- Model usage
+
+ ![Model analytics.](../media/content-understanding/model-analytics.png)
+
+### Roll up of model usage data in the default content center
+
+In Syntex, the default content center is created during setup. More content centers can also be created as needed. For example, departments might create their own content centers to create and manage their models.
+
+Regarding model usage analytics, note that:
+
+- Your default content center will show model usage analytics for all content centers and models in your organization, including ones created in other content centers. This gives content managers and other stakeholders a centralized portal to manage and oversee the content centers and models across the company.
+
+- Other content centers will only show model usage analytics for the models that were created in them. This gives content managers insights into usage data for only the models they're concerned with.
+
+## Classification by model
+
+ ![Total model percentage.](../media/content-understanding/total-model-percentage.png)
+
+The **Classification by model** pie chart displays which models have classified the most files. It shows each published model as a percentage of the total files processed by all published models on the content center.
+
+Each model also shows the **Completeness Rate**, the percentage of uploaded files that were successfully analyzed by the model. A low completeness rate may mean that there are issues with either the model or the files that are being analyzed.
+
+## Classification by library
+
+ ![Files processed.](../media/content-understanding/files-processed-over-time.png)
+
+The **Classification by library** bar chart helps you determine the effectiveness of content understanding in your organization. It shows you not only the number of files processed over time for each model, but by selecting a column in chart, it will also show you the document libraries to which the model was applied.
++
+## Model usage
+
+The model usage list shows usage analytics for the models created through the content center.
+
+> [!NOTE]
+> If you are in the default content center and have additional content centers in your organization, the model usage list will be grouped by content center.
+
+Each model in the model usage list will show the usage data:
+
+- Classified item count: Number of files processed by the model.
+- Average confidence score: Average accuracy score of the model when run against files.
+- Target list URL: The SharePoint document library to which the model is applied.
+
syntex Powershell Syntex Explanations https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/powershell-syntex-explanations.md
+
+ Title: Work with explanations for unstructured document processing models in PowerShell
++++
+audience: admin
+++
+ - enabler-strategic
+ - m365initiative-syntex
+search.appverid: MET150
+ms.localizationpriority: medium
+description: Learn about work with Microsoft Syntex model explanations in PowerShell.
++
+# Work with explanations for unstructured document processing models in PowerShell
+
+<sup>**Applies to:** &ensp; &#10003; Unstructured document processing </sup>
+
+> [!IMPORTANT]
+> The Microsoft Syntex PowerShell cmdlets and all other PnP components are open-source tools backed by an active community providing support for them. There is no SLA for open-source tool support from official Microsoft support channels.
+
+Custom explanation templates are stored in a list within a content center. Because these explanations are stored as list items, PowerShell can be used to interact with them.
+
+## List saved explanations
+
+This example shows how to view all of the custom explanation templates that have been saved on a specific content center.
+
+```PowerShell
+$contentCenterURL = "https://contoso.sharepoint.com/sites/yourContentCenter"
+
+# Connect to content center
+Connect-PnPOnline -url $contentCenterURL
+
+# Load explanation templates list and items
+$explanationTemplatesList = Get-PnPList -Identity "/Explanations"
+$explanations = Get-PnPListItem -List $explanationTemplatesList -Fields "Id", "Title", "ExplanationName", "ExplanationType", "ExplanationDescription","ExplanationContent"
+
+# Extract explanation components
+$explanationValues = $explanations.fieldvalues
+$explanationOutput = @()
+
+foreach ($explanation in $explanationValues) {
+ $content = $explanation.ExplanationContent
+ $content = $content.replace('false','"false"')
+ $content = $content.replace('true','"true"')
+ $contentArray = $content | ConvertFrom-Json
+
+ $output = New-Object -TypeName PSObject
+ Add-Member -InputObject $output -MemberType NoteProperty -Name "Explanation Name" -Value $explanation.ExplanationName
+ Add-Member -InputObject $output -MemberType NoteProperty -Name "Explanation Description" -Value $explanation.ExplanationDescription
+ Add-Member -InputObject $output -MemberType NoteProperty -Name "Explanation Type" -Value $contentArray.kind
+ Add-Member -InputObject $output -MemberType NoteProperty -Name "RegEx Pattern" -Value $contentArray.pattern
+ Add-Member -InputObject $output -MemberType NoteProperty -Name "Phrase List" -Value $contentArray.ngrams
+ Add-Member -InputObject $output -MemberType NoteProperty -Name "Case Sensitive" -Value $contentArray.caseSensitive
+ Add-Member -InputObject $output -MemberType NoteProperty -Name "Ignore Digit Identity" -Value $contentArray.ignoreDigitIdentity
+ Add-Member -InputObject $output -MemberType NoteProperty -Name "Ignore Letter Identity" -Value $contentArray.ignoreLetterIdentity
+
+ $explanationOutput += $output
+}
+
+$explanationOutput
+```
+
+## Create a phrase list explanation
+
+This example shows how to create a custom phrase list explanation template.
+
+```PowerShell
+$contentCenterURL = "https://contoso.sharepoint.com/sites/yourContentCenter"
+$explanationName = "Phrase Explanation A"
+$explanationDescription = "This is my explanation"
+$phrases = "Phrase 1", "Phrase 2"
+$caseSensitive = $false
+$ignoreDigitIdentity= $false
+$ignoreLetterIdentity = $false
+
+# Connect to content center
+Connect-PnPOnline -url $contentCenterURL
+
+# Load explanation templates list
+$explanationTemplatesList = Get-PnPList -Identity "/Explanations"
+
+#Generate GUID for explanation
+$guid = New-Guid
+
+#Format phrase list
+$phrases = $phrases -join "`",`""
+
+#Convert booleans to lower case strings
+$caseSensitive = ($caseSensitive.ToString()).ToLower()
+$ignoreDigitIdentity= ($ignoreDigitIdentity.ToString()).ToLower()
+$ignoreLetterIdentity = ($ignoreLetterIdentity.ToString()).ToLower()
+
+# Build explanation content
+$explanationContent = "{`"id`":`"$guid`",`"kind`":`"dictionaryFeature`",`"name`":`"$explanationName`",`"active`":true,`"nGrams`":[`"$phrases`"],`"caseSensitive`":$caseSensitive,`"ignoreDigitIdentity`":$ignoreDigitIdentity,`"ignoreLetterIdentity`":$ignoreLetterIdentity}"
+
+# Create item in explanation list
+Add-PnPListItem -List $explanationTemplatesList -Values @{"Title"= $explanationName; "ExplanationName" = $explanationName; "ExplanationDescription" = $explanationDescription; "ExplanationContent" = $explanationContent}
+```
+
+## Create a regular expression explanation
+
+This example shows how to create a custom regular expression explanation template.
+
+```PowerShell
+$contentCenterURL = "https://contoso.sharepoint.com/sites/yourContentCenter"
+$explanationName = "RegEx Explanation A"
+$explanationDescription = "This is my explanation"
+$pattern = "\b(https?):\/\/\S+"
+
+# Connect to content center
+Connect-PnPOnline -url $contentCenterURL
+
+# Load explanation templates list
+$explanationTemplatesList = Get-PnPList -Identity "/Explanations"
+
+#Generate GUID for explanation
+$guid = New-Guid
+
+# Build explanation content
+$pattern = $pattern.Replace('\','\\')
+$explanationContent = "{`"id`":`"$guid`",`"kind`":`"regexFeature`",`"name`":`"$explanationName`",`"active`":true,`"pattern`":`"$pattern`"}"
+
+# Create item in explanation list
+Add-PnPListItem -List $explanationTemplatesList -Values @{"Title"= $explanationName; "ExplanationName" = $explanationName; "ExplanationDescription" = $explanationDescription; "ExplanationContent" = $explanationContent}
+```
+
+## Create a phrase list explanation based on a term set
+
+This example shows how to create a custom phrase list explanation template by taking the values from a term set. This includes the preferred term names and any synonyms.
+
+```PowerShell
+$contentCenterURL = "https://contoso.sharepoint.com/sites/yourContentCenter"
+$termSetName = "Terms"
+$termGroupName = "GroupA"
+$explanationName = "MMS Explanation A"
+$explanationDescription = "This is my explanation"
+$caseSensitive = $false
+$ignoreDigitIdentity= $false
+$ignoreLetterIdentity = $false
+
+# Connect to content center
+Connect-PnPOnline -url $contentCenterURL
+
+# Load explanation templates list
+$explanationTemplatesList = Get-PnPList -Identity "/Explanations"
+
+#Generate GUID for explanation
+$guid = New-Guid
+
+#Get term set, including preferred labels and synonyms
+$terms = Get-PnPTerm -TermGroup $termGroupName -TermSet $termSetName -Includes Labels
+$phrases = $terms.labels.value
+
+#Format phrase list
+$phrases = $phrases -join "`",`""
+
+#Convert booleans to lower case strings
+$caseSensitive = ($caseSensitive.ToString()).ToLower()
+$ignoreDigitIdentity= ($ignoreDigitIdentity.ToString()).ToLower()
+$ignoreLetterIdentity = ($ignoreLetterIdentity.ToString()).ToLower()
+
+# Build explanation content
+$explanationContent = "{`"id`":`"$guid`",`"kind`":`"dictionaryFeature`",`"name`":`"$explanationName`",`"active`":true,`"nGrams`":[`"$phrases`"],`"caseSensitive`":$caseSensitive,`"ignoreDigitIdentity`":$ignoreDigitIdentity,`"ignoreLetterIdentity`":$ignoreLetterIdentity}"
+
+# Create item in explanation list
+Add-PnPListItem -List $explanationTemplatesList -Values @{"Title"= $explanationName; "ExplanationName" = $explanationName; "ExplanationDescription" = $explanationDescription; "ExplanationContent" = $explanationContent}
+```
syntex Powershell Syntex Import Export https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/powershell-syntex-import-export.md
+
+ Title: Export and import unstructured document processing models with PowerShell
++++
+audience: admin
+++
+ - enabler-strategic
+ - m365initiative-syntex
+search.appverid: MET150
+ms.localizationpriority: medium
+description: Learn about how to export and import models with PowerShell in Microsoft Syntex.
++
+# Export and import unstructured document processing models with PowerShell
+
+<sup>**Applies to:** &ensp; &#10003; Unstructured document processing </sup>
+
+> [!IMPORTANT]
+> The Microsoft Syntex PowerShell cmdlets and all other PnP components are open-source tools backed by an active community providing support for them. There is no SLA for open-source tool support from official Microsoft support channels.
+
+Syntex models can be exported as PnP templates, enabling reuse across content centers or tenants.
+
+## Export all models in a content center
+
+To export all unstructured document processing models in a content center into a single PnP template, use the following [PnP PowerShell](https://pnp.github.io/powershell/) cmdlets:
+
+```powershell
+Connect-PnPOnline -Url "https://contoso.sharepoint.com/sites/yourContentCenter"
+
+Get-PnPSiteTemplate -Out MyModels.pnp -Handlers SyntexModels
+```
+
+## Export specific models
+
+To export specific unstructured document processing models from a content center into a PnP template, use the following [PnP PowerShell](https://pnp.github.io/powershell/) cmdlets:
+
+```powershell
+Connect-PnPOnline -Url "https://contoso.sharepoint.com/sites/yourContentCenter"
+
+Get-PnPSiteTemplate -Out MyModels.pnp -Configuration .\extract.json
+```
+
+The extract.json defines which models you want to export, allowing to specify model by name or ID and optionally configuring to not extract training data.
+
+### Example - Specify model by name
+
+```json
+{
+ "$schema": "https://developer.microsoft.com/en-us/json-schemas/pnp/provisioning/202102/extract-configuration.schema.json",
+ "persistAssetFiles": true,
+ "handlers": [
+ "SyntexModels"
+ ],
+ "syntexModels": {
+ "models": [
+ {
+ "name": "Sample - benefits change notice.classifier"
+ }
+ ]
+ }
+}
+```
+
+### Example - Specify model by ID
+
+```json
+{
+ "$schema": "https://developer.microsoft.com/en-us/json-schemas/pnp/provisioning/202102/extract-configuration.schema.json",
+ "persistAssetFiles": true,
+ "handlers": [
+ "SyntexModels"
+ ],
+ "syntexModels": {
+ "models": [
+ {
+ "id": 3,
+ "excludeTrainingData": true
+ }
+ ]
+ }
+}
+```
+
+If you don't include the property "includeTrainingData", the default behavior is to include.
+
+> [!NOTE]
+> Training data is required for a model to be editable when imported to a destination content center.
+
+## Import models to a content center
+
+Unstructured document processing models that have been exported to PnP templates can be imported to a content center on any tenant. If the export included training data, then the model will be editable once imported.
+
+To import a model, use the following commands:
+
+```PowerShell
+Connect-PnPOnline -Url "https://contoso.sharepoint.com/sites/yourContentCenter"
+
+Invoke-PnPSiteTemplate -Path .\sampleModel.pnp
+```
syntex Powershell Syntex Intro https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/powershell-syntex-intro.md
+
+ Title: Manage Microsoft Syntex by using PowerShell
++++
+audience: admin
+++
+ - enabler-strategic
+ - m365initiative-syntex
+search.appverid: MET150
+ms.localizationpriority: medium
+description: Learn how to manage Microsoft Syntex with PowerShell.
++
+# Manage Microsoft Syntex by using PowerShell
+
+> [!IMPORTANT]
+> The Microsoft Syntex PowerShell cmdlets and all other PnP components are open-source tools backed by an active community providing support for them. There is no SLA for open-source tool support from official Microsoft support channels.
+
+For these scenarios, the Syntex cmdlets in the PnP PowerShell module can be used to interact with models and explanations. To learn more about how to install this module, see [PnP PowerShell overview](/powershell/sharepoint/sharepoint-pnp/sharepoint-pnp-cmdlets).
+
+Select from the following scenarios to learn how to use PowerShell to manage Syntex:
+
+- [**Export and import models**](powershell-syntex-import-export.md)
+
+ Start here if you want to learn how to export an unstructured document processing model from a content center, and import to another content center or tenant.
+
+- [**Publishing**](powershell-syntex-publishing.md)
+
+ Start here if want to learn how to use PowerShell to publish custom models to document libraries.
+
+- [**Processing**](powershell-syntex-processing.md)
+
+ Start here if you want to learn how to use PowerShell to trigger processing of custom models on a document library.
+
+- [**Explanations**](powershell-syntex-explanations.md)
+
+ Start here if want to learn how to create a custom explanation template for an unstructured document processing model using PowerShell.
syntex Powershell Syntex Processing https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/powershell-syntex-processing.md
+
+ Title: Use PowerShell to request processing by a custom model
++++
+audience: admin
+++
+ - enabler-strategic
+ - m365initiative-syntex
+search.appverid: MET150
+ms.localizationpriority: medium
+description: Learn how to use PowerShell to request processing by a Microsoft Syntex custom model.
++
+# Use PowerShell to request processing by a custom model
+
+<sup>**Applies to:** &ensp; &#10003; All custom models </sup>
+
+> [!IMPORTANT]
+> The Microsoft Syntex PowerShell cmdlets and all other PnP components are open-source tools backed by an active community providing support for them. There is no SLA for open-source tool support from official Microsoft support channels.
+
+Custom models will process newly uploaded files to a library. It's also possible to manually request processing in the UI. However there might be scenarios where it's more efficient to trigger processing through PowerShell.
+
+## Request processing of all items that haven't been previously classified
+
+You can request processing for all items in the library that haven't previously been classified by using this command:
+
+```PowerShell
+#Note: you're connecting here to the site that holds the document library you want to process
+Connect-PnPOnline -Url "https://contoso.sharepoint.com/sites/finance"
+
+Request-PnPSyntexClassifyAndExtract -List "Documents"
+```
+
+For lower priority processing, you might also consider using the -OffPeak parameter, which will queue files for processing outside of business hours where your tenant is located. For more information, see [Request-PnPSyntexClassifyAndExtract](https://pnp.github.io/powershell/cmdlets/Request-PnPSyntexClassifyAndExtract.html).
+
+## Request processing of all items in a library
+
+You can request processing of all files in the library, even if they have previously been classified. This step might be useful if you've updated a model or added another model to the library.
+
+```PowerShell
+#Note: you're connecting here to the site that holds the document library you want to process
+Connect-PnPOnline -Url "https://contoso.sharepoint.com/sites/finance"
+
+Request-PnPSyntexClassifyAndExtract -List "Documents" -Force
+```
+
+> [!NOTE]
+> Using the -Force option with more than 5000 items will automatically enable off peak processing.
+
+## Request processing of all items based on a property
+
+If you want to limit processing to a specific subset of items in a library, you can use a script to select a specific group of files. In the following example, the script allows a field to be selected, and a field value to filter by. More complex queries can be completed using [Get-PnPListItem](https://pnp.github.io/powershell/cmdlets/Get-PnPListItem.html).
+
+```PowerShell
+#Note: you're connecting here to the site that holds the document library you want to process
+Connect-PnPOnline -Url "https://contoso.sharepoint.com/sites/finance"
+$list = Get-PnPList -Identity "Documents"
+# Set the field name to filter items by
+$fieldName = "Vendor"
+# Set the field value to filter by
+$fieldFilter = "Fabrikam"
+
+$listItems = (Get-PnPListItem -List $list -fields $fieldName).fieldValues
+$targetItems = $listItems | Where-Object -Property Provider -EQ -Value $fieldFilter
+
+# Create a new batch
+$batch = New-PnPBatch
+
+# Add files to classify to the batch
+foreach ($listItem in $targetItems) {
+ Request-PnPSyntexClassifyAndExtract -FileUrl $listItem.FileRef -Batch $classifyBatch
+}
+
+# Execute batch
+Invoke-PnPBatch -Batch $batch
+```
+
+## Request processing of specific files
+
+Processing can also be requested for specific files.
+
+```PowerShell
+#Note: you're connecting here to the site that holds the document library you want to process
+Connect-PnPOnline -Url "https://contoso.sharepoint.com/sites/finance"
+
+Request-PnPSyntexClassifyAndExtract -FileUrl "/sites/finance/documents/contoso contract.docx"
+```
++
+```PowerShell
+#Note: you're connecting here to the site that holds the document library you want to process
+Connect-PnPOnline -Url "https://contoso.sharepoint.com/sites/finance"
+
+# Create a new batch
+$batch = New-PnPBatch
+
+# Add files to classify to the batch
+Request-PnPSyntexClassifyAndExtract -FileUrl "/sites/finance/documents/contoso contract.docx" -Batch $batch
+Request-PnPSyntexClassifyAndExtract -FileUrl "/sites/finance/documents/relecloud contract.docx" -Batch $batch
+
+# Execute batch
+Invoke-PnPBatch -Batch $batch
+```
syntex Powershell Syntex Publishing https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/powershell-syntex-publishing.md
+
+ Title: Publish custom models with PowerShell
++++
+audience: admin
+++
+ - enabler-strategic
+ - m365initiative-syntex
+search.appverid: MET150
+ms.localizationpriority: medium
+description: Learn how to publish Microsoft Syntex custom models by using PowerShell.
++
+# Publish custom models with PowerShell
+
+<sup>**Applies to:** &ensp; &#10003; All custom models </sup>
+
+> [!IMPORTANT]
+> The Microsoft Syntex PowerShell cmdlets and all other PnP components are open-source tools backed by an active community providing support for them. There is no SLA for open-source tool support from official Microsoft support channels.
+
+Syntex models typically are deployed to document libraries across your tenant. This can be done by using the content center site, but this can also be done using [PnP PowerShell](https://pnp.github.io/powershell/) as explained in this article.
+
+## Listing the available models in a content center
+
+To get an overview of the models added to the current Syntex content center site, use the [Get-PnPSyntexModel](https://pnp.github.io/powershell/cmdlets/Get-PnPSyntexModel.html) cmdlet:
+
+```PowerShell
+Connect-PnPOnline -Url "https://contoso.sharepoint.com/sites/yourContentCenter"
+Get-PnPSyntexModel
+```
+
+## Apply a model to a library
+
+To apply a model to a library, use the [Publish-PnPSyntexModel](https://pnp.github.io/powershell/cmdlets/Publish-PnPSyntexModel.html) cmdlet:
+
+```PowerShell
+Connect-PnPOnline -Url "https://contoso.sharepoint.com/sites/yourContentCenter"
+Publish-PnPSyntexModel -Model "Contract Notice" -ListWebUrl "https://contoso.sharepoint.com/sites/finance" -List "Documents"
+```
+
+## Understanding where a model is used
+
+Once you've deployed a model to many libraries, you might want to review the list of libraries using your model. This can be done using the [Get-PnPSyntexModelPublication](https://pnp.github.io/powershell/cmdlets/Get-PnPSyntexModelPublication.html) cmdlet:
+
+```PowerShell
+Connect-PnPOnline -Url "https://contoso.sharepoint.com/sites/yourContentCenter"
+Get-PnPSyntexModelPublication -Identity "Contract Notice"
+```
+
+## Removing a model from a library
+
+Removing a model from a library follows the same pattern as applying and can be done using the [Unpublish-PnPSyntexModel](https://pnp.github.io/powershell/cmdlets/Unpublish-PnPSyntexModel.html) cmdlet either interactively or as batch of multiple actions.
+
+```PowerShell
+Connect-PnPOnline -Url "https://contoso.sharepoint.com/sites/yourSite"
+Unpublish-PnPSyntexModel -Model "Invoice model" -ListWebUrl "https://contoso.sharepoint.com/sites/finance" -List "Documents"
+```
+
+## Apply models in bulk
+
+If you want to publish multiple models to multiple libraries, create an input CSV file listing the models and the target locations:
+
+```CSV
+ModelName,TargetSiteUrl,TargetWebServerRelativeUrl,TargetLibraryServerRelativeUrl
+Contract Notice,https://contoso.sharepoint.com/sites/Site1,/sites/Site1,/sites/site1/shared%20documents
+Contract Notice,https://contoso.sharepoint.com/sites/Site1,/sites/Site1,/sites/site1/other
+Trade Confirmation,https://contoso.sharepoint.com/sites/Site2,/sites/Site2,/sites/site2/shared%20documents
+```
+
+This CSV file can then be used as an input into a script that will publish the listed models to the appropriate libraries. In the following example, batching is used to increase the efficiency of the requests.
+
+```PowerShell
+$contentCenterURL = "https://contoso.sharepoint.com/sites/yourSite"
+$targetsCSV = "./Publish-SyntexModelBulk.csv"
+
+Connect-PnPOnline -url $contentCenterURL
+
+$targetLibraries = Import-Csv -Path $targetsCSV
+
+$batch = New-PnPBatch
+
+foreach ($target in $targetLibraries) {
+ Publish-PnPSyntexModel -Model $target.ModelName -TargetSiteUrl $target.TargetSiteUrl -TargetWebServerRelativeUrl $target.TargetWebServerRelativeUrl -TargetLibraryServerRelativeUrl $target.TargetLibraryServerRelativeUrl -Batch $batch
+}
+
+Invoke-PnPBatch -Batch $batch
+```
syntex Prebuilt Model Invoice https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/prebuilt-model-invoice.md
+
+ Title: Use a prebuilt model to extract information from invoices in Microsoft Syntex
++++
+audience: admin
++
+search.appverid:
+
+ - enabler-strategic
+ - m365initiative-syntex
+ms.localizationpriority: medium
+description: Learn how to use a prebuilt invoices model in Microsoft Syntex.
+++
+# Use a prebuilt model to extract information from invoices in Microsoft Syntex
+
+The prebuilt *invoices model* analyzes and extracts key information from sales invoices. The API recognizes invoices in various formats and [extracts key invoice information](/azure/applied-ai-services/form-recognizer/concept-invoice#field-extraction), such as customer name, billing address, due date, and amount due.
+
+To use an invoices model, follow these steps:
+
+- Step 1: [Create an invoices model](#create-an-invoices-model)
+- Step 2: [Upload an example file to analyze](#upload-an-example-file-to-analyze)
+- Step 3: [Select extractors for your model](#select-extractors-for-your-model)
+- Step 4: [Apply the model](#apply-the-model)
+
+## Create an invoices model
+
+Follow the instructions in [Create a model in Syntex](create-syntex-model.md) to create a prebuilt invoices model. Then continue with the following steps to complete your model.
++
+<!
+## Create an invoices model
+
+Follow these steps to create a trained invoices model.
+
+1. From the **Models** page, select **Create a model**.
+
+ ![Screenshot of the Models page showing the Create a model button.](../media/content-understanding/create-a-model-from-the-models-page.png)
++
+2. On the **View options for classification and extraction** page, in the **Use a trained model** section, select **Invoices**.
+
+ ![Screenshot of the View options for classification and extraction page showing the custom models and trained models.](../media/content-understanding/view-options-for-classification-and-extraction-page.png)
+
+3. To continue, follow these [instructions to continue to create an invoices model](create-syntex-model.md#invoices).
+
+ > [!NOTE]
+ > Sensitivity labels are not available for trained models at this time.
+>
+
+## Upload an example file to analyze
+
+1. On the **Models** page, in the **Add a file to analyze** section, select **Add file**.
+
+ ![Screenshot of the new models page showing the Add a file to analyze section.](../media/content-understanding/prebuilt-add-file-to-analyze.png)
+
+2. On the **Files to analyze the model** page, select **Add** to find the file you want to use.
+
+ ![Screenshot of the Files to analyze the model page showing the Add button.](../media/content-understanding/prebuilt-add-file-button.png)
+
+3. On the **Add a file from the training files library** page, select the file, and then select **Add**.
+
+ ![Screenshot of the Add a file from the training files library page.](../media/content-understanding/prebuilt-add-file-from-training-library.png)
+
+4. On the **Files to analyze the model** page, select **Next**.
+
+## Select extractors for your model
+
+On the extractor details page, you'll see the document area on the right and the **Extractors** panel on the left. The **Extractors** panel shows the list of extractors that have been identified in the document.
+
+ ![Screenshot of the extractor details page and Extractor panel.](../media/content-understanding/prebuilt-extractor-details-page.png)
+
+The entity fields that are highlighted in green in the document area are the items that were detected by the model when it analyzed the file. When you select an entity to extract, the highlighted field will change to blue. If you later decide not to include the entity, the highlighted field will change to gray. The highlights make it easier to see the current state of the extractors you've selected.
+
+> [!TIP]
+> You can use the scroll wheel on your mouse or the controls at the bottom of the document area to zoom in or out as needed to read the entity fields.
+
+### Select an extractor entity
+
+You can select an extractor either from the document area or from the **Extractors** panel, depending on your preference.
+
+- To select an extractor from the document area, select the entity field.
+
+ ![Screenshot of the document area showing how to select an entity field.](../media/content-understanding/prebuilt-document-area-select-field.png)
+
+- To select an extractor from the **Extractors** panel, select the checkbox to the right of the entity name.
+
+ ![Screenshot of the Extractors panel showing how to select an entity field.](../media/content-understanding/prebuilt-extractors-panel-select-field.png)
+
+When you select an extractor, a **Select extractor?** box is displayed in the document area. The box shows the extractor name, the original value, and the option to select it as an extractor. For certain data types such as numbers or dates, it will also show an extracted value.
+
+ ![Screenshot of the Select extractor box on the extractor details page.](../media/content-understanding/prebuilt-select-distractor-box.png)
+
+The original value is what is actually in the document. The extracted value is what will be written into the column in SharePoint. When the model is applied to a library, you can use column formatting to specify how you want it to look in the document.
+
+Continue to select additional extractors you want to you use. You can also add other files to analyze for this model configuration.
+
+### Rename an extractor
+
+You can rename an extractor either from the model home page or from the **Extractors** panel. You might consider renaming selected extractors because these names will be used as the column names when the model is applied to the library.
+
+To rename an extractor from the model home page:
+
+1. In the **Extractors** section, select the extractor you want to rename, and then select **Rename**.
+
+ ![Screenshot of the Extractors section with the Rename option highlighted.](../media/content-understanding/prebuilt-model-page-rename-extractor.png)
+
+2. On the **Rename entity extractor** panel, enter the new name of the extractor, and then select **Rename**.
+
+To rename an extractor from the **Extractors** panel:
+
+1. Select the extractor you want to rename, and then select **Rename**.
+
+ ![Screenshot of the Extractors panel showing how to rename an extractor.](../media/content-understanding/prebuilt-extractors-panel-rename-field.png)
+
+2. In the **Rename extractor** box, enter the new name of the extractor, and then select **Rename**.
+
+## Apply the model
+
+- To save changes and return to the model home page, on the **Extractors** panel, select **Save and exit**.
+
+- If you're ready to apply the model to a library, in the document area, select **Next**. On the **Add to library** panel, choose the library to which you want to add the model, and then select **Add**.
+
+## Change the view in a document library
+
+For information about how to set the default view and how to change the view of a document library, see [Choose the view in a document library](choose-library-view.md).
+
+<!
+>
syntex Prebuilt Model Receipt https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/prebuilt-model-receipt.md
+
+ Title: Use a prebuilt model to extract information from receipts in Microsoft Syntex
++++
+audience: admin
++
+search.appverid:
+
+ - enabler-strategic
+ - m365initiative-syntex
+ms.localizationpriority: medium
+description: Learn how to use a prebuilt receipts model in Microsoft Syntex.
+++
+# Use a prebuilt model to extract information from receipts in Microsoft Syntex
+
+The prebuilt *receipts model* in Microsoft Syntex analyzes and extracts key information from sales receipts. The API recognizes printed and handwritten receipts and [extracts key receipt information](/azure/applied-ai-services/form-recognizer/concept-receipt#field-extraction), such as merchant name, merchant phone number, transaction date, tax, and transaction total. Receipts can be of various formats and quality including printed and handwritten receipts.
+
+To use a receipts model, follow these steps:
+
+- [Step 1: Create a receipts model](#step-1-create-a-receipts-model)
+- [Step 2: Upload an example file to analyze](#step-2-upload-an-example-file-to-analyze)
+- [Step 3: Select extractors for your model](#step-3-select-extractors-for-your-model)
+- [Step 4: Apply the model](#step-4-apply-the-model)
+
+## Step 1: Create a receipts model
+
+Follow the instructions in [Create a model in Syntex](create-syntex-model.md) to create a prebuilt receipts model. Then continue with the following steps to complete your model.
+
+## Step 2: Upload an example file to analyze
+
+1. On the **Models** page, in the **Add a file to analyze** section, select **Add file**.
+
+ ![Screenshot of the new models page showing the Add a file to analyze section.](../media/content-understanding/prebuilt-add-file-to-analyze.png)
+
+2. On the **Files to analyze the model** page, select **Add** to find the file you want to use.
+
+ ![Screenshot of the Files to analyze the model page showing the Add button.](../media/content-understanding/prebuilt-add-file-button.png)
+
+3. On the **Add a file from the training files library** page, select the file, and then select **Add**.
+
+ ![Screenshot of the Add a file from the training files library page.](../media/content-understanding/prebuilt-add-file-from-training-library.png)
+
+4. On the **Files to analyze the model** page, select **Next**.
+
+## Step 3: Select extractors for your model
+
+On the extractor details page, you'll see the document area on the right and the **Extractors** panel on the left. The **Extractors** panel shows the list of extractors that have been identified in the document.
+
+ ![Screenshot of the extractor details page and Extractor panel.](../media/content-understanding/prebuilt-extractor-details-page.png)
+
+The entity fields that are highlighted in green in the document area are the items that were detected by the model when it analyzed the file. When you select an entity to extract, the highlighted field will change to blue. If you later decide not to include the entity, the highlighted field will change to gray. The highlights make it easier to see the current state of the extractors you have selected.
+
+> [!TIP]
+> You can use the scroll wheel on your mouse or the controls at the bottom of the document area to zoom in or out as needed to read the entity fields.
+
+### Select an extractor entity
+
+You can select an extractor either from the document area or from the **Extractors** panel, depending on your preference.
+
+- To select an extractor from the document area, select the entity field.
+
+ ![Screenshot of the document area showing how to select an entity field.](../media/content-understanding/prebuilt-document-area-select-field.png)
+
+- To select an extractor from the **Extractors** panel, select the checkbox to the right of the entity name.
+
+ ![Screenshot of the Extractors panel showing how to select an entity field.](../media/content-understanding/prebuilt-extractors-panel-select-field.png)
+
+When you select an extractor, a **Select extractor?** box is displayed in the document area. The box shows the extractor name, the original value, and the option to select it as an extractor. For certain data types such as numbers or dates, it will also show an extracted value.
+
+ ![Screenshot of the Select extractor box on the extractor details page.](../media/content-understanding/prebuilt-select-distractor-box.png)
+
+The original value is what is actually in the document. The extracted value is what will be written into the column in SharePoint. When the model is applied to a library, you can use column formatting to specify how you want it to look in the document.
+
+Continue to select additional extractors you want to you use. You can also add other files to analyze for this model configuration.
+
+### Rename an extractor
+
+You can rename an extractor either from the model home page or from the **Extractors** panel. You might consider renaming selected extractors because these names will be used as the column names when the model is applied to the library.
+
+To rename an extractor from the model home page:
+
+1. In the **Extractors** section, select the extractor you want to rename, and then select **Rename**.
+
+ ![Screenshot of the Extractors section with the Rename option highlighted.](../media/content-understanding/prebuilt-model-page-rename-extractor.png)
+
+2. On the **Rename entity extractor** panel, enter the new name of the extractor, and then select **Rename**.
+
+To rename an extractor from the **Extractors** panel:
+
+1. Select the extractor you want to rename, and then select **Rename**.
+
+ ![Screenshot of the Extractors panel showing how to rename an extractor.](../media/content-understanding/prebuilt-extractors-panel-rename-field.png)
+
+2. In the **Rename extractor** box, enter the new name of the extractor, and then select **Rename**.
+
+## Step 4: Apply the model
+
+- To save changes and return to the model home page, on the **Extractors** panel, select **Save and exit**.
+
+- If you're ready to apply the model to a library, in the document area, select **Next**. On the **Add to library** panel, choose the library to which you want to add the model, and then select **Add**.
+
+## Change the view in a document library
+
+For information about how to set the default view and how to change the view of a document library, see [Choose the view in a document library](choose-library-view.md).
++
syntex Prebuilt Overview https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/prebuilt-overview.md
+
+ Title: Overview of prebuilt models in Microsoft Syntex
++++
+audience: admin
+++
+search.appverid:
+
+ - enabler-strategic
+ - m365initiative-syntex
+ms.localizationpriority: medium
+description: Learn about prebuilt models in Microsoft Syntex.
++
+# Overview of prebuilt models in Microsoft Syntex
+
+In addition to [custom models](model-types-overview.md#custom-models), Microsoft Syntex provides *prebuilt models* to automate the extraction of information.
+
+Prebuilt models are preconfigured to recognize documents and the structured information in the documents. Instead of having to create a new custom model from scratch, you can iterate on an existing pretrained model to add specific fields that fit the needs of your organization.
+
+Prebuilt models use optical character recognition (OCR) combined with deep learning models to identify and extract predefined text and data fields common to specific document types. You start by analyzing one of your files against the prebuilt model. You then select the detected fields that make sense for your purpose. If the model doesn't detect the fields that you need, you can analyze again by using a different file.
+
+Like other models, prebuilt models are created and managed in the [content center](create-a-content-center.md). When applied to a SharePoint document library, the model is associated with a content type and has columns to store the information being extracted.
+
+After publishing your model, use the content center to apply it to any SharePoint document library that you have access to.
+
+## Available prebuilt models
+
+Currently, there are two prebuilt models available: [invoices](prebuilt-model-invoice.md) and [receipts](prebuilt-model-receipt.md).
+
+- The *invoices model* analyzes and extracts key information from sales invoices. The API analyzes invoices in various formats and [extracts key invoice information](/azure/applied-ai-services/form-recognizer/concept-invoice#field-extraction) such as customer name, billing address, due date, and amount due.
+
+- The *receipts model* analyzes and extracts key information from sales receipts. The API analyzes printed and handwritten receipts and [extracts key receipt information](/azure/applied-ai-services/form-recognizer/concept-receipt#field-extraction) such as merchant name, merchant phone number, transaction date, tax, and transaction total.
+
+Additional prebuilt models will be available in future releases.
+
+## Requirements
+
+For information about requirements to consider when choosing this model, see [Requirements and limitations for models in Microsoft Syntex](requirements-and-limitations.md).
+
+## See also
+
+[Use a prebuilt model to extract information from invoices](prebuilt-model-invoice.md)
+
+[Use a prebuilt model to extract information from receipts](prebuilt-model-receipt.md)
+
+
+
syntex Push Content Type To Hub https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/push-content-type-to-hub.md
+
+ Title: Push content types to a hub
+description: Learn how to push content types to a hub.
++++
+audience: admin
++
+search.appverid:
+
+ - enabler-strategic
+ - m365initiative-syntex
+
+ms.localizationpriority: high
++
+# Push content types to a hub
+
+</br>
+
+> [!VIDEO https://www.microsoft.com/videoplayer/embed/RE4GyeV]
+
+</br>
++
+To make important content types more consistently available to SharePoint libraries and lists, you can push them to the hubs that you choose. Pushing the content types automatically adds them to any new lists and libraries created on the sites associated with the hub, and to any new sites added to the hub. This feature requires a [Microsoft Syntex license](syntex-licensing.md).
+
+For this feature to work, the content types being pushed must already be published.
+
+To push content types to hubs
+
+1. In the SharePoint admin center, expand **Content services**, and then select <a href="https://go.microsoft.com/fwlink/?linkid=2185074" target="_blank">**Content type gallery**</a>.
+2. Select the content type that you want to push to hubs.
+3. Select **Edit** in the command bar.
+4. Select **Choose hub sites**.
+5. Select the hub sites you want and then choose **OK**.
+6. Choose **Save**.
+
+When you push a content type to an existing hub & its existing associated sites for the first time, it can take up to an hour from when the hub or associated sites are visited, for the settings to update in the site. Any new associations to the hub won't require this wait and will have the settings reflected in a few minutes.
+
+After the settings are updated, the content type with these settings will be available in any newly associated site with the hub in a few minutes. The default library view will be changed to one of these automatically created views. If there are multiple content types pushed to the same library, then the latest one (based on the order of the action of pushing those content types to the hub this library belongs to) is what will be set as the default view. Then, any new list or library created will have the content type automatically added to it within a few minutes of creation. A pushed content type will be added to a document library only if it derives directly or indirectly from the Document content type, and a content type will be added to a list only if it does not derive from the Document content type directly or indirectly.
++
syntex Rename A Model https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/rename-a-model.md
+
+ Title: Rename a model in Microsoft Syntex
+++
+audience: admin
+++
+search.appverid:
+
+ - enabler-strategic
+ - m365initiative-syntex
+ms.localizationpriority: medium
+description: Learn how and why to rename a model in Microsoft Syntex.
++
+# Rename a model in Microsoft Syntex
+
+<sup>**Applies to:** &ensp; &#10003; All custom models &ensp; | &ensp; &#10003; All prebuilt models</sup>
+
+At some point, you might want to rename a model. A common example is when you create an initial draft of a model, you might not have given a lot of thought as to the final name (for example, you might have named it ΓÇ£AlexWilburModel1ΓÇ¥). As you come closer to finalizing the model and putting it to use, you realize that a more proper name would be ΓÇ£Contract Renewals,ΓÇ¥ and you want to rename it.
+
+Another example is when your organization makes a decision to refer to a process or document type by a different name. For example, after you create your model and are ready to apply it, your organization might mandate that all ΓÇ£ContractsΓÇ¥ will now formally be referred to as ΓÇ£Agreements.ΓÇ¥ If needed, you can choose to rename your model from ΓÇ£Contract RenewalsΓÇ¥ to ΓÇ£Agreement Renewals.ΓÇ¥
+
+> [!IMPORTANT]
+> You can only rename a model if it has not been applied to a document library.
+
+Renaming a model also renames the [content type](/sharepoint/governance/content-type-and-workflow-planning#content-type-overview) that is associated with the model.
+
+## Rename a model
+
+Follow these steps to rename a model.
+
+1. From the content center, select **Models** to see your models list.
+
+2. On the **Models** page, select the model you want to rename.
+
+3. By using either the ribbon or the **Show actions** button (next to the model name), select **Rename**. </br>
+
+ ![Screenshot of the Models page showing a selected model with the Rename options highlighted.](../media/content-understanding/select-model-rename-both.png) </br>
+
+4. On the **Rename model** panel:
+
+ a. Under **New name**, enter the new name of the model that you want to rename.</br>
+
+ ![Screenshot showing the Rename model panel.](../media/content-understanding/rename-model-panel.png) </br>
+
+ b. (Optional) Under **Advanced settings**, select whether you want to associate an existing [content type](/sharepoint/governance/content-type-and-workflow-planning#content-type-overview). If you choose **Use an existing content type**, the model will be renamed to match the selected content type.
+
+5. Select **Rename**.
+
+## See also
+
+[Delete a model](delete-a-model.md)
+
syntex Rename An Extractor https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/rename-an-extractor.md
+
+ Title: Rename an extractor in Microsoft Syntex
+++
+audience: admin
+++
+search.appverid:
+
+ - enabler-strategic
+ - m365initiative-syntex
+ms.localizationpriority: medium
+description: Learn how and why to rename an extractor in Microsoft Syntex.
++
+# Rename an extractor in Microsoft Syntex
+
+<sup>**Applies to:** &ensp; &#10003; Unstructured document processing </sup>
+
+At some point, you might need to rename an extractor if you want to refer to an extracted data field by a different name. For example, your organization decides to make changes to their contract documents, and refers to ΓÇ£customersΓÇ¥ as ΓÇ£clientsΓÇ¥ in their documents. If you were extracting a ΓÇ£CustomerΓÇ¥ field in your model, you can choose to rename it to ΓÇ£Client.ΓÇ¥
+
+When you sync your updated model to your SharePoint document library, you will see a new ΓÇ£ClientΓÇ¥ column in your document library view. Your view will retain the ΓÇ£CustomerΓÇ¥ column for past activity, but will update the new ΓÇ£ClientΓÇ¥ column for all new documents that are processed by your model.
+
+> [!IMPORTANT]
+> Make sure to sync your updated model to the document libraries where you had previously applied it for the new column name to display.
+
+## Rename an extractor
+
+Follow these steps to rename an entity extractor.
+
+1. From the content center, select **Models** to see your models list.
+
+2. On the **Models** page, in the **Name** column, select the model for which you want to rename an extractor.
+
+3. Under **Entity extractors**, select the name of the extractor you want to rename, and then select **Rename**.
+
+ ![Screenshot of the Entity extractors section showing a selected extractor with the Rename option highlighted.](../media/content-understanding/entity-extractor-rename.png)
+
+4. On the **Rename entity extractor** panel:
+
+ a. Under **New name**, enter the new name of the extractor.
+
+ ![Screenshot showing the Entity extractor panel.](../media/content-understanding/rename-entity-extractor-panel.png)
+
+ b. (Optional) Under **Advanced settings**, select whether you want to associate an existing site column.
+
+5. Select **Rename**.
+
+## See also
+
+[Create an extractor](create-an-extractor.md)
++
syntex Requirements And Limitations https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/requirements-and-limitations.md
+
+ Title: Requirements and limitations for models in Microsoft Syntex
++++
+audience: admin
++
+search.appverid:
+
+ - enabler-strategic
+ - m365initiative-syntex
+ms.localizationpriority: medium
+description: Learn about file limitations, file types, supported languages, and other requirements for models in Microsoft Syntex.
++
+# Requirements and limitations for models in Microsoft Syntex
+
+<sup>**Applies to:** &ensp; &#10003; All custom models &ensp; | &ensp; &#10003; All prebuilt models</sup>
+
+Microsoft Syntex lets you create [custom models and prebuilt models](model-types-overview.md). Depending on the type of model you choose, there might be different requirements, such as file type and size, languages that need to be supported, geographical considerations, and other factors that will help you decide which type of model to use.
+
+Custom models:
+
+- [Unstructured document processing](#unstructured-document-processing)
+- [Freeform document processing](#freeform-document-processing)
+- [Structured document processing](#structured-document-processing)
+
+Prebuilt models:
+
+- [Invoice processing](#invoice-processing)
+- [Receipt processing](#receipt-processing)
+
+## Custom models
+
+### Unstructured document processing
+
+| Icon | Description |
+| - | - |
+| ![Files symbol.](/office/medi, .msg, .pdf, .png, .ppt, .pptx, .rtf, .tif, .tiff, .txt, .xls, and .xlsx. |
+| ![Conversation symbol.](/office/media/icons/chat-room-conversation-blue.png) | **Supported languages** <br>This model supports all of the Latin-based languages, including: English, French, German, Italian, and Spanish. |
+| ![Paragraph symbol.](/office/media/icons/paragraph-writing-blue.png) | **OCR considerations** <br>This model uses optical character recognition (OCR) technology to scan .pdf files, image files, and .tiff files. OCR processing works best on documents that meet the following requirements: <br> - File format of .jpg, .png, or .pdf (text or scanned). Text-embedded .pdf files are better, because there won't be any errors in character extraction and location. <br> - If your .pdf files are password-locked, you must remove the lock before submitting them. <br> - The combined file size of the documents used for training per collection must not exceed 50 MB, and PDF documents shouldn't have more than 500 pages. <br> - For images, dimensions must be between 50 x 50 and 10,000 x 10,000 pixels. Images that are very wide or have odd dimensions (for example, floor plans) might get truncated in the OCR process and lose accuracy. <br> - For .pdf files, dimensions must be at most 17 x 17 inches, corresponding to Legal or A3 paper sizes and smaller. <br> - If scanned from paper documents, scans should be high-quality images. <br> - Must use the Latin alphabet (English characters). <br> Note the following differences about Microsoft Office text-based files and OCR-scanned files (.pdf, image, or .tiff): <br> - Office files: Truncated at 64,000 characters (in training and when run against files in a document library). <br> - OCR-scanned files: There's a 500-page limit. Only PDF and image file types are processed by OCR. |
+| ![Globe symbol.](/office/media/icons/globe-internet.png) | **Multi-Geo environments** <br>When setting up Syntex in a [Microsoft 365 Multi-Geo](/microsoft-365/enterprise/microsoft-365-multi-geo) environment, you can only configure it to use the model type in the central location. If you want to use this model type in a satellite location, contact Microsoft support. |
+| ![Objects symbol.](/office/media/icons/objects-blue.png) | **Multi-model libraries** <br>If two or more trained models are applied to the same library, the file is classified using the model that has the highest average confidence score. The extracted entities will be from the applied model only. |
+
+### Freeform document processing
+
+| Icon | Description |
+| - | - |
+| ![Files symbol.](/office/media/icons/files-blue.png) | **Supported file types** <br>This model supports the following file types: see [file type requirements](/ai-builder/form-processing-model-requirements#requirements). |
+| ![Conversation symbol.](/office/media/icons/chat-room-conversation-blue.png) | **Supported languages** <br>This model supports the following language: English. |
+| ![Paragraph symbol.](/office/media/icons/paragraph-writing-blue.png) | **OCR considerations** <br>This model uses optical character recognition (OCR) technology to scan .pdf files, image files, and .tiff files. OCR processing works best on documents that meet [these requirements](/ai-builder/form-processing-model-requirements#requirements). |
+| ![Bandwidth/efficiency symbol.](/office/media/icons/bandwidth-efficiency-blue.png) | **Optimization tips** <br>If your model isn't performing as you want it to, try [these steps to improve the performance of your model](/ai-builder/improve-form-processing-performance). |
+| ![Globe symbol.](/office/media/icons/globe-internet.png) | **Multi-Geo environments** <br>When setting up Syntex in a [Microsoft 365 Multi-Geo](/microsoft-365/enterprise/microsoft-365-multi-geo) environment, you can only configure it to use the model type in the central location. If you want to use this model type in a satellite location, contact Microsoft support. |
+| ![Blocks symbol.](/office/media/icons/blocks-blue.png) | **Custom Power Platform environments** <br>If you use a custom environment (rather than the default environment) for Power Platform processing, there are additional setup requirements. For more information, see [Custom Power Platform environments](/microsoft-365/contentunderstanding/set-up-content-understanding#custom-power-platform-environments). |
+| ![Objects symbol.](/office/media/icons/objects-blue.png) | **Multi-model libraries** <br>If two or more trained models are applied to the same library, the file is classified using the model that has the highest average confidence score. The extracted entities will be from the applied model only. You can have only one freeform or one structured model per library. |
+
+### Structured document processing
+
+| Icon | Description |
+| - | - |
+| ![Files symbol.](/office/media/icons/files-blue.png) | **Supported file types** <br>This model supports the following file types: see [file type requirements](/ai-builder/form-processing-model-requirements#requirements). |
+| ![Conversation symbol.](/office/media/icons/chat-room-conversation-blue.png) | **Supported languages** <br>This model supports 73 languages: see [supported languages](/ai-builder/form-processing-model-requirements#languages-supported). |
+| ![Paragraph symbol.](/office/media/icons/paragraph-writing-blue.png) | **OCR considerations** <br>This model uses optical character recognition (OCR) technology to scan .pdf files, image files, and .tiff files. OCR processing works best on documents that meet [these requirements](/ai-builder/form-processing-model-requirements#requirements). |
+| ![Bandwidth/efficiency symbol.](/office/media/icons/bandwidth-efficiency-blue.png) | **Optimization tips** <br>If your model isn't performing as you want it to, try [these steps to improve the performance of your model](/ai-builder/improve-form-processing-performance). |
+| ![Globe symbol.](/office/media/icons/globe-internet.png) | **Multi-Geo environments** <br>When setting up Syntex in a [Microsoft 365 Multi-Geo](/microsoft-365/enterprise/microsoft-365-multi-geo) environment, you can only configure it to use the model type in the central location. If you want to use this model type in a satellite location, contact Microsoft support. |
+| ![Blocks symbol.](/office/media/icons/blocks-blue.png) | **Custom Power Platform environments** <br>If you use a custom environment (rather than the default environment) for Power Platform processing, there are additional setup requirements. For more information, see [Custom Power Platform environments](/microsoft-365/contentunderstanding/set-up-content-understanding#custom-power-platform-environments). |
+| ![Objects symbol.](/office/media/icons/objects-blue.png) | **Multi-model libraries** <br>If two or more trained models are applied to the same library, the file is classified using the model that has the highest average confidence score. The extracted entities will be from the applied model only. You can have only one freeform or one structured model per library. |
+
+## Prebuilt models
+
+### Invoice processing
+
+| Icon | Description |
+| - | - |
+| ![Files symbol.](/office/media/icons/files-blue.png) | **Supported file types** <br>This model supports the following file types: .bmp, .jpeg, .pdf, .png, and .tiff. |
+| ![Conversation symbol.](/office/media/icons/chat-room-conversation-blue.png) | **Supported languages** <br>This model supports only English language invoices from the United States. |
+| ![Paragraph symbol.](/office/media/icons/paragraph-writing-blue.png) | **OCR considerations** <br>This model uses optical character recognition (OCR) technology to scan .pdf files, image files, and .tiff files. OCR processing works best on documents that meet the following requirements: <br> - File format of .jpg, .png, or .pdf (text or scanned). Text-embedded .pdf files are better, because there won't be any errors in character extraction and location. <br> - For .pdf and .tiff files, up to 2,000 pages can be processed. <br> - The file size must be less than 50 MB. <br> - For images, dimensions must be between 50 x 50 and 10,000 x 10,000 pixels. <br> - For .pdf files, dimensions must be at most 17 x 17 inches, corresponding to Legal or A3 paper sizes and smaller. <br> - The total size of the training data is 500 pages or less. <br> Note the following differences about Microsoft Office text-based files and OCR-scanned files (.pdf, image, or .tiff): <br> - Office files: Truncated at 64,000 characters (in training and when run against files in a document library). <br> - OCR-scanned files: There's a 20-page limit.|
+| ![Globe symbol.](/office/media/icons/globe-internet.png) | **Multi-Geo environments** <br>When setting up Syntex in a [Microsoft 365 Multi-Geo](/microsoft-365/enterprise/microsoft-365-multi-geo) environment, you can only configure it to use the model type in the central location. If you want to use this model type in a satellite location, contact Microsoft support. |
+| ![Objects symbol.](/office/media/icons/objects-blue.png) | **Multi-model libraries** <br>If two or more trained models are applied to the same library, the file is classified using the model that has the highest average confidence score. The extracted entities will be from the applied model only. |
+
+### Receipt processing
+
+| Icon | Description |
+| - | - |
+| ![Files symbol.](/office/media/icons/files-blue.png) | **Supported file types** <br>This model supports the following file types: .bmp, .jpeg, .pdf, .png, and .tiff. |
+| ![Conversation symbol.](/office/media/icons/chat-room-conversation-blue.png) | **Supported languages** <br>This model supports English sales receipts from Australia, Canada, Great Britain, India, and the United States. |
+| ![Paragraph symbol.](/office/media/icons/paragraph-writing-blue.png) | **OCR considerations** <br>This model uses optical character recognition (OCR) technology to scan .pdf files, image files, and .tiff files. OCR processing works best on documents that meet the following requirements: <br> - File format of .jpg, .png, or .pdf (text or scanned). Text-embedded .pdf files are better, because there won't be any errors in character extraction and location. <br> - For .pdf and .tiff files, up to 2,000 pages can be processed. <br> - The file size must be less than 50 MB. <br> - For images, dimensions must be between 50 x 50 and 10,000 x 10,000 pixels. <br> - For .pdf files, dimensions must be at most 17 x 17 inches, corresponding to Legal or A3 paper sizes and smaller. <br> - The total size of the training data is 500 pages or less. <br> Note the following differences about Microsoft Office text-based files and OCR-scanned files (.pdf, image, or .tiff): <br> - Office files: Truncated at 64,000 characters (in training and when run against files in a document library). <br> - OCR-scanned files: There's a 20-page limit.|
+| ![Globe symbol.](/office/media/icons/globe-internet.png) | **Multi-Geo environments** <br>When setting up Syntex in a [Microsoft 365 Multi-Geo](/microsoft-365/enterprise/microsoft-365-multi-geo) environment, you can only configure it to use the model type in the central location. If you want to use this model type in a satellite location, contact Microsoft support. |
+| ![Objects symbol.](/office/media/icons/objects-blue.png) | **Multi-model libraries** <br>If two or more trained models are applied to the same library, the file is classified using the model that has the highest average confidence score. The extracted entities will be from the applied model only. |
syntex Set Up Content Understanding https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/set-up-content-understanding.md
+
+ Title: Set up Microsoft Syntex
++++
+audience: admin
+++
+- enabler-strategic
+- m365initiative-syntex
+
+- admindeeplinkMAC
+search.appverid: MET150
+ms.localizationpriority: high
+description: Set up Microsoft Syntex.
++
+# Set up Microsoft Syntex
+
+Admins can use the <a href="https://go.microsoft.com/fwlink/p/?linkid=2024339" target="_blank">Microsoft 365 admin center</a> to set up Microsoft Syntex.
+
+Consider the following before you start:
+
+- In which SharePoint sites will you enable document processing? All of them, some, or select sites?
+- What will you name your default content center?
+
+You can change your settings after initial setup in the <a href="https://go.microsoft.com/fwlink/p/?linkid=2024339" target="_blank">Microsoft 365 admin center</a>.
+
+Prior to setup, make sure to plan for the best way to set up and configure content understanding in your environment. For example, you need to make the following decisions:
+
+- The SharePoint sites in which you want to enable document processing - all of them, some, or selected sites
+- The name and admins for your content center
+
+## Requirements
+
+> [!NOTE]
+> You must have Global admin or SharePoint admin permissions to be able to access the Microsoft 365 admin center and set up Syntex.
+
+As an admin, you can also make changes to your selected settings anytime after setup, and throughout the content understanding management settings in the <a href="https://go.microsoft.com/fwlink/p/?linkid=2024339" target="_blank">Microsoft 365 admin center</a>.
+
+### Custom Power Platform environments
+
+If you plan to use a custom Power Platform environment, you must install the *AI Builder for Project Cortex* app in this environment. See [Manage Dynamics 365 apps](/power-platform/admin/manage-apps#install-an-app-in-the-environment-view) for details and look for the *AI Builder for Project Cortex* app in the list of Dynamics 365 apps.
+
+You also need to [allocate AI Builder credits](/power-platform/admin/capacity-add-on) to the custom environment before you can create document processing models.
+
+When using a custom environment, model creators must be assigned the Environment Maker security role and model users must be assigned the Basic User security role. See [Assign a security role to a user](/power-platform/admin/assign-security-roles) for more information.
+
+Users creating models in a [content center site](/microsoft-365/contentunderstanding/create-a-content-center) must be site members. Users creating models locally outside the content center must be site owners of those sites.
+
+### Licensing
+
+To use Syntex, your organization must have a subscription to Syntex, and each user must have a license assigned. Syntex licenses include the following apps, which must all be assigned:
+
+- Syntex
+- Syntex - SPO type
+- Common Data Service for Syntex
+
+To use structured document processing or freeform document processing models, you also need AI Builder credits. For each licensed user of Syntex, an allocation of AI Builder credits is provided each month.
+
+For details about Syntex licensing, see [Microsoft Syntex licensing](syntex-licensing.md)
+
+### Pay-as-you-go preview
+
+Microsoft Syntex is offering a limited-time free preview for pay-as-you-go document processing charged through an Azure subscription. The preview allows you to track Microsoft Syntex processing events at no cost to assess usage and estimate costs for a future pay-as-you-go license. For details about the preview, see [Microsoft Syntex pay-as-you-go preview](/legal/microsoft-365/microsoft-syntex-azure-billing-trial). To set up the preview, see [Configure Microsoft Syntex for Azure pay-as-you-go billing](syntex-azure-billing.md).
+
+## To set up Syntex
+
+1. In the Microsoft 365 admin center, select <a href="https://go.microsoft.com/fwlink/p/?linkid=2171997" target="_blank">**Setup**</a>, and then view the **Files and content** section.
+
+1. In the **Files and content** section, select **Use content AI with Microsoft Syntex**.
+
+1. On the **Use content AI with Microsoft Syntex** page, select **Set up Microsoft Syntex** to walk through the setup process. <br/>
+
+1. On the **Configure AI Builder model creation** page, you can choose if you want to let end users create and train models that use AI Builder and apply them to document libraries. A menu option will be available in the document library ribbon in SharePoint document libraries in which it is enabled.
+
+ For **Which SharePoint sites should show the option to create structured and freeform document processing models**, you can select:</br>
+ - **All SharePoint sites** to make it available to all SharePoint libraries in your organization.</br>
+ - **Libraries in selected SharePoint sites**, and then select the sites in which you want to make it available or upload a list of up to 50 sites.</br>
+ - **No SharePoint libraries** if you don't want to make it available to any sites (you can change this after setup).
+
+ > [!Note]
+ > Removing a site after it has been included does not affect existing models applied to the libraries in that site or the ability to apply unstructured document processing models to a library.
+
+ If you want to enable model creation in all content center sites, select the **Enable AI Builder model creation in all content center sites** check box under **Libraries in selected SharePoint sites**.
+
+ If you have multiple Power Platform environments configured, you can choose which one you want to use with for document processing. (This option will not appear if you only have one environment.)
+
+ For **Power Platform environment**, you can select:
+ - **Use the default environment** to use your default Power Platform environment.
+ - **Use a custom environment** to use a custom environment. Choose the environment that you want to use from the list. ([See the requirements for a custom environment](/microsoft-365/contentunderstanding/set-up-content-understanding#requirements).)
+
+ Select **Next**.
+
+1. On the **Create a content center** page, you can create a SharePoint content center site where your users can create and manage unstructured document processing models. If you previously created a content center from the SharePoint admin center, that information will display here and you can just select **Next**.
+
+ 1. For **Content center name**, type the name you want to give your content center site.
+
+ 1. The **Site address** will show the URL for your site, based on what you selected for the site name. If you want to change it, select **Edit**.
+
+ Select **Next**.
+
+1. On the **Review and finish** page, you can look at your selected setting and choose to make changes. If you are satisfied with your selections, select **Activate**.
+
+1. On the confirmation page, select **Done**.
+
+1. You'll be returned to your **Use content AI with Microsoft Syntex** page. From this page, you can select **Manage Microsoft Syntex** to make any changes to your configuration settings.
+
+If you plan to use the pay-as-you-go preview, see [Configure Microsoft Syntex for Azure pay-as-you-go billing](syntex-azure-billing.md).
+
+## Assign licenses
+
+Once you have configured Syntex, you must assign licenses for the users who will be using any Syntex features.
+
+To assign licenses:
+
+1. In the Microsoft 365 admin center, under **Users**, select <a href="https://go.microsoft.com/fwlink/p/?linkid=834822" target="_blank">**Active users**</a>.
+
+1. Select the users that you want to license, and choose **Manage product licenses**.
+
+1. Choose **Apps** from the drop-down menu.
+
+1. Select **Show apps for Syntex**. Under **Apps**, make sure **Common Data Service for Syntex**, **Syntex**, and **Syntex - SPO type** are all selected.
+
+1. Select **Save changes**.
+
+## See also
+
+[Overview of the document processing model in AI Builder](/ai-builder/form-processing-model-overview)
+
+[Create and manage environments in the Power Platform admin center](/power-platform/admin/create-environment)
syntex Skos Format Reference https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/skos-format-reference.md
+
+ Title: SKOS format reference for SharePoint taxonomy
+++
+audience: admin
++
+search.appverid:
+
+- enabler-strategic
+- m365initiative-syntex
+ms.localizationpriority: high
+description: Learn about the SKOS format reference for SharePoint taxonomy.
++
+# SKOS format reference for SharePoint taxonomy
+
+This article includes RDF vocabulary used to represent [SharePoint taxonomy](/dotnet/api/microsoft.sharepoint.taxonomy) and is based on [SKOS](https://www.w3.org/TR/skos-primer/). For serialization of this RDF syntax, use RDF [TURTLE](https://www.w3.org/TR/turtle/).
+
+The following table shows the [SKOS](https://www.w3.org/TR/skos-primer/) equivalents for the [SharePoint taxonomy](/dotnet/api/microsoft.sharepoint.taxonomy) vocabulary. SharePoint doesn't support [SKOS](https://www.w3.org/TR/skos-primer/) values that have no SharePoint taxonomy equivalent.
+
+|SharePoint taxonomy|SKOS equivalent|
+|:--|:--|
+|sharepoint-taxonomy: Term|skos: Concept|
+|sharepoint-taxonomy: TermSet|skos: ConceptScheme|
+|sharepoint-taxonomy: inTermSet|skos: inScheme|
+|sharepoint-taxonomy: hasTopLevelTerm|skos: hasTopConcept|
+|sharepoint-taxonomy: topLevelTermOf|skos: topConceptOf|
+|sharepoint-taxonomy: defaultLabel|skos: prefLabel|
+|sharepoint-taxonomy: termSetName|skos: prefLabel|
+|sharepoint-taxonomy: propertyName|skos: prefLabel|
+|sharepoint-taxonomy: otherLabel|skos: altLabel|
+|sharepoint-taxonomy: description|skos: definition|
+|sharepoint-taxonomy: parent|skos: broader|
+|sharepoint-taxonomy: child|skos: narrower|
+
+The following table displays the entities of the SharePoint taxonomy vocabulary derived from [OWL](https://www.w3.org/TR/owl2-primer/).
+
+|SharePoint taxonomy vocabulary|Derived from OWL|
+|:--|:-|
+|sharepoint-taxonomy: isAvailableForTagging|owl: datatypeproperty|
+|sharepoint-taxonomy: SharedCustomPropertyForTerm|owl: ObjectProperty|
+|sharepoint-taxonomy: LocalCustomPropertyForTerm|owl: ObjectProperty|
+|sharepoint-taxonomy: CustomPropertyForTermSet|owl: ObjectProperty|
+
+## SharePoint taxonomy vocabulary
+
+A taxonomy is a formal classification system. A taxonomy groups the words, labels, and terms that describe something, and then arranges the groups into a hierarchy.
+
+**sharepoint-taxonomy:Term**
+
+Represents a Term or a Keyword in a managed metadata hierarchy.
+
+A [Term](/dotnet/api/microsoft.sharepoint.taxonomy.term) is the atomic unit of a SharePoint [TermStore](/dotnet/api/microsoft.sharepoint.taxonomy.termstore). Each [Term](/dotnet/api/microsoft.sharepoint.taxonomy.term) belongs to a [TermSet](/dotnet/api/microsoft.sharepoint.taxonomy.termset) that belongs to a [TermGroup](/dotnet/api/microsoft.sharepoint.taxonomy.group).
+
+The syntax to define a [Term](/dotnet/api/microsoft.sharepoint.taxonomy.term) is as follows:
+
+```SKOS
+ex:TermA a sharepoint-taxonomy:Term;
+ sharepoint-taxonomy:inTermSet ex:TermSetA;
+ sharepoint-taxonomy:topLevelTermOf ex:TermSetA;
+ sharepoint-taxonomy:child ex:TermA1;
+ sharepoint-taxonomy:isAvailableForTagging ΓÇ£trueΓÇ¥^^xsd:Boolean;
+ sharePoint-taxonomy:defaultLabel ΓÇ£Term AΓÇ¥@en-us.
+```
+
+A [Term](/dotnet/api/microsoft.sharepoint.taxonomy.term) compulsorily exists within a [TermSet](/dotnet/api/microsoft.sharepoint.taxonomy.termset). DefaultLabel is the name of the [Term](/dotnet/api/microsoft.sharepoint.taxonomy.term) as it appears in the visual representation. The required fields for defining a [Term](/dotnet/api/microsoft.sharepoint.taxonomy.term) include:
+
+- sharepoint-taxonomy: defaultLabel
+- sharepoint-taxonomy: inTermSet
+
+A [Term](/dotnet/api/microsoft.sharepoint.taxonomy.term) can:
+
+- Be hierarchically related to another [Term](/dotnet/api/microsoft.sharepoint.taxonomy.term) that is provided both the [Terms](/dotnet/api/microsoft.sharepoint.taxonomy.term) belong to the same [TermSet](/dotnet/api/microsoft.sharepoint.taxonomy.termset).
+- Have multiple child [Terms](/dotnet/api/microsoft.sharepoint.taxonomy.term), but only a single parent [Term](/dotnet/api/microsoft.sharepoint.taxonomy.term).
+- Not have a parent [Term](/dotnet/api/microsoft.sharepoint.taxonomy.term) defined, if it's a topLevelTermOf a [TermSet](/dotnet/api/microsoft.sharepoint.taxonomy.termset).
+- Have one defaultLabel, per [TermStore](/dotnet/api/microsoft.sharepoint.taxonomy.termstore) working language.
+- Not exist if it neither contains a parent [Term](/dotnet/api/microsoft.sharepoint.taxonomy.term), nor is the topLevelTermOf a [TermSet](/dotnet/api/microsoft.sharepoint.taxonomy.termset).
+- Have only a unique defaultLabel in the same hierarchical level.
+
+**sharepoint-taxonomy:TermSet**
+
+Represents a hierarchical or flat set of Term objects known as a "TermSet".
+
+As the name suggests, TermSet is a set of [Terms](/dotnet/api/microsoft.sharepoint.taxonomy.term). A [Term](/dotnet/api/microsoft.sharepoint.taxonomy.term) in a [TermStore](/dotnet/api/microsoft.sharepoint.taxonomy.termstore) must belong to a [TermSet](/dotnet/api/microsoft.sharepoint.taxonomy.termset). No [Term](/dotnet/api/microsoft.sharepoint.taxonomy.term) can exist independently.
+
+The syntax to define a [TermSet](/dotnet/api/microsoft.sharepoint.taxonomy.termset) is:
+
+```SKOS
+ex:TermSetA a sharepoint-taxonomy:TermSet;
+ sharepoint-taxonomy:termSetName ΓÇ£TermSet A";
+ sharepoint-taxonomy:isAvailableForTagging ΓÇ£trueΓÇ¥^^xsd:Boolean;
+ sharepoint-taxonomy:hasTopLevelTerm Ex:Term A.
+```
+
+[TermSets](/dotnet/api/microsoft.sharepoint.taxonomy.termset) are logically grouped together in [TermGroups](/dotnet/api/microsoft.sharepoint.taxonomy.group). The required field for defining a [TermSet](/dotnet/api/microsoft.sharepoint.taxonomy.termset) is:
+
+- sharepoint-taxonomy: termSetName
+
+If the termSetName provided isn't unique within the [TermGroup](/dotnet/api/microsoft.sharepoint.taxonomy.group), SharePoint appends a number at the end of the name to maintain the uniqueness of termSetName(s).
+
+**sharepoint-taxonomy:hasTopLevelTerm**
+
+SharePoint uses this property to map the top-most [Term](/dotnet/api/microsoft.sharepoint.taxonomy.term) in the [TermSet](/dotnet/api/microsoft.sharepoint.taxonomy.termset), which is the entry point to the hierarchy of [Terms](/dotnet/api/microsoft.sharepoint.taxonomy.term) in a [TermSet](/dotnet/api/microsoft.sharepoint.taxonomy.termset). This is an inverse relation to sharepoint-taxonomy: topLevelTermOf.
+
+The syntax to define this is:
+
+```SKOS
+ex:TermSetA sharepoint-taxonomy:hasTopLevelTerm ex:TermA.
+```
+
+> [!NOTE]
+> You cannot define the top level [Term](/dotnet/api/microsoft.sharepoint.taxonomy.term) of a parent [Term](/dotnet/api/microsoft.sharepoint.taxonomy.term).
+
+**sharepoint-taxonomy:topLevelTermOf**
+
+Sharepoint-taxonomy: topLevelTermOf is the inverse of sharepoint-taxonomy: hasTopLevelTerm
+
+The syntax to define this is:
+
+```SKOS
+ex:TermA sharepoint-taxonomy:topLevelTermOf ex:TermSetA.
+```
+
+**sharepoint-taxonomy:inTermSet**
+
+Use this to map a [Term](/dotnet/api/microsoft.sharepoint.taxonomy.term) to a [TermSet](/dotnet/api/microsoft.sharepoint.taxonomy.termset). A [Term](/dotnet/api/microsoft.sharepoint.taxonomy.term) can only exist in a single [TermSet](/dotnet/api/microsoft.sharepoint.taxonomy.termset). SharePoint requires this property when [defining a term](#sharepoint-taxonomy-vocabulary).
+
+## Required labels
+
+Your organization may want to do careful planning before you start to use managed metadata. The amount of planning that you must do depends on how formal your taxonomy is. It also depends on how much control that you want to impose on metadata. At each level of the hierarchy, you need to configure required labels for a Term or TermSet.
+
+A Term can have one or more labels in the default language, and zero or more labels in the non-default language. If the term has labels in a language, one of the labels must be the default label.
+
+**sharepoint-taxonomy:defaultLabel**
+
+Use this default lexical label for a [Term](/dotnet/api/microsoft.sharepoint.taxonomy.term) that is a required parameter for a [Term](/dotnet/api/microsoft.sharepoint.taxonomy.term). Use to visually representing the [Term](/dotnet/api/microsoft.sharepoint.taxonomy.term).
+
+The syntax to define a defaultLabel is:
+
+```SKOS
+ex:TermA sharepoint-taxonomy:defaultLabel ΓÇ£Term AΓÇ¥@en-us.
+```
+
+The defaultLabel contains two parts to it ΓÇô the string and the language tag. The language must be one of the [TermStore](/dotnet/api/microsoft.sharepoint.taxonomy.termstore) working languages. The defaultLabel must be unique for all [Terms](/dotnet/api/microsoft.sharepoint.taxonomy.term) in the same [TermSet](/dotnet/api/microsoft.sharepoint.taxonomy.termset), at the same hierarchical level.
+
+**sharepoint-taxonomy:termSetName**
+
+Gets and sets the name for the current TermSet object.
+
+This is the lexical label for a [TermSet](/dotnet/api/microsoft.sharepoint.taxonomy.termset), in a [TermStore](/dotnet/api/microsoft.sharepoint.taxonomy.termstore) working language. This is a required parameter for a [TermSet](/dotnet/api/microsoft.sharepoint.taxonomy.termset). Use to visually representing a [TermSet](/dotnet/api/microsoft.sharepoint.taxonomy.termset).
+
+The syntax to define a termSetName is:
+
+```SKOS
+ex:TermA sharepoint-taxonomy:TermSetName ΓÇ£Term Set AΓÇ¥@en-us.
+```
+
+**sharepoint-taxonomy:propertyName**
+
+Gets and sets the property name for the current TermSet object.
+
+This is the lexical label for a sharepoint-taxonomy:SharedCustomPropertyForTerm, sharepoint-taxonomy:LocalCustomPropertyForTerm and sharepoint-taxonomy:CustomPropertyForTermSet in a [TermStore](/dotnet/api/microsoft.sharepoint.taxonomy.termstore) working language.
+
+The sharepoint-taxonomy: propertyName is treated as the key of the CustomProperty.
+
+The syntax to define a propetyName is:
+
+```SKOS
+ex:SharedCustomProperty1 sharepoint-taxonomy:propertyName ΓÇ£Shared Custom Property Key 1ΓÇ¥@en-us.
+```
+
+## Optional labels
+
+You can also add optional labels to your taxonomy.
+
+**sharepoint-taxonomy:otherLabel**
+
+This is the alternate lexical label for a [Term](/dotnet/api/microsoft.sharepoint.taxonomy.term).
+
+The syntax to define an otherLabel is:
+
+```SKOS
+ex:TermA sharepoint-taxonomy:otherLabel ΓÇ£Term AΓÇ¥@en-us.
+```
+
+## Semantic relationships
+
+Taxonomies have hierarchical and sometimes a simple ΓÇ£related termΓÇ¥ associative relationship, but some have "semantic relationships" or custom-created relationships.
+
+**sharepoint-taxonomy:parent**
+
+This hierarchically relates a [Term](/dotnet/api/microsoft.sharepoint.taxonomy.term) to another [Term](/dotnet/api/microsoft.sharepoint.taxonomy.term). A [Term](/dotnet/api/microsoft.sharepoint.taxonomy.term) could be a top level [Term](/dotnet/api/microsoft.sharepoint.taxonomy.term) of a [TermSet](/dotnet/api/microsoft.sharepoint.taxonomy.termset), but in case it doesnΓÇÖt it must have a parent [Term](/dotnet/api/microsoft.sharepoint.taxonomy.term).
+
+The syntax to define a parent is:
+
+```SKOS
+ex:TermA1 sharepoint-taxonomy:parent ex:TermA.
+```
+
+This means that TermA is the parent and TermA is the child.
+
+**sharepoint-taxonomy:child**
+
+The object contains one or more child TermSet instances, and these can be accessed through the TermSets property. This class also provides methods for creating new child TermSet objects. Permissions for editing child Term and TermSet instances are specified on the group.
+
+This hierarchically relates a [Term](/dotnet/api/microsoft.sharepoint.taxonomy.term) to another [Term](/dotnet/api/microsoft.sharepoint.taxonomy.term).
+
+The syntax to define a child is:
+
+```SKOS
+ex:TermA sharepoint-taxonomy:child ex:TermA1.
+```
+
+This means that TermA is the parent and TermA is the child.
+
+## Documentation notes
+
+This section discusses the taxonomy detailed in the Microsoft.SharePoint.Taxonomy Namespace.
+
+**sharepoint-taxonomy:description**
+
+This is a detailed explanation of any [SharePoint taxonomy](/dotnet/api/microsoft.sharepoint.taxonomy) vocabulary entity.
+
+The syntax to add a description is:
+
+```SKOS
+ex:TermA sharepoint-taxonomy:description ΓÇ£Term A is the top level term of TermSetAΓÇ¥@en-us.
+```
+
+## Custom properties
+
+Gets the collection of custom property objects for the current Term object from the read-only dictionary.
+
+Custom Properties are key-values pairs that can be defined for a [Term](/dotnet/api/microsoft.sharepoint.taxonomy.term) or a [TermSet](/dotnet/api/microsoft.sharepoint.taxonomy.termset), to further the description of the [Term](/dotnet/api/microsoft.sharepoint.taxonomy.term) or a [TermSet](/dotnet/api/microsoft.sharepoint.taxonomy.termset). SharePoint specifies the key of the custom property with the help of propertyName.
+
+**sharepoint-taxonomy:CustomPropertyForTermSet**
+
+The syntax to define this is:
+
+```SKOS
+ex:CustomProp1 rdf:type sharepoint-taxonomy:CustomPropertyForTermSet;
+ sharepoint-taxonomy:propertyName ΓÇ£ColourΓÇ¥.
+
+ex:TermSetA ex:CustomProp1 ΓÇ£RedΓÇ¥@en-us.
+```
+
+**sharepoint-taxonomy:SharedCustomPropertyForTerm**
+
+If the custom property for a [Term](/dotnet/api/microsoft.sharepoint.taxonomy.term) needs to be carried along with the [Term](/dotnet/api/microsoft.sharepoint.taxonomy.term), when you reuse the [Term](/dotnet/api/microsoft.sharepoint.taxonomy.term) somewhere else, then you need to be define it under SharedCustomPropertyForTerm.
+
+The syntax to define this is:
+
+```SKOS
+ex:CustomProp2 rdf:type sharepoint-taxonomy:SharedCustomPropertyForTerm;
+ sharepoint-taxonomy:propertyName ΓÇ£LengthΓÇ¥.
+
+ex:TermA ex:CustomProp2 ΓÇ£5 cmΓÇ¥@en-us.
+```
+**sharepoint-taxonomy:LocalCustomPropertyForTerm**
+
+If the custom property for a [Term](/dotnet/api/microsoft.sharepoint.taxonomy.term) doesn't need to be carried along with the [Term](/dotnet/api/microsoft.sharepoint.taxonomy.term), when you reuse the [Term](/dotnet/api/microsoft.sharepoint.taxonomy.term) somewhere else, then you need to define it under LocalCustomPropertyForTerm.
+
+The syntax to define this is:
+
+```SKOS
+ex:CustomProp3 rdf:type sharepoint-taxonomy:LocalCustomPropertyForTerm;
+ sharepoint-taxonomy:propertyName ΓÇ£widthΓÇ¥.
+
+ex:TermA ex:CustomProp3 ΓÇ£5 cmΓÇ¥@en-us.
+```
+
+## Data properties
+
+At each level of the hierarchy, you can configure specific data properties for a Term or TermSet.
+
+**sharepoint-taxonomy:isAvailableForTagging**
+
+Use this to specify if a [Term](/dotnet/api/microsoft.sharepoint.taxonomy.term) or a [TermSet](/dotnet/api/microsoft.sharepoint.taxonomy.termset) available in SharePoint Lists and Libraries.
+
+The syntax for this is:
+
+```SKOS
+ex:TermA sharepoint-taxonomy:isAvailableForTagging "true"^^xsd:Boolean;
+```
+
+## Domain and range
+
+The table below describes the domain and range of SharePoint taxonomy vocabulary.
+
+|Predicates/verb|Meaning|Domain|Range|
+|:--|:|:--|:-|
+inTermSet|In term set|Term|Term Set|
+inTermGroup|In term group|TermSet|TermGroup|
+topLevelTermOf|Is Top Level Term Of|Term|TermSet|
+hasTopLevelTerm|Has top level term|Term Set|Term|
+termSetName|Term set has Name|Term|Plain literal|
+defaultLabel|Term has default label|Term|Plain literal|
+otherLabel|Term has other label|Term|Plain literal|
+propertyName|Has Property Label|SharedCustomPropertyForTerm, LocalCustomPropertyForTerm, CustomPropertyForTermSet |Boolean, String, Integer, Decimal, Double|
+|description|Has Description|All|Plain literal|
+|parent|Has parent|Term|Term|
+|child|Has Child|Term|Term|
+|isAvailableForTagging|Is available for tagging|Term, Term Set|Boolean|
+|SharedCustomPropertyForTerm|Has shared custom property|Term|Boolean, string, Integer, Decimal, Double|
+|LocalCustomPropertyForTerm|Has local custom property|Term|Boolean, String, Integer, Decimal, Double|
+|CustomPropertyForTermSet|Has Custom Property|TermSet|Boolean, String, Integer, Decimal, Double|
+
+[SKOS](https://www.w3.org/TR/skos-primer/) valid scenarios that [SharePoint taxonomy](/dotnet/api/microsoft.sharepoint.taxonomy) doesn't allow:
+
+- Hierarchical redundancy - A [SKOS](https://www.w3.org/TR/skos-primer/) concept can be attached to several broader concepts at the same time, but a sharepoint-taxonomy:Term can have only one sharepoint-taxonomy:parent, hence cyclic dependency, of Terms are also not allowed.
+- Orphaned terms aren't allowed in SharePoint taxonomy. Every sharepoint-taxonomy: Term should either have a sharepoint-taxonomy: parent or it should be the sharepoint-taxonomy: topLevelTermOf a TermSet.
+- SharePoint taxonomy doesn't support associative relations.
+- SharePoint taxonomy only allows two types of Hierarchical relations ΓÇô sharepoint-taxonomy: parent and sharepoint-Taxonomy: child.
+- Unlike [SKOS](https://www.w3.org/TR/skos-primer/) the hierarchical relationship in SharePoint taxonomy vocabulary, can only be established with Terms within the same TermSet.
+
+## See also
+
+[Import a term set using a SKOS-based format](import-term-set-skos.md)
syntex Solution Manage Contracts In Microsoft 365 https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/solution-manage-contracts-in-microsoft-365.md
+
+ Title: Manage contracts using a Microsoft 365 solution
++++
+audience: admin
+ Last updated : ++
+- m365solution-managecontracts
+- m365solution-overview
+- highpri
+- m365initiative-syntex
+search.appverid:
+ms.localizationpriority: medium
+ROBOTS:
+description: Learn how to manage contracts using a Microsoft 365 solution of Microsoft Syntex, SharePoint lists, Microsoft Teams, and Power Automate.
++
+# Manage contracts using a Microsoft 365 solution
+
+This article describes how to create a contracts management solution for your organization by using Microsoft Syntex and components of Microsoft 365. It provides you with a framework to help you plan and create a solution that fits your unique business needs. Even though this solution talks about contract management, you can adapt it to create other document management solutions, such as for statements of work or invoices.
+
+</br>
+
+> [!VIDEO https://www.microsoft.com/videoplayer/embed/RWJUR0]
+
+</br>
+
+## Identify the business problem
+
+The first step in planning your contract management system is to understand the problem you're trying to solve. For this solution, four key issues need to be addressed:
+
+- **Identify contracts**. Your organization works with many documents, such as invoices, contracts, statements of work, and so on. Some are digital assets sent through email, and some are paper assets sent through traditional mail. You need a way to identify all customer contracts from all other documents, and then classifying them as such.
+
+- **Track the history of contract approvals**. Your organization needs a reliable way to find whether contracts have been either approved or rejected, and whether payment has been processed.
+
+- **Site to manage contract approvals**. Your organization needs to set up a collaborative site in which all required stakeholders can easily review contracts. Stakeholders should be able to review the whole contract if needed, but mostly care about seeing several key fields from each contract (for example, customer name, PO number, and total cost). Stakeholders should be able to easily approve or reject incoming contracts.
+
+- **Route reviewed contracts**. Approved and rejected contracts need to be routed through a specific workflow. Approved contracts need to be routed to a third-party application for payment processing. Rejected contracts need to be routed for additional review.
+
+## Overview of the solution
+
+ ![Diagram of the solution using Syntex, SharePoint lists, Teams, and Power Automate.](../media/content-understanding/syntex-solution-manage-contracts-setup-steps.png)
+
+This contract management solution guidance includes four components of Microsoft 365:
+
+- **Microsoft Syntex**: Create models to identify and classify your contract files and then extract the appropriate data from them.
+
+- **Microsoft SharePoint lists**: Use the formatting available in modern SharePoint lists to present contracts in a business-friendly format.
+
+- **Microsoft Teams**: Use the functionality of a Teams channel and associated tabs to allow your stakeholders to review and manage contracts.
+
+- **Power Automate**: Use flows to guide contracts through the approval process, and then to a third-party application for payment.
+
+### How it all works
+
+ ![Diagram of the solution showing the workflow to upload documents, extract data, notify stakeholders, and approve or reject the contract.](../media/content-understanding/syntex-solution-manage-contracts-overview.png)
+
+1. Documents are uploaded to a SharePoint document library. A Syntex unstructured document processing model has been applied to the document library. It checks each file to see if any match a "contract" content type it's trained to look for. If it finds a match, it classifies the file as a "contract" and updates the content type for the document.
+
+2. The model also pulls out specific data from each contract file that stakeholders are interested in seeing, such as the *Client*, *Contractor*, and *Fee amount*.
+
+ The following page is an example of a contract that the model is trained to identify.
+
+ ![Example of a contract.](../media/content-understanding/contract.png)
+
+3. In Microsoft Teams, all stakeholders are members of a secure Teams channel in which all contracts in the document library are visible for approval or rejection. By using Teams functionality, all stakeholders are notified when new contracts need to be reviewed.
+
+4. By using Power Automate, contracts are moved through the approval process in the Teams channel. When a member approves a contract, the contract status is changed to approved, all members are notified through a Teams post, and a line item is created to show that the contract is ready for payout. This process can be extended to write directly to a third-party financial application for payment.
+
+5. When a member rejects a contract, the status is changed to rejected, and all members are notified through a Teams post.
+
+6. The end result of this solution is an automated business process for your organization. Employees can easily use the custom tile view in Teams to initiate and monitor the approval workflow of your documents.
+
+ ![Contracts tab.](../media/content-understanding/tile-view.png)
+
+### Licensing requirements
+
+This solution relies on the following functionality, all available as part of a Microsoft 365 Enterprise (E1, E3, E5, F3) or Business (Basic, Standard, or Premium) license:
+
+- Microsoft Syntex
+- Microsoft Teams
+- Power Automate
+
+### Learn how to use Syntex
+
+New to Microsoft Syntex? Learn how to use Syntex to manage content using AI.
+
+The [Get started with Microsoft Syntex](/training/paths/syntex-get-started) learning path will teach how you can use unstructured, freeform, and unstructured document processing models to classify documents, extract text, and label your documents for quick and easy knowledge management.
+
+## Create the solution
+
+The next sections will go into detail about how to configure your contracts management solution. It's divided into three steps:
+
+- [Step 1. Use Microsoft Syntex to identify contract files and extract data](solution-manage-contracts-step1.md)
+- [Step 2. Use Microsoft Teams to create your contract management channel](solution-manage-contracts-step2.md)
+- [Step 3. Use Power Automate to create the flow to process your contracts](solution-manage-contracts-step3.md)
syntex Solution Manage Contracts Step1 https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/solution-manage-contracts-step1.md
+
+ Title: Step 1. Use Microsoft Syntex to identify contract files and extract data
++++
+audience: admin
+ Last updated : +
+search.appverid:
+ms.localizationpriority: medium
+ROBOTS:
+description: Learn how to use Microsoft Syntex to identify contract files and extract data by using a Microsoft 365 solution.
++
+# Step 1. Use Microsoft Syntex to identify contract files and extract data
+
+Your organization needs a way to identify and classify all contract documents from the many files you receive. You also want to be able to quickly view several key elements in each of the contract files identified (for example, *Client*, *Contractor*, and *Fee amount*). You can do this by using Syntex] to create an unstructured document processing model and applying it to a document library.
+
+## Overview of the process
+
+[Unstructured document processing models](document-understanding-overview.md) uses artificial intelligence (AI) to automate classification of files and extraction of information. These types of models are also optimal in extracting information from unstructured and semi-structured documents where the information you need isn't contained in tables or forms, such as contracts.
+
+Unstructured document processing models use optical character recognition (OCR) technology to scan PDFs, images, and TIFF files, both when you train a model with example files and when you run the model against files in a document library.
+
+1. First, you need to find at least five example files that you can use to "train" the model to search for characteristics that are specific to the content type you're trying to identify (a contract).
+
+2. Using Syntex, create a new unstructured document processing model. Using your example files, you need to [create a classifier](create-a-classifier.md). By training the classifier with your example files, you teach it to search for characteristics that are specific to what you would see in your company's contracts. For example, [create an "explanation"](create-a-classifier.md#create-an-explanation) that searches for specific strings that are in your contracts, such as *Service Agreement*, *Terms of Agreement*, and *Compensation*. You can even train your explanation to look for these strings in specific sections of the document, or located next to other strings. When you think you have trained your classifier with the information it needs, you can test your model on a sample set of example files to see how efficient it is. After testing, if needed you can choose to make changes to your explanations to make them more efficient.
+
+3. In your model, you can [create an extractor](create-an-extractor.md) to pull out specific pieces of data from each contract. For example, for each contract, the information you're most concerned about is who the client is, the name of the contractor, and the total cost.
+
+4. After you successfully create your model, [apply it to a SharePoint document library](apply-a-model.md). As you upload documents to the document library, your unstructured document processing model will run and will identify and classify all files that match the contracts content type you defined in your model. All files that are classified as contracts will display in a custom library view. The files will also display the values from each contract that you defined in your extractor.
+
+ ![Contracts in document library.](../media/content-understanding/doc-lib-solution.png)
+
+5. If you have retention or security requirements for your contracts, you can also use your model to apply a [retention label](apply-a-retention-label-to-a-model.md) or a [sensitivity label](apply-a-sensitivity-label-to-a-model.md) that will prevent your contracts from being deleted for a specified period of time or to restrict who can access the contracts.
+
+## Steps to create and train your model
+
+> [!NOTE]
+> For these steps, you can use the example files in the [Contracts Management Solution Assets repository](https://github.com/pnp/syntex-samples/tree/main/scenario-samples/Contracts-Management). The examples in this repository contain both the model files and the files used to train the model.
+
+### Create a Contract model
+
+The first step is to create your Contract model.
+
+1. From the content center, select **New** > **Model** > **Teaching method**.
+
+2. On the **Create a model with the teaching method** pane, in the **Name** field, type the name of the model. For this contract management solution, you can name the model *Contract*.
+
+4. Choose **Create**. This creates a home page for the model.</br>
+
+ ![Screenshot of the Contract home page.](../media/content-understanding/models-contract-home-page.png)
++
+### Train your model to classify a type of file
+
+#### Add example files for your model
+
+You need to add at least five example files that are contract documents, and one example file that's not a contract document (for example, a statement of work).
+
+1. On the **Models > Contract** page, under **Key actions** > **Add example files**, select **Add files**.
+
+ ![Screenshot showing the Contracts page with Add example files option highlighted.](../media/content-understanding/key-actions-add-example-files.png)
+
+2. On the **Select example files for your model** page, open the Contract folder, select files you want to use, and then select **Add**. If you don't have example files there, select **Upload** to add them.
+
+#### Label the files as positive or negative examples
+
+1. On the **Models > Contract** page, under **Key actions** > **Classify files and run training**, select **Train classifier**.
+
+ ![Screenshot showing the Contracts page with Classify files and run training option highlighted.](../media/content-understanding/key-actions-classify-files.png)
+
+2. On the **Models > Contract > Contract classifier** page, in the viewer on the top of the first example file, you'll see text asking if the file is an example of the Contract model you created. If it is a positive example, select **Yes**. If it is a negative example, select **No**.
+
+3. From the **Labeled examples** list on the left, select other files that you want to use as examples, and label them.
+
+ ![Classifier home page.](../media/content-understanding/models-contract-classifier.png)
+
+#### Add at least one explanation to train the classifier
+
+1. On the **Models > Contract > Contract classifier** page, select the **Train** tab.
+
+2. In the **Trained files** section, you'll see a list of the example files that you previously labeled. Select one of the positive files from the list to display it in the viewer.
+
+3. In the **Explanations** section, select **New** and then **Blank**.
+
+4. On the **Create an explanation** page:
+
+ a. In the **Name** field, type the name of the explanation (such as "Agreement").
+
+ b. In the **Explanation type** field, select **Phrase list**, because you add a text string.
+
+ c. In the **Phrase list** box, type the string (such as "AGREEMENT"). You can select **Case sensitive** if the string needs to be case-sensitive.
+
+ d. Select **Save and train**.
+
+ ![Screenshot of the Create an explanation panel.](../media/content-understanding/contract-classifier-create-explanation.png)
+
+#### Test your model
+
+You can test your Contract model on example files it hasnΓÇÖt seen before. This is optional, but it can be a useful best practice.
+
+1. On the **Models > Contract > Contract classifier** page, select the **Test** tab. This runs the model on your unlabeled example files.
+
+2. In the **Test Files** list, your example files display and shows if the model predicted them to be positive or negative. Use this information to help determine the effectiveness of your classifier in identifying your documents.
+
+ ![Screenshot of the unlabeled files in the Text Files list.](../media/content-understanding/test-on-files.png)
+
+3. When done, select **Exit Training**.
+
+### Create and train an extractor
+
+1. On the **Models > Contract** page, under **Key actions** > **Create and train extractors**, select **Create extractor**.
+
+ ![Screenshot showing the Contracts page with Create and train extractors option highlighted.](../media/content-understanding/key-actions-create-extractors.png)
+
+2. On the **New entity extractor** panel, in the **New name** field, type the name of your extractor. For example, name it *Client* if you want to extract the name of the client from each contract.
+
+3. When you're done, select **Create**.
+
+#### Label the entity you want to extract
+
+When you create the extractor, the extractor page opens. Here you see a list of your sample files, with the first file on the list displayed in the viewer.
+
+![Screenshot of the Client extractor Labeled examples page.](../media/content-understanding/client-extractor-labeled-examples.png)
+
+To label the entity:
+
+1. From the viewer, select the data that you want to extract from the files. For example, if you want to extract the *Client*, you highlight the client value in the first file (in this example, *Best For You Organics*), and then select **Save**. You'll see the value display from the file in the **Labeled examples** list, under the **Label** column.
+
+2. Select **Next file** to autosave and open the next file in the list in the viewer. Or select **Save**, and then select another file from the **Labeled examples** list.
+
+3. In the viewer, repeat steps 1 and 2, then repeat until you saved the label in all the files.
+
+After you've labeled the files, a notification banner displays informing you to move to training. You can choose to label more documents or advance to training.
+
+#### Add an explanation
+
+You can create an explanation that provides a hint about the entity format itself and variations it might have in the example files. For example, a date value can be in many different formats, such as:
+
+- 10/14/2019
+- October 14, 2019
+- Monday, October 14, 2019
+
+To help identify the *Contract Start Date*, you can create an explanation.
+
+1. In the **Explanations** section, select **New** and then **Blank**.
+
+2. On the **Create an explanation** page:
+
+ a. In the **Name** field, type the name of the explanation (such as *Date*).
+
+ b. In the **Explanation type** field, select **Phrase list**.
+
+ c. In the **Value** field, provide the date variation as they appear in the sample files. For example, if you have date formats that appear as 0/00/0000, you enter any variations that appear in your documents, such as:
+
+ - 0/0/0000
+ - 0/00/0000
+ - 00/0/0000
+ - 00/00/0000
+
+4. Select **Save and train**.
+
+#### Test your model again
+
+You can test your Contract model on example files it hasnΓÇÖt seen before. This is optional, but it can be a useful best practice.
+
+1. On the **Models > Contract > Contract classifier** page, select the **Test** tab. This runs the model on your unlabeled example files.
+
+2. In the **Test files** list, your example files display and shows if the model is able to extract the information you need. Use this information to help determine the effectiveness of your classifier in identifying your documents.
+
+3. When done, select **Exit Training**.
+
+### Apply your model to a document library
+
+To apply your model to a SharePoint document library:
+
+1. On the **Models > Contract** page, under **Key actions** > **Apply model to libraries**, select **Apply model**.
+
+ ![Screenshot showing the Contracts page with Apply model to libraries option highlighted.](../media/content-understanding/key-actions-apply-model.png)
+
+2. On the **Add Contract** panel, select the SharePoint site that contains the document library that you want to apply the model to. If the site does not show in the list, use the search box to find it. Select **Add**.
+
+ > [!NOTE]
+ > You must have *Manage List* permissions or *Edit* rights to the document library you are applying the model to.
+
+3. After you select the site, select the document library to which you want to apply the model.
+
+4. Because the model is associated to a content type, when you apply it to the library it will add the content type and its view with the labels you extracted showing as columns. This view is the library's default view by default, but you can optionally choose to have it not be the default view by selecting **Advanced settings** and clearing the **Set this new view as default** check box.
+
+5. Select **Add** to apply the model to the library.
+
+6. On the **Models > Contract** page, in the **Libraries with this model** section, you'll see the URL to the SharePoint site listed.
+
+ ![Screenshot of the Contract home page showing the Libraries with this model section.](../media/content-understanding/contract-libraries-with-this-model.png)
+
+7. Under **Settings** > **Library settings**:
+
+ - Add a column named **Status** and select **Choice** as the column type.
+ - Apply the **In review**, **Approved**, and **Rejected** values.
+
+After you apply the model to the document library, you can begin uploading documents to the site and see the results.
+
+## Next step
+
+[Step 2. Use Microsoft Teams to create your contract management channel](solution-manage-contracts-step2.md)
syntex Solution Manage Contracts Step2 https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/solution-manage-contracts-step2.md
+
+ Title: Step 2. Use Microsoft Teams to create your contract management channel
++++
+audience: admin
+ Last updated :+
+search.appverid:
+ms.localizationpriority: medium
+ROBOTS:
+description: Learn how to use Microsoft Teams to create your contract management channel by using a Microsoft 365 solution.
++
+# Step 2. Use Microsoft Teams to create your contract management channel
+
+When your organization sets up a contracts management solution, you need a central location in which stakeholders can review and manage contracts. For this purpose, you can use [Microsoft Teams](/microsoftteams/) to set up a Teams channel and use the features in Teams to:
+
+- **Create a location for stakeholders to easily see all contracts that require action.** For example, in Teams you can create a **Contracts** tab in the Contract Management channel in which members can see a useful tile view of all contracts that need approval. You can also configure the view so that each "card" lists the important data you care about (such as *Client*, *Contractor*, and *Fee amount*).
+
+ ![Contracts tab.](../media/content-understanding/tile-view.png)
+
+- **Have a location for members to interact with each other and see important events.** For example, in Teams, the **Posts** tab can be used to have conversations, get updates, and see actions (such as a member rejecting a contract). When something has happened (such as a new contract submitted for approval), the **Posts** tab can be used not only to announce it, but also to keep a record of it. And if members subscribe to notifications, they'll get notified whenever there's an update.
+
+ ![Posts tab.](../media/content-understanding/posts.png)
+
+- **Have a location for members to see approved contracts to know when they can be submitted for payment.** In SharePoint, you'll need to create a **For Payout** list and include columns for **Client**, **Contractor**, and **Fee amount**, selecting **Single line of text** as the column type. You'll need to add the **For Payout** list as a Teams tab in the Contract Management channel, similar to [what you'll do for the **Contracts** tab](solution-manage-contracts-step2.md#attach-your-sharepoint-document-library-to-the-contracts-tab). The **For Payout** tab will list all contracts that will need to be submitted for payment. You can easily extend this solution to instead write this information directly to a third-party financial application (for example, Dynamics CRM).
+
+## Attach your SharePoint document library to the Contracts tab
+
+After you create a **Contracts** tab in your Contracts Management channel, you need to [attach your SharePoint document library to it](https://support.microsoft.com/office/add-a-sharepoint-page-list-or-document-library-as-a-tab-in-teams-131edef1-455f-4c67-a8ce-efa2ebf25f0b). The SharePoint document library you want to attach is the one in which you applied your unstructured document processing model to in the previous section.
+
+After you attach the SharePoint document library, you'll be able to view any classified contracts through a default list view.
+
+ ![List view of SharePoint library.](../media/content-understanding/list-view.png)
+
+## Customize your Contracts tab tile view
+
+> [!NOTE]
+> This section references code examples that are contained in the [ContractTileFormatting.json](https://github.com/pnp/syntex-samples/blob/main/scenario-samples/Contracts-Management/View%20Formatter/ContractTileFormatting.json) file that is included in the [Contracts Management Solution Assets repository](https://github.com/pnp/syntex-samples/tree/main/scenario-samples/Contracts-Management).
+
+While Teams lets you view your contracts in a tile view, you might want to customize it to view the contract data you want to make visible in the contract card. For example, for the **Contracts** tab, it is important for members to see the client, contractor, and fee amount on the contract card. All of these fields were extracted from each contract through your Syntex model that was applied to your document library. You also want to be able to change the tile header bar to different colors for each status so that members can easily see where the contract is in the approval process. For example, all approved contracts will have a blue header bar.
+
+ ![Tile view of SharePoint library.](../media/content-understanding/tile.png)
+
+The custom tile view you use requires you to make changes to the JSON file used to format the current tile view. You can reference the JSON file used to create the card view by looking at the [ContractTileFormatting.json](https://github.com/pnp/syntex-samples/blob/main/scenario-samples/Contracts-Management/View%20Formatter/ContractTileFormatting.json) file. In the following sections, you'll see specific sections of the code for features that are in the contract cards.
+
+If you want to see or make changes to the JSON code for your view in your Teams channel, in the Teams channel, select the view drop-down menu, and then select **Format current view**.
+
+ ![Screenshot of json format in Teams channel.](../media/content-understanding/jason-format.png)
+
+## Card size and shape
+
+In the [ContractTileFormatting.json](https://github.com/pnp/syntex-samples/blob/main/scenario-samples/Contracts-Management/View%20Formatter/ContractTileFormatting.json) file, look at the following section to see the code for how the size and shape of the card is formatted.
+
+```JSON
+ {
+ "elmType": "div",
+ "style": {
+ "background-color": "#f5f5f5",
+ "padding": "5px",
+ "width": "180px"
+ },
+ "children": [
+ {
+ "elmType": "img",
+ "attributes": {
+ "src": "@thumbnail.large"
+ },
+ "style": {
+ "width": "185px",
+ "height": "248px"
+ }
+ }
+```
+
+## Contract status
+
+The following code lets you define the status of each title card. Note that each status value (*New*, *In review*, *Approved*, and *Rejected*) will display a different color code for each. In the [ContractTileFormatting.json](https://github.com/pnp/syntex-samples/blob/main/scenario-samples/Contracts-Management/View%20Formatter/ContractTileFormatting.json) file, look at the section that defines the status.
+
+```JSON
+ {
+ "elmType": "div",
+ "children": [
+ {
+ "elmType": "div",
+ "style": {
+ "color": "white",
+ "background-color": "=if([$Status] == 'New', '#00b7c3', if([$Status] == 'In review', '#ffaa44', if([$Status] == 'Approved', '#0078d4', if([$Status] == 'Rejected', '#d13438', '#8378de'))))",
+ "padding": "5px 15px",
+ "height": "auto",
+ "text-transform": "uppercase",
+ "font-size": "12.5px"
+ },
+ "txtContent": "[$Status]"
+ }
+```
+
+## Extracted fields
+
+Each contract card will display three fields that were extracted for each contract (*Client*, *Contractor*, and *Fee Amount*). Additionally, you also want to display the time/date that the file was classified by the Syntex model used to identify it.
+
+In the [ContractTileFormatting.json](https://github.com/pnp/syntex-samples/blob/main/scenario-samples/Contracts-Management/View%20Formatter/ContractTileFormatting.json) file, the following sections define each of these.
+
+### Client
+
+This section defines how "Client" will display on the card, and uses the value for the specific contract.
+
+```JSON
+ {
+ "elmType": "div",
+ "style": {
+ "color": "#767676",
+ "font-size": "12px"
+ },
+ "txtContent": "Client"
+ },
+ {
+ "elmType": "div",
+ "style": {
+ "margin-bottom": "12px",
+ "font-size": "16px",
+ "font-weight": "600"
+ },
+ "txtContent": "[$Client]"
+ },
+```
+
+### Contractor
+
+This section defines how the "Contractor" will display on the card, and uses the value for the specific contract.
+
+```JSON
+ {
+ "elmType": "div",
+ "txtContent": "Contractor",
+ "style": {
+ "color": "#767676",
+ "font-size": "12px",
+ "margin-bottom": "2px"
+ }
+ },
+ {
+ "elmType": "div",
+ "style": {
+ "margin-bottom": "12px",
+ "font-size": "14px"
+ },
+ "txtContent": "[$Contractor]"
+ },
+```
+
+### Fee amount
+
+This section defines how the "Fee Amount" will display on the card, and uses the value for the specific contract.
+
+```JSON
+ {
+ "elmType": "div",
+ "txtContent": "Fee amount",
+ "style": {
+ "color": "#767676",
+ "font-size": "12px",
+ "margin-bottom": "2px"
+ }
+ },
+ {
+ "elmType": "div",
+ "style": {
+ "margin-bottom": "12px",
+ "font-size": "14px"
+ },
+ "txtContent": "[$FeeAmount]"
+ },
+```
+
+### Classification date
+
+This section defines how "Classification" will display on the card, and uses the value for the specific contract.
+
+```JSON
+ {
+ "elmType": "div",
+ "txtContent": "Classified",
+ "style": {
+ "color": "#767676",
+ "font-size": "12px",
+ "margin-bottom": "2px"
+ }
+ },
+ {
+ "elmType": "div",
+ "style": {
+ "margin-bottom": "12px",
+ "font-size": "14px"
+ },
+ "txtContent": "[$PrimeLastClassified]"
+ }
+```
+
+## Next step
+
+[Step 3. Use Power Automate to create the flow to process your contracts](solution-manage-contracts-step3.md)
syntex Solution Manage Contracts Step3 https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/solution-manage-contracts-step3.md
+
+ Title: Step 3. Use Power Automate to create the flow to process your contracts
++++
+audience: admin
+ Last updated : +
+search.appverid:
+ms.localizationpriority: medium
+ROBOTS:
+description: Learn how to use Power Automate to create your flow to process your contracts by using a Microsoft 365 solution.
++
+# Step 3. Use Power Automate to create the flow to process your contracts
+
+You've created your Contract Management channel and have attached your SharePoint document library. The next step is to create a Power Automate flow to process your contracts that your Syntex model identifies and classifies. You can do this step by [creating a Power Automate flow in your SharePoint document library](https://support.microsoft.com/office/create-a-flow-for-a-list-or-library-in-sharepoint-or-onedrive-a9c3e03b-0654-46af-a254-20252e580d01).
+
+For your contracts management solution, you want to create a Power Automate flow to do the following actions:
+
+- After a contract has been classified by your Syntex model, change the contract status to **In review**.
+- The contract is then reviewed and is either approved or rejected.
+- For approved contracts, the contract information is posted to a tab for payment processing.
+- For rejected contracts, the team is notified for further analysis.
+
+The following diagram shows the Power Automate flow for the contract management solution.
+
+![Flow diagram showing the entire solution.](../media/content-understanding/flow-entire-process.png)
+
+## Prepare your contract for review
+
+When a contract is identified and classified by your unstructured document processing model, the Power Automate flow will first change the status to **In review**.
+
+![Update status.](../media/content-understanding/flow-overview.png)
+
+After checking out the file, change the status value to **In review**.
+
+![In review status.](../media/content-understanding/in-review.png)
+
+The next step is to create an adaptive card stating that the contract is waiting for review and posting it to the Contract Management channel.
+
+![Contract review post.](../media/content-understanding/contract-approval-post.png)
++
+![Create adaptive card for review.](../media/content-understanding/adaptive-card.png)
+
+The following code is the JSON used for this step in the Power Automate flow.
+
+```JSON
+{
+"$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
+"type": "AdaptiveCard",
+"version": "1.0",
+"body": [
+ {
+ "type": "TextBlock",
+ "text": "Contract approval request",
+ "size": "large",
+ "weight": "bolder",
+ "wrap": true
+ },
+ {
+ "type": "Container",
+ "items": [
+ {
+ "type": "FactSet",
+ "spacing": "Large",
+ "facts": [
+ {
+ "title": "Client",
+ "value": "@{triggerOutputs()?['body/Client']}"
+ },
+ {
+ "title": "Contractor",
+ "value": "@{triggerOutputs()?['body/Contractor']}"
+ },
+ {
+ "title": "Fee amount",
+ "value": "@{triggerOutputs()?['body/FeeAmount']}"
+ },
+ {
+ "title": "Date created",
+ "value": "@{triggerOutputs()?['body/Modified']} "
+ },
+ {
+ "title": "Link",
+ "value": "[@{triggerOutputs()?['body/{FilenameWithExtension}']}](@{triggerOutputs()?['body/{Link}']})"
+ }
+ ]
+ }
+ ]
+ },
+ {
+ "type": "TextBlock",
+ "text": "Comment:"
+ },
+ {
+ "type": "Input.Text",
+ "placeholder": "Enter comments",
+ "id": "acComments"
+ }
+],
+"actions": [
+ {
+ "type": "Action.Submit",
+ "title": "Approve",
+ "data": {
+ "x": "Approve"
+ }
+ },
+ {
+ "type": "Action.Submit",
+ "title": "Reject",
+ "data": {
+ "x": "Reject"
+ }
+ }
+]
+}
+```
++
+## Conditional context
+
+In your flow, next you need to create a condition in which your contract will be either [approved](#if-the-contract-is-approved) or [rejected](#if-the-contract-is-rejected).
+
+![Conditional.](../media/content-understanding/condition.png)
+
+## If the contract is approved
+
+When a contract has been approved, the following things occur:
+
+- On the **Contracts** tab, the status in the contract card will change to **Approved**.
+
+ ![Card status approved.](../media/content-understanding/approved-contracts-tab.png)
+
+- In your flow, the status is changed to **Approved**.
+
+ ![Flow status approved.](../media/content-understanding/status-approved.png)
+
+- In this solution, the contract data will be added to the **For Payout** tab so that the payouts can be managed. This process can be extended to allow the flow to submit the contracts for payment by a third-party financial application (for example, Dynamics CRM).
+
+ ![Contract moved to Pay Out.](../media/content-understanding/for-payout.png)
+
+- In the flow, you create the following item to move approved contracts to the **For Payout** tab.
+
+ ![Flow item to move to Pay Out.](../media/content-understanding/ready-for-payout.png)
+
+ To get the expressions for the information needed from the Teams card, use the values shown in the following table.
+
+ |Name |Expression |
+ ||--|
+ | Approval state | body('Post_an_Adaptive_Card_to_a_Teams_channel_and_wait_for_a_response')?['submitActionId'] |
+ | Approved by | body('Post_an_Adaptive_Card_to_a_Teams_channel_and_wait_for_a_response')?['responder']['displayName'] |
+ | Approval date | body('Post_an_Adaptive_Card_to_a_Teams_channel_and_wait_for_a_response')?['responseTime'] |
+ | Comment | body('Post_an_Adaptive_Card_to_a_Teams_channel_and_wait_for_a_response')?['data']?['acComments'] |
+
+ The following example shows how to use the formula box in Power Automate to write an expression.
+
+ ![Screenshot in Power Automate showing an expression formula.](../media/content-understanding/expression-formula-power-automate.png)
+
+- An adaptive card stating that the contract has been approved is created and posted to the Contract Management channel.
+
+ ![Contract approval posted.](../media/content-understanding/adaptive-card-approval.png)
+
+ ![Adaptive card approval.](../media/content-understanding/adaptive-card.png)
++
+ The following code is the JSON used for this step in the Power Automate flow.
+
+```JSON
+{
+ "type": "AdaptiveCard",
+ "body": [
+ {
+ "type": "Container",
+ "style": "emphasis",
+ "items": [
+ {
+ "type": "ColumnSet",
+ "columns": [
+ {
+ "type": "Column",
+ "items": [
+ {
+ "type": "TextBlock",
+ "size": "Large",
+ "weight": "Bolder",
+ "text": "CONTRACT APPROVED"
+ }
+ ],
+ "width": "stretch"
+ }
+ ]
+ }
+ ],
+ "bleed": true
+ },
+ {
+ "type": "Container",
+ "items": [
+ {
+ "type": "FactSet",
+ "spacing": "Large",
+ "facts": [
+ {
+ "title": "Client",
+ "value": "@{triggerOutputs()?['body/Client']}"
+ },
+ {
+ "title": "Contractor",
+ "value": "@{triggerOutputs()?['body/Contractor']}"
+ },
+ {
+ "title": "Fee amount",
+ "value": "@{triggerOutputs()?['body/FeeAmount']}"
+ },
+ {
+ "title": "Approval by",
+ "value": "@{body('Post_an_Adaptive_Card_to_a_Teams_channel_and_wait_for_a_response')?['responder']['displayName']}"
+ },
+ {
+ "title": "Approved date",
+ "value": "@{body('Post_an_Adaptive_Card_to_a_Teams_channel_and_wait_for_a_response')?['responseTime']}"
+ },
+ {
+ "title": "Approval comment",
+ "value": "@{body('Post_an_Adaptive_Card_to_a_Teams_channel_and_wait_for_a_response')?['data']?['acComments']}"
+ },
+ {
+ "title": " ",
+ "value": " "
+ },
+ {
+ "title": "Status",
+ "value": "Ready for payout"
+ }
+ ]
+ }
+ ]
+ }
+ ],
+ "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
+ "version": "1.2",
+ "fallbackText": "This card requires Adaptive Cards v1.2 support to be rendered properly."
+}
+```
+
+## If the contract is rejected
+
+When a contract has been rejected, the following things occur:
+
+- On the **Contracts** tab, the status in the contract card will change to **Rejected**.
+
+ ![Card status rejected.](../media/content-understanding/rejected-contracts-tab.png)
+
+- In your flow, you check out the contract file, change the status to **Rejected**, and then check the file back in.
+
+ ![Flow status rejected in contract file.](../media/content-understanding/reject-flow.png)
+
+- In your flow, you create an adaptive card stating that the contract has been rejected.
+
+ ![Flow status shows rejected on adaptive card.](../media/content-understanding/reject-flow-item.png)
+
+The following code is the JSON used for this step in the Power Automate flow.
+
+```JSON
+{
+ "type": "AdaptiveCard",
+ "body": [
+ {
+ "type": "Container",
+ "style": "attention",
+ "items": [
+ {
+ "type": "ColumnSet",
+ "columns": [
+ {
+ "type": "Column",
+ "items": [
+ {
+ "type": "TextBlock",
+ "size": "Large",
+ "weight": "Bolder",
+ "text": "CONTRACT REJECTED"
+ }
+ ],
+ "width": "stretch"
+ }
+ ]
+ }
+ ],
+ "bleed": true
+ },
+ {
+ "type": "Container",
+ "items": [
+ {
+ "type": "FactSet",
+ "spacing": "Large",
+ "facts": [
+ {
+ "title": "Client",
+ "value": "@{triggerOutputs()?['body/Client']}"
+ },
+ {
+ "title": "Contractor",
+ "value": "@{triggerOutputs()?['body/Contractor']}"
+ },
+ {
+ "title": "Fee amount",
+ "value": "@{triggerOutputs()?['body/FeeAmount']}"
+ },
+ {
+ "title": "Rejected by",
+ "value": "@{body('Post_an_Adaptive_Card_to_a_Teams_channel_and_wait_for_a_response')?['responder']['displayName']}"
+ },
+ {
+ "title": "Rejected date",
+ "value": "@{body('Post_an_Adaptive_Card_to_a_Teams_channel_and_wait_for_a_response')?['responseTime']}"
+ },
+ {
+ "title": "Comment",
+ "value": "@{body('Post_an_Adaptive_Card_to_a_Teams_channel_and_wait_for_a_response')?['data']?['acComments']}"
+ },
+ {
+ "title": " ",
+ "value": " "
+ },
+ {
+ "title": "Status",
+ "value": "Needs review"
+ }
+ ]
+ }
+ ]
+ }
+ ],
+ "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
+ "version": "1.2",
+ "fallbackText": "This card requires Adaptive Cards v1.2 support to be rendered properly."
+}
+```
+
+- The card is posted in the Contract Management channel.
+
+ ![Flow adaptive card to reject.](../media/content-understanding/rejected.png)
syntex Syntex Azure Billing https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/syntex-azure-billing.md
+
+ Title: Configure Microsoft Syntex for pay-as-you-go billing in Azure (Preview)
++++
+audience: admin
+++
+ - enabler-strategic
+ - m365initiative-syntex
+search.appverid: MET150
+ms.localizationpriority: medium
+description: Learn about how to set up pay-as-you-go Azure billing for Microsoft Syntex and how to monitor your usage.
++
+# Configure Microsoft Syntex for pay-as-you-go billing in Azure (Preview)
+
+Some Microsoft Syntex features are billed through an Azure subscription. In this limited-time preview, you can use prebuilt and unstructured document processing (formerly document understanding) at no cost and see activity reports in Azure.
+
+After the preview ends, document processing will be charged on a pay-as-you-go basis. You will have the option to opt in at that time. For details about the preview, see [Microsoft Syntex pay-as-you-go preview](/legal/microsoft-365/microsoft-syntex-azure-billing-trial).
+
+This preview does not include structured or freeform document processing which use AI Builder credits.
+
+## Prerequisites
+
+To use Microsoft Syntex pay-as-you go, you need:
+
+- An Azure subscription in the same tenant as Microsoft Syntex
+- An Azure resource group in that subscription
+- An Azure storage account in that subscription if you want to create usage reports. (See [Azure Blob Storage pricing](https://azure.microsoft.com/pricing/details/storage) for pricing.)
+
+If you already have these resources for other purposes, you can also use them with Microsoft Syntex.
+
+For information about how to create an Azure subscription, see [Create your initial Azure subscriptions](/azure/cloud-adoption-framework/ready/azure-best-practices/initial-subscriptions)
+
+For information about how to create an Azure resource group, see [Manage Azure resource groups by using the Azure portal](/azure/azure-resource-manager/management/manage-resource-groups-portal).
+
+For information about how to create an Azure storage account, see [Create a storage account](/azure/storage/common/storage-account-create). The storage account does not need to be public or connected to the internet.
+
+## Set up Microsoft Syntex billing in Azure
+
+When you set up Microsoft Syntex billing in Azure, events will be sent to the Azure meter in your account and you will be able to view the pages processed for unstructured and prebuilt document processing models.
+
+The following permissions are required to set up Microsoft Syntex billing:
+
+- You must have Global Administrator or SharePoint Administrator permissions to be able to access the Microsoft 365 admin center and set up Syntex.
+- You must have owner or contributor rights to the Azure subscription that you want to use for Microsoft Syntex billing.
+
+To configure Microsoft Syntex billing
+
+1. In the Microsoft 365 admin center, select <a href="https://go.microsoft.com/fwlink/p/?linkid=2171997" target="_blank">**Setup**</a>, and then view the **Files and content** section.
+
+1. In the **Files and content** section, select **Use content AI with Microsoft Syntex**.
+
+1. On the **Microsoft Syntex** page, select **Configure billing** to walk through the setup process.
+1. On the **Enter your Azure subscription** panel, choose an Azure subscription from the **Azure subscription** dropdown.
+1. Choose a resource group and region. (The region determines where your tenant ID and usage information such as site names will be stored.)
+1. Select **Save**.
+
+If you need to change or disconnect your Azure subscription, you can select **Manage billing** on the **Use content AI with Microsoft Syntex**.
+
+If you have not previously configured Microsoft Syntex, read [Set up Microsoft Syntex](set-up-content-understanding.md) to learn how.
+
+## Monitor your Microsoft Syntex pay-as-you-go usage
+
+You can monitor your Microsoft Syntex pay-as-you-go usage in Azure Cost Management. (There's no charge for this usage during the preview and the cost analysis dashboard won't show any information.)
+
+To run the report, the customer must have at least *read* access to the resource group and *contributor* access to the storage container.
+
+Pages processed are counted for every time the model runs against the document for all pages processed in the document regardless of whether there was a positive classification. This includes when a document is processed after being updated.
+
+Model training does not count toward pages processed.
+
+To create a report
+1. Sign in to [Azure Cost Management](https://portal.azure.com/#view/Microsoft_Azure_CostManagement/Menu/~/overview).
+1. Under **Settings**, select **Exports**.
+1. Select **Add**.
+1. Type a name for the export.
+1. Select the **Metric** that you want to report on.
+1. Choose an **Export type** and the dates for the export.
+1. In the **Storage** section, choose the subscription that you're using for Microsoft Syntex billing.
+1. In the **Storage account** dropdown, choose a storage account to which you have contributor access.
+1. Type a name for the container where the report will be stored.
+1. Type the path within the container where you want to export the report.
+1. Select **Create**.
+
+Once the report has been created, it will run on the date you specified. You can also run it manually.
+
+To run a report
+1. In the Azure Cost Management Exports list, select the report that you want to run.
+1. Select **Run now**.
+
+The report may take up to an hour to run.
+
+To access the report
+1. In the Azure Cost Management Exports list, select the report.
+1. Select the storage account.
+1. Under **Data storage**, select **Containers**.
+1. Select the container where you stored the report.
+1. Navigate to the csv file for the report that you want to view.
+1. Select the csv, and then select **Download**.
+
+Filter the csv on **consumedService** = *Microsoft.Syntex*. The following columns include Microsoft Syntex transaction information:
+
+- meterName
+- meterCategory
+- meterSubCategory
+- ProductName
+- quantity
+- tags (site and library information)
+
+## Related topics
+
+[Overview of Microsoft Syntex](syntex-overview.md)
+
+[Licensing for Microsoft Syntex](syntex-licensing.md)
+
syntex Syntex Licensing https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/syntex-licensing.md
+
+ Title: Licensing for Microsoft Syntex
++++
+audience: admin
+++
+ - enabler-strategic
+ - m365initiative-syntex
+search.appverid: MET150
+ms.localizationpriority: high
+description: Learn about licensing for Microsoft Syntex.
++
+# Licensing for Microsoft Syntex
+
+To use Microsoft Syntex, you must have a license for each Syntex user. If you remove all Syntex licenses from your tenant at a future date (or your trial expires), users will no longer be able to create, publish, or run custom models. Additionally, term store reports, SKOS taxonomy import, and content type push will no longer be available. No models, content, or metadata will be deleted, and site permissions won't be changed.
+
+> [!NOTE]
+> Syntex is an add-on license and requires users also to have a license for Microsoft 365.
+
+## Tasks requiring a license
+
+The following tasks require a [Syntex license](https://www.microsoft.com/microsoft-365/enterprise/sharepoint-syntex) for the user performing them:
+
+- Apply an unstructured document processing model to a library. (Unlicensed users can be granted access to a content center and can create models there, but can't apply them to a document library.)
+- Create a structured document processing model or a freeform document processing model via the entry point in a library
+- Upload content to a library where a custom model has been applied
+- Run an unstructured document processing model on-demand
+- Create a modern template with content assembly
+- Generate a document from a modern template
+- Use of advanced metadata search
+- Use of premium taxonomy services. (Premium taxonomy services comprise SKOS-based term set import, pushing enterprise content types to hub-associated sites, and term store reports.)
+
+Unlicensed users can be granted access to a content center and can create models there, but can't apply them to a document library.
+
+## Cost of training and running models
+
+The cost of training and running unstructured document processing models is included in the cost of a Syntex license. However, the structured document processing and freeform document processing models use AI Builder capacity, for both training and runtime processing. Capacity must be allocated to the Power Apps environment where you will use AI Builder.
+
+For each Syntex license, you are allocated 3,500 AI Builder credits per license, per month pooled at the tenant level, with a maximum allocation of 1 million credits per month. This allocation is renewed each month for each active Syntex license. (Unused credits don't roll over from month to month.)
+
+You can estimate the AI Builder capacity thatΓÇÖs right for you with the [AI Builder calculator](https://powerapps.microsoft.com/ai-builder-calculator).
+
+If you plan to use a custom Power Platform environment, you must [allocate credits to that environment](/power-platform/admin/capacity-add-on).
+
+Go to the [Power Platform admin center](https://admin.powerplatform.microsoft.com/resources/capacity) to check your credits and usage.
+
+## Additional term store features
+
+Having one or more Syntex licenses in your organization enables the following additional term store features for SharePoint admins:
+
+- SKOS-based term set import
+- Pushing enterprise content types to a hub site, which also adds them to the associated sites and any newly created lists or libraries
+- Term store reports providing insights into published term sets and their use across your tenant
+
+## See also
+
+[Licensing overview for Microsoft Power Platform](/power-platform/admin/pricing-billing-skus)
+
+[Power Apps and Power Automate licensing FAQ](/power-platform/admin/powerapps-flow-licensing-faq)
syntex Syntex Overview https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/syntex-overview.md
+
+ Title: Overview of Microsoft Syntex
++++
+audience: admin
+++
+search.appverid:
+
+ - enabler-strategic
+ - m365initiative-syntex
+ms.localizationpriority: medium
+description: Learn about the capabilities and features in Microsoft Syntex.
++
+# Overview of Microsoft Syntex
+
+Microsoft Syntex is a content understanding, processing, and compliance service that uses intelligent document processing, content artificial intelligence (AI), and advanced machine learning to automatically and thoughtfully find, organize, and classify documents in your SharePoint libraries.
+
+ :::column span="":::
+ With Syntex, you can automate your content-based processesΓÇöcapturing the information in your business documents and transforming that information into working knowledge for your organization.
+
+ Rather than clicking and sorting through hundreds or thousands of files, Syntex extracts, analyzes, and categorizes the data for you.
+ :::column-end:::
+ :::column span="":::
+ ![Image of computers running Syntex.](../media/content-understanding/syntex-devices-image.png)
+ :::column-end:::
+
+You can dive deeper into your content to truly understand it, and you can turn the information into meaningful insights that your organization can use to make informed business decisions.
+
+## Models
+
+ :::column span="":::
+ ![Image of generic model icon.](../media/content-understanding/model-generic-image.png)
+ :::column-end:::
+ :::column span="3":::
+ Understanding your content with Syntex begins with models. Models let you identify and classify documents that are uploaded to your SharePoint document libraries, and then to extract the information you need from each file.
+
+ In Syntex, you can build [custom models](model-types-overview.md) or you can use [prebuilt models](prebuilt-overview.md).
+ :::column-end:::
+
+The type of model you choose will depend on the types of files you use, the format and structure of the files, the information you want to extract, and where you want to apply the model.
+
+### Custom models
+
+You build custom models to understand the layout of your files from example documents. The models learn to look for the data you need to extract from similar documents. Custom models include:
+
+- [Unstructured document processing](document-understanding-overview.md)
+- [Freeform document processing](freeform-document-processing-overview.md)
+- [Structured document processing](form-processing-overview.md)
+
+| Unstructured<br>document processing | Freeform<br>document processing | Structured<br>document processing |
+| - | - | - |
+| ![Icon for unstructured document processing model.](../media/content-understanding/custom-classify-and-extract-by-text-pattern.png) | ![Icon for freeform document processing model.](../media/content-understanding/custom-extract-by-text-pattern-and-layout.png) | ![Icon for structured document processing model.](../media/content-understanding/custom-extract-by-layout.png) |
+| Use this custom model to automatically classify documents and extract information from them. Use the patterns of the text in example documents to train the model. Best for Office files and automatic classification of files. <br>[Learn more](document-understanding-overview.md) | Use this custom model to automatically extract information from unstructured documents. Use the patterns of the text or the layout in example documents to train the model. Best for a mix of both text and layout needs. <br>[Learn more](freeform-document-processing-overview.md) | Use this custom model to automatically identify field and table values from structured or semi-structured documents like forms. Best for most languages and files that include form layouts or tables. <br>[Learn more](form-processing-overview.md) |
+
+### Prebuilt models
+
+If you don't need to build a custom model, you can use a [prebuilt model](prebuilt-overview.md). This type of model is pretrained to extract predefined entities from common business files. Prebuilt models include:
+
+- [Invoice processing](prebuilt-model-invoice.md)
+- [Receipt processing](prebuilt-model-receipt.md)
+
+| Invoice processing | Receipt processing |
+| - | - |
+| ![Icon for Invoices model.](../media/content-understanding/trained-invoices-model.png) | ![Icon for Receipts model.](../media/content-understanding/trained-receipts-model.png) |
+| Use this prebuilt model to save time processing invoices. Automatically extract key information specific to invoices. <br>[Learn more](prebuilt-model-invoice.md) | Use this prebuilt model to save time processing receipts. Automatically extract key information specific to expenses. <br>[Learn more](prebuilt-model-receipt.md) |
+
+For more information about custom and prebuilt models, see [Overview of model types in Microsoft Syntex](model-types-overview.md).
+
+## Content assembly
+
+ :::column span="":::
+ ![Image of generic document icon.](../media/content-understanding/document-assembly-image.png)
+ :::column-end:::
+ :::column span="3":::
+ With Syntex, you can create *modern templates* based on the business documents you use most.
+
+ You can then use those templates to automatically generate new documents using SharePoint lists or user entries as a data source.
+ :::column-end:::
+
+ This process lets you automatically generate standard repetitive business documents, such as contracts, statements of work, service agreements, letters of consent, and correspondence. You can do all these tasks quicker, more consistently, and with fewer errors in Syntex.
+
+For more information, see [Create documents using content assembly in Microsoft Syntex](content-assembly.md).
+
+## Advanced metadata search
+
+ :::column span="3":::
+ The advanced metadata search feature in Syntex lets you perform specific metadata-based queries on SharePoint document libraries.
+
+ You can make faster, more precise queries based on specific metadata column values, rather than just searching for keywords.
+ :::column-end:::
+ :::column span="":::
+ ![Image of generic search icon.](../media/content-understanding/search-generic-image.png)
+ :::column-end:::
+
+This feature is useful when you have a specific piece of information you want to search for, such as when a document was last modified, a specific person associated with a file, or a specific file type.
+
+For more information, see [Search for metadata in document libraries in Microsoft Syntex](metadata-search.md).
+
+## Content compliance
+
+ :::column span="":::
+ ![Image of generic compliance icon.](../media/content-understanding/compliance-image.png)
+ :::column-end:::
+ :::column span="3":::
+ Understanding your content allows for better compliance control and increases management and governance options for all your data. When content is properly tagged and labeled, you have better control over your data and can follow regulations more easily. Syntex helps you ensure compliance by using retention labels and sensitivity labels to manage your documents.
+ :::column-end:::
+
+For more information, see [Apply a retention label to a model in Microsoft Syntex](apply-a-retention-label-to-a-model.md) and [Apply a sensitivity label to a model in Microsoft Syntex](apply-a-sensitivity-label-to-a-model.md).
+
+## Premium taxonomy services
+
+ :::column span="3":::
+ Having one or more Syntex licenses in your organization enables the following additional term store features for admins:<br><br>
+
+ - [SKOS-based term set import](import-term-set-skos.md), which lets you import a term set using a SKOS-based format.
+ :::column-end:::
+ :::column span="":::
+ ![Image of generic taxonomy icon.](../media/content-understanding/taxonomy-image.png)
+ :::column-end:::
++
+- [Pushing enterprise content types to a hub site](push-content-type-to-hub.md), which also adds them to the associated sites and any newly created lists or libraries.
+
+- [Term store reports](term-store-analytics.md), which provides you insights into published term sets and their use across your organization.
+
+## Scenarios and use cases
+
+ :::column span="":::
+ ![Image of generic scenario icon.](../media/content-understanding/scenarios-image.png)
+ :::column-end:::
+ :::column span="3":::
+ Syntex can help your organization automate business processes, improve search accuracy, and manage compliance risk.
+
+ With content AI services and capabilities, you can build content understanding and classification directly into the content management flow.
+ :::column-end:::
+
+To prompt ideas about how you can use Syntex in your organization, see [Scenarios and use cases for Microsoft Syntex](adoption-scenarios.md).
+<br><br>
+> [!div class="nextstepaction"]
+> [Learn more about models in Microsoft Syntex](model-types-overview.md)
syntex Term Store Analytics https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/term-store-analytics.md
+
+ Title: Term store reports
+description: Learn how to report on term store activity.
+++
+audience: admin
++
+search.appverid:
+
+ - enabler-strategic
+ - m365initiative-syntex
+
+ms.localizationpriority: high
++
+# Term store reports
+
+You can access reports for <a href="https://go.microsoft.com/fwlink/?linkid=2185073" target="_blank">Term store</a> in the SharePoint admin center. This feature requires a [Microsoft Syntex license](syntex-licensing.md).
+
+Expand **Reports**, and then click **Content services**.
+
+The following reports are available:
+
+### Term store operations
+
+View the top operations that have taken place in your term store in a 15-day period and see a trend of daily volumes in that period. This is useful when you want to understand the nature of changes in your term store at a high level and identify any unexpected trends in volumes of operations.
+
+### Term store composition
+
+View the distribution of types of terms between regular managed terms and enterprise keywords. Move multiple keywords to managed terms if desired. This is useful when you want to identify if your users are actively using keywords. You can review them to identify potential candidates for managed terms.
+
+### Open and closed term sets
+
+View the distribution of open and closed term sets. This is useful if you want to understand how many term sets allow users to add terms. You can convert them to closed if desired, for example if the volumes are growing unexpectedly.
+
+### Terms without synonyms
+
+View the number of terms in each of the added working languages that don't have synonyms defined. This is useful to help identify languages where you want to define synonyms. Synonyms help end users disambiguate and find the correct terms to tag their content.
+
+## See also
+++
+
++++++
syntex Train Freeform Document Processing Model https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/train-freeform-document-processing-model.md
+
+ Title: Train a freeform document processing model in Microsoft Syntex
++++
+audience: admin
++
+search.appverid:
+
+ - enabler-strategic
+ - m365initiative-syntex
+
+ms.localizationpriority: medium
+description: Learn how to train a freeform document processing model in Microsoft Syntex.
++
+# Train a freeform document processing model in Microsoft Syntex
+
+Follow the instructions in [Create a model in Syntex](create-syntex-model.md) to create a freeform document processing model in a content center. Or, follow the instructions in [Create a model on a local SharePoint site](create-local-model.md) to create the model on a local site. Then use this article to train your model.
+
+![Diagram of the workflow to train an AI Builder model.](../media/content-understanding/train-aib-model.png)
+
+To train a freeform document processing model, follow these steps:
+
+ - [Step 1: Add and analyze documents](#step-1-add-and-analyze-documents)
+ - [Step 2: Tag fields and tables](#step-2-tag-fields-and-tables)
+ - [Step 3: Train and publish your model](#step-3-train-and-publish-your-model)
+ - [Step 4: Use your model](#step-4-use-your-model)
+
+## Step 1: Add and analyze documents
+
+After you create your structured document processing model, the **Choose information to extract** page opens. Here you list all pieces of information that you want the AI model to extract from your documents, such as Name, Address, or Amount.
+
+> [!NOTE]
+> When you look for example files to use, see the [document processing model input document requirements and optimization tips](/ai-builder/form-processing-model-requirements).
+
+1. You first define the fields and tables you want to teach your model to extract on the **Choose information to extract** page. For detailed steps, see [Define fields and tables to extract](/ai-builder/create-form-processing-model#define-fields-and-tables-to-extract).
+
+2. You can create as many collections of document layouts you want your model to process. For detailed steps, see [Group documents by collections](/ai-builder/create-form-processing-model#group-documents-by-collections).
+
+3. After you create your collections and add at least five example files for each, AI Builder on Syntex will examine the uploaded documents to detect the fields and tables. This process usually takes a few seconds. When the analysis is complete, you can proceed with tagging the documents.
+
+## Step 2: Tag fields and tables
+
+You need to tag the documents to teach the model to understand the fields and table data you want to extract. For detailed steps, see [Tag documents](/ai-builder/create-form-processing-model#tag-documents).
+
+## Step 3: Train and publish your model
+
+1. After you create and train your model, you're ready to publish it and use it in SharePoint. To publish the model, select **Publish**. For detailed steps, see [Train and publish your document processing model](/ai-builder/form-processing-train).
+
+ ![Screenshot in showing the model details on the model home page.](../media/content-understanding/ai-builder-create-a-flow-1.png)
+
+2. After the model is published, you will go to the model home page. You'll then have the option to apply the model to a document library.
+
+ ![Screenshot of the model home page to apply the model a library.](../media/content-understanding/ai-builder-apply-model.png)
+
+## Step 4: Use your model
+
+1. In the document library model view, notice that the fields you selected now display as columns.
+
+ ![Screenshot showing document library model applied.](../media/content-understanding/doc-lib-view.png)
+
+2. Notice that the information link next to **Documents** notes that a forms processing model is applied to this document library.
+
+3. Upload files to your document library. Any files that the model identifies as its content type lists the files in your view and displays the extracted data in the columns.
+
+ ![Screenshot showing process is done.](../media/content-understanding/doc-lib-done.png)
+
+> [!NOTE]
+> If a freeform or structured document processing model and an unstructured document processing model are applied to the same library, the file is classified using the unstructured document processing model and any trained extractors for that model. If there are any empty columns that match the freeform or structured document processing model, the columns will be populated using those extracted values.
+
+### Classification Date field
+
+When a Syntex custom model is applied to a document library, the **Classification Date** field is included in the library schema. By default, this field is empty. However, when documents are processed and classified by a model, this field is updated with a date-time stamp of completion.
+
+When a model is stamped with the **Classification Date**, you can use the **Send an email after Syntex processes a file** flow to notify users that a new file has been processed and classified by a model in the SharePoint document library.
+
+To run the flow:
+
+1. Select a file, and then select **Integrate** > **Power Automate** > **Create a flow**.
+
+2. On the **Create a flow** panel, select **Send an email after Syntex processes a file**.
+
+ ![Screenshot showing the Create a flow panel and flow option highlighted.](../media/content-understanding/integrate-create-flow.png)
+
+## See also
+
+[Create a model in Microsoft Syntex](create-syntex-model.md)
+
+[Power Automate documentation](/power-automate/)
+
+[Training: Improve business performance with AI Builder](/learn/paths/improve-business-performance-ai-builder/?source=learn)
syntex Train Model https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/train-model.md
+
+ Title: Train your model in Microsoft Syntex
++++
+audience: admin
+++
+search.appverid:
+
+ - enabler-strategic
+ - m365initiative-syntex
+ms.localizationpriority: medium
+description: Learn how to train custom models in Microsoft Syntex.
++
+# Train your model in Microsoft Syntex
+
+<sup>**Applies to:** &ensp; &#10003; All custom models &ensp; </sup>
+
+The steps to train your model depends on the type of model you are using.
+
+|Model type |Steps to train |
+|||
+|Unstructured document processing |[Train your unstructured document processing model](create-a-classifier.md) |
+|Freeform document processing |[Train your freeform document processing model](train-freeform-document-processing-model.md) |
+|Structured document processing |[Train your structured document processing model](create-a-form-processing-model.md) |
+
+## See also
+
+[Overview of model types in Microsoft Syntex](model-types-overview.md)
syntex Trial Syntex https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/trial-syntex.md
+
+ Title: Run a trial of Microsoft Syntex
++++ Last updated :
+audience: admin
+++
+- enabler-strategic
+- m365initiative-syntex
+
+- Adopt
+- admindeeplinkMAC
+search.appverid:
+ms.localizationpriority: medium
+description: Learn how to plan, sign up, and run a trial pilot program for Microsoft Syntex in your organization.
++
+# Run a trial of Microsoft Syntex
+
+This article describes how to set up and run a trial pilot program to deploy Microsoft Syntex in your organization. It also recommends best practices for the trial.
+
+## Sign up for a trial
+
+The trial of Syntex gives access to 300 users for 30 days.
+
+> [!NOTE]
+> Up to 300 users are included in the trial to ensure the automatic addition of 1 million AI Builder credits. You do not have to include 300 users for a trial to succeed.
+
+You can get the trial version from one of the following sources:
+
+- The [Syntex product page](https://www.microsoft.com/microsoft-365/enterprise/sharepoint-syntex?activetab=pivot:overviewtab)
+
+- The [Microsoft 365 admin center](https://admin.microsoft.com)
+ 1. Sign in to the [Microsoft 365 admin center](https://admin.microsoft.com).
+ 2. Go to **Billing** > <a href="https://go.microsoft.com/fwlink/p/?linkid=868433" target="_blank">**Purchase Services**</a>.
+ 3. Scroll down to the **Add-Ons** section.
+ 4. On the Syntex tile, select **Details**.
+ 5. Select **Start free trial**.
+ 6. To confirm the trial, follow the remaining wizard steps.
+
+You must be a Microsoft 365 global administrator or billing administrator to activate a trial.
+
+### Who should be involved in a trial
+
+|Role|Activity|
+|||
+|Microsoft 365 global admin or billing admin|Activate the trial and assign licenses|
+|Microsoft 365 global admin or SharePoint admin|Configure Syntex and create content centers|
+|Business users|Model building and testing|
+
+### Before you activate a trial
+
+To successfully plan a Syntex trial, consider the following factors:
+
+- The most meaningful testing is completed on ΓÇ£real worldΓÇ¥ scenarios and data.
+- You can only activate a Syntex trial once per tenant.
+
+A test or demo tenant can be used as a ΓÇ£dry runΓÇ¥ to walk through the activation steps and administrative controls. But it's probably best to evaluate model building on a production tenant.
+
+To maximize the value of a trial on a production tenant, planning and business engagement are essential. You should engage one or more business areas to identify three to six use cases that could potentially be addressed by Syntex. These use cases should:
+
+- Include scenarios that could be solved by using either a custom model or a prebuilt model.
+
+- Have a clear understanding of the purpose for any extracted metadata; for example, view formatting or automation by using Power Automate. While Syntex is focused on classifying documents and extracting metadata, the value to quantify is what this metadata enables.
+
+- Be based on a defined set of data; for example, specific SharePoint sites or libraries. A common misconception of Syntex is that general purpose models can be applied across all organization content. A more accurate view is that models are built to help solve specific business problems in targeted locations.
+
+All of these use cases might not be a good fit for Syntex. The goal of a quality trial isn't to prove that Syntex will fit all the scenarios. Instead, the trial should help you better understand the value of the product.
+
+For each of the planned use cases, identify users who are subject matter experts in the related content or process. The creation of Syntex models is focused on domain experts in the content, rather than on IT professionals or developer resources.
+
+## Activate a trial
+
+When you initiate a trial, you need to:
+
+- Assign licenses to the relevant users.
+- Perform [additional setup of Syntex](set-up-content-understanding.md).
+ - You might want to [create more content centers](create-a-content-center.md).
+
+After the trial is activated, you can create models and process files. See [guidance for model creation](create-a-content-center.md).
+
+## During a trial
+
+Trial periods are limited, so it's best to focus initially on whether Syntex models can classify documents and extract metadata for the defined use cases. After the trial period is over, you can evaluate how the metadata can be used.
+
+## After a trial
+
+Based on the outcome of the trial, you can decide whether to proceed to production use of Syntex.
+
+### Proceed to production use
+
+To ensure continuity of service, you need to purchase the required number of [licenses](syntex-licensing.md) and assign those licenses to users. Trial users who don't have a full license at the end of the trial period won't be able to fully use Syntex.
+
+You might have to estimate your projected use of Sstructured document processing or freeform document processing models, and plan for the expected number of AI Builder credits. For help, see [Estimate the AI Builder capacity that's right for you](https://powerapps.microsoft.com/ai-builder-calculator/).
+
+### Don't proceed to production use
+
+If you don't purchase licenses following the trial:
+
+- You won't be able to create new models.
+
+- Libraries that were running models will no longer automatically classify files or extract models.
+
+- Any previously classified files or extracted metadata won't be affected.
+
+- Content centers and any models in them won't be automatically deleted. These will remain available for use if you decide to purchase licenses in the future.
+
+- Structured document processing or freeform document processing models will be stored in the Dataverse (formerly named Common Data Service (CDS)) instance of the default Power Platform environment. These could be used with future licensing for Syntex or with AI Builder capabilities in the Power Platform.
+
+## See also
+
+[Get started driving adoption of Microsoft Syntex](adoption-getstarted.md)
+
+[Scenarios and use cases for Microsoft Syntex](adoption-scenarios.md)
syntex Use Content Center Site https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/use-content-center-site.md
+
+ Title: Use the content center site template for Microsoft Syntex
+++
+audience: admin
+++
+search.appverid:
+
+ - enabler-strategic
+ - m365initiative-syntex
+ms.localizationpriority: medium
+description: Learn how to provision and use the content center site template in Microsoft Syntex.
++
+# Use the content center site template for Microsoft Syntex
+
+The Microsoft Syntex content center site is a ready-to-deploy instructional SharePoint site template designed to help you better understand Syntex capabilities.
+
+You'll be introduced to the tools and information youΓÇÖll need to create and train your own models. You'll then be able to use this site as a central content repository or as the control center for managing your own Syntex models.
+
+![Screenshot of the content center site template home page.](../media/content-understanding/content-center-site-home-page.png)
+
+In this site, models can be trained and evaluated using your own content. However, to apply the models to libraries, a license for Syntex is required.
+
+## Provision the site
+
+The content center site can be provisioned from the [SharePoint look book service](https://lookbook.microsoft.com/).
+
+![Screenshot of the content center site template provisioning page.](../media/content-understanding/content-center-site-provisioning-page.png)
+
+> [!NOTE]
+> You must be a global administrator or SharePoint administrator in Microsoft 365 to provision the site.
+
+1. From the main page of the [SharePoint look book](https://lookbook.microsoft.com/), on the **View the designs** menu, select **Syntex** > **Syntex content center**.
+
+2. On the **Content center** page, select **Add to your tenant**.
+
+ ![Screenshot of the Add to your tenant button on the Content Center site template provisioning page.](../media/content-understanding/content-center-site-add-to-your-tenant.png)
+
+3. Enter your email address (for a notification of when your site is ready to use), the site URL you want to use, and the title you want to use for your site.
+
+ ![Screenshot showing the Content Center site template provisioning page.](../media/content-understanding/content-center-email-and-url.png)
+
+4. Select **Provision**, and in a short time your site will be ready for you to use. YouΓÇÖll get an email (sent to the email address you provided) indicating that your request to provision the content center site template is completed.
+
+5. Select **Open site**, and youΓÇÖll see your content center site. From here, you can explore the site and learn more about Syntex.
+
+For more information about provisioning from the SharePoint look book service, see [Provision a new learning pathways solution](/office365/customlearning/custom_provision).
+
+## Explore the site
+
+The content center site includes prepopulated pages that walk you through the steps to begin using Syntex in your organization.
+
+### Get started with Syntex
+
+Get an introduction to Syntex and learn how you can use it for your organization. Watch a video that gives you an overview of Syntex, and find training to help you get started.
+
+### Learn about model types
+
+Learn about three types of models, and see how you can use them to resolve business issues for search, business processes, compliance, and more.
+
+### Take an interactive tour to create a model
+
+See how to build a model in the models library, and then enable a pretrained sample model.
+
+### Syntex in six simple steps
+
+Begin with a content center, and then learn step-by-step how to create models to identify, classify, and extract the information you need.
+
+### Streamline everyday processes and tasks
+
+Learn how to use Syntex to take what is manual and turn it into something automated and streamlined for your organization.
+
+### Manage compliance
+
+Implement steps to reduce risks and ensure the data and information your organization captures is used in a secure and thoughtful way.
+
+### View model activity
+
+See how content is used to illustrate model activity and to provide more information about how your models are being used.
+
+### Find additional resources
+
+Discover additional resources and scenarios to help you learn more about Syntex.
++
syntex Use Contracts Management Site https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/use-contracts-management-site.md
+
+ Title: Use the contracts management site template for Microsoft Syntex
+++
+audience: admin
+++
+search.appverid:
+
+ - enabler-strategic
+ - m365initiative-syntex
+ms.localizationpriority: medium
+description: Learn how to provision, use, and customize the contracts management site template in Microsoft Syntex.
++
+# Use the contracts management site template for Microsoft Syntex
+
+> [!NOTE]
+> The latest version of the contracts management site template is now available as a [team site template directly from SharePoint](https://support.microsoft.com/office/80820115-c700-4a62-bb59-69b33c8e3b4f). The look book version of this site template is no longer being updated.
+
+The contracts management site is a ready-to-deploy and customizable SharePoint site template that helps your organization maximize the value of Microsoft Syntex. The site is designed to let you create a professional site to manage, process, and track the status of contracts in your organization.
+
+## Features of the site
+
+![Screenshot of the contracts management site template home page.](../media/content-understanding/contracts-management-site-home-page.png)
+
+The contracts management site includes pre-populated pages, web parts, and site navigation. The site can be customized to incorporate your organization's own branding, employee information, policy and planning information, workflow, contacts, and resources.
+
+The site uses the power of a Syntex model running on a SharePoint document library to classify documents and extract metadata. The site provides prebuilt document libraries to get you started quickly, but you can also create your own as needed. The site includes the following featured libraries:
+
+- **Regions** ΓÇô Classify contract documents by geographical area, country, or region.
+
+- **Templates** ΓÇô Select the appropriate contract template for the type of contract, such as non-disclosure agreements, service agreements, and statements of work.
+
+- **Contract requests** ΓÇô Launch a contract request directly to your contracts team.
+
+- **Clients** ΓÇô Find client information in one convenient location.
+
+- **Models** ΓÇô Use the model in this library to classify documents and extract metadata. Users can create their own models to fit their needs and add them to this library.
+
+- **Sample contracts library** ΓÇô Find files that were classified and have had metadata extracted using the Syntex model.
+
+There is a separate view in the library where you can track other metadata such as status, and that uses document library formatting to show it in a more visual way.
+
+## Provision the site
+
+The contracts management site can be provisioned from the [SharePoint look book service](https://lookbook.microsoft.com/).
+
+![Screenshot of the contracts management site template provisioning page.](../media/content-understanding/contracts-management-site-provisioning-page.png)
+
+> [!NOTE]
+> You must be a global administrator or SharePoint administrator in Microsoft 365 to provision the site. You also must have a [Microsoft Syntex license](syntex-licensing.md) to add this site template to your organization.
+
+1. From the main page of the [SharePoint look book](https://lookbook.microsoft.com/), on the **View the designs** menu, select **Syntex** > **Syntex contracts management**.
+
+2. On the **Contracts management** page, select **Add to your tenant**.
+
+ ![Screenshot of the Add to your tenant button on the contracts management site template provisioning page.](../media/content-understanding/contracts-management-site-add-to-your-tenant.png)
+
+3. Enter your email address (for a notification of when your site is ready to use), the site URL you want to use, and the title you want to use for your site.
+
+ ![Screenshot of the email and site URL fields on the contracts management site template provisioning page.](../media/content-understanding/contracts-management-email-and-site-url.png)
+
+4. Select **Provision**, and in a short time your site will be ready for you to use. YouΓÇÖll get an email (sent to the email address you provided) indicating that your request to provision the contracts management site template is completed.
+
+5. Select **Open site**, and youΓÇÖll see your contracts management site. From here, you can explore the site and customize the pages and content.
+
+For more information about provisioning from the SharePoint look book service, see [Provision a new learning pathways solution](/office365/customlearning/custom_provision).
+
+## Customize the site
+
+Before you share the contracts management site with other users, you'll want to customize the site to meet your requirements.
+
+### Customize the look and feel of your site
+
+Customize the following elements of your site to fit the need of your organization:
+
+- Update the [branding](https://support.microsoft.com/office/customize-your-sharepoint-site-320b43e5-b047-4fda-8381-f61e8ac7f59b) on the contracts management site to align with your organization.
+- Customize the [Hero web part](https://support.microsoft.com/office/use-the-hero-web-part-d57f449b-19a0-4b0d-8ce3-be5866430645) to include images of real sites in your organization where possible.
+- Customize the [People web part](https://support.microsoft.com/office/show-people-profiles-on-your-page-with-the-people-web-part-7e52c5f6-2d72-48fa-a9d3-d2750765fa05) to include contact information for the contract managers or others.
+- Customize the [Text web part](https://support.microsoft.com/office/add-text-and-tables-to-your-page-with-the-text-web-part-729c0aa1-bc0d-41e3-9cde-c60533f2c801) to add paragraphs to and formatting options like styles, bullets, indentations, highlighting, and links.
+- Customize the [Image web part](https://support.microsoft.com/office/use-the-image-web-part-a63b335b-ad0a-4954-a65d-33c6af68beb2) to add an image to a page.
+- Customize the [Quick Links web part](https://support.microsoft.com/office/use-the-quick-links-web-part-e1df7561-209d-4362-96d4-469f85ab2a82) to organize and display links to other resources.
+- Add [other web parts](https://support.microsoft.com/office/using-web-parts-on-sharepoint-pages-336e8e92-3e2d-4298-ae01-d404bbe751e0) to your site as needed.
+- Customize the [page layouts](https://support.microsoft.com/office/add-sections-and-columns-on-a-sharepoint-modern-page-fc491eb4-f733-4825-8fe2-e1ed80bd0899) as needed.
+- Add [new pages](https://support.microsoft.com/office/create-and-use-modern-pages-on-a-sharepoint-site-b3d46deb-27a6-4b1e-87b8-df851e503dec) to add additional support or informational resources.
+
+### Customize the site navigation
+
+You have control of the site navigation for the contracts management site. Use the following resources to help you make changes that align with your organization:
+
+- Customize the [site navigation](https://support.microsoft.com/office/customize-the-navigation-on-your-sharepoint-site-3cd61ae7-a9ed-4e1e-bf6d-4655f0bf25ca).
+- [Associate this site with a hub](https://support.microsoft.com/office/associate-a-sharepoint-site-with-a-hub-site-ae0009fd-af04-4d3d-917d-88edb43efc05).
+- Use [audience targeting](https://support.microsoft.com/office/target-navigation-news-and-files-to-specific-audiences-33d84cb6-14ed-4e53-a426-74c38ea32293) to target specific navigational links to specific users.
+- [Delete unwanted pages](https://support.microsoft.com/office/delete-a-page-from-a-sharepoint-site-1d4197b8-31b6-460d-906b-3fb492a51db1) if you need to.
++
+### Add other workflows
+
+The contracts management site contains the components you need to get started, but you can also include additional components, such as:
+
+- Use a [Power Automate flow](/power-automate/getting-started) to trigger a workflow when a new contract is added to the **Contract requests** library.
+- Build additional [Syntex models](/microsoft-365/contentunderstanding/#models).
+- Use the [content assembly](content-assembly.md) feature on the **Templates** library.
+- Create a [contracts management solution](solution-manage-contracts-in-microsoft-365.md) by using Syntex together with other components of Microsoft 365.
+
+## Share the site with others
+
+[Share your site with others](https://support.microsoft.com/office/share-a-site-958771a8-d041-4eb8-b51c-afea2eae3658). Partner with others in your organization to ensure the contracts management site is widely known and adopted.
+
+Key success factors to managing the contracts management site:
+
+- Celebrate the launch of your contracts management site.
+- Create and post news announcing the new resource.
+- Ensure users have an outlet for questions and feedback.
+- Use insights from [site analytics](https://support.microsoft.com/office/view-usage-data-for-your-sharepoint-site-2fa8ddc2-c4b3-4268-8d26-a772dc55779e) to promote content on the home page, update navigation, or rewrite content for clarity.
+- Review the contracts management site as needed to ensure content is fresh and still relevant.
+