Does WorkloadIdentityCredential work with ESTS-R environment variable "AZURE_REGIONAL_AUTHORITY_NAME" or "MSAL_FORCE_REGION"

[GeoJim1218]

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
I'm trying to adopt ESTS-R for WorkloadIdentityCredential. When I set environment variable "AZURE_REGIONAL_AUTHORITY_NAME" with region value defined in ‎sdk/identity/azure-identity/azure/identity/_enums.py. The authority host is always login.microsoftonline.com.

Describe the solution you'd like
A clear and concise description of what you want to happen.
I want WorkloadIdentityCredential to use regional authority when the environment variable "AZURE_REGIONAL_AUTHORITY_NAME" is set correctly.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
I also tried "MSAL_FORCE_REGION". It doesn't work either.

Additional context
Add any other context or screenshots about the feature request here.
In the changelog, I can see "CertificateCredential and ClientSecretCredential support regional STS" in 2021. I want to know the plan of support for WorkloadIdentityCredential.

[github-actions]

Thank you for your feedback. Tagging and routing to the team member best able to assist.

[xiangyan99]

Thanks for reaching out.

WorkloadIdentityCredential does not honor environment variable "AZURE_REGIONAL_AUTHORITY_NAME".

But you can specify the authority host in its constructor.

credential = WorkloadIdentityCredential(authority="YOUR_AUTHORITY_HOST")

[github-actions]

Hi @GeoJim1218. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text "/unresolve" to remove the "issue-addressed" label and continue the conversation.

[GeoJim1218]

@xiangyan99 thanks for the information. I can try the workaround. I wonder if there is any plan to make WorkloadIdentityCredential leverage "AZURE_REGIONAL_AUTHORITY_NAME". We're also using the environment variable in Azure SDK of .NET and Go. I think a unified solution be preferred.

[GeoJim1218]

I realize there is one scenario where we don't construct WorkloadIdentityCredential directly. For example, we're using https://github.com/Azure/azure-kusto-python/blob/d72e890c8f128307f45aa883d0231f2a75cc61c3/azure-kusto-data/azure/kusto/data/kcsb.py#L375 in azure-kusto-data. We cannot pass the regional authority host.