Mario

@skghq Thanks! I will adjust the resource to skip such Teams during export.

@ricmestre It is just my personal opinion, but in this case the Export method cannot even call the Get method, because we have a validation of the display name length...

@ricmestre Is there a Github issue for this? I think we should not mix similar issues for different resources here.

Seems to be a bug in the get method. It is using the name of the filter policy instead of the rule. I will work on this.

You have two resources with the same name (TeamsChannel-test) in your config. Please remove or rename one of them. The resource identifier must be unique.

Could you please share the corresponding DSC configuration? The error message sounds like you have two resources with the same display name (this is the key property for a Teams...

The attached config looks good, I cannot detect the conflicts from the error message. But the M365 DSC version used to generate the config is old, could you please try...

The TeamsUser resource has no Certificate parameter, it is called CertificateThumbprint. Please have a look at the documentation: https://microsoft365dsc.com/resources/teams/TeamsUser/

The error message says "Certificate not found". Is the mentioned thumbprint correct and is the certificate in the cert store accessible for DSC? Maybe you can try with credentials instead...

Is your Connect-MicrosoftTeams command working? It is using another CertificateThumbprint than mentioned in the error message