Merge pull request #256211 from MicrosoftDocs/main

10/25/2023 PM Publish

Author: Taojunshen

.openpublishing.redirection.json

@@ -9367,6 +9367,11 @@
             "redirect_url": "/azure/azure-vmware/configure-site-to-site-vpn-gateway",
             "redirect_document_id": false
         },
+        {
+            "source_path_from_root": "/articles/vpn-gateway/vpn-gateway-howto-multi-site-to-site-resource-manager-portal.md",
+            "redirect_url": "/azure/vpn-gateway/add-remove-site-to-site-connections",
+            "redirect_document_id": false
+        },
         {
             "source_path_from_root": "/articles/vpn-gateway/vpn-gateway-howto-openvpn-clients.md",
             "redirect_url": "/azure/vpn-gateway/point-to-site-vpn-client-cert-windows",
@@ -9381,7 +9386,7 @@
          "source_path_from_root": "/articles/vpn-gateway/vpn-gateway-forced-tunneling-rm.md",
          "redirect_url": "/azure/vpn-gateway/about-site-to-site-tunneling",
          "redirect_document_id": false
-     },
+        },
         {
             "source_path_from_root": "/articles/azure-vmware/public-ip-usage.md",
             "redirect_url": "/azure/azure-vmware/enable-public-ip-nsx-edge",

articles/api-center/overview.md

@@ -38,7 +38,7 @@ In preview, create and use an API Center in the Azure portal for the following:
 
 For more information about the information you can manage and the capabilities in API Center, see [Key concepts](key-concepts.md).
 
-## Preview limitations
+## Available regions
 
 * In preview, API Center is available in the following Azure regions:
    * Australia East

articles/api-center/set-up-api-center.md

@@ -55,7 +55,7 @@ If you haven't already, you need to register the **Microsoft.ApiCenter** resourc
 
     1. Enter a **Name** for your API center. It must be unique in your subscription. 
 
-    1. In **Region**, select one of the [available regions](overview.md#preview-limitations) for API Center preview. 
+    1. In **Region**, select one of the [available regions](overview.md#available-regions) for API Center preview. 
 
 1. Optionally, on the **Tags** tab, add one or more name/value pairs to help you categorize your Azure resources.
 

articles/api-management/api-management-howto-policies.md

@@ -1,13 +1,13 @@
 ---
-title: Policies in Azure API Management | Microsoft Docs
-description: Learn about policies in API Management, a way for API publishers to change API behavior through configuration. Policies are statements that run sequentially on the request or response of an API.
+title: Policies in Azure API Management 
+description: Introduction to API Management policies, which change API behavior through configuration. Policy statements run sequentially on an API request or response.
 services: api-management
 documentationcenter: ''
 author: dlepow
 
 ms.service: api-management
 ms.topic: article
-ms.date: 03/07/2023
+ms.date: 10/18/2023
 ms.author: danlep
 
 ---
@@ -65,7 +65,7 @@ By placing policy statements in the `on-error` section, you can:
 * Inspect and customize the error response using the `set-body` policy.
 * Configure what happens if an error occurs. 
 
-For more information, see [Error handling in API Management policies](./api-management-error-handling-policies.md) 
+For more information, see [Error handling in API Management policies](./api-management-error-handling-policies.md). 
 
 ## Policy expressions
 
@@ -76,7 +76,7 @@ Unless the policy specifies otherwise, [policy expressions](api-management-polic
 
 Each expression has access to the implicitly provided `context` variable and an allowed subset of .NET Framework types.
 
-Policy expressions provide a sophisticated means to control traffic and modify API behavior without requiring you to write specialized code or modify backend services. Some policies are based on policy expressions, such as the [Control flow][Control flow] and [Set variable][Set variable]. For more information, see [Advanced policies][Advanced policies].
+Policy expressions provide a sophisticated means to control traffic and modify API behavior without requiring you to write specialized code or modify backend services. Some policies are based on policy expressions, such as [Control flow][Control flow] and [Set variable][Set variable]. For more information, see [Advanced policies][Advanced policies].
 
 ## Scopes
 
@@ -95,10 +95,16 @@ When configuring a policy, you must first select the scope at which the policy a
 ### Things to know
 
 * For fine-grained control for different API consumers, you can configure policy definitions at more than one scope
-* Not all policies can be applied at each scope and policy section
-* When configuring policy definitions at more than one scope, you control the policy evaluation order in each policy section by placement of the `base` element 
+* Not all policies are supported at each scope and policy section
+* When configuring policy definitions at more than one scope, you control policy inheritance and the policy evaluation order in each policy section by placement of the `base` element
+* Policies applied to API requests are also affected by the request context, including the presence or absence of a subscription key used in the request, the API or product scope of the subscription key, and whether the API or product requires a subscription. 
 
-For more information, see [Set or edit policies](set-edit-policies.md#use-base-element-to-set-policy-evaluation-order).
+    [!INCLUDE [api-management-product-policy-alert](../../includes/api-management-product-policy-alert.md)]
+
+For more information, see:
+
+* [Set or edit policies](set-edit-policies.md#use-base-element-to-set-policy-evaluation-order)
+* [Subscriptions in API Management](api-management-subscriptions.md)
 
 ### GraphQL resolver policies
 

articles/api-management/api-management-subscriptions.md

@@ -77,8 +77,7 @@ Each API Management instance comes with a built in all-access subscription that
 > [!WARNING]
 > The all-access subscription enables access to every API in the API Management instance and should only be used by authorized users. Never use this subscription for routine API access or embed the all-access subscription key in client apps.
 
-> [!NOTE]
-> If you're using an API-scoped subscription or the all-access subscription, any [policies](api-management-howto-policies.md) configured at the product scope aren't applied to requests from that subscription.
+[!INCLUDE [api-management-product-policy-alert](../../includes/api-management-product-policy-alert.md)]
 
 ### Standalone subscriptions
 

articles/api-management/set-edit-policies.md

@@ -1,13 +1,13 @@
 ---
 title: How to set or edit Azure API Management policies | Microsoft Docs
-description: Learn how to use the Azure portal to set or edit policies in an Azure API Management instance. Policies are defined in XML documents that contain a sequence of statements that are run sequentially on the request or response of an API.
+description: Configure policies at different scopes in an Azure API Management instance using the policy editor in the Azure portal.
 services: api-management
 documentationcenter: ''
 author: dlepow
 
 ms.service: api-management
 ms.topic: how-to
-ms.date: 03/01/2022
+ms.date: 10/18/2023
 ms.author: danlep
 ---
 
@@ -149,6 +149,8 @@ Product scope is configured for a selected product.
 
 1. Select **Save** to propagate changes to the API Management gateway immediately.
 
+
+
 ### API scope
 
 API scope is configured for **All operations** of the selected API.
@@ -221,7 +223,7 @@ To modify the policy evaluation order using the policy editor:
 
     A globally scoped policy has no parent scope, and using the `base` element in it has no effect.
 
-## Next steps
+## Related content
 
 For more information about working with policies, see:
 

articles/application-gateway/proxy-buffers.md

@@ -86,4 +86,4 @@ For reference, visit [Azure SDK for .NET](/dotnet/api/microsoft.azure.management
 ## Limitations
 - API version 2020-01-01 or later should be used to configure buffers.
 - Currently, these changes are not supported through Portal and PowerShell.
-- Request and Response Buffers can only be disabled for the WAF v2 SKU if request body checking is disabled. Otherwise, Request and Response Buffers cannot be disabled for the WAF v2 SKU.
+- Request buffering cannot be disabled if you are running the WAF SKU of Application Gateway. The WAF requires the full request to buffer as part of processing, therefore, even if you disable request buffering within Application Gateway the WAF will still buffer the request. Response buffering is not impacted by the WAF.

articles/azure-arc/resource-bridge/upgrade.md

@@ -70,7 +70,7 @@ Or to upgrade a resource bridge on Azure Stack HCI, run: `az arcappliance upgrad
 
 Currently, private cloud providers differ in how they perform Arc resource bridge upgrades. Review the following information to see how to upgrade your Arc resource bridge for a specific provider.
 
-For Arc-enabled VMware vSphere (preview), manual upgrade is available, and cloud-managed upgrade is supported for appliances on version 1.0.15 and higher. When Arc-enabled VMware vSphere announces General Availability, appliances on version 1.0.15 and higher will receive cloud-managed upgrade as the default experience. Appliances that are below version 1.0.15 must be manually upgraded.
+For Arc-enabled VMware vSphere (preview), manual upgrade is available, and cloud-managed upgrade is supported for appliances on version 1.0.15 and higher. When Arc-enabled VMware vSphere announces General Availability, appliances on version 1.0.15 and higher will receive cloud-managed upgrade as the default experience. Appliances that are below version 1.0.15 must be manually upgraded. 
 
 [Azure Arc VM management (preview) on Azure Stack HCI](/azure-stack/hci/manage/azure-arc-vm-management-overview) supports upgrade of an Arc resource bridge on Azure Stack HCI, version 22H2 up until appliance version 1.0.14 and `az arcappliance` CLI extension version 0.2.33. These upgrades can be done through manual upgrade or a support request for cloud-managed upgrade. For subsequent upgrades, you must transition to Azure Stack HCI, version 23H2 (preview). In version 23H2 (preview), the LCM tool manages upgrades across all components as a "validated recipe" package. For more information, visit the [Arc VM management FAQ page](/azure-stack/hci/manage/azure-arc-vms-faq).
 
@@ -82,14 +82,16 @@ The Arc resource bridge version is tied to the versions of underlying components
 
 ## Supported versions
 
-Generally, the latest released version and the previous three versions (n-3) of Arc resource bridge are supported. For example, if the current version is 1.0.10, then the typical n-3 supported versions are:
+Generally, the latest released version and the previous three versions (n-3) of Arc resource bridge are supported, starting from appliance version 1.0.15 and onward. An Arc resource bridge with an appliance version earlier than 1.0.15 must be upgraded or redeployed to be at minimum on appliance version 1.0.15 to be in a production support window.
 
-- Current version: 1.0.10
-- n-1 version: 1.0.9
-- n-2 version: 1.0.8
-- n-3 version: 1.0.7
+For example, if the current version is 1.0.18, then the typical n-3 supported versions are:
 
-There might be instances where supported versions are not sequential. For example, version 1.0.11 is released and later found to contain a bug. A hot fix is released in version 1.0.12 and version 1.0.11 is removed. In this scenario, n-3 supported versions become 1.0.12, 1.0.10, 1.0.9, 1.0.8.
+- Current version: 1.0.18
+- n-1 version: 1.0.17
+- n-2 version: 1.0.16
+- n-3 version: 1.0.15
+
+There might be instances where supported versions are not sequential. For example, version 1.0.18 is released and later found to contain a bug. A hot fix is released in version 1.0.19 and version 1.0.18 is removed. In this scenario, n-3 supported versions become 1.0.19, 1.0.17, 1.0.16, 1.0.15.
 
 Arc resource bridge typically releases a new version on a monthly cadence, at the end of the month, although it's possible that delays could push the release date further out. Regardless of when a new release comes out, if you are within n-3 supported versions, then your Arc resource bridge version is supported. To stay updated on releases, visit the [Arc resource bridge release notes](https://github.com/Azure/ArcResourceBridge/releases) on GitHub.
 
@@ -113,3 +115,5 @@ To see the current version of an Arc resource bridge appliance, run `az arcappli
 
 - Learn about [Arc resource bridge maintenance operations](maintenance.md).
 - Learn about [troubleshooting Arc resource bridge](troubleshoot-resource-bridge.md).
+
+

articles/azure-functions/configure-monitoring.md

@@ -37,7 +37,14 @@ When custom application logs are sent directly, the host no longer be emits them
 
 ## Configure categories
 
-The Azure Functions logger includes a *category* for every log. The category indicates which part of the runtime code or your function code wrote the log. Categories differ between version 1.x and later versions. The following chart describes the main categories of logs that the runtime creates:
+The Azure Functions logger includes a *category* for every log. The category indicates which part of the runtime code or your function code wrote the log. Categories differ between version 1.x and later versions. 
+
+Category names are assigned differently in Functions compared to other .NET frameworks. For example, when you use `ILogger<T>` in ASP.NET, the category is the name of the generic type. C# functions also use `ILogger<T>`, but instead of setting the generic type name as a category, the runtime assigns categories based on the source. For example:
+ 
++ Entries related to running a function are assigned a category of `Function.<FUNCTION_NAME>`.
++ Entries created by user code inside the function, such as when calling `logger.LogInformation()`, are assigned a category of `Function.<FUNCTION_NAME>.User`.
+
+The following chart describes the main categories of logs that the runtime creates:
 
 # [v2.x+](#tab/v2)
 
@@ -74,13 +81,11 @@ The **Table** column indicates to which table in Application Insights the log is
 
 For each category, you indicate the minimum log level to send. The *host.json* settings vary depending on the [Functions runtime version](functions-versions.md).
 
-The example below defines logging based on the following rules:
-
-+ For logs of `Host.Results` or `Function`, only log events at `Error` or a higher level.
-+ For logs of `Host.Aggregator`, log all generated metrics (`Trace`).
-+ For all other logs, including user logs, log only `Information` level and higher events.
-+ For `fileLoggingMode` the default is `debugOnly`. The value `always` should only be used for short periods of time to review logs in the filesystem. Revert this setting when you are done debugging. 
+The examples below define logging based on the following rules:
 
++ The default logging level is set to `Warning` to prevent [excessive logging](#solutions-with-high-volume-of-telemetry) for unanticipated categories.
++ `Host.Aggregator` and `Host.Results` are set to lower levels. Setting these to too high a level (especially higher than `Information`) can result in loss of metrics and performance data.
++ Logging for function runs is set to `Information`. This can be [overridden](functions-host-json.md#override-hostjson-values) in local development to `Debug` or `Trace`, when needed.
 
 # [v2.x+](#tab/v2)
 
@@ -89,10 +94,10 @@ The example below defines logging based on the following rules:
   "logging": {
     "fileLoggingMode": "debugOnly",
     "logLevel": {
-      "default": "Information",
-      "Host.Results": "Error",
-      "Function": "Error",
-      "Host.Aggregator": "Trace"
+      "default": "Warning",
+      "Host.Aggregator": "Trace",
+      "Host.Results": "Information",
+      "Function": "Information"
     }
   }
 }
@@ -104,11 +109,11 @@ The example below defines logging based on the following rules:
 {
   "logger": {
     "categoryFilter": {
-      "defaultLevel": "Information",
+      "defaultLevel": "Warning",
       "categoryLevels": {
-        "Host.Results": "Error",
-        "Function": "Error",
-        "Host.Aggregator": "Trace"
+        "Host.Results": "Information",
+        "Host.Aggregator": "Trace",
+        "Function": "Information"
       }
     }
   }