Azure AI Foundry – “Waiting for Foundry login to complete” when using custom Teams agent

Question

Azure AI Foundry – “Waiting for Foundry login to complete” when using custom Teams agent

Shital Kuyate 50

Hello Team,

I am facing an issue while integrating a custom AI agent (built using Azure AI Foundry) with Microsoft Teams.

When I open the agent inside Teams and asking "Hi" or anything , it displays the following message and remains stuck indefinitely:

“Waiting for Foundry login to complete”

The login process never finishes and the agent does not respond.

SRILAKSHMI C 19,735 Reputation points Microsoft External Staff Moderator

2026-03-11T06:00:18.8766667+00:00

Hi Shital Kuyate,

Did you get any chance to review the above response. Do let me know if you have any further queries.

Thank you!
Shital Kuyate 50 Reputation points

2026-03-23T06:42:20.3866667+00:00

Hi SRILAKSHMI,
Yes, the issue is resolved —thank you!

Also, I appreciate your detailed and informative response. I’d like to understand the exact steps to disable the AI Foundry authentication, as the agent prompts for login every time a chat starts. Could you please guide me on how to turn this off?
SRILAKSHMI C 19,735 Reputation points Microsoft External Staff Moderator

2026-03-24T12:10:30.73+00:00
Hi Shital Kuyate,

You can’t fully “turn off” Azure AI Foundry authentication for a Teams-based agent. That login prompt is happening by design, not as a configurable toggle.

Here’s how to explain it to the customer in a clear, non-GPT way

Why the login happens

When your agent is built in Azure AI Foundry and used inside Microsoft Teams, it relies on Microsoft Entra ID authentication to:

Identify the user

Access the correct Foundry project/workspace

Enforce RBAC and data security

So when Teams shows “Waiting for Foundry login to complete”

it’s trying to complete that sign-in/token exchange. There is no setting today to disable this authentication entirely.

What you can do instead

If the concern is that users are being asked to log in every time, here are the practical options:

Enable/verify Teams SSO

Instead of removing authentication, configure Single Sign-On (SSO) so users aren’t prompted repeatedly.

Things to check:

Teams app is registered in Microsoft Entra ID

सही redirect URIs are configured

Proper delegated permissions are granted

Token exchange is enabled between Teams ↔ Foundry

With SSO working correctly, login becomes silent

Avoid user-context dependency (if applicable)

If your agent doesn’t need user-specific data, doesn’t enforce per-user access

You can redesign it to use a service principal / backend identity instead of user login.

But This is an architectural change, Not a toggle in Foundry, Still requires authentication just not per user

Check session persistence issues

If login is happening every time, it may indicate:

Tokens not being cached

Third-party cookies blocked

Teams desktop client cache issue

Quick checks:

Try Teams web client

Enable cookies/pop-ups

Clear Teams cache

At the moment, Azure AI Foundry does not provide an option to disable authentication for agents used in Microsoft Teams. The login is required for security and access control. However, this can typically be made seamless by configuring Teams Single Sign-On (SSO), so users are not prompted repeatedly.

Thank you!
Shital Kuyate 50 Reputation points

2026-03-24T17:42:01.0766667+00:00

Hi SHILAKASHMI,
Thank you so much for clarifying this. I was getting different solutions across multiple platforms, which left me quite confused. Your explanation really helped clear things up.

I understand now that Azure AI Foundry does not allow disabling authentication for agents in Microsoft Teams due to security and access control requirements. Configuring Teams Single Sign-On (SSO) to make the experience seamless makes sense.

Thanks again for your support! Many thanks to Microsoft as well for the prompt response. Really appreciate the quick and helpful support.

Answer accepted by question author

SRILAKSHMI C 19,735 Microsoft External Staff Moderator

Hello Shital Kuyate,

Welcome to Microsoft Q&A and Thank you for reaching out.

Based on your description, it appears that Microsoft Teams is loading the custom agent but the Azure AI Foundry authentication process is not completing, which causes the message “Waiting for Foundry login to complete” to remain indefinitely. This usually indicates that the sign-in or token exchange between Microsoft Teams and Azure AI Foundry has not successfully finished.

Below are several checks that may help resolve the issue:

Verify the Azure AI resource and permissions Ensure that you have an Azure AI / Azure OpenAI resource configured for your agent. Also confirm that your user account or the identity used by the Teams application has the required permissions. Common roles include Owner, Contributor, Azure AI Developer, Azure AI User, or Project Manager. These permissions are managed through Microsoft Entra ID.

Confirm tenant and subscription selection during login When the Foundry login prompt appears, make sure the correct Azure tenant and subscription are selected. If the authentication occurs under the wrong directory or subscription, the agent workspace cannot be initialized and the login process may remain stuck.

Check Teams app and authentication configuration If you are using a custom Teams app, verify that the Teams app manifest contains the correct bot/app ID and that it matches the configuration used for the agent in Foundry. Also confirm that redirect URIs and permissions in Entra ID are correctly configured for the application.

Validate network and security restrictions If your environment uses firewalls, private endpoints, or proxies, ensure they are not blocking required endpoints such as:

ai.azure.com

openai.azure.com

*.services.ai.azure.com

If you are using Key Vault or restricted networking for credentials, confirm the calling identity has appropriate access permissions.

Test the Foundry login outside Teams Try signing in directly to the Foundry portal at https://ai.azure.com using the same account and open or create an agent there. If the agent works in the portal but not in Teams, this usually indicates the issue is specific to the Teams integration or SSO configuration.

Check for blocked login pop-ups or cookies Authentication may fail if pop-ups or third-party cookies are blocked. Ensure your browser allows pop-ups and cookies for ai.azure.com.

Clear client cache or try another client Sometimes the issue can be caused by a cached authentication state. You can try:

Clearing the Teams desktop cache
Signing out and signing back in
Testing the agent in the Teams web client

Please refer this

Resolve issues with logging in to Azure AI Foundry: https://learn.microsoft.com/azure/ai-studio/concepts/ai-resources#hubs https://learn.microsoft.com/azure/ai-studio/concepts/rbac-ai-studio

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

Thank you!

0 comments

1 additional answer

Your answer

SRILAKSHMI C 19,735 Reputation points Microsoft External Staff Moderator

2026-03-11T06:00:18.8766667+00:00

Hi Shital Kuyate,

Did you get any chance to review the above response. Do let me know if you have any further queries.

Thank you!
Shital Kuyate 50 Reputation points

2026-03-23T06:42:20.3866667+00:00

Hi SRILAKSHMI,
Yes, the issue is resolved —thank you!

Also, I appreciate your detailed and informative response. I’d like to understand the exact steps to disable the AI Foundry authentication, as the agent prompts for login every time a chat starts. Could you please guide me on how to turn this off?
Shital Kuyate 50 Reputation points

2026-03-24T17:42:01.0766667+00:00

Hi SHILAKASHMI,
Thank you so much for clarifying this. I was getting different solutions across multiple platforms, which left me quite confused. Your explanation really helped clear things up.

I understand now that Azure AI Foundry does not allow disabling authentication for agents in Microsoft Teams due to security and access control requirements. Configuring Teams Single Sign-On (SSO) to make the experience seamless makes sense.

Thanks again for your support! Many thanks to Microsoft as well for the prompt response. Really appreciate the quick and helpful support.

Answer 1

Holt, Conner 0

After publishing from the Foundry portal, the publish flow auto-creates an Azure Bot Service but doesn't tell you there's a mandatory manual step to complete it.

Fix:

Azure Portal → find the Bot Service resource created by the publish flow
Channels → Microsoft Teams
Accept the Terms of Service
Hit Publish, then Apply

0 comments