| Service | Microsoft Docs article | Related commit history on GitHub | Change details |
|---|---|---|---|
| SharePoint | Manage Loop Components | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/manage-loop-components.md | Previously updated : 01/31/2022 Last updated : 03/31/2023 Title: "Manage Loop experiences (Loop app and Loop components) in SharePoint" Loop experiences on Microsoft 365 OneDrive or SharePoint are backed by .fluid or 1. Cloud Policy 2. SharePoint PowerShell command -If you're new to Cloud Policy and looking to enable the Loop app for your organization during the public preview, you may appreciate a more step by step, all-in-one document for how to roll out Cloud Policy settings to your tenant. If so, check out this Tech Community blog: [Learn how to enable the Microsoft Loop app, now in Public Preview](https://techcommunity.microsoft.com/t5/microsoft-365-blog/learn-how-to-enable-the-microsoft-loop-app-now-in-public-preview/ba-p/3769013). +## Requirements -## Loop service requirements +Just like other Microsoft 365 experiences, Loop also leverages core services across SharePoint and Microsoft 365. To effectively enable Loop experiences or OneDrive and SharePoint files-backed experiences powered by Fluid Framework, follow the instructions in [Office 365 URLs and IP address ranges](/microsoft-365/enterprise/urls-and-ip-address-ranges) to ensure connections to Loop services. ++#### Security group for Cloud Policy ++You must create or use an existing security group that defines which users in your organization this policy will apply to. You can [learn more about creating groups in the Microsoft 365 admin center](/microsoft-365/admin/email/create-edit-or-delete-a-security-group) or [learn more about creating dynamic groups in AzureAD](/azure/active-directory/external-identities/use-dynamic-groups). You'll need this group for the Cloud Policy setup procedure below. ++#### Exchange Online license The Loop app currently requires each user to have an Exchange Online license. If not, users will experience failures in the Loop app, be unable to create new Loop workspaces, will not receive notifications or signals when users collaborate and update, and other experiences may also fail. -Loop's near real-time communications are enabled by the core services that run a WebSocket server. Coauthors in the same session need to establish secured WebSocket connections to this service to send and receive collaborative data such as changes made by others, live cursors, presence, etc. These experiences are crucial to Loop, and all the scenarios powered by Fluid framework. So, at the minimum, WebSocket will need to be unblocked from the user's endpoint. +#### WebSocket connections -Just like other Microsoft 365 experiences, Loop also leverages core services across SharePoint and Microsoft 365. To effectively enable Loop experiences or OneDrive and SharePoint files-backed experiences powered by Fluid Framework, follow the instructions in [Office 365 URLs and IP address ranges](/microsoft-365/enterprise/urls-and-ip-address-ranges) to ensure connections to Loop services. +Loop's near real-time communications are enabled by the core services that run a WebSocket server. Coauthors in the same session need to establish secured WebSocket connections to this service to send and receive collaborative data such as changes made by others, live cursors, presence, etc. These experiences are crucial to Loop, and all the scenarios powered by Fluid framework. So, at the minimum, WebSocket will need to be unblocked from the user's endpoint. ## Available policy settings The Loop experiences (except for Microsoft Teams) check the following Cloud Poli See the [Cloud Policy](/deployoffice/admincenter/overview-cloud-policy) setting templates for more information on the settings above. +> [!TIP] +> If you're new to Cloud Policy and looking to enable the Loop app for your organization during the public preview, you may appreciate a more step by step document for how to roll out Cloud Policy settings to your tenant. If so, check out this Tech Community blog: [Learn how to enable the Microsoft Loop app, now in Public Preview](https://techcommunity.microsoft.com/t5/microsoft-365-blog/learn-how-to-enable-the-microsoft-loop-app-now-in-public-preview/ba-p/3769013). + To configure these Cloud Policy settings: 1. Sign in to https://config.office.com/ with your Microsoft 365 admin credentials. 2. Select **Customization** from the left pane. 3. Select **Policy Management**. 4. Create a new policy configuration or edit an existing one.-5. In **Choose the scope**, choose the security group for which you want to apply the policy. - - **Note**: you MUST FIRST create a security group that defines which users in your organization this policy will apply to. You can [learn more about creating groups in the Microsoft 365 admin center](/microsoft-365/admin/email/create-edit-or-delete-a-security-group) or creating dynamic groups in AzureAD [here](/azure/active-directory/external-identities/use-dynamic-groups). If you do not create a group, the settings you configure will not apply to your users. +5. In **Choose the scope**, choose the security group for which you want to apply the policy. See [Security Group for Cloud Policy](#security-group-for-cloud-policy) for more information. If you do not apply to a security group, your settings will not take effect in your tenant. 6. In **Configure Settings**, choose one of the settings listed at the top of this section. 7. In configuration setting, choose one of the following: - For **Create and view Loop files in Microsoft apps that support Loop** - **Enabled**: Loop experience is available to users.- - **Disabled**: Loop experience is NOT available to users. + - **Disabled**: Loop experience is not available to users. - **Not configured**: Loop experience is available to users. - For **Create and view Loop files in Outlook** - **Enabled**: Loop experience is available to users.- - **Disabled**: Loop experience is NOT available to users. + - **Disabled**: Loop experience is not available to users. - **Not configured**: Loop experience is available to users. - For **Create and view Loop files in Loop** - **Enabled**: Loop app is available to users.- - **Disabled**: Loop app is NOT available to users. - - **Not configured**: Loop app is NOT available to users. (Loop during Public Preview is Opt-in by default) + - **Disabled**: Loop app is not available to users. + - **Not configured**: Loop app is not available to users. + - Loop during Public Preview is IT Admin Opt-in by default. + - Ensure additional [Loop service requirements](#requirements) are met. 8. Save the policy configuration. 9. Reassign priority for any security group if required. (If two or more policy configurations are applicable to the same set of users, the one with the higher priority is applied.) 10. In case you create a new policy configuration or change the configuration for an existing policy, there will be a delay in the change being reflected as follows: The feature will be available on Teams Windows Desktop, Mac, iOS, Android, and w To disable Loop components in Teams, run `Set-SPOTenant -IsLoopEnabled $false`. The change will take a short time to apply across your organization. If your organization has multiple regions (that is, organization URLs), you need to disable loop components for all the regions to have consistent results across the organization. -## eDiscovery --### Loop components +## eDiscovery for Loop components -Loop components created in Teams or Outlook are discoverable and have eDiscovery workflow support using the Microsoft Purview tool. Currently, these files are stored in the creatorΓÇÖs OneDrive for Business and are available for search and collection, and render in review for both eDiscovery (Standard) and eDiscovery (Premium). The HTML offline export format is supported on eDiscovery (Premium). You can also download and re-upload the files to any OneDrive for Business to view them in their native format. +Loop components created in Teams or Outlook are discoverable and have eDiscovery workflow support using the Microsoft Purview tool. Currently, these files are stored in the creatorΓÇÖs OneDrive and are available for search and collection, and render in review for both eDiscovery (Standard) and eDiscovery (Premium). The HTML offline export format is supported on eDiscovery (Premium). You can also download and re-upload the files to any OneDrive to view them in their native format. Microsoft is currently working on a third-party export API solution for Loop components. -### Loop app --The Loop app and content created in the Loop app does not yet support eDiscovery workflows. +> [!NOTE] +> The Loop app and content created in the Loop app does not yet support eDiscovery workflows. ## Related topics -- [Overview of Loop components in Teams](/microsoftteams/live-components-in-teams)-- [Use Loop components in Outlook](https://support.microsoft.com/office/9b47c279-011d-4042-bd7f-8bbfca0cb136)+[Overview of Loop components in Teams](/microsoftteams/live-components-in-teams) ++[Use Loop components in Outlook](https://support.microsoft.com/office/9b47c279-011d-4042-bd7f-8bbfca0cb136) |
| SharePoint | Install And Configure Workflow For Sharepoint Server | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/governance/install-and-configure-workflow-for-sharepoint-server.md | SharePoint Workflow Manager may be installed on the same servers as SharePoint o SharePoint Workflow Manager requires Azure Service Fabric, which must be installed before you run SharePoint Workflow Manager setup. If the Azure Service Fabric Runtime is not already installed, follow these steps below to install it: -1. The minimum version of Azure Service Fabric Runtime supported by SharePoint Workflow Manager is 9.0.1048.9590, and you can download it from [Azure Service Fabric Runtime](https://download.microsoft.com/download/b/8/a/b8a2fb98-0ec1-41e5-be98-9d8b5abf7856/MicrosoftServiceFabric.9.0.1048.9590.exe). Or you can find and download any higher version of its Windows Installer from [here](/azure/service-fabric/service-fabric-get-started#install-the-sdk-and-tools). +1. The minimum version of Azure Service Fabric Runtime supported by SharePoint Workflow Manager is 9.1.1583.9590, and you can download it from [Azure Service Fabric Runtime](https://download.microsoft.com/download/8/3/6/836E3E99-A300-4714-8278-96BC3E8B5528/9.1.1583.9590/Microsoft.Azure.ServiceFabric.WindowsServer.9.1.1583.9590.zip). Or you can find and download any higher version of its Windows Installer from [here](/azure/service-fabric/service-fabric-get-started). + 2. Open a PowerShell console as an elevated administrator and run the following command: - `.\MicrosoftServiceFabric.9.0.1048.9590.exe /accepteula` + `.\MicrosoftServiceFabric.9.1.1583.9590.exe /accepteula` 3. To verify the Azure Service Fabric is installed, you should be able to find it in the Programs and Features of the Control Panel. > [!NOTE]->SharePoint Workflow Manager supports the version 9.0 CU2 (9.0.1048.9590) of Azure Service Fabric and [higher versions](/azure/service-fabric/service-fabric-versions). You can install higher versions than that. If you want to directly upgrade your Azure Service Fabric without uninstallation, note that there are [upgrade dependencies](/azure/service-fabric/service-fabric-versions). If **Windows Fabric** is already installed on your machine, you must uninstall it before installing Azure Service Fabric. +>SharePoint Workflow Manager supports the version 9.1 CU2 (9.1.1583.9590) of Azure Service Fabric and [higher versions](/azure/service-fabric/service-fabric-versions). If you want to directly upgrade your Azure Service Fabric without uninstallation, note that there are [upgrade dependencies](/azure/service-fabric/service-fabric-versions). If **Windows Fabric** is already installed on your machine, you must uninstall it before installing Azure Service Fabric. ### Install SharePoint Workflow Manager Install both SharePoint Workflow Manager and SharePoint Workflow Manager Client Install SharePoint Workflow Manager Client on all servers in the SharePoint Server farm. ### Install and configure SharePoint Server-<a name="section3"> </a> Install and configure SharePoint Server. To do so, see [Install and deploy SharePoint Server Subscription Edition](../install/install.md). > [!NOTE] > The SharePoint 2010 Workflow platform installs automatically when you install SharePoint Server. The SharePoint 2013 Workflow platform requires either Microsoft Workflow Manager or SharePoint Workflow Manager and must be installed separately and then configured to work with your SharePoint Server farm. To function correctly SharePoint 2013 Workflows require that the App Management Service and Site Subscription Service are provisioned. It is not required to set up a wildcard certificate and DNS registration but both instances need to be running. +### Configure Workflow Manager farm and SharePoint Workflow Manager ++To create a Workflow Manager farm and join your servers to the farm, you can configure SharePoint Workflow Manager through the Workflow Manager Configuration Wizard, see [Video series Install and configure Workflow](/SharePoint/governance/video-series-install-and-configure-workflow-in-sharepoint-server-2013#episode-3-install-and-configure-workflow-manager). + ### Configure SharePoint Workflow Manager to work with the SharePoint Server farm <a name="section5"> </a> Follow the steps below to uninstall Microsoft Workflow Manager and install Share 7. If there is more than one server in your Workflow Manager farm, repeat the previous steps on all farm servers. 8. Run the Workflow Manager Configuration Wizard and rejoin the previous farm with the databases you noted in the previous steps on all servers in your Workflow Manager farm. > [!NOTE]- >There is no need to delete the existing Workflow Service Application Proxy, and there is no need to re-register SPWorkflowService. -- > [!NOTE] - > In some situations you might get a message that the Certificate Generation Key is invalid. If that happens, you should follow the instructions in the following article to reset the Certificate Generation Key: [Reset Certificate Generation Key for WorkFlowManager and ServiceBus](/archive/blogs/biztalknotes/reset-certificate-generation-key-for-workflowmanager-and-servicebus). + >There is no need to delete the existing Workflow Service Application Proxy, and there is no need to re-register SPWorkflowService. If you encounter the invalidity of the Certificate Generation Key for SharePoint Workflow Manager and Service Bus, you may reset it, see [Reset Certificate Generation Key](/archive/blogs/biztalknotes/reset-certificate-generation-key-for-workflowmanager-and-servicebus). 9. Rerun the Workflow Manager Configuration Wizard, select **Upgrade Workflow Manager Farm**, and confirm subsequent steps until the end. > [!NOTE] Follow these steps to validate that you have successfully installed and configur **To validate the installation** -1. Add a user to your SharePoint site, and grant the user Site Designer permissions. - -2. Install SharePoint Designer 2013 and create a workflow based on the SharePoint 2013 Workflow platform. For more information, see [Creating a workflow by using SharePoint Designer 2013 and the SharePoint 2013 Workflow platform](/sharepoint/dev/general-development/creating-a-workflow-by-using-sharepoint-designer-and-the-sharepoint-wo). - +1. Add a user to your SharePoint site, and grant the user Site Designer permissions. +2. Install SharePoint Designer 2013 and create a workflow based on the SharePoint 2013 Workflow platform. For more information, see [Creating a workflow by using SharePoint Designer 2013 and the SharePoint 2013 Workflow platform](/sharepoint/dev/general-development/creating-a-workflow-by-using-sharepoint-designer-and-the-sharepoint-wo). 3. Run this workflow from the SharePoint user interface. ## Troubleshooting |