Merge pull request #304815 from MicrosoftDocs/main

Auto Publish – main to live - 2025-08-28 17:00 UTC

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

articles/api-management/observability.md

@@ -6,7 +6,7 @@ author: dlepow
 
 ms.service: azure-api-management
 ms.topic: concept-article
-ms.date: 02/10/2025
+ms.date: 08/26/2025
 ms.author: danlep
 ---
 
@@ -27,21 +27,20 @@ The following table summarizes all the observability capabilities supported by A
 > [!NOTE]
 > For API consumers who use the developer portal, a built-in API report is available. It only provides information about their individual API usage during the preceding 90 days. Currently, the built-in API report isn't available in the developer portal for the v2 service tiers.
 >  
-| Tool        | Useful for    | Data lag | Retention | Sampling | Data kind | Supported Deployment Model(s) |
+| Tool        | Useful for    | Data lag<sup>4</sup> | Retention | Sampling | Data kind | Supported Deployment Model(s) |
 |:------------- |:-------------|:---- |:----|:---- |:--- |:---- |
-| **[API Inspector](api-management-howto-api-inspector.md)** | Testing and debugging | Instant | Last 100 traces | Turned on per request | Request traces | Managed, Self-hosted, Azure Arc, Workspace |
+| **[Request tracing (API Inspector)](api-management-howto-api-inspector.md)** | Testing and debugging | Instant | Last 100 traces | Turned on per request | Request traces | Managed, Self-hosted, Azure Arc, Workspace |
 | **[Built-in Analytics](monitor-api-management.md#get-api-analytics-in-azure-api-management)** | Reporting and monitoring | Minutes | Lifetime | 100% | Reports and logs | Managed |
 | **[Azure Monitor Metrics](monitor-api-management-reference.md#metrics)** | Reporting and monitoring | Minutes | 90 days (upgrade to extend) | 100% | Metrics | Managed, Self-hosted<sup>2</sup>, Azure Arc |
 | **[Azure Monitor Logs](monitor-api-management-reference.md#resource-logs)** | Reporting, monitoring, and debugging | Minutes | 31 days/5GB (upgrade to extend) | 100% (adjustable) | Logs | Managed<sup>1</sup>, Self-hosted<sup>3</sup>, Azure Arc<sup>3</sup> |
 | **[Azure Application Insights](api-management-howto-app-insights.md)** | Reporting, monitoring, and debugging | Seconds | 90 days/5GB (upgrade to extend) | Custom | Logs, metrics | Managed<sup>1</sup>, Self-hosted<sup>1</sup>, Azure Arc<sup>1</sup>, Workspace<sup>1</sup> |
 | **[Logging through Azure Event Hubs](api-management-howto-log-event-hubs.md)** | Custom scenarios | Seconds | User managed | Custom | Custom | Managed<sup>1</sup>, Self-hosted<sup>1</sup>, Azure Arc<sup>1</sup> |
 | **[OpenTelemetry](how-to-deploy-self-hosted-gateway-kubernetes-opentelemetry.md#introduction-to-opentelemetry)** | Monitoring | Minutes | User managed | 100% | Metrics | Self-hosted<sup>2</sup> |
 
-*1. Optional, depending on the configuration of feature in Azure API Management*
-
-*2. Optional, depending on the configuration of the gateway*
-
-*3. The [self-hosted gateway](self-hosted-gateway-overview.md) currently doesn't send diagnostic logs to Azure Monitor. However, it's possible to configure and persist logs locally where the self-hosted gateway is deployed. For more information, please see [configuring local metrics and logs for self-hosted gateway](how-to-configure-local-metrics-logs.md)*
+<sup>1</sup> Optional, depending on the configuration of feature in Azure API Management.<br/>
+<sup>2</sup> Optional, depending on the configuration of the gateway.<br/>
+<sup>3</sup> The [self-hosted gateway](self-hosted-gateway-overview.md) currently doesn't send diagnostic logs to Azure Monitor. However, it's possible to configure and persist logs locally where the self-hosted gateway is deployed. For more information, see [configuring local metrics and logs for self-hosted gateway](how-to-configure-local-metrics-logs.md).<br/>
+<sup>4</sup> Except for request tracing, all logging in API Management occurs asynchronously.
 
 ## Related content
 

articles/app-service/monitor-app-service-reference.md

@@ -73,13 +73,11 @@ The following table lists more information about resource logs you can collect f
 | AppServiceEnvironmentPlatformLogs | Yes | N/A | Yes | Yes | App Service Environment: scaling, configuration changes, and status logs|
 | AppServiceAuditLogs | Yes | Yes | Yes | Yes | Login activity via FTP and Kudu |
 | AppServiceFileAuditLogs | Yes | Yes | TBA | TBA | File changes made to the site content; **only available for Premium tier and above** |
-| AppServiceAppLogs | ASP.NET | ASP.NET | Java SE & Tomcat Images <sup>1</sup> | Java SE & Tomcat Blessed Images <sup>1</sup> | Application logs |
+| AppServiceAppLogs | ASP.NET | ASP.NET | Java SE & Tomcat Images | Java SE & Tomcat Images | Java and Tomcat are supported in their default configuration. [Additional code and/or configuration might be required for some logging frameworks](https://github.com/Azure-Samples/SpringBoot3Log4j2AppSvcLogs). |
 | AppServiceIPSecAuditLogs  | Yes | Yes | Yes | Yes | Requests from IP Rules |
 | AppServicePlatformLogs  | TBA | Yes | Yes | Yes | Container operation logs |
 | AppServiceAntivirusScanAuditLogs | Yes | Yes | Yes | Yes | [Anti-virus scan logs](https://azure.github.io/AppService/2020/12/09/AzMon-AppServiceAntivirusScanAuditLogs.html) using Microsoft Defender for Cloud; **only available for Premium tier** | 
 
-<sup>1</sup> For Java SE apps, add "$WEBSITE_AZMON_PREVIEW_ENABLED" to the app settings and set it to 1 or to true.
-
 [!INCLUDE [horz-monitor-ref-logs-tables](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-logs-tables.md)]
 ### App Services
 
@@ -125,4 +123,4 @@ The following table lists common activity log operations related to App Service.
 ## Related content
 
 - See [Monitor App Service](monitor-app-service.md) for a description of monitoring App Service.
-- See [Monitor Azure resources with Azure Monitor](/azure/azure-monitor/essentials/monitor-azure-resource) for details on monitoring Azure resources.
+- See [Monitor Azure resources with Azure Monitor](/azure/azure-monitor/essentials/monitor-azure-resource) for details on monitoring Azure resources.

articles/azure-fluid-relay/index.yml

@@ -7,7 +7,7 @@ metadata:
   title: Azure Fluid Relay
   description: Azure Fluid Relay is a managed cloud service that supports Fluid Framework Clients
   ms.service: azure-fluid
-  ms.author: mahgarg
+  ms.author: pranshukumar
   ms.topic: landing-page
   ms.date: 08/19/2023
 

articles/azure-netapp-files/data-protection-disaster-recovery-options.md

@@ -13,7 +13,7 @@ ms.author: anfdocs
 
 Learn about the different data protection and disaster recovery features in Azure NetApp Files and understand what solutions best serve your needs.  
 
-## On-Disk data protection
+## On-disk data protection
 
 Azure NetApp Files Flexible, Standard, Premium and Ultra service levels are built on a [fault-tolerant bare-metal fleet powered by ONTAP®](azure-netapp-files-introduction.md#simplicity-and-availability), delivering enterprise-grade resilience, and uses RAID-DP® (Double Parity RAID) to safeguard data against disk failures. This mechanism distributes parity across multiple disks, enabling seamless data recovery even if two disks fail simultaneously. RAID-DP has a long-standing presence in the enterprise storage industry and is recognized for its proven reliability and fault tolerance.
 

articles/azure-vmware/native-auto-peering-sync.md

@@ -34,6 +34,10 @@ Ensures that virtual machines hosted in Azure VMware Solution can securely and c
 
 ---
 
+## Prerequisite
+
+- Ensure the "Microsoft.BareMetal" resource provider is registered.
+
 ## Deployment steps 
 
 1. Deploy your Azure VMware Solution private cloud.  

articles/azure-vmware/native-create-azure-vmware-virtual-network-private-cloud.md

@@ -21,9 +21,10 @@ With this generation, you can directly create the private cloud using the AV64 S
 
 Before you begin, these items are required to create an Azure VMware Solution Gen 2 private cloud:
 
+- Read through the [Gen 2 design considerations](native-network-design-consideration.md) before deploying your private cloud.
 - Enable the Azure VMware Solution Fleet Rp Service Principal as described in the [enable Azure VMware Solution Fleet Rp service Principal](native-first-party-principle-security.md).
 - Ensure you have appropriate administrative rights and permission to create a private cloud. You must be at minimum Owner or User Access Administrator on the subscription.
-- Hosts provisioned and the "Microsoft.AVS" resource provider is registered.
+- Hosts provisioned and the "Microsoft.AVS" and "Microsoft.BareMetal" resource provider is registered.
 - Deploy or use an existing Azure Virtual Network with a minimum network address space of a /22 or four /24s.
 - The newly created Azure Virtual Network and your Azure VMware Solution Gen 2 private cloud must be in the same Resource Group.
 - Ensure you have sufficient AV64 quota allocated to your subscription in the desired region before your deployment. 

articles/azure-vmware/native-first-party-principle-security.md

@@ -69,12 +69,13 @@ If customers **delete either application ID** (for example, during a tenant clea
 
 To help customers quickly identify issues, we added an **error check** that validates the presence of both apps. If either app is missing or disabled, the error message clearly indicates the required fix and provides a link back to this documentation for guidance.  
 
-> [!Important:]
-> Always verify both applications are enabled before deploying or troubleshooting an Azure VMware Solution Gen 2 private cloud.  
-
+> [!IMPORTANT]  
+> Always verify both applications are enabled before deploying or troubleshooting an Azure VMware Solution Gen 2
 
 ## Next steps
   
+- Review steps to [enable role assignments for your identifies if they are removed](native-role-assignment.md) 
+
 - Follow a tutorial for [Creating an Azure VMware Gen 2 private cloud](native-create-azure-vmware-virtual-network-private-cloud.md)
 
 - Learn more about [Azure VMware Solution Gen 2 private cloud design considerations](native-network-design-consideration.md)

articles/azure-vmware/native-introduction.md

@@ -11,7 +11,6 @@ ms.author: jacobjaygbay
 # customer intent: As a cloud administrator, I want to learn about Azure VMware Solution Gen 2 private clouds so that I can understand the features and benefits of this offering.
 # Customer intent: As a cloud administrator, I want to understand the features and benefits of Azure VMware Solution Generation 2 private clouds so that I can make informed decisions about deploying and managing cost-effective, secure, and high-performance cloud architectures in Azure.
 ---
-
 # Introduction to Azure VMware Solution Generation 2 Private Clouds
 
 Azure VMware Solution Generation 2 (Gen 2) private clouds can now be deployed inside an Azure Virtual Network, conforming Azure VMware Solution to Azure networking standards. This architecture simplifies networking architecture, enhances data transfer speeds, reduces latency for workloads, and improves performance when accessing other Azure services. Users can now deploy Azure VMware Solution private clouds with the AV64 SKU directly, eliminating the need for a minimum of 3-host AV36, AV36P, AV48, or AV52 seed cluster. A minimum 3-host AV64 cluster is still required. The same Azure VMware Solution limits apply as described in [Scale clusters in a Private Cloud](tutorial-scale-private-cloud.md).
@@ -22,7 +21,7 @@ Azure VMware Solution Generation 2 (Gen 2) private clouds can now be deployed in
 
 The following table summarizes the differences between Gen 1 and Gen 2 private clouds:
 
-| Feature               | Azure VMware Solution Gen 1 private clouds    | Azure VMware Solution Gen 2 private clouds       |
+| Feature               | Gen 1   | Gen 2      |
 |-----------------------|-----------------------------------------------|--------------------------------------------------|
 | Supported SKU type    | <ul><li>AV36, AV36P, AV52, AV48</li><li>AV64 (with seed cluster of at least three AV36, AV36P, AV48, or AV52 nodes)</li></ul>| <ul><li>Minimum 3-host AV64 cluster</li></ul>|
 | Network Attach Model  | <ul><li>ExpressRoute</li></ul>                | <ul><li>Virtual Network</li></ul>                |