Microsoft Loop startup problem: fix blank screen or loading

If Microsoft Loop opens to a blank screen, keeps loading, freezes on launch, or sends you back to sign-in, the problem is usually a browser issue, a Microsoft 365 account sign-in problem, a stuck cached session, or a Microsoft service or admin setting blocking access. The safest first fixes are to refresh, sign out and back in, try InPrivate or another browser, and check Microsoft 365 service status before you change anything bigger.

What the startup problem looks like

A Microsoft Loop startup problem usually shows up in one of a few ways. You click Loop and get a blank white screen, a spinner that never finishes, a page that freezes before your workspace appears, or a sign-in loop where Loop asks you to sign in again after you already did. Sometimes the app opens, but the workspace area never loads, or you can see the page frame with no content inside it.

Blank screen
Endless loading spinner
Freezes on launch
Sign-in loop
Workspace frame opens, but no content loads

If Loop is working normally, you should reach a landing page or a workspace, then open pages and components without being kicked back out. If the page never gets that far, the problem is usually happening before your content loads, not inside the document itself.

When this happens in Loop and when it does not

This advice fits the browser-based Microsoft Loop experience and most work or school accounts. It also helps when you use Loop through Microsoft 365 in a browser and the site itself will not finish loading.

It does not cover every possible app issue. If Loop is down for lots of people at the same time, the problem may be a Microsoft service outage. If your company blocks Loop for your tenant, no browser fix will make it appear until an admin changes the policy.

Before you start, you do not need administrator rights for the early steps. You should not need to back up anything for a refresh, sign-out, browser switch, or cache check. Start with these safe checks first:

• Make sure other Microsoft 365 sites load normally for you.
• Check whether Loop opens in another browser or in an InPrivate or private window.
• If this is a work account, note whether colleagues in the same tenant can open Loop.

If you use the desktop app or a wrapped app shell instead of the browser, the same sign-in and cache ideas still apply, but the exact menus can be different.

The first fixes to try, in the right order

Start with the least risky steps. The goal is to clear a temporary loading problem without changing your data or settings.

1. Refresh the page once. If Loop is open in a browser tab, press refresh and wait a full minute. Sometimes the first load stalls because a session token or script did not finish correctly. Expected result: the landing page or workspace appears. If nothing changes, move on. Do not keep hard-refreshing over and over; that can keep a bad session alive.
2. Sign out of your Microsoft account, then sign back in. Sign out of Loop and, if needed, out of the Microsoft 365 account in that browser. Then close the browser tab or window completely and sign in again. Expected result: Loop starts with a clean authentication session. If you still get a blank page or sign-in loop, the account session in the browser is probably stuck or your tenant is blocking access.
3. Check Microsoft 365 service status. If you have access to the admin center, check the service health page for Microsoft Loop and related Microsoft 365 services. If you do not have admin access, ask your IT team whether there is an incident or advisory. Expected result: you can confirm whether the problem is on Microsoft’s side. If there is an active outage, wait for Microsoft to resolve it. Browser changes will not fix a service-side failure.
4. Restart the browser, then try again. Close every browser window, not just the tab with Loop. Open the browser again and sign in once more. Expected result: any stuck tab process clears out. If it still fails, restart the computer too. That clears cached login components and background browser processes that a normal close can leave behind.
5. Try InPrivate or another browser. Open Loop in a private window first. If it works there, the problem is usually cached site data, an extension, or a browser profile issue. If it fails in the private window too, try a different browser. Expected result: one browser session loads Loop normally. If another browser works, the original browser profile is the likely cause. If no browser works, the issue is more likely account-related, tenant-related, or service-related.
6. Clear cache and site data for Loop and Microsoft 365 sites. Do this in the browser that fails, and clear only the site data you need if possible. You are looking for cached cookies, storage, or tokens that can stop Loop from finishing startup. Settings path: ``text title="Settings path" Browser settings > Privacy or Site data > Clear browsing data `` Expected result: Loop signs in with fresh site data and loads normally. If this does not help, an extension, a policy, or a tenant restriction may still be interfering.
7. Disable extensions that can interfere with sign-in or page loading. Focus on ad blockers, privacy tools, script blockers, security extensions, and anything that manages cookies. Reopen Loop after disabling them. Settings path: ``text title="Settings path" Browser menu > Extensions > Manage extensions `` Expected result: the page loads once the extension is out of the way. If that fixes it, re-enable extensions one by one to find the one causing the block.
8. Check whether your company has restricted Loop. If other people can use Loop but you cannot, ask whether your user account or group is allowed to use it. A tenant policy can block Loop even when your sign-in works elsewhere in Microsoft 365. Expected result: your admin confirms access is allowed, or changes the setting for your account. If only your account is affected, the issue may be a license, policy assignment, or conditional access rule on your side.

Do not reinstall, reset, or delete browser profiles as your first move. Those steps can make troubleshooting harder, and they are rarely needed before you have checked the browser, account, and service status.

How to tell whether the fix worked

The fix worked if Loop opens to a normal landing page, shows your workspace list, and lets you open a page without dropping you back to sign-in or freezing on a spinner. You should be able to click around for a minute or two and see content load normally each time.

A good sign is that Loop behaves the same after you close the tab, reopen it, and sign in again. If it only works once in a private window but not in your normal browser profile, the problem is still in your browser data or extensions, not in Loop itself.

If Loop still will not start after the steps above, collect the details that matter before you escalate: the browser name and version, whether private mode works, whether another browser works, and whether the problem affects only you or everyone in your tenant. That usually makes it much faster for IT or Microsoft support to trace the cause.

Conclusion

If Loop still will not start after a refresh, sign-out, browser test, and service check, the next move is to separate a personal browser problem from an account or tenant issue. Try one clean browser session, then bring those results to your IT admin with the exact symptom and when it started.

Frequently Asked Questions

Why does Microsoft Loop open to a blank screen?

Most often it is a browser session problem, a blocked cookie or script, or a temporary Microsoft 365 loading issue. Trying a private window and signing out and back in usually tells you which one it is.

Why does Loop keep asking me to sign in again?

That usually means the browser session, cookies, or account token is stuck. Clearing the site data for Loop and Microsoft 365 or using another browser often fixes it.

If Loop works for other people but not me, what should I check?

Check your browser cache, extensions, and whether your work account is allowed to use Loop in your tenant. If another browser or private window works, the problem is probably in your browser profile.