updateDeviceProfileAssignment returning 200 OK and not 204 No Content

Question

The following issue I am having is that when trying to change the enrollment profile of an iOS device using .net and httpclient, I am getting back a 200 response with an empty object. I have tried both in my code and with in Graph Explorer. Just last week I was getting a response 204

https://graph.microsoft.com/beta/deviceManagement/depOnboardingSettings/{####}/enrollmentProfiles/{####}/updateDeviceProfileAssignment

{
    "deviceIds": [
        "serialNumber"
    ]
}

Headers:
Authorization: Bearer {token}
Accept: application/json

Permissions Granted:
DeviceManagementServiceConfig.ReadWrite.All, 
DeviceManagementConfiguration.ReadWrite.All

Here is the response:

200 OK

Preview:
{}

Headers:
{
    "client-request-id": "38ed1c72-7704-77f2-a979-cba9cc8a30ce",
    "content-length": "0",
    "request-id": "889d6054-4721-43ed-94e6-de8b636bb524"
}

The response should be a 204 and the profile should be changed. What am I missing? Getting the response of 200 at least means the call is working, but it's not adding the profile to the device. I assume that if that if the profile is added, then I would get the 204 response.

Answer 1

There is no difference in HTTP responses between a 200 with a body and a 204 without one. They are the same thing. Every HTTP client I'm aware of will behave the same way.

APIs can return either a 200 success with or without a body or they can provide a little extra context to the client and return a 204 which simply means there is no body. The client handles it the same either way. 2xx codes mean success, if there is a content body then additional information is available otherwise it isn't. It is up to the API to decide which it returns as there is no standard.

Bear in mind you're using the beta endpoint which can and will change while you're using it. Until it is stabilized you should be prepared for changes. Irrelevant 200 and 204 are interchangeable and your code should behave the same either way.