When accessing data using https://graph.microsoft.com/beta/teams/{id}, it is failing with 400 bad request without any error details. {id} is the value received from the response of https://graph.microsoft.com/beta/groups.
Following response is returned.
{
"error": {
"code": "AuthenticationError",
"message": "Error authenticating with resource",
"innerError": {
"date": "2021-10-15T15:01:43",
"request-id": "1d82fe40-5186-46fc-9fb7-c16341eb1ffb",
"client-request-id": "29c9e68d-bfd8-6f53-65c4-c49a82581a76"
}
}
}
We tried using MS graph SDK as well as graph explorer. All the consent are given for the end point.
What could be the reason for the error?
Related
When I execute a request for a specific callRecord like this it works:
https://graph.microsoft.com/v1.0/communications/callRecords/{id}
But when I do this I get an error (500):
https://graph.microsoft.com/v1.0/communications/callRecords/{id}?$expand=sessions
{
"error": {
"code": "InternalServerError",
"message": "Object reference not set to an instance of an object.",
"innerError": {
"date": "2022-04-14T12:21:34",
"request-id": "{guid}",
"client-request-id": "{guid}"
}
}
}
It looks like this doesn't happen for every callRecord though. We started seeing this error in our logging around 2022-04-11T00:24:00Z, now we get thousands of those.
It was an internal issue on Microsoft's side. Everything seems to be fixed.
I have an active GraphAPI subscription to /communications/callRecords which is successfully returning the callid for calls. When attempting to get the call details using the following request:
https://graph.microsoft.com/beta/communications/callRecords/45578cfe-8329-48b7-ba6b-54a627b00bf4?$expand=sessions($expand=segments)
I receive the following error:
{
"error": {
"code": "BadRequest",
"message": "Unsupported segment type. ODataQuery: /communications/callRecords/45578cfe-8329-48b7-ba6b-54a627b00bf4",
"innerError": {
"date": "2020-11-24T12:34:11",
"request-id": "277b4fa1-11a5-4922-94d7-83fec3a57572",
"client-request-id": "277b4fa1-11a5-4922-94d7-83fec3a57572"
}
}
}
I get the same error if I change the GraphAPI call to /v1.0/. I am sure this worked previously but can't seem to work out what may have changed.
I need to read the list of synchtonizationProfile entities. I get accessToken using grant_type=code and requested permissions for EduAdministration.Read and EduAdministration.ReadWrite (as specified in the documentation).
But when I try the request, I get the following error:
{
"error": {
"code": "AuthenticationError",
"message": "Error authenticating with resource.",
"innerError": {
"request-id": "1a47270e-f902-48af-81cc-5ed8e279b050",
"date": "2017-12-21T12:20:27"
}
}
}
The problem only with the /synchronizationProfiles endpoint.
What is the problem? And how to solve it?
I'm using the Microsoft Graph Explorer on the Microsoft Planner (formerly Tasks) API.
I can requests users fine, e.g. /beta/users.
But when I try to access my plans using /beta/me/plans or /beta/plans/{ID}, I get an unknown error with the details below:
Status Code: 403
{
"error": {
"code": "UnknownError",
"message": "",
"innerError": {
"request-id": "62299f57-1792-4b0c-8b60-8613c54f4f50",
"date": "2017-01-17T21:12:51"
}
}
}
I'm trying to query the tasks on a plan that I own.
This API has changed. This URL should be
GET https://graph.microsoft.com/v1.0/me/planner/plans
POST https://graph.microsoft.com/v1.0/me/messages/AAMkADFkZDdjMWM0LTg2MzYtNGI4ZC1hNDAzLWY2NDljZmZmZDM4YQBGAAAAAAAy50dDcjLxRroxR16zN80WBwAqP1cdrk5dTLdAWYlr7M8QAAAAAAEPAAAqP1cdrk5dTLdAWYlr7M8QAAChu4WSAAA=/send
Suddenly started throwing this now (first it was seen on the beta endpoints. Now it is coming on v1.0 as well
{
"error": {
"code": "InternalServerError",
"message": "Object reference not set to an instance of an object.",
"innerError": {
"request-id": "eecf9817-1c44-4fa5-aabb-f975f8496484",
"date": "2016-09-25T09:16:43"
}
}
}