https://dev.botframework.com/ not letting me sign in?

Manage the bot through the Azure portal rather than dev.botframework.com; the current Azure AI Bot Service documentation uses an Azure Bot resource in the Azure portal for bot registration, configuration, identity, and channels.^1^

Access an existing Azure bot

1. Sign in to the Azure portal.
2. Use the global search box to search for Azure Bot or the bot/resource name.
3. Open the Azure Bot resource from the correct subscription and directory.
4. Use its resource menu:
   • Configuration for the messaging endpoint, Microsoft App ID, and tenant information.
   • Channels for channel configuration.
   • Test in Web Chat to test the deployed bot.

The Azure portal account menu lets you switch directories if the bot belongs to another Microsoft Entra tenant.^2^

Existing Web App Bot and Bot Channels Registration resources remain supported even though new resources of those types cannot be created. You do not need to recreate a working legacy Azure resource merely because its resource type is older.^3^

If the bot exists only in the Bot Framework Dev Portal

Microsoft still documents dev.botframework.com specifically for migrating a Dev Portal registration to Azure. That procedure requires signing into the Dev Portal, adding a co-owner from the target directory, signing out, and then signing in as that co-owner to perform the migration.^4^

Because your sign-in immediately invokes sign-out—and you have already reproduced it across Chrome, Safari, incognito, mobile, and another account—that migration procedure is currently blocked. Repeating browser or account-switching tests is unlikely to provide new information. The screenshots also show no error code that identifies an account, tenant, or bot-configuration failure.

Do not change the bot’s OAuth redirect URL, App ID, or secret to address this portal login loop. Those settings govern bot/user authentication, while the failure shown occurs while authenticating to the management portal.

Escalate the Dev Portal redirect loop

Open an Azure support request so Microsoft can investigate the portal-side authentication transaction:

1. In the Azure portal, select ? in the global header.
2. Enter a description such as Bot Framework Dev Portal immediately signs out after successful account selection.
3. Complete the diagnostic prompts.
4. If no recommendation resolves it, select Create a support request.
5. Choose the affected subscription and the service closest to Azure AI Bot Service.
6. Include:
   • The UTC date and time of a failed attempt.
   • The exact reproduction sequence.
   • Confirmation that it occurs across multiple browsers, devices, private browsing, and two accounts.
   • Whether the bot appears in any Azure subscription/directory.
   • Whether access is required specifically to migrate a Dev Portal-only registration.
   • The screenshots and, if requested, a browser trace—without passwords, tokens, or other confidential data.

Microsoft documents this global-header and resource-menu support workflow, including attaching a browser trace.^5^

Creating a subscription-scoped request requires Owner, Contributor, Support Request Contributor, or an equivalent custom role containing Microsoft.Support/*. A request without a subscription, such as an Entra scenario, requires an administrator.^5^

References

1. Use the Azure portal to Create an Azure Bot resource
2. What is the Azure portal?
3. Bot Framework Azure Frequently Asked Questions
4. General troubleshooting for Azure AI Bot Service bots
5. Create an Azure support request