Skip to content

Commit 746f627

Browse files
authored
Merge pull request #108248 from nalogan/patch-3
Added importing config section
2 parents 58049a7 + 0c11bdd commit 746f627

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

articles/azure-app-configuration/howto-best-practices.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -69,6 +69,10 @@ You can provide access to App Configuration for web apps or functions by using a
6969
* Use Azure managed identities to access the App Configuration store. For more information, see [Integrate with Azure managed identities](howto-integrate-azure-managed-service-identity.md).
7070
* Push configuration from App Configuration to App Service. App Configuration provides an export function (in Azure portal and the Azure CLI) that sends data directly into App Service. With this method, you don't need to change the application code at all.
7171

72+
## Importing configuration data into App Configuration
73+
74+
App Configuration offers the option to bulk [import](https://aka.ms/azconfig-importexport1) your configuration settings from your current configuration files using either the Azure Portal or CLI. You can also use the same options to export values from App Configuration, for example between related stores. If you’d like to set up an ongoing sync with your GitHub repo, you can use our [GitHub Action](https://aka.ms/azconfig-gha2) so that you can continue using your existing source control practices while getting the benefits of App Configuration.
75+
7276
## Next steps
7377

7478
* [Keys and values](./concept-key-value.md)

0 commit comments

Comments
 (0)