Nik Charlebois

Still, I don't know how to reproduce this scenario. Trying to replicate your scenario, I get the following error when using the same name/display name for two sub-labels with a...

I am however able to reproduce the issue with Delta report. It's as if the function thinks DisplayName is the primary key. Stay tuned

Problem comes from here: https://github.com/microsoft/Microsoft365DSC/blob/Dev/Modules/Microsoft365DSC/Modules/M365DSCReport.psm1#L691 Will be looking at making this more dynamic

Will also work on adding support for ParentId as a separate PR

As mentioned by @ykuijs, this would have been fixed with the Fall Major release. We can re-open later if the issue still persists for you.

Closing due to inactivity

Trying to revive this thread. I like this idea. It would clearly be a breaking change across multiple resource however. We should start building a list of resources that are...

Not to my knowledge. The unique ids would end up being GUID which will ensure there are no conflicts. We could always keep a registry of already used GUID during...

Closing this one as other threads are also covering this. Also, we introduced the -Validate switch on the Export-M365DSCConfiguration cmdlet to assist with this.

Started some investigation on this. The Get-DLPSensitiveInformationTyupe cmdlet doesn't return much other than name and description. We are required to look at the DLPSensitiveInformationTypeRuleCollection property which is obtained by the...