Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Note
The Copilot Pages and Copilot Notebooks content has moved to a dedicated article.
Loop components and their integrations are powered by .loop
files (earlier releases of Loop created these as .fluid
files), which are stored in OneDrive, SharePoint, or SharePoint Embedded. Storage for these files counts toward your organization's overall SharePoint quota. For details about where the content is stored, see storage and lifecycle. IT administrators can control the creation and use of Loop content through settings discussed in this article.
Two Admin Policy Tools
IT administrators must manage the creation of Loop components in the Microsoft 365 ecosystem using BOTH:
- Cloud Policy
- SharePoint PowerShell command (Loop experiences in Teams only)
Requirements
Loop components and Loop workspaces are a core service integrated into SharePoint and Microsoft 365. See requirements to learn more about configuration requirements, service connections, and license requirements.
Scoping Cloud Policy with Microsoft 365 Groups
To apply Cloud Policy settings to specific users, assign the policy to a Microsoft 365 group. For steps to create a group, see Create a Microsoft 365 group.
You can also use security or dynamic groups. For details, see Create, edit, or delete a security group and Create dynamic groups in Azure AD.
Note
If you apply the policy to all users in the tenant, group setup isn't required.
Available policy settings
There are several IT Admin policy settings provided to enable creation of Loop content across Microsoft 365:
Configure | Setting Type | Specific Policy | Notes |
---|---|---|---|
Loop workspaces creation | Cloud Policy | Create Loop workspaces in Loop | Applies to: Loop workspaces, including Teams channel workspaces |
Loop component creation and integration across Microsoft 365 | Cloud Policy | Create and view Loop files in Microsoft apps that support Loop | Applies to: - Outlook integration - Teams New Calendar integration - OneNote integration - Whiteboard integration Does NOT apply to: - Loop workspaces - Teams integration - Copilot Pages - Copilot Notebooks |
Outlook creation and integration of Loop experiences | Cloud Policy | Create and view Loop files in Outlook | First checks Create and view Loop files in Microsoft apps that support Loop; then applies Create and view Loop files in Outlook, if applicable. Applies to: - Outlook - Teams New Calendar |
Teams creation and integration | SharePoint property | See Settings management for Loop components in Teams | Teams only checks the settings in this row. |
Storage based view of the admin policy settings
Configure the creation of content in these locations by using the appropriate policy setting:
Loop content originally created in | ️️️Manage with this policy | Loop content storage |
---|---|---|
Loop app, My workspace | Cloud Policy: Create Loop workspaces in Loop | SharePoint Embedded: ✔️in user-owned container |
Loop app, shared workspace | Cloud Policy: Create Loop workspaces in Loop | SharePoint Embedded: ✔️in shared container |
Teams channel, shared workspace | Cloud Policy: Create Loop workspaces in Loop | SharePoint Embedded: ✔️in shared container |
Teams channel meeting (Teams Classic Calendar) | SharePoint property Set-SPOTenant -IsCollabMeetingNotesFluidEnabled $true |
SharePoint Site: 📁Meetings |
Teams channel meeting (Teams New Calendar) | Cloud Policy: Create and view Loop files in Microsoft apps that support Loop -or- Create and view Loop files in Outlook | SharePoint Site: 📁Meetings |
Teams channel | SharePoint property Set-SPOTenant -IsCollabMeetingNotesFluidEnabled $true |
SharePoint Site: ✔️in Channel folder |
Teams private chat | SharePoint property Set-SPOTenant -IsLoopEnabled $true |
User's OneDrive: 📁Microsoft Teams Chat files |
Teams private meeting (Teams Classic Calendar) | SharePoint property Set-SPOTenant -IsLoopEnabled $true |
User's OneDrive: 📁Meetings |
Teams private meeting (Teams New Calendar) | Cloud Policy: Create and view Loop files in Microsoft apps that support Loop -or- Create and view Loop files in Outlook | User's OneDrive: 📁Meetings |
Outlook email message | Cloud Policy: Create and view Loop files in Microsoft apps that support Loop -or- Create and view Loop files in Outlook | User's OneDrive: 📁Attachments |
OneNote for Windows or for the web | Cloud Policy: Create and view Loop files in Microsoft apps that support Loop | User's OneDrive: 📁OneNote Loop files |
Whiteboard | Cloud Policy: Create and view Loop files in Microsoft apps that support Loop | User's OneDrive: 📁Whiteboard\Components |
Example configurations
Scenario | Policies Configured |
---|---|
✅Enable Loop workspaces creation and Loop component creation and integration everywhere | ✅ Create Loop workspaces in Loop = Enabled (or Not Configured) ✅ Create and view Loop files in Microsoft apps that support Loop = Enabled (or Not Configured) ✅ [Teams-only] Set-SPOTenant -IsLoopEnabled $true , Set-SPOTenant -IsCollabMeetingNotesFluidEnabled $true |
✅Enable Loop workspaces creation and Loop component creation and integration everywhere, but ⛔Disable Loop component creation and integration in Communication apps (Outlook, Teams) | ✅ Create Loop workspaces in Loop = Enabled (or Not Configured) ✅ Create and view Loop files in Microsoft apps that support Loop = Enabled (or Not Configured) ⛔ Create and view Loop files in Outlook = Disabled ⛔ [Teams-only] Set-SPOTenant -IsLoopEnabled $false , Set-SPOTenant -IsCollabMeetingNotesFluidEnabled $false |
⛔Disable Loop workspace creation and Loop component creation and integration everywhere | ⛔ Create Loop workspaces in Loop = Disabled ⛔ Create and view Loop files in Microsoft apps that support Loop = Disabled ⛔ [Teams-only] Set-SPOTenant -IsLoopEnabled $false , Set-SPOTenant -IsCollabMeetingNotesFluidEnabled $false |
User experience expectations when admin settings are configured
IT administrators can control whether users in their organization can create new Loop content. However, these admin controls do not restrict access to existing Loop files or workspaces. Admin controls can be applied to specific groups or the entire tenant, except for Teams-related settings, which always apply tenant-wide.
- To restrict collaboration between specific groups, use Information Barriers where supported.
- To block access to existing Loop content or the Loop app, use Conditional Access policies.
Expected user experience when Loop creation is disabled
Refer to the Loop experience examples based on admin settings article for details and screenshots.
Settings management in the Microsoft Admin Center
If you're looking for a simple way to turn on or off the creation of only Loop workspaces in your tenant, do the following:
Sign in to the Microsoft 365 admin center as Office Apps Administrator, Security Administrator, or Global Administrator.
Important
Microsoft recommends that you use roles with the fewest permissions. This helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role.
Navigate to Home > Org settings > Services > Loop.
Choose your desired state for Loop workspaces via the checkbox.
Note
The checkbox may not reflect your configured state on load. However, the state you select and choose Save in the Admin Center will persist and override any defaults for your tenant.
Select Save.
The Microsoft Admin Center configures the Cloud Policy setting Create Loop workspaces in Loop, described in the next section, targeted at All users (your full tenant). See the next section if you wish to perform more advanced controls. If you configured Create Loop workspaces in Loop in Cloud Policy, review your Cloud Policy settings to confirm they still match your expectation after configuring in the Microsoft Admin Center.
Settings management in Cloud Policy
Copilot Pages, Copilot Notebooks, and the Loop experiences (except for Microsoft Teams) check the following Cloud Policy settings. See Available policy settings to understand how each app checks these settings:
- Create Loop workspaces in Loop
- Create and view Loop files in Microsoft apps that support Loop
- Create and view Loop files in Outlook
- Sign in to https://config.office.com/ with your Microsoft 365 admin credentials.
- Select Customization from the left pane.
- Select Policy Management.
- Create a new policy configuration or edit an existing one.
- From the Choose the scope dropdown list, choose either All users or select the group for which you want to apply the policy. For more information, see Microsoft 365 Groups for Cloud Policy.
- In Configure Settings, choose one of the following settings:
- For Create Loop workspaces in Loop:
- Disabled: Creation of Loop workspaces isn't available to the users.
- Loop app will open Loop components when workspaces is disabled.
- Enabled: Creation of Loop workspaces is available to the users.
- Not configured: Creation of Loop workspaces is available to the users.
- For Create and view Loop files in Microsoft apps that support Loop:
- recall:
- this setting applies to:
- Outlook integration
- Teams New Calendar integration
- OneNote integration
- Whiteboard integration
- this setting does NOT apply to:
- Loop workspaces
- Teams integration (see Settings management for Loop components in Teams)
- Copilot Pages
- Copilot Notebooks
- this setting applies to:
- Enabled: Creation of Loop components and integration is available to the users.
- Disabled: Creation of Loop components and integration isn't available to the users.
- Not configured: Creation of Loop components and integration is available to the users.
- recall:
- For Create and view Loop files in Outlook (includes Outlook and Teams New Calendar):
- Enabled: Creation of Loop components and integration is available to the users.
- Disabled: Creation of Loop components and integration isn't available to the users.
- Not configured: Creation of Loop components and integration is available to the users.
- For Create Loop workspaces in Loop:
- Save the policy configuration.
- 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.)
In case you create a new policy configuration or change the configuration for an existing policy, there can be a delay in the change being reflected as described below:
- If there were existing policy configurations prior to the change, then it will take 90 mins for the change to be reflected.
- If there were no policy configurations prior to the change, then it will take 24 hours for the change to be reflected.
Note
To enable a Cloud Policy for only a specific subset of users:
- Create Group A containing the users you want to enable the policy for. Assign the Cloud Policy to this group and set it to Enabled.
- Create Group B that includes All users. Assign the same Cloud Policy to this group and set it to Disabled.
- Set the priority for Group A to a lower number (for example, priority 0) so it is evaluated before Group B (for example, priority 1).
In Cloud Policy, lower priority numbers are evaluated first. This ensures users in Group A have the policy Enabled, while all other users in Group B have it Disabled.
Settings management for Loop functionality in Teams
You'll need the latest version of SharePoint PowerShell module to enable or disable Loop experiences in Teams. Loop components default to ON for all organizations. Because Loop components are designed for collaboration, the components are always shared as editable by others, even if your organization is set to create shareable links that have view-only permissions as the default value for other file types. For more information, see the Learn more link next to the setting.
Experience | SharePoint organization properties | Notes |
---|---|---|
Loop components in Teams | IsLoopEnabled (boolean) |
This property controls Loop component creation and integration in Microsoft Teams. It applies to the entire tenant and can't be configured at the user level. |
Collaborative meeting notes | IsCollabMeetingNotesFluidEnabled (boolean) |
This property controls the collaborative meeting notes creation and integration in Microsoft Teams. It applies to the entire tenant and can't be configured at the user level. The SharePoint organization property doesn't apply to collaborative meeting notes in Teams New Calendar, see Settings management in Cloud Policy. |
To check your tenant's default file permissions, perform the following steps:
- Sign in to Microsoft 365 admin center.
- Under Admin centers, select SharePoint.
- Select Policies > Sharing, and under File and folder links, view your organization's default file permissions.
To check if Loop components are enabled, run Get-SPOTenant
without any arguments. Verify the value of IsLoopEnabled
is true.
To enable Loop components in Teams, run Set-SPOTenant -IsLoopEnabled $true
. The change will take a short time to apply across your organization.
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.
Related topics
- Summary of Compliance, Lifecycle, Governance
- Requirements
- Storage
- Permissions
- UX examples for admin toggle states
- Managing SharePoint Embedded containers
- Overview of Loop components in Microsoft 365
- Use Loop components in Outlook
- Use Loop components in OneNote
- Loop components in Whiteboard
- Get started with Microsoft Loop - Microsoft Support