Chatbot Built on Azure (https://sop-chatbot-ui.azurewebsites.net/) is not working Desktop Teams but its working on Web teams as well as Teams on Mobile

Question

Chatbot Built on Azure (https://sop-chatbot-ui.azurewebsites.net/) is not working Desktop Teams but its working on Web teams as well as Teams on Mobile

R Thirividhi 0

We have a built an Internal SOP Chatbot using RAG Architecture and deployed as web app at the url - https://sop-chatbot-ui.azurewebsites.net/. We are able to access the chatbot in the Web Teams and Mobile Teams but when we try on dektop teams, it doesnt work. We just see a blank screen.

Screenshot from Desktop Teams.

User's image

Screenshot from Web

User's image

2 answers

Your answer

Answer 1

Anshika Varshney 1,910 Microsoft External Staff Moderator

Hello R Thirividhi,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

This usually happens because the Teams desktop client sometimes has stricter rendering rules compared to the web or mobile versions, especially when the chatbot UI is loaded inside an iFrame.

A couple of things you can try: first, confirm that the web app (https://sop-chatbot-ui.azurewebsites.net/) opens properly in a normal desktop browser, if it does, then the issue is more about how Teams desktop handles embedded content. Also, check if there are any Conditional Access or security policies applied in your org that may block the desktop Teams app from loading the site, while still allowing it in web or mobile clients.

As a workaround, since it’s working fine on Web Teams and Mobile Teams, you can continue using those until the desktop experience is adjusted. Some organizations resolve this by modifying their Teams app manifest settings or updating allowed domains for embedded content. If that applies, it might be worth checking your Teams app configuration.

Some documents for your References:

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

If you feel that your quires have been resolved, please accept the answer by clicking the "Upvote" and "Accept Answer" on the post.

Thank you!

Anshika Varshney 1,910 Reputation points Microsoft External Staff Moderator

2025-09-23T09:09:10.4266667+00:00

Hello R Thirividhi,

Following up to see if the above answer was helpful. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Thankyou!
Anshika Varshney 1,910 Reputation points Microsoft External Staff Moderator

2025-09-24T13:23:58.27+00:00

Hello R Thirividhi,

Just checking in to see if you have got a chance to see my response to your question in resolving the issue.

If you feel that your quires have been resolved, please accept the answer by clicking the "Upvote" and "Accept Answer" on the post.

Thank you!
R Thirividhi 0 Reputation points

2025-10-16T23:00:16.3133333+00:00

Hi Anishka, Chatbot is still not working. We could not find any security policies that would limit chatbot in Teams. Could you please help with instructions on modifying Teams app manifest settings. If possible, can we have a screen share session?Here is the App Manifest.Json text -

{"$schema":"https://developer.microsoft.com/en-us/json-schemas/teams/v1.23/MicrosoftTeams.schema.json","version":"1.0.0","manifestVersion":"1.23","id":"4c5bcc0e-c447-409d-a347-5b4036942a44","name":{"short":"SOP RAG"},"developer":{"name":"tSoft","websiteUrl":"https://sop-chatbot-ui.azurewebsites.net/","privacyUrl":"https://sop-chatbot-ui.azurewebsites.net/","termsOfUseUrl":"https://sop-chatbot-ui.azurewebsites.net/"},"description":{"short":"SOP RAG ChatBot","full":"SOP-Ensure consistency, quality, safety, and compliance."},"icons":{"outline":"outline.png","color":"color.png"},"accentColor":"#780202","staticTabs":[{"entityId":"7984a75a-4026-439f-96b3-8e3180450de3","name":"SOP-RAG-ChatBot","contentUrl":"https://sop-chatbot-ui.azurewebsites.net/","websiteUrl":"https://sop-chatbot-ui.azurewebsites.net/","scopes":["personal"],"context":["personalTab"]}],"validDomains":["sop-chatbot-ui.azurewebsites.net"],"webApplicationInfo":{"id":"8e127efe-bbde-493a-a614-fdcdd17768cf"}}

Sandeep Singh 0

{
  "$schema": "https://developer.microsoft.com/en-us/json-schemas/teams/v1.23/MicrosoftTeams.schema.json",
  "version": "1.0.0",
  "manifestVersion": "1.23",
  "id": "4c5bcc0e-c447-409d-a347-5b4036942a44",
  "name": {
    "short": "SOP RAG"
  },
  "developer": {
    "name": "tSoft",
    "websiteUrl": "https://sop-chatbot-ui.azurewebsites.net/",
    "privacyUrl": "https://sop-chatbot-ui.azurewebsites.net/",
    "termsOfUseUrl": "https://sop-chatbot-ui.azurewebsites.net/"
  },
  "description": {
    "short": "SOP RAG ChatBot",
    "full": "SOP-Ensure consistency, quality, safety, and compliance."
  },
  "icons": {
    "outline": "outline.png",
    "color": "color.png"
  },
  "accentColor": "#780202",
  "staticTabs": [
    {
      "entityId": "7984a75a-4026-439f-96b3-8e3180450de3",
      "name": "SOP-RAG-ChatBot",
      "contentUrl": "https://sop-chatbot-ui.azurewebsites.net/",
      "websiteUrl": "https://sop-chatbot-ui.azurewebsites.net/",
      "scopes": [
        "personal"
      ],
      "context": [
        "personalTab"
      ]
    }
  ],
  "validDomains": [
    "sop-chatbot-ui.azurewebsites.net"
  ],
  "webApplicationInfo": {
    "id": "8e127efe-bbde-493a-a614-fdcdd17768cf"
  }
}

Sandeep Singh 0 Reputation points

2025-10-16T23:36:05.6833333+00:00

Please look this Manifest file
Sandeep Singh 0 Reputation points

2025-10-18T01:58:40.9933333+00:00

Hi Anshika Varshney,
Did you have a chance to look at these ?
Anshika Varshney 1,910 Reputation points Microsoft External Staff Moderator

2025-10-18T07:43:05.55+00:00
Hello Sandeep Singh & R Thirividhi,
The issue is likely related to Teams App Manifest configuration or Azure AD permissions rather than security policies. Your manifest looks mostly correct, but a few critical points need attention:

1.Manifest Version

You are using "manifestVersion": "1.23". Ensure your Teams client supports this schema. If not, downgrade to "1.16" or the latest supported version

2.WebApplicationInfo

The id under webApplicationInfo must match the Azure AD App Registration (Client ID) for your bot. Example:

"webApplicationInfo": { "id": "<Azure AD App ID>", "resource": "https://api.botframework.com" }

If resource is missing, add it as shown above.

3.Valid Domains

Ensure all domains used by your bot (including authentication endpoints) are listed under "validDomains". If you use OAuth or other services, add those URLs.

4.Static Tabs

Your tab configuration looks fine for a personal scope. If you need team/channel scope, add "scopes": ["team"] and configure context accordingly.

5.Bot Section

If this is a chatbot, you need a "bots" section in the manifest:

"bots": [ { "botId": "<Azure Bot ID>", "scopes": ["personal", "team"], "supportsFiles": false, "isNotificationOnly": false } ]

Without this, Teams will not recognize the bot.

You can follow the additional steps as well.

Upload the updated manifest via Teams Developer Portal or App Studio.

Check Azure AD App Registration:

Add Teams as a channel in Azure Bot Service.

Ensure API permissions include User.Read and any required Graph scopes.

Enable SSO (if needed):

Configure webApplicationInfo properly for Teams SSO.

I hope this clears things up! If this guidance resolves your concern, please consider accepting the answer.
Anshika Varshney 1,910 Reputation points Microsoft External Staff Moderator

2025-10-21T11:12:42.33+00:00

Hello Sandeep Singh & R Thirividhi,

Did you get any chance to review the above response.

Thank you!
Sandeep Singh 0 Reputation points

2025-10-21T22:35:16.6266667+00:00

Thank you so much for information, I will look into today,

Answer 2

Sandeep Singh 0

1.Manifest Version
Latest stable version 1.23 and that's what we are using
2,WebApplicationInfo
The id under webApplicationInfo is matches with the Azure AD App Registration (Client ID)

3.Valid Domains : It matches

4.Static Tabs: it matches

5.Bot Section : This is "azure web app" not a chat app ; do we have to have BOT Section
I have configured the item: 1 - 4
I have the published to MS Teams still we are seeing some kind issue;

Web App works and Desktop Client doesn't
User's image

Anshika Varshney 1,910 Reputation points Microsoft External Staff Moderator

2025-10-22T20:44:22.9066667+00:00
Hello Sandeep Singh,

Thanks for sharing the details!
No, if your app doesn’t include a bot or messaging extension, you can omit the Bot section. Tabs‑only apps work fine without it.
This is a common issue because the Teams desktop client uses an embedded WebView, which is stricter than a normal browser. Typical causes:

Framing/CSP headers: Your app must allow Teams to frame it. Add this header to all tab pages:
Content-Security-Policy: frame-ancestors https://teams.microsoft.com https://*.teams.microsoft.com https://*.skype.com https://*.office.com;
Remove any X-Frame-Options: DENY or SAMEORIGIN.

Cookies and auth flow: If you use cookies for session/auth, set:

SameSite=None; Secure

Otherwise, auth may fail in desktop.

Teams JS SDK initialisation: Ensure you call microsoftTeams.initialize() (or app.initialize() for v2) before using Teams APIs.

Cache issues: After updating the manifest, bump the version (not manifestVersion) and reinstall the app. Clear Teams desktop cache or sign out/in.

I hope this clears things up! If this guidance resolves your concern, please consider accepting the answer.
Anshika Varshney 1,910 Reputation points Microsoft External Staff Moderator

2025-10-23T21:13:31.36+00:00

Hello Sandeep Singh,

Did you get any chance to review the above response.

Thank you!
Sandeep Singh 0 Reputation points

2025-10-23T22:37:37.8+00:00

Hi Anshika,This web app was deployed in Azure using the No code deployment option. Therefore, we were unable to locate any settings or code sections that would allow us to modify the Framing/CSP headers.
here's the screen how we deployed the code

Should we configure Azure Front Door for this purpose, or would it be necessary to download the source code locally and redeploy it to Azure App Service?

Share via

Chatbot Built on Azure (https://sop-chatbot-ui.azurewebsites.net/) is not working Desktop Teams but its working on Web teams as well as Teams on Mobile

2 answers

Your answer