How to fix "The browser is closed" error for the Entra ID connector in Logic Apps?

Hello Bradley Paoli,

Greetings! Thanks for raising this question in the Q&A forum.

The "The browser is closed" message comes from the OAuth sign-in popup that the Logic Apps designer opens when you create an Entra ID connection. The message means the designer lost contact with that popup window, or the popup was closed or blocked before sign-in finished. Since your other connectors work, the usual causes are browser-side (popup blocked, third-party cookies or tracking protection, an extension) or a tenant-side policy such as Conditional Access or missing consent that applies to the Entra ID connector only. I can't confirm which one applies to you from the question alone, so please go through these steps in order.

Rule out the browser. Open the Azure portal in a fresh InPrivate or Incognito window with all extensions disabled, and allow popups for portal.azure.com and login.microsoftonline.com. Also allow third-party cookies for those sites, then retry creating the connection. Trying a different browser (Edge, Chrome) is a quick way to confirm.

Clear stale sign-in state. Sign out of all Microsoft accounts, clear cookies and cache for the Microsoft sign-in domains, then sign in again with only the account that should own the connection. Multiple signed-in accounts can cause the popup to close immediately.

Delete any old connection and recreate it. In the Azure portal, search for API Connections, delete the failed Entra ID connection (typically named azuread), then add the action again in the designer and sign in.

Check Conditional Access and consent. In Entra ID, open Sign-in logs, filter on your user and the time of the attempt, and look at the failure reason and the Conditional Access tab. A policy that requires a compliant device, blocks popups from the portal session, or restricts the app can end the flow immediately. Also check Enterprise applications, then Consent and permissions, to see whether user consent is disabled and admin consent is required. If it is, a Global Administrator can grant consent for the connector's application. The Microsoft documentation for the related HTTP with Microsoft Entra ID connector also shows how to grant consent through a PowerShell script.

Use a non-interactive option if the popup keeps failing. If you only need to call Entra ID or Microsoft Graph from the workflow, you can avoid the popup by using the HTTP action with a managed identity for the Logic App, and granting that identity the required Microsoft Graph application permission. The CLI to assign a managed identity is:

az logic workflow identity assign --name <logic-app-name> --resource-group <rg-name> --system-assigned

You can then call Graph, for example https://graph.microsoft.com/v1.0/users, with the HTTP action using Managed Identity authentication and the audience https://graph.microsoft.com.

1. Escalate if it still fails. If the error persists in a clean browser session, and the sign-in logs show no blocking policy, please open an Azure Support request under Logic Apps. Include the Logic App name, region, subscription ID, your screenshot, the exact time of the attempt with timezone, and the browser network trace (HAR file) captured while reproducing the error.

If this answer helps you kindly accept the answer which will help others who have similar questions.

Best Regards,
Jerald Felix