Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AZURE_REGIONAL_AUTHORITY_NAME won't work after updating to 1.6 (works in 1.5) #29112

Closed
sadjadbp opened this issue Jun 4, 2022 · 2 comments · Fixed by #29612
Closed

AZURE_REGIONAL_AUTHORITY_NAME won't work after updating to 1.6 (works in 1.5) #29112

sadjadbp opened this issue Jun 4, 2022 · 2 comments · Fixed by #29612
Assignees
Labels
Azure.Identity Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that

Comments

@sadjadbp
Copy link

sadjadbp commented Jun 4, 2022

I'm following the example here

var previousRegionValue = Environment.GetEnvironmentVariable("AZURE_REGIONAL_AUTHORITY_NAME");
var regionValue = Config.AzureRegion ?? RegionalAuthority.AutoDiscoverRegion;
Environment.SetEnvironmentVariable("AZURE_REGIONAL_AUTHORITY_NAME", regionValue);

var credential = new ClientCertificateCredential(tenantId, clientId, certificate,
    new ClientCertificateCredentialOptions
    {
        AuthorityHost = PublicCloudAuthority,
        SendCertificateChain = true,
    });
Environment.SetEnvironmentVariable("AZURE_REGIONAL_AUTHORITY_NAME", previousRegionValue);

With Azure.Identity 1.5+MSAL 4.44.0 it works fine and if I check credentials.Client.RegionalAuthority it is set to the AzureRegion like 'westus', but if I use Azure.Identity 1.6+MSAL 4.44.0 that credentials.Client.RegionalAuthority would be null. I have tried all below combination and looks like the only culprit is Azure.Identity 1.6

1.5+4.42.1 worked
1.5+4.43.0 worked
1.5+4.43.1 worked
1.5+4.43.2 worked
1.5+4.44.0 worked

1.6+4.42.1 didn't work
1.6+4.43.0 didn't work
1.6+4.43.1 didn't work
1.6+4.43.2 didn't work
1.6+4.44.0 didn't work

@ghost ghost added needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Jun 4, 2022
@azure-sdk azure-sdk added Azure.Identity Client This issue points to a problem in the data-plane of the library. needs-team-triage Workflow: This issue needs the team to triage. labels Jun 4, 2022
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Jun 4, 2022
@jsquire jsquire added needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team and removed needs-team-triage Workflow: This issue needs the team to triage. labels Jun 4, 2022
@jsquire
Copy link
Member

jsquire commented Jun 4, 2022

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

@stowen-msft
Copy link
Contributor

We seem to be seeing the same behavior as well. We are uniformly on 1.6 as well

@github-actions github-actions bot locked and limited conversation to collaborators Mar 25, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Azure.Identity Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants
@jsquire @sadjadbp @schaabs @azure-sdk @stowen-msft and others