Merge pull request #211141 from maud-lv/patch-14

Add tip following user suggestion

Author: prmerger-automator[bot]

articles/azure-app-configuration/enable-dynamic-configuration-azure-functions-csharp.md

@@ -96,6 +96,14 @@ Azure Functions support running [in-process](../azure-functions/functions-dotnet
 
     > [!TIP]
     > When you are updating multiple key-values in App Configuration, you normally don't want your application to reload configuration before all changes are made. You can register a *sentinel key* and update it only when all other configuration changes are completed. This helps to ensure the consistency of configuration in your application.
+    >
+    > You may also do following to minimize the risk of inconsistencies:
+    >
+    > * Design your application to be tolerable for transient configuration inconsistency
+    > * Warm-up your application before bringing it online (serving requests)
+    > * Carry default configuration in your application and use it when configuration validation fails
+    > * Choose a configuration update strategy that minimizes the impact to your application, for example, a low traffic timing.
+
 
 ### [In-process](#tab/in-process)
 
@@ -237,4 +245,4 @@ Azure Functions support running [in-process](../azure-functions/functions-dotnet
 In this tutorial, you enabled your Azure Functions app to dynamically refresh configuration settings from App Configuration. To learn how to use an Azure managed identity to streamline the access to App Configuration, continue to the next tutorial.
 
 > [!div class="nextstepaction"]
-> [Access App Configuration using managed identity](./howto-integrate-azure-managed-service-identity.md)
+> [Access App Configuration using managed identity](./howto-integrate-azure-managed-service-identity.md)