Skip to content

Latest commit

 

History

History
131 lines (85 loc) · 4.95 KB

quickstart-bicep.md

File metadata and controls

131 lines (85 loc) · 4.95 KB
Raw
title titleSuffix description author ms.author ms.date ms.service ms.topic ms.custom
Create an Azure App Configuration store using Bicep
Azure App Configuration
Learn how to create an Azure App Configuration store using Bicep.
maud-lv
malev
05/30/2024
azure-app-configuration
quickstart
subject-armqs, mode-arm, devx-track-bicep

Quickstart: Create an Azure App Configuration store using Bicep

This quickstart describes how you can use Bicep to:

  • Deploy an App Configuration store.
  • Create key-values in an App Configuration store.
  • Read key-values in an App Configuration store.

[!INCLUDE About Bicep]

Prerequisites

If you don't have an Azure subscription, create a free account before you begin.

Authorization

Managing an Azure App Configuration resource with Bicep file requires an Azure Resource Manager role, such as contributor or owner. Accessing Azure App Configuration data (key-values, snapshots) requires an Azure Resource Manager role and an additional Azure App Configuration data plane role when the configuration store's ARM authentication mode is set to pass-through ARM authentication mode.

Important

Configuring ARM authentication mode requires App Configuration control plane API version 2023-08-01-preview or later.

Review the Bicep file

The Bicep file used in this quickstart is from Azure Quickstart Templates.

Note

Bicep files use the same underlying engine as ARM templates. All of the tips, notes, and important information found in the ARM template quickstart apply here. It's recommended to reference this information when working with Bicep files.

:::code language="bicep" source="~/quickstart-templates/quickstarts/microsoft.appconfiguration/app-configuration-store-kv/main.bicep":::

Two Azure resources are defined in the Bicep file:

With this Bicep file, we create one key with two different values, one of which has a unique label.

Deploy the Bicep file

  1. Save the Bicep file as main.bicep to your local computer.

  2. Deploy the Bicep file using either Azure CLI or Azure PowerShell.

    CLI

    az group create --name exampleRG --location eastus
az deployment group create --resource-group exampleRG --template-file main.bicep --parameters configStoreName=<store-name>

    PowerShell

    New-AzResourceGroup -Name exampleRG -Location eastus
New-AzResourceGroupDeployment -ResourceGroupName exampleRG -TemplateFile ./main.bicep -configStoreName "<store-name>"

    [!NOTE] Replace <store-name> with the name of the App Configuration store.

    When the deployment finishes, you should see a message indicating the deployment succeeded.

Review deployed resources

Use Azure CLI or Azure PowerShell to list the deployed resources in the resource group.

CLI

az resource list --resource-group exampleRG

PowerShell

Get-AzResource -ResourceGroupName exampleRG

You can also use the Azure portal to list the resources:

  1. Sign in to the Azure portal.
  2. In the search box, enter App Configuration, then select App Configuration from the list.
  3. Select the newly created App Configuration resource.
  4. Under Operations, select Configuration explorer.
  5. Verify that two key-values exist.

Clean up resources

When no longer needed, use Azure CLI or Azure PowerShell to delete the resource group and its resources.

CLI

az group delete --name exampleRG

PowerShell

Remove-AzResourceGroup -Name exampleRG

You can also use the Azure portal to delete the resource group:

  1. Navigate to your resource group.
  2. Select Delete resource group.
  3. A tab will appear. Enter the resource group name and select Delete.

Next steps

To learn about adding feature flag and Key Vault reference to an App Configuration store, check out the ARM template examples.