microsoftgraph / microsoft-graph-explorer-v4

React/Redux version of Graph Explorer used to learn the Microsoft Graph Api
https://developer.microsoft.com/graph/graph-explorer
MIT License
214 stars 93 forks source link

https://graph.microsoft.com/v1.0/sites API is returning 502 Bad Gateway #1918

Closed denisnigulas closed 2 years ago

denisnigulas commented 2 years ago

Describe the bug Unable to poll Microsoft Graph https://graph.microsoft.com/v1.0/sites API. It is returning 502 Bad Gateway even though other APIs work fine and there are no permissions or other issue. API appears completely broken from the MS side.

To Reproduce Steps to reproduce the behavior:

  1. Go to 'https://developer.microsoft.com/en-us/graph/graph-explorer'
  2. Sign-in with credentials (i used Global Admin creds) that has Sites.Read.All
  3. In the Sample queries list find 'Sharepoint Sites'
  4. Select 'GET my organization's default SharePoint site'
  5. Run Query

Expected behavior This API endpoint is supposed to return information about my organization default Sharepoint site but instead I get Bad Gateway - 502 - 112ms { "error": { "code": "UnknownError", "message": "", "innerError": { "date": "2022-07-12T02:48:46", "request-id": "81a213cf-8c39-4442-bd8f-7e964c690e8d", "client-request-id": "b8d5de76-1282-5090-48fe-a4ee923be096" } } }

Same behavior is exhibited when polling API through Postman.

Screenshots If applicable, add screenshots to help explain your problem.

Screen Shot 2022-07-11 at 7 17 28 PM

Desktop (please complete the following information):

Additional context All issues point to a broken API on the MS side. Please repair ASAP as this is impacting our operations.

Onokaev commented 2 years ago

Hey @denisnigulas. I've just tested this and its working on my end. image Are you still experiencing this issue?

denisnigulas commented 2 years ago

@Onokaev hey thanks for checking. So I did some more digging on my end and because we are developing a solution that works with Azure/MS365 APIs we have a couple of tenants. So I went ahead and tested with a portal that Azure team recently gave us as partners and it works fine there:

Screen_Shot_2022-07-12_at_1_21_32_PM

Now our older test tenant still fails exactly the same:

Screen Shot 2022-07-12 at 1 26 09 PM

My best guess here is the subscription level: the test tenant only has a Basic subscription and while I can't for some reason pull subscription information for the other one (maybe because I am not an admin there) I know it's higher.

But even if the subscription level is the issue here, this kind of error handling without any reasonable message is a bug, right?

Onokaev commented 2 years ago

Yes, it is. The error returned is confusing. However, this isn't an issue we can fix on Graph Explorer. For a wider audience, let me post this on the Microsoft Q&A side.

Onokaev commented 2 years ago

Here is a link to the issue I've opened on the Q&A side: https://docs.microsoft.com/en-us/answers/questions/951483/error-reporting-on-sitesroot-is-confusing-for-tena.html

Onokaev commented 2 years ago

From the Q&A response, this endpoint does not support personal tenants. This is the reason why you are getting 502s

Onokaev commented 2 years ago

Let me know if you need any further assistance

RabebOthmani commented 2 years ago

@adhiambovivian @Onokaev Looking at the thread above, it doesn't seem this ticket require any GE work. Is there any particular reason for it to be added to august milestone instead of being closed?

Onokaev commented 2 years ago

Hey @RabebOthmani. Not really. Let me remove it from the milestone. The bot will automatically close it tomorrow if there is no response from the author

ghost commented 2 years ago

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.