Update note title

maud-lv · maud-lv · commit 2643047bd3d6 · 2024-08-26T15:12:25.000+02:00
diff --git a/articles/service-connector/concept-permission.md b/articles/service-connector/concept-permission.md
@@ -230,7 +230,7 @@ Service Connector creates connections between Azure services using an [on-behalf
 
 ### Azure Cosmos DB
 
-> [!IMPORTANT]
+> [!WARNING]
 > Microsoft recommends that you use the most secure authentication flow available. The authentication flow described in this procedure requires a very high degree of trust in the application, and carries risks that are not present in other flows. You should only use this flow when other more secure flows, such as managed identities, aren't viable.
 
 > [!div class="mx-tableFixed"]
diff --git a/articles/service-connector/how-to-integrate-app-configuration.md b/articles/service-connector/how-to-integrate-app-configuration.md
@@ -63,7 +63,7 @@ Refer to the steps and code below to connect to Azure App Configuration using a
 
 ### Connection string
 
-> [!IMPORTANT]
+> [!WARNING]
 > Microsoft recommends that you use the most secure authentication flow available. The authentication flow described in this procedure requires a very high degree of trust in the application, and carries risks that are not present in other flows. You should only use this flow when other more secure flows, such as managed identities, aren't viable.
 
 > [!div class="mx-tdBreakAll"]
diff --git a/articles/service-connector/how-to-integrate-confluent-kafka.md b/articles/service-connector/how-to-integrate-confluent-kafka.md
@@ -42,7 +42,7 @@ Use the connection details below to connect compute services to Kafka. For each
 
 ### Secret / Connection String
 
-> [!IMPORTANT]
+> [!WARNING]
 > Microsoft recommends that you use the most secure authentication flow available. The authentication flow described in this procedure requires a very high degree of trust in the application, and carries risks that are not present in other flows. You should only use this flow when other more secure flows, such as managed identities, aren't viable.
 
 #### SpringBoot client type
diff --git a/articles/service-connector/how-to-integrate-cosmos-cassandra.md b/articles/service-connector/how-to-integrate-cosmos-cassandra.md
@@ -78,7 +78,7 @@ Refer to the steps and code below to connect to Azure Cosmos DB for Cassandra us
 
 ### Connection String
 
-> [!IMPORTANT]
+> [!WARNING]
 > Microsoft recommends that you use the most secure authentication flow available. The authentication flow described in this procedure requires a very high degree of trust in the application, and carries risks that are not present in other flows. You should only use this flow when other more secure flows, such as managed identities, aren't viable.
 
 #### SpringBoot client type
diff --git a/articles/service-connector/how-to-integrate-cosmos-db.md b/articles/service-connector/how-to-integrate-cosmos-db.md
@@ -70,7 +70,7 @@ Refer to the steps and code below to connect to Azure Cosmos DB for MongoDB usin
 
 ### Connection string
 
-> [!IMPORTANT]
+> [!WARNING]
 > Microsoft recommends that you use the most secure authentication flow available. The authentication flow described in this procedure requires a very high degree of trust in the application, and carries risks that are not present in other flows. You should only use this flow when other more secure flows, such as managed identities, aren't viable.
 
 #### SpringBoot client type
diff --git a/articles/service-connector/how-to-integrate-cosmos-gremlin.md b/articles/service-connector/how-to-integrate-cosmos-gremlin.md
@@ -76,7 +76,7 @@ Refer to the steps and code below to connect to Azure Cosmos DB for Gremlin usin
 
 ### Connection string
 
-> [!IMPORTANT]
+> [!WARNING]
 > Microsoft recommends that you use the most secure authentication flow available. The authentication flow described in this procedure requires a very high degree of trust in the application, and carries risks that are not present in other flows. You should only use this flow when other more secure flows, such as managed identities, aren't viable.
 
 | Default environment variable name | Description                                   | Example value                                  |
diff --git a/articles/service-connector/how-to-integrate-cosmos-sql.md b/articles/service-connector/how-to-integrate-cosmos-sql.md
@@ -94,7 +94,7 @@ Refer to the steps and code below to connect to Azure Cosmos DB for NoSQL using
 
 ### Connection string
 
-> [!IMPORTANT]
+> [!WARNING]
 > Microsoft recommends that you use the most secure authentication flow available. The authentication flow described in this procedure requires a very high degree of trust in the application, and carries risks that are not present in other flows. You should only use this flow when other more secure flows, such as managed identities, aren't viable.
 
 #### SpringBoot client type
diff --git a/articles/service-connector/how-to-integrate-cosmos-table.md b/articles/service-connector/how-to-integrate-cosmos-table.md
@@ -73,7 +73,7 @@ Refer to the steps and code below to connect to Azure Cosmos DB for Table using
 |-----------------------------------|-------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | AZURE_COSMOS_CONNECTIONSTRING     | Azure Cosmos DB for Table connection string | `DefaultEndpointsProtocol=https;AccountName=<account-name>;AccountKey=<account-key>;TableEndpoint=https://<table-name>.table.cosmos.azure.com:443/; ` |
 
-> [!IMPORTANT]
+> [!WARNING]
 > Microsoft recommends that you use the most secure authentication flow available. The authentication flow described in this procedure requires a very high degree of trust in the application, and carries risks that are not present in other flows. You should only use this flow when other more secure flows, such as managed identities, aren't viable.
 
 #### Sample code
diff --git a/articles/service-connector/how-to-integrate-event-hubs.md b/articles/service-connector/how-to-integrate-event-hubs.md
@@ -107,7 +107,7 @@ Refer to the steps and code below to connect to Azure Event Hubs using a user-as
 
 ### Connection string
 
-> [!IMPORTANT]
+> [!WARNING]
 > Microsoft recommends that you use the most secure authentication flow available. The authentication flow described in this procedure requires a very high degree of trust in the application, and carries risks that are not present in other flows. You should only use this flow when other more secure flows, such as managed identities, aren't viable.
 
 #### SpringBoot client type
diff --git a/articles/service-connector/how-to-integrate-mysql.md b/articles/service-connector/how-to-integrate-mysql.md
@@ -241,7 +241,7 @@ Refer to the steps and code below to connect to Azure Database for MySQL using a
 
 ### Connection String
 
-> [!IMPORTANT]
+> [!WARNING]
 > Microsoft recommends that you use the most secure authentication flow available. The authentication flow described in this procedure requires a very high degree of trust in the application, and carries risks that are not present in other flows. You should only use this flow when other more secure flows, such as managed identities, aren't viable.
 
 #### [.NET](#tab/dotnet)
diff --git a/articles/service-connector/how-to-integrate-postgres.md b/articles/service-connector/how-to-integrate-postgres.md
@@ -223,7 +223,7 @@ Refer to the steps and code below to connect to Azure Database for PostgreSQL us
 
 ### Connection String
 
-> [!IMPORTANT]
+> [!WARNING]
 > Microsoft recommends that you use the most secure authentication flow available. The authentication flow described in this procedure requires a very high degree of trust in the application, and carries risks that are not present in other flows. You should only use this flow when other more secure flows, such as managed identities, aren't viable.
 
 #### [.NET](#tab/dotnet)
diff --git a/articles/service-connector/how-to-integrate-redis-cache.md b/articles/service-connector/how-to-integrate-redis-cache.md
@@ -43,7 +43,7 @@ Use the environment variable names and application properties listed below to co
 
 ### Connection String
 
-> [!IMPORTANT]
+> [!WARNING]
 > Microsoft recommends that you use the most secure authentication flow available. The authentication flow described in this procedure requires a very high degree of trust in the application, and carries risks that are not present in other flows. You should only use this flow when other more secure flows, such as managed identities, aren't viable.
 
 #### [.NET](#tab/dotnet) 
diff --git a/articles/service-connector/how-to-integrate-service-bus.md b/articles/service-connector/how-to-integrate-service-bus.md
@@ -81,7 +81,7 @@ Refer to the steps and code below to connect to Service Bus using a user-assigne
 
 ### Connection string
 
-> [!IMPORTANT]
+> [!WARNING]
 > Microsoft recommends that you use the most secure authentication flow available. The authentication flow described in this procedure requires a very high degree of trust in the application, and carries risks that are not present in other flows. You should only use this flow when other more secure flows, such as managed identities, aren't viable.
 
 #### SpringBoot client type
diff --git a/articles/service-connector/how-to-integrate-signalr.md b/articles/service-connector/how-to-integrate-signalr.md
@@ -62,7 +62,7 @@ Refer to the steps and code below to connect to Azure SignalR Service using a us
 
 ### Connection string
 
-> [!IMPORTANT]
+> [!WARNING]
 > Microsoft recommends that you use the most secure authentication flow available. The authentication flow described in this procedure requires a very high degree of trust in the application, and carries risks that are not present in other flows. You should only use this flow when other more secure flows, such as managed identities, aren't viable.
 
   | Default environment variable name | Description | Example value |
diff --git a/articles/service-connector/how-to-integrate-sql-database.md b/articles/service-connector/how-to-integrate-sql-database.md
@@ -174,7 +174,7 @@ Refer to the steps and code below to connect to Azure SQL Database using a user-
 
 ### Connection String
 
-> [!IMPORTANT]
+> [!WARNING]
 > Microsoft recommends that you use the most secure authentication flow available. The authentication flow described in this procedure requires a very high degree of trust in the application, and carries risks that are not present in other flows. You should only use this flow when other more secure flows, such as managed identities, aren't viable.
 
 #### [.NET](#tab/sql-secret-dotnet)
diff --git a/articles/service-connector/how-to-integrate-storage-blob.md b/articles/service-connector/how-to-integrate-storage-blob.md
@@ -70,7 +70,7 @@ Refer to the steps and code below to connect to Azure Blob Storage using a user-
 
 ### Connection string
 
-> [!IMPORTANT]
+> [!WARNING]
 > Microsoft recommends that you use the most secure authentication flow available. The authentication flow described in this procedure requires a very high degree of trust in the application, and carries risks that are not present in other flows. You should only use this flow when other more secure flows, such as managed identities, aren't viable.
 
 For default environment variables and sample code of other authentication type, please choose from beginning of the documentation.
diff --git a/articles/service-connector/how-to-integrate-storage-file.md b/articles/service-connector/how-to-integrate-storage-file.md
@@ -44,7 +44,7 @@ Use the connection details below to connect compute services to Azure File Stora
 
 ### Connection string
 
-> [!IMPORTANT]
+> [!WARNING]
 > Microsoft recommends that you use the most secure authentication flow available. The authentication flow described in this procedure requires a very high degree of trust in the application, and carries risks that are not present in other flows. You should only use this flow when other more secure flows, such as managed identities, aren't viable.
 
 #### SpringBoot client type
diff --git a/articles/service-connector/how-to-integrate-storage-queue.md b/articles/service-connector/how-to-integrate-storage-queue.md
@@ -64,7 +64,7 @@ Refer to the steps and code below to connect to Azure Queue Storage using a user
 
 ### Connection string
 
-> [!IMPORTANT]
+> [!WARNING]
 > Microsoft recommends that you use the most secure authentication flow available. The authentication flow described in this procedure requires a very high degree of trust in the application, and carries risks that are not present in other flows. You should only use this flow when other more secure flows, such as managed identities, aren't viable.
 
 #### SpringBoot client type
diff --git a/articles/service-connector/how-to-integrate-storage-table.md b/articles/service-connector/how-to-integrate-storage-table.md
@@ -61,7 +61,7 @@ Refer to the steps and code below to connect to Azure Table Storage using a user
 
 ### Connection string
 
-> [!IMPORTANT]
+> [!WARNING]
 > Microsoft recommends that you use the most secure authentication flow available. The authentication flow described in this procedure requires a very high degree of trust in the application, and carries risks that are not present in other flows. You should only use this flow when other more secure flows, such as managed identities, aren't viable.
 
 | Default environment variable name   | Description                     | Example value                                                                                                        |
diff --git a/articles/service-connector/how-to-integrate-web-pubsub.md b/articles/service-connector/how-to-integrate-web-pubsub.md
@@ -63,7 +63,7 @@ Refer to the steps and code below to connect to Azure Web PubSub using a user-as
 
 ### Connection string
 
-> [!IMPORTANT]
+> [!WARNING]
 > Microsoft recommends that you use the most secure authentication flow available. The authentication flow described in this procedure requires a very high degree of trust in the application, and carries risks that are not present in other flows. You should only use this flow when other more secure flows, such as managed identities, aren't viable.
 
 > [!div class="mx-tdBreakAll"]
diff --git a/articles/service-connector/tutorial-portal-key-vault.md b/articles/service-connector/tutorial-portal-key-vault.md
@@ -71,8 +71,8 @@ Now you can create a service connection to another target service and directly s
 
     ### [Connection string](#tab/connectionstring)
 
-> [!IMPORTANT]
-> Microsoft recommends that you use the most secure authentication flow available. The authentication flow described in this procedure requires a very high degree of trust in the application, and carries risks that are not present in other flows. You should only use this flow when other more secure flows, such as managed identities, aren't viable.
+    > [!IMPORTANT]
+    > Microsoft recommends that you use the most secure authentication flow available. The authentication flow described in this procedure requires a very high degree of trust in the application, and carries risks that are not present in other flows. You should only use this flow when other more secure flows, such as managed identities, aren't viable.
 
     Select **Next: Authentication** to select the authentication type and select **Connection string** to use an access key to connect your storage account.
 
diff --git a/articles/service-connector/tutorial-python-aks-sql-database-connection-string.md b/articles/service-connector/tutorial-python-aks-sql-database-connection-string.md
@@ -61,6 +61,9 @@ az provider register --namespace Microsoft.KubernetesConfiguration
 
 Create a service connection between your AKS cluster and your SQL database in the Azure portal or the Azure CLI.
 
+> [!WARNING]
+> Microsoft recommends that you use the most secure authentication flow available. The authentication flow described in this procedure requires a very high degree of trust in the application, and carries risks that are not present in other flows. You should only use this flow when other more secure flows, such as managed identities, aren't viable.
+
 ### [Azure portal](#tab/azure-portal)
 
 1. In the [Azure portal](https://portal.azure.com/), navigate to your AKS cluster resource.
diff --git a/articles/service-connector/tutorial-python-functions-storage-queue-as-trigger.md b/articles/service-connector/tutorial-python-functions-storage-queue-as-trigger.md
@@ -37,7 +37,7 @@ An overview of the function project components in this tutorial:
 
 ## Create a Python function project
 
-> [!IMPORTANT]
+> [!WARNING]
 > Microsoft recommends that you use the most secure authentication flow available. The authentication flow described in this procedure requires a very high degree of trust in the application, and carries risks that are not present in other flows. You should only use this flow when other more secure flows, such as managed identities, aren't viable.
 
 Follow the [tutorial to create a local Azure Functions project](../azure-functions/create-first-function-vs-code-python.md?pivots=python-mode-configuration#create-an-azure-functions-project), and provide the following information at the prompts:
diff --git a/articles/service-connector/tutorial-python-functions-storage-table-as-output.md b/articles/service-connector/tutorial-python-functions-storage-table-as-output.md
@@ -38,7 +38,7 @@ An overview of the function project components in this tutorial:
 
 ## Create a Python function project
 
-> [!IMPORTANT]
+> [!WARNING]
 > Microsoft recommends that you use the most secure authentication flow available. The authentication flow described in this procedure requires a very high degree of trust in the application, and carries risks that are not present in other flows. You should only use this flow when other more secure flows, such as managed identities, aren't viable.
 
 Follow the [tutorial to create a local Azure Functions project](../azure-functions/create-first-function-vs-code-python.md?pivots=python-mode-configuration#create-an-azure-functions-project), and provide the following information at the prompts:
