Microsoft Planner service status and what to do next

If Microsoft Planner won’t open, won’t save tasks, or keeps spinning, start by checking Microsoft 365 service health for Planner, Teams, and Microsoft 365. If Microsoft shows an active incident, the right move is usually to wait; if it doesn’t, the problem is more likely your browser, device, network, or tenant settings.

Is Microsoft Planner down right now?

If you have access to the admin center, check the service health page first and look for any active incident or advisory affecting Planner, Microsoft 365, or Teams.

Microsoft 365 admin center > Health > Service health

If you see an incident that matches what you’re seeing, that usually explains the problem. In that case, local troubleshooting probably won’t fix it right away.

Planner boards do not load, tasks do not save, or updates lag behind what you just changed.

Those symptoms usually show up when Planner is disrupted for a tenant or more broadly in Microsoft 365. If the service health page is clean, keep checking your own browser, device, and account setup before you assume Microsoft is at fault.

A lack of an incident does not prove everything is healthy, but it does make a local cause more likely.

When this is a Microsoft problem and when it isn’t

A Microsoft problem usually affects more than one person, shows up in more than one place, and often lines up with the health dashboard. If Planner fails in the browser, in Teams, and on mobile for several coworkers at the same time, that points to a service issue or a tenant-wide issue.

A tenant-specific issue looks different. For example, only one group, one plan, or one user may be affected because of permissions, licensing, or a policy set by your admin. In that case, Planner itself may still be working, but your account or the plan’s sharing settings are blocking you.

A browser- or device-specific problem usually stays on one machine or one browser. If Planner opens in Edge but not in Chrome, or it works in a private window but not in your normal session, that usually points to cached data, cookies, an extension, or a sign-in session problem rather than a Microsoft outage.

Before you start, this applies to Planner in the web app, Planner in Microsoft 365, and Planner inside Teams. Most of the checks below need no admin rights. If you’re an admin, you may need access to the Microsoft 365 admin center for the service health dashboard and tenant checks. No restart or backup is usually needed for the first round of checks, and the safest first steps are to compare behavior across another browser and another device.

What to check first on your side

Start with the checks that are easy to reverse and least likely to make things worse. You’re trying to separate a Microsoft outage from a local issue without changing anything permanent.

1. Check the Microsoft 365 Service health dashboard if you can access it.

Microsoft 365 admin center > Health > Service health

If Planner, Microsoft 365, or Teams shows an incident, stop looking for a local fix unless you also need a workaround for your own workflow.

2. Open Planner in another browser.

If it works there, your original browser is the problem. That usually means cached site data, cookies, or an extension is interfering.

3. Try an incognito or private window.

If Planner works there, the issue is usually tied to your normal browser profile, saved session, or an extension.

4. Test another device.

If Planner works on your phone but not your laptop, or the other way around, you’ve narrowed it to the device or browser rather than the service.

5. Try another network if you can.

A VPN, proxy, or restrictive corporate network can interfere with sign-in or loading. If the app works on a mobile hotspot but not on your office network, that’s a useful clue.

6. Use the mobile app if it’s available to you.

If the web version is flaky but the app works, you can keep moving while you wait for the underlying problem to clear.

If none of those checks changes anything, and the service health dashboard is clean, the problem is more likely tenant-specific or tied to your account session. That’s the point where an admin should check permissions, licensing, and any recent policy changes.

How to confirm Planner is working again

Don’t tell the team the issue is fixed just because the page loads once. Confirm that Planner behaves normally from end to end.

1. Open the affected plan in the web app.

You want the board to load without a long delay, blank sections, or repeated refreshes.

2. Create or edit a test task.

Save a small change, such as a title edit or a due date change.

3. Refresh the page and check that the change is still there.

If the edit persists after refresh, that’s a good sign the save path is working again.

4. Check a second location where the same plan appears, such as Teams or the mobile app, if you use those.

If the change shows up there too, sync is likely back to normal.

5. Ask one other person in the same tenant to check the same plan.

If they can load and edit it too, you’ve got a better signal that the issue is resolved for the tenant, not just for your browser.

The expected result is simple: the plan loads, edits save, and those edits appear consistently across the places your team uses Planner. If that doesn’t happen, the outage may be partial or still settling down.

What to do if Planner still won’t load after the status says it’s fixed

Sometimes Microsoft marks an incident as resolved before your browser or device fully catches up. In that case, the service may be back, but your local session is still stuck.

1. Sign out of Microsoft 365 in the browser, then sign back in.

This clears a stale session without changing anything permanent.

If that does not help, clear the site data for Microsoft 365 and Planner in your browser, then try again.

The expected result is that Planner signs in cleanly and loads your board. If it still fails, the problem is probably not just a stale session.

2. Try Planner with browser extensions turned off or in a clean browser profile.

Browser extensions can get in the way, especially ad blockers, privacy tools, or script blockers. If Planner works there, re-enable your extensions one by one until you find the one causing the problem.

3. Open Planner directly instead of through Teams, or use Teams if you started in the web app.

A problem can be specific to one host app even when Planner itself is fine. If one route works and the other does not, that points to the app shell rather than the service.

4. Check the same plan on another device or in the mobile app before telling your team the issue is over.

If the plan loads, your edits save, and the changes show up in more than one place, you can be more confident the fix has stuck.

If the issue only affects you after the service health page says the incident is over, ask your admin to check whether your account still has a cached session problem, a policy issue, or a permissions change. If several people are still affected, the incident may not be fully closed in practice even if the status page says it is.

Conclusion

If Planner is down for everyone, wait for Microsoft and keep an eye on the service health dashboard. If it’s only affecting you, compare browsers, devices, and networks until you find the narrowest cause. Once the plan loads and saves normally in more than one place, it’s safe to tell your team the issue is resolved.

Frequently Asked Questions

Where do I check Microsoft Planner service status?

Use the Microsoft 365 admin center and open Health > Service health. Check Planner, Microsoft 365, and Teams, since Planner problems can show up in those services too.

What symptoms usually mean Planner is having a service disruption?

Common signs are boards not loading, tasks not saving, pages spinning or timing out, and sync delays where changes take a while to appear in Teams or on mobile.

How can I tell if it’s my browser or device instead of Microsoft?

If Planner works in another browser, a private window, another device, or on mobile data but not on your normal setup, it is usually a local browser, device, or network issue rather than a Microsoft outage.

How do I know Planner is really fixed before I tell my team?

Open the affected plan, make a small edit, refresh, and confirm the change is still there. Then check the same plan in another place, such as Teams or the mobile app, and if possible ask one other person in the tenant to confirm it works for them too.