Microsoft planner won t stay signed in

If Microsoft Planner won’t stay signed in, open the browser first, then clear cached Microsoft credentials, then check tenant policy. The fix depends on where reauthentication begins. Repeated prompts can block plan access and task updates. The fastest first step is to check Microsoft sign-in cookies and site data in the browser.

Likely causes

Planner sign-in loops are commonly caused by a handful of issues. The browser may block or clear Microsoft cookies. Windows may hand over stale Office credentials. A second Microsoft account may be competing with the work account. For work tenants, Microsoft Entra ID policy can force reauthentication. Less commonly, the account has lost access or the service is having a problem.

Browser state is the most common place to start. Microsoft account sign-in depends on cookies and JavaScript being enabled, and the keep-signed-in flow depends on a persistent cookie. If the browser blocks cookies, clears site data on exit, or strips tracking data too aggressively, Planner may load and then send you back to the login prompt. (Microsoft)

Open the browser you use for Planner and go to its privacy settings.
Allow cookies for Microsoft sign-in sites, and make sure site data is not being cleared on exit.
Check tracking prevention or third-party cookie blocking in the browser’s Privacy, search, and services area.
Enable JavaScript and cookies for Microsoft sign-in pages if the browser has per-site controls.
Use Microsoft Edge if another browser keeps looping; Microsoft says Edge gets the latest features and security updates.

Suppose Planner opens in a tab, shows the sign-in page, and then asks again after you enter the password. That pattern usually points to a browser session that cannot keep the Microsoft login cookie alive, not to a broken plan or taskboard.

Stored Windows credentials are interfering

On Windows, old Microsoft 365 or Office entries in Credential Manager can keep handing Planner stale sign-in data. That is a common reason Office apps or browser-based Microsoft services keep looping after a reinstall, a password change, or a device sign-in change. The browser may be clean while Windows still supplies the wrong token.

Open Control Panel > User Accounts > Credential Manager.
Open Windows Credentials and Generic Credentials.
Remove entries that reference Microsoft 365, Office, Teams, OneDrive, or the work account domain.
Restart the browser, then sign in again with the correct work or school account.
If the prompt still returns, sign out of Microsoft 365 apps on the device and try Planner again in a fresh browser window.

A common first-timer mistake is signing out of the wrong Microsoft account and then wondering why Planner keeps asking for credentials. Keep the focus on Microsoft 365, Office, Teams, and tenant-related entries. Those are the ones most likely to interfere with Planner sign-in.

Multiple Microsoft accounts are competing

Planner can fail when a personal Microsoft account and a work account are both active in the same browser. The browser may try to reuse the wrong identity, especially if you are signed into Outlook, Teams, or another Microsoft service in the same profile. That confusion can look like a bad password or a broken Planner session.

Open a private or InPrivate window and go directly to Planner.
Sign out of other Microsoft services in the regular browser profile before retrying.
Confirm the tenant email address before entering the password.
Make sure you are using the work or school account tied to the Planner tenant, not a personal Microsoft account.
If the browser keeps mixing identities, create a separate browser profile for work sign-in only.

Say your personal Microsoft account is signed into the browser for Outlook.com, and your work tenant uses a different address for Planner. A login loop can appear even when the password is correct, because the browser keeps presenting the wrong identity first.

Microsoft Planner sign-in matrix — Promotional graphic about using Microsoft Planner for an Eisenhower matrix

This table helps you separate browser problems from device credentials and tenant policy. Use the fastest test first, then escalate only if the symptom survives that layer. Capture the exact error text before you hand it to an admin.

Symptom	Likely layer	Fastest test	User can fix	Admin required	What to capture before escalating
Planner loads, then returns to sign-in after entering credentials	Browser cookie blocks or cleared site data	Try InPrivate or another browser profile with Microsoft cookies allowed	Yes	No	Browser name, privacy settings, exact redirect behavior, error text
Planner works after browser reset, but not on the normal Windows profile	Stale Windows credentials	Open Credential Manager and remove old Microsoft 365 entries	Yes	No	Windows version, Credential Manager entries removed, whether the device was recently reimaged or reinstalled
Sign-in succeeds only after signing out of a personal Microsoft account	Multiple Microsoft accounts in the same browser	Use a clean profile and confirm the tenant email address first	Yes	No	Work account UPN, personal account email, browser profile used
Sign-in works, then fails again after restart or at a fixed interval	Persistent browser session or sign-in frequency policy	Check whether the session expires at the same interval on different devices	No	Yes	Time to re-prompt, device type, browser, and whether the issue repeats across users
User sees “you no longer have access” after authentication	Tenant access or license change	Check whether the account still belongs to the right tenant and has the correct assignment	No	Yes	Exact message, account name, tenant name, and when access stopped

For work accounts, Microsoft Entra ID controls whether the browser can stay signed in. Conditional Access can shorten session times, and sign-in frequency can force reauthentication at a set interval. The default sign-in frequency is 90 days, but a policy can shorten that window. Persistent browser session settings also affect whether Planner stays signed in after restart. (Microsoft Learn)

Ask your Microsoft 365 admin to open the Entra admin center.
Review Conditional Access policies that apply to the account.
Check Sign-in frequency and see whether the policy is shorter than 90 days.
Review persistent browser session settings for the user or group.
Review Entra sign-in logs for repeated reauthentication, failure codes, or device compliance blocks.

If the same account is prompted again after a fixed delay, that is a policy clue, not a cookie clue.

Planner often repeats the prompt when the browser cannot preserve the Microsoft session, Windows is reusing stale credentials, or Entra policy is requiring a new sign-in. The fastest way to separate those causes is to test in InPrivate mode, then in a different browser profile, then with Credential Manager cleaned up, and only after that move to tenant policy review.

If Planner opens but does not function after authentication, the problem is often identity state rather than Planner content. The session may be half-valid, the browser may be mixing accounts, or the tenant may be blocking access after sign-in. Try a clean browser profile first, then confirm you signed in with the tenant account tied to the plan.

Why do I get “you no longer have access” in Microsoft Planner?

That message usually points to tenant access, licensing, or assignment changes. The account may no longer belong to the right Microsoft 365 tenant, or the user may have lost the app assignment needed for Planner. An admin should confirm the user is still assigned to the right tenant and that the license or access path is still active.

Could my Microsoft account or tenant settings cause repeated Planner sign-ins?

Yes. Microsoft account sign-in depends on cookies and JavaScript, while work accounts inherit Microsoft Entra ID settings. A personal Microsoft account in the same browser can also interfere with a work tenant session. If the loop happens only for one tenant or one account, policy or identity mix-up is more likely than a Planner outage.

What should I check if Microsoft Planner won't stay signed in?

Start with browser cookies and site data, then remove old Windows credentials, then test for mixed Microsoft accounts. If the problem persists only on a work account, move to Entra sign-in logs, Conditional Access, and persistent browser session settings. That order keeps you from chasing policy before you rule out local browser state.

Test Planner in Microsoft Edge or another fresh browser profile.
Allow Microsoft sign-in cookies and keep JavaScript enabled.
Delete old Microsoft 365 and Office entries from Credential Manager.
Retest with only the work account active in the browser.
If the loop continues, escalate to the Microsoft 365 admin with the exact error text and timing.

Is there an issue with Microsoft Planner right now?

A service issue is possible, but it is less likely than a browser, credential, or policy problem. If Planner fails for many users at once, ask the Microsoft 365 admin to check service health and compare sign-in logs across accounts. If only one user or one browser profile is affected, the cause is usually local or tenant-specific.

Does Microsoft Planner still exist or is it going away?

Microsoft Planner still exists and remains part of Microsoft 365 task management. If someone cannot open it, the problem is usually access, sign-in state, or policy, not that the app has disappeared. Check the account, browser, and tenant first before assuming the service is being retired.

Still not working?

If the browser, Credential Manager, and account checks do not stop the loop, move to tenant evidence. Collect the exact error text, the browser used, the account UPN, the device type, and whether the prompt repeats on another device or network. Then ask the admin to review Entra sign-in logs, Conditional Access, and persistent browser session settings together.

Try the same account in a fresh browser profile on a second device.
Note whether the prompt returns immediately, after restart, or after a fixed time.
Capture any “you no longer have access” message exactly as shown.
Escalate with the collected browser, device, and tenant details.

Keep Microsoft sign-in cookies allowed for the work browser profile, and keep personal and work accounts in separate profiles.

Keep reading

Frequently asked questions

Yes. Microsoft account sign-in requires cookies and JavaScript, and the keep-signed-in flow depends on a persistent cookie. If the browser blocks, clears, or purges those cookies on exit, Planner can sign you in and then immediately prompt again.

Does Microsoft Planner still exist?

Yes. Planner is still part of Microsoft 365 task management. If you cannot access it, focus on the sign-in path, tenant assignment, and browser session state before assuming the app is unavailable or discontinued.