Merge pull request #297688 from MicrosoftDocs/main

Merged by Learn.Build PR Management system

Author: learn-build-service-prod[bot]

articles/application-gateway/ingress-controller-install-existing.md

@@ -6,7 +6,7 @@ author: greg-lindsay
 ms.service: azure-application-gateway
 ms.custom: devx-track-arm-template, devx-track-azurecli
 ms.topic: how-to
-ms.date: 2/28/2025
+ms.date: 4/4/2025
 ms.author: greglin
 ---
 
@@ -264,15 +264,15 @@ Use [Cloud Shell](https://shell.azure.com/) to install the AGIC Helm package:
 1. Install the Helm chart with the `helm-config.yaml` configuration from the previous step:
 
     ```bash
-    helm install agic-controller oci://mcr.microsoft.com/azure-application-gateway/charts/ingress-azure --version 1.8.0 -f helm-config.yaml
+    helm install agic-controller oci://mcr.microsoft.com/azure-application-gateway/charts/ingress-azure --version 1.8.1 -f helm-config.yaml
     ```
 
     Alternatively, you can combine `helm-config.yaml` and the Helm command in one step:
 
     ```bash
     helm install oci://mcr.microsoft.com/azure-application-gateway/charts/ingress-azure \
          --name agic-controller \
-         --version 1.8.0 \
+         --version 1.8.1 \
          --namespace default \
          --debug \
          --set appgw.name=applicationgatewayABCD \

articles/application-gateway/ingress-controller-install-new.md

@@ -5,7 +5,7 @@ services: application-gateway
 author: greg-lindsay
 ms.service: azure-application-gateway
 ms.topic: how-to
-ms.date: 10/15/2024
+ms.date: 4/4/2025
 ms.author: greglin
 ---
 
@@ -288,7 +288,7 @@ If you use [Cloud Shell](https://shell.azure.com/), you don't need to install He
 1. Install the AGIC package:
 
     ```bash
-    helm install agic-controller oci://mcr.microsoft.com/azure-application-gateway/charts/ingress-azure --version 1.8.0 -f helm-config.yaml
+    helm install agic-controller oci://mcr.microsoft.com/azure-application-gateway/charts/ingress-azure --version 1.8.1 -f helm-config.yaml
     ```
 
 ## Install a sample app

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

@@ -5,7 +5,7 @@ services: application-gateway
 author: greg-lindsay
 ms.service: azure-application-gateway
 ms.topic: how-to
-ms.date: 2/28/2025
+ms.date: 4/4/2025
 ms.author: greglin
 ---
 
@@ -39,7 +39,7 @@ You can upgrade the Azure Application Gateway Ingress Controller (AGIC) for Kube
     helm upgrade \
         odd-billygoat \
         oci://mcr.microsoft.com/azure-application-gateway/charts/ingress-azure \
-        --version 1.8.0
+        --version 1.8.1
     ```
 
 ## Roll back

articles/azure-functions/functions-add-output-binding-cosmos-db-vs-code.md

@@ -78,10 +78,10 @@ In the [previous quickstart article](./create-first-function-vs-code-csharp.md),
 
     |Prompt| Selection|
     |--|--|
-    |**Enter new app setting name**| Type `CosmosDbConnectionSetting`.|
-    |**Enter value for "CosmosDbConnectionSetting"**| Paste the connection string of your Azure Cosmos DB account you copied. You can also configure [Microsoft Entra identity](./functions-bindings-cosmosdb-v2-trigger.md#connections) as an alternative.|
+    |**Enter new app setting name**| Type `CosmosDbConnectionString`.|
+    |**Enter value for "CosmosDbConnectionString"**| Paste the connection string of your Azure Cosmos DB account you copied. You can also configure [Microsoft Entra identity](./functions-bindings-cosmosdb-v2-trigger.md#connections) as an alternative.|
 
-    This creates an application setting named connection `CosmosDbConnectionSetting` in your function app in Azure. Now, you can download this setting to your local.settings.json file.
+    This creates an application setting named connection `CosmosDbConnectionString` in your function app in Azure. Now, you can download this setting to your local.settings.json file.
 
 1. Press <kbd>F1</kbd> again to open the command palette, then search for and run the command `Azure Functions: Download Remote Settings...`. 
 
@@ -136,7 +136,7 @@ The `MyDocument` class defines an object that gets written to the database. The
 
 The `MultiResponse` class allows you to both write to the specified collection in the Azure Cosmos DB and return an HTTP success message. Because you need to return a `MultiResponse` object, you need to also update the method signature.
 
-Specific attributes specify the name of the container and the name of its parent database. The connection string for your Azure Cosmos DB account is set by the `CosmosDbConnectionSetting`.  
+Specific attributes specify the name of the container and the name of its parent database. The connection string for your Azure Cosmos DB account is set by the `CosmosDbConnectionString`.  
 ::: zone-end  
 ::: zone pivot="programming-language-javascript"  
 Binding attributes are defined directly in your function code. The [Azure Cosmos DB output configuration](./functions-bindings-cosmosdb-v2-output.md#configuration) describes the fields required for an Azure Cosmos DB output binding.  
@@ -155,10 +155,10 @@ Binding attributes are defined directly in the *function_app.py* file. You use t
 
 ```python
 @app.cosmos_db_output(arg_name="outputDocument", database_name="my-database", 
-    container_name="my-container", connection="CosmosDbConnectionSetting")
+    container_name="my-container", connection="CosmosDbConnectionString")
 ```
 
-In this code, `arg_name` identifies the binding parameter referenced in your code, `database_name` and `container_name` are the database and collection names that the binding writes to, and `connection` is the name of an application setting that contains the connection string for the Azure Cosmos DB account, which is in the `CosmosDbConnectionSetting` setting in the *local.settings.json* file.  
+In this code, `arg_name` identifies the binding parameter referenced in your code, `database_name` and `container_name` are the database and collection names that the binding writes to, and `connection` is the name of an application setting that contains the connection string for the Azure Cosmos DB account, which is in the `CosmosDbConnectionString` setting in the *local.settings.json* file.  
 ::: zone-end  
 
 ## Add code that uses the output binding

articles/azure-netapp-files/azure-government.md

@@ -25,7 +25,7 @@ All [Azure NetApp Files features](whats-new.md) available on Azure public cloud
 | Azure NetApp Files features | Azure public cloud availability |  Azure Government availability |
 |:--- |:--- |:--- |
 | Azure NetApp Files large volumes | Generally available (GA) | Generally available [(select regions)](large-volumes-requirements-considerations.md#supported-regions) |
-| Azure NetApp Files file access logs | Public preview | Public preview [(select regions)](manage-file-access-logs.md#supported-regions) |
+| Azure NetApp Files file access logs | Public preview | No |
 
 ## Portal access
 

articles/azure-netapp-files/manage-file-access-logs.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-ahibbard
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 04/01/2025
+ms.date: 04/04/2025
 ms.author: anfdocs
 ms.custom: references_regions
 ---
@@ -106,13 +106,13 @@ Availability for file access log is limited to the following regions:
 - Central US
 - East US
 - East US 2
+- Japan East
 - Japan West
 - North Europe
 - South Central US
 - Switzerland North
 - Switzerland West
 - UK South
-- US Gov Virginia
 - West Europe
 - West US
 - West US 2

articles/azure-resource-manager/management/azure-subscription-service-limits.md

@@ -63,12 +63,6 @@ The following limits apply when you use Azure Resource Manager and Azure resourc
 
 [!INCLUDE [azure-resource-groups-limits](../../../includes/azure-resource-groups-limits.md)]
 
-<a name='azure-active-directory-limits'></a>
-
-## Microsoft Entra ID limits
-
-[!INCLUDE [entra-service-limits](../../../includes/entra-service-limits-include.md)]
-
 ## Azure API Center limits
 
 [!INCLUDE [api-center-service-limits](../../api-center/includes/api-center-service-limits.md)]
@@ -404,10 +398,6 @@ For limits specific to Media Services v2 (legacy), see [Media Services v2 (legac
 
 [!INCLUDE [mobile-services-limits](../../../includes/mobile-services-limits.md)]
 
-## Microsoft Entra service limits
-
-[!INCLUDE [microsoft-entra-service-limits](../../../includes/entra-service-limits-include.md)]
-
 ## Azure networking limits
 
 [!INCLUDE [azure-virtual-network-limits](../../../includes/azure-virtual-network-limits.md)]
@@ -482,6 +472,12 @@ Unless stated otherwise, the following limits apply to Azure VPN Gateway resourc
 
 [!INCLUDE [dev-box-limits](../../../includes/dev-box-limits.md)]
 
+<a name='azure-active-directory-limits'></a>
+
+## Microsoft Entra service limits
+
+See [Microsoft Entra service limits](/entra/identity/users/directory-service-limits-restrictions) for Microsoft Entra service limits.
+
 ## Microsoft Purview limits
 
 See [Classic Microsoft Purview data governance limits](../../purview/how-to-manage-quotas.md#classic-microsoft-purview-data-governance-limits) for the most current Microsoft Purview quotas.

articles/azure-vmware/architecture-network-design-considerations.md

@@ -46,7 +46,7 @@ The following ASNs are reserved for internal Azure VMware Solution infrastructur
 
 - **Transport ASNs (T0 Gateways):** 64513 (NSX Edges), 64600 – 64940
 
-- **Management ASNs:** 65000 – 65412
+- **Management ASNs:** 65000 – 65412, 398656-398670, 400572-400581
 
 ### Impact of Using Reserved ASNs
 

articles/cost-management-billing/costs/save-share-views.md

@@ -18,7 +18,7 @@ Cost analysis is used to explore costs and get quick answers for things like fin
 
 ## Save and share cost views
 
-A *view* is a saved query in Cost Management. When you save a view, all settings in cost analysis are saved, including filters, grouping, granularity, the main chart type, and donut charts. Underlying data isn't saved. Only you can see private views, while everyone with Cost Management Reader access or greater to the scope can see shared views.
+A *view* is a saved query in Cost Management. When you save a view, all settings in cost analysis are saved, including filters, grouping, granularity, the main chart type, and donut charts. A view is saved only within the scope in which it was created. Underlying data isn't saved. Only you can see the private views you saved per scope, while shared views, saved within a scope, can be seen by anyone with Cost Management Reader access or greater to the scope.
 
 Check out the [Sharing and saving views](https://www.youtube.com/watch?v=kQkXXj-SmvQ) video.
 
@@ -36,7 +36,7 @@ You can also pin the current view to an Azure portal dashboard. Pinning only inc
 1. After you save a view, it's available to select from the **View** menu.  
      :::image type="content" source="./media/save-share-views/view-list.png" alt-text="Screen shot showing the View list." lightbox="./media/save-share-views/view-list.png" :::
 
-You can save up to 100 private views across all scopes for yourself and up to 100 shared views per scope that anyone with Cost Management Reader or greater access can use.
+You can save up to 100 private views, across all scopes you have access to, for yourself and up to 100 shared views per scope that anyone with Cost Management Reader or greater access can use.
 
 ### To share a view