TeamsGroupPolicyAssignment TeamsModule bug in getting priority

[sandrola]

Description of the issue

A bug in Teams Module get different priority when used with / without attribute.
Get-CsGroupPolicyAssignment output can differ from Get-CsGroupPolicyAssignment -GroupId $Group.Id -PolicyType $PolicyType output.

Solution:
Use always Get-CsGroupPolicyAssignment and search for GroupId / PolicyType in a Where clause.

Microsoft 365 DSC Version

V1.24.1204.1

Which workloads are affected

Teams

The DSC configuration

n/a

Verbose logs showing the problem

Environment Information + PowerShell Version

[NikCharlebois]

This will have a major impact on the performance of the resource. I understand we don't have much of a choice since this appears to be a bug with the Teams PowerShell module. It will loop in the appropriate team for review. Can you provide additional examples with outputs to clearly show the bug? Thanks

[sandrola]

The printscreen show the 'Rank' differences if the same policy on the same group is retrived with the different method.