"NO Odata route" error message when trying to delete Intune device compliance policy assignments

[Kvikku]

Describe the bug

I am trying to delete Intune device compliance policy assignments (Entra groups) from compliance policies in Intune, both in graph explorer and using C# SDK, but I get this error:

"No OData route exists that match template ~/singleton/navigation/key/navigation/key with http verb DELETE for request /DeviceConfiguration_2311/StatelessDeviceConfigurationFEService/deviceManagement/deviceCompliancePolicies('{5ea2aa68-e1aa-4dd7-b9aa-779e3a3f9d87}')/assignments('{5ea2aa68-e1aa-4dd7-b9aa-779e3a3f9d87_6f32bcce-4c71-4ef4-b80c-1a08974a7eb3}').",

5ea2aa68-e1aa-4dd7-b9aa-779e3a3f9d87 is my compliance policy

5ea2aa68-e1aa-4dd7-b9aa-779e3a3f9d87_6f32bcce-4c71-4ef4-b80c-1a08974a7eb3 is the assignment ID, which includes the above mentioned policy, as well as my Entra group (6f32bcce-4c71-4ef4-b80c-1a08974a7eb3).

To Reproduce
Steps to reproduce the behavior:

1. Use this format in graph explorer

https://graph.microsoft.com/beta/deviceManagement/deviceCompliancePolicies/{5ea2aa68-e1aa-4dd7-b9aa-779e3a3f9d87}/assignments/{5ea2aa68-e1aa-4dd7-b9aa-779e3a3f9d87_6f32bcce-4c71-4ef4-b80c-1a08974a7eb3}

Would need to replace the ID's.

In C#:

await graphClient.Result.DeviceManagement.DeviceCompliancePolicies[policyID].Assignments[assignment.Id].DeleteAsync();

Expected behavior

According to the documentation this should work, but I am not experiencing that.

Screenshots
If applicable, add screenshots to help explain your problem.

Client version
Provide the client version number from the NuGet package.

6.51.0

Desktop (please complete the following information):

• OS: Windows 11 - 22631.2715
• Browser: Chrome
• Version 119.0.6045.160

Additional context
Add any other context about the problem here.

[andrueastman]

Thanks for raising this @Kvikku

The referenced documentation seems to the point to the v1.0 endpoint and not the beta endpoint. Any chance you can confirm if the behaviour happens on the v1.0 endpoint as well?

[Kvikku]

Thank you for the reply.

You are right about it pointing to 1.0. I didn't see that - my mistake!

I've tried with 1.0 now, but the result is the same.

Picture for reference

[andrueastman]

We're following up with the internal team to confirm if this API is supported via https://portal.microsofticm.com/imp/v3/incidents/details/443405526/home and will give feedback once we get confirmation.

[andrueastman]

@Kvikku Any chance you can confirm if this is still an issue?

[Kvikku]

Hello! I just tested it again yesterday, and it is still an issue.

An interesting note is that I also tried it with Powershell and the SDK for Graph, and I get the exact same error message and issue with that.

[baywet]

@andrueastman this incident got automatically archived by the service team without even looking at it.
I suggest you re-open as a sev3 this time, and you ping the OCE about that