Penv Cloud
Start free
Docs
Reference

Azure App Configuration

Per-key configuration with one label per environment.

Per-key configuration with one label per environment.

Connection

WhatThis provider
VendorMicrosoft Azure
Keyazure-app-configuration
Availabilityavailable. You can connect it today.
Credential we holdazure-service-principal
Values read backyes
Activationimmediate

Directions

DirectionWhat it does
importWe read names and values out of the store into your environment.
exportWe write names and values from your environment into the store.

Activation

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

Conflict policies

DirectionPolicies you can pick
importskip_existing, new_version, fail
exportcreate_only, overwrite, overwrite_and_prune

How syncs work says what each one does.

Connect

Paste a credential from the vendor. We seal it and never show it again.

FieldLabelKindRequiredWhat it is
tenantIdDirectory (tenant) IDsecret; we mask it here and seal ityes
clientIdApplication (client) IDsecret; we mask it here and seal ityes
clientSecretClient secretsecret; we mask it here and seal ityes

Connection fields

You set these when you connect. Every mapping on the connection shares them.

FieldLabelKindRequiredAdvancedWhat it is
storeNameStoretextyesnoThe store's name alone. Its host is <name>.azconfig.io.

Mapping fields

You answer these once per environment you map.

FieldLabelKindRequiredAdvancedWhat it is
labelLabeltextyesnoA sync owns one label. We leave keys under other labels alone.

Required permissions

We probe for these when we verify the connection.

PermissionDirectionsBlockingWithout it
appconfig:readevery directionyesPreview cannot list what the store holds.
appconfig:writeexportyesExport cannot write anything.