Adding MS Teams Tab (Planner) result in BadRequest

Asked Mar 26 '20 at 14:13

Active Mar 26 '20 at 14:13

Viewed 425 times

When trying to create a planner tab via graph api it always ends in a BadRequest error. I tried following request:

https://graph.microsoft.com/v1.0/teams/<tenant>/channels/<id>/tabs

Body:

{
    "displayName": "Planner",
    "teamsApp@odata.bind": "https://graph.microsoft.com/v1.0/appCatalogs/teamsApps/com.microsoft.teamspace.tab.planner",
    "configuration": {
        "entityId:": "<planId>",
        "contentUrl": "https://tasks.office.com/<tenant>/Home/PlannerFrame?page=7&planId=<planId>",
        "removeUrl": "https://tasks.office.com/<tenant>/Home/PlannerFrame?page=7&planId=<planId>",
        "websiteUrl": "https://tasks.office.com/<tenant>/Home/PlannerFrame?page=7&planId=<planId>"
    }
}

Result:

"code": "BadRequest",
"message": "Value cannot be null.\r\nParameter name: entity"

I also tried using the teamsAppId property instead of teamsApp@odata.bind. It ends up in another error: The navigation bind for the teamsApp was missing in request.

The request seems to be right when checking the graph api documentation.

asked Mar 26 '20 at 14:13

André

We can see this issue, we are looking into this Thanks. – Trinetra-MSFT Mar 27 '20 at 06:44
@Trinetra-MSFT is there an update from your side? – André Mar 31 '20 at 18:27
We filed a bug for this, We will update you once it is fixed. – Trinetra-MSFT Apr 15 '20 at 03:18
The issue is no longer repro at our end. – Trinetra-MSFT Sep 25 '20 at 07:16

Adding MS Teams Tab (Planner) result in BadRequest

0 Answers0