Forum Discussion
SanaLabs
May 23, 2024Copper Contributor
Deployed Teams app cannot find any installation, but I've installed it via "Upload custom app"
I've followed the https://learn.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot?tabs=vscode docs to create a Team App that sends a "Hello World" message to an specific user (email)...
SanaLabs
May 24, 2024Copper Contributor
* The endpoint is not behind a firewall.
* The cloud service (and any other Azure resource) has been deployed with Microsoft Teams Toolkit for Visual Studio Code, following the aforementioned guide.
Something that I notice is that, if I visit the Azure Bot resource that was provisioned and I click on channels, I see a warning in Microsoft Teams with the message "The tenant admin disabled this bot". However, I made sure in Microsoft Team Admins that the application is not blocked and that the appropriate policies are assigned to the users.
* The cloud service (and any other Azure resource) has been deployed with Microsoft Teams Toolkit for Visual Studio Code, following the aforementioned guide.
Something that I notice is that, if I visit the Azure Bot resource that was provisioned and I click on channels, I see a warning in Microsoft Teams with the message "The tenant admin disabled this bot". However, I made sure in Microsoft Team Admins that the application is not blocked and that the appropriate policies are assigned to the users.
Vaibhav-MSFT
May 24, 2024Former Employee
Hi SanaLabs,
Can you check if you have approved the "grant request for publishing the app" from admin portal?
- SanaLabsMay 24, 2024Copper ContributorIn Microsoft Teams admin center, I have a global App setup policy that allows everyone to upload custom apps. I'm not sure if this is what are you referring to. The app is not yet published to my organization's store.
- Vaibhav-MSFTMay 27, 2024Former Employee
SanaLabs,
Yes it's same I was referring to. Can you please share the deployed manifest so we can test this from our end?- SanaLabsMay 27, 2024Copper Contributor
In the end, I was able to "fix it" by creating and provisioning a new app from scratch. I did not change anything about the manifests/deployment but this time I did not get the same error.
Vaibhav-MSFT