Forum Discussion

smosche635's avatar
smosche635
Copper Contributor
Jan 05, 2024

Remove "Add to a meeting" from Bot app install scope?

I would like to prevent users from being able to install our Bot application into a "meeting". See the attached image. I have added "team" as the "defaultInstallScope" and my bot's scopes are defined...
developer
meetings
microsoft teams
Prasad_Das-MSFT's avatar
Prasad_Das-MSFT
Icon for Microsoft rankMicrosoft
Jan 08, 2024

smosche635 - 

In your case, you have set the defaultInstallScope to "team" and your bot's scopes are defined as ["personal", "team", "groupChat"]. To remove the "Add to a meeting" option, you can set the defaultGroupCapability for the "meetings" scope to a capability other than "bot".

"defaultGroupCapability": {
  "team": "bot",
  "groupchat": "bot",
  "meetings": "tab"
}

In the above example, the default capability for the "meetings" scope is set to "tab". This means that when users try to install your app in a meeting, they will only see the option to add a tab, and the "Add to a meeting" option will be removed.

Ref: Manifest schema reference - Teams | Microsoft Learn

 

 

 

Thanks, 

Prasad Das

------------------------------------------------------------------------------------------ 

If the response is helpful, please click "**Mark as Best Response**" and like it. You can share your feedback via Microsoft Teams Developer Feedback link. Click here to escalate. 

smosche635's avatar
smosche635
Copper Contributor
Jan 08, 2024

Prasad_Das-MSFT Thank you for the reply. I did try your suggestion but I am still seeing "Add to a meeting" in the dialog box when I "Upload a custom app"  to Microsoft Teams for testing.

I have also tried to use "connector" in place of "tab" for the meetings value in `defaultGroupCapability` but I see the same options in the "add" menu.

 

 

Here is the relevant portion of my manifest:

"bots": [
  {
    "botId": "MY_BOT_ID",
    "scopes": [
      "personal",
      "team",
      "groupChat"
    ],
    ...
  }
],
"defaultGroupCapability": {
  "team": "bot",
  "groupchat": "bot",
  "meetings": "tab"
 },
"defaultInstallScope": "team"
 
I do see that if, for example, I remove "personal" from the scopes array, then "Add for me" no longer appears in the install list. So my manifest changes are able to affect the list. I do still want the "personal" scope, but I would prefer to not have "Add to a meeting" as one of the allowed install options.

Thanks for your help.
  • Prasad_Das-MSFT's avatar
    Prasad_Das-MSFT
    Icon for Microsoft rankMicrosoft
    Jan 09, 2024

    smosche635 - Could you please provide the app manifest zip which you used, so that we can investigate from our end?

      • Prasad_Das-MSFT's avatar
        Prasad_Das-MSFT
        Icon for Microsoft rankMicrosoft
        Jan 10, 2024

        scottmoschella - By removing the "meetings" capability from the defaultGroupCapability object in the manifest also we are able to get the option to add the app to any meeting.

         

         

        We have raised a bug for the same. We will inform you once we get any further update from engineering team. 

         

         

        Thanks, 

        Prasad Das

        ------------------------------------------------------------------------------------------ 

        If the response is helpful, please click "**Mark as Best Response**" and like it. You can share your feedback via Microsoft Teams Developer Feedback link. Click here to escalate. 

         

Resources