Graph API get private channel connected site url failing

Brass Contributor

I am following this article Manage lifecycle of private channels to get private channel's site url using App-Only authentication. As per the article, its giving the desired result for this first request

"GET https://graph.microsoft.com/beta/teams/<group_id>/channels?$filter=membershipType eq 'private'"

 but for second request

GET https://graph.microsoft.com/beta/teams/<group_id>/channels/<channel_id>/filesFolder

 its throwing error  "502 Bad Gateway". Can anyone suggest what could be the issue? 

Error: 

{ "error": { "code": "BadGateway", "message": "Failed to execute backend request.", "innerError": { "request-id": "6ab8032b-8d33-4543-b2f1-0e13978e9699", "date": "2020-02-05T07:00:11" } } }

@Jeremy Thake any tip why its failing?

8 Replies

@Prashant Gupta , This is a known issue at our end. We are working on it. We will let you know once the fix will be rolled out. 

@Trinetra-MSFT Good to know. Thanks.

Is there any place where do you follow these issues and report the fix for e.g. in github?

@Prashant Gupta , We are tracking this bug internally. We will let you once it is fixed.

@Trinetra-MSFT 

I get the same trying to create a channel with members as per documentation 

{
  "@odata.type": "#Microsoft.Teams.Core.channel",
  "membershipType": "private",
  "displayName": "My First Private Channel",
  "description": "This is my first private channels",
  "members":
     [
        {
           "@odata.type":"#microsoft.graph.aadUserConversationMember",
           "user@odata.bind":"https://graph.microsoft.com/beta/users('{9b5c5cc9-cafb-4fe4-a58d-5bdc96ea7712}')",
           "roles":["owner"]
        }
     ]
}

@Trinetra-MSFT  I get this error since Thursday, April 16th 2020 when trying to create a private channel in a team with the beta API. My code was working fine until then. Now I get a 502 Bad Gateway with «Error processing backend request.» error message :

 

Server error: `POST https://graph.microsoft.com/beta/teams/{my-team-id-is-here}/channels` resulted in a `502 Bad Gateway` response:
{
  "error": {
    "code": "BadGateway",
    "message": "Failed to execute backend request.",
    "innerError": {
      "request-id": "2ceece83-e3ff-455d-bc7b-b82f5454269f",
      "date": "2020-04-17T12:45:12"
    }
  } 

The JSON data posted :

 

displayName = "Private Channel Test"
membershipType = "private"
description = "Test"

Any update about this problem would be appreciated. I also opened a StackOverflow issue : https://stackoverflow.com/questions/61272195/microsoft-graph-502-bad-gateway-failed-to-execute-backe...

@tiois @Trinetra-MSFT Hi, as of today, I can read channels ok with a get, including private channels, but I cannot add members to a private channel using either POST to graph api or powershell.  Output is a 502 BadGateway.

Private channels are in high demand in university classes to be able to organise team assignments.  This worked at the start of the year, but is not working now.

@Ben Hatton @Trinetra-MSFT 

 

Hi, I'm also getting error: "Failed to execute Aad backend request GetUsersByObjectIdsS2SRequest. Workload Unknown"

 

I'm trying to create a private channel with the json structure indicated on the documentation. I have granted app al required permissions.