| Category | Microsoft Docs article | Related commit history on GitHub | Change details |
|---|---|---|---|
| lighthouse | M365 Lighthouse Whats New | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/lighthouse/m365-lighthouse-whats-new.md | We're continuously adding new features to [Microsoft 365 Lighthouse](m365-lighth > > To see which new features are currently available in your partner tenant, go to the **Home** page of Microsoft 365 Lighthouse, and then either select the **What's new** link in the upper-right corner of the page or select **What's new** on the **What's new & learning resources** card. +## August 2024 ++### Access mailbox storage information from the tenant details page ++Our enhanced tenant details page now lets you track mailbox storage usage for users and shared mailboxes in your customer tenants. This feature provides insights into storage consumption, which helps with license resource optimization and planning. ++To access mailbox storage information, in the left navigation pane in Lighthouse, select **Tenants**, and then select any tenant in the list to open the tenant details page. From there, select either the **Overview** tab or the **Users** tab, and then select **Mailbox storage usage**. ++[Go to the Tenants page now](https://lighthouse.microsoft.com/#view/Microsoft_Intune_MTM/Tenants.ReactView) (once there, select a tenant) ++### Alert improvements ++Alert rules for Microsoft Defender for Endpoint alerts now include the option to filter by alert status. You can update existing alert rules to exclude **Resolved** endpoint alerts. ++To reduce the likelihood of reactivation, a Microsoft 365 Lighthouse alert in the **Dismissed** state will no longer move to the **Resolved** state. ++[Go to the Alerts page now](https://lighthouse.microsoft.com/#view/Microsoft_Intune_MTM/ManagedTenantAlerts.ReactView) ++To learn more, see [Overview of the Alerts page in Microsoft 365 Lighthouse](m365-lighthouse-alerts-overview.md). + ## June 2024 ### Access key information from enhanced tenant details page Plus, in the coming months we'll roll out even more enhancements: To check out the recent enhancements, in the left navigation pane in Lighthouse, select **Tenants**, and then select any tenant in the list to open the tenant details page. -[Go to the Tenants page now](https://lighthouse.microsoft.com/#view/Microsoft_Intune_MTM/Tenants.ReactView) -(Once there, select a tenant to view the enhanced tenant details page.) +[Go to the Tenants page now](https://lighthouse.microsoft.com/#view/Microsoft_Intune_MTM/Tenants.ReactView) (once there, select a tenant to view the enhanced tenant details page) ## May 2024 We've improved the tenant details page to provide a more comprehensive view of c To check out these improvements, in the left navigation pane in Lighthouse, select **Tenants**, and then select any tenant in the list to open the tenant details page and view the **Overview** tab. From there you can also access the new **Action items** tab. -[Go to the Tenants page now](https://lighthouse.microsoft.com/#view/Microsoft_Intune_MTM/Tenants.ReactView) -(Once there, select a tenant.) +[Go to the Tenants page now](https://lighthouse.microsoft.com/#view/Microsoft_Intune_MTM/Tenants.ReactView) (once there, select a tenant) ## April 2024 |
| syntex | Structured Freeform Setup | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/structured-freeform-setup.md | By default, structured and default document processing is turned on for librarie ## Turn off structured and freeform document processing -When the structured and freeform document processing service is turned off, structured and freeform models will not run, and users will not be able to create or apply structured or freeform models. +When the structured and freeform document processing service is turned off, structured and freeform models won't run, and users won't be able to create or apply structured or freeform models. Follow these steps to turn off structured and freeform document processing. Follow these steps to turn off structured and freeform document processing. > [!NOTE] > For multi-geo environments, when the service is turned off, the service is off for all geos. -## Using a custom Power Platform environment +## Using a Power Platform environment -Your tenant comes with a default Power Platform environment. 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. -<! -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. -> -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. +### Set up a default Power Platform environment -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. +Your tenant comes with a default Power Platform environment. To make the default environment ready for to use with Microsoft Syntex, follow these steps: +1. Sign in to the [Power Platform admin center](https://admin.powerplatform.microsoft.com/) as a Global Administrator, a Power Platform Administrator, or a Dynamics 365 Administrator. -<! -Users creating models in a [content center site](create-a-content-center.md) must be site members. Users creating models locally outside the content center must be site owners of those sites.> +2. Select the checkmark next to the default environment. -<! -## Prerequisites +3. In the **Dataverse** column, verify that the value is **Yes**. -### Permissions + - If the value is **No**, add Dataverse to the environment: -You must have Global admin or SharePoint admin permissions to be able to access the Microsoft 365 admin center and set up structured and freeform document processing in Syntex. + 1. On the command bar, select **Add Dataverse** and then confirm the action. -### Licensing + 2. Refresh the page until the **State** column is **Ready.** -> [!NOTE] -> As of July 1, 2023, per-user licenses are no longer available for purchase. You will need to [set up pay-as-you-go billing](syntex-azure-billing.md).<br><br> -> Per-user licenses purchased before July 1 can still be assigned to new users. After existing per-user licenses expire, you will need to opt-in to Syntex [pay-as-you-go billing](syntex-azure-billing.md). + - If the value is **Yes**, go to the next step. -For an overview of licensing options for Microsoft Syntex, see [Licensing for Microsoft Syntex](syntex-licensing.md). +4. On the command bar, select **Membership**. On the **System Administrators** panel, select **Add me**, and then select **Close**. -Each user for structured and freeform document processing must have a license assigned. To assign licenses, see [Set up Microsoft Syntex per-user licensing](set-up-content-understanding.md#assign-licenses). +5. On the command bar, select **Resources** > **Dynamics 365 apps**. The Dynamics 365 apps page for the default environment opens. -## Set up structured and freeform document processing --### Get AI Builder credits +6. Verify that the **AI Builder for Project Cortex** app is installed. -To use structured 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 in your default Power Platform environment. + - If **AI Builder for Project Cortex** isn't on the installed apps list, on the command bar, select **Install app**. -### Enable sites + - If **AI Builder for Project Cortex** is already on the installed apps list and the **Status** column shows **Installed**, the remaining steps can be skipped. -By default, structured and freeform document processing is turned off for all sites. + - If **AI Builder for Project Cortex** is on the installed apps list, but the **Status** column shows **Installation failed**, then select the status text to view the error details. On the **Error details** panel, select **Retry installation**. -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**. +7. On the **Install Dynamic 365 app** panel, select **AI Builder for Project Cortex**, and then select **Next**. -2. On the **Use content AI with Microsoft Syntex** page, select **Manage Microsoft Syntex**. +8. On the **Install AI Builder for Project Cortex** panel, agree to the terms of service, and then select **Install**. -3. On the **Manage Microsoft Syntex** page, select **Structured and freeform document processing**. +9. Wait for the app to install, and then refresh the page until the **Status** column shows **Installed**. -4. On the **Structured and freeform document processing** page: +### Set up a custom Power Platform environment - a. Choose which site or sites this service should be enabled for. +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. - > [!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, select **No SharePoint libraries** or **Libraries in selected SharePoint 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. -- c. Select **Save**. --## Using a custom Power Platform environment --Your tenant will come with a default Power Platform environment. 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. --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. +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. -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. For more information, see [Assign a security role to a user](/power-platform/admin/assign-security-roles). You don't need to assign users this role if you're using the default Power Platform environment. +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. -Users creating models in a [content center site](create-a-content-center.md) must be site members. Users creating models locally outside the content center must be site owners of those sites. -> |
| syntex | Syntex Licensing | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/syntex-licensing.md | Users with active per-user licenses can perform the following tasks: - Use the document library rules to move or copy content. - Merge and extract PDFs -If you plan to use a custom Power Platform environment for structured or freeform document processing, see [Using a custom Power Platform environment](structured-freeform-setup.md#using-a-custom-power-platform-environment). +If you plan to use a custom Power Platform environment for structured or freeform document processing, see [Set up a custom Power Platform environment](structured-freeform-setup.md#set-up-a-custom-power-platform-environment). <! ## AI Builder credits |