Merge pull request #270245 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: Taojunshen

articles/application-gateway/ingress-controller-migration.md

@@ -37,15 +37,10 @@ Using Azure CLI, delete your AGIC Helm deployment from your cluster. You need to
 ## Enable AGIC add-on using your existing Application Gateway 
 You can now enable the AGIC add-on in your AKS cluster to target your existing Application Gateway through Azure CLI or Portal. Run the following Azure CLI command to enable the AGIC add-on in your AKS cluster. The example enables the add-on in a cluster called *myCluster*, in a resource group called *myResourceGroup*, using the Application Gateway resource ID *appgwId* we saved in the earlier step. 
 
-
 ```azurecli-interactive
 az aks enable-addons -n myCluster -g myResourceGroup -a ingress-appgw --appgw-id $appgwId
 ```
 
-Alternatively, you can navigate to your AKS cluster in Portal using this [link](https://portal.azure.com/?feature.aksagic=true) and enable the AGIC add-on in the Networking tab of your cluster. Select your existing Application Gateway from the dropdown menu when you choose which Application Gateway the add-on should target. 
-
-![Application Gateway Ingress Controller Portal](./media/tutorial-ingress-controller-add-on-existing/portal-ingress-controller-add-on.png)
-
 ## Next Steps
 - [**Application Gateway Ingress Controller Troubleshooting**](ingress-controller-troubleshoot.md): Troubleshooting guide for AGIC 
-- [**Application Gateway Ingress Controller Annotations**](ingress-controller-annotations.md): List of annotations on AGIC 
+- [**Application Gateway Ingress Controller Annotations**](ingress-controller-annotations.md): List of annotations on AGIC 

articles/application-gateway/media/tutorial-ingress-controller-add-on-existing/portal-ingress-controller-add-on.png

@@ -79,15 +79,9 @@ appgwId=$(az network application-gateway show -n myApplicationGateway -g myResou
 az aks enable-addons -n myCluster -g myResourceGroup -a ingress-appgw --appgw-id $appgwId
 ```
 
-## Enable the AGIC add-on in existing AKS cluster through Azure portal 
-
-If you'd like to use Azure portal to enable AGIC add-on, go to [(https://aka.ms/azure/portal/aks/agic)](https://aka.ms/azure/portal/aks/agic) and navigate to your AKS cluster through the portal link. From there, go to the Networking tab within your AKS cluster. You'll see an application gateway ingress controller section, which allows you to enable/disable the ingress controller add-on using the Azure portal. Select the box next to **Enable ingress controller**, and then select the application gateway you created, **myApplicationGateway** from the dropdown menu. Select **Save**.
-
 > [!IMPORTANT]
 > When you use an application gateway in a different resource group than the AKS cluster resource group, the managed identity **_ingressapplicationgateway-{AKSNAME}_** that is created must have **Contributor** and **Reader** roles set in the application gateway resource group.
 
-:::image type="content" source="./media/tutorial-ingress-controller-add-on-existing/portal-ingress-controller-add-on.png" alt-text="Screenshot showing how to enable application gateway ingress controller from the networking page of the Azure Kubernetes Service.":::
-
 ## Peer the two virtual networks together
 
 Since you deployed the AKS cluster in its own virtual network and the Application gateway in another virtual network, you'll need to peer the two virtual networks together in order for traffic to flow from the Application gateway to the pods in the cluster. Peering the two virtual networks requires running the Azure CLI command two separate times, to ensure that the connection is bi-directional. The first command will create a peering connection from the Application gateway virtual network to the AKS virtual network; the second command will create a peering connection in the other direction.

articles/application-gateway/tutorial-ingress-controller-add-on-existing.md

@@ -13,7 +13,7 @@ ms.author: banders
 
 # Download your savings plan price sheet
 
-This article explains how you can download the price sheet for an Enterprise Agreement (EA) or Microsoft Customer Agreement (MCA). Your price sheet contains pricing for savings plans.
+This article explains how you can download the price sheet for an Enterprise Agreement (EA) or Microsoft Customer Agreement (MCA) via the Azure portal. Included in the price sheet is the list of products that are eligible for savings plans, as well as the 1- and 3-year savings plans prices for these products.
 
 ## Download EA price sheet
 
@@ -51,4 +51,4 @@ If you have questions about Azure savings plan for compute, contact your account
   - [Who can manage a savings plan](manage-savings-plan.md#who-can-manage-a-savings-plan)
   - [How saving plan discount is applied](discount-application.md)
   - [Understand savings plan costs and usage](utilization-cost-reports.md)
-  - [Software costs not included with Azure savings plans](software-costs-not-included.md)
+  - [Software costs not included with Azure savings plans](software-costs-not-included.md)

articles/cost-management-billing/savings-plan/download-savings-plan-price-sheet.md

@@ -72,7 +72,7 @@ Machine Learning environments are an encapsulation of the environment where your
 
 Machine Learning supports two types of environments: curated and custom.
 
-Curated environments are provided by Machine Learning and are available in your workspace by default. They're intended to be used as is. They contain collections of Python packages and settings to help you get started with various machine learning frameworks. These precreated environments also allow for faster deployment time. For a full list, see [Azure Machine Learning curated environments](resource-curated-environments.md).
+Curated environments are provided by Machine Learning and are available in your workspace by default. They're intended to be used as is. They contain collections of Python packages and settings to help you get started with various machine learning frameworks. These precreated environments also allow for faster deployment time. To retrieve a full list of available environments, see [Azure Machine Learning environments with the CLI & SDK (v2)](/azure/machine-learning/how-to-manage-environments-v2?view=azureml-api-2&tabs=cli&preserve-view=true#curated-environments).
 
 In custom environments, you're responsible for setting up your environment. Make sure to install the packages and any other dependencies that your training or scoring script needs on the compute. Machine Learning allows you to create your own environment by using:
 
@@ -82,7 +82,7 @@ In custom environments, you're responsible for setting up your environment. Make
 
 ## Model
 
-Machine Learning models consist of the binary files that represent a machine learning model and any corresponding metadata. You can create models from a local or remote file or directory. For remote locations, `https`, `wasbs`, and `azureml` locations are supported. The created model is tracked in the workspace under the specified name and version. Machine Learning supports three types of storage format for models:
+Machine Learning models consist of the binary files that represent a machine learning model and any corresponding metadata. You can create models from a local or remote file or directory. For remote locations, `https`, `wasbs`, and `azureml` locations are supported. The created model is tracked in the workspace under the specified name and version. Machine Learning supports three types of storage formats for models:
 
 * `custom_model`
 * `mlflow_model`

articles/machine-learning/azure-machine-learning-glossary.md

@@ -31,7 +31,7 @@ The following table provides a mapping of the version of the Windows Log Analyti
 
 | Agent version | VM extension version | Release date | Release notes |
 | --- | --- | --- | --- |
-| 10.20.18076.0 | 1.0.18076   | September 2024 | - Support for TLS 1.3 and small patches |
+| 10.20.18076.0 | 1.0.18076   | March 2024     | - Support for TLS 1.3 and small patches |
 | 10.20.18069.0 | 1.0.18069   | September 2023 | - Rebuilt the agent to resign then and to replace and expired certificates, Added deprication message to installer |
 | 10.20.18067.0 | 1.0.18067   | March 2022     | - Bug fix for performance counters <br> - Enhancements to Agent Troubleshooter |
 | 10.20.18064.0 | 1.0.18064   | December 2021  | - Bug fix for intermittent crashes |