Get-MgBetaDeviceManagementManagedDeviceEncryptionState -Filter not work

[YohannTh]

Describe the bug

Get-MgBetaDeviceManagementManagedDeviceEncryptionState -filter "DeviceName eq 'PC-xxxx'" not working
Displays the complete list of devices without taking the filter into account
Get-MgBetaDeviceManagementManagedDeviceEncryptionState -Filter "EncryptionPolicySettingState eq 'compliant'" not working
Displays the complete list of devices without taking the filter into account
Get-MgBetaDeviceManagementManagedDeviceEncryptionState -Filter "EncryptionPolicySettingState eq '1'" not working
Displays the complete list of devices without taking the filter into account

The "Get-MgBetaDeviceManagementManagedDeviceEncryptionState -All" command does not show all devices. In particular, a Surface HUB v1 with the OS "Windows 10 TeamOS (119)". Is this normal?

Expected behavior

"Get-MgBetaDeviceManagementManagedDeviceEncryptionState" command to take filters into consideration.

How to reproduce

Get-MgBetaDeviceManagementManagedDeviceEncryptionState -Filter "EncryptionPolicySettingState eq 'compliant'"

SDK Version

2.28.0

Latest version known to work for scenario above?

No response

Known Workarounds

Using the "| Where-Object"

Debug output

Click to expand log

```

</details>


### Configuration

_No response_

### Other information

Only works with filter "id eq 'xxxx'".

[krallsm]

I have this exact same issue with Get-MgSubSite - This might help you, but I found in another bug report (#513) adding -Consistencylevel eventual as a workaround. I'm still in the process of testing this, but figured it'd be helpful to respond

[gavinbarron]

Implementation of filtering differs from API to API, so if you have a filtering issue for a different Cmdlet please raise a separate issue @krallsm

@YohannTh is there any example of a filter working that you can provide? If you can provide the output when running with the -Debug parameter we will be better able to help as this may be a service issue.

[microsoft-github-policy-service]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.