ources that the connector is configured to access.Note that the discovered credentials inherit the full set of permissions of the local Azure CLI configuration, environment variables or remote Azure managed identity. Depending on the extent of those permissions, this authentication method might not be recommended for production use, as it can lead to accidental privilege escalation. Instead, it is recommended to use the Azure service principal authentication method to limit the validity and/or permissions of the credentials being issued to connector clients.

The following assumes the local Azure CLI has already been configured with user account credentials by running the az login command:

zenml service-connector register azure-implicit --type azure --auth-method implicit --auto-configure

Example Command Output

⠙ Registering service connector 'azure-implicit'...

Successfully registered service connector `azure-implicit` with access to the following resources:

┏━━━━━━━━━━━━━━━━━━━━━━━┯━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓

┃     RESOURCE TYPE     │ RESOURCE NAMES                                ┃

┠───────────────────────┼───────────────────────────────────────────────┨

┃   🇦 azure-generic    │ ZenML Subscription                            ┃

┠───────────────────────┼───────────────────────────────────────────────┨

┃   📦 blob-container   │ az://demo-zenmlartifactstore                  ┃

┠───────────────────────┼───────────────────────────────────────────────┨

┃ 🌀 kubernetes-cluster │ demo-zenml-demos/demo-zenml-terraform-cluster ┃

┠───────────────────────┼───────────────────────────────────────────────┨

┃  🐳 docker-registry   │ demozenmlcontainerregistry.azurecr.io         ┃

┗━━━━━━━━━━━━━━━━━━━━━━━┷━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛

No credentials are stored with the Service Connector:

zenml service-connector describe azure-implicit

Example Command Output