fix: add required Graph scope for Intune enrollment and fix permission query parsing#1138
Open
richlilly2004 wants to merge 1 commit intomicrosoft:mainfrom
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR fixes issues encountered while running
Invoke-ZtAssessmentagainst a live tenant.It corrects DuckDB queries for delegated permission parsing and adds the required Graph scope for the Windows enrollment policy endpoint so the assessment can complete successfully in scenarios where that endpoint otherwise returns
403 Forbidden.Type
Testing
Invoke-ZtAssessmentcompletes and generates the HTML reportGetting Windows enrollment summary -> CompletedChanges
Policy.ReadWrite.MobilityManagementto the Graph scope list used byConnect-ZtAssessmentNotes
This was validated against a live tenant where the previous run reproduced:
403 ForbiddenforGET /beta/policies/mobileDeviceManagementPoliciesAfter the fixes, the assessment completed successfully and generated the report as expected.