[FEATURE REQ] Add constructor to allow using custom audience, appId for authenticating with Load Balancing through Azure API Management about azure-sdk-for-net HOT 2 OPEN

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @jpalvarezl @trrwilson.

from azure-sdk-for-net.

Thank you, both for filing here and for the ongoing off-thread discussion to clarify the credential mechanisms being used and the requirements. As you've noted, the transference of TokenCredential configuration into the new client is currently limited and we're actively exploring how we should best apply the Azure.Core authentication constructs to the new client derived from System.ClientModel.

In the interim, it's possible to work around this by manually updating the authentication header values via a custom PipelinePolicy, which is semantically very parallel to the Azure Core equivalent. We'll add more formal documentation for this soon, but as a quick reference, this gist demonstrates a very rudimentary header application to outgoing requests:
https://gist.github.com/trrwilson/6c33e9d82bf46c592070aa2961f6eb68

from azure-sdk-for-net.