-
Notifications
You must be signed in to change notification settings - Fork 503
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[draft] IntuneDeviceManagementComplianceManagementPartner #5333
base: Dev
Are you sure you want to change the base?
[draft] IntuneDeviceManagementComplianceManagementPartner #5333
Conversation
…ttps://github.com/salbeck-sit/Microsoft365DSC into IntuneDeviceManagementComplianceManagementPartner
…ttps://github.com/salbeck-sit/Microsoft365DSC into IntuneDeviceManagementComplianceManagementPartner
Posted an issue with regards to ConvertTo-IntunePolicyASsignment silently dropping assignments for groups that can't be read - this includes unit-tests failing in spite of required mocks. The easy workaround was to omit datatype *GroupAssignmentTarget from unit-tests. However in cross-tenant scenarios it's not implausible to reference a group that might not exist and in such a situation the resource should emit some sort of warning |
updated resource to write event if a group is unknown - when getting assignments that refer to an unkown group, a warning is written, when setting assignments that refer to an unknown group, an error is written. I'm still undecided if that should cause an exception to avoid thinking that a configuration was updated if it really wasn't. |
…ttps://github.com/salbeck-sit/Microsoft365DSC into IntuneDeviceManagementComplianceManagementPartner
Pull Request (PR) description
Initial release (take two).
CimInstances from DRG-generated resource has been 'flattened' to one level and property GroupDisplayName has been added to ensure cross-tenant capability.
I have omitted property 'lastHeartbeatDateTime' although it appears possible to modify it.
Not too sure about property 'CollectionId' in the ...AssignmentTarget CimInstance. Advice is welcome.
This Pull Request (PR) fixes the following issues