Increase request timeout to match default retry attempts. #1018
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.
This PR proposes:
-ClientTimeout
parameter toConnect-MgGraph
. This parameter allows customers to configure an HTTP client timeout when throttled requests respond with a retry-after header > the client's default of 300 seconds.Invoke-MgGraphRequest
that made it not throw exceptions on error in certain conditions. Closes Invoke-MgGraphRequest Should Always Throw on Error #1014.Tests
Using default timeout of 300 seconds.

Using a timeout of 10 seconds.

Related to timeouts being experienced by customers when running https://docs.microsoft.com/en-us/troubleshoot/azure/active-directory/enable-support-tls-environment?tabs=powershell#overview-of-new-telemetry-in-the-sign-in-logs.