Merge pull request #281276 from MicrosoftDocs/main

7/18/2024 PM Publish

Author: Taojunshen

articles/ai-services/language-service/conversational-language-understanding/concepts/best-practices.md

@@ -75,7 +75,13 @@ If you require the learned component, make sure that *ticket quantity* is only r
 
 ## Addressing model inconsistencies
 
-If your model is overly sensitive to small grammatical changes, like casing or diacritics, you can systematically manipulate your dataset directly in the Language Studio. To use these features, click on the Settings tab on the left toolbar and locate the **Advanced project settings** section. First, you can ***Enable data transformation for casing***, which normalizes the casing of utterances when training, testing, and implementing your model. If you've migrated from LUIS, you might recognize that LUIS did this normalization by default. To access this feature via the API, set the `"normalizeCasing"` parameter to `true`. See an example below:
+If your model is overly sensitive to small grammatical changes, like casing or diacritics, you can systematically manipulate your dataset directly in the Language Studio. To use these features, click on the Settings tab on the left toolbar and locate the **Advanced project settings** section. 
+
+:::image type="content" source="../media/advanced-project-settings.png" alt-text="A screenshot showing an example of the advanced project settings." lightbox="../media/advanced-project-settings.png":::
+
+First, you can ***Enable data transformation for casing***, which normalizes the casing of utterances when training, testing, and implementing your model. If you've migrated from LUIS, you might recognize that LUIS did this normalization by default. To access this feature via the API, set the `"normalizeCasing"` parameter to `true`. See an example below:
+
+
 
 ```json
 {

articles/ai-services/language-service/conversational-language-understanding/media/advanced-project-settings.png

@@ -4,7 +4,8 @@ titleSuffix: Azure Linux AKS Container Host partner solutions
 description: Discover partner-tested solutions that enable you to build, test, deploy, manage, and monitor your AKS environment using Azure Linux Container Host.
 ms.author: schaffererin
 author: schaffererin
-ms.topic: article
+ms.service: azure-kubernetes-service
+ms.topic: conceptual
 ms.custom: linux-related-content
 ms.date: 06/13/2024
 ---

articles/aks/azure-linux-aks-partner-solutions.md

@@ -116,7 +116,7 @@ The Dapr extension supports stable versions of Dapr APIs (building blocks).
 | [**Secrets**][dapr-secrets]                           | Stable | Access secrets from your application code or reference secure values in your Dapr components.                                                                   |
 | [**Configuration**][dapr-config]                           | Stable | Retrieve and subscribe to application configuration items for supported configuration. stores.                                                                   |
 
-[!INCLUDE [component-support](../../includes/dapr-in-azure/dapr-support-policy.md)]
+[!INCLUDE [component-support](~/reusable-content/ce-skilling/azure/includes/dapr-in-azure/dapr-support-policy.md)]
 
 ### Clouds/regions
 

articles/aks/dapr-overview.md

@@ -190,7 +190,7 @@ For more information, see the [**Recommended passive-cold failover solution over
 
 AKS sets default limits and quotas for resources and features, including usage restrictions for certain VM SKUs.
 
-[!INCLUDE [container-service-limits](../../includes/container-service-limits.md)]
+[!INCLUDE [container-service-limits](~/reusable-content/ce-skilling/azure/includes/container-service-limits.md)]
 
 For more information, see [AKS service quotas and limits](./quotas-skus-regions.md#service-quotas-and-limits).
 

articles/aks/ha-dr-overview.md

@@ -259,7 +259,7 @@ The default expiration time for the service principal credentials is one year. I
 
 **General Azure CLI troubleshooting**
 
-[!INCLUDE [azure-cli-troubleshooting.md](../../includes/azure-cli-troubleshooting.md)]
+[!INCLUDE [azure-cli-troubleshooting.md](~/reusable-content/ce-skilling/azure/includes/azure-cli-troubleshooting.md)]
 
 ### [Azure PowerShell](#tab/azure-powershell)
 

articles/aks/kubernetes-service-principal.md

@@ -17,7 +17,7 @@ This article details the default resource limits for Azure Kubernetes Service (A
 
 ## Service quotas and limits
 
-[!INCLUDE [container-service-limits](../../includes/container-service-limits.md)]
+[!INCLUDE [container-service-limits](~/reusable-content/ce-skilling/azure/includes/container-service-limits.md)]
 
 ## Provisioned infrastructure
 

articles/aks/quotas-skus-regions.md

@@ -88,6 +88,8 @@ Visual Studio Code will open a diff view between the two API specifications. Any
 
 Use the power of GitHub Copilot with the Azure API Center extension for Visual Studio Code to create an OpenAPI specification file from your API code. Right click on the API code, select **Copilot** from the options, and select **Generate API documentation**. This will create an OpenAPI specification file.
 
+:::image type="content" source="media/use-vscode-extension/generate-api-documentation.gif" alt-text="Animation showing how to use GitHub Copilot to generate an OpenAPI spec from code." lightbox="media/use-vscode-extension/generate-api-documentation.gif":::
+
 After generating the OpenAPI specification file and checking for accuracy, you can register the API with your API center using the **Azure API Center: Register API** command.
 
 ## Discover APIs

articles/api-center/media/use-vscode-extension/generate-api-documentation.gif

@@ -3,7 +3,7 @@ title: App Service Environment networking
 description: App Service Environment networking details
 author: madsd
 ms.topic: overview
-ms.date: 04/23/2024
+ms.date: 07/18/2024
 ms.author: madsd
 ---
 
@@ -74,6 +74,10 @@ You can bring your own inbound address to your App Service Environment. If you c
 
 For your app to receive traffic, ensure that inbound network security group (NSG) rules allow the App Service Environment subnet to receive traffic from the required ports. In addition to any ports, you'd like to receive traffic on, you should ensure that Azure Load Balancer is able to connect to the subnet on port 80. This port is used for health checks of the internal virtual machine. You can still control port 80 traffic from the virtual network to your subnet.
 
+> [!NOTE]
+> Changes to NSG rules can take up to 14 days to take effect due to HTTP connection persistence. If you make a change that blocks platform/management traffic, it could take up to 14 days for the impact to be seen.
+>
+
 It's a good idea to configure the following inbound NSG rule:
 
 |Source / Destination Port(s)|Direction|Source|Destination|Purpose|
@@ -87,6 +91,7 @@ The minimal requirement for App Service Environment to be operational is:
 |* / 80|Inbound|AzureLoadBalancer|App Service Environment subnet range|Allow internal health ping traffic|
 
 If you use the minimum required rule, you might need one or more rules for your application traffic. If you're using any of the deployment or debugging options, you must also allow this traffic to the App Service Environment subnet. The source of these rules can be the virtual network, or one or more specific client IPs or IP ranges. The destination is always the App Service Environment subnet range.
+
 The internal health ping traffic on port 80 is isolated between the Load balancer and the internal servers. No outside traffic can reach the health ping endpoint.
 
 The normal app access ports inbound are as follows:
@@ -100,6 +105,7 @@ The normal app access ports inbound are as follows:
 
 > [!NOTE]
 > For FTP access, even if you want to disallow standard FTP on port 21, you still need to allow traffic from the LoadBalancer to the App Service Environment subnet range on port 21, as this is used for internal health ping traffic for the ftp service specifically.
+>
 
 ## Network routing