Fixes subsequent failures after first successful Invoke-MgGraphRequest
run when using national cloud environments
#2971
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.
Fixes #2950
The fix provided here only works once when an absolute uri is passed to
Invoke-MgGraphRequest
cmdlet after connecting to a national cloud environment. Subsequent requests after the first successful one fails.Changes proposed in this pull request
Find-MgGraphPermission
in order to get the correct environment and extract the correct graph endpoint instead of using the default graph one (https://graph.microsoft.com) assigned to global environment.Test scenarios.
Find-MgGraphPermission
does not default the session to the global graph endpoint after connecting to a national cloud environment.NB: See attached image below for the above tests