Skip to content

Conversation

@rmvangun
Copy link
Contributor

Adds support for configuring context specific data for an Azure profile / context, such that you can configure a section in windsor.yaml as follows:

contexts:
  production:
    azure:
      enabled: true
      subscription_id: your-subscription-id
      tenant_id: your-tenant-id

This results in the followig env vars on the context:

export ARM_SUBSCRIPTION_ID="your-subscription-id"
export ARM_TENANT_ID="your-tenant-id"
export AZURE_CONFIG_DIR="/path/to/contexts/local/.azure"
export AZURE_CORE_LOGIN_EXPERIENCE_V2="false"

To log in to Azure, if you are on a context, all that is required is az login. You will be prompted to log in via the SSO flow locally. In automated contexts, it's expected to use more automated methods including OIDC, etc.

@rmvangun rmvangun added enhancement New feature or request and removed enhancement New feature or request labels May 11, 2025
Copy link

@hernan82arg hernan82arg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, although, I think there is no need for tenant_id.
I've no much experience with Azure, but I've been only setting ARM_SUBSCRIPTION_ID when working on Azure in core repo. Everything else seems to be handled by az login.

@rmvangun rmvangun merged commit 0938057 into main May 11, 2025
12 checks passed
@rmvangun rmvangun deleted the azure-auth-support branch May 11, 2025 15:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants