Open dotconfig404 opened 5 months ago
Thanks @dotconfig404 for using the SDK and for raising this.
This needs to be investigated to see if the SDK is generated for a functionality that does not exist in the Graph SDK.
We could try run the http version to confirm this, otherwise the our team will look into this.
I have tried using the Graph Explorer to check the http version, but it gave the same error back:
{
"error": {
"code": "No method match route template",
"message": "No OData route exists that match template ~/singleton/navigation with http verb POST for request /DeviceFE/StatelessDeviceFEService/deviceManagement/managedDevices.",
"innerError": {
"date": "2024-06-04T13:40:19",
"request-id": "b0426bf9-566e-4af6-9cdf-55da30716958",
"client-request-id": "bda47207-c55f-6a51-97a0-2d5ca2c0dcf9"
}
}
}
Any update? Is there an other way to update device compliancy state?
Describe the bug
In the SDK documentation for creating managed devices there is an example which does not work, I am not sure if this is a user error or a bug, maybe someone can help me here?
The example I am talking about is here, specifically the python version. https://learn.microsoft.com/en-us/graph/api/intune-devices-manageddevice-create?view=graph-rest-1.0&tabs=python
I am getting a 400 Bad Request error when using the example. The client object itself is not the problem, it works for all other calls without issues, my application has the required API permissions, but this is not related to that either since the error shows up without any permissions anyways.
Expected behavior
Should create a managed device when calling device_management.managed_devices.post(device)
How to reproduce
SDK Version
No response
Latest version known to work for scenario above?
No response
Known Workarounds
No response
Debug output
Click to expand log
```Configuration
No response
Other information
No response