Forum Discussion
Issue when opening Planner via browser
Hello everyone,
we are currently experiencing an issue when opening Planner via browser: every time, the sign-in screen appears and we are asked to sign in with our Microsoft account. This happens even though we open it directly via https://planner.cloud.microsoft.
After we sign in, close the browser, and open Planner again, we are prompted with the sign-in screen once more.
While checking the cookies, I've noticed that no authentication information was created when signing in via direct url.
Using https://m365.cloud.microsoft/apps/ and open Planner from the Apps section, it creates authentication information in Edge / in the cookies.
Has anyone else experienced something similar?
Is this a known / general problem?
3 Replies
- MBAPBrass Contributor
Same issues since using Planner, free and now on paid plan. Happens in the browser and also in Teams where I have Planner added.
Annoying when you are reviewing tasks and doing other work to populate info and it logs you out, asking you to "refresh" your session.
No policies exist to cause this for planner, and all other MS apps remain signed in. This is also on an SSO and Intune fully joined device and Edge also logged in under our company. - ChickTCopper Contributor
We have the same issue also.
- AnqdersCopper Contributor
Hi, yes we are having the same issue. (Denmark). Have been going on for at least a few weeks. I have the same issue on a private PC with my private Office subscription, so we can rule out tenent settings I think.
Here is the summary of the troubleshooting steps attempted so far:
- Firewall Whitelisting: All necessary URLs have been added to the firewall's allowlist.
- DNS Configuration: It has been confirmed that all domain names can be resolved via DNS, so the browser should be able to locate the servers.
- Decryption: SSL/TLS decryption (inspektion of encrypted traffic) has been disabled for all relevant URLs.
- Security Zones: *.cloud.microsoft and *.office.com have been added to "Trusted Sites" in the Windows settings.
- Cookie Settings: The browser has been configured to allow third-party cookies for Microsoft domains.
- Testing with Private Account/Network: The issue has been reproduced on a private computer with a private internet connection and a private Microsoft account.