Teams Bot vs. Azure Bot
Hi, What is the differences between the Bot what you can setup on Teams' Development Portal and Azure Bots? Azure Bot's requires response group. But Bots from development portal seems to not requiring that. Is the development portal only way to setup such a bots, or should I be able to setup those bots from some other way as well?
Ability 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.
Getting "WebApplicationInfoIdConflictOnSideloadingIntoTeam" when trying to update a custom app
Hi, I'm trying to update the custom app that's already been published to the Teams store, I personally can't sideload it into my tenant, because I'm getting this error: `WebApplicationInfoIdConflictOnSideloadingIntoTeam` on this POST: `https://teams.microsoft.com/api/apps/emea/beta/users/apps/definitions/appPackage` The error has also been flagged by the Teams submission team, since they can't upload the newer version to the same tenant, hence they're not able to test it. I've tried deleting all the other test applications from Teams Admin as well as Teams itself, with no luck. I've been dealing with the issue for over a month now. Is there a way to publish a newer version of the app for testing purposes, would I have to duplicate it?
New Teams Workflow Based Webhooks Notification Issues
Hi all, Hoping someone else has experienced the same and is able to help out. We've started looking at migrating away from the old webhooks that are being deprecated and in to the Workflows replacement. One of the things we set up back at the start of October was using Azure Key Vault events alerting to alert about events as below: This was set up and working fine, the events sent a JSON payload that got parsed in the Workflow after being posted to the Teams webhook and then successfully posted in specific Teams Channels: This was all working great until some time recently when we went back and found that this functionality just no longer works and the Key Vault events metrics show all delivery attempts as failures. Once we'd enabled diagnostic logging for the delivery failures all that it really gives is that it was a bad request: { "time": "2024-11-22T09:52:15.9868768Z", "resourceId": "/SUBSCRIPTIONS/PLACEHOLD_SUB_ID/RESOURCEGROUPS/PLACERHOLDER_NAME/PROVIDERS/MICROSOFT.EVENTGRID/SYSTEMTOPICS/TEST-EVENTGRID-TOPIC", "eventSubscriptionName": "PLACEHOLDER_NAME", "category": "DeliveryFailures", "operationName": "Deliver", "message": "outcome=BadRequest, latencyInMs=170, id=PLACEHOLDER_ID, outputEventSystemId=PLACEHOLDER_ID, state=Filtered, deliveryTime=11/22/2024 9:52:15 AM, deliveryCount=0, probationCount=0, deliverySchema=EventGridEvent, trackedSystemTopicState=CreatedExplicitlyByUser, eventSubscriptionDeliverySchema=EventGridEvent, outputEventFields=InputEvent| EventSubscriptionId| DeliveryTime| State| Id| LastHttpStatusCode| DeliverySchema| LastDeliveryAttemptTime| SystemId| UseMappedResourceArmIdForBilling| TrackedSystemTopicState, outputEventFieldCount=, dedicatedQueueDeliveryQueueId=, requestExpiration=1/1/0001 12:00:00 AM, delivered=False id=PLACEHOLDER_ID, inputEventSystemId=PLACEHOLDER_ID publishTime=11/22/2024 9:52:15 AM, eventTime=11/22/2024 9:52:15 AM, eventType=Microsoft.KeyVault.SecretNewVersionCreated, deliveryTime=11/22/2024 9:52:15 AM, filteringState=FilteredWithRpc, inputSchema=EventGridEvent, publisher=MICROSOFT-KEYVAULT-VAULTS.UKSOUTH-1.EVENTGRID.AZURE.NET, size=662, subject=PLACEHOLDER_NAME, inputEventFields=Id| PublishTime| SerializedBody| EventType| Topic| Subject| FilteringHashCode| SystemId| Publisher| FilteringTopic| TopicCategory| DataVersion| MetadataVersion| InputSchema| EventTime| FilteringPolicy, inputEventFieldCount=16, type=HttpPost, subType=LogicApps, supportsBatching=False, aadIntegration=False, managedIdentityType=None, urlPath=PLACEHOLDER_URL, deliveryResponse=BadRequest, errorCode=BadRequest, HttpRequestMessage: httpVersion=1.1, HttpResponseMessage: HttpVersion=1.1, StatusCode=BadRequest(BadRequest), StatusDescription=Bad Request, IsRedirected=False, RedirectUrl=, "} I can point the Key Vault at another non-Microsoft webhook and it will successfully post the payload with no issue. I can also take the payload and post it to the above webhook myself and it will work fine, which leads mean to think it's either something in the way Azure posts these events has changed and the new Teams Workflow webhook doesn't like it, or the Teams Workflow webhook has changed in what it's expecting and the Azure events don't have what's required. If anyone else has experienced and overcome this issue it would be great to know what you did, as this is driving me round the bend. I'm not even sure if this is the right place to post about this problem! Thanks all.Teams or security groups should be searchable in the search field
Hello , Our users that we are connected to have stated that not being able to search for Teams teams or dl/sg causes a waste of time and that they meet this need on the Outlook side. In a similar way as in Outlook, searching for teams or groups will provide a mini window and displaying the features of members etc. will save time and be beneficial for users.
Is 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"?
Take ownership for a teams app on dev portal
Hi Microsoft Teams community, I'm an IT admin, and i'm having issues to find the owner of a published app on the MS teams store. Is there a way to know who the owner of an app is ? We need to update the manifest of the app. - Using the take ownership with the app ID is not allowing me to do it. No errors, it just doesn't do anything. Thank you
Steps to redeploy a Teams Apps after applying some changes and deploy it to local GIT repo
We already have a Teams Apps installed inside our Microsoft Teams Admin Center, the apps is inside GitHub @ https://github.com/OfficeDev/microsoft-teams-emergency-operations-center. Now we want to do some changes that will not be deployed to the upstream. So i did those steps:- 1) Clone the GitHub code locally 2) Do the modifications using Visual Studio code. 3) then push the changes to our BitBucket repository which is public 4) Now I will redeploy the manifest.json + the resources images to the Microsoft Teams Admin center. 5) I will modify the "Git Repo URL" field inside the existing custom deployment template , to reference our custom Repo inside Bitbucket instead of the upstream GitHub? My first question, are my above steps valid? and all the required steps? and can i modify existing template to change the "GIT Repo URL"? Second question, now inside our public Bitbucket repo we will have the ClientID and appdomain inside the manifest.json .. so can we hide them? or they will need to be there for the "Git Repo Url" to reference them? or those values are only needed inside the manifest .json uploaded inside our Microsoft Teams admin center? and doe snot require to be inside the public bitbucket repository? ThanksCan i get the Manifest.JSON file for a Teams app that is already installed our Microsoft Teams Admin
We have a Teams App already installed inside our tenant and users are using it:- Now i downloaded the code from this GitHUb site https://github.com/OfficeDev/microsoft-teams-emergency-operations-center >> and i modified the code using visual studio code to apply some customization based on our needs. Now to be able to deploy the updated Teams app, i need the following information inside the Manifest.json file:- AppDomain Website url ClientID now those should be already defined inside the current app which is already installed inside our Microsoft Teams admin center. but i can not find any option to download the current Teams App from our Teams admin center.. so how i can get these info to be able to upload my updated version of the app and replace the current version? Also i need the current app files, incase my updated app had some issues so i can revert back the old version of the app.. any advice? Thanks
Unable to get user details after Notification Bot is app installed
I've a Notification Bot, which is currently deployed to my organization, and all the users are able to see it and add to their teams app individually. I want to send welcome message to all users who've installed the app. I've an endpoint added in the bot framework which gives me an update whenever someone adds or remove the app in their teams app. But whenever someone is installing the app, I'm getting this error "Failed to acquire token". I've tried to install the app from Admin teams to all users as well from particular user by going to "Teams store > Built for your organization > App > click on "Add"". But both of the options are giving me same error. Here is the Bot permission given by admin in Portal Azure I've added the Application Id as myBotId according to the documentation and BotSecret as well Please help me in solving this problem. P.S. I don't know what this "d6d49420-xxxx-xxxx-xxxx-xxxxxx" resembles while the former one is my BotId i.e., "28c8b3b1-xxxx-xxxx-xxxx-xxxxxxxx". Thanks in advance.
