Azure App Configuration

Per-key configuration with one label per environment.

The connection

What	This provider
Vendor	Microsoft Azure
Key	`azure-app-configuration`
Availability	`available`. You can connect it today.
Credential penv holds	`azure-service-principal`
Values read back	yes
Activation	`immediate`

Direction	What it does
`import`	Reads names and values out of the store into penv.
`export`	Writes names and values from penv into the store.

immediate. The running app sees a new value at once.

Direction	Policies you can pick
`import`	`skip_existing`, `new_version`, `fail`
`export`	`create_only`, `overwrite`, `overwrite_and_prune`

How syncs work says what each one does.

You paste a credential you already hold. penv seals it and never shows it again.

Field	Label	Kind	Required
`tenantId`	Directory (tenant) ID	secret, masked here and sealed	yes
`clientId`	Application (client) ID	secret, masked here and sealed	yes
`clientSecret`	Client secret	secret, masked here and sealed	yes

Fixed when you connect, and shared by every mapping on it.

Field	Label	Kind	Required	Advanced	What it is
`storeName`	Store	text	yes	no	The store's name alone. Its host is <name>.azconfig.io.

Answered once per environment you map.

Field	Label	Kind	Required	Advanced	What it is
`label`	Label	text	yes	no	A sync owns one label. Keys under other labels are left alone.

penv probes for these when it verifies the connection.

Permission	Directions	Blocking	Without it
`appconfig:read`	every direction	yes	Preview cannot list what the store holds.
`appconfig:write`	`export`	yes	Export cannot write anything.