Microsoft Planner not connecting — diagnose and fix it

If Planner opens but doesn't load or sync, the cause is either local (browser, device, network, or account) or tenant/service-side (license, Azure AD, conditional access, or a Microsoft outage). Start with quick local checks: sign out and back in, try incognito, clear browser cache, or test from another device or network. If those don't work, run tenant-level checks (licenses, Microsoft 365 Group membership, Azure AD sign-in logs, conditional access) and collect HAR and sign-in logs before contacting Microsoft support.

Is Planner down for everyone or just you

Planner page loads but stays spinning, shows an error, or does not display plans or tasks; sync doesn't complete.

When it appears

This happens when you open planner.office.com, the Planner tile in Microsoft 365, or the Planner app and content fails to render or update. It can be a global outage, a regional Microsoft problem, or a tenant-level misconfiguration.

Where to act: Microsoft 365 admin center (privileges: global admin or service admin for Service health).

1. Ask your Microsoft 365 admin to sign into the admin center and open Service health.
2. If you are an admin, open Service health in the Microsoft 365 admin center and look for incidents affecting Planner, Microsoft 365 Groups, SharePoint, or authentication.
3. Use a third-party status checker as a quick sanity check if you can't reach an admin; treat third-party reports as signals, not proof.

Expected result: Service health shows no active incidents for Planner or related services.

What it means if that did not happen: If Service health shows an active incident, follow any guidance there or wait for Microsoft updates. If no incident exists, continue with local and tenant-level troubleshooting.

Have you ruled out basic local problems (browser, app, account)

Before you start

• Product and versions: Planner in modern browsers (Chrome, Edge, Firefox) and Planner mobile apps (iOS/Android). Applies to current app and browser releases.
• Privileges: Normal user. Admin rights are not required for these checks.
• Safe checks: Sign out/in, try an alternate device or network, and use an incognito/private window.

Where to act: your browser or device (privileges: normal user).

1. Sign out of Office and sign back in.
2. Open a private/incognito window and sign into Planner.
3. Clear your browser cache.

Chrome: Settings > Privacy and security > Clear browsing data
Edge: Settings > Privacy, search, and services > Choose what to clear
Firefox: Settings > Privacy & Security > Cookies and Site Data > Clear Data

Expected result: Planner loads or shows a fresh authentication prompt. If Planner still fails, the problem is less likely to be stale cache.

4. Try a different browser or another device using the same Azure AD account.

Expected result: If Planner works elsewhere, the original browser/profile is the problem (extensions, cookies, or a corrupted profile).

5. If on mobile, update the Planner app from the App Store/Play Store and force‑close the app before relaunching.
6. Confirm you are signed into the correct Azure AD account. If you have multiple Microsoft accounts, sign out of personal accounts and sign in with your work/school account.

What it means if these steps didn’t help: If Planner still won’t connect after these checks, move to network and tenant checks.

Could network or corporate security be blocking Planner

Where to act: network or device (privileges: normal user for quick tests; admin privileges may be needed for traceroute, DNS or firewall checks).

1. Test with a different network: connect the device to a mobile hotspot and open Planner.

Expected result: Planner works on the hotspot -> a corporate network/proxy/firewall is likely blocking required endpoints.

2. Run a traceroute to planner.office.com to check routing.

tracert planner.office.com

Expected result: A route to Microsoft service IPs with no abrupt timeouts near your network edge. If the trace fails early, the block is on your network.

3. Check DNS resolution using a public DNS temporarily (for example 1.1.1.1 or 8.8.8.8).
4. Ask your network or security team whether they block or inspect TLS traffic, specific Microsoft domains, or user agents. Provide this short checklist of endpoints and protocols Planner depends on:

• Office 365 / Microsoft 365 service endpoints (including Microsoft 365 Groups and SharePoint Online)
• Standard HTTPS (port 443) and OAuth endpoints used for authentication

Expected result: Network team confirms these endpoints and ports are allowed. If blocked, request an exception for Microsoft 365 services or a split-tunnel for cloud apps.

What it means if this did not fix the issue: If Planner still fails on a mobile hotspot, the issue is likely tenant or account-related rather than the corporate network.

Is it a tenant, license or permission problem

Before you start

• Privileges: Microsoft 365 admin or license manager.
• Safe checks: Do not delete groups or change user accounts without confirmation.

Where to act: Microsoft 365 admin center and Azure AD portal (privileges: admin).

1. Verify the user has a license that includes Planner. In the admin center, check the user's assigned licenses.

Microsoft 365 admin center > Users > Active users > select user > Licenses and Apps

Expected result: The license SKU is assigned and Planner is enabled. If Planner or required apps are not assigned, enable them and ask the user to sign out/in.

2. Confirm the user is a member of the Microsoft 365 Group that backs the plan. Planner uses Microsoft 365 Groups; incorrect membership prevents access to the plan.
3. Check whether the group's SharePoint site was deleted, blocked, or is otherwise unhealthy. If the SharePoint site is unavailable, Planner can fail to load tasks.
4. Inspect tenant settings that restrict group creation or block Exchange/SharePoint integration; these settings can break Planner indirectly.

Expected result: User has the right license, is in the correct group, and group resources (SharePoint site) are healthy. If not, restore the group or assign the correct license.

What it means if these checks did not resolve it: If licensing and group membership look correct, proceed to Azure AD and conditional access checks.

Are conditional access, MFA or Azure AD issues causing the problem

Where to act: Azure AD (privileges: Azure AD admin) and the user's device for MFA prompts.

1. Check the Azure AD sign-in logs for the affected user at the time they attempted to access Planner. Look for failures, conditional access policy names, and error codes.

Expected result: Sign-in shows success or an explicit conditional access block with a policy name. If a policy blocked access, the log will identify which policy and why (device compliance, location, legacy auth, etc.).

2. Common causes to look for:

• Conditional access policy blocking unregistered or noncompliant devices.
• MFA prompts failing or timing out.
• Conflicting or stale device registrations marking a device noncompliant.

3. If you find a conditional access block, either adjust the policy for the user's scenario temporarily or remediate the device compliance issue.
4. Copy error codes exactly from sign-in logs to include in support requests. The exact message varies; include the code and the conditional access policy name if present.

What it means if this did not fix the issue: If sign-in logs show successful authentication with no CA blocks, the problem likely lives in service configuration or an intermittent Microsoft backend issue. Collect logs and escalate to support.

How to collect logs, reproduce the issue and escalate to support

Before you call Microsoft support, gather evidence so support can act quickly.

What to capture (minimum set):

• Exact time (UTC) when the failure occurred.
• Tenant ID and affected user UPN(s).
• Screenshots of the error or the stuck UI.
• HAR file from the browser network tab or a Fiddler capture showing failing requests and responses.
• Azure AD sign-in log entries for the user with timestamps and error codes.
• Microsoft 365 admin center Service health entries that match the time range.

1. Reproduce the issue while capturing a HAR file.

A HAR contains sensitive tokens. Share it only with trusted admins or Microsoft support.

2. To export a HAR in Chrome/Edge:

• Open DevTools (F12) > Network tab > check Preserve log > reproduce the failure > right-click the network list > Save all as HAR with content.

3. Capture the browser console errors and the failing HTTP responses from the network tab as screenshots or text copies.
4. Export the Azure AD sign-in log rows: filter by user and time, then export the CSV which includes error codes and conditional access results.

How to escalate: When you open a support ticket, include tenant ID, UPNs, exact UTC timestamps, HAR file, sign-in log export, screenshots, and a concise reproduction sequence. Use the Microsoft 365 apps or Planner support category and reference any conditional access policy names or error codes you found.

Expected result: Support can reproduce the failure from your HAR/logs and identify whether the issue is client-side, tenant-side, or a Microsoft service incident.

What it means if support asks for more: Provide screenshots of Service health in the admin center and state whether the issue is isolated to a user, a group, or the whole tenant.

Verify the fix and prevent recurrence

Where to act: browser/device and admin portals (privileges vary by step).

1. Sign in as the affected user in a browser where you cleared the cache or used incognito and open planner.office.com.

Expected result: Plans and tasks load and changes sync immediately.

2. Edit a task (change title or due date) and confirm the change appears using a different device or account.

Expected result: The edit replicates within seconds across devices.

3. If the issue was tenant-side, have an admin confirm license assignment, Microsoft 365 Group integrity, and that no conditional access policy will block normal use going forward.
4. Prevent recurrence:

• Document the environment and steps that caused the failure (browser, extensions, network configuration).
• For tenant issues, add a process: verify license changes and group deletions before they go live; monitor Service health and sign-in logs after policy changes.

What it means if verification fails: If Planner still doesn't load after applying fixes, collect fresh HAR and sign-in logs at the new failure time and reopen a support ticket with that evidence.

Conclusion

If local fixes restore Planner, confirm the user signs out and back in and record the environment that caused the failure. If the problem is tenant-side, collect HAR files and sign-in logs and have an admin verify licenses, group membership, and conditional access policies before opening a Microsoft support ticket. After a fix is applied, verify by signing in as the affected user and confirming Planner loads and tasks sync.

Frequently Asked Questions

What quick check confirms Planner is working again?

Sign in as the affected user on a browser where you cleared cache or used incognito, open `planner.office.com`, and confirm plans and tasks load and changes sync immediately. Edit a task and verify the change appears from a different device or account.

Can missing Planner features be a license issue?

Yes. If the user's license SKU doesn't include Planner or the Planner service is disabled on their license, Planner won't connect properly. Confirm the license in the Microsoft 365 admin center and enable Planner if necessary.

Should I send HAR files to Microsoft support?

Yes, but only via the secure support case upload. HAR files contain sensitive tokens, so do not email them broadly; include them with your official support ticket.