Skip to content

Update PIM-G to align with Role Eligibility #6124

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

Open
wants to merge 3 commits into
base: Dev
Choose a base branch
from

Conversation

mpoulson
Copy link
Contributor

Pull Request (PR) description

  • Update PIM-G to align with Role Eligibility and allow UPN for users
  • work with owner (and not just member)
  • fix bugs with multi schedules per group

This Pull Request (PR) fixes the following issues

Task list

  • Added an entry to the change log under the Unreleased section of the file CHANGELOG.md.
    Entry should say what was changed and how that affects users (if applicable), and
    reference the issue being resolved (if applicable).
  • Resource parameter descriptions added/updated in the schema.mof.
  • Resource documentation added/updated in README.md.
  • Resource settings.json file contains all required permissions.
  • Examples appropriately added/updated.
  • Unit tests added/updated.
  • New/changed code adheres to DSC Community Style Guidelines.

Mike Poulson added 2 commits May 26, 2025 15:50
@M365DSCApprover
Copy link
Collaborator

This would be a breaking change, meaning the soonest we could release it would be during the first week of October.

@mpoulson
Copy link
Contributor Author

@NikCharlebois - Given this resource was fairly badly broken I find it hard to believe it was used much if at all. Is there a logic path to use the telemetry collected to determine if this breaking change would actually be impactful before October?

The existing resource

  1. Didn't support >1 assignment per group
  2. Only supported member assignments not owner

It isn't a blocker for me if not, just hoping to not have to do custom patches on my local builds for a few months.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

AADGroupEligibilitySchedule should not use DisplayName as key
3 participants