If you need a fix before Graph fixes the endpoint, these fields are causing the 500s allowedOnlineMeetingProviders
, and defaultOnlineMeetingProvider
. You can use $select
to get only the fields you need, excluding the two online meeting provider fields.
Getting 500 response errors to GET /me/calendars all of a sudden
We're suddenly seeing the following for a large number of Outlook and Hotmail users. This is a simple API call to the MS Graph Calendaring API.
This has also been raised as a case with Microsoft Support: #2506020050001353
GET https://graph.microsoft.com/v1.0/me/calendars/
Accept: application/json
Content-Type: application/json
Authorization: <>
Cache-Control: no-cache
Accept-Encoding: gzip, deflate, br
2025-05-27 13:22:59 B -1- received 500 response =>
HTTP 500
URL: https://graph.microsoft.com/v1.0/me/calendars/
Content-Type: application/json; odata.metadata=minimal; odata.streaming=true; IEEE754Compatible=false; charset=utf-8
Strict-Transport-Security: max-age=31536000
client-request-id: 64ca1aca-b971-4520-b75d-28bb17590cde
Date: Tue, 27 May 2025 11:22:59 GMT
x-ms-ags-diagnostic: {"ServerInfo":{"DataCenter":"France Central","Slice":"E","Ring":"5","ScaleUnit":"001","RoleInstance":"PA2PEPF000366F6"}}
Content-Encoding: gzip
request-id: 64ca1aca-b971-4520-b75d-28bb17590cde
Cache-Control: private
{"error":{"code":"ErrorInternalServerError","message":"An internal server error occurred. The operation failed."}}
Microsoft Graph
-
dewski • 35 Reputation points
2025-05-28T03:56:56.12+00:00 Getting this as well and on the Graph Explorer. Tried using
/me/calendars
as well as calendarGroups, and expanding events. None of those endpoints returns calendars. When requesting a calendar directly, also getting 500s. -
kawinn • 20 Reputation points
2025-05-29T11:15:51.7066667+00:00 I’ve been experiencing the same issue since around 05/19. I'm receiving 500 error responses for the
GET /me/calendars
endpoint on some user accounts, even though it was working previously. -
Rohit M • 20 Reputation points
2025-05-29T22:12:16.2166667+00:00 I experienced issue starting on Sunday May 25, 2025 via a dramatic increase in the 5XXs we observed
-
himanshu Jain • 20 Reputation points
2025-05-30T02:50:33.9866667+00:00 I've been experiencing this same issue for the past few days. It persists even with a new Microsoft account, and appears to be isolated to the
/me/calendars
API call; other API calls likes /me/events are working correctly. -
Joeg-8824 • 20 Reputation points
2025-05-30T19:37:31.19+00:00 Me too. Spent too much money downloading new calendars and troubleshooting shooting for 2 days. C'mon help
-
Jon Leigh • 5 Reputation points
2025-05-30T19:50:05.5066667+00:00 I’ve had this problem for about a week, having used exactly the same calls without any issues for several years.
Step 1 is to recognise something is wrong. Step 2 is to figure out what caused it (the timing should help)
Step 3 is to fix it.
Which step are you at?
-
Tuan Lima • 10 Reputation points
2025-05-30T19:56:20.64+00:00 I'm experiencing the same issue on me/calendars derived APIs.
-
Santiago • 15 Reputation points
2025-05-30T20:03:24.26+00:00 This issue has been affecting numerous developers for over a week, breaking previously stable integrations with /me/calendars. We need a clear update and ETA on a fix, NOW!
-
Romulo Novillo Jr • 5 Reputation points
2025-05-30T20:21:00.6466667+00:00 Me too!
-
Rohit M • 20 Reputation points
2025-05-30T20:27:26.6166667+00:00 this is the documentation link for the endpoint, I don't see any information about it being deprecated: https://learn.microsoft.com/en-us/graph/api/calendar-get?view=graph-rest-1.0&tabs=http
-
Enzo • 10 Reputation points
2025-05-30T20:31:10.3766667+00:00 Same issue here - fetching
/me/calendars
doesn't work. I'm in the final stages of wrapping up a critical project, and this issue with/me/calendars
is blocking us hard. Over 500 users depend on our app, and this unexpected failure is putting the entire launch at risk. We urgently need clarity and an ETA on a fix. -
dewski • 35 Reputation points
2025-05-30T20:52:35.2833333+00:00 It's worth noting I am not able to reproduce this consistently with all accounts. I have one account this works for, and another it doesn't.
-
Fahad Gilani • 320 Reputation points
2025-05-31T01:11:01.61+00:00 Unfortunately this continues to be a problem for our users, we're seeing the same thing - happening for a select few but we don't know why.
-
Marco Ancona • 6 Reputation points
2025-05-31T20:54:34.5566667+00:00 This requires attention, having the same issue. I noticed that the result changes depending on the $top parameter. For one of my test accounts any value > 11 (or following the @odata.nextLink link) causes the 500 error.
-
Rudy • 35 Reputation points
2025-05-31T21:07:48.2933333+00:00 same issue here
-
David Narine • 35 Reputation points
2025-05-31T23:13:17.3166667+00:00 Is there a way to open a support ticket with Microsoft - I am sure this is an oversight and just needs looking at.
-
Gary • 0 Reputation points
2025-06-01T06:02:41.7033333+00:00 Me too
-
corsall • 0 Reputation points
2025-06-01T16:25:02.3+00:00 Having the same issue
-
Jeroen B • 56 Reputation points
2025-06-02T07:21:09.9833333+00:00 Same issue here, according to our analyics 10K+ users are at least affected.
Also github issues have been raised:
https://github.com/microsoftgraph/microsoft-graph-explorer-v4/issues/3861 -
Marko • 0 Reputation points
2025-06-02T07:42:43.64+00:00 Same issue here!
-
aden micro • 0 Reputation points
2025-06-02T07:50:36.92+00:00 same issue here
-
Joeg-8824 • 20 Reputation points
2025-06-02T10:52:00.18+00:00 Unless Im not seeing it, This was not a solution just another acknowledgement ok the problem
-
Fahad Gilani • 320 Reputation points
2025-06-02T13:23:04.5266667+00:00 Yes I'd recommend this answer be deleted because this issue will otherwise go answered and unnoticed.
-
Jeroen B • 56 Reputation points
2025-06-02T13:26:29.7633333+00:00 I might have accidentaly marked it as helpful but I undid it. But still marked by someone else.
-
JUDY BLUNT • 0 Reputation points
2025-06-02T13:54:41.48+00:00 Affecting me too. . . .tried deleting app and reinstalling now all my appts are gone.
need this info back ASAP.
-
Andre vd Riet • 15 Reputation points
2025-06-02T15:05:47.07+00:00 Me too
-
Tuan Lima • 10 Reputation points
2025-06-02T15:07:02.26+00:00 I've noticed that the number of accounts affected has increased from last Friday to today.
-
Andre vd Riet • 15 Reputation points
2025-06-02T15:08:04.65+00:00 Me too, I have the same problem
-
Jeroen B • 56 Reputation points
2025-06-02T15:54:17.82+00:00 I expect that's normal since Microsoft usually uses a gradual rollout for their major cloud systems, to test if there are any problems with new changes.
-
Kimberley Mahabirsingh • 0 Reputation points
2025-06-02T17:10:38.8066667+00:00 Same issue on calendars derived APIs.
-
McKenzie Wiechman • 0 Reputation points
2025-06-02T18:15:02.2233333+00:00 Me too. I use a 3rd party app called BusyCal and am getting the same issue.
-
Aaron Johnson • 10 Reputation points
2025-06-02T18:46:36.23+00:00 We have the exact same problem over at Reclaim.ai... impacting about 25% of our users and many of our prospective new signups.
-
Ole Schmitto • 0 Reputation points
2025-06-02T19:17:16.2266667+00:00 Me too, same issue...
-
Fahad Gilani • 320 Reputation points
2025-06-02T19:20:26.0366667+00:00 AAron I'd encourage you to contact Microsoft Support as well and refer to them to this thread and case #2506020050001353. It's been much harder than it should have been to report a serious server-side issue.
-
Aaron Johnson • 10 Reputation points
2025-06-02T19:47:32.3966667+00:00 I already have contacted MS support from two different portals and have yet to receive a response.
-
Omid Rooholfada • 1 Reputation point
2025-06-02T20:05:07.08+00:00 Seeing the same issue
-
SiRi • 0 Reputation points
2025-06-03T09:11:26.78+00:00 I've been experiencing exactly the same issue for the past week, please solve this ASAP!
-
Denzyl Dick • 0 Reputation points
2025-06-03T09:18:58.2866667+00:00 I also have been experiencing the same issue.
-
Jeroen B • 56 Reputation points
2025-06-03T14:38:27.83+00:00 I just received a phone call from Microsoft Support and the team is notified and is working on it. They suggested to use the workaround. They cannot say anything about when it will be fixed.
-
Deleted
This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Sign in to comment
-
Tas Drake • 115 Reputation points
2025-06-02T21:04:23.55+00:00 -
Aaron Johnson • 10 Reputation points
2025-06-03T00:43:11.26+00:00 super helpful, we just deployed a workaround based on this and it's working great.... would have been really nice if someone from MS had posted a workaround and / or even acknowledged the issue.
-
Fahad Gilani • 320 Reputation points
2025-06-03T02:02:37.6366667+00:00 Beautiful. Thank you!!!!
-
Fahad Gilani • 320 Reputation points
2025-06-03T02:08:07.0266667+00:00 This seems to only be affecting Personal Outlook accounts right? O365 enterprise accounts continue to function
-
Aaron Johnson • 10 Reputation points
2025-06-03T03:24:53.3933333+00:00 From what I can see, yes, this is only impacting Personal Outlook accounts
-
Fahad Gilani • 320 Reputation points
2025-06-03T04:38:53.74+00:00 Confirmed - Microsoft broke something for personal accounts potentially as part of deprecating / removing Skype. I've now had users confirm a successful sync.
-
Fahad Gilani • 320 Reputation points
2025-06-03T04:41:01.6+00:00 What's truly infuriating is the entire bug reporting mechanism - Microsoft seems to have no official way for developers to report bugs. There's no transparency in bug fixes and there's absolutely no way to contact support without paying $100/month only so you get the privilege of sending them an email, and only to be gas lit by being told "it's a permission related issue at your end". Nightmare past 7 days trying to explain this to rightfully upset users.
-
mwf • 20 Reputation points
2025-06-03T05:23:59.3966667+00:00 How long before the fix from Microsoft? Does anyone have information on this?
-
Jeroen B • 56 Reputation points
2025-06-03T05:50:00.2233333+00:00 Well I don't mind paying for support, but we created a Severtiy A case at Microsoft support this Saturday and we haven't heard from it until now. It might even be that the Microsoft Graph team doesn't even know about this problem at the moment.
Also I would expect the critical Graph API's to be under daily integration testing so they would be notified if something breaks down. -
mwf • 20 Reputation points
2025-06-03T05:55:26.4+00:00 Where has the idea gone of a versioned API. I only see a V1.0 and beta, nothing in between. (I would appreciate a stable untouched API version, unless I opt in).
If I were on API V1.0, then I would not have expected two altered fields to affect my API version.
-
mwf • 20 Reputation points
2025-06-03T08:59:51.79+00:00 Is there any monitoring for the Graph API? - Was no ALARM triggered?
-
CRN Testing2 • 0 Reputation points
2025-06-12T14:00:45.54+00:00 Thank you sooooo much. This is really weird. if I created a new account then it works for "me/calendars". But after an hour it showed me "500 Error".
So as you mentioned @Tas Drake mentioned I passed $select and it's work.
This is really really weird.
Again thank you soo much .
Sign in to comment -