MS Graph Beta: POST /workplace/sensorDevices/ingestTelemetry returns HTTP 500 "An unknown error occurred"

Niels Heidbrink 0 Reputation points
2025-12-05T10:11:11.72+00:00

I'm trying to create a proof-of-concept for the Microsoft Places API/SDK. The goal is to dynamically mark desks in the Places app as available/unavailable (as in setting occupancy to true/false) based on some telemetry data ingested from an external system.

For this to work it is my current understanding that I would need to use the MS Graph (Beta) API/SDK.

I was able to set up rooms/sections/desks etc. in the Places admin app. I have also been able to create sensor devices using the SDK.

However, when trying to ingest telemetry data using the "POST https://graph.microsoft.com/beta/workplace/sensorDevices/ingestTelemetry" I'm getting an error:

HTTP 500 Internal Server Error
{
	"error": {
		"code": "internalServerError",
		"message": "An unknown error occurred",
		"innerError": {
			"date": "2025-12-05T06:43:16",
			"request-id": "XXXXX",
			"client-request-id": "XXXXX"
		}
	}
}

Am I doing something wrong or is there a bug in the API implementation?


Moved from: Microsoft 365 and Office | Other

Windows development | Windows App SDK
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Q&A Assist
    2025-12-05T10:11:28.94+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    When encountering an HTTP 500 Internal Server Error with the Microsoft Graph API, it typically indicates a problem on the server side rather than an issue with your request. Here are a few steps you can take to troubleshoot the problem:

    1. Check for Known Issues: Before proceeding, verify if there are any known issues with the Microsoft Graph API that could be affecting your request. You can check the Microsoft Graph known issues website.
    2. Review API Documentation: Ensure that your request conforms to the expected format and requirements as specified in the API documentation. This includes checking the payload structure, headers, and any required permissions.
    3. Inspect the Request: Log the request details, including headers and body, to ensure that everything is formatted correctly. Sometimes, minor errors in the request can lead to server errors.
    4. Check Throttling Limits: If you are making multiple requests in a short period, you may be hitting throttling limits. Review the throttling limits to ensure you are within the acceptable range.
    5. Generate Client-Request-ID: Include a unique client-request-id in your request headers. This can help in tracking the request and diagnosing issues if you need to contact Microsoft Support.
    6. Retry the Request: Sometimes, server errors can be transient. Try resending the request after a brief wait.

    If the problem persists after these steps, consider reaching out to Microsoft support with the request-id and client-request-id provided in the error response for further assistance.


    References:

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.