added "AdditionalHeaders" parameter to Invoke-DCMSGraphQuery #45
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.
My auto-formatter formatted the file differently, sorry about that.
You can also see that I modified Invoke-DCMSGraphQuery to include a new parameter "AdditionalHeaders". This will allow folks to add additional headers like "ConsistencyLevel" and setting it to "eventual" so that we can perform search in a resource graph query as shown in the example I added.
Invoke-DCMsGraphQuery -AccessToken $AccessToken -GraphMethod 'GET' -GraphUri 'https://graph.microsoft.com/v1.0/users/?$count=true&search="displayName:-admin"' -AdditionalHeaders @{'ConsistencyLevel' = 'eventual' }
Since those responses have a nextLink instead of .@odata.nextLink I also added handling for that with these additional lines:
While ($QueryRequest.nextLink) {
$QueryRequest = Invoke-RestMethod -Headers $HeaderParams -Uri $QueryRequest.'nextLink' -UseBasicParsing -Method $GraphMethod -ContentType "application/json"
$QueryResult += $QueryRequest.value
}
I've been using it and it has worked great for me.