The `exportAuthRecord` process does not respect the tenant when running in /azure

[bwateratmsft]

When running in /azure, e.g. in a BAMI tenant, the tenant ID is passed to the Azure Cloud Shell extension and used to sign in. However, exportAuthRecord does not pick up that tenant ID at all, and consequently, exports an authentication record that will not work with DefaultAzureCredential.

Additionally, even when passing in tenantId to DefaultAzureCredential's options, and with the @azure.argTenant setting altered to correct the tenant set by exportAuthRecord, I still cannot get DefaultAzureCredential to work. I also tried signing in to Azure CLI with az login --use-device-code -t <tenantId>, and while that was successful, DefaultAzureCredential is still failing.

/cc @g2vinay @alexweininger @meeraharidasa

[g2vinay]

This should now be resolved.

1. DAC worked with az login and by setting AZURE_TOKEN_CREDENTIALS to dev. (was getting blocked by MI auth in cloud shell)
2. @azure.argTenant was fixed by installing the extension back I believe.

[bwateratmsft]

It's been worked around (mostly via using AzureCliCredential) but I wouldn't call it resolved 😄