Table of Contents
One Click to Make the Loop App Available to All Users
In an unannounced August 7 change (no blog post, no message center notification), Microsoft pushed an update to the Microsoft 365 admin center to introduce a one-click control in the Microsoft 365 admin center to enable Loop for a tenant. The new setting is located in the Services section of Org settings (Figure 1).
Selecting the option displays the screen shown in Figure 2. Click the option Microsoft Loop workspaces are available to all users in my organization and the job is done. There’s no need to configure SharePoint Online with PowerShell or deploy a cloud policy to enable users.
As explained in the Microsoft documentation, organizations now have two options to deploy Loop.
- Use the one-click approach to make Loop available to everyone.
- Use a cloud policy to restrict access to the set of user accounts specified in a group.
I’m all for making things easier, so view the new setting as a good change. It’s also indicative of the kind of change that happens as an app makes its way through preview toward general availability. When Loop reaches general availability, the app is likely to be available to all users by default. This is the normal approach taken by Microsoft and there’s no reason to believe that they’ll do something different for Loop.
One thing that might change with general availability is how to exert granular control over Loop so that some users can use the app and others cannot. Today, control is via a cloud policy. In the future, it might be via a service plan that’s part of the license assigned to user accounts.
What Happens Behind the Scenes
If you opt to enable Loop for everyone, the code behind the Microsoft 365 admin center option enables all the prerequisites for Loop and sets a tenant setting to allow Loop for all. It then checks if a cloud policy already exists. If a policy is in place, Microsoft updates its settings to allow the tenant setting to take precedence (Figure 3).
Loop PWA in Microsoft Store
Speaking of Loop, another recent change is the appearance of a Loop app in the Microsoft Store (Figure 4). This is a PWA wrapper around the Loop web app that allows Loop to install as a desktop app.
The good news is that the Loop PWA works well. I’ve been using it for a couple of weeks and haven’t run into any issues. It’s not a desktop app in the traditional sense, but it’s more than a good enough alternative.
Loop Everywhere
Apart from the Loop app, Loop components are available in Teams chat (but still not channel conversations), Teams meetings (agenda, notes, and to-do lists), OWA, Outlook desktop, and Outlook Monarch. The ecosystem is building out and appears to be on the way to replacing OneNote eventually. I’d like to make more use of Loop in my day-to-day work, but as most of my projects involve external people who don’t have user accounts in my tenant, the inability of Loop to accommodate collaboration with anyone except internal users is a block. Hopefully, Microsoft will lift that restriction soon.
So much change, all the time. It’s a challenge to stay abreast of all the updates Microsoft makes across Office 365. Subscribe to the Office 365 for IT Pros eBook to receive monthly insights into what happens, why it happens, and what new features and capabilities mean for your tenant.
I’ve observed this one-click Loop setting to be set by default to ‘on’ in my test tenant, and yet the Loop app only shows Loops from Microsoft Apps, and not the Loop Workspaces feature. Have you seen this defaulting to ‘on’? Is it possible we need cloud app policy for the Loop Workspace feature, even though the one-click policy is already on?
I have no idea because I can’t see the settings in your tenant. You can always ask the Microsoft support folk to check things out for you.