Microsoft Planner connection problem: fix sign-in and sync

If Microsoft Planner won’t load, keeps spinning, won’t sync, or keeps sending you back to sign-in, the cause is usually a stale session, a Microsoft 365 service issue, a Teams or browser cache problem, or an account or permission change. The quickest safe fixes are to refresh the session, check Microsoft service health, sign out and back in, and try Planner in a private window or another browser. If it works in one place but not another, that usually tells you whether the problem is Planner itself, Teams, Microsoft 365 sign-in, or your network.

What the connection problem looks like

Planner connection issues usually show up in a few predictable ways: the page never finishes loading, you get an endless spinner, the plan opens but tasks won’t save, changes don’t appear on another device, or you get sent back to sign in over and over. In Teams, you may see a blank tab, a message that the app couldn’t load, or a plan that works in the browser but not inside Teams.

Sometimes the failure is less obvious. You can open Planner, but tasks won’t update until much later, attachments refuse to load, or a board seems frozen after you switch accounts. If you recently changed your password, approved an MFA prompt, or moved between work accounts, that’s a strong clue that the session itself is stale rather than Planner being fully down.

The key question is not just whether Planner is broken, but where it is broken. If the same problem happens in the web app, Teams, and mobile, think service or account. If it happens in only one place, think cache, app data, or a local sign-in issue.

Symptom

The exact message varies

This problem shows up when Planner won’t finish loading, keeps looping back to sign-in, won’t save changes, or works in one place but not another. In Teams, the symptom is often a blank tab or a Planner app that won’t open at all.

Before you start

This applies to Microsoft Planner in Microsoft 365, including Planner in the web app, Planner or Tasks in Teams, and the mobile app. No administrator rights are needed for the first checks, but you may need access to sign out, clear browser data, or open service health if you are an admin.

You do not need to restart anything to start troubleshooting, and you do not need to back up your plan before the first fixes. As a safe first check, try Planner in a private or incognito window. Also check whether Outlook, OneDrive, or SharePoint are having the same sign-in or loading problem, because that points away from Planner itself.

Is it Planner, Teams, your browser, or Microsoft 365?

Before you change anything, narrow down the scope. Open Planner in the web app, then check the same plan in Teams if your organization uses the Planner or Tasks app there. If you can, also check from another device or the mobile app. The pattern matters more than the exact message.

Use this quick split:

• Fails everywhere: likely Microsoft 365 sign-in, tenant permissions, or a service outage.
• Works in the browser but not in Teams: likely a Teams app cache or Teams sign-in problem.
• Works on one device but not another: likely local browser data, app cache, or a device-specific sign-in session.
• Loads but won’t sync changes: often a permissions issue, a stale token, or a temporary service problem.

If other Microsoft 365 apps are also acting up, such as Outlook, OneDrive, or SharePoint, that points away from Planner itself and toward account or tenant health. If only Planner is affected, the fix is usually narrower and less disruptive.

Try the quickest fixes first

Start with the least risky steps. These usually fix expired sessions and broken cached data without changing anything in your plan.

1. Refresh Planner in the place where it fails.

If the page is half-loaded or stuck spinning, reload it once. In Teams, close the Planner tab and open it again. The expected result is that the plan loads normally. If it still spins or bounces back to sign-in, move on.

2. Sign out of Microsoft 365, then sign back in.

Use the sign-out option for the app or browser, then reopen Planner and authenticate again. This clears many expired-session problems, especially after a password change or MFA update. The expected result is that Planner opens without a sign-in loop. If it does not, the session problem is probably still cached somewhere else.

3. Check Microsoft service health.

If you have access to the Microsoft 365 admin center, look at service health for Planner and related Microsoft 365 services. If you do not have admin access, ask someone who does whether there is an active incident. The expected result is a clear service status, or an incident that matches what you are seeing. If there is an outage, local fixes will not help much.

4. Try a private or incognito window.

This helps you separate a broken browser session from an account problem. If Planner opens there, your normal browser data is likely the issue. If it still fails, the problem is less likely to be just cached browser data.

5. Clear site data for Microsoft 365 and try again.

Use your browser settings to clear cached data for Microsoft sites, then sign in again.

Browser settings > Privacy and security > Cookies and other site data > See all site data and permissions > search for Microsoft or office.com > remove site data

Clearing site data can sign you out of other Microsoft services in that browser. Save anything unfinished first.

If Planner works after one of these steps, the issue was most likely a stale token or cache entry. If none of them change the behavior, the problem is probably not just on your device.

When the problem is only in one place

If Planner works in the browser but not in Teams, the problem is usually inside Teams rather than Planner itself. Close Teams completely, reopen it, and try again. If the tab still fails, your Teams cache or Teams sign-in state may be stuck. The practical sign is that the same plan opens normally in the browser but keeps failing in Teams.

If the mobile app is the only place that fails, check whether the app needs you to sign in again, whether the phone has a pending system update, and whether the app has been paused by a battery or data-saving setting. Mobile sync problems often show up after a password reset, an MFA change, or a long period of inactivity.

If the issue started right after a password change, a password reset, or an MFA prompt, you may simply have an expired token in one app. Signing out everywhere you can reach, then signing back in to the affected app, often clears that up. If you see an approval prompt that never appears, make sure you are using the right authenticator account and the right phone number or device.

If one browser works and another does not, the broken one probably has stale cookies or cached site data. That is a good sign because it usually means the account itself is fine.

How to confirm it’s actually fixed

A fix is real only if Planner behaves normally in the place that failed before. Open a plan, switch between buckets or views, and confirm the tasks load without delays or blank sections. Then change something small, such as a task title or status, and make sure the change saves without an error.

If you use Planner in more than one place, check the second place too. For example, if you fixed the browser version, open the same plan in Teams and confirm it loads there as well. If you fixed a mobile issue, make a small update on the phone and see whether it appears in the browser after a refresh.

A successful recovery usually looks like this:

• Plans open without endless loading.
• Sign-in does not loop.
• Changes save on the first try.
• Updates appear in the other app or device after a short refresh.

If the same failure comes back after you close and reopen the app, the underlying issue is not fully fixed yet. That usually means the problem is still with the session, the tenant, or permissions rather than a one-time cache glitch.

When you need your IT admin or Microsoft support

Bring in IT if the problem affects more than one person, more than one device, or more than one Microsoft 365 app. That pattern usually points to a tenant-wide outage, a policy change, or a service health issue that you cannot repair yourself. It also points to problems with licensing or permissions if you can open Planner but specific plans, groups, or tabs fail to load.

Ask for help sooner if any of these are true:

• Planner fails for many users in your organization.
• The problem started after an admin change, migration, or license update.
• You can sign in, but specific plans or groups are missing.
• The browser works, but Teams fails for everyone.
• You see repeated permission or access errors after you have already signed out and back in.

When you hand it off, give IT the exact place it fails, the device or app involved, and what you already tried. That shortens the back-and-forth. If they confirm a Microsoft incident, waiting is usually the only safe move until the service clears.

Conclusion

If Planner is broken right now, start with the session: refresh, sign out, sign back in, and test in a private window. If that does not help, compare browser, Teams, and mobile to see where the break actually lives. If it still fails everywhere, hand it to your admin with the exact symptom and the places you tested so they can check service health, permissions, or tenant issues.

Frequently Asked Questions

Why does Microsoft Planner keep asking me to sign in again?

That usually means your session token is expired, your browser is holding stale Microsoft cookies, or an MFA or password change left one app out of sync. Signing out and back in, then testing in a private window, usually shows which one it is.

Why does Planner work in the browser but not in Teams?

That often points to a Teams cache or Teams sign-in problem rather than Planner itself. If the web version works normally, Teams is the place to focus first.

Can a Microsoft 365 outage break Planner?

Yes. If Planner fails for multiple people or across devices, service health or a tenant-level issue is a likely cause. If other Microsoft apps are also affected, that makes an outage more likely.