Forum Discussion
MS Teams App requires approval although is unblocked and available to everyone.
Hi,
I have a MS teams bot (custom app) published via the MS Graph API to our org and team space.
It shows up under the MS Teams Admin with the following flag/settings:
Available to: Everyone
App Status: unblocked
Publishing Status: Published
Custom App: yes
When our teams admin tries to install the app in their MS teams client, it shows "request approval" button, and then shows in the ms teams admin that his user account has requested it.
As mentioned it's marked as available to everyone and is unblocked - not sure why it's requesting approval?
Then secondly our IT admin has recently changed some of our user roles, and so was thinking it could be that? if so, what role should our MS teams admin have in order to simply install the app rather than requesting approval for it?
Pls let me know if you need more information.
Thank you, Robert
- We are having the same issue with a prebuilt app (Culture Amp). Previously it was blocked for all users except for certain ones under the old policy structure. I went to add users to the policy to find the new changes for setting access in the Manage Apps section in Teams Admin Center. The app is set to unblocked and is assigned to particular users. The app has a padlock on its icon in the apps list within Teams and has a "Request" button, which of course does the same as the above poster. The request shows in the Teams admin, and it instructs us to change access to everyone or add them to a list of users. Doing so still does not allow the users to add the app to Teams. We're trying to test and roll this out to our users but as of now, can't. Powershell confirms that this app is not in the blocked apps list. I've done everything I can try to get this to work. Do we need to open an incident report to get this looked at? I find it unlikely that we are the only 2 people who are encountering this issue.
- We've also encountered inconsistencies with our custom app. On our testing tenant custom apps are enabled and every user has the same policies attached to them.
We published our custom app to our tenant and added all of our test accounts to it. We did this before the weekend (2-3 days ago). Our testers reported very inconsistent issues:
* One tester couldn't see the app in the 'made for your org' app listing at all.
* Two testers had to request approval from an admin. I couldn't easily approve their request as they were already in the 'app availability' list.
* At least 5 other tests were able to succesfully install the custom app and use it.
Did you happen to find a solution to this problem and/ or others with this problem?I have the same exact issue, I have had nothing but issues trying to deploy apps from Copilot Studio. I have tried uploading the app, publishing it, removing and re-adding. There is something seriously wrong with the solution. I have had nothing but issues with Copilot studio from bots not working on teams to deployments. At this point I am questioning the validity of this solution versus creating my own custom bot and not relying on copilot studio.
I have spent the last month designing a canvas app and finally finishes it. It's beautiful but useless.
Its been requested and approved, but we cannot get the app to display within the teams channel and it still shows as Requested. Its has certainly been approved for this team. Is this another classis MS situation where I need to wait like 24 hours in order for this to work?
Or am I missing something?
Or is this system just fkn broken?
- I have seen the same issue - deploying apps to Teams from the Custom Copilot doesn't work.
- Any update? We're running in to the same issue.
- Hi - I'm running into the same as the OP. I've tried deploying a few bots and a test app, but only have the option to request approval and it has the locked icon. We haven't made any policy changes and other conversation bots previously uploaded can be added to the Teams client. Its almost as if when I upload a new bot, its being considered a Third Party app and not a Custom App which we allow.
- Working on internal application for our startup. I can relate to your problem.
I've experienced bad user experience regarding MS Teams APP publish.
Who is in charge of Microsoft Teams need very quickly to consolidate all documentation.
from developing to publishing and monitoring.
you can basically have bot framework or apps developer portal or azure bot or using the Teams sdk in vs code. this is frustrating.
The time in which i'm waiting for an app to be available in my Org is outrageous.
I've used Slack before, it takes 5min to do all the cycle. in MS teams it can take *DAYS*.- The only reliable method I have seen is to deploy with Teams and wait the 1-2 days before your app updates, this is not a good solution in any way shape or form. We need the ability to deploy within a reasonable amount of time (<15 minutes).
- September and this is still an issue. Unless I give it to everyone it just doesn't work. Not only that but the only way to get it to even show in the store (for some some people) is to set the availability to " Show to everyone" then, restrict via group. Only thing is, the second part doesn't work properly, if at all. You suck Microsoft, yet another example of a half-baked system released to the public.
- All of a sudden i have the problem with every app, alltough all users can install and use apps by default. I cannot even approve the request, since it is available for everyone.
It also happened with apps, which are installed via setup policy.
Very strange
