[BUG] Setting DefaultAzureCredentialOptions.TenantId twice leads to InvalidOperationException

[dfederm]

Library name and version

Azure.Identity 1.13.1

Describe the bug

I have code that essentially does:

DefaultAzureCredentialOptions defaultAzureCredentialOptions = new()
{
    TenantId = DefaultTenantId,
};

if (!string.IsNullOrEmpty(authSettings.TenantId))
{
    defaultAzureCredentialOptions.TenantId = authSettings.TenantId;
}

Which leads to the following error:

Applications should not set both TenantId and InteractiveBrowserTenantId. TenantId is preferred, and is functionally equivalent. InteractiveBrowserTenantId exists only to provide backwards compatibility.

I obviously can refactor the code to just set TenantId exactly once, but I shouldn't have to.

From looking at the code, setting TenantId also sets _interactiveBrowserTenantId.Value. Setting TenantId again throws due to this logic in the setter:

if (_interactiveBrowserTenantId.Updated && value != _interactiveBrowserTenantId.Value)
{
    throw new InvalidOperationException("Applications should not set both TenantId and InteractiveBrowserTenantId. TenantId is preferred, and is functionally equivalent. InteractiveBrowserTenantId exists only to provide backwards compatibility.");
}

Since _interactiveBrowserTenantId is set from the first setting of TenantId, but I did NOT set InteractiveBrowserTenantId directly, I consider this a bug.

Expected behavior

For it not to throw.

Actual behavior

Exception

Reproduction Steps

See above

Environment

No response

[github-actions]

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