Latest Discussions
Question about "Open" button on the "About" of Teams Android mobile
Dear Sir Unlike iOS mobile, I found "About" tab on Teams Android mobile. I works well. However, there is an "Open" button at the bottom side. I'm still developing my Teams app. So I'm testing the app by locally upload. The "Open" button of My app is not activated. Other app installed from Teams Store has the button activated below. Do I have to set/configure to activate this "Open" button on the About? Otherwise, is it related to Teams Store production. Many thanks BH10Views0likes1CommentTeams bot not working when deployed
I have developed a RAG chat bot with Azure OpenAI and Teams Toolkit for VSCode. When I run the app in debug it works perfectly as expected, the problem is when I upload it to Teams it only sends the welcome message, then error messages. I published it to Teams with "Zip Teams App Package", and uploaded the zip file there. I suspect there might be a problem with the manifest, but would be grateful for any other pointers that might cause this issue. This is what my manifest file looks like:tjsonNov 08, 2024Copper Contributor21Views0likes1CommentReal-time Microsoft Teams Phone (PSTN) Events & Bot Joining Calls Automatically
I’m working on a solution to capture real-time events from Microsoft Teams Phone(PSTNCalling), specifically for events like: Outbound calls Inbound calls My goal is not only to capture these events but also to have a bot, built with the Microsoft Bot Framework, join the calls as soon as they start. Here are a few questions I have: Capturing Events: What is the best way to retrieve these specific events in real time? I’ve explored the Microsoft Graph API, but I’m uncertain if it provides what I need for Teams Phone (PSTNCalling). Bot Joining Calls: How can I programmatically have the bot join a call automatically? I’ve read about call automation and using the Graph API for joining calls, but not sure how to get the meeting id of teams phone (pstn) calls real or near real-time. Any advice or relevant documentation would be really helpful! Thanks!Eric BrasherNov 08, 2024Copper Contributor19Views0likes1CommentIs there a way to edit or change the "Bot Added" notification on Teams Mobile client
Hi everyone, Is there a way to change the generic notification “Bot added“ that we get on teams mobile when an app is added automatically to a meeting by a setup policy? I do not see any notification on the left chat sidebar on the desktop client. I can see a notification saying "Your organization has added test bot to the meeting" in the chat window of the meeting. Can we edit the notification "Bot Added" in the mobile client to include the name of the bot that got installed in the meeting like "Test Bot added"?18Views0likes1CommentTeams message extension on outlook
Hi, We have a message extension on MS Teams that is also showing on outlook. Is there a way to make it Teams only? on the provisioning on the teamsapp.yml we had this: # Extend your Teams app to Outlook and the Microsoft 365 app - uses: teamsApp/extendToM365 with: # Relative path to the build app package. appPackagePath: ./appPackage/build/appPackage.${{TEAMSFX_ENV}}.zip # Write the information of created resources into environment file for # the specified environment variable(s). writeToEnvironmentFile: titleId: M365_TITLE_ID appId: M365_APP_ID This was setting a channel on the Azure Bot Service for Microsoft 365. We removed this and don't have a M365 channel setup anymore, but the message extension is still appearing on outlook, is there another configuration to disable that?PedroKleinNov 08, 2024Copper Contributor501Views0likes5CommentsAbility to add metadata to manifest to inspect when receive chat for routing to different pipelines
Hello, We have developed a Microsoft Teams application that we deploy from the Microsoft Teams store. So, we have a single inbound chat channel (Azure Bot) for multiple inbound tenants - and we route to the custom tenant\instance base on their tenant ID. It all works great. Chime V5 site We have some customers who deploy our solution for IT Support, HR, and even legal departments. When our customers deploy, they generally take our app manifest, possibly update the icon and name, and then push to the left side navigator of their MS Teams clients. If they are just using the IT Support chat service, then is simple an only involves pushing one manifest. Info on some of the MS Teams app package stuff. However, since the traffic is taking place using a single inbound chat channel, and some customers might want 3 separate MS Teams navigation\bots (IT Support, HR Questions, Legal) we currently can only install one icon and then we need display some menu (adaptive card) when the employee starts a chat. This is OK, but not great. So, we might have 1, 2, or even 10 chat services that we deploy for a customer. Right now, we place all of these behind one MS Teams icon on the left side navigator. For instance: Blog article on pushing to teams If we could attach some metadata (even a very simple int) to a field in the manifest, and have this value attached to chat session, then we could attach multiple icons to the left side navigator - and automatically 'route' the inbound chat to the appropriate chat service. For example, these are all totally different chat services (bots) that have different AI prompts, agent routing options, adaptive cards, and UI. We'd like to be able to create unique icons on the MS Teams client for each chat pipeline - and some simple addition to the manifest could help with this Is there anyway to 'attach' any custom metadata at the MS Teams manifest level and have that value included as part of the chat conversation? For instance, basic IT Support would be a 1 HR requests 2 Legal 3 and we could use our single service, and Azure Bot, to take in 3 different requests from 3 different icons and have them routed to the appropriate bot pipeline.10Views0likes0CommentsCSS Properties being stripped from Teams Chat messages from Bot
Hi Team, We've noticed that certain CSS properties are no longer appearing in HTML messages when sent to Teams Chat. Previously, our bot styled messages using display and border properties, but now these properties are missing from the HTML when we inspect the page. Steps to Reproduce: Start the Echo bot from the sample templates (I used Teams Toolkit to deploy it to Teams or run it in the Test tool). In the TeamsBot.ts file, modify the onMessage function by replacing await context.sendActivity(...) with the following code. This example adds styling to an echo message. const a: Partial<Activity> = { text: `<span style="display: block; color: red; border-radius: 4px; padding: 4px; border: 1px solid red; ">Echoo:</span> <span style="display: block;">${txt}</span>`, textFormat: TextFormatTypes.Xml }; await context.sendActivity(a); Note: I also tried sending the HTML directly with context.sendActivity(...) without setting the textFormat property in the Activity, and observed the same result. Run the bot in the Test tool and Teams to compare behavior. Observed behavior: In the Test tool: All styles are applied as expected. In Teams: Only the color property is applied, while display, padding, and border properties are ignored (stripped out of the HTML). Here’s an example of the HTML output in Teams: <div dir="auto" id="content-1730973548675" aria-label="Echoo: test styles properties" class="fui-Primitive ___16zla5h f1oy3dpc fqtknz5 fyvcxda"> <span style="color: red;">Echoo:</span> <span>test styles properties</span> </div> Could you provide insights on whether this change is intended, and if there are any workarounds for preserving these CSS properties in Teams messages? Thank you!CedricZimmermannNov 07, 2024Copper Contributor77Views8likes0CommentsNot receiving online meeting change notifications
Hi, I did the following but I did not receive any online meeting notifications when I started/joined the meeting. Created an online meeting using the graph api. Created an online meeting "created,updated" subscription using the graph api (beta). My notification URLwas hit for the token validation and the subscription was created successfully. When I used the joinWebUrl to join the online meeting from my browser, no change notifications were sent to my notification URL. How do I debug this issue? Thank you.dragon-flyNov 07, 2024Copper Contributor2.2KViews0likes18CommentsTeams application hosted media bot not calling webhook
I have setup a media bot as per the instructions mentioned in PsiBot. The TCP address has been added in the firewall. Necessary API permissions in App Registration has been provided. Currently, testing on local computer using ngrok and followed the instructions mentioned in the link above. Issues: In an online teams meeting an App is added to the meeting and a call to JoinCallAsync api for bot to join the call occurs, which is successful. But after that nothing happens. The bot is not added in the meeting. The call to webhook (api/calling) should be called which is not happening. Please guide what should be done to add the bot to the meeting to fetch the audio of participants. 1. Ngrok points TCP to: Forwarding tcp://0.tcp.in.ngrok.io:12345 -> localhost:8445 In domain added the below record: CNAME 0.local.bot mapped to 0.tcp.in.ngrok.io Created certificate using openssl for *.local.bot.example.com and added in the Microsoft Management Control under Personal Certificates. The program has accepted this certificate i.e. no exception occurred. 2. Added all the ports, domains, endpoints, application id in the appsettings of the project. 3. Set supportsCalling to true in manifest file How can the issue be traced? Please guide.121Views0likes7CommentsTeams Connectors Actionable Message throwing Target URL Not Found
Hi, I had developed a Microsoft Teams connector for our application, that can post requests from MS-Teams Message cards to our application, but since yesterday the Actionable messages are failing with the exception { displayMessage: "<p>Target URL is not allowed.</p>\n", errorCode: "InvalidTargetUrlException" } This error is not just applicable to our connector, but other published connectors like Trello's and Incoming Web hook Connectors. I realise there was an update with MS-Teams yesterday, did that in someway made changes to the connector actionable messages? Expecting a response at the earliest possible.BaluVijayaKumarNov 07, 2024Copper Contributor1.7KViews0likes3Comments