Forum Discussion

bertold's avatar
bertold
Copper Contributor
Jun 03, 2025
Solved

Maximum # of scopes in manifest 1.21

I am looking at the 1.21 version of the https://developer.microsoft.com/json-schemas/teams/v1.21/MicrosoftTeams.schema.json and I see the definition below for the scopes properties. It only allows a maximum of 3 items, which means that you cannot allow all 4 available values to be defined. E.g. the following definition in the bot manifest would be invalid

scopes: ["team", "personal", "groupChat", "copilot"]

Is this intentional?

 

Thank you.

 

          "scopes": {
            "type": "array",
            "description": "Specifies whether the bot offers an experience in the context of a channel in a team, in a 1:1 or group chat, or in an experience scoped to an individual user alone. These options are non-exclusive.",
            "maxItems": 3,
            "items": {
              "enum": [
                "team",
                "personal",
                "groupChat",
                "copilot"
              ]
            }
          },
          "commandLists": {
            "type": "array",
            "maxItems": 3,
            "description": "The list of commands that the bot supplies, including their usage, description, and the scope for which the commands are valid. A separate command list should be used for each scope.",
            "items": {
              "type": "object",
              "additionalProperties": false,
              "properties": {
                "scopes": {
                  "type": "array",
                  "description": "Specifies the scopes for which the command list is valid",
                  "maxItems": 3,
                  "items": {
                    "enum": [
                      "team",
                      "personal",
                      "groupChat",
                      "copilot"
                    ]
                  }
                }

 

  • Thank you for your question. Yes, the "maxItems": 3 restriction in the schema for the scopes property is intentional. This means you can only specify up to three scopes out of the available options ("team", "personal", "groupChat", "copilot") for a given bot or command list.

    This limitation is likely in place to ensure clarity in the bot's experience and to avoid potential conflicts or ambiguities that could arise from enabling all possible scopes simultaneously. If you have a scenario that requires more than three scopes, you may want to provide feedback to Microsoft via the official documentation or support channels, as this could be a candidate for future schema updates

    Thanks,

    Smit Agrawal

    If the response is helpful, please click on "upvote" button. You can share your feedback via Microsoft Copilot Developer Feedback link. Click here to escalate




1 Reply

  • Thank you for your question. Yes, the "maxItems": 3 restriction in the schema for the scopes property is intentional. This means you can only specify up to three scopes out of the available options ("team", "personal", "groupChat", "copilot") for a given bot or command list.

    This limitation is likely in place to ensure clarity in the bot's experience and to avoid potential conflicts or ambiguities that could arise from enabling all possible scopes simultaneously. If you have a scenario that requires more than three scopes, you may want to provide feedback to Microsoft via the official documentation or support channels, as this could be a candidate for future schema updates

    Thanks,

    Smit Agrawal

    If the response is helpful, please click on "upvote" button. You can share your feedback via Microsoft Copilot Developer Feedback link. Click here to escalate




Resources