Charles Lowell

These models are handwritten and have never inherited Model or exposed serialization methods. The prior (track 1) azure-keyvault package's KeyVaultClient returned auto-generated Models, so there could be a migration issue...

Can we reopen this for tracking?

@rayluo is this still relevant? I'm implementing OBO and wonder whether there are any gotchas or limitations in the current MSAL I should consider.

May at the earliest, in the current plan. #16902 has an example you could follow in the meantime if you want to implement it yourself.

We published 1.2.0-beta.2 today with a new credential type, `ClientAssertionCredential`, that does most of what's required for Workload Identity. ~I expect to have full Workload Identity support in v1.2.0 but...

> should the client created this way be made a singleton across your app? Our clients for HTTP services (including AAD) share a single `http.Client` by default. If you aren't...

Looks related to #16722

@Sean-Holcomb Here's how to configure a client for a sovereign cloud with today's API: ```go // using armcompute v0.3.0 and azidentity v0.13.1 import ( "github.com/Azure/azure-sdk-for-go/sdk/azcore/arm" "github.com/Azure/azure-sdk-for-go/sdk/azidentity" "github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/compute/armcompute" ) cred, err...

Depends on the authentication provider for your Stack. azidentity supports Azure AD but not ADFS. We're tracking ADFS support with #14405. I see I never came back to update this...

Thanks for opening this! We have API in place for ARM cross-tenant authentication but, as you've seen, the implementation is incomplete in that credentials always authenticate in the tenant set...