Skip to main content
Version: v2.10.0

AZURE SERVICE PRINCIPAL

Stores an Azure service principal used to authenticate against Azure services.

AZURE SERVICE PRINCIPAL is the second entry in the Secret Type dropdown and it's available at all three scopes: User, Workspace and Tenant. A service principal is the identity Azure expects an application to authenticate as, distinct from the user account somebody signs in with interactively, and it's what we use to reach ADLS Gen2 storage and the other Azure services a workload depends on.

The four required fields identify the directory, the application and the secret that proves the application is what it claims to be.

We validate all four together, because three correct values and one wrong one fail identically at runtime.

Basic Details

Common to every secret type:

FieldRequiredControlPlaceholder / default
Secret NameYestexttitle_example_user_secret_1
Secret TypeYesdropdownselect AZURE SERVICE PRINCIPAL
WorkspaceYesdropdownWorkspace scope only
DescriptionNotextareaEnter Description

Secret Details

FieldRequiredControlPlaceholder
Client IDYestextc8b87a2f-41de-4b66-b0d1-9f7cd28fb3c1
Tenant IDYestextf52d3c1a-9dd8-4a8b-913e-0e27b795ac4a
Client SecretYespassword(none)
Subscription IDYestext7a94c28e-6c32-4ef2-912f-4fcd528918ef
note

A secret does not carry a storage target. Settings ▸ Credentials ▸ Azure Service Principal is a different form with six fields: these four plus Storage Account Name and Container Name.

Validate and Metastore

  • Validate is available for this type, and stays disabled until the four required fields are filled.
  • This type does not expose the Metastore dropdown.

Azure Service Principal secret form