Microsoft Loop supported versions: what works, what doesn’t

Microsoft Loop is supported only in certain Microsoft 365 setups, and the exact experience depends on your account type, tenant settings, browser, and app version. In practice, Loop may show up in the web app, inside other Microsoft 365 apps, or not at all if one of those pieces is outside the supported path.

What Microsoft Loop is supported on right now

Microsoft Loop has three different surfaces, and each one can have different support rules: the Loop web experience, the Loop app, and Loop components inside other Microsoft 365 apps. That is why one person may be able to use Loop in Teams but not in the standalone app, or vice versa.

In practical terms, Loop is meant for current Microsoft 365 environments, especially work and school tenants. Support is tied to your Microsoft account type, your Microsoft 365 license, and the app or browser you are using. If any one of those is outside the supported path, you may still be able to sign in, but you might not see the Loop app, editing controls, or shared components.

For example, say you can open loop.microsoft.com in a supported browser, but Loop components still do not appear in Outlook. That usually points to an app version or tenant setting issue, not a problem with your account alone.

Boundaries matter here. Loop support in one place does not mean it is supported everywhere else in Microsoft 365. The web experience, the Loop app, and embedded components are related, but they are not interchangeable for support or rollout.

Which accounts and Microsoft 365 plans can use Loop

The first check is the account type. Loop for business is generally aimed at Microsoft 365 work and school accounts. If you sign in with a consumer Microsoft account, some Loop experiences may not be available, especially in places that depend on Microsoft 365 business services such as Teams or enterprise sharing.

For business and education use, eligibility also depends on the Microsoft 365 plan and the tenant configuration. Even with the right license, an admin can block Loop by turning off the service, restricting connected experiences, or limiting previews and cloud collaboration features. In other words, having a Microsoft 365 subscription is not always enough by itself.

A simple way to think about it is this: your license may say you can use Microsoft 365, but your tenant still decides whether Loop is turned on. If you are an admin, check the Microsoft 365 admin center and the relevant service or app settings for Loop, sharing, and connected experiences. If you are a user, ask whether your organization has intentionally disabled it before you keep troubleshooting your device.

For example, if the same user can open other Microsoft 365 services but Loop is missing, the account may be fine and the tenant may be the part that is restricting it.

Browsers, devices, and apps that actually work with Loop

Loop works best in current, supported browsers and up-to-date Microsoft apps. For the web experience, use a modern browser that Microsoft supports for Microsoft 365 web apps, such as the current versions of Microsoft Edge or Google Chrome. If you are using an older browser, a locked-down browser profile, or privacy settings that block cookies and cross-site sign-in, Loop may fail to load or save correctly.

For desktop use, the key point is not just the operating system, but the version of the Microsoft app. Loop components show up inside supported Microsoft 365 apps, most commonly in places like Teams, Outlook, and Word where Microsoft has enabled them. If the app is out of date, the Loop command may be missing even though the same feature appears in the browser.

On mobile, support is more limited than on desktop or web. If you need reliable editing, use the Loop web experience or a supported Microsoft 365 app on a current iOS or Android device. Mobile often works better for viewing and light edits than for full troubleshooting, especially if your organization is still rolling out Loop.

For example, if you can insert a Loop component in Teams on your laptop but not on your phone, that usually means the mobile app path is behind the desktop path, not that your account is broken.

If you are checking a specific device, confirm all three parts: the browser, the Microsoft app, and the platform. A current browser on an unsupported device, or a current device with an old app, can still leave Loop unavailable.

When Loop says no even though you’re signed in

A sign-in prompt does not mean Loop is actually available. The most common reason Loop appears unavailable is that one of the support gates is closed: unsupported browser version, outdated Microsoft app, missing license entitlement, or tenant policy.

Another common issue is account mismatch. You may be signed into a personal Microsoft account in the browser, but the feature you are trying to use only works with a work or school account. The reverse happens too: you may be in a company tenant, but the page or app is trying to use a personal profile.

Here are the failures people run into most often:

• The browser is current, but third-party cookies or tracking protection are blocking sign-in.
• The Microsoft app is installed, but it is not the version that includes Loop components.
• The tenant allows Microsoft 365, but Loop or connected experiences are disabled by policy.
• You are using a consumer account on a work-only feature path.
• The service is enabled, but your organization has not rolled it out to your user group yet.

If Loop is missing in one Microsoft app but present in another, that is usually a version or rollout issue, not a license issue alone.

This is also where the difference between the three Loop surfaces matters. Loop web can work when the standalone app is missing, and Loop components can be present in one Microsoft 365 app before they appear in another. That does not always mean something is broken; sometimes it just means the rollout is uneven.

How to check your version before you spend time troubleshooting

Start by checking the account type. In Microsoft 365 or Loop, open your profile or account menu and confirm whether you are signed in with a work, school, or personal account. If you can see your organization name or tenant, that is a good sign you are in a business environment.

Next, check the browser version if you are using Loop on the web. In Edge or Chrome, open the browser menu and look for the About page. You want a current release, not an old build that has been sitting unpatched.

Then check the Microsoft app version if you are using Loop components in Teams, Outlook, or Word. Open the app’s About or Version page and compare it with whatever your organization considers current. If your company manages updates, your app may be behind even if your computer looks up to date.

If you are an admin, confirm the license and tenant settings in the Microsoft 365 admin center before you chase device issues. That step saves time because it tells you whether the problem is at the account level or the client level.

A quick checklist can help before deeper troubleshooting:

• Confirm the signed-in account.
• Check the browser version if you are using the web app.
• Check the Microsoft app version if you are using Teams, Outlook, or Word.
• Confirm that Loop is allowed in the tenant settings.
• Verify whether your organization is using a staged rollout.

What to do if your version is close but still not supported

If you are close to the supported version but not quite there, update first. A browser update, a Microsoft 365 app update, or a Teams update often fixes missing Loop controls without any deeper change.

If the app is current and Loop still does not show up, switch to the Loop web experience. That is often the quickest way to tell whether the issue is the client or the tenant. If Loop works in the browser but not in the desktop app, you have narrowed the problem to the app version or feature rollout.

If neither path works, ask your Microsoft 365 admin to check the tenant settings for Loop, connected experiences, and any policy that might block collaborative components. If your organization is rolling Loop out gradually, you may also simply not be in the enabled group yet. In that case, the fix is policy, not troubleshooting.

If you are documenting the issue for support, note the exact app, browser, and account you used. That makes it much easier to separate a local version problem from a tenant-level restriction.

Conclusion

If you are checking Microsoft Loop before rollout, the fastest path is to verify three things: the account type, the Microsoft 365 tenant settings, and the exact browser or app version. If all three line up, Loop usually works in the web experience first, then inside supported Microsoft 365 apps. If one piece is off, fix that piece before you keep testing other devices or accounts.

Frequently Asked Questions

Can I use Microsoft Loop with a personal Microsoft account?

Some Loop experiences may be available outside a work or school tenant, but the business feature path is built around Microsoft 365 work and school accounts. If a feature depends on Teams, Outlook, or tenant sharing, a personal account usually will not be enough.

Why do I see Loop in Teams but not in Outlook?

That usually means the app versions or feature rollout are different. Loop components can appear in one Microsoft 365 app before another, especially if your organization is on a staged rollout or one app has not been updated.

Do I need the desktop app, or is the browser enough?

The browser is often enough for checking access and using the Loop web experience. For Loop components inside Microsoft 365 apps, you may need the current desktop or web version of the specific app you are using.

What should I check first if Loop is missing?

Check the account type, confirm the Microsoft 365 license or tenant setting, and then verify that your browser or Microsoft app is current. Those three checks catch most support problems.