Broken Absolute URI referenced by New-MGBetaDeviceManagementconfigurationPolicyAssignment

[pmod2]

Describe the bug

I am from Microsoft internal team and recently came across a broken reference of the absolute URI with the New-MgBetaDevicemanagementConfigurationPolicyAssignment PS cmdlet. The PS cmdlet is running into a HTTP 400 error and the same absolute URI that is referenced by this cmd is returning HTTP 400 on Graph-

Absolute URI pointed by the PS command - /deviceManagement/configurationPolicies/{deviceManagementConfigurationPolicy-id}/assignments - Same URI returns HTTP 400 on Graph also

After capturing the network trace on the Intune portal we received the correct URI which returns HTTP 200 on Graph- Correct URI - https://graph.microsoft.com/beta/deviceManagement/configurationPolicies('')/assign

While we already have the workaround script with Invoke-MgGraphRequest and using the correct URI, there is still this bug with this PS cmdlet that customers might want to use to ensure uniformity across their script.

Expected behavior

PS cmdlet should point to the correct URI and give HTTP 200 as per the MS docs.

How to reproduce

1. Execute New-MGBetaDeviceManagementconfigurationPolicyAssignment command with appropriate permissions.
2. Returns HTTP 400 on PS command as well as on Graph (with the URI referenced by this cmd)

SDK Version

No response

Latest version known to work for scenario above?

No response

Known Workarounds

Invoke-MgGraphRequest can be used as a workaround.

Debug output

Click to expand log

```

</details>


### Configuration

_No response_

### Other information

_No response_