TeamsGroupPolicyAssignment: Export stops if it finds an assignment with an orphaned/deleted group

[ricmestre]

Description of the issue

While with a customer performing an export of their policies we found a problem with one of their TeamsGroupPolicyAssignments where the assignment was done to an already deleted group and therefore the export of TeamsGroupPolicyAssignment resources stopped, fortunately only skipped one additional assignment that wasn't exported but it means that with this problem it could basically skip dozens or hundreds of assignments if a single problem with an assignment is found.

Fix is to skip the assignment to the next one if group is not found.

EDIT: Actually now that I've looked again it skipped only one additional assignment when the error occurred but it didn't save any of the other assignments that it had already exported to the final blueprint.

Microsoft 365 DSC Version

1.24.228.1

Which workloads are affected

Teams

The DSC configuration

N/A

Verbose logs showing the problem

N/A

Environment Information + PowerShell Version

OsName               : Microsoft Windows 11 Enterprise
OsOperatingSystemSKU : EnterpriseEdition
OsArchitecture       : 64-bit
WindowsVersion       : 2009
WindowsBuildLabEx    : 22621.1.amd64fre.ni_release.220506-1250
OsLanguage           : en-US
OsMuiLanguages       : {en-US, en-GB}

Name                           Value
----                           -----
PSVersion                      5.1.22621.1778
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.22621.1778
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1