Power Apps thirdPartyCookiesBlocked: fix the sign-in error

You open an app, or Power Apps itself, and get "Hmmm... Something went wrong." with the code thirdPartyCookiesBlocked, and a request to enable third-party cookies and site data in your browser settings. Power Apps keeps some data in your browser, such as who you are and your preferences. When the browser blocks that storage, or blocks the third-party cookies Power Apps sets, Microsoft says problems occur. The fix is in your browser's settings, or for the iOS mobile apps in iOS settings: turn on third-party cookies and local data the way Microsoft's steps describe, then try again.

The messages and what they mean

Microsoft's troubleshooting page for Power Apps sign-in groups these messages together and gives one list of fixes for all of them:

In a model-driven app, the same cause can look different. Microsoft's page for Unified Interface apps (the interface model-driven apps use) shows "Something has gone wrong" with UserInterventionNeeded_CookiesBlocked and the text "Power Apps requires cookies to be enabled." It says the cause is blocked third-party cookies and points to the same browser steps.

The AADSTS50058 code is a general Microsoft Entra code. Our guide to AADSTS sign-in errors explains the code family.

Fix it step by step

Microsoft's fixes, in its order. Most browsers apply a cookie change straight away; if yours doesn't, close every browser window and open it again.

1. Allow third-party cookies and site data

Do this in the browser you use for Power Apps. Learn gives two options for Edge and for Chrome: allow third-party cookies and local data for all sites (option 1), or add exceptions for Power Apps and associated services (option 2). Here are Learn's steps, with its menu names.

Option 1 for Edge and Chrome refers to these addresses:

https://create.powerapps.com
https://*.create.powerapps.com
https://make.*.powerapps.com
https://make.powerapps.com
https://login.microsoftonline.com
https://apps.*.powerapps.com
https://apps.powerapps.com

For US Government environments (a sovereign cloud), Learn links a separate list of US Government addresses.

Microsoft Edge, option 1 (all sites):

1. Select Settings > Cookies and site permissions.
2. Expand Cookies and data stored.
3. Make sure Block third-party cookies is turned off.
4. If any of the addresses above are in the site-specific cookie settings under Block or Clear on exit, remove them.

Microsoft Edge, option 2 (exceptions for Power Apps; Learn says it needs Edge 87 or later):

1. Select Settings > Cookies and site permissions.
2. Expand Cookies and data stored.
3. Under Allow, select Add and add [*.]powerapps.com.
4. Select Clear browsing data on close.
5. Make sure Cookies and other site data is turned off. To keep it on, select Add there instead and add [*.]powerapps.com.

Learn's pages don't agree on the name in Edge's step 2. The Power Apps page says Cookies and data stored. Microsoft's Power Automate page for the same Edge steps says Manage and delete cookies and site data. Both pages are under Sources.

Google Chrome, option 1 (all sites):

1. Select Settings > Privacy and security.
2. Expand Cookies and other site data.
3. Make sure Block third-party cookies or Block all cookies isn't selected.
4. If any of the addresses above are in the site-specific cookie settings under Sites that can always use cookies or Always clear cookies when windows are closed, remove them.

That's how Learn words step 4 for Chrome, although its option 2 adds [*.]powerapps.com to Sites that can always use cookies.

Google Chrome, option 2 (exceptions for Power Apps):

1. Select Settings > Privacy and security.
2. Expand Cookies and other site data.
3. Go to Sites that can always use cookies, select Add and add [*.]powerapps.com.
4. When you add it, select Including third-party cookies on this site.

Safari: select Safari > Preferences > Privacy, and make sure neither Block all cookies nor Prevent cross-site tracking is selected.

Mozilla Firefox, for apps embedded in another site such as SharePoint: in Settings, select Privacy & security, find Enhanced Tracking Protection and select Manage Exceptions. Add the address of the site the apps are embedded in, such as your SharePoint address.

The Power Apps mobile app on iOS: Learn says to change this in iOS settings, not in the browser. Select Settings, scroll down to Power Apps and turn on Allow Cross-Website Tracking. Learn gives the same steps for the Dynamics 365 app (scroll to Dynamics 365) and for Edge on iOS (scroll to Edge).

2. Clear the cache and try again

Clear your browser's cache and cookies. Microsoft says cached data can sometimes stop you signing in.

3. Try another browser

Sign in with a different browser from Microsoft's list of supported browsers for Power Apps.

4. Check your network

Microsoft's list also includes checking that your network connection is stable.

5. Read any Microsoft Entra error

If the page shows a Microsoft Entra error, it usually concerns authentication or authorisation. The error page may say more, and Microsoft says you might need help from your IT department.

6. The third-party storage partitioning flag

This step is only for four situations Microsoft names:

• One device signs in with several Microsoft Entra identities, for different apps.
• You use several apps that sign in with Microsoft Entra, in more than one tab, and signing out of one tab doesn't sign you out of the other.
• The app is embedded in a third-party website in an iframe.
• A canvas app is embedded in a model-driven app form.

In those cases, Microsoft says to make sure the browser's Third-party Storage Partitioning setting is disabled. Open edge://flags/#third-party-storage-partitioning in Edge, or chrome://flags/#third-party-storage-partitioning in Chrome, by typing it into the address bar.

Private windows: Incognito and InPrivate

Learn notes "Sign in required" and AADSTS50058 especially in InPrivate or Incognito mode. For Chrome's Incognito mode, the thirdPartyCookiesBlocked message itself points to the switch: uncheck Block third-party cookies on the Incognito landing page. Microsoft's troubleshooting page gives no separate steps for InPrivate in Edge.

Apps embedded in SharePoint, Teams or a website

Microsoft lists a prompt to sign in every time, when an app is embedded in SharePoint or Microsoft Teams, among these issues. Its Firefox steps are written for this case: they let apps use cookies when they're embedded in another client, such as SharePoint.

• Allow cookies as in step 1. In Firefox, add the address of the site the app is embedded in to the exceptions.
• For a canvas app in an iframe on your own website, Microsoft's embedding page says a site that signs people in with Microsoft Entra ID needs no extra sign-in. A site with any other sign-in, or none, shows a sign-in prompt inside the iframe.
• If the app is in an iframe on a third-party website, it's one of the four cases for the storage partitioning flag.

Power Automate has its own page for blank or spinning embedded screens caused by blocked third-party cookies. It's listed under Sources.

Sources

• Microsoft Learn: Troubleshooting startup or sign-in issues for Power Apps
• Microsoft Learn: Third-party cookies or pop-up blocker errors when accessing Unified Interface apps in a web browser
• Microsoft Learn: Enhanced user experience with Unified Interface for model-driven apps
• Microsoft Learn: Microsoft Entra authentication and authorization error codes
• Microsoft Learn: Integrate canvas apps into websites and other services
• Microsoft Learn: Supported browsers for running Power Apps
• Microsoft Learn: Power Apps US Government service URLs
• Microsoft Learn: Third-party cookies or pop-up blocker errors when accessing Power Automate embedded experiences