Category | Microsoft Docs article | Related commit history on GitHub | Change details |
---|---|---|---|
admin | Manage Feedback Ms Org | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/admin/manage/manage-feedback-ms-org.md | description: "Manage feedback your users can send to Microsoft about Microsoft p # Manage Microsoft feedback for your organization -As the admin of a Microsoft 365 organization, there are several policies to help you manage the feedback collection and the customer engagement experience of your users when using Microsoft 365 applications. You can create and use existing Microsoft Entra groups in your organization for each of these policies. With these policies, you can control how different departments in your organization can send feedback to Microsoft. Microsoft reviews all feedback submitted by customers and uses this feedback to improve the product experiences for users, including by improving the quality of AI-generated responses and troubleshooting product issues. Keeping the feedback experiences turned **On** allows you to see what your users are saying about the Microsoft products they're using. The feedback we collect from your users is available in the <a href="https://go.microsoft.com/fwlink/p/?linkid=2024339" target="_blank">Microsoft 365 admin center</a>. +As the admin of a Microsoft 365 organization, there are several policies to help you manage the feedback collection and the customer engagement experience of your users when using Microsoft 365 applications. You can create and use existing Microsoft Entra groups in your organization for each of these policies. With these policies, you can control how different departments in your organization can send feedback to Microsoft. Microsoft reviews all feedback submitted by customers and uses this feedback to improve the product experiences for users, including by improving the quality of AI-generated responses and troubleshooting product issues. Keeping the feedback experiences turned **On** allows you to see what your users are saying about the Microsoft products they're using. The feedback we collect from your users is available in the [Microsoft 365 admin center](https://go.microsoft.com/fwlink/p/?linkid=2024339). ++> [!NOTE] +> Microsoft acts as a data processor for your tenant's feedback. As the tenant administrator, you can manage your tenant's feedback in the Microsoft 365 admin center. For more information, see [How can I see my user's feedback?](../misc/feedback-user-control.md#how-can-i-see-my-users-feedback) To learn more about the types of feedback and how Microsoft uses user feedback, see [Learn about Microsoft feedback for your organization](../misc/feedback-user-control.md). -The table below represents which apps and services are currently connected to the feedback policies shown in the feedback policies table below. See below the table for screenshot examples. +The following table represents which apps and services are currently connected to the feedback policies shown in the [Feedback policies table](#feedback-policies). For examples of in-product feedback and surveys, see [Feedback types](/microsoft-365/admin/misc/feedback-user-control#feedback-types). |**Apps & Services**|**In-product feedback** <br> |**In-product surveys** <br> |**Metadata collection** <br> |**Customer engagement** <br> | |:--|:--|:--|:--|:--| The table below represents which apps and services are currently connected to th |**Viva Insights**|Yes|Yes|Yes|Yes| |**Viva Pulse**|Yes|Yes|Yes|Yes| --[See here for some examples of in-product surveys and feedback.](/microsoft-365/admin/misc/feedback-user-control#in-product-surveys) --## Before you begin --Your devices must be on a minimum build number to use these policies. See the table below for more information. --|**Build #**|**Win32**|**iOS**|**Android**|**Mac**|**Web**| -|:--|:--|:--|:--|:--|:--| -|In-product feedback|At least Version 2010|At least 2.42|At least 16.0.13328|At least 16.42|Publicly available| -|In-product surveys|At least Version 2010|At least 2.42|At least 16.0.13426|At least 16.42|Pending rollout| -|Metadata collection|At least Version 2010|At least 2.42|At least 16.0.13328|At least 16.42|Publicly available| -|Customer engagement|At least Version 2010|At least 2.42|At least 16.0.13426|At least 16.42|Pending rollout| --## Specific policies you can configure --### Feedback policies +## Feedback policies |**Policy name**|**Default state**|**Control summary**| |:--|:--|:--| |Allow users to access feedback portal|On|Manage user access to the feedback portal where users can follow up on their feedback and participate in community feedback.| |Allow users to submit feedback to Microsoft|On|Controls feedback entry points across applications.| |Allow users to receive and respond to in-product surveys from Microsoft|On|Controls survey prompts within product.|-|Allow users to include screenshots and attachments when they submit feedback to Microsoft|On|Allows users to choose relevant files, screen recordings and screenshots to help Microsoft better understand and troubleshoot their feedback.| +|Allow users to include screenshots and attachments when they submit feedback to Microsoft|On|Allows users to choose relevant files, screen recordings, and screenshots to help Microsoft better understand and troubleshoot their feedback.| |Allow Microsoft to follow up on feedback submitted by users|On|Determines if user can share contact info with feedback/survey for follow-up by Microsoft. Also allows users to get notified of feedback status changes. Users can manage communications settings in the feedback portal.|-|Allow users to include log files and content samples when feedback is submitted to Microsoft|On|Allows users to include Microsoft generated files such as additional log files and content samples when relevant to feedback they are submitting. Examples may include [Microsoft 365 Copilot](https://blogs.microsoft.com/blog/2023/03/16/introducing-microsoft-365-copilot-your-copilot-for-work/) prompt and response interactions.| +|Allow users to include log files and content samples when feedback is submitted to Microsoft|On|Allows users to include Microsoft generated files such as additional log files and content samples when relevant to feedback they're submitting. Examples may include [Microsoft 365 Copilot](https://blogs.microsoft.com/blog/2023/03/16/introducing-microsoft-365-copilot-your-copilot-for-work/) prompt and response interactions.| > [!NOTE] > The **Allow users to access the feedback portal** policy is a cloud policy. This policy isn't defined in ADMX and doesn't have a corresponding registry key available to set the policy. You should create a cloud policy to enforce it. This is a cloud policy because the feedback portal is a web application that makes a call to the cloud policy service, which is also a web application, requesting the policies for the person who signs in. If this policy is configured, the feedback portal will receive the configured policy value in the response from the cloud policy service. You can find these policy settings under User Configuration\Policies\Administrat > [!NOTE] > It takes a few hours for the client applications to update. -### User experience examples +## User experience examples :::image type="content" source="../../media/feedbackexamplesfg1.png" alt-text="Screenshot: Example of user feedback submission to Microsoft"::: |
admin | Use Qr Code Download Outlook | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/admin/manage/use-qr-code-download-outlook.md | description: "Learn how to use a QR code to authenticate and download Outlook mo # Use a QR code to sign-in to the Outlook mobile apps > [!IMPORTANT]-> As of August 2024, this feature will turned back on for Enterprise users. For more details on the settings and controls for this feature see, [Conditional Access: Authentication flows (Preview)](/entra/identity/conditional-access/concept-authentication-flows). +> As of September2024, this feature will turned off indefinitely for Enterprise users. For more details on the settings and controls for this feature see, [Conditional Access: Authentication flows (Preview)](/entra/identity/conditional-access/concept-authentication-flows). As the Microsoft 365 administrator, you can allow your users to sign in to the Outlook for Android or iOS app on their mobile devices without having to enter their username and password. By scanning a QR code, users can securely authenticate and sign in to Outlook mobile. |
admin | Password Policy Recommendations | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/admin/misc/password-policy-recommendations.md | Good password practices fall into a few broad categories: The primary goal of a more secure password system is password diversity. You want your password policy to contain lots of different and hard to guess passwords. Here are a few recommendations for keeping your organization as secure as possible. -- Maintain an eight-character minimum length requirement+- Maintain an fourteen-character minimum length requirement - Don't require character composition requirements. For example, \*&(^%$ |
archive | Archive Pricing | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/archive/archive-pricing.md | The following table helps visualize the savings you realize by archiving content ## Billing scenarios -Your charges for Microsoft 365 Archive depend on your tenantΓÇÖs Standard storage quota. The following scenarios and diagram can help you compare charges based on excess storage. +Your charges for Microsoft 365 Archive depend on your tenantΓÇÖs standard storage quota. The following scenarios and diagram can help you compare charges based on excess storage. |Scenario |Description |Additional costs | |::|||-|**A** |Tenant hasn't archived any data and exceeds the Standard storage quota by 200 GB. |Purchase 200 GB of additional Standard storage packs. | -|**B** |Tenant has archived the 200 GB of data that exceeded their Standard storage quota. |Pay at $0.05/GB/month for 200 GB of Archive storage. | -|**C** |Tenant has archived more storage than exceeded their Standard storage quota. |Pay only for the 200 GB of Archived data that exceeds the Standard storage quota. | -|**D** |Tenant has archived some, but not all, of the data that exceeds their Standard storage quota. |Purchase additional Standard storage packs and pay $0.05/GB/month for approximately 100 GB of Archived data. | -|**E** |TenantΓÇÖs total data (Standard + Archive) is less than their Standard storage quota. |No additional costs. | +|**A** |Tenant hasn't archived any data and exceeds the standard storage quota by 200 GB. |Purchase 200 GB of additional standard storage packs. | +|**B** |Tenant has archived the 200 GB of data that exceeded their standard storage quota. |Pay at $0.05/GB/month for 200 GB of archive storage. | +|**C** |Tenant has archived more storage than exceeded their standard storage quota. |Pay only for the 200 GB of archived data that exceeds the standard storage quota. | +|**D** |Tenant has archived some, but not all, of the data that exceeds their standard storage quota. |Purchase additional standard storage packs and pay $0.05/GB/month for approximately 100 GB of archived data. | +|**E** |TenantΓÇÖs total data (standard + archive) is less than their standard storage quota. |No additional costs. | -![Diagram showing comparisons for five archive scenarios.](../media/m365-archive/archive-billing-scenarios-diagram.png) +![Diagram showing comparisons for five archive billing scenarios.](../media/m365-archive/archive-billing-scenarios-diagram2.png) |
enterprise | Deploy Identity Solution Identity Model | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/deploy-identity-solution-identity-model.md | |
enterprise | Hybrid Modern Auth Overview | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/hybrid-modern-auth-overview.md | |
enterprise | Prepare For Directory Synchronization | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/prepare-for-directory-synchronization.md | Title: "Prepare for directory synchronization to Microsoft 365" Previously updated : 12/28/2023 Last updated : 09/25/2024 audience: Admin |
enterprise | Protect Your Global Administrator Accounts | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/protect-your-global-administrator-accounts.md | Title: "Step 2. Protect your Microsoft 365 privileged accounts" Previously updated : 12/28/2023 Last updated : 09/26/2024 audience: Admin |
enterprise | Turn Off Directory Synchronization | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/turn-off-directory-synchronization.md | To turn off Directory synchronization: } # Perform the update- Update-MgBetaOrganization -OrganizationId $organizationId -BodyParameter $params + Update-MgOrganization -OrganizationId $organizationId -BodyParameter $params # Check that the command worked Get-MgOrganization | Select OnPremisesSyncEnabled |
syntex | Autofill Setup | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/autofill-setup.md | By default, autofill columns is turned on for libraries in all SharePoint sites. 3. On the **Automate content processes with Syntex** page, select **Go to Syntex settings**. -4. On the Syntex page, under **Document & image services**, select **Autofill columns**. +4. On the Syntex page, in the **Document & image services** section, select **Autofill columns**. 5. On the **Autofill columns** panel: - a. Choose which site or sites this service should be enabled for. + a. Choose the site or sites on which this service should be enabled. - b. To restrict user access to this service, under **Sites where autofill columns can be used when it's turned on**, select **Edit**. On the **Where can autofill columns be used?** panel, change the setting from **All sites** to **Selected sites (up to 100)** or **No sites**. For selected sites, follow the instructions to select the sites or upload a CSV listing of the sites. You can then manage site access permissions for the sites you selected. + b. To restrict user access to this service, under **Sites where Autofill can be used when it's turned on**, select **Edit**. On the **Where can autofill columns be used?** panel, change the setting from **All sites** to **Selected sites (up to 100)** or **No sites**. For selected sites, follow the instructions to select the sites or upload a CSV listing of the sites. You can then manage site access permissions for the sites you selected. c. Select **Save**. |
syntex | Content Assembly Setup | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/content-assembly-setup.md | By default, content assembly is available for libraries on all SharePoint sites. 3. On the **Automate content processes with Syntex** page, select **Go to Syntex settings**. -4. On the Syntex page, under **Document & image services**, select **Content assembly**. +4. On the Syntex page, in the **Document & image services** section, select **Content assembly**. -5. On the **Content assembly** pane;, select **No sites**, and then select **Save**. +5. On the **Content assembly** panel, select **Edit**. ++6 On the **Which SharePoint sites should show the option to create templates and generate documents**, select **No libraries**, and then select **Save**. |
syntex | Esignature Setup | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/esignature-setup.md | You must be a [SharePoint Administrator](/entra/identity/role-based-access-contr 3. On the **Automate content processes with Syntex** page, select **Go to Syntex settings**. -4. On the Syntex page, under **Document & image services**, select **eSignature**. +4. On the Syntex page, in the **Document & image services** section, select **eSignature**. 5. For existing customers, read the [terms of service](/legal/microsoft-365/esignature-terms-of-service), and then select **Turn on** to enable the service. You must be a [SharePoint Administrator](/entra/identity/role-based-access-contr By default, SharePoint eSignature is turned on for libraries in all SharePoint sites. Follow these steps to limit which sites users can use eSignature. -1. On the **Manage Microsoft Syntex** page, select **eSignature**. +1. On the Syntex page, in the **Document & image services** section, select **eSignature**. -2. On the **eSignature** panel, under **SharePoint libraries where Syntex eSignature is turned on**, select **Select sites**. +2. On the **eSignature** panel, under **Sites where eSignature can be used**, select **Select sites**. - a. Choose which site or sites this service should be enabled for. + a. Choose the site or sites on which this service should be enabled. - b. To restrict user access to this service, select **No SharePoint libraries** or **Libraries in selected sites** and follow the instructions to either select the sites or upload a CSV listing a maximum of 100 sites. Be sure to add your content center site if you want it to be included. You can then manage site access permissions for the sites you selected. + b. To restrict user access to this service, select **No sites** or **Selected sites (up to 100)**. Follow the instructions to either select the sites or upload a CSV listing a maximum of 100 sites. Be sure to add your content center site if you want it to be included. You can then manage site access permissions for the sites you selected. c. Select **Save**. By default, SharePoint eSignature is turned on for libraries in all SharePoint s ### Turn off eSignature -1. On the **Manage Microsoft Syntex** page, select **eSignature**. +1. On the Syntex page, in the **Document & image services** section, select **eSignature**. -2. If SharePoint eSignature is turned on, there will be a **Turn off** button visible. To turn off SharePoint eSignature, select **Turn off**. +2. If SharePoint eSignature is turned on, on the **eSignature** panel, the **Turn off** button is visible. To turn off SharePoint eSignature, select **Turn off**. ### Add other signature providers -1. On the **Manage Microsoft Syntex** page, select **eSignature**. +1. On the Syntex page, in the **Document & image services** section, select **eSignature**. -2. On the **eSignature** panel, select **Add or remove other signature providers**. +2. On the **eSignature** panel, under **Other signature providers**, select **Add or remove signature providers**. -3. On the **Edit signature providers** panel, select the provider you want to add. +3. On the **Add or remove other signature providers** panel, select the provider you want to add. ![Screenshot showing the Edit signature providers panel.](../media/content-understanding/esignature-edit-providers-panel.png) By default, SharePoint eSignature is turned on for libraries in all SharePoint s ### Microsoft Entra B2B -Microsoft Entra B2B provides authentication and management of guests. External signers or recipients are considered as guests within your tenant. To be able to send requests to signers outside your organization, you need to enable [Microsoft Entra B2B integration for SharePoint and OneDrive](/sharepoint/sharepoint-azureb2b-integration). You would need to resend the eSignature request if a guest user is deleted from the tenant while a signature request is still ongoing. The guest user would no longer be able to access the request document or the final signed document. If you need to delete a guest user, make sure they are not a party to any ongoing request. +Microsoft Entra B2B provides authentication and management of guests. External signers or recipients are considered as guests within your tenant. To be able to send requests to signers outside your organization, you need to enable [Microsoft Entra B2B integration for SharePoint and OneDrive](/sharepoint/sharepoint-azureb2b-integration). You would need to resend the eSignature request if a guest user is deleted from the tenant while a signature request is still ongoing. The guest user would no longer be able to access the request document or the final signed document. If you need to delete a guest user, make sure they aren't a party to any ongoing request. ### Authentication External recipients might need to authenticate before they're able to access a d ### Conditional access -Certain [conditional access](/entra/identity/conditional-access/overview) might determine whether external recipients (signers outside of your organization or Microsoft 365 tenant) will be able sign a document. Depending on the admin setup, external signers might not be able to access and read the document for signing. In some other cases, they might be able to access the document for signing, but the signing operation will be unsuccessful. One common way to resolve this is to add the **Microsoft eSignature Service** to the list of approved apps via the Microsoft Entra admin center. +Certain [conditional access](/entra/identity/conditional-access/overview) might determine whether external recipients (signers outside of your organization or Microsoft 365 tenant) are able sign a document. Depending on the admin setup, external signers might not be able to access and read the document for signing. In some other cases, they might be able to access the document for signing, but the signing operation is unsuccessful. One common way to resolve this is to add the **Microsoft eSignature Service** to the list of approved apps via the Microsoft Entra admin center. > [!NOTE] > When using other electronic signature providers, settings within Microsoft 365 don't impact whether you can send requests outside to external recipients. Certain [conditional access](/entra/identity/conditional-access/overview) might ### Document storage -SharePoint eSignature lets a requester start a signature request from a PDF document that is saved in a SharePoint library for which eSignature has been enabled. After all required parties have signed, the SharePoint eSignature service saves a copy of the signed document to the folder of the original document (originating folder). The sender is notified in an email that includes a link to view the document and a separate link to the SharePoint folder where the signed document was saved. +SharePoint eSignature lets a requester start a signature request from a PDF document that is saved in a SharePoint library on which eSignature is enabled. After all required parties have signed, the SharePoint eSignature service saves a copy of the signed document to the folder of the original document (originating folder). The sender is notified in an email that includes a link to view the document and a separate link to the SharePoint folder where the signed document was saved. Before a signature request is sent and at the completion of the request, certain checks are done to ensure that the sender has the permission to write to the document and the originating folder. If the permission changes when the signature request is in progress, the service might not be able to save a copy of the signed document in the originating folder. This event can happen when: Before a signature request is sent and at the completion of the request, certain ### Document retention -When a signature request is created for a document in SharePoint, the SharePoint eSignature service creates a working copy of the document. It's this working copy that is sent out to all recipients for signing, and it's how the sender can track the status of their requests. The working copy of the request is stored in a hidden document library in SharePoint. The signature will only be added to the working copy of the request document after all parties have signed; otherwise, it will appear as unsigned even if one of the parties has added their signature. +When a signature request is created for a document in SharePoint, the SharePoint eSignature service creates a working copy of the document. It's this working copy that is sent out to all recipients for signing, and it's how the sender can track the status of their requests. The working copy of the request is stored in a hidden document library in SharePoint. The signature will be added to the working copy of the request document only after all parties have signed. If any party has not signed, the document will appear as unsigned, even if one party has already added their signature. The working copy of the request is stored and retained for five years or in accordance with the document retention policy set up by the SharePoint or tenant admin. Learn more about [retention policies](/purview/retention-policies-sharepoint). For more protection, when a sender cancels a request, recipients immediately los ### Other electronic signature providers -At the end of the signing process when all required parties have signed, a copy of the signed document is automatically saved to SharePoint. The signed document is saved to a provider-specific folder of a special **Apps** folder in SharePoint. Every document library has a provider-specific folder where all documents signed by using that provider are saved. The signed document will be stored in the folder path < Document library > → Apps → Signed documents → < Provider > +At the end of the signing process when all required parties have signed, a copy of the signed document is automatically saved to SharePoint. The signed document is saved to a provider-specific folder of a special **Apps** folder in SharePoint. Every document library has a provider-specific folder where all documents signed by using that provider are saved. The signed document will be stored in the folder path *Document library\Apps\Signed documents\Provider*. ![Screenshot showing a signed document in a provider-specific folder.](../media/content-understanding/esignature-other-provider-folder.png) |
syntex | Image Tagging Setup | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/image-tagging-setup.md | By default, image tagging is available for libraries on all SharePoint sites. Fo 3. On the **Automate content processes with Syntex** page, select **Go to Syntex settings**. -4. On the Syntex page, under **Document & image services**, select **Image tagging**. +4. On the Syntex page, in the **Document & image services** section, select **Image tagging**. 5. On the **Image tagging** panel: - a. Choose which site or sites this service should be enabled for. + a. Choose the site or sites on which this service should be enabled. - b. To restrict user access to this service, select **No sites** or **Selected sites** and follow the instructions to either select the sites or upload a CSV listing a maximum of 100 sites. Be sure to add your content center site if you want it to be included. You can then manage site access permissions for the sites you selected. + b. To restrict user access to this service, select **Edit**, and then select **No sites** or **Selected sites (up to 100)**. Follow the instructions to either select the sites or upload a CSV listing a maximum of 100 sites. Be sure to add your content center site if you want it to be included. You can then manage site access permissions for the sites you selected. c. Select **Save**. |
syntex | Ocr | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/ocr.md | Follow these steps to manage which SharePoint sites have OCR enabled for Microso 3. On the **Automate content processes with Syntex** page, select **Go to Syntex settings**. -4. On the Syntex page, under **Document & image services**, select **Optical character recognition**. +4. On the Syntex page, in the **Document & image services** section, select **Optical character recognition**. 5. On the **Optical character recognition** panel: - a. Choose which site or sites this service should be enabled for. + a. Choose the site or sites on which this service should be enabled. - b. To restrict user access to this service, select **No sites** or **Selected sites** and follow the instructions to either select the sites or upload a CSV listing a maximum of 100 sites. Be sure to add your content center site if you want it to be included. You can then manage site access permissions for the sites you selected. + b. To restrict user access to this service, under **Select the SharePoint libraries where you would like to enable optical character recognition**, select **No sites** or **Selected sites (up to 100)**. Follow the instructions to either select the sites or upload a CSV listing a maximum of 100 sites. Be sure to add your content center site if you want it to be included. You can then manage site access permissions for the sites you selected. c. Select **Save**. |
syntex | Prebuilt Setup | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/prebuilt-setup.md | After an [Azure subscription is linked to Microsoft Syntex](syntex-azure-billing By default, prebuilt document processing is turned on for libraries in all SharePoint sites. When prebuilt document processing is on, prebuilt models are allowed to run. Prebuilt models can also be created and applied on sites that are specified. -Follow these steps to limit which sites users can use create prebuilt models to process files. +Follow these steps to limit on which sites users can create prebuilt models to process files. 1. In the Microsoft 365 admin center, select <a href="https://go.microsoft.com/fwlink/p/?linkid=2171997" target="_blank">**Setup**</a>. Follow these steps to limit which sites users can use create prebuilt models to 3. On the **Automate content processes with Syntex** page, select **Go to Syntex settings**. -4. On the Syntex page, under **Document & image services**, select **Prebuilt document processing**. +4. On the Syntex page, in the **Document & image services** section, select **Prebuilt document processing**. 5. On the **Prebuilt document processing** panel: - a. Choose which site or sites this service should be enabled for. + a. On the **Sites** tab, choose the site or sites on which this service should be enabled. > [!NOTE] > Disabling a site after a model is made available to process files on that site will not disable the model. Models can still be used to process files and incur charges. A model can be made available to process files by being created on that site or in a content center. - b. To restrict user access to this service, under **Sites where models can be created**, select **Edit**. On the **Where can prebuilt models be used?** panel, select **No sites** or **Selected sites (up to 100)** and follow the instructions to either select the sites or upload a CSV file listing a maximum of 100 sites. You can then manage site access permissions for the sites you selected. + b. To restrict user access to this service, under **Sites where models can be created**, select **Edit**. On the **Sites where models can be created** panel, select **No sites** or **Selected sites (up to 100)** and follow the instructions to either select the sites or upload a CSV file listing a maximum of 100 sites. You can then manage site access permissions for the sites you selected. If you don't want the service available on any sites, select **No sites**. > [!NOTE] > You must be a member of any site that you want to include in the CSV file. Follow these steps to limit which sites users can use create prebuilt models to ## Turn off prebuilt document processing -When the prebuilt document processing service is turned off, prebuilt models will not run, and users will not be able to create or apply prebuilt models. +When the prebuilt document processing service is turned off, prebuilt models won't run, and users won't be able to create or apply prebuilt models. Follow these steps to turn off prebuilt document processing. -1. On the **Manage Microsoft Syntex** page, select **Prebuilt document processing**. +1. On the **Prebuilt document processing** panel, on the **Settings** tab, turn the **Status** to **Off**. -2. On the **Prebuilt document processing** page, under **Status**, turn the toggle to **Off**. -- ![Screenshot of a Prebuilt document processing panel showing the Status toggle.](../media/content-understanding/turn-off-service.png) +2. On the **Turn off prebuilt document processing?** panel, select **Turn off**. > [!NOTE]- > For multi-geo environments, when the service is turned off, the service is off for all geos. + > For multi-geo environments, when the service is turned off, the service is off for all geos. ++<! + ![Screenshot of a Prebuilt document processing panel showing the Status toggle.](../media/content-understanding/turn-off-service.png) +> |
syntex | Structured Freeform Setup | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/structured-freeform-setup.md | After an [Azure subscription is linked to Microsoft Syntex](syntex-azure-billing ## Manage sites -By default, structured and default document processing is turned on for libraries in all SharePoint sites. Follow these steps to manage which SharePoint sites users can use to create custom models to process files. +By default, structured and default document processing is turned on for libraries in all SharePoint sites. Follow these steps to limit on which sites users can create custom models to process files. 1. In the Microsoft 365 admin center, select <a href="https://go.microsoft.com/fwlink/p/?linkid=2171997" target="_blank">**Setup**</a>. By default, structured and default document processing is turned on for librarie 3. On the **Automate content processes with Syntex** page, select **Go to Syntex settings**. -4. On the Syntex page, under **Document & image services**, select **Structured and freeform document processing**. +4. On the Syntex page, in the **Document & image services** section, select **Structured and freeform document processing**. 5. On the **Structured and freeform document processing** panel: - a. Choose which site or sites this service should be enabled for. + a. On the **Sites** tab, choose the site or sites on which this service should be enabled. > [!NOTE] > Disabling a site after a model is made available to process files on that site will not disable the model. Models can still be used to process files and incur charges. A model can be made available to process files by being created either on that site or in a content center. - b. To restrict user access to this service, under **Sites where models can be created**, select **Edit**. On the **Where can prebuilt models be used?** panel, select **No sites** or **Selected sites (up to 100)** and follow the instructions to either select the sites or upload a CSV file listing a maximum of 100 sites. You can then manage site access permissions for the sites you selected. + b. To restrict user access to this service, under **Sites where models can be created**, select **Edit**. On the **Sites where models can be created** panel, select **No sites** or **Selected sites (up to 100)** and follow the instructions to either select the sites or upload a CSV file listing a maximum of 100 sites. You can then manage site access permissions for the sites you selected. If you don't want the service available on any sites, select **No sites**. > [!NOTE] > You must be a member of any site that you want to include in the CSV file. When the structured and freeform document processing service is turned off, stru Follow these steps to turn off structured and freeform document processing. -1. On the **Manage Microsoft Syntex** page, select **Structured and freeform document processing**. +1. On the **Structured and freeform document processing** panel, on the **Settings** tab, turn the **Status** to **Off**. -2. On the **Structured and freeform document processing** page, under **Status**, turn the toggle to **Off**. -- ![Screenshot of a Structured and freeform document processing panel showing the Status toggle.](../media/content-understanding/turn-off-service.png) +2. On the **Turn off structured and freeform document processing?** panel, select **Turn off**. > [!NOTE] > For multi-geo environments, when the service is turned off, the service is off for all geos. Your tenant comes with a default Power Platform environment. To make the default 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. The environment must not be of the Sandbox type. -If you have [AI Builder credits available](/power-platform/admin/capacity-add-on) to the environment, these credits will be used first. For both custom and default Power Platform environments, once the credits are exhausted, the processing transactions are charged to the meter. +If you have [AI Builder credits available](/power-platform/admin/capacity-add-on) to the environment, these credits are used first. For both custom and default Power Platform environments, once the credits are exhausted, the processing transactions are charged to the meter. When using a custom environment, model creators must be assigned the Environment Maker security role. Model users must have permission to use (not edit) the model file in SharePoint libraries. For more information, see [Assign a security role to a user](/power-platform/admin/assign-security-roles). Custom security roles can be created to specifically grant access to the AI Builder tables as the Environment Maker role so those users can create models. You don't need to assign users this role if you're using the default Power Platform environment. |
syntex | Taxonomy Tagging Setup | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/taxonomy-tagging-setup.md | By default, taxonomy tagging is available for libraries on all SharePoint sites. 3. On the **Automate content processes with Syntex** page, select **Go to Syntex settings**. -4. On the Syntex page, under **Document & image services**, select **Taxonomy tagging**. +4. On the Syntex page, in the **Document & image services** section, select **Taxonomy tagging**. 5. On the **Taxonomy tagging** panel: - a. Choose which site or sites this service should be enabled for. + a. Choose the site or sites on which this service should be enabled. > [!NOTE] > You can enable taxonomy tagging only at the site level, and it will work for any subsites under the site. Enabling only for a particular subsite is not supported. - b. To restrict user access to this service, select **No sites** or **Selected sites** and follow the instructions to either select the sites or upload a CSV listing a maximum of 100 sites. Be sure to add your content center site if you want it to be included. You can then manage site access permissions for the sites you selected. + b. To restrict user access to this service, select **Edit**, and then select **No sites** or **Selected sites (up to 100)**. Follow the instructions to either select the sites or upload a CSV listing a maximum of 100 sites. Be sure to add your content center site if you want it to be included. You can then manage site access permissions for the sites you selected. c. Select **Save**. |
syntex | Translation Setup | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/translation-setup.md | After an [Azure subscription is linked to Microsoft Syntex](syntex-azure-billing By default, document translation is turned on for libraries in all SharePoint sites. Follow these steps to limit which sites users can use document translation. -1. In the Microsoft 365 admin center, select <a href="https://go.microsoft.com/fwlink/p/?linkid=2171997" target="_blank">**Setup**</a>, and then select **Use content AI with Microsoft Syntex**. +1. In the Microsoft 365 admin center, select <a href="https://go.microsoft.com/fwlink/p/?linkid=2171997" target="_blank">**Setup**</a>. -2. On the **Use content AI with Microsoft Syntex** page, select **Manage Microsoft Syntex**. +2. Under **Files and content**, select **Automate content processes with Syntex**. -3. On the **Microsoft Syntex** panel, select **Document translation**. +3. On the **Automate content processes with Syntex** page, select **Go to Syntex settings**. -4. On the **Document translation** panel: +4. On the Syntex page, in the **Document & image services** section, select **Document translation**. - a. Choose which site or sites this service should be enabled for. +5. On the **Document translation** panel: - b. To restrict user access to this service, under **Sites where document translation can be used when it's turned on**, select **Edit**. On the **Where can document translation be used?** panel, change the setting from **All sites** to **Selected sites (up to 100)** or **No sites**. For selected sites, follow the instructions to select the sites or upload a CSV listing of the sites. You can then manage site access permissions for the sites you selected. + a. Choose the site or sites on which this service should be enabled. ++ b. To restrict user access to this service, under **Where document translation can be used when it's turned on**, select **Edit**. On the **Where can document translation be used?** panel, change the setting from **All sites** to **Selected sites (up to 100)** or **No sites**. For selected sites, follow the instructions to select the sites or upload a CSV listing of the sites. You can then manage site access permissions for the sites you selected. c. By default, document translation for OneDrive is turned on. If you want to turn it off, in the **OneDrive** section, select **Edit**. On the **Where can document translation be used?** panel, in the **OneDrive** section, clear the **Available in OneDrive** checkbox. |
syntex | Unstructured Setup | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/unstructured-setup.md | After an [Azure subscription is linked to Microsoft Syntex](syntex-azure-billing ## Manage sites -By default, unstructured document processing is turned on for libraries in all SharePoint sites. Follow these steps to manage which SharePoint sites users can use to create custom models to process files. +By default, unstructured document processing is turned on for libraries in all SharePoint sites. Follow these steps to limit on which sites users can create custom models to process files. 1. In the Microsoft 365 admin center, select <a href="https://go.microsoft.com/fwlink/p/?linkid=2171997" target="_blank">**Setup**</a>. By default, unstructured document processing is turned on for libraries in all S 3. On the **Automate content processes with Syntex** page, select **Go to Syntex settings**. -4. On the Syntex page, under **Document & image services**, select ***Unstructured document processing**. +4. On the Syntex page, in the **Document & image services** section, select ***Unstructured document processing**. 5. On the **Unstructured document processing** panel: - a. Choose which site or sites this service should be enabled for. + a. On the **Sites** tab, choose the site or sites on which this service should be enabled. > [!NOTE] > Disabling a site after a model is made available to process files on that site will not disable the model. Models can still be used to process files and incur charges. A model can be made available to process files by being created either on that site or in a content center. - b. To restrict user access to this service, under **Sites where models can be created**, select **Edit**. On the **Where can prebuilt models be used?** panel, select **No sites** or **Selected sites (up to 100)** and follow the instructions to either select the sites or upload a CSV file listing a maximum of 100 sites. You can then manage site access permissions for the sites you selected. + b. To restrict user access to this service, under **Sites where models can be created**, select **Edit**. On the **Sites where models can be created** panel, select **No sites** or **Selected sites (up to 100)** and follow the instructions to either select the sites or upload a CSV file listing a maximum of 100 sites. You can then manage site access permissions for the sites you selected. If you don't want the service available on any sites, select **No sites**. > [!NOTE] > You must be a member of any site that you want to include in the CSV file. By default, unstructured document processing is turned on for libraries in all S ## Turn off unstructured document processing -When the unstructured document processing service is turned off, unstructured models will not run, and users will not be able to create or apply unstructured models. +When the unstructured document processing service is turned off, unstructured models won't run, and users won't be able to create or apply unstructured models. Follow these steps to turn off unstructured document processing. -1. On the **Manage Microsoft Syntex** page, select **Unstructured document processing**. +1. On the **Unstructured document processing** panel, on the **Settings** tab, turn the **Status** to **Off**. -2. On the **Unstructured document processing** page, under **Status**, turn the toggle to **Off**. -- ![Screenshot of an Unstructured document processing panel showing the Status toggle.](../media/content-understanding/turn-off-service.png) +2. On the **Turn off unstructured document processing?** panel, select **Turn off**. > [!NOTE] > For multi-geo environments, when the service is turned off, the service is off for all geos. |