Skip to content

Remove WindowsPrivacyAccessControl from module generation #3326

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 1 commit into
base: dev
Choose a base branch
from

Conversation

FabienTschanz
Copy link

This PR excludes the deviceManagement_windowsPrivacyAccessControl resource from being generated into the DeviceManagement module. This is necessary because it otherwise is "merged" with the Get-MgBetaDeviceManagementDeviceConfiguration cmdlet, therefore resulting in a broken parameter set resolution.

deviceManagement_windowsPrivacyAccessControl is assigned the Get-MgBetaDeviceManagementDeviceConfiguration command in MgCommandMetadata.json. There, also the variants Access, AccessExpanded, AccessViaIdentity and AccessViaIdentityExpanded are defined. Having this definition there forces the merge of the default Get-MgBetaDeviceManagementDeviceConfiguration cmdlet with this object, although this should have a dedicated cmdlet, or even better, simply be excluded because it doesn't serve a purpose in having it.

Changes proposed in this pull request

  • Exclude the deviceManagement_windowsPrivacyAccessControl object from module generation.

@FabienTschanz FabienTschanz requested a review from a team as a code owner May 20, 2025 20:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Get-MgBetaDeviceManagementDeviceConfiguration - Wrong cmdlet definition
1 participant