Support for AAD Audience in connection string (for sovereign cloud) #4121
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.
Fix # .
Note: Don't merge until this related change from the autoconfigure module is released.
This PR incorporates connection string parsing changes from the autoconfigure module to use the AAD audience that is either provided via the connection string (or a default audience if that isn't provided). This is applicable for sovereign cloud scenarios where customers may be using AAD auth - the LazyHttpClient would use the provided audience when creating a new http pipeline, and all calls to quickpulse/breeze/profiler would be made with that audience.
Need to test in sovereign cloud environment.
For significant contributions please make sure you have completed the following items: