Azure Bot to Foundry Bot connection error!

Question

Azure Bot to Foundry Bot connection error!

Bhatt, Nitin 0

Azure Bot to Foundry Bot connection works fine as 'Test in web chat' feature of Azure bot works. However, the webchat code or directline tries to login to foundry repeatedly with ' Waiting for foundry login to complete' error.

Anshika Varshney 9,740 Reputation points Microsoft External Staff Moderator

2026-03-30T17:53:22.37+00:00

Hi Bhatt, Nitin,

Please let me know if there are any remaining questions or additional details, I can help with, I’ll be glad to provide further clarification or guidance.

Thankyou!
Bhatt, Nitin 0 Reputation points

2026-03-30T18:11:44.2433333+00:00

i cant pin point what the issue is everything seems to be there. When BOT is published from foundry , is there any change needed in configuration ?
Anshika Varshney 9,740 Reputation points Microsoft External Staff Moderator

2026-03-30T23:54:57.9866667+00:00

Thanks for the update. Yes, publishing can require changes. When you publish from Foundry, it creates a new agent application with its own stable endpoint and its own identity, separate from the one used inside the project. Because of that, if your bot uses tools or accesses any Azure resources, you usually need to reassign the required permissions to the published agent identity. Also note the application ID and tenant ID shown during publishing as they help confirm you are calling the published agent and not the playground version. Microsoft also notes that publishing creates an Azure Bot Service resource, so the Bot Service provider must be registered in the subscription used for publishing. Publish agents to Microsoft 365 Copilot and Microsoft Teams
Anshika Varshney 9,740 Reputation points Microsoft External Staff Moderator

2026-03-31T20:29:59.68+00:00

Hi Bhatt, Nitin,

Did you get any chance to review the response.

Thankyou!
Manas Mohanty 16,190 Reputation points Microsoft External Staff Moderator

2026-04-02T07:41:22.0533333+00:00

Hi Bhatt, Nitin,

Does the issue still persist for you. Pattern was initially observable at my side but seems to be mitigated now.

I just tested Foundry Agent with "MS Learn" tool in Sweden Central region

Please share your region and tool attached along network setting if the issue persists for you.

Thank you.
Bhatt, Nitin 0 Reputation points

2026-04-02T13:16:40.3766667+00:00

Azure Bot itself and its connection to Foundry work correctly (since Test in Web Chat succeeds), but the custom Web Chat/Direct Line integration is not completing the authentication flow against Foundry.

2 answers

Your answer

Anshika Varshney 9,740 Reputation points Microsoft External Staff Moderator

2026-03-30T17:53:22.37+00:00

Hi Bhatt, Nitin,

Please let me know if there are any remaining questions or additional details, I can help with, I’ll be glad to provide further clarification or guidance.

Thankyou!
Bhatt, Nitin 0 Reputation points

2026-03-30T18:11:44.2433333+00:00

i cant pin point what the issue is everything seems to be there. When BOT is published from foundry , is there any change needed in configuration ?
Anshika Varshney 9,740 Reputation points Microsoft External Staff Moderator

2026-03-30T23:54:57.9866667+00:00

Thanks for the update. Yes, publishing can require changes. When you publish from Foundry, it creates a new agent application with its own stable endpoint and its own identity, separate from the one used inside the project. Because of that, if your bot uses tools or accesses any Azure resources, you usually need to reassign the required permissions to the published agent identity. Also note the application ID and tenant ID shown during publishing as they help confirm you are calling the published agent and not the playground version. Microsoft also notes that publishing creates an Azure Bot Service resource, so the Bot Service provider must be registered in the subscription used for publishing. Publish agents to Microsoft 365 Copilot and Microsoft Teams
Anshika Varshney 9,740 Reputation points Microsoft External Staff Moderator

2026-03-31T20:29:59.68+00:00

Hi Bhatt, Nitin,

Did you get any chance to review the response.

Thankyou!
Manas Mohanty 16,190 Reputation points Microsoft External Staff Moderator

2026-04-02T07:41:22.0533333+00:00

Hi Bhatt, Nitin,

Does the issue still persist for you. Pattern was initially observable at my side but seems to be mitigated now.

I just tested Foundry Agent with "MS Learn" tool in Sweden Central region

Please share your region and tool attached along network setting if the issue persists for you.

Thank you.
Bhatt, Nitin 0 Reputation points

2026-04-02T13:16:40.3766667+00:00

Azure Bot itself and its connection to Foundry work correctly (since Test in Web Chat succeeds), but the custom Web Chat/Direct Line integration is not completing the authentication flow against Foundry.

Answer 1

Hi Bhatt, Nitin,

This type of connection error between an Azure Bot and a Foundry Bot usually happens due to configuration or identity mismatch between the two environments.

Here are a few things you can check step by step.

First, make sure both bots are using the same Azure Active Directory tenant and subscription. If the Azure Bot was created in a different tenant or subscription than the Foundry project, the connection will fail even if everything looks correct in the portal.

Next, verify the App Registration linked to the Azure Bot. The Application ID used by the Azure Bot should match the identity configured in the Foundry Bot. Also check that the Client Secret or Certificate is still valid and not expired.

Another common issue is API permissions. The App Registration should have the required Microsoft Graph permissions, and admin consent must be granted. Without proper consent, the Foundry Bot will not be able to authenticate correctly.

Also double‑check the messaging endpoint configured in the Azure Bot channel. It should point to the correct Foundry Bot endpoint and environment. Even a small mismatch, like using an old endpoint or a different environment, can cause connection failures.

If you recently recreated or migrated the bot from Azure Bot to Foundry Bot, try re‑saving the bot configuration and reconnecting it. In many cases, older references or cached values cause the connection to fail until the configuration is refreshed.

You can also review the bot logs in Azure Monitor or Application Insights. These logs usually show whether the error is related to authentication, permission, or endpoint access, which makes troubleshooting much easier.

Helpful official references that explain these areas in more detail:

Azure Bot authentication and app registration setup on Microsoft Learn https://dotnet.territoriali.olinfo.it/azure/bot-service/bot-builder-authentication

Once these points are aligned, the connection between the Azure Bot and Foundry Bot should start working as expected.

I Hope this helps. Do let me know if you have any further queries.

Thankyou!

Answer 2

The behavior indicates that the Azure Bot itself and its connection to Foundry work correctly (since Test in Web Chat succeeds), but the custom Web Chat/Direct Line integration is not completing the authentication flow against Foundry.

From the available information, the supported troubleshooting path is:

Verify the bot works in Azure Web Chat
- In Azure portal, open the Azure Bot resource.
- Use Test in Web Chat and confirm that:
  - Messages are processed correctly.
  - Any Foundry-related login or SSO flow completes successfully.
- Since this already works, the bot and its Foundry connection are functioning in the cloud.
Confirm Web Chat/Direct Line configuration
- Ensure the Web Chat or Direct Line client is using the correct bot endpoint and credentials by comparing behavior with Test in Web Chat.
- If using Direct Line, follow the guidance for embedding Web Chat securely:
  - Get the Web Chat secret key from Channels → Web Chat → Default Site.
  - Exchange the secret for a token via the documented token exchange URL, then use that token in the Web Chat control.
- Any mismatch between the configuration used by Azure’s built-in Web Chat and the custom Web Chat/Direct Line client can cause repeated login attempts.
Check for channel-specific behavior
- The built-in Test in Web Chat uses the Web Chat channel configuration that is already known to work.
- If a custom Web Chat or Direct Line client behaves differently (for example, stuck on “Waiting for foundry login to complete”), treat this as a channel-specific issue:
  - Recreate or reset the Web Chat/Direct Line configuration in the Azure Bot Channels blade.
  - Ensure that any authentication or SSO logic in the bot is compatible with the Web Chat/Direct Line channel being used.
Re-deploy and retest in the cloud
- Confirm the bot is deployed and running in Azure with security enabled.
- In Azure portal, use Test in Web Chat again to verify that the bot responds correctly with HTTPS and valid credentials.
- Once confirmed, reconnect the Web Chat/Direct Line client using the same configuration.

If the loop persists only in the custom Web Chat/Direct Line client while Azure’s Test in Web Chat continues to work, the issue is in the external Web Chat/Direct Line integration rather than the Azure Bot or its Foundry connection. Re-aligning the external client’s configuration with the working Web Chat channel configuration is the supported remediation.

References:

Share via

Azure Bot to Foundry Bot connection error!

2 answers

Your answer