| Category | Microsoft Docs article | Related commit history on GitHub | Change details |
|---|---|---|---|
| admin | Share Calendars With External Users | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/admin/manage/share-calendars-with-external-users.md | It's sometimes necessary for your users to schedule meetings with people outside You can enable calendar sharing for all users in your organization in the Microsoft 365 admin center. Once sharing is enabled, your users can use Outlook Web App to share their calendars with anyone inside or outside the organization. People inside the organization can view the shared calendar along with their own calendar. People outside the organization will be sent a URL that they can use to view the calendar. Users in your organization decide when to share and how much to share. +It's sometimes necessary for your users to schedule meetings with people outside your organization. To simplify the process of finding mutually agreeable meeting times, Microsoft 365 enables you to make calendars available to external users. These are people who need to see free and busy times for users in your organization, but don't have user accounts for your Microsoft 365 organization. + +As the admin, you can enable calendar sharing for all users in your organization. Once sharing is enabled, users can use Outlook Web App to share their calendars with anyone inside or outside the organization. People inside the organization can view the shared calendar along with their own calendar. People outside the organization will be sent a URL that they can use to view the calendar. Users decide when to share, how much to share, and when to keep their calendars private. + > [!NOTE]-> If you want to share calendars with an organization that uses Exchange Server 2013 (an on-premises solution), the Exchange administrator will need to set up an authentication relationship with the cloud. This is known as federation, and must meet minimum software requirements. See [Sharing](/exchange/sharing-exchange-2013-help) for more information. +> If you want to share calendars with an organization that uses Exchange Server 2013 (an on-premises solution), the Exchange administrator will need to set up an authentication relationship with the cloud. This is known as "federation" and must meet minimum software requirements. See [Sharing](https://technet.microsoft.com/library/dd638083%28v=exchg.150%29.aspx) for more information. ## Enable calendar sharing using the Microsoft 365 admin center -1. Sign in as a **Global Administator** to the admin center, go to **Settings** \> **Org settings**, and on the <a href="https://go.microsoft.com/fwlink/p/?linkid=2053743" target="_blank">**Services** tab</a>, select **Calendar**. +1. In the admin center, go to **Settings** \> **Org Settings**. ++2. On the **Services** tab, select **Calendar**. -3. On the **Calendar** page, choose whether you want to let users share their calendars with people outside of your organization who have Microsoft 365 or Exchange. Choose whether you want to allow anonymous users (users without credentials) to access calendars via an email invitation. +3. On the **Calendar** page, choose whether you want to let users share their calendars with people outside of your organization who have Microsoft 365 or Exchange. Choose whether you want to allow anonymous users (users without logon credentials) to access calendars via an email invitation. 4. Choose what type of calendar information to make available to users. You can allow all information, or limit it to time only or time, subject, and location only. -## External sharing sync interval --Instant syncing for sharing outside your tenant isn't supported currently. While you can share in these configurations, syncing will happen periodically. There are two types of cross-tenant sharing: --1. **Microsoft 365 to another Microsoft 365 user (if external sharing is enabled)**: A fully shared calendar is created, but the sync will happen approximately every three hours. Instant syncing will eventually be enabled for this setup. --2. **Microsoft 365 to an Outlook.com user**: If external sharing is disabled, sharing to another Microsoft 365 user also falls into this group. An ICS URL is generated when sharing, which the recipient can use to add to any calendar service. With an ICS subscription, the recipientΓÇÖs calendar service chooses when to sync the ICS subscription to receive new updates. If the recipient is an Outlook.com or a Microsoft 365 user, the sync will happen approximately every three hours. - ## Invite people to access calendars -Once sharing is enabled, calendar owners can extend invitations to specific users. --1. Open [Outlook on the Web](https://outlook.office365.com). --2. At the top of the page, select the app launcher and select **Calendar**. By default, your primary calendar is called "Calendar". If you created other calendars, you can select one of them to share instead. You cannot share calendars owned by other people. --3. Enter the name or email address of the person with whom you want to share your calendar in the **Send a sharing invitation in email** box. --4. Choose how much information you want this person to see: -- - **Can view when I'm busy** lets the person see when you are busy but does not include details such as the event location. -- - **Can view titles and locations** lets the person see when you are busy as well as the title and location of events. -- - **Can view all details** lets the person see all the details of your events. -- - **Can edit** lets the person see all details of your events and edit your calendar (only available when sharing with people in your organization). --5. Select **Share**. --## Related content --[Turn external sharing on or off for a site](/sharepoint/change-external-sharing-site) (article)\ -[Overview of the Microsoft 365 admin center](../admin-overview/admin-center-overview.md) (video)\ -[Manage email and calendars](/admin) (link page) -+Once sharing is enabled, calendar owners can extend invitations to specific users. See [Sharing your calendar in Outlook Web App](https://support.microsoft.com/office/7ecef8ae-139c-40d9-bae2-a23977ee58d5) for instructions. |
| admin | Enable Modern Authentication | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/admin/security-and-compliance/enable-modern-authentication.md | To enable MFA for Office 2013 client apps, you must have the following software To determine whether your Office installation is Click-to-run or MSI-based: -1. Start Outlook 2013. -2. From the **File** menu, select **Office Account**. -3. For Outlook 2013 Click-to-Run installations, an **Update Options** item displays. For MSI-based installations, an **Update Options** item does not display. +1. Start Outlook 2013. +2. From the **File** menu, select **Office Account**. +3. For Outlook 2013 Click-to-Run installations, an **Update Options** item displays. For MSI-based installations, an **Update Options** item does not display. :::image type="content" source="../../security/defender-endpoint/images/office-2013-run-installation.png" alt-text="Screenshot of office 2013"::: For Click-to-run installations, you must have the following files installed. If |||| |MSO.DLL|C:\Program Files\Microsoft Office 15\root\vfs\ProgramFilesCommonx86\Microsoft Shared\OFFICE15\MSO.DLL|15.0.4753.1001| |CSI.DLLL|CSI.DLL C:\Program Files\Microsoft Office 15\root\office15\csi.dll|15.0.4753.1000|-|Groove.EXE|C:\Program Files\Microsoft Office 15\root\office15\GROOVE.exe|15.0.4763.1000| +|Groove.EXE*|C:\Program Files\Microsoft Office 15\root\office15\GROOVE.exe|15.0.4763.1000| |Outlook.exe|C:\Program Files\Microsoft Office 15\root\office15\OUTLOOK.exe|15.0.4753.1002| |ADAL.DLL|C:\Program Files\Microsoft Office 15\root\vfs\ProgramFilesCommonx86\Microsoft Shared\OFFICE15\ADAL.DLL|1.0.2016.624| |Iexplore.exe|C:\Program Files\Internet Explorer|Varies| +\* If Groove.EXE isn't part of your Office installation, it doesn't need to be installed for the Azure Active Directory Authentication Library (ADAL) to work. However, if Groove.EXE is present, then the file version listed in the table is required. + ### MSI-based installations For MSI-based installations, you must have the following files installed. If your file version is not equal to or greater than the file version listed, use the link in the Where to get the update column to update it. For MSI-based installations, you must have the following files installed. If you ||||| |MSO.DLL|C:\Program Files\Microsoft Office 15\root\vfs\ProgramFilesCommonx86\Microsoft Shared\OFFICE15\MSO.DLL|[KB3085480](https://support.microsoft.com/en-us/topic/description-of-the-security-update-for-office-2013-september-10-2019-0d171ba2-2eba-a2ca-a54d-c0f568de6bcc)|15.0.4753.1001| |CSI.DLLL|CSI.DLL C:\Program Files\Microsoft Office 15\root\office15\csi.dll|[KB3172545](https://support.microsoft.com/en-us/topic/july-11-2017-update-for-office-2013-kb3172545-d6b47054-04d5-5154-40ba-3436d1e0efdb)|15.0.4753.1000|-|Groove.EXE|C:\Program Files\Microsoft Office 15\root\office15\GROOVE.exe|[KB4022226](https://support.microsoft.com/en-us/topic/august-7-2018-update-for-onedrive-for-business-for-office-2013-kb4022226-6163bb26-cbde-eb16-ac42-abfda7afbf68)|15.0.4763.1000| +|Groove.EXE*|C:\Program Files\Microsoft Office 15\root\office15\GROOVE.exe|[KB4022226](https://support.microsoft.com/en-us/topic/august-7-2018-update-for-onedrive-for-business-for-office-2013-kb4022226-6163bb26-cbde-eb16-ac42-abfda7afbf68)|15.0.4763.1000| |Outlook.exe|C:\Program Files\Microsoft Office 15\root\office15\OUTLOOK.exe|[KB4484096](https://support.microsoft.com/en-us/topic/october-1-2019-update-for-outlook-2013-kb4484096-6513145a-cc75-1cd1-72b7-78cb62d8476b)|15.0.4753.1002| |ADAL.DLL|C:\Program Files\Microsoft Office 15\root\vfs\ProgramFilesCommonx86\Microsoft Shared\OFFICE15\ADAL.DLL|[KB3085565](https://support.microsoft.com/en-us/topic/july-5-2016-update-for-office-2013-kb3085565-1d1a6d24-fbd4-1bae-242f-a35e0e2aba40)|1.0.2016.624| |Iexplore.exe|C:\Program Files\Internet Explorer|[MS14-052](https://support.microsoft.com/en-us/topic/ms14-052-cumulative-security-update-for-internet-explorer-september-9-2014-17d29b71-9e78-0bc1-8961-7b812d04e4e1)|Not applicable| +\* If Groove.EXE isn't part of your Office installation, it doesn't need to be installed for the Azure Active Directory Authentication Library (ADAL) to work. However, if Groove.EXE is present, then the file version listed in the table is required. + ## Enable modern authentication for Office 2013 clients 1. Close Outlook. |
| commerce | Manage Billing Notifications | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/commerce/billing-and-payments/manage-billing-notifications.md | Your organization's billing notifications are sent to the primary and alternate To change the primary and alternate email address of other admins in your organization, use the following steps. > [!NOTE]-> Billing admins can change their own primary and alternate email addresses, but not for other admins. +> Billing admins can only change their own alternate email address. They can't change email addresses for other admins. 1. In the admin center, go to the **Billing** > <a href="https://go.microsoft.com/fwlink/p/?linkid=853212" target="_blank">Billing notifications</a> page. 2. In the **Admins receiving billing notifications** section, select a name. |
| compliance | Alert Policies | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/alert-policies.md | The tables also indicate the Office 365 Enterprise and Office 365 US Government ### Information governance alert policies +> [!NOTE] +> The alert policies in this section are in the process of being deprecated based on customer feedback as false positives. To retain the functionality of these alert policies, you can create custom alert policies with the same settings. + |Name|Description|Severity|Automated investigation|Enterprise subscription| |||||| |**Unusual external user file activity**|Generates an alert when an unusually large number of activities are performed on files in SharePoint or OneDrive by users outside of your organization. This includes activities such as accessing files, downloading files, and deleting files.|High|No|E5/G5, Microsoft Defender for Office 365 P2, or Microsoft 365 E5 add-on subscription| The tables also indicate the Office 365 Enterprise and Office 365 US Government ### Threat management alert policies -> [!NOTE] -> We've temporarily removed the **Phish delivered due to tenant or user override** and **User impersonation phish delivered to inbox/folder** default alert policies based on customer feedback. We're working to improve them, and we'll eventually replace them with new versions. Until then, you can create custom alert policies to replace their functionality by using the following conditions: -> -> - **Activity is**: Phishing email detected at time of delivery -> - **Mail is not ZAP'd** -> - **Mail direction is**: Inbound -> - **Mail delivery status is**: Delivered -> - **Detection technology is**: -> - To replicate **Phish delivered due to tenant or user override**: Malicious URL retention, URL detonation, Advanced phish filter, General phish filter, Domain impersonation, User impersonation, and Brand impersonation. -> - To replicate **User impersonation phish delivered to inbox/folder**: User impersonation -> -> For more information about anti-phishing in Office 365, see [Set up anti-phishing and anti-phishing policies](../security/office-365-security/set-up-anti-phishing-policies.md). - |Name|Description|Severity|Automated investigation|Enterprise subscription| |||||| |**A potentially malicious URL click was detected**|Generates an alert when a user protected by [Safe Links](/microsoft-365/security/office-365-security/safe-links) in your organization clicks a malicious link. This alert is generated when a user clicks on a link and this event triggers a URL verdict change identification by Microsoft Defender for Office 365. This alert automatically triggers [automated investigation and response in Office 365](/microsoft-365/security/office-365-security/office-365-air). For more information on events that trigger this alert, see [Set up Safe Links policies](/microsoft-365/security/office-365-security/set-up-safe-links-policies).|High|Yes|E5/G5 or Defender for Office 365 P2 add-on subscription| The tables also indicate the Office 365 Enterprise and Office 365 US Government |**Email sending limit exceeded**|Generates an alert when someone in your organization has sent more mail than is allowed by the outbound spam policy. This is usually an indication the user is sending too much email or that the account may be compromised. If you get an alert generated by this alert policy, it's a good idea to [check whether the user account is compromised](../security/office-365-security/responding-to-a-compromised-email-account.md).|Medium|No|E1/F1/G1, E3/F3/G3, or E5/G5| |**Form blocked due to potential phishing attempt**|Generates an alert when someone in your organization has been restricted from sharing forms and collecting responses using Microsoft Forms due to detected repeated phishing attempt behavior.|High|No|E1, E3/F3, or E5| |**Form flagged and confirmed as phishing**|Generates an alert when a form created in Microsoft Forms from within your organization has been identified as potential phishing through Report Abuse and confirmed as phishing by Microsoft.|High|No|E1, E3/F3, or E5|-|**Malware campaign detected after delivery**|Generates an alert when an unusually large number of messages containing malware are delivered to mailboxes in your organization. If this event occurs, Microsoft removes the infected messages from Exchange Online mailboxes.|High|No|E5/G5 or Microsoft Defender for Office 365 P2 add-on subscription| -|**Malware campaign detected and blocked**|Generates an alert when someone has attempted to send an unusually large number of email messages containing a certain type of malware to users in your organization. If this event occurs, the infected messages are blocked by Microsoft and not delivered to mailboxes.|Low|No|E5/G5 or Defender for Office 365 P2 add-on subscription| -|**Malware campaign detected in SharePoint and OneDrive**|Generates an alert when an unusually high volume of malware or viruses is detected in files located in SharePoint sites or OneDrive accounts in your organization.|High|No|E5/G5 or Defender for Office 365 P2 add-on subscription| +|**Malware campaign detected after delivery**<sup>\*</sup>|Generates an alert when an unusually large number of messages containing malware are delivered to mailboxes in your organization. If this event occurs, Microsoft removes the infected messages from Exchange Online mailboxes.|High|No|E5/G5 or Microsoft Defender for Office 365 P2 add-on subscription| +|**Malware campaign detected and blocked**<sup>\*</sup>|Generates an alert when someone has attempted to send an unusually large number of email messages containing a certain type of malware to users in your organization. If this event occurs, the infected messages are blocked by Microsoft and not delivered to mailboxes.|Low|No|E5/G5 or Defender for Office 365 P2 add-on subscription| +|**Malware campaign detected in SharePoint and OneDrive**<sup>\*</sup>|Generates an alert when an unusually high volume of malware or viruses is detected in files located in SharePoint sites or OneDrive accounts in your organization.|High|No|E5/G5 or Defender for Office 365 P2 add-on subscription| |**Malware not zapped because ZAP is disabled**| Generates an alert when Microsoft detects delivery of a malware message to a mailbox because Zero-Hour Auto Purge for Phish messages is disabled.|Informational|No|E5/G5 or Defender for Office 365 P2 add-on subscription| |**Messages containing malicious entity not removed after delivery**|Generates an alert when any message containing malicious content (file, URL, campaign, no entity), is delivered to mailboxes in your organization. If this event occurs, Microsoft attempted to remove the infected messages from Exchange Online mailboxes using [Zero-hour auto purge](../security/office-365-security/zero-hour-auto-purge.md), but the message was not removed due to a failure. Additional investigation is recommended. This policy automatically triggers [automated investigation and response in Office 365](../security/office-365-security/office-365-air.md).|Medium|Yes|E5/G5 or Defender for Office 365 P2 add-on subscription| |**Phish delivered because a user's Junk Mail folder is disabled**|**Note**: This alert policy is in the process of being deprecated. Mailbox settings no longer determine whether detected messages can be moved to the Junk Email folder. For more information, see [Configure junk email settings on Exchange Online mailboxes](/microsoft-365/security/office-365-security/configure-junk-email-settings-on-exo-mailboxes).|Informational|No|E1/F1/G1, E3/F3/G3, or E5/G5|-|**Phish delivered due to an ETR override**|Generates an alert when Microsoft detects an Exchange transport rule (also known as a mail flow rule) that allowed delivery of a high confidence phishing message to a mailbox. For more information about Exchange Transport Rules (Mail flow rules), see [Mail flow rules (transport rules) in Exchange Online](/exchange/security-and-compliance/mail-flow-rules/mail-flow-rules).|Informational|No|E1/F1/G1, E3/F3/G3, or E5/G5| -|**Phish delivered due to an IP allow policy**|Generates an alert when Microsoft detects an IP allow policy that allowed delivery of a high confidence phishing message to a mailbox. For more information about the IP allow policy (connection filtering), see [Configure the default connection filter policy - Office 365](../security/office-365-security/configure-the-connection-filter-policy.md).|Informational|No|E1/F1/G1, E3/F3/G3, or E5/G5| -|**Phish not zapped because ZAP is disabled**|Generates an alert when Microsoft detects delivery of a high confidence phishing message to a mailbox because Zero-Hour Auto Purge for Phish messages is disabled.|Informational|No|E5/G5 or Defender for Office 365 P2 add-on subscription| +|**Phish delivered due to an ETR override**<sup>\*\*</sup>|Generates an alert when Microsoft detects an Exchange transport rule (also known as a mail flow rule) that allowed delivery of a high confidence phishing message to a mailbox. For more information about Exchange Transport Rules (Mail flow rules), see [Mail flow rules (transport rules) in Exchange Online](/exchange/security-and-compliance/mail-flow-rules/mail-flow-rules).|Informational|No|E1/F1/G1, E3/F3/G3, or E5/G5| +|**Phish delivered due to an IP allow policy**<sup>\*\*</sup>|Generates an alert when Microsoft detects an IP allow policy that allowed delivery of a high confidence phishing message to a mailbox. For more information about the IP allow policy (connection filtering), see [Configure the default connection filter policy - Office 365](../security/office-365-security/configure-the-connection-filter-policy.md).|Informational|No|E1/F1/G1, E3/F3/G3, or E5/G5| +|**Phish not zapped because ZAP is disabled**<sup>\*\*</sup>|Generates an alert when Microsoft detects delivery of a high confidence phishing message to a mailbox because Zero-Hour Auto Purge for Phish messages is disabled.|Informational|No|E5/G5 or Defender for Office 365 P2 add-on subscription| |**Potential nation-state activity**|Microsoft Threat Intelligence Center detected an attempt to compromise accounts from your tenant.|High|No|E5/G5 or Defender for Office 365 P2 add-on subscription| |**Remediation action taken by admin on emails or URL or sender**|**Note**: This alert policy has been replaced by the **Administrative action submitted by an Administrator** alert policy. This alert policy will eventually go away, so we recommend disabling this alert policy and using **Administrative action submitted by an Administrator** instead. <br/><br/> This alert is triggered when an admin takes remediation action on the selected entity|Informational|Yes|E5/G5 or Defender for Office 365 P2 add-on subscription| |**Suspicious connector activity**|Generates an alert when a suspicious activity is detected on an inbound connector in your organization. Mail is blocked from using the inbound connector. The admin will receive an email notification and an alert. This alert provides guidance on how to investigate, revert changes, and unblock a restricted connector. To learn how to respond to this alert, see [Respond to a compromised connector](/microsoft-365/security/office-365-security/respond-compromised-connector).|High|No|E1/F1/G1, E3/F3/G3, or E5/G5| The tables also indicate the Office 365 Enterprise and Office 365 US Government |**Tenant Allow/Block List entry is about to expire**|Generates an alert when a Tenant Allow/Block List entry is about to be removed. This event is triggered three days prior to expiration date, which is based when the entry was created or last updated. <br/><br/> For blocks, you can extend the expiration date to keep the block in place. For allows, you need to resubmit the item so that our analysts can take another look. However, if the allow has already been graded as a false positive, then the entry will only expire when the system filters have been updated to naturally allow the entry. For more information on events that trigger this alert, see [Manage the Tenant Allow/Block list](../security/office-365-security/tenant-allow-block-list.md).|Informational|No|E5/G5 or Defender for Office 365 P2 add-on subscription| |**Tenant restricted from sending email**|Generates an alert when most of the email traffic from your organization has been detected as suspicious and Microsoft has restricted your organization from sending email. Investigate any potentially compromised user and admin accounts, new connectors, or open relays, and then contact Microsoft Support to unblock your organization. For more information about why organizations are blocked, see [Fix email delivery issues for error code 5.7.7xx in Exchange Online](/Exchange/mail-flow-best-practices/non-delivery-reports-in-exchange-online/fix-error-code-5-7-700-through-5-7-750).|High|No|E1/F1/G1, E3/F3/G3, or E5/G5| |**Tenant restricted from sending unprovisioned email**|Generates an alert when too much email is being sent from unregistered domains (also known as _unprovisioned_ domains). Office 365 allows a reasonable amount of email from unregistered domains, but you should configure every domain that you use to send email as an accepted domain. This alert indicates that all users in the organization can no longer send email. For more information about why organizations are blocked, see [Fix email delivery issues for error code 5.7.7xx in Exchange Online](/Exchange/mail-flow-best-practices/non-delivery-reports-in-exchange-online/fix-error-code-5-7-700-through-5-7-750).|High|No|E1/F1/G1, E3/F3/G3, or E5/G5|-|**Unusual increase in email reported as phish**|Generates an alert when there's a significant increase in the number of people in your organization using the Report Message add-in in Outlook to report messages as phishing mail. For more information about this add-in, see [Use the Report Message add-in](https://support.office.com/article/b5caa9f1-cdf3-4443-af8c-ff724ea719d2).|Medium|No|E5/G5 or Defender for Office 365 P2 add-on subscription| +|**Unusual increase in email reported as phish**<sup>\*</sup>|Generates an alert when there's a significant increase in the number of people in your organization using the Report Message add-in in Outlook to report messages as phishing mail. For more information about this add-in, see [Use the Report Message add-in](https://support.office.com/article/b5caa9f1-cdf3-4443-af8c-ff724ea719d2).|Medium|No|E5/G5 or Defender for Office 365 P2 add-on subscription| |**User requested to release a quarantined message**|Generates an alert when a user requests release for a quarantined message. To request the release of quarantined messages, the **Allow recipients to request a message to be released from quarantine** (_PermissionToRequestRelease_) permission is required in the quarantine policy (for example, from the **Limited access** preset permissions group). For more information, see [Allow recipients to request a message to be released from quarantine permission](../security/office-365-security/quarantine-policies.md#allow-recipients-to-request-a-message-to-be-released-from-quarantine-permission).|Informational|No|Microsoft Business Basic, Microsoft Business Standard, Microsoft Business Premium, E1/F1/G1, E3/F3/G3, or E5/G5| |**User restricted from sending email**|Generates an alert when someone in your organization is restricted from sending outbound mail. This typically results when an account is compromised, and the user is listed on the **Restricted Users** page in the compliance portal. (To access this page, go to **Threat management \> Review \> Restricted Users**). For more information about restricted users, see [Removing a user, domain, or IP address from a block list after sending spam email](/office365/securitycompliance/removing-user-from-restricted-users-portal-after-spam).|High|Yes|Microsoft Business Basic, Microsoft Business Standard, Microsoft Business Premium, E1/F1/G1, E3/F3/G3, or E5/G5| |**User restricted from sharing forms and collecting responses**|Generates an alert when someone in your organization has been restricted from sharing forms and collecting responses using Microsoft Forms due to detected repeated phishing attempt behavior.|High|No|E1, E3/F3, or E5| +<sup>\*</sup> This alert policy is in the process of being deprecated based on customer feedback as a false positive. To retain the functionality of this alert policy, you can create a custom alert policy with the same settings. ++<sup>\*\*</sup> This alert policy is part of the replacement functionality for the **Phish delivered due to tenant or user override** and **User impersonation phish delivered to inbox/folder** alert policies that were removed based on user feedback. For more information about anti-phishing in Office 365, see [Set up anti-phishing and anti-phishing policies](../security/office-365-security/set-up-anti-phishing-policies.md). + ## View alerts When an activity performed by users in your organization matches the settings of an alert policy, an alert is generated and displayed on the **Alerts** page in the Microsoft Purview portal or the Defender portal. Depending on the settings of an alert policy, an email notification is also sent to a list of specified users when an alert is triggered. For each alert, the dashboard on the **Alerts** page displays the name of the corresponding alert policy, the severity and category for the alert (defined in the alert policy), and the number of times an activity has occurred that resulted in the alert being generated. This value is based on the threshold setting of the alert policy. The dashboard also shows the status for each alert. For more information about using the status property to manage alerts, see [Managing alerts](#manage-alerts). |
| compliance | Assign Ediscovery Permissions | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/assign-ediscovery-permissions.md | -If you want people to use any of the [eDiscovery-related tools](ediscovery.md) in the Microsoft Purview compliance portal, you have to assign them the appropriate permissions. The easiest way to do this is to add the person the appropriate role group on the **Permissions** page in the compliance portal. This topic describes the permissions required to perform eDiscovery tasks. +If you want people to use any of the [eDiscovery-related tools](ediscovery.md) in the Microsoft Purview compliance portal, you have to assign them the appropriate permissions. The easiest way to assign roles is to add the person the appropriate role group on the **Permissions** page in the compliance portal. This article describes the permissions required to perform eDiscovery tasks. > [!TIP] > You can view your own permissions on the eDiscovery (Premium) overview page in the compliance portal. You must have at least one role assigned for your permissions to be displayed. -The primary eDiscovery-related role group in compliance portal is called **eDiscovery Manager**. There are two subgroups within this role group. +The primary eDiscovery-related role group in compliance portal is called **eDiscovery Manager**. There are two subgroups within this role group: - **eDiscovery Manager** - An eDiscovery Manager can use eDiscovery search tools to search content locations in the organization, and perform various search-related actions such as preview and export search results. Members can also create and manage cases in Microsoft Purview eDiscovery (Standard) and Microsoft Purview eDiscovery (Premium), add and remove members to a case, create case holds, run searches associated with a case, and access case data. eDiscovery Managers can only access and manage the cases they create. They can't access or manage cases created by other eDiscovery Managers. - **eDiscovery Administrator** - An eDiscovery Administrator is a member of the eDiscovery Manager role group, and can perform the same content search and case management-related tasks that an eDiscovery Manager can perform. Additionally, an eDiscovery Administrator can: - Access all cases that are listed on the **eDiscovery (Standard)** and **eDiscovery (Premium)** pages in the compliance portal.- - Access case data in eDiscovery (Premium) for any case in the organization.- - Manage any eDiscovery case after they add themselves as a member of the case.- - Remove members from an eDiscovery case. Only an eDiscovery Administrator can remove members from a case. Users who are members of the eDiscovery Manager subgroup can't remove members from a case, even if the user created the case. For reasons why you might want eDiscovery Administrators in your organization, see [More information](#more-information). The primary eDiscovery-related role group in compliance portal is called **eDisc ## Before you assign permissions -- You have to be a member of the Organization Management role group or be assigned the Role Management role to assign eDiscovery permissions in the compliance portal.+- You have to be a member of the *Organization Management* role group or be assigned the *Role Management* role to assign eDiscovery permissions in the compliance portal. -- You can use the [Add-RoleGroupMember](/powershell/module/exchange/Add-RoleGroupMember) cmdlet in Security & Compliance PowerShell to add a mail-enabled security group as a member of the eDiscovery Managers subgroup in the eDiscovery Manager role group. However, you can't add a mail-enabled security group to the eDiscovery Administrators subgroup. For details, see [More information](#more-information).+- You can use the [Add-RoleGroupMember](/powershell/module/exchange/Add-RoleGroupMember) cmdlet in Security & Compliance PowerShell to add a mail-enabled security group as a member of the *eDiscovery Managers* subgroup in the *eDiscovery Manager* role group. However, you can't add a mail-enabled security group to the *eDiscovery Administrators* subgroup. For details, see [More information](#more-information). ## Assign eDiscovery permissions 1. Go to the <a href="https://go.microsoft.com/fwlink/p/?linkid=2077149" target="_blank">compliance portal</a> and sign in using an account that can assign permissions.- 2. In the left pane, select **Permissions**.--3. On the **Permissions & Roles** page, under **Microsoft Purview solutions**, click **Roles**. +3. On the **Permissions & Roles** page, under **Microsoft Purview solutions**, select **Roles**. To go directly to this page, use <https://compliance.microsoft.com/compliancecenterpermissions>. 4. On the **Role groups for Microsoft Purview solutions** page, select **eDiscovery Manager**.- -5. On the **eDiscovery Manager** flyout page, do one of the following based on the eDiscovery permissions that you want to assign. - - **To make a user an eDiscovery - - **To make a user an eDiscovery Administrator:** Next to **eDiscovery Administrator**, select **Edit**. On the **Choose eDiscovery Administrator** page, click  **Add**. Select the user (or users) you want to add as an **eDiscovery Administrator**, and then **Add**. When you're finished adding users, select **Done**. Then, on the **Editing Choose eDiscovery Administrator** wizard page, select **Save** to save the changes to the eDiscovery Administrator membership. +5. On the **eDiscovery Manager** flyout pane, do one of the following based on the eDiscovery permissions that you want to assign. + + **To make a user an eDiscovery + - Next to **eDiscovery Manager**, select **Edit**. + - On the **Choose eDiscovery Manager** wizard page, select  **Add**. + - Select the user (or users) you want to add as an eDiscovery manager, and then select **Add**. + - When you're finished adding users, select **Done**. + - On the **Editing Choose eDiscovery Manager** wizard page, select **Save** to save the changes to the eDiscovery Manager membership. + + **To make a user an eDiscovery Administrator:** + - Next to **eDiscovery Administrator**, select **Edit**. + - On the **Choose eDiscovery Administrator** page, select  **Add**. + - Select the user (or users) you want to add as an **eDiscovery Administrator**, and then **Add**. + - When you're finished adding users, select **Done**. + - On the **Editing Choose eDiscovery Administrator** wizard page, select **Save** to save the changes to the eDiscovery Administrator membership. > [!NOTE]-> You can also use the **Add-eDiscoveryCaseAdmin** cmdlet to make a user an eDiscovery Administrator. However, the user must be assigned the Case Management role before you can use this cmdlet to make them an eDiscovery Administrator. For more information, see [Add-eDiscoveryCaseAdmin](/powershell/module/exchange/add-ediscoverycaseadmin). +> You can also use the **Add-eDiscoveryCaseAdmin** cmdlet to make a user an eDiscovery Administrator. However, the user must be assigned the *Case Management* role before you can use this cmdlet to make them an eDiscovery Administrator. For more information, see [Add-eDiscoveryCaseAdmin](/powershell/module/exchange/add-ediscoverycaseadmin). -On the **Permissions** page in the compliance portal, you can also assign users eDiscovery-related permissions by adding them to the Compliance Administrator, Organization Management, and Reviewer role groups. For a description of the eDiscovery-related RBAC roles assigned to each of these role groups, see [RBAC roles related to eDiscovery](#rbac-roles-related-to-ediscovery). +On the **Permissions** page in the compliance portal, you can also assign users eDiscovery-related permissions by adding them to the *Compliance Administrator*, *Organization Management*, and *Reviewer* role groups. For a description of the eDiscovery-related role-based access control roles assigned to each of these role groups, see [Role-based access control roles related to eDiscovery](#rbac-roles-related-to-ediscovery). ## RBAC roles related to eDiscovery -The following table lists the eDiscovery-related RBAC roles in the compliance portal, and indicates the built-in role groups that each role is assigned to by default. +The following table lists the eDiscovery-related role-based access control roles in the compliance portal, and indicates the built-in role groups that each role is assigned to by default. | Role | Compliance Administrator | eDiscovery Manager & Administrator | Organization Management | Reviewer | |:--|:--:|:--:|:--:|:--:| The following table lists the eDiscovery-related RBAC roles in the compliance po |Custodian||||| |Export||||| |Hold|||||+|Manage review set tags| |||| |Preview||||| |Review||||| |RMS Decrypt||||| |Search And Purge||||| -The following sections describe each of the eDiscovery-related RBAC roles listed in the previous table. +The following sections describe each of the eDiscovery-related role-based access control roles listed in the previous table. ### Case Management -This role lets users create, edit, delete, and control access to eDiscovery (Standard) and eDiscovery (Premium) cases in the compliance portal. As previously explained, a user must be assigned the Case Management role before you can use the **Add-eDiscoveryCaseAdmin** cmdlet to make them an eDiscovery Administrator. +This role lets users create, edit, delete, and control access to eDiscovery (Standard) and eDiscovery (Premium) cases in the compliance portal. As previously explained, a user must be assigned the *Case Management* role before you can use the **Add-eDiscoveryCaseAdmin** cmdlet to make them an eDiscovery Administrator. For more information, see: - [Get started with eDiscovery (Standard)](get-started-core-ediscovery.md)- - [Get started with eDiscovery (Premium)](get-started-with-advanced-ediscovery.md) ### Communication For more information, see [Work with communications in eDiscovery (Premium)](man This role lets users run the Content Search tool in the compliance portal to search mailboxes and public folders, SharePoint Online sites, OneDrive for Business sites, Skype for Business conversations, Microsoft 365 groups, and Microsoft Teams, and Yammer groups. This role allows a user to get an estimate of the search results and create export reports, but other roles are needed to initiate content search actions such as previewing, exporting, or deleting search results. -In Content search and eDiscovery (Standard), users who are assigned the Compliance Search role but don't have the Preview role can preview the results of a search in which the preview action has been initiated by a user who is assigned the Preview role. The user without the Preview role can preview results for up to two weeks after the initial preview action was created. +In Content search and eDiscovery (Standard), users who are assigned the *Compliance Search* role but don't have the *Preview* role can preview the results of a search in which the preview action has been initiated by a user who is assigned the *Preview* role. The user without the *Preview* role can preview results for up to two weeks after the initial preview action was created. -Similarly, users in Content search and eDiscovery (Standard) who are assigned the Compliance Search role but don't have the Export role can download the results of a search in which the export action was initiated by a user who is assigned the Export role. The user without the Export role can download the results of a search for up to two weeks after the initial export action was created. After that, they can't download the results unless someone with the Export role restarts the export. +Similarly, users in Content search and eDiscovery (Standard) who are assigned the *Compliance Search* role but don't have the *Export* role can download the results of a search in which the export action was initiated by a user who is assigned the *Export* role. The user without the *Export* role can download the results of a search for up to two weeks after the initial export action was created. After that, they can't download the results unless someone with the *Export* role restarts the export. -The two-week grace period for previewing and exporting search results (without the corresponding search and export roles) doesn't apply to eDiscovery (Premium). Users must be assigned the Preview and Export roles to preview and export content in eDiscovery (Premium). +The two-week grace period for previewing and exporting search results (without the corresponding search and export roles) doesn't apply to eDiscovery (Premium). Users must be assigned the *Preview* and *Export* roles to preview and export content in eDiscovery (Premium). ### Custodian This role lets users place content on hold in mailboxes, public folders, sites, For more information about holds, see: - [Create a hold in eDiscovery (Standard)](create-ediscovery-holds.md) - - [Create a hold in eDiscovery (Premium)](add-custodians-to-case.md) +### Manage review set tags ++This role lets users create, edit, and delete review set tags for cases they can access. Users will need at least have the *Review* role and this role to [manage tags](/microsoft-365/compliance/tagging-documents#creating-and-applying-tags) during reviews. + ### Preview This role lets users view a list of items that were returned from a Content Search. They can also open and view each item from the list to view its contents. You can add role groups as members of eDiscovery (Standard) and eDiscovery (Prem - [Add or remove members from an eDiscovery (Premium) case](add-or-remove-members-from-a-case-in-advanced-ediscovery.md) -With this in mind, it's important to know that if a role is added or removed from a role group, then that role group will be automatically removed as a member of any case the role group is a member of. The reason for this is to protect your organization from inadvertently providing additional permissions to members of a case. Similarly, if a role group is deleted, it will be removed from all cases it was a member of. +With this requirement in mind, it's important to know that if a role is added or removed from a role group, then that role group will be automatically removed as a member of any case the role group is a member of. The reason for this is to protect your organization from inadvertently providing additional permissions to members of a case. Similarly, if a role group is deleted, it will be removed from all cases it was a member of. Before you add or remove roles to a role group that may be a member of an eDiscovery case, you can run the following commands in [Security & Compliance PowerShell](/powershell/exchange/connect-to-scc-powershell) to get a list of cases the role group is a member of. After you update the role group, you add the role group back as a member of those cases. Get-ComplianceCase -RoleGroup "Name of role group" -CaseType AdvancedEdiscovery - **Why create an eDiscovery Administrator?** As previously explained, an eDiscovery Administrator is member of the eDiscovery Manager role group who can view and access all eDiscovery cases in your organization. This ability to access all the eDiscovery cases has two important purposes: - If a person who is the only member of an eDiscovery case leaves your organization, no one (including members of the Organization Management role group or another member of the eDiscovery Manager role group) can access that eDiscovery case because they aren't a member of a case. In this situation, there would be no way to access the data in the case. But because an eDiscovery Administrator can access all eDiscovery cases in the organization, they can view the case and add themselves or another eDiscovery manager as a member of the case.+ - Because an eDiscovery Administrator can view and access all eDiscovery (Standard) and eDiscovery (Premium) cases, they can audit and oversee all cases and associated compliance searches. This functionality can help to prevent any misuse of compliance searches or eDiscovery cases. And because eDiscovery Administrators can access potentially sensitive information in the results of a compliance search, you should limit the number of people who are eDiscovery Administrators. - - Because an eDiscovery Administrator can view and access all eDiscovery (Standard) and eDiscovery (Premium) cases, they can audit and oversee all cases and associated compliance searches. This can help to prevent any misuse of compliance searches or eDiscovery cases. And because eDiscovery Administrators can access potentially sensitive information in the results of a compliance search, you should limit the number of people who are eDiscovery Administrators. --- **Can I add a group as a member of the eDiscovery Manager role group?** As previously explained, you can add a mail-enabled security group as a member of the eDiscovery Managers subgroup in the eDiscovery Manager role group by using the **Add-RoleGroupMember** cmdlet in Security & Compliance PowerShell. For example, you can run the following command to add a mail-enabled security group to the eDiscovery Manager role group. +- **Can I add a group as a member of the eDiscovery Manager role group?** As previously explained, you can add a mail-enabled security group as a member of the eDiscovery Managers subgroup in the *eDiscovery Manager* role group by using the **Add-RoleGroupMember** cmdlet in Security & Compliance PowerShell. For example, you can run the following command to add a mail-enabled security group to the *eDiscovery Manager* role group. ```powershell Add-RoleGroupMember "eDiscovery Manager" -Member <name of security group> |
| compliance | Create Apply Retention Labels | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/create-apply-retention-labels.md | Use the following sections to learn how published retention labels can be applie - [Automatically applying a retention label to email by using rules](#automatically-applying-a-retention-label-to-email-by-using-rules) -In addition, when you use [SharePoint Syntex](../contentunderstanding/index.md) and publish retention labels to SharePoint locations, you can [apply a retention label to a document understanding model](../contentunderstanding/apply-a-retention-label-to-a-model.md) so that identified documents are automatically labeled. +In addition, when you use [SharePoint Syntex](/microsoft-365/contentunderstanding/) and publish retention labels to SharePoint locations, you can [apply a retention label to a document understanding model](../contentunderstanding/apply-a-retention-label-to-a-model.md) so that identified documents are automatically labeled. After content is labeled, see the following information to understand when the applied label can be removed or changed: [Only one retention label at a time](retention.md#only-one-retention-label-at-a-time). |
| compliance | Enable Archive Mailboxes | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/enable-archive-mailboxes.md | Archiving in Microsoft 365 (also called *In-Place Archiving*) provides users wit Use the information in this article to enable or disable an archive mailbox by using an admin portal or by using PowerShell. Also learn how to run an automated diagnostic check on a user's archive mailbox to identify any problems and suggested resolutions. -Currently, you can use either the [Microsoft Purview compliance portal](microsoft-365-compliance-center.md) or the [new Exchange admin center (EAC)](/exchange/exchange-admin-center) to enable or disable archive mailboxes. +Configuration to enable or disable archive mailboxes is moving from the [Microsoft Purview compliance portal](microsoft-365-compliance-center.md) to the [new Exchange admin center (EAC)](/exchange/exchange-admin-center). Until this move is complete for all tenants, this page includes instructions for both admin experiences. [!INCLUDE [purview-preview](../includes/purview-preview.md)] |
| compliance | Enhancing Mail Flow With Mta Sts | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/enhancing-mail-flow-with-mta-sts.md | mx: *.mail.protection.outlook.com max_age: 604800 ``` -Any customer whose MX records point directly to Exchange Online can specify in their own policy, with the same values that are shown above in the microsoft.com policy. The unique required information in the policy is the MX record that points to Exchange Online (`*`.mail.protection.outlook.com), and the same certificate is shared by all Exchange Online customers. It's possible to publish your policy in *test* mode to ensure it's valid before changing it to *enforce* mode. There are third-party validation tools out there that can check your configuration. +Any customer whose MX records point directly to Exchange Online can specify in their own policy with the same values that are shown above in the microsoft.com policy. The unique required information in the policy is the MX record that points to Exchange Online (`*`.mail.protection.outlook.com) and the same certificate is shared by all Exchange Online customers. Exchange Online only allows one organization to receive emails for a given domain so using a wildcard doesn't weaken security, however that may not be the case for other email services. It's possible to publish your policy in *testing* mode to ensure it's valid before changing it to *enforce* mode. There are third-party validation tools out there that can check your configuration. These policies aren't something that Exchange Online can host on behalf of customers, so customers must configure their domain's STS policy using the services they prefer. Azure services can be easily used for policy hosting and there's a configuration walk-through later in this article. The policy needs to be protected by HTTPS with a certificate for the subdomain `mta-sts.<domain name>`. |
| compliance | Office 365 Encryption Risks And Protections | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/office-365-encryption-risks-and-protections.md | Some risk scenarios and the currently available encryption technologies that mit | | Skype for Business | AES 256-bit | AES external key is stored in a Secret Safe. The Secret Safe is a secured repository that requires high-level elevation and approvals to access. Access can be requested and approved only by using an internal tool called Lockbox. The AES external key is also stored in the Trusted Platform Module in the server. A 48-digit numerical password is stored in Active Directory and protected by Lockbox. | Yes | | Service Encryption | SharePoint Online | AES 256-bit | The keys used to encrypt the blobs are stored in the SharePoint Online Content Database. The SharePoint Online Content Database is protected by database access controls and encryption at rest. Encryption is performed using TDE in Azure SQL Database. These secrets are at the service level for SharePoint Online, not at the tenant level. These secrets (sometimes referred to as the master keys) are stored in a separate secure repository called the Key Store. TDE provides security at rest for both the active database and the database backups and transaction logs. When customers provide the optional key, the customer key is stored in Azure Key Vault, and the service uses the key to encrypt a tenant key, which is used to encrypt a site key, which is then used to encrypt the file level keys. Essentially, a new key hierarchy is introduced when the customer provides a key. | Yes | | | Skype for Business | AES 256-bit | Each piece of data is encrypted using a different randomly generated 256-bit key. The encryption key is stored in a corresponding metadata XML file, which is also encrypted by a per-conference master key. The master key is also randomly generated once per conference. | Yes |-| | Exchange Online | AES 256-bit | Each mailbox is encrypted using a data encryption policy that uses encryption keys controlled by Microsoft (on roadmap) or by the customer (when Customer Key is used). | Yes | +| | Exchange Online | AES 256-bit | Each mailbox is encrypted using a data encryption policy that uses encryption keys controlled by Microsoft or by the customer (when Customer Key is used). | Yes | | TLS between Microsoft 365 and clients/partners | Exchange Online | [Opportunistic TLS supporting multiple cipher suites](./exchange-online-uses-tls-to-secure-email-connections.md) | The TLS certificate for Exchange Online (outlook.office.com) is a 2048-bit SHA256RSA certificate issued by Baltimore CyberTrust Root. <br> <br> The TLS root certificate for Exchange Online is a 2048-bit SHA1RSA certificate issued by Baltimore CyberTrust Root. | Yes, when TLS 1.2 with 256-bit cipher strength is used | | | SharePoint Online | TLS 1.2 with AES 256 <br> <br> [Data Encryption in OneDrive for Business and SharePoint Online](./data-encryption-in-odb-and-spo.md) | The TLS certificate for SharePoint Online (*.sharepoint.com) is a 2048-bit SHA256RSA certificate issued by Baltimore CyberTrust Root. <br> <br> The TLS root certificate for SharePoint Online is a 2048-bit SHA1RSA certificate issued by Baltimore CyberTrust Root. | Yes | | | Skype for Business | [TLS for SIP communications and PSOM data sharing sessions](https://support.office.com/article/Set-up-your-network-for-Skype-for-Business-Online-d21f89b0-3afc-432e-b735-036b2432fdbf) | The TLS certificate for Skype for Business (*.lync.com) is a 2048-bit SHA256RSA certificate issued by Baltimore CyberTrust Root. <br> <br> The TLS root certificate for Skype for Business is a 2048-bit SHA256RSA certificate issued by Baltimore CyberTrust Root. | Yes | |
| contentunderstanding | Accessibility Mode | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/accessibility-mode.md | description: Learn how to use accessibility features mode when training and work # Accessibility mode in Microsoft Syntex -In [Microsoft Syntex](index.md), users can turn on accessibility mode in all stages of model training (label, train, test) when working with example documents. Using accessibility mode can help low-sight users to have easier keyboard accessibility as they navigate and label items in the document viewer. +<sup>**Applies to:**   ✓ Unstructured document processing </sup> -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. +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.  ## 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 system. +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.  For keyboard users using accessibility mode, if you are labeling text in an exam > [!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. For Narrator users using accessibility mode, use the same keyboard navigation de 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". ++- 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. |
| contentunderstanding | Adoption Assessment Tool | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/adoption-assessment-tool.md | |
| contentunderstanding | Adoption Getstarted | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/adoption-getstarted.md | Title: Get started driving adoption of Microsoft Syntex -description: Learn how to use and implement Microsoft Syntex in your organization to help you streamline your business processes. 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 havin - **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. There are two different ways of understanding your content. The model type you use is based on file format and use case. +With new AI services and capabilities, you can build content understanding and classification apps directly into the content management flow using Syntex. 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. -| Form processing | Document understanding | -|:-|:-| -| Created from document library. | Created in the content center, part of Syntex. | -| Model created in AI builder. | Model created in native interface. | -| Used for semi-structured file formats. | Used for unstructured file formats. | -| Settable classifier. | Trainable classifier with optional extractors. | -| Restricted to a single library. | Can be applied to multiple libraries. | -| Train on PDF, JPG, PNG format, total 50 MB/500 pp. | Train on 5-10 PDF, Office, or email files, including negative examples. | +| 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 capabilities, see [Difference between document understanding and form processing models](difference-between-document-understanding-and-form-processing-model.md). +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 org based on where the model will be applied. Here are a few scenarios where document understanding can help your organization: +To prepare for using Syntex in your organization, you first need to understand the scenarios in which it will be useful. The "why" helps determine what model will be needed, and how to structure your 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. -- **Content processing:** Process contracts, statements of work, and other form-like documents. Intake the forms, train the model to understand and map the fields, and then run your forms through to automatically collect the data. For more information, see [Form processing overview](form-processing-overview.md).-- **Invoice analysis:** Pull out the relevant details from your invoices and make sure they're complying with policy or are being processed appropriately.+- **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: Prioritize scenarios based on impact and ease of implementation. Make your initi Use the [example scenarios and use cases](adoption-scenarios.md) to prompt ideas about how you can use Syntex in your organization. -## Identify roles & responsibilities +## 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 form processing | Configure Dataverse environment for form processing | Gather use cases | Gather business use cases | +| 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 may be involved: Compliance admin, Taxonomy managers. +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? -- Form processing: Decide which sites will get Form processing action.-- Document understanding: You can create multiple content centers for different business areas.+- 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 Identify the stakeholders for your project. |Role |Responsibilities |Department | |:-|:-|:--|-| Executive sponsor(s) | Communicate high-level vision and values to the company | Executive leadership | -| Project lead(s) | Oversee the entire launch execution and rollout process | Project management | +| 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) | Identify the stakeholders for your project. | Power Platform administrator| Configure Dataverse environment | IT department| > [!NOTE]-> Though we recommend having each of these roles fulfilled throughout your rollout, you may find that you don't require them all to get started with your identified solution. +> 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: - + 1. Plan the end state- - Document understanding models are the means, not the end. + - Models are the means, not the end. - Plan for harnessing the value of extracted metadata with: - Search - Filtering and view formatting To get ready for implementing Syntex, you need to: - 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, management. + - 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 project plan. -1. Configure settings and apply licenses. -1. Begin awareness and training ΓÇô Recruit Champions. -1. Roll out in stages. -1. Gather feedback and iterate. -1. As usage grows plan for any AI Builder credits as needed. +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 -[Scenarios and use cases for Syntex](adoption-scenarios.md) +[Microsoft Syntex adoption center](https://adoption.microsoft.com/sharepoint-syntex/adoption/) ++[Scenarios and use cases for Microsoft Syntex](adoption-scenarios.md) -[Manage contracts using a Microsoft 365 solution](solution-manage-contracts-in-microsoft-365.md) +[Overview of model types in Microsoft Syntex](syntex-overview.md) |
| contentunderstanding | Adoption Scenarios | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/adoption-scenarios.md | description: Find business scenarios about how to use Microsoft Syntex in your o Use the following example scenarios to prompt ideas about how you can use Microsoft Syntex in your organization. -- [Scenario: Track data from invoices with form processing](adoption-scenarios.md#scenario-track-data-from-invoices-with-form-processing)-- [Scenario: Track information from contracts with document understanding](adoption-scenarios.md#scenario-track-information-from-contracts-with-document-understanding)+- [Scenario: 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 data from invoices with form processing +## 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.-1. Train the model to recognize fields in the documents. -1. Extract the fields you want to track into a list. -1. Set up a flow to notify you for specific events, such as: +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. 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 with document understanding +## 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 document understanding model for contracts. -1. Upload sample documents for positive and negative examples, then run the training to identify contract documents and review the results. -1. Train the extractor to identify fields in the contracts, such as the client name, fee, and date, and then test the extractor. -1. When the model is complete, apply the model to a library where you can upload contracts. -1. Apply a retention label to the date field, so that contracts are retained in the library for the required length of time. +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.  When you automate this scenario, you can: 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 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. For example, an HR director needs to quickly access all HR documents ΓÇô includi When you automate this scenario, you can: - Unlock knowledge from digital content.-- Classify HR policies, resumes, sales documents, technical blueprints, account plans and extract information.+- 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. When you automate this scenario, you can: ## 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 document library by using OCR processing and then extract the metadata from those orders so you can fulfill them by using automated processes. +With Syntex, you can reduce the time of manual processing of customer orders. For example, you can upload orders from fax, email, or paper into SharePoint 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: ## 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 and/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. +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: When you automate this scenario, you can ensure that: ## See also -[Get started driving adoption of Syntex](adoption-getstarted.md) +[Get started driving adoption of Microsoft Syntex](adoption-getstarted.md) ++[Manage contracts using a Microsoft 365 solution](solution-manage-contracts-in-microsoft-365.md) |
| contentunderstanding | Apply A Model | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/apply-a-model.md | Title: Apply a document understanding model in Microsoft Syntex + Title: Apply a model to a document library in Microsoft Syntex audience: admin -+ search.appverid: - enabler-strategic ms.localizationpriority: medium description: Learn how to apply a published a model to a SharePoint document library in Microsoft Syntex. -# Apply a document understanding model in Microsoft Syntex +# Apply a model to a document library in Microsoft Syntex +<sup>**Applies to:**   ✓ All custom models   |   ✓ All prebuilt models</sup> ++<! </br> > [!VIDEO https://www.microsoft.com/videoplayer/embed/RE4CSoL] </br>+> -After publishing your document understanding model, you can apply it to one or more SharePoint document libraries in your Microsoft 365 tenant. +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. -> [!NOTE] -> You are only able to apply the model to document libraries that you have access to. +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 -To apply your model to a SharePoint 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**. +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**.  To apply your model to a SharePoint document library:  - For more information, see [Change the view in a document library](#change-the-view-in-a-document-library) later in this article. + 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 document understanding models**. +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. After applying the model to the document library, you can begin uploading docume 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 document understanding 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 custom form processing model and document understanding model are applied to the same library, the file is classified using the document understanding model and any trained extractors for that model. If there are any empty columns that match the form processing model, the columns will be populated using those extracted values. +> 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 libraries +## 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 one or only selected libraries: ## Apply the model to files and folder content already in the document library -While an applied model processes all files and folder content uploaded to the document library after it's applied, you can also do the following to run the model on files and folder content that already exist in the document library prior to the model being applied: +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. While an applied model processes all files and folder content uploaded to the do ### Classification Date field -When a Syntex document understanding model (or a form processing 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 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.  To run the flow:  -## Change the view in a document library -- ## See also -[Create a classifier](create-a-classifier.md) +[Share an enterprise model](model-discovery.md) ++[Discover other trained models](discover-other-trained-models.md) -[Create an extractor](create-an-extractor.md) +[Choose the view in a document library](choose-library-view.md) -[Document Understanding overview](document-understanding-overview.md) |
| contentunderstanding | Apply A Retention Label To A Model | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/apply-a-retention-label-to-a-model.md | 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:**   ✓ Unstructured document processing   |   ✓ Structured document processing  |   ✓ 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. -You can easily apply a [retention label](../compliance/retention.md) to a model in Microsoft Syntex. You can do this for both document understanding and form processing models. +> [!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 cannot be deleted from the document library for the specified time period (the next five months, for example). +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 document understanding 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. +> 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. ++  -## To add a retention label to a document understanding model +3. Select the retention label you want to apply to the model, and then select **Save**. -1. From the model home page, select **Model settings**.</br> -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 your to apply to the model.</br> - </br> -3. Select the retention label you want to apply to the model, and then select **Save**.</br> +After applying the retention label to your model, you're able to apply it to a: -After applying the retention label to your model, you are 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 +### Apply the retention label to a document library to which the model is already applied -If your document understanding 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:</br> +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. </br> -2. Select **Sync**. </br> - </br> +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**. -After applying the update and syncing it to your model, you can confirm that it has been applied by doing the following: + </br> -1. In the content center, in the **Libraries with this model** section, click on the library to which your updated model was applied. </br> -2. In your document library view, select the information icon to check the model properties.</br> -3. In the **Active models** list, select your updated model.</br> -4. In the **Retention label** section you will see the name of the applied retention label.</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. -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 it's 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. +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. -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 is not allowed because of the applied retention label. +4. In the **Retention label** section, you'll see the name of the applied retention label. -## To add a retention label to a form processing model +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. -> [!Important] -> For retention labels to be available to apply to your form processing model, 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. +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. -You can either apply a retention label to a form processing model when you are creating a model, or apply it to an existing model. +## Add a retention label to a structured document processing model -### To add a retention label when you create a form 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. -1. When you are [creating a new form processing model](./create-a-form-processing-model.md), select <b>Advanced settings.</b> -2. In <b>Advanced settings</b>, in the <b>Retention label</b> section, select the menu and then select the retention label you want to apply to the model.</b> +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. - - </br> +### To add a retention label when you create a structured document processing model -3. After you've completed your remaining model settings, select <b>Create</b> to build your model. +1. When you're [creating a new structured document processing model](./create-a-form-processing-model.md), select **Advanced settings**. -### To add a retention label to an existing form processing model +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. + +  -You can add a retention label to an existing form processing model in different ways: -- Through the Automate menu in the document library-- Through the Active model settings in the document library +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 -#### To add a retention label to an existing form processing model through the Automate menu +You can add a retention label to an existing structured document processing model in different ways: -You can add a retention label to an existing form processing model that you own through the Automate menu in the document library in which the model is applied. +- 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 -1. In your document library to which the form processing model is applied, select the <b>Automate</b> menu, select <b>AI Builder</b>, then select <b>View form processing model details</b>. +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. - </br> +1. In your document library to which the model is applied, select the **Automate** > **AI Builder** > **View model details**. -2. In the model details, in the <b>Retention Label</b> section, select the retention label you want to apply. Then select <b>Save</b>. +  - </br> +2. In the model details, in the **Retention label** section, select the retention label you want to apply, and then select **Save**. -#### To add a retention label to an existing form processing model in the active model settings + </br> -You can add a retention label to an existing form processing model that you own through the Active model settings in the document library in which the model is applied. +#### To add a retention label to an existing structured document processing model in the active model settings -1. In the SharePoint document library in which the model is applied, select the <b>View active models</b> icon, and then select <b>View active models</b>.</b> +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. - </br> +1. In the SharePoint document library in which the model is applied, select the **View active models** icon, and then select **View active models**. -2. In <b>Active models</b>, select the form processing model to which you want to apply the retention label. +  - </br> +2. In **Active models**, select the model to which you want to apply the retention label. + </br> -3. In the model details, in the <b>Retention Label</b> section, select the retention label you want to apply. Then select <b>Save</b>. +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 -[Create a classifier](create-a-classifier.md) +[Apply a sensitivity label to a model in Microsoft Syntex](create-a-classifier.md) + -[Create an extractor](create-an-extractor.md) -[Document Understanding overview](document-understanding-overview.md) |
| contentunderstanding | Apply A Sensitivity Label To A Model | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/apply-a-sensitivity-label-to-a-model.md | description: Learn how to apply a sensitivity label to a model in Microsoft Synt # Apply a sensitivity label to a model in Microsoft Syntex -You can easily apply a [sensitivity label](../compliance/sensitivity-labels.md) to document understanding models in Microsoft Syntex. This feature isn't available yet for form processing models. +<sup>**Applies to:**   ✓ Unstructured document processing </sup> -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 do not overwrite an existing label that was manually applied by a user to the file. +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 document understanding models, they need to be [created and published in the Microsoft Purview compliance portal](../admin/security-and-compliance/set-up-compliance.md). +> 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 document understanding model +## Add a sensitivity label to a model 1. From the model home page, select **Model settings**. After you apply the sensitivity label to your model, you can apply it to a: ### Apply the sensitivity label to a document library to which the model is already applied -If your document understanding 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: +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. On your model's view page in your document library, a new **Sensitivity label** 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. -<! -## Add a sensitivity label to a form processing model --> [!Important] -> For sensitivity labels to be available to apply to your form processing model, they need to be [created and published in the Microsoft Purview compliance portal](../admin/security-and-compliance/set-up-compliance.md). --You can either apply a sensitivity label to a form processing model when you are creating a model, or apply it to an existing model. --### Add a sensitivity label when you create a form processing model --1. When you [create a new form processing model](create-a-form-processing-model.md), select **Advanced settings**. --2. In **Advanced settings**, in the **Sensitivity label** section, select the menu and then select the sensitivity label you want to apply to the model. --3. After you've completed your remaining model settings, select **Create** to build your model. --### Add a sensitivity label to an existing form processing model --You can add a sensitivity label to an existing form processing model in different ways: --- Through the **Automate** menu in the document library-- Through the **Active model** settings in the document library --#### Add a sensitivity label to an existing form processing model through the Automate menu --You can add a sensitivity label to an existing form 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 form processing model is applied, select the **Automate** menu, select **AI Builder**, and then select **View form processing model details**. --2. On the **Model details** pane, in the **Sensitivity label** section, select the sensitivity label you want to apply. Then select **Save**. --#### Add a sensitivity label to an existing form processing model in the active model settings --You can add a sensitivity label to an existing form 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**. --2. In **Active models**, select the form processing model to which you want to apply the sensitivity label. --3. On the **Model details** pane, in the **Sensitivity label** section, select the sensitivity label you want to apply. Then select **Save**. -- > [!NOTE] - > You must be the model owner for the **Model settings** pane to be editable. -> - ## See also [Apply a retention label](apply-a-retention-label-to-a-model.md) -[Create a classifier](create-a-classifier.md) --[Create an extractor](create-an-extractor.md) --[Document Understanding overview](document-understanding-overview.md) |
| contentunderstanding | Automate Document Generation | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/automate-document-generation.md | Title: Automate document generation with Microsoft Syntex and Power Automate (preview) + Title: Automate document generation with Microsoft Syntex and Power Automate (Preview) audience: admin -+ search.appverid: - enabler-strategic Follow these steps to automatically generate documents using a modern template a ## See also - [Create documents using content assembly in Microsoft Syntex](content-assembly.md) + [Overview of content assembly in Microsoft Syntex](content-assembly.md) |
| contentunderstanding | Choose Library View | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/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:**   ✓ All custom models   |   ✓ 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. ++  ++## 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. ++  ++For example, if you select **Tiles** from the list, the page will display as shown. ++  ++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**. +++ |
| contentunderstanding | Content Assembly Create Document | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/content-assembly-create-document.md | |
| contentunderstanding | Content Assembly Modern Template | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/content-assembly-modern-template.md | |
| contentunderstanding | Content Assembly | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/content-assembly.md | You upload an existing document to create a modern template, and then use that t > [!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 |
| contentunderstanding | Create A Classifier | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/create-a-classifier.md | description: Learn how to create a classifier in Microsoft Syntex. # Create a classifier in Microsoft Syntex +<sup>**Applies to:**   ✓ Unstructured document processing </sup> </br> To create a classifier, you need to: The first step to create your model is to give it a name: -1. From the content center, select **New**, and then **Create a model**. -2. In the **New document understanding model** pane, in the **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*. -3. Choose **Create**. This creates a home page for the model.</br> +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.  Select **Advanced settings** if you want to map this model to an existing enterp ## 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> +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. If you received a match on your labeled sample files, you can now test your mod [Create an extractor](create-an-extractor.md) -[Document Understanding overview](document-understanding-overview.md) - [Explanation types](explanation-types-overview.md) [Apply a model](apply-a-model.md) -[Syntex accessibility mode](accessibility-mode.md) +[Syntex accessibility mode](accessibility-mode.md) |
| contentunderstanding | Create A Content Center | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/create-a-content-center.md | description: Learn how to create a content center in Microsoft Syntex. # Create a content center in Microsoft Syntex +<sup>**Applies to:**   ✓ All custom models   |   ✓ All prebuilt models</sup> +<! </br> > [!VIDEO https://www.microsoft.com/videoplayer/embed/RE4CPSF] </br>+> -To create and manage document understanding 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. +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.  -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 may be fine for environments for which you want a roll-up of all model activity, you may want to have additional centers for multiple departments within your organization, which might have different needs and permission requirements for their models. +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 document understanding models but can't apply them to a document library. +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. A SharePoint admin can create a content center site like they would [create any 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>. +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, click **Create**, and then select **Other options**. +2. On the **Active sites** page, select **Create**, and then select **Other options**. -3. On the **Choose a template** menu, select **Content Center**. +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> +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 will see it listed on <a href="https://go.microsoft.com/fwlink/?linkid=2185220" target="_blank">**Active sites**</a> in the SharePoint admin center. +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 In Syntex, the first content center created during setup is the *default content  -The **Models** library in the default content center view groups the created models by content center for a summary view of all document understanding models and form processing models that have been created. +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 -[Create a classifier](create-a-classifier.md) +[Overview of model types](model-types-overview.md) -[Create an extractor](create-an-extractor.md) -[Create a content center](create-a-content-center.md) --[Document understanding overview](document-understanding-overview.md) --[Create a form processing model](create-a-form-processing-model.md) --[Apply a model](apply-a-model.md) |
| contentunderstanding | Create A Form Processing Model | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/create-a-form-processing-model.md | Title: Create a form processing model in Microsoft Syntex + 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 create a form processing model in Microsoft Syntex. +description: Learn how to train a structured document processing model in Microsoft Syntex. -# Create a form 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 - Microsoft Syntex users can create a [form processing model](form-processing-overview.md) directly from a SharePoint document library. -Creating a form processing model involves the following steps: +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. -## Requirements + -You can only create a form processing model in SharePoint document libraries for which it's enabled. If form processing is enabled, you're able to see the **Automate** > **AI Builder** > **Create a model to process forms** menu in your document library. If you need processing enabled on your document library, you must contact your SharePoint administrator. +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: Create a form processing model +## Step 1: Add and analyze documents -The first step in creating a form processing model is to name the model, define the new content type, and create a new document library view for it. --1. From the document library, select the **Automate** menu, select **AI Builder**, and then select **Create a model to process forms**. --  --2. In the **Create a model to process forms** panel, in the **Name** field, type a name for your model (for example, *Purchase Orders*). --  --3. You can now automatically extract and save information from a *collection* of structured files that share a similar layoutΓÇösuch as invoices or tax documentsΓÇöthat are in a SharePoint document library. This lets you compose several models into a single model and extract specific table item information. -- The collection name is saved to a dedicated column in the document library where the model is applied, which allows you to distinguish different file layouts processed by the same model. -- In addition, the extracted table information is saved to a specified list and associated with the uploaded file for easy viewing or for additional business process automation. -- To extract table information to an associated list:<br><br> -- 1. In the **Extract info from tables?** section, select **Yes**. --  -- 2. In the **Where should we save table info?** section: - - - If you select **A new list** (the default setting), a suggested name is automatically provided in the **New list name** box. You can modify the name if you want to. If you want to show the list in the site navigation, select the **Show in site navigation** checkbox. -- - If you select **An existing list**, in the **Selected list** box, choose the list you want to use. --4. When you create a form processing model, you create a new SharePoint content type. A SharePoint 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 <a href="https://go.microsoft.com/fwlink/?linkid=2185219" target="_blank">SharePoint admin center</a>. -- To map this model to an existing content type in the SharePoint content types gallery, select **Advanced settings**. --  -- 1. In the <a href="https://go.microsoft.com/fwlink/?linkid=2185074" target="_blank">Content type gallery</a>, choose whether to create a new content type or to use an existing one. -- 2. To use an existing content type, select **Select one**, and choose a content type from the list. -- 3. Your model creates a new view in your document library for your extracted data. If you don't want it to be the default view, in the **Library view for this model** section, clear the **Set the view as default** checkbox. -- 4. To apply a retention label to your files, in the **Retention label** section, select the retention label you want to use. --5. Select **Create**. --## Step 2: Add and analyze documents --After you create your new form processing model, your browser opens a new Power Apps AI Builder forms processing model page. On this page, you can add and analyze your example 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 [form processing model input document requirements and optimization tips](/ai-builder/form-processing-model-requirements). +> 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 the example files for each, AI Builder will examine the uploaded documents to detect the fields and tables. This usually takes a few minutes. When the analysis is complete, you can proceed with tagging the documents. +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 3: Tag fields and tables +## 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 4: Train and publish your model +## 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. For detailed steps, see [Train and publish your form processing model](/ai-builder/form-processing-train). +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). -2. After the model is published, select **Use model**, and then select **Create flow**. This creates a Power Automate flow that can run in your SharePoint document library and that extracts the fields that have been identified in the model. +  -  - -3. When completed, you'll see the message: *Your flow was successfully created*. +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. -4. Select the **Go to SharePoint** button to see the document library updated with your model. +  -## Step 5: Use your model +## Step 4: Use your model 1. In the document library model view, notice that the fields you selected now display as columns.  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. -  +  > [!NOTE]-> If a custom form processing model and document understanding model are applied to the same library, the file is classified using the document understanding model and any trained extractors for that model. If there are any empty columns that match the form processing model, the columns will be populated using those extracted values. +> 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**. ++  ### Use flows to extract information -Two flows are available to process a selected file or batch of files in a library where a form processing model has been applied. +> [!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 form processing model** ΓÇö Use to extract text from a selected image or PDF file by running a form 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**.+- **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**.  -- **Extract info from files with a form processing model** ΓÇö Use with form 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:+- **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 is not to include previously processed files). + - 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). Two flows are available to process a selected file or batch of files in a librar  > [!NOTE]-> The **Extract info from an image or PDF file with a form processing model** flow is automatically available for a library with a form processing model associated. The **Extract info from files with a form processing model** flow is a template that must be added to the library if required. +> 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. -### Classification Date field --When a Syntex form processing model (or a document understanding 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**. +## See also -  +[Create a model in Microsoft Syntex](create-syntex-model.md) -## See also - [Power Automate documentation](/power-automate/) [Training: Improve business performance with AI Builder](/training/paths/improve-business-performance-ai-builder/?source=learn) |
| contentunderstanding | Create An Extractor | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/create-an-extractor.md | description: Learn how to create an extractor in Microsoft Syntex. # Create an extractor in Microsoft Syntex +<sup>**Applies to:**   ✓ Unstructured document processing </sup> <br/> The next step is to label the entity you want to extract in your example trainin 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, 2019*). and then select **Save**. You should see the value display from the file in the Labeled examples list, under the **Label** column. +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. The Find feature is useful if you're searching a large document or if there are 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/2019-- October 14, 2019-- Monday, October 14, 2019+- 10/14/2022 +- October 14, 2022 +- Monday, October 14, 2022 To help identify the *Service Start Date*, you can create a pattern explanation. To help identify the *Service Start Date*, you can create a pattern explanation. > [!NOTE] > For more learn more about explanation types, see [Explanation types](./explanation-types-overview.md). -### Use the Explanation library +### 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. If you have duplicate entities and want to extract only one value or a certain n [Leverage term store taxonomy when creating an extractor](leverage-term-store-taxonomy.md) -[Document Understanding overview](document-understanding-overview.md) --[Apply a model](apply-a-model.md) - [Syntex accessibility mode](accessibility-mode.md) |
| contentunderstanding | Create Local Model | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/create-local-model.md | description: Learn how to create a local model on a local SharePoint site with M # Create a model on a local SharePoint site with Microsoft Syntex -Microsoft Syntex now 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. +<sup>**Applies to:**   ✓ All custom models   |   ✓ 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 b - Explanation templates list - Model usage list -This feature is available only for creating [document understanding models](apply-a-model.md) and [prebuilt models](prebuilt-models.md). +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 This feature is available only for creating [document understanding models](appl  -6. Proceed to [train your document understanding model](apply-a-model.md) or to [configure your prebuilt model](prebuilt-models.md) using the files that you selected. +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. This feature is available only for creating [document understanding models](appl  +> [!NOTE] +> When a local model is applied to a single library, it becomes available for discovery for application to other libraries in same site. |
| contentunderstanding | Create Syntex Model | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/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:**   ✓ All custom models   |   ✓ 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**. ++ ++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) ++ ++> [!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 types of custom models you can create. ++ ++- **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. ++  + +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. ++  + +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. ++  + +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. ++ ++- **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. ++  + +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. ++  + +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. ++  + +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. ++  + +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. ++  + +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. ++  ++ - [**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. ++  + +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. ++  + +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). +> |
| contentunderstanding | Delete A Model | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/delete-a-model.md | -description: Learn how to delete a document understanding model in Microsoft Syntex. +description: Learn how to delete a model in Microsoft Syntex. # Delete a model in Microsoft Syntex -At some point, you might want to delete a document understanding model or a prebuilt model. Before you delete the model, you must first remove the model from all of the SharePoint document libraries where it has been applied. +<sup>**Applies to:**   ✓ All custom models   |   ✓ 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, ## Delete a model -Follow these steps to delete a document understanding model or a prebuilt 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. Follow these steps to delete a document understanding model or a prebuilt model. ## See also -[Document understanding overview](document-understanding-overview.md) +[Rename a model](rename-a-model.md) -[Apply a model](apply-a-model.md) |
| contentunderstanding | Difference Between Document Understanding And Form Processing Model | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/difference-between-document-understanding-and-form-processing-model.md | Title: Differences between custom models in Microsoft Syntex + Title: Compare custom models in Microsoft Syntex audience: admin -+ search.appverid: - enabler-strategic - m365initiative-syntex ms.localizationpriority: medium-description: Learn about key differences between a document understanding model and a form processing model in Microsoft Syntex. +description: Learn about key differences between custom models in Microsoft Syntex. -# Differences between custom models in Microsoft Syntex +# Compare custom models in Microsoft Syntex -Content understanding in Microsoft Syntex allows you to identify and classify documents that are uploaded to SharePoint document libraries, and then to extract relevant information from each file. For example, as files are uploaded to a SharePoint document library, all files that are identified as *Purchase Orders* are classified as such, and then displayed in a custom document library view. Additionally, you can pull specific information from each file (for example, *PO Number* and *Total*) and display it as a column in your document library view. --Content understanding lets you create *models* to identify and extract the information you need. Models have value in helping to resolve business issues for search, business processes, compliance, and many others. --There are two custom model types that you can use: --- [Document understanding models](document-understanding-overview.md)-- [Form processing models](form-processing-overview.md)--While both models are generally used for the same purpose, the key differences listed below affect which ones you can use. --> [!NOTE] -> See the [Get started driving adoption of Syntex](./adoption-getstarted.md) for more information about form processing and document understanding scenario examples. --## Structured versus unstructured and semi-structured content --Use document understanding models to identify and extract data from unstructured documents, such as letters or contracts, where the text entities you want to extract is in sentences or specific regions of the document. 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. --Use form processing models to identify files and extract data from structured or semi-structured documents, such as forms or invoices. Form processing models are trained to understand the layout of your form from example documents, and learn 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 in a tax form). --> [!NOTE] -> You must have access to a content center site to create a document understanding model or to apply one to a SharePoint document library. --## Where models are created --Document understanding models are created and managed in a SharePoint content center site. --> [!NOTE] -> For more information about input documents, see [Form processing model requirements and limitations](/ai-builder/form-processing-model-requirements). --Form processing models are created in Power Apps [AI Builder](/ai-builder/overview), but the creation starts directly from a SharePoint document library. A document library must have form processing model creation enabled before a user can create a form processing model for it. Admins can enable form processing model creation in the content understanding admin settings. Form processing models use Power Automate flows to process files when they're uploaded to the document library. --When you create a document understanding model, you create a new [SharePoint content type](https://support.microsoft.com/office/use-content-types-to-manage-content-consistently-on-a-site-48512bcb-6527-480b-b096-c03b7ec1d978) that is saved to the SharePoint Content Types gallery. Or you can use existing content types to define your model if needed. --Once a content type is created and associated with a model, you can also reference that model from the **Site Content Type** property panel. ---Form processing models also create new [SharePoint content types](https://support.microsoft.com/office/use-content-types-to-manage-content-consistently-on-a-site-48512bcb-6527-480b-b096-c03b7ec1d978), and are also stored in the SharePoint Content Types gallery. --## Where they can be applied --You can apply document understanding models to SharePoint document libraries that you have access to. Use the content center to create a document understanding model, and apply it to different document libraries. The content center gives you a more central control for how document understanding models are used and where they're applied. Note this information must also roll up to a content center. --Form processing models can currently be applied only to the SharePoint document library from which you created them. This allows licensed users with access to the site to create a form processing model. Note that an admin needs to enable form processing on a SharePoint document library for it to be available to licensed users. --## Comparison of form processing and document understanding --Use the following table to understand when to use form processing and when to use document understanding. --| Feature | Form processing | Document understanding | -| - | - | - | -| Model type - when to use each | 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. | Unstructured or semi-structured file formats, for example, Office documents where there are differences in the layout, but still similar information to be extracted. | -| Model creation | Model created in AI builder with seamless access from SharePoint document library.| Model created in SharePoint in a new site, the content center. | -| Classification type| Settable classifier is used to give clues to the system on what data to extract.| Trainable classifier with optional extractors using machine teaching to assign document location on what data to extract.| -| Locations | Trained for a single document library.| Can be applied to multiple libraries.| -| Supported file types| Train on PDF, JPG, PNG format, total 50 MB and 500 pages.| Train on 5-10 PDF, Office, or email files, including negative examples.<br>Office files are truncated at 64K characters. OCR-scanned files are limited to 20 pages. See [supported file types](document-understanding-overview.md#supported-file-types).| -| Integrate with Managed Metadata | No | Yes, by training entity extractor referencing a configured managed metadata field.| -| Compliance feature integration with Microsoft Purview Information Protection | Set published retention labels.<br>Set sensitivity labels is coming. | Set published retention labels.<br>Set published sensitivity labels. | -| Supported regions| Form processing 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/). | Available in all regions.| -| Transactional cost | Uses AI Builder credits.<br>3.5K credits are included for each Syntex license per month.<br>1M credits will allow processing of 2,000 file pages.<br>| Not applicable | -| Capacity | Uses the default Power Platform environment (custom environments with Dataverse database supported). | Does not have capacity restrictions.| -| Supported languages| Language support for more than [73 languages](/power-platform-release-plan/2021wave2/ai-builder/form-processing-new-language-support). | Models work on all Latin alphabet languages. In addition to English: German, Swedish, French, Spanish, Italian, and Portuguese.| +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 | +| - | - | - | - | +| 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. | Trained for a single document library. | Trained for a single document library. | +| 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) -[Document understanding overview](document-understanding-overview.md) --[Form processing overview](form-processing-overview.md) -[Introduction to Microsoft Syntex](index.md) |
| contentunderstanding | Discover Other Trained Models | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/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:**   ✓ All custom models   |   ✓ 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. ++  ++ - 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. ++  ++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**. ++  ++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**. ++  ++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**. ++  ++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. ++  ++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) |
| contentunderstanding | Document Understanding Overview | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/document-understanding-overview.md | Title: Document understanding overview in Microsoft Syntex + Title: Overview of unstructured document processing in Microsoft Syntex audience: admin -ms.customer: intro-overview -++ search.appverid: - enabler-strategic - m365initiative-syntex ms.localizationpriority: medium-description: Learn about document understanding in Microsoft Syntex. +description: Learn about the unstructured document processing model in Microsoft Syntex. -# Document understanding overview in Microsoft Syntex +# Overview of unstructured document processing in Microsoft Syntex +> [!NOTE] +> *Unstructured document processing* was known as *document understanding* in previous releases. +<! </br> > [!VIDEO https://www.microsoft.com/videoplayer/embed/RE4CSu7] </br>+> ++Use the unstructured document processing model ([training 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. -Document understanding uses artificial intelligence (AI) models to automate classification of files and extraction of information. 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). +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). > [!NOTE]-> See the [Syntex adoption: Get started guide](./adoption-getstarted.md) for more information about document understanding scenario examples. +> 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). -Document understanding models are created and managed in a type of SharePoint site called a *content center*. 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. +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 cannot be updated, so they can't be used in a model. +> Read-only or sealed content types can't be updated, so they can't be used in a model. -Add *classifiers* and *extractors* to your document understanding models to do the following actions: +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. You can use example files to train and test your classifiers and extractors in y After publishing your model, use the content center to apply it to any SharePoint document library that you have access to. -## File limitations --Document understanding models use Optical Character Recognition (OCR) technology to scan PDFs, images, and TIFF files. Files are scanned when you train a model with example files and when you run the model against files in a document library. --Note the following differences about Microsoft Office text-based files and OCR-scanned files (PDF, image, or TIFF): --- Office files: Truncated at 64,000 characters (in training and when run against files in a document library).--- OCR-scanned files: There's a 20-page limit. --### Requirements --OCR processing works best on documents that meet the following requirements: --- JPG, PNG, or PDF format (text or scanned). Text-embedded PDFs are better, because there won't be any errors in character extraction and location.--- If your PDFs are password-locked, you must remove the lock before submitting them.--- 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.--- For images, dimensions must be between 50 x 50 and 10,000 x 10,000 pixels.- > [!NOTE] - > Images that are very wide or have odd dimensions (for example, floor plans) might get truncated in the OCR process and lose accuracy. --- For PDF files, dimensions must be at most 17 x 17 inches, corresponding to Legal or A3 paper sizes and smaller.+## Requirements -- If scanned from paper documents, scans should be high-quality images.--- Must use the Latin alphabet (English characters).--### Supported file types --Document understanding models support the following file types: --- csv-- doc-- docx-- eml-- heic-- heif-- htm-- html-- jpeg-- jpg-- markdown-- md-- msg-- pdf-- png-- ppt-- pptx-- rtf-- tif-- tiff-- txt-- xls-- xlsx--### Supported languages --Document understanding models support *all* of the Latin-based languages, including: --- English-- French-- German-- Italian-- Spanish+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 -[Create a classifier](create-a-classifier.md) --[Create an extractor](create-an-extractor.md) --[Create a content center](create-a-content-center.md) --[Create a form processing model](create-a-form-processing-model.md) --[Apply a model](apply-a-model.md) --[Difference between a document understanding and a form processing model](difference-between-document-understanding-and-form-processing-model.md) - -[Form processing overview](form-processing-overview.md) +[Compare custom models](difference-between-document-understanding-and-form-processing-model.md) -[Syntex accessibility mode](accessibility-mode.md) |
| contentunderstanding | Duplicate A Model | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/duplicate-a-model.md | -description: Learn how and why to duplicate a document understanding model in Microsoft Syntex. +description: Learn how and why to duplicate a model in Microsoft Syntex. # Duplicate a model in Microsoft Syntex -Duplicating a document understanding 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. +<sup>**Applies to:**   ✓ 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 R ## Duplicate a model -Follow these steps to duplicate a document understanding model. +Follow these steps to duplicate an unstructured document processingmodel. 1. From the content center, select **Models** to see your models list. Follow these steps to duplicate a document understanding model. ## See also -[Create a classifier](create-a-classifier.md) - [Rename a model](rename-a-model.md) -[Create an extractor](create-an-extractor.md) --[Document Understanding overview](document-understanding-overview.md) --[Explanation types](explanation-types-overview.md) --[Apply a model](apply-a-model.md) - [Syntex accessibility mode](accessibility-mode.md) |
| contentunderstanding | Explanation Templates | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/explanation-templates.md | description: Learn more about how to use and save explanation templates in Micro # Use explanation templates in Microsoft Syntex +<sup>**Applies to:**   ✓ 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: For example, instead of manually adding all the variations for *date*, you can u The explanation library includes commonly used *phrase list* explanations, including: -- Date: Calendar dates, all formats. Includes text and numbers (for example, "Dec 9, 2020").-- Date (numeric): Calendar dates, all formats. Includes numbers (for example, 1-11-2020).+- 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%. |
| contentunderstanding | Explanation Types Overview | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/explanation-types-overview.md | description: Learn more about phrase list, regular expression, and proximity exp # Explanation types in Microsoft Syntex -Explanations are used to help to define the information you want to label and extract in your document understanding 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. +<sup>**Applies to:**   ✓ 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.  |
| contentunderstanding | Form Processing Overview | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/form-processing-overview.md | Title: Form processing overview in Microsoft Syntex + 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 Build to create form processing models in Microsoft Syntex. +description: Learn how to use AI Builder to create structured document processing models in Microsoft Syntex. -# Form processing overview in Microsoft Syntex +# Overview of structured document processing in Microsoft Syntex - </br> +> [!NOTE] +> *Structured document processing* was known as *form processing* in previous releases. -Microsoft Syntex uses Microsoft Power Apps [AI Builder](/ai-builder/overview) form processing to create models within SharePoint document libraries. +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. -You can use AI Builder form processing to create AI 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. +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. +<! +  +> +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, form processing automates this process. +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]-> See the [Syntex adoption: Get started guide](./adoption-getstarted.md) for more information about form processing scenario examples. --For example, you can create a form processing model that identifies all purchase order documents that are uploaded to the document library. From each purchase order, you can then extract and display specific data that is important to you, such as *PO Number*, *Date*, or *Total Cost*. --</br> --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. AI Builder 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. +> 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). -After you train and publish your model, your model creates a [Power Automate flow](/power-automate/getting-started). The flow runs when a file is uploaded to the SharePoint document library and will extract data that has been identified in the model. The extracted data will display in columns in your model's document library view. +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. -An Office 365 admin needs to [enable form processing](./set-up-content-understanding.md) for the SharePoint document library for users to be able to [create a form processing model](create-a-form-processing-model.md) in it. You can select the sites during setup, or after setup in your management settings. + -## File limitations +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. -When using form processing models, make sure to note the [requirements and limitations for file usage](/ai-builder/form-processing-model-requirements). +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. -## Supported languages + -Form processing supports documents in more than 73 languages. For the list of languages, see [Form processing language support](/power-platform-release-plan/2021wave2/ai-builder/form-processing-new-language-support). +If you need it enabled on your document library, contact your Microsoft 365 admin. -## Multi-Geo environments +## Requirements -When setting up Syntex in a [Microsoft 365 Multi-Geo environment](../enterprise/microsoft-365-multi-geo.md), you can only configure it to use form processing in the central location. If you want to use form processing in a satellite location, contact Microsoft support. +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). -## Custom environments +## See also -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](set-up-content-understanding.md#requirements). +[Compare custom models](difference-between-document-understanding-and-form-processing-model.md) +[Train a structured document processing model](create-a-form-processing-model.md) -## See also - [Power Automate documentation](/power-automate/) -[Create a form processing model](create-a-form-processing-model.md) --[Document understanding overview](document-understanding-overview.md) - [Training: Improve business performance with AI Builder](/training/paths/improve-business-performance-ai-builder/?source=learn) |
| contentunderstanding | Freeform Document Processing Overview | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/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. +<! +  +> +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. ++ ++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. ++ ++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) |
| contentunderstanding | Image Tagging | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/image-tagging.md | |
| contentunderstanding | Import Term Set Skos | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/import-term-set-skos.md | 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](index.md) license. +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. On successful import of the file, a success message will be displayed, and the t [Introduction to managed metadata](/sharepoint/managed-metadata) -[Document understanding overview](document-understanding-overview.md) +[Unstructured document processing overview](document-understanding-overview.md) [Import term sets (site level)](https://support.microsoft.com/office/168fbc86-7fce-4288-9a1f-b83fc3921c18) |
| contentunderstanding | Index | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/index.md | - Title: Introduction to Microsoft Syntex-------- intro-overview-- intro-get-started-- - - enabler-strategic - - m365initiative-syntex -description: Learn how to find resources for Microsoft Syntex. ---# Introduction to Microsoft Syntex --Microsoft Syntex is a Microsoft 365 service that helps organizations to: --- Use advanced AI and machine teaching and learning to amplify human experiences-- Automate content processing-- Transform content into knowledge--The resources on this page are designed to get you started with learning about and using Syntex in your organization. --</br> --> [!VIDEO https://www.microsoft.com/videoplayer/embed/RE4GJXS] --</br> --## Get started --The resources in this section help you learn more about the methods of data classification and extraction used by Syntex. There are two custom model typesΓÇö[document understanding](document-understanding-overview.md) and [form processing](form-processing-overview.md)ΓÇöand a [prebuilt](prebuilt-overview.md) model type. --> [!NOTE] -> You can get started with Syntex without buying licenses by [creating a content center from the SharePoint admin center](create-a-content-center.md). Unlicensed users can create document understanding models but can't apply them to a document library. --| If you're looking for this information: | Go to this resource: | -|:--|:--| -|Learn more about document understanding|[Document understanding overview](./document-understanding-overview.md)| -|Learn more about form processing|[Form processing overview](./form-processing-overview.md)| -|Understand the differences between the two methods|[Difference between document understanding and form processing models](./difference-between-document-understanding-and-form-processing-model.md)| -|See resources in the Microsoft Tech Community Resource Center|[Syntex - Content services in Microsoft 365](https://techcommunity.microsoft.com/t5/sharepoint-syntex/bg-p/SharePointSyntex)| -|Syntex FAQ on the Microsoft Tech Community Resource Center |[Syntex - FAQ](https://resources.techcommunity.microsoft.com/sharepoint-syntex/faq/)| -|How to get Syntex |[Syntex product page](https://www.microsoft.com/microsoft-365/enterprise/sharepoint-syntex)| -|Learn to use Syntex |[Syntex learning path](/training/paths/syntex-get-started)| --## Adoption --Learn more about how to use and implement Syntex in your organization to help you solve your business problems. --| If you're looking for this information: | Go to this resource: | -|:--|:--| -|Learn how to start planning to use Syntex |[Syntex adoption: get started](./adoption-getstarted.md)| -|See example scenarios to give you ideas about how you can use Syntex in your organization |[Scenarios and use cases for Syntex](./adoption-scenarios.md)| -|Set up and run a trial pilot program for Syntex |[Run a trial](./trial-syntex.md)| -|Learn how to use Syntex to automate document processes |[Manage contracts using a Microsoft 365 solution](./solution-manage-contracts-in-microsoft-365.md)| -|Try out a customizable SharePoint site template to help manage contracts |[Use the Contracts Management site template](./use-contracts-management-site.md)| -|Try out an instructional Content Center site template to learn more about models |[Use the Content Center site template](./use-content-center-site.md)| --## Set up Syntex --The resources in this section help your admin in your organization to set up and configure Microsoft Syntex in your Microsoft 365 environment. --| If you're looking for this information: | Go to this resource: | -|:--|:--| -|Set up and configure Syntex|[Set up Syntex](./set-up-content-understanding.md)| -|Learn about licensing for Syntex|[Licensing for Syntex](./syntex-licensing.md)| -|Learn about image tagging and how to disable|[Image tagging in Syntex](./image-tagging.md)| -|Use PowerShell to manage Syntex|[Manage Syntex with PowerShell](./powershell-syntex-intro.md)| --## Models --The resources in this section help your users learn how to create and configure document understanding and form processing models. --| If you're looking for this information: | Go to this resource: | -|:--|:--| -|Learn how to work with models|[Create a content center](./create-a-content-center.md)<br><br>[Create a classifier](./create-a-classifier.md)<br><br>[Duplicate a model](./duplicate-a-model.md)<br><br>[Rename a model](./rename-a-model.md)<br><br>[Create an extractor](./create-an-extractor.md)<br><br>[Rename an extractor](./rename-an-extractor.md)<br><br>[Create a form processing model](./create-a-form-processing-model.md)<br><br>[Explanation types](./explanation-types-overview.md)<br><br>[Use explanation templates](./explanation-templates.md)<br><br>[Apply a document understanding model](./apply-a-model.md)<br><br>[Learn about document understanding models through the sample model](./learn-about-document-understanding-models-through-the-sample-model.md)<br><br>| -|Apply a retention label to your model|[Apply a retention label to a document understanding model](./apply-a-retention-label-to-a-model.md)| -|Apply a sensitivity label to your model|[Apply a sensitivity label to a document understanding model](./apply-a-sensitivity-label-to-a-model.md)| -|Use prebuilt models to extract info from documents |[Use a prebuilt model to extract info from invoices or receipts](./prebuilt-models.md)| -|Create and train models locally on a SharePoint site |[Create a model on a local SharePoint site](./create-local-model.md)| -|Use trained models in other content centers |[Publish and discover document understanding models](./model-discovery.md)| -|Perform metadata-based queries on document libraries|[Search for metadata in document libraries](./metadata-search.md)| -|Use Managed Metadata services term store taxonomy when creating an extractor|[Leverage term store taxonomy when creating an extractor](./leverage-term-store-taxonomy.md)| -|Learn how to see data about your models|[Model usage analytics](./model-usage-analytics.md)| -|Learn how to use accessibility mode when training a model|[Syntex accessibility mode](./accessibility-mode.md)| --## Premium services --A Syntex license gives your users premium content services that give you additional functionality in your Microsoft 365 environment. The resources in this section give you more details about these features and how to use them. --| If you're looking for this information: | Go to this resource: | -|:--|:--| -|Learn about importing a data set using Simple Knowledge Organization System based format|[Import a term set using a SKOS-based format](./import-term-set-skos.md)<br><br>[SKOS format reference for SharePoint taxonomy](./skos-format-reference.md)<br><br>| -|Learn how to make content types more consistently available to SharePoint libraries and lists|[Push content types to a hub](./push-content-type-to-hub.md)| -|Learn about the term store reports that are available to you|[Term store reports](./term-store-analytics.md)| --## Extensibility --Use REST APIs to create a document understanding model, apply or remove the model to one or more libraries, and obtain or update information about the model. --| If you're looking for this information: | Go to this resource: | -|:--|:--| -|Use REST APIs for document understanding models|[Syntex document understanding model REST API](/sharepoint/dev/apis/syntex/syntex-model-rest-api)| |
| contentunderstanding | Learn About Document Understanding Models Through The Sample Model | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/learn-about-document-understanding-models-through-the-sample-model.md | Title: Import a sample document understanding model for Microsoft Syntex + Title: Import a sample model for Microsoft Syntex -description: Learn about document understanding models through the sample model. +description: Learn about unstructured document processing models in Microsoft Syntex by using the sample model. -# Import a sample document understanding model for Microsoft Syntex +# Import a sample model for Microsoft Syntex -Microsoft Syntex provides you with a sample 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. +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.</br> -2. On the **Models** page, select **Import sample model**.</br> +1. From the content center, select **Models** to see your models list. -  </br> +2. On the **Models** page, select **Import sample model**. -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 do this from the models list in the content center. </br> +  - </br> +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. -You can not only look through analyze the sample model to get a better understanding of how the model is constructed, but as a working model can go further and do things such as: +  ++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*. -- Add a 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 document understanding models. The samples in this repository contain both the document understanding 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. +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-[Create a classifier](create-a-classifier.md) -[Create an extractor](create-an-extractor.md) +[Overview of unstructured document processing](document-understanding-overview.md) -[Document Understanding overview](document-understanding-overview.md) +[Create a classifier](create-a-classifier.md) -[Create a form processing model](create-a-form-processing-model.md) +[Create an extractor](create-an-extractor.md) |
| contentunderstanding | Leverage Term Store Taxonomy | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/leverage-term-store-taxonomy.md | -description: Use term store taxonomy when creating an extractor in your document understanding model in Microsoft Syntex. +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:**   ✓ Unstructured document processing </sup> ++<! </br> > [!VIDEO https://www.microsoft.com/videoplayer/embed/RE4GpJJ] </br>+> -When you create an extractor in your document understanding 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. +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 example below, while training the model we see that one sample document contains the outdated term of *Design*. +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*. </br> -## Use a Managed metadata column in your extractor +## 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*. After applying your model to the document library, when documents are uploaded t > 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) ++[Introduction to managed metadata](/sharepoint/managed-metadata#terms) [Create an extractor](create-an-extractor.md) |
| contentunderstanding | Metadata Search | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/metadata-search.md | |
| contentunderstanding | Model Discovery | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/model-discovery.md | Title: Publish and discover models in Microsoft Syntex + Title: Share an enterprise model in Microsoft Syntex audience: admin -+ search.appverid: - enabler-strategic ms.localizationpriority: medium description: Learn how to make trained models available to other users and how to apply other trained models in Microsoft Syntex. -# Publish and discover models in Microsoft Syntex +# Share an enterprise model in Microsoft Syntex -You can make your trained document understanding models available for others to view and use directly from the SharePoint document library. +<sup>**Applies to:**   ✓ All custom models   |   ✓ All prebuilt models</sup> -You can also find and evaluate trained models in other content centers that were created by others in your organization. Select the model that is most useful for classifying your files or extracting specific information from them. +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). -> [!NOTE] -> This feature is not yet available for form processing models. --## Make your model discoverable to others +## Share your model with others To make your trained model available for others to use: To make your trained model available for others to use: 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 are an administrator. +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 are a SharePoint administrator, you will see this view. + If you're a SharePoint administrator, you'll see this view.  - **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. Click in 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. + - **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 are *not* a SharePoint administrator, you will see this view. + If you *aren't* a SharePoint administrator, you'll see this view.  To make your trained model available for others to use: 4. Select the sites where you want the model to be available for other users to apply, and then select **Save**. -## Discover other trained models --To find trained models that might be suitable for your content: --1. In the document library for your model, select **Automate** > **View document understanding models**. --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. --  -- - 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. --  --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**. --  --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**. --  --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**. --  --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. --  --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 --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**. -- ## See also -[Apply a document understanding model](apply-a-model.md) --[Document understanding overview](document-understanding-overview.md) +[Discover other trained models](discover-other-trained-models.md) |
| contentunderstanding | Model Types Overview | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/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 ++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. ++Syntex uses [custom models](#custom-models) and [prebuilt models](#prebuilt-models). ++ ++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). ++<! +</br> ++> [!VIDEO https://www.microsoft.com/videoplayer/embed/RE4GJXS] ++</br> +> ++## 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). ++### 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). ++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. ++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). ++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) |
| contentunderstanding | Model Usage Analytics | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/model-usage-analytics.md | -description: Learn how to find more information about how your document understanding and form processing models are performing. +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:**   ✓ All custom models   |   ✓ All prebuilt models</sup> ++<! </br> > [!VIDEO https://www.microsoft.com/videoplayer/embed/RE4GnhX] </br>+> --Your Microsoft Syntex content center 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 <b>How your models are performing in the last 30 days</b> section of the content center includes a 30 day roll-up of usage analytics data provided in the following charts and lists: +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 -  </br> +  ### Roll up of model usage data in the default content center In Syntex, the default content center is created during setup. More content cent Regarding model usage analytics, note that: -- Your default content center will show model usage analytics for all content centers and models in your org, 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. +- 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 -  </br> +  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 file ## Classification by library -  </br> +  -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. +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 will show usage analytics for the models created through the content center. +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: - 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. ---## See also -[Create a classifier](create-a-classifier.md) --[Create an extractor](create-an-extractor.md) --[Document Understanding overview](document-understanding-overview.md) --[Create a form processing model](create-a-form-processing-model.md) |
| contentunderstanding | Powershell Syntex Explanations | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/powershell-syntex-explanations.md | Title: Work with document understanding model explanations in PowerShell + 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 document understanding model explanations in PowerShell. +description: Learn about work with Microsoft Syntex model explanations in PowerShell. -# Work with document understanding model explanations in PowerShell +# Work with explanations for unstructured document processing models in PowerShell ++<sup>**Applies to:**   ✓ 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. |
| contentunderstanding | Powershell Syntex Import Export | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/powershell-syntex-import-export.md | Title: Export and import document understanding models with PowerShell + 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 document understanding models with PowerShell in Microsoft Syntex. +description: Learn about how to export and import models with PowerShell in Microsoft Syntex. -# Export and import document understanding models with PowerShell +# Export and import unstructured document processing models with PowerShell ++<sup>**Applies to:**   ✓ 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 ce ## Export all models in a content center -To export all models in a content center into a single PnP template, use the following [PnP PowerShell](https://pnp.github.io/powershell/) cmdlets: +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 models from a content center into a PnP template, use the following [PnP PowerShell](https://pnp.github.io/powershell/) cmdlets: +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" The extract.json defines which models you want to export, allowing to specify mo } ``` -If you do not include the property "includeTrainingData", the default behavior is to include. +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-Document understanding 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. ++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: |
| contentunderstanding | Powershell Syntex Intro | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/powershell-syntex-intro.md | Title: Manage Microsoft Syntex by using PowerShell -+ audience: admin -+ - enabler-strategic - m365initiative-syntex For these scenarios, the Syntex cmdlets in the PnP PowerShell module can be used Select from the following scenarios to learn how to use PowerShell to manage Syntex: -- [**Import and Export Models**](powershell-syntex-import-export.md)+- [**Export and import models**](powershell-syntex-import-export.md) - Start here if you want to learn how to export document understanding models from a content center, and import to another content center or tenant. + 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 document understanding models to document libraries. + 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 document understanding processing on a document library. + 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 custom document understanding explanation templates using PowerShell. + Start here if want to learn how to create a custom explanation template for an unstructured document processing model using PowerShell. |
| contentunderstanding | Powershell Syntex Processing | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/powershell-syntex-processing.md | Title: Use PowerShell to request processing by a document understanding model + 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 document understanding model. +description: Learn how to use PowerShell to request processing by a Microsoft Syntex custom model. -# Use PowerShell to request processing by a document understanding model +# Use PowerShell to request processing by a custom model ++<sup>**Applies to:**   ✓ 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. -Document understanding models will process newly uploaded files to a library. It is also possible to manually request processing in the UI. However there might be scenarios where it is more efficient to trigger processing through PowerShell. +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 have not been previously classified +## Request processing of all items that haven't been previously classified -You can request processing for all items in the library that have not previously been classified by using this command: +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. See [Request-PnPSyntexClassifyAndExtract](https://pnp.github.io/powershell/cmdlets/Request-PnPSyntexClassifyAndExtract.html) for more details. +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 might be useful if you have updated a model or added another model to the 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 |
| contentunderstanding | Powershell Syntex Publishing | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/powershell-syntex-publishing.md | Title: Publish document understanding models with PowerShell + Title: Publish custom models with PowerShell -+ audience: admin -+ - enabler-strategic - m365initiative-syntex search.appverid: MET150 ms.localizationpriority: medium-description: "Learn how to publish a Microsoft Syntex document understanding models with PowerShell." +description: Learn how to publish Microsoft Syntex custom models by using PowerShell. -# Publish document understanding models with PowerShell +# Publish custom models with PowerShell ++<sup>**Applies to:**   ✓ 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. |
| contentunderstanding | Prebuilt Model Invoice | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/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**. ++  +++2. On the **View options for classification and extraction** page, in the **Use a trained model** section, select **Invoices**. ++  ++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**. ++  ++2. On the **Files to analyze the model** page, select **Add** to find the file you want to use. ++  ++3. On the **Add a file from the training files library** page, select the file, and then select **Add**. ++  ++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. ++  ++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. ++  ++- To select an extractor from the **Extractors** panel, select the checkbox to the right of the entity name. ++  ++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. ++  ++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**. ++  ++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**. ++  ++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). ++<! +> |
| contentunderstanding | Prebuilt Model Receipt | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/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**. ++  ++2. On the **Files to analyze the model** page, select **Add** to find the file you want to use. ++  ++3. On the **Add a file from the training files library** page, select the file, and then select **Add**. ++  ++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. ++  ++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. ++  ++- To select an extractor from the **Extractors** panel, select the checkbox to the right of the entity name. ++  ++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. ++  ++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**. ++  ++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**. ++  ++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). ++ |
| contentunderstanding | Prebuilt Overview | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/prebuilt-overview.md | Title: Prebuilt models overview in Microsoft Syntex + Title: Overview of prebuilt models in Microsoft Syntex audience: admin -ms.customer: intro-overview -++ search.appverid: - enabler-strategic ms.localizationpriority: medium description: Learn about prebuilt models in Microsoft Syntex. -# Prebuilt models overview in Microsoft Syntex +# Overview of prebuilt models in Microsoft Syntex -In addition to [document understanding models](document-understanding-overview.md) and [form processing models](form-processing-overview.md), Microsoft Syntex provides prebuilt models to automate the extraction of information. +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 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. +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 document understanding 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. +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. -## Requirements --- Supported file formats: JPEG, PNG, BMP, TIFF, and PDF (text-embedded or scanned).--- Supported languages: only English language invoices from the United States are currently supported. English sales receipts from Australia, Canada, United States, Great Britain, and India are supported.--- Text-embedded PDFs are best to eliminate the possibility of error in character extraction and location.--- For PDF and TIFF, up to 2,000 pages can be processed.--- The file size must be less than 50 MB.+## Available prebuilt models -- Image dimensions must be between 50 x 50 pixels and 10,000 x 10,000 pixels.+Currently, there are two prebuilt models available: [invoices](prebuilt-model-invoice.md) and [receipts](prebuilt-model-receipt.md). -- PDF dimensions are up to 17 x 17 inches, corresponding to Legal or A3 paper size, or smaller.+- 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 total size of the training data is 500 pages or less.+- 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. -### File limitations +Additional prebuilt models will be available in future releases. -Note the following differences about Microsoft Office text-based files and OCR-scanned files (PDF, image, or TIFF): --- Office files: Truncated at 64,000 characters (when run against files in a document library).--- OCR-scanned files: There's a 20-page limit. --## Model considerations +## Requirements -- If two or more prebuilt 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.+For information about requirements to consider when choosing this model, see [Requirements and limitations for models in Microsoft Syntex](requirements-and-limitations.md). -- If a prebuilt model is applied to a library that has a custom form processing model, the file is classified using the prebuilt model and any detected extractors for that model. If there are any empty columns that match the form processing model, the columns will be populated using those extracted values.+## See also -- Applying more than one custom form processing model to a library is not supported.+[Use a prebuilt model to extract information from invoices](prebuilt-model-invoice.md) -## See also +[Use a prebuilt model to extract information from receipts](prebuilt-model-receipt.md) -[Use a prebuilt model to extract information from invoices or receipts](prebuilt-models.md) |
| contentunderstanding | Push Content Type To Hub | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/push-content-type-to-hub.md | ms.localizationpriority: high </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](index.md) license. +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 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. +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. + -## See also |
| contentunderstanding | Rename A Model | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/rename-a-model.md | -description: Learn how and why to rename a document understanding model in Microsoft Syntex. +description: Learn how and why to rename a model in Microsoft Syntex. # Rename a model in Microsoft Syntex -At some point, you might want to rename a document understanding 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. +<sup>**Applies to:**   ✓ All custom models   |   ✓ 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 document understanding model if it has not been applied to a document library. +> 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 document understanding model. +Follow these steps to rename a model. 1. From the content center, select **Models** to see your models list. Follow these steps to rename a document understanding model. 5. Select **Rename**. ## See also-[Create a classifier](create-a-classifier.md) --[Create an extractor](create-an-extractor.md) --[Rename an extractor](rename-an-extractor.md) --[Document Understanding overview](document-understanding-overview.md) -[Explanation types](explanation-types-overview.md) +[Delete a model](delete-a-model.md) -[Apply a model](apply-a-model.md) |
| contentunderstanding | Rename An Extractor | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/rename-an-extractor.md | description: Learn how and why to rename an extractor in Microsoft Syntex. # Rename an extractor in Microsoft Syntex +<sup>**Applies to:**   ✓ 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. Follow these steps to rename an entity extractor. 5. Select **Rename**. ## See also-[Create an extractor](create-an-extractor.md) --[Create a classifier](create-a-classifier.md) -[Rename a model](rename-a-model.md) --[Explanation types](explanation-types-overview.md) --[Leverage term store taxonomy when creating an extractor](leverage-term-store-taxonomy.md) +[Create an extractor](create-an-extractor.md) -[Document Understanding overview](document-understanding-overview.md) -[Apply a model](apply-a-model.md) |
| contentunderstanding | Requirements And Limitations | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/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:**   ✓ All custom models   |   ✓ 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 | +| - | - | +|  | **Supported languages** <br>This model supports all of the Latin-based languages, including: English, French, German, Italian, and Spanish. | +|  | **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. | +|  | **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. | +|  | **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 | +| - | - | +|  | **Supported file types** <br>This model supports the following file types: see [file type requirements](/ai-builder/form-processing-model-requirements#requirements). | +|  | **Supported languages** <br>This model supports the following language: English. | +|  | **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). | +|  | **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). | +|  | **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. | +|  | **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). | +|  | **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 | +| - | - | +|  | **Supported file types** <br>This model supports the following file types: see [file type requirements](/ai-builder/form-processing-model-requirements#requirements). | +|  | **Supported languages** <br>This model supports 73 languages: see [supported languages](/ai-builder/form-processing-model-requirements#languages-supported). | +|  | **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). | +|  | **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). | +|  | **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. | +|  | **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). | +|  | **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 | +| - | - | +|  | **Supported file types** <br>This model supports the following file types: .bmp, .jpeg, .pdf, .png, and .tiff. | +|  | **Supported languages** <br>This model supports only English language invoices from the United States. | +|  | **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.| +|  | **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. | +|  | **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 | +| - | - | +|  | **Supported file types** <br>This model supports the following file types: .bmp, .jpeg, .pdf, .png, and .tiff. | +|  | **Supported languages** <br>This model supports English sales receipts from Australia, Canada, Great Britain, India, and the United States. | +|  | **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.| +|  | **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. | +|  | **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. | |
| contentunderstanding | Set Up Content Understanding | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/set-up-content-understanding.md | 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](index.md). +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 form processing? All of them, some, or select sites?+- 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 form processing - all of them, some, or selected sites+- 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 As an admin, you can also make changes to your selected settings anytime after s 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 form processing models. +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/contentunderstan ### Licensing -To use Syntex, your organization must have a subscription to Syntex, and each user must have a licenses assigned. yntex licenses include the following apps, which must all be assigned: +To use Syntex, your organization must have a subscription to Syntex, and each user must have a licenses assigned. Syntex licenses include the following apps, which must all be assigned: -- Microsoft Syntex-- Microsoft Syntex - SPO type-- Common Data Service for Microsoft Syntex+- Syntex +- Syntex - SPO type +- Common Data Service for Syntex -To use form processing, you also need AI Builder credits. For each licensed user of Syntex, an allocation of AI Builder credits is provided each month. +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 [Syntex licensing](syntex-licensing.md). +For details about Syntex licensing, see [Microsoft Syntex licensing](syntex-licensing.md) ## To set up Syntex For details about Syntex licensing, see [Syntex licensing](syntex-licensing.md). > [!div class="mx-imgBorder"] > </br> -4. On the **Configure Form Processing** page, you can choose if you want to let users be able to create form processing models in specific SharePoint document libraries. A menu option will be available in the document library ribbon to **Create a form processing model** in SharePoint document libraries in which it is enabled. +4. On the **Configure Form Processing** page, you can choose if you want to let users be able to create document processing models in specific SharePoint document libraries. A menu option will be available in the document library ribbon to **Create a form processing model** in SharePoint document libraries in which it is enabled. For **Which SharePoint libraries should show option to create a form processing model**, you can select:</br> - **Libraries in all SharePoint sites** to make it available to all SharePoint libraries in your organization.</br> For details about Syntex licensing, see [Syntex licensing](syntex-licensing.md). - **No SharePoint libraries** if you don't want to make it available to any sites (you can change this after setup). > [!div class="mx-imgBorder"]- >  + >  > [!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 document understanding models to a library. + > 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 have multiple Power Platform environments configured, you can choose which one you want to use with for form processing. (This option will not appear if you only have one environment.) + 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. For details about Syntex licensing, see [Syntex licensing](syntex-licensing.md). Click **Next**. -5. On the **Create Content Center** page, you can create a SharePoint content center site where your users can create and manage document understanding models. If you previously created a content center from the SharePoint admin center, that information will display here and you can just select **Next**. +5. On the **Create 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 **Site name**, type the name you want to give your content center site. To assign licenses: 3. Choose **Apps** from the drop-down menu. -4. Select **Show apps for SharePoint Syntex**. Under **Apps**, make sure **Common Data Service for SharePoint Syntex**, **SharePoint Syntex**, and **SharePoint Syntex - SPO type** are all selected. +4. Select **Show apps for Syntex**. Under **Apps**, make sure **Common Data Service for Syntex**, **Syntex**, and **Syntex - SPO type** are all selected. > [!div class="mx-imgBorder"] >  To assign licenses: ## See also -[Overview of the form processing model](/ai-builder/form-processing-model-overview) --[Step-by-Step: How to Build a Document Understanding Model (video)](https://www.youtube.com/watch?v=DymSHObD-bg) +[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) |
| contentunderstanding | Skos Format Reference | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/skos-format-reference.md | -description: Learn about SKOS format reference for SharePoint taxonomy. +description: Learn about the SKOS format reference for SharePoint taxonomy. # SKOS format reference for SharePoint taxonomy |
| contentunderstanding | Solution Manage Contracts In Microsoft 365 | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/solution-manage-contracts-in-microsoft-365.md | -description: Learn how to manage contracts using a Microsoft 365 solution of Microsoft Syntex, SharePoint Lists, Microsoft Teams, and Power Automate. +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 contract management solution guidance includes four components of Microsoft  -1. Documents are uploaded to a SharePoint document library. A Syntex document understanding 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. +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*. This solution relies on the following functionality, all available as part of a 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 document understanding and form processing models to classify documents, extract text, and label your documents for quick and easy knowledge management. +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 |
| contentunderstanding | Solution Manage Contracts Step1 | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/solution-manage-contracts-step1.md | description: Learn how to use Microsoft Syntex to identify contract files and ex # 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](index.md) to create a document understanding model and applying it to a document library. +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 -[Document understanding](document-understanding-overview.md) uses artificial intelligence (AI) models to automate classification of files and extraction of information. Document understanding 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](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. -Document understanding 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. +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 document understanding 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. +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 document understanding 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. +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.  Document understanding models use Optical Character Recognition (OCR) technology ## 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%20samples/Contracts%20Management). The examples in this repository contain both the document understanding model files and the files used to train the model. +> 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%20samples/Contracts%20Management). 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**, and then **Create a model**. +1. From the content center, select **New** > **Model** > **Teaching method**. -2. On the **New document understanding model** pane, in the **Name** field, type the name of the model. For this contract management solution, you can name the model *Contract*. +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> |
| contentunderstanding | Solution Manage Contracts Step2 | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/solution-manage-contracts-step2.md | When your organization sets up a contracts management solution, you need a centr - **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 Syntex document understanding model to in the previous section. +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. |
| contentunderstanding | Solution Manage Contracts Step3 | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/solution-manage-contracts-step3.md | The following diagram shows the Power Automate flow for the contract management ## Prepare your contract for review -When a contract is identified and classified by your Syntex document understanding model, the Power Automate flow will first change the status to **In 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**.  |
| contentunderstanding | Syntex Licensing | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/syntex-licensing.md | 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 document understanding or form processing 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 will not be changed. +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. To use Microsoft Syntex, you must have a license for each Syntex user. If you re The following tasks require a [Syntex license](https://www.microsoft.com/microsoft-365/enterprise/sharepoint-syntex) for the user performing them: -- Applying a document understanding model to a library. (Unlicensed users can be granted access to a content center and can create document understanding models there but can't apply them to a document library.)-- Creating a form processing model via the entry point in a library-- Uploading content to a library where a document understanding or form processing model has been applied-- Running a document understanding model on-demand-- Creating a modern template with content assembly-- Generating a document from a modern template+- 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 document understanding models there but can't apply them to a document 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. ## Cost of training and running models -The cost of training and running document understanding models is included in the cost of a Syntex license. However, form 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. +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.) Having one or more Syntex licenses in your organization enables the following ad - 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) |
| contentunderstanding | Syntex Overview | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/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=""::: +  + :::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=""::: +  + :::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 | +| - | - | - | +|  |  |  | +| 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 | +| - | - | +|  |  | +| 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=""::: +  + :::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=""::: +  + :::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=""::: +  + :::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=""::: +  + :::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=""::: +  + :::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) |
| contentunderstanding | Term Store Analytics | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/term-store-analytics.md | 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](index.md) license. +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**. |
| contentunderstanding | Train Freeform Document Processing Model | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/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. ++ ++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). ++  ++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. ++  ++## Step 4: Use your model ++1. In the document library model view, notice that the fields you selected now display as columns. ++  ++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. ++  ++> [!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**. ++  ++## 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) |
| contentunderstanding | Train Model | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/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 ++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) |
| contentunderstanding | Trial Syntex | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/trial-syntex.md | A test or demo tenant can be used as a ΓÇ£dry runΓÇ¥ to walk through the activat 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 either the form processing or document understanding model.+- 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. Based on the outcome of the trial, you can decide whether to proceed to producti 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 form processing 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/). +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 document understanding models won't be automatically deleted. These will remain available for use if you decide to purchase licenses in the future.-- Form processing models will be stored in the Dataverse (previously 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.++- 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 |
| contentunderstanding | Use Content Center Site | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/use-content-center-site.md | Title: Use the Content Center site template for Microsoft Syntex + 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. +description: Learn how to provision and use the content center site template in Microsoft Syntex. -# Use the Content Center site template for 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. +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. - + 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/). +The content center site can be provisioned from the [SharePoint look book service](https://lookbook.microsoft.com/). - + > [!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**. +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**. +2. On the **Content center** page, select **Add to your tenant**.  The Content Center site can be provisioned from the [SharePoint look book servic  -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. +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. +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 pre-populated pages that walk you through the steps to begin using Syntex in your organization. +The content center site includes prepopulated pages that walk you through the steps to begin using Syntex in your organization. ### Get started with Syntex Learn about three types of models, and see how you can use them to resolve busin ### Take an interactive tour to create a model -See how to build a document understanding model in the models library, and then enable a pretrained sample model. +See how to build a model in the models library, and then enable a pretrained sample model. ### Syntex in six simple steps |
| contentunderstanding | Use Contracts Management Site | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/contentunderstanding/use-contracts-management-site.md | Title: Use the Contracts Management site template for Microsoft Syntex + 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. +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 +# Use the contracts management site template for Microsoft Syntex -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. +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 - + -The Contract 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 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: There is a separate view in the library where you can track other metadata such ## Provision the site -The Contracts Management site can be provisioned from the [SharePoint look book service](https://lookbook.microsoft.com/). +The contracts management site can be provisioned from the [SharePoint look book service](https://lookbook.microsoft.com/). - + > [!NOTE]-> You must be a global administrator or SharePoint administrator in Microsoft 365 to provision the site. You also must have a Syntex license to add this site template to your organization. +> 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**. +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**. +2. On the **Contracts management** page, select **Add to your tenant**. -  +  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. -  +  -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. +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. +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. +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.+- 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 following elements of your site to fit the need of your organizati ### 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: +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). You have control of the site navigation for the Contracts Management site. Use t ### Add other workflows -The Contracts Management site contains the components you need to get started, but you can also include additional components, such as: +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). The Contracts Management site contains the components you need to get started, b ## 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. +[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: +Key success factors to managing the contracts management site: -- Celebrate the launch of your 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.+- Review the contracts management site as needed to ensure content is fresh and still relevant. |
| enterprise | O365 Data Locations | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/o365-data-locations.md | New Microsoft 365 tenants are defaulted to Geo based on the country of the billi | Viva Insights - Manager/Leader AAD org data only | United States | | Viva Insights - Manager/Leader with 3rd party HR data only | United States | | Viva Insights - Advanced | United States |+| Viva Goals | United States | </p></details> ## Uruguay |
| lighthouse | M365 Lighthouse Block User Signin | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/lighthouse/m365-lighthouse-block-user-signin.md | f1.keywords: NOCSH -+ audience: Admin |
| lighthouse | M365 Lighthouse Change Cloud Pc Account Type | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/lighthouse/m365-lighthouse-change-cloud-pc-account-type.md | f1.keywords: NOCSH -+ audience: Admin |
| lighthouse | M365 Lighthouse Compare Compliance Policies | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/lighthouse/m365-lighthouse-compare-compliance-policies.md | f1.keywords: NOCSH -+ audience: Admin |
| lighthouse | M365 Lighthouse Configure Portal Security | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/lighthouse/m365-lighthouse-configure-portal-security.md | f1.keywords: CSH -+ audience: Admin |
| lighthouse | M365 Lighthouse Deploy Baselines | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/lighthouse/m365-lighthouse-deploy-baselines.md | f1.keywords: CSH -+ audience: Admin |
| lighthouse | M365 Lighthouse Deploy Standard Tenant Configurations Overview | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/lighthouse/m365-lighthouse-deploy-standard-tenant-configurations-overview.md | f1.keywords: CSH -+ audience: Admin |
| lighthouse | M365 Lighthouse Device Compliance Page Overview | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/lighthouse/m365-lighthouse-device-compliance-page-overview.md | f1.keywords: NOCSH -+ audience: Admin |
| lighthouse | M365 Lighthouse Device Security Overview | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/lighthouse/m365-lighthouse-device-security-overview.md | f1.keywords: NOCSH -+ audience: Admin |
| lighthouse | M365 Lighthouse Get Help And Support | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/lighthouse/m365-lighthouse-get-help-and-support.md | f1.keywords: CSH -+ audience: Admin |
| lighthouse | M365 Lighthouse Known Issues | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/lighthouse/m365-lighthouse-known-issues.md | f1.keywords: NOCSH -+ audience: Admin |
| lighthouse | M365 Lighthouse Manage Inactive Users | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/lighthouse/m365-lighthouse-manage-inactive-users.md | f1.keywords: NOCSH -+ audience: Admin |
| lighthouse | M365 Lighthouse Manage Mfa | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/lighthouse/m365-lighthouse-manage-mfa.md | f1.keywords: NOCSH -+ audience: Admin |
| lighthouse | M365 Lighthouse Manage Sspr | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/lighthouse/m365-lighthouse-manage-sspr.md | f1.keywords: NOCSH -+ audience: Admin |
| lighthouse | M365 Lighthouse Manage Tenant List | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/lighthouse/m365-lighthouse-manage-tenant-list.md | f1.keywords: NOCSH -+ audience: Admin |
| lighthouse | M365 Lighthouse Mitigate Threats | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/lighthouse/m365-lighthouse-mitigate-threats.md | f1.keywords: NOCSH -+ audience: Admin |
| lighthouse | M365 Lighthouse Overview Of Permissions | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/lighthouse/m365-lighthouse-overview-of-permissions.md | f1.keywords: CSH -+ audience: Admin |
| lighthouse | M365 Lighthouse Overview | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/lighthouse/m365-lighthouse-overview.md | f1.keywords: CSH -+ audience: Admin |
| lighthouse | M365 Lighthouse Quarantine Messages Overview | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/lighthouse/m365-lighthouse-quarantine-messages-overview.md | f1.keywords: CSH -+ audience: Admin |
| lighthouse | M365 Lighthouse Reprovision Cloudpc | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/lighthouse/m365-lighthouse-reprovision-cloudpc.md | f1.keywords: NOCSH -+ audience: Admin |
| lighthouse | M365 Lighthouse Requirements | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/lighthouse/m365-lighthouse-requirements.md | f1.keywords: CSH -+ audience: Admin |
| lighthouse | M365 Lighthouse Reset User Password | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/lighthouse/m365-lighthouse-reset-user-password.md | f1.keywords: NOCSH -+ audience: Admin |
| lighthouse | M365 Lighthouse Review Audit Logs | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/lighthouse/m365-lighthouse-review-audit-logs.md | f1.keywords: CSH -+ audience: Admin |
| lighthouse | M365 Lighthouse Search For Users | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/lighthouse/m365-lighthouse-search-for-users.md | f1.keywords: NOCSH -+ audience: Admin |
| lighthouse | M365 Lighthouse Sign Up | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/lighthouse/m365-lighthouse-sign-up.md | f1.keywords: CSH -+ audience: Admin |
| lighthouse | M365 Lighthouse Tenants Page Overview | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/lighthouse/m365-lighthouse-tenants-page-overview.md | f1.keywords: NOCSH -+ audience: Admin |
| lighthouse | M365 Lighthouse Threat Management Page Overview | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/lighthouse/m365-lighthouse-threat-management-page-overview.md | f1.keywords: NOCSH -+ audience: Admin |
| lighthouse | M365 Lighthouse Troubleshoot | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/lighthouse/m365-lighthouse-troubleshoot.md | f1.keywords: NOCSH -+ audience: Admin |
| lighthouse | M365 Lighthouse Users Page Overview | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/lighthouse/m365-lighthouse-users-page-overview.md | f1.keywords: NOCSH -+ audience: Admin |
| lighthouse | M365 Lighthouse View Failed Network Connections | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/lighthouse/m365-lighthouse-view-failed-network-connections.md | f1.keywords: NOCSH -+ audience: Admin |
| lighthouse | M365 Lighthouse View Manage Risky Users | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/lighthouse/m365-lighthouse-view-manage-risky-users.md | f1.keywords: NOCSH -+ audience: Admin |
| lighthouse | M365 Lighthouse View Service Health | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/lighthouse/m365-lighthouse-view-service-health.md | f1.keywords: NOCSH -+ audience: Admin |
| lighthouse | M365 Lighthouse View Your Roles | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/lighthouse/m365-lighthouse-view-your-roles.md | f1.keywords: NOCSH -+ audience: Admin |
| lighthouse | M365 Lighthouse Whats New | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/lighthouse/m365-lighthouse-whats-new.md | f1.keywords: CSH -+ audience: Admin |
| lighthouse | M365 Lighthouse Win365 Page Overview | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/lighthouse/m365-lighthouse-win365-page-overview.md | f1.keywords: CSH -+ audience: Admin |
| security | Built In Protection | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/defender-endpoint/built-in-protection.md | Built-in protection is a set of default settings that are rolling out to help en | Phase | What happens | |:|:|-| Built-in protection (preview) is rolling out | Customers who have opted to receive preview features are receiving [notification](#what-does-the-notification-look-like) that built-in protection is coming. If it's not already configured, tamper protection will be turned on for customers who have Defender for Endpoint Plan 2 or Microsoft 365 E5. | +| Built-in protection is rolling out | Customers are receiving [notification](#what-does-the-notification-look-like) that built-in protection is coming. If it's not already configured, tamper protection will be turned on for customers who have Defender for Endpoint Plan 2 or Microsoft 365 E5. | | Built-in protection becomes available for your tenant | You'll be [notified](#what-does-the-notification-look-like) that your tenant is about to receive built-in protection and when tamper protection will be turned on (if it's not already configured). | | Built-in protection arrives | Tamper protection will be turned on for your tenant, and will be applied to your organization's Windows devices. You can [opt out](#can-i-opt-out) or [change your built-in protection settings](#can-i-change-built-in-protection-settings). | | After built-in protection has arrived | Whenever new devices are onboarded to Defender for Endpoint, built-in protection settings will be applied to any new devices running Windows. You can always [change your built-in protection settings](#can-i-change-built-in-protection-settings). | |
| security | Experts On Demand | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/defender-endpoint/experts-on-demand.md | search.appverid: met150 > Want to experience Microsoft Defender for Endpoint? [Sign up for a free trial.](https://signup.microsoft.com/create-account/signup?products=7f379fee-c4f9-4278-b0a1-e4c8c2fcdf7e&ru=https://aka.ms/MDEp2OpenTrial?ocid=docs-wdatp-exposedapis-abovefoldlink) > [!NOTE]-> As of August 2022, the Experts on Demand option to **Consult a threat expert** has been rebranded to **Ask Defender Experts**. This documentation is still here to support the legacy Microsoft Threat Experts service, however, if you're interested to explore the service beyond your current license, refer to [Microsoft Defender Experts for Hunting](/microsoft-365/security/defender/defender-experts-for-hunting). Microsoft Defender Experts for Hunting subscription includes [Experts on Demand](/microsoft-365/security/defender/onboarding-defender-experts-for-hunting?view=o365-worldwide#collaborate-with-experts-on-demand). +> As of August 2022, the Experts on Demand option to **Consult a threat expert** has been rebranded to **Ask Defender Experts**. This documentation is still here to support the legacy Microsoft Threat Experts service, however, if you're interested to explore the service beyond your current license, refer to [Microsoft Defender Experts for Hunting](/microsoft-365/security/defender/defender-experts-for-hunting). Microsoft Defender Experts for Hunting subscription includes [Experts on Demand](/microsoft-365/security/defender/onboarding-defender-experts-for-hunting). Customers can engage our security experts directly from within Microsoft 365 Defender portal to get their response. Experts provide insights needed to better understand the complex threats affecting your organization, from alert inquiries, potentially compromised devices, root cause of a suspicious network connection, to more threat intelligence regarding ongoing advanced persistent threat campaigns. With this capability, you can: You can partner with Microsoft Defender Experts who can be engaged directly from > [!NOTE] > > - Alert inquiries related to your organization's customized threat intelligence data are currently not supported. Consult your security operations or incident response team for details.-> - You need to have the **Manage security settings** permission in the Microsoft 365 Defender portal to be able to submit the **Ask Defender Experts** inquiry. +> - You need to have the **[Manage security settings](../defender-endpoint/user-roles.md)** permission in the Microsoft 365 Defender portal to be able to submit the **Ask Defender Experts** inquiry. 1. Navigate to the portal page with the relevant information that you'd like to investigate, for example, the **Incident** page. Ensure that the page for the relevant alert or device is in view before you send an investigation request. |
| security | Microsoft Defender Antivirus Compatibility | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/defender-endpoint/microsoft-defender-antivirus-compatibility.md | For example, [Endpoint detection and response (EDR) in block mode](edr-in-block- In order for Microsoft Defender Antivirus to run in passive mode, endpoints must meet the following requirements: -- Operating system: Windows 10 or newer; Windows Server 2022, Windows Server 2019, or Windows Server, version 1803, or newer-- Microsoft Defender Antivirus must be installed-- Another non-Microsoft antivirus/antimalware product must be installed and used as the primary antivirus solution-- Endpoints must be onboarded to Defender for Endpoint+- Operating system: Windows 10 or newer; Windows Server 2022, Windows Server 2019, or Windows Server, version 1803, or newer <br/>(Windows Server 2012 R2 and Windows Server 2016 if onboarded using the [modern, unified solution](/microsoft-365/security/defender-endpoint/configure-server-endpoints)). +- Microsoft Defender Antivirus must be installed. +- Another non-Microsoft antivirus/antimalware product must be installed and used as the primary antivirus solution. +- Endpoints must be onboarded to Defender for Endpoint. > [!IMPORTANT]-> - Microsoft Defender Antivirus is only available on devices running Windows 10 and 11, Windows Server 2022, Windows Server 2019, Windows Server, version 1803 or newer, Windows Server 2016, and Windows Server 2012 R2. +> - Microsoft Defender Antivirus is only available on devices running Windows 10 and 11, Windows Server 2022, Windows Server 2016, Windows Server 2019, Windows Server, version 1803 or newer, Windows Server 2016, and Windows Server 2012 R2. > - Passive mode is only supported on Windows Server 2012 R2 & 2016 when the device is onboarded using the [modern, unified solution](/microsoft-365/security/defender-endpoint/configure-server-endpoints). > - In Windows 8.1, enterprise-level endpoint antivirus protection is offered as [System Center Endpoint Protection](/previous-versions/system-center/system-center-2012-R2/hh508760(v=technet.10)), which is managed through Microsoft Endpoint Configuration Manager. > - Windows Defender is also offered for [consumer devices on Windows 8.1](/previous-versions/windows/it-pro/windows-8.1-and-8/dn344918(v=ws.11)#BKMK_WindowsDefender), although Windows Defender does not provide enterprise-level management. |
| security | Network Protection Macos | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/defender-endpoint/network-protection-macos.md | ms.sitesec: library ms.pagetype: security ms.localizationpriority: medium audience: ITPro--++ Last updated search.appverid: met150 +<! jweston-1 to return as author and ms.author appx April/May 2023. > + # Network protection for macOS [!INCLUDE [Microsoft 365 Defender rebranding](../../includes/microsoft-defender.md)] Network protection expands the scope of Microsoft 365 Defender [SmartScreen](/ - Onboarded Machines: - Minimum macOS version: 11 - Product version 101.78.13 or later- - Your device must be in either the InsiderSlow (Preview) or InsiderFast (Beta) Microsoft AutoUpdate update channel. You can check the update channel using the following command: + - Your device must be in either the External (Preview) or InsiderFast (Beta) Microsoft AutoUpdate update channel. You can check the update channel using the following command: ```bash mdatp health --field release_ring ``` -If your device isn't already in the InsiderSlow(Preview) update channel, execute the following command from the Terminal. The channel update takes effect next time the product starts (when the next product update is installed or when the device is rebooted). +If your device isn't already in the External(Preview) update channel, execute the following command from the Terminal. The channel update takes effect next time the product starts (when the next product update is installed or when the device is rebooted). ```bash-defaults write com.microsoft.autoupdate2 ChannelName -string InsiderSlow +defaults write com.microsoft.autoupdate2 ChannelName -string External ``` Alternatively, if you are in a managed environment (JAMF or Intune), you can configure the device group remotely. For more information, see [Set preferences for Microsoft 365 Defender for Endpoint on macOS](mac-preferences.md). Alternatively, if you are in a managed environment (JAMF or Intune), you can con ### Microsoft 365 Defender for Endpoint -After you’ve configured your device to be in the InsiderSlow(preview) update channel, install the most recent product version through Microsoft AutoUpdate. To open Microsoft AutoUpdate, run the following command from the Terminal: +After you’ve configured your device to be in the External(preview) update channel, install the most recent product version through Microsoft AutoUpdate. To open Microsoft AutoUpdate, run the following command from the Terminal: ```bash open /Library/Application\ Support/Microsoft/MAU2.0/Microsoft\ AutoUpdate.app |
| security | Network Protection | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/defender-endpoint/network-protection.md | ms.mktglfcycl: manage ms.sitesec: library ms.pagetype: security ms.localizationpriority: medium Previously updated : 10/13/2022 Last updated : 10/20/2022 audience: ITPro Here's an example query for advanced hunting: ```kusto DeviceNetworkEvents-|where ActionType in ('ExploitGuardNetworkProtectionAudited','ExploitGuardNetworkProtectionBlocked', 'ConnectionSuccess') +|where ActionType in ('ExploitGuardNetworkProtectionAudited','ExploitGuardNetworkProtectionBlocked') ``` |
| security | Prevent Changes To Security Settings With Tamper Protection | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/defender-endpoint/prevent-changes-to-security-settings-with-tamper-protection.md | To learn more about Microsoft Defender Vulnerability Management, see [Dashboard ## See also +- [Built-in protection helps guard against ransomware](built-in-protection.md) - [Help secure Windows PCs with Endpoint Protection for Microsoft Intune](/intune/help-secure-windows-pcs-with-endpoint-protection-for-microsoft-intune) - [Get an overview of Microsoft Defender for Endpoint](/microsoft-365/security/defender-endpoint) - [Better together: Microsoft Defender Antivirus and Microsoft Defender for Endpoint](why-use-microsoft-defender-antivirus.md) |
| security | Supported Event Types | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/defender/supported-event-types.md | The following table only includes the list of the tables supported in the stream | **[DeviceNetworkInfo](advanced-hunting-devicenetworkinfo-table.md)** | GA | GA | GA | GA | | **[DeviceProcessEvents](advanced-hunting-deviceprocessevents-table.md)** | GA | GA | GA | GA | | **[DeviceRegistryEvents](advanced-hunting-deviceregistryevents-table.md)** | GA | GA | GA | GA |-| **[EmailAttachmentInfo](advanced-hunting-emailattachmentinfo-table.md)** | GA |||| -| **[EmailEvents](advanced-hunting-emailevents-table.md)** | GA |||| -| **[EmailPostDeliveryEvents](advanced-hunting-emailpostdeliveryevents-table.md)** | GA |||| -| **[EmailUrlInfo](advanced-hunting-emailurlinfo-table.md)** | GA |||| +| **[EmailAttachmentInfo](advanced-hunting-emailattachmentinfo-table.md)** | GA |Public preview|Public preview|Public preview| +| **[EmailEvents](advanced-hunting-emailevents-table.md)** | GA |Public preview|Public preview|Public preview| +| **[EmailPostDeliveryEvents](advanced-hunting-emailpostdeliveryevents-table.md)** | GA |Public preview|Public preview|Public preview| +| **[EmailUrlInfo](advanced-hunting-emailurlinfo-table.md)** | GA |Public preview|Public preview|Public preview| | **[IdentityLogonEvents](advanced-hunting-identitylogonevents-table.md)**|GA|||| | **[IdentityQueryEvents](advanced-hunting-identityqueryevents-table.md)**|GA|||| | **[IdentityDirectoryEvents](advanced-hunting-identitydirectoryevents-table.md)**|GA|||| | **[CloudAppEvents](advanced-hunting-cloudappevents-table.md)**|GA||||+| **[UrlClickEvents](advanced-hunting-urlclickevents-table.md)**|Public preview|Public preview|Public preview|Public preview| |
| security | Report Junk Email Messages To Microsoft | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/security/office-365-security/report-junk-email-messages-to-microsoft.md | Watch this video that shows more information about the unified submissions exper |[Submit files for analysis](../intelligence/submission-guide.md)|Admin|Submit email attachments and other suspected files to Microsoft for analysis.| > [!NOTE]-> When you report an email entity to Microsoft, a copy is made of everything associated with the email to include it in the reviews. This copy includes the email content, the email headers, and related data about the email routing. Attachments in the message are also included. +> When you report an email entity to Microsoft, we copy everything associated with the email to include it in our continual algorithm reviews. This copy includes the email content, email headers, and related data about email routing. Any message attachments are also included. >-> Microsoft treats your feedback as your organization's permission to analyze all of the information and to improve the suspected message reporting and review process. Your message is stored securely until it is deleted no later than 30 days after you provided it. Microsoft may read your submitted message and attachments, however, your email is still treated as confidential between you and Microsoft. Your submission is not provided to any other party for the review process. +> Microsoft treats your feedback as your organization's permission for us to analyze all of the previously described information to fine tune the message hygiene algorithms. We hold your message in our secure audited datacenters in the USA. The submission is deleted no later than 30 days after you provide it to us. Microsoft personnel might read your submitted messages and attachments, which is normally not permitted for email in Microsoft 365. However, your email is still treated as confidential between you and Microsoft, and we will not provide your email or attachments to any other party as part of the review process. |
| whiteboard | Manage Data Organizations | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/whiteboard/manage-data-organizations.md | description: Learn about data retention for Microsoft Whiteboard in Azure and On # Manage data for Microsoft Whiteboard -Whiteboard content is stored in OneDrive for Business and Azure. OneDrive for Business is the default storage for all new whiteboards. Whiteboards that were originally created in Azure, and whiteboards that were initiated on a Surface Hub or a Microsoft Teams Room device, are stored in Azure. +Whiteboard content is stored in OneDrive for Business and Azure. OneDrive for Business is the default storage for all new whiteboards. Whiteboards that were originally created in Azure, and whiteboards that were initiated on a Surface Hub or a Microsoft Teams Rooms device, are stored in Azure. In order to manage data, you must first ensure that Whiteboard is enabled for your organization. For more information, see [Manage access to Whiteboard](manage-whiteboard-access-organizations.md). Data controls planned for future releases: [Manage sharing for Whiteboard](manage-sharing-organizations.md) -[Deploy Whiteboard on Windows](deploy-on-windows-organizations.md) +[Deploy Whiteboard on Windows](deploy-on-windows-organizations.md) |