Merge pull request #294268 from MicrosoftDocs/main

2/7/2025 AM Publish

Author: Taojunshen

articles/api-management/TOC.yml

@@ -703,3 +703,5 @@
     href: /answers/tags/29/azure-api-management
   - name: Stack Overflow
     href: https://stackoverflow.com/questions/tagged/azure-api-management
+  - name: aka.ms/apimlove
+    href: https://aka.ms/apimlove

articles/api-management/api-management-key-concepts.md

@@ -45,6 +45,9 @@ Common scenarios include:
 * **Multi-channel user experiences** - APIs are frequently used to enable user experiences such as web, mobile, wearable, or Internet of Things applications. Reuse APIs to accelerate development and ROI.
 * **B2B integration** - APIs exposed to partners and customers lower the barrier to integrate business processes and exchange data between business entities. APIs eliminate the overhead inherent in point-to-point integration. Especially with self-service discovery and onboarding enabled, APIs are the primary tools for scaling B2B integration.
 
+> [!TIP]
+> Visit [aka.ms/apimlove](https://aka.ms/apimlove) for a library of useful resources, including videos, blogs, and customer stories about using Azure API Management.
+
 ## API Management components
 
 Azure API Management is made up of an API *gateway*, a *management plane*, and a *developer portal*. These components are Azure-hosted and fully managed by default. API Management is available in various [tiers](#api-management-tiers) differing in capacity and features.
@@ -132,7 +135,8 @@ API Management integrates with many complementary Azure services to create enter
 **More information**:
 * [Basic enterprise integration](/azure/architecture/reference-architectures/enterprise-integration/basic-enterprise-integration?toc=%2Fazure%2Fapi-management%2Ftoc.json&bc=/azure/api-management/breadcrumb/toc.json)
 * [Landing zone accelerator](/azure/cloud-adoption-framework/scenarios/app-platform/api-management/landing-zone-accelerator?toc=%2Fazure%2Fapi-management%2Ftoc.json&bc=/azure/api-management/breadcrumb/toc.json)
-* [Import APIs to API Center from API Management](../api-center/import-api-management-apis.md?toc=%2Fazure%2Fapi-management%2Ftoc.json&bc=/azure/api-management/breadcrumb/toc.json)
+* [GenAI gateway capabilities in API Management](genai-gateway-capabilities.md)
+* [Synchronize APIs to API Center from API Management](../api-center/synchronize-api-management-apis.md?toc=%2Fazure%2Fapi-management%2Ftoc.json&bc=/azure/api-management/breadcrumb/toc.json)
 
 ## Key concepts
 

articles/application-gateway/for-containers/toc.yml

@@ -130,5 +130,5 @@
   - name: Regional availability
     href: https://azure.microsoft.com/global-infrastructure/services/
   - name: Stack Overflow
-    href: https://stackoverflow.com/questions/tagged/azure-application-gateway-for-containers
+    href: https://stackoverflow.com/questions/tagged/azure-app-gateway-for-containers
 

articles/azure-large-instances/workloads/epic/available-skus.md

@@ -8,7 +8,7 @@ ms.custom: references_regions
 author: jjaygbay1
 ms.author: jacobjaygbay
 ms.service: azure-large-instances
-ms.date: 06/01/2023
+ms.date: 2/7/2024
 ---
 
 # Azure Large Instances for Epic workload SKUs
@@ -70,7 +70,7 @@ A deployed tenant in the Azure Large Instances stamp is assigned to one Azure su
 If you deploy with another Azure subscription in the same Azure region, you also request for a separated Azure Large Instances tenant.
 
 ### Operational model
-In addition to its BareMetal offering, Azure Large Instances also has an offering where Microsoft deploys a foundational ESXi environment onto the host servers and subsequent configuration of VMware vCenter by Microsoft as an ESXi VM in the cluster. Microsoft owns the ESXi licenses. On the storage configurations, Azure Large Instances comes with highly redundant Fiber Channel storage provisioned. Microsoft retains the root admin access to ESXi and provides a cloud admin role for customer’s use. The Cloud Admin role in Azure Large Instances Solution has the following privileges on vCenter Server. 
+In addition to its BareMetal offering, Azure Large Instances also has an offering where Microsoft deploys a foundational ESXi environment onto the host servers and subsequent configuration of VMware vCenter Server by Microsoft as an ESXi VM in the vSphere cluster. Microsoft owns the ESXi licenses. On the storage configurations, Azure Large Instances comes with highly redundant Fiber Channel storage provisioned. Microsoft retains the root administrator access to ESXi and provides a cloud administrator role for customer’s use. The Cloud Admin role in Azure Large Instances Solution has the following privileges on vCenter Server. 
 
 The following table color-codes areas of management responsibility, where:
 

articles/cost-management-billing/manage/direct-ea-azure-usage-charges-invoices.md

@@ -270,7 +270,7 @@ For a new enrollment, the default PO number is the enrollment number.
 
 If you don’t change the PO number, then the same PO number is used for all upcoming invoices. The PO number doesn't automatically increment. If you want to get new PO number for each month, then update it from Azure portal.
 
-Starting in May 2025, the EA admin won't receive a notification email reminding them to update the PO number. However, you can create a custom alert to send an email notification to yourself every month after an invoice is finalized. Then you can use the email notification as a reminder to update your PO number. For more information, see [Subscribe to scheduled alerts](../costs/save-share-views.md#subscribe-to-scheduled-alerts). Set the alert **Frequency** to **Custom**, **Repeat every month**, and then choose a day early in the month to give yourself enough time to update the PO before the invoice is finalized. To view your usage and charges anytime, you can use the **Usage + Charges** tab in the [Azure portal](https://portal.azure.com).
+Starting in May 2025, the EA admin won't receive a notification email reminding them to update the PO number. However, you can create a custom alert to send an email notification to yourself every month before an invoice is finalized. Then you can use the email notification as a reminder to update your PO number. For more information, see [Subscribe to scheduled alerts](../costs/save-share-views.md#subscribe-to-scheduled-alerts). Set the alert **Frequency** to **Custom**, **Repeat every month**, and then choose a day early in the month to give yourself enough time to update the PO before the invoice is finalized. To view your usage and charges anytime, you can use the **Usage + Charges** tab in the [Azure portal](https://portal.azure.com).
 Here's an example of how to set up a custom alert to remind you to update your PO number:
 
 :::image type="content" source="./media/direct-ea-azure-usage-charges-invoices/subscribe-emails-reminder.png" alt-text="Screenshot showing the Subscribe to emails window where you can define the email frequency." lightbox="./media/direct-ea-azure-usage-charges-invoices/subscribe-emails-reminder.png" :::

articles/iot/howto-iot-industrial-dataspaces.md

@@ -17,7 +17,7 @@ Many manufacturers need to provide data about their manufactured products to the
 
 ## What is an industrial dataspace?
 
-An industrial dataspace is a virtual environment designed to facilitate the secure and efficient exchange of data between different organizations within an industrial ecosystem, focusing on the following key principles:
+An industrial dataspace is a virtual environment designed to facilitate the secure and efficient exchange of data between different organizations within an industrial ecosystem, such as those developed by [International Data Spaces Association](https://internationaldataspaces.org/why/data-spaces). An industrial dataspaces focuses on the following key principles:
 
 * **Data sovereignty**: It ensures that data providers retain control over their data, including who can access it and under what conditions.
 * **Interoperability**: It uses standardized protocols and governance models to enable seamless data sharing across various platforms and industries.
@@ -94,7 +94,7 @@ The two EDC Connectors *provider* and *consumer* automatically deployed are prov
 
 ### Trigger an automatic digital contract negotiation through the dataspace protocol and transfer a PCF
 
-The EDC Connector supports an automated EDC digital contract negotiation where the entire workflow is handled automatically. To trigger this automatic contract negotiation, followed by the transfer of a PCF from the AAS submodel for which you copied the ID in the previous step, complete the following steps:
+The EDC Connector supports an automated EDC digital contract negotiation where the entire workflow is handled automatically in accordance with the [Dataspace Protocol](https://internationaldataspaces.org/offers/dataspace-protocol). To trigger this automatic contract negotiation, followed by the transfer of a PCF from the AAS submodel for which you copied the ID in the previous step, complete the following steps:
 
 1. In the Azure portal, navigate to the overview page of your **EDC provider** instance. Copy the **Application URL** displayed.
 

articles/network-watcher/packet-capture-manage.md

@@ -1,19 +1,19 @@
 ---
-title: Manage packet captures for VMs
+title: Manage packet captures
 titleSuffix: Azure Network Watcher
 description: Learn how to start, stop, download, and delete Azure virtual machines packet captures with the packet capture feature of Network Watcher.
 author: halkazwini
 ms.author: halkazwini
 ms.service: azure-network-watcher
 ms.topic: how-to
-ms.date: 01/31/2025
+ms.date: 02/07/2025
 
 #CustomerIntent: As an administrator, I want to capture IP packets to and from a virtual machine (VM) so I can review and analyze the data to help diagnose and solve network problems.
 ---
 
-# Manage packet captures with Azure Network Watcher
+# Start, stop, download, and delete packet captures with Azure Network Watcher
 
-In this article, you learn how to use the Azure Network Watcher [packet capture](packet-capture-overview.md) feature to remotely configure, start, stop, download, and delete virtual machine packet captures.
+In this article, you learn how to use the Azure Network Watcher [packet capture](packet-capture-overview.md) feature to remotely configure, start, stop, download, and delete packet captures.
 
 ## Prerequisites
 
@@ -298,9 +298,9 @@ The following example is the output from the `az network watcher packet-capture
 
 ## Download a packet capture
 
-# [**Portal**](#tab/portal)
+After your packet capture session completes, the resulting capture file is saved to Azure Storage, a local file on the target virtual machine, or both. The storage destination for the packet capture is specified during its creation. For more information, see [Start a packet capture](#start-a-packet-capture) section.
 
-After concluding your packet capture session, the resulting capture file is saved to Azure storage, a local file on the target virtual machine or both. The storage destination for the packet capture is specified during its creation. For more information, see [Start a packet capture](#start-a-packet-capture) section.
+# [**Portal**](#tab/portal)
 
 To download a packet capture file saved to Azure storage, follow these steps:
 
@@ -312,19 +312,14 @@ To download a packet capture file saved to Azure storage, follow these steps:
 
 1. In the blob page, select **Download**.
 
-> [!NOTE]
-> You can also download capture files from the storage account container using the Azure portal or Storage Explorer<sup>1</sup> at the following path: 
-> ```
-> https://{storageAccountName}.blob.core.windows.net/network-watcher-logs/subscriptions/{subscriptionId}/resourcegroups/{storageAccountResourceGroup}/providers/microsoft.compute/virtualmachines/{virtualMachineName}/{year}/{month}/{day}/packetcapture_{UTCcreationTime}.cap
-> ```
-> <sup>1</sup> Storage Explorer is a standalone app that you can conveniently use to access and work with Azure Storage data. For more information, see [Get started with Storage Explorer](../vs-azure-tools-storage-manage-with-storage-explorer.md).
 
-To download a packet capture file saved to the virtual machine (VM), connect to the VM and download the file from the local path specified during the packet capture creation. 
+You can also download capture files by directly going to the storage account container at the following path: 
+```
+https://{storageAccountName}.blob.core.windows.net/network-watcher-logs/subscriptions/{subscriptionId}/resourcegroups/{storageAccountResourceGroup}/providers/microsoft.compute/virtualmachines/{virtualMachineName}/{year}/{month}/{day}/packetcapture_{UTCcreationTime}.cap
+```
 
 # [**PowerShell**](#tab/powershell)
 
-After concluding your packet capture session, the resulting capture file is saved to Azure storage, a local file on the target virtual machine or both. The storage destination for the packet capture is specified during its creation. For more information, see [Start a packet capture](#start-a-packet-capture) section.
-
 If a storage account is specified, capture files are saved to the storage account at the following path:
 
 ```url
@@ -338,13 +333,8 @@ To download a packet capture from Azure storage to the local disk, use [Get-AzSt
 Get-AzStorageBlobContent -Container 'network-watcher-logs' -Blob '/subscriptions/aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e/resourcegroups/myresourcegroup/providers/microsoft.compute/virtualmachines/myvm/2024/01/25/packetcapture_22_44_54_342.cap' -Destination 'C:\Capture\myVM_1.cap'
 ```
 
-> [!NOTE]
-> You can also download the capture file from the storage account container using the Azure Storage Explorer. Storage Explorer is a standalone app that you can conveniently use to access and work with Azure Storage data. For more information, see [Get started with Storage Explorer](../vs-azure-tools-storage-manage-with-storage-explorer.md).
-
 # [**Azure CLI**](#tab/cli)
 
-After concluding your packet capture session, the resulting capture file is saved to Azure storage, a local file on the target virtual machine or both. The storage destination for the packet capture is specified during its creation. For more information, see [Start a packet capture](#start-a-packet-capture) section.
-
 If a storage account is specified, capture files are saved to the storage account at the following path:
 
 ```url
@@ -358,10 +348,15 @@ To download a packet capture from Azure storage to the local disk, use [az stora
 az storage blob download --container-name 'network-watcher-logs' --blob-url '/subscriptions/aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e/resourcegroups/myresourcegroup/providers/microsoft.compute/virtualmachines/myvm/2024/01/25/packetcapture_22_44_54_342.cap' --file 'C:\Capture\myVM_1.cap'
 ```
 
+---
+
 > [!NOTE]
-> You can also download the capture file from the storage account container using the Azure Storage Explorer. Storage Explorer is a standalone app that you can conveniently use to access and work with Azure Storage data. For more information, see [Get started with Storage Explorer](../vs-azure-tools-storage-manage-with-storage-explorer.md).
+> You can use Azure Storage Explorer to download capture files from the storage account container. Storage Explorer is a standalone app that you can conveniently use to access and work with Azure Storage data. For more information, see [Get started with Storage Explorer](../vs-azure-tools-storage-manage-with-storage-explorer.md).
 
----
+> [!IMPORTANT]
+> During the packet capture session, the capture file might not immediately appear in the storage account container because it's initially saved to a temporary location. The file is transferred to its final location after the capture session is completed.
+
+To download a packet capture file saved to the virtual machine (VM), connect to the VM and download the file from the local path specified during the packet capture creation. 
 
 ## Delete a packet capture
 

articles/network-watcher/traffic-analytics-schema.md

@@ -6,7 +6,7 @@ author: halkazwini
 ms.author: halkazwini
 ms.service: azure-network-watcher
 ms.topic: concept-article
-ms.date: 02/06/2025
+ms.date: 02/07/2025
 
 #CustomerIntent: As a administrator, I want learn about traffic analytics schema so I can easily use the queries and understand their output.
 ---
@@ -333,6 +333,9 @@ List of threat types:
     - `UnknownPrivate`: One of the IP addresses belong to an Azure virtual network, while the other IP address belongs to the private IP range defined in RFC 1918 and couldn't be mapped by traffic analytics to a customer owned site or Azure virtual network.
     - `Unknown`: Unable to map either of the IP addresses in the flow with the customer topology in Azure and on-premises (site).
 
+    > [!NOTE]
+    > A subscription is visible to traffic analytics in a Log Analytics workspace if it contains a flow log configured to that workspace.
+
 ## Related content
 
 - To learn more about traffic analytics, see [Traffic analytics overview](traffic-analytics.md).

articles/operator-nexus/troubleshoot-bare-metal-machine-provisioning.md

@@ -5,7 +5,7 @@ ms.service: azure-operator-nexus
 ms.custom: troubleshooting
 ms.topic: troubleshooting
 ms.date: 07/19/2024
-author: bpinto
+author: bartpinto
 ms.author: bpinto
 ---
 
@@ -234,7 +234,7 @@ This condition typically shows the BMM at the bootloader stage on the console an
 
 To reset the NVRAM, use the following sequence in the BMC UI:
 
-1. Select **Maintenance** > **Diagnostics** > **Reset iDrac to Factory Defaults**.
+1. Select **Maintenance** > **Diagnostics** > **Reset iDRAC to Factory Defaults**.
 
 1. Select **Discard All Settings, but preserve user and network settings**, and then select **Apply and reboot**.
 

articles/virtual-wan/route-maps-about.md

@@ -54,7 +54,7 @@ Before using Route-maps, take into consideration the following limitations:
 
 * During Preview, hubs that are using Route-maps must be deployed in their own virtual WANs.
 * When using Route-maps to summarize a set of routes, the hub router strips the *BGP Community* and *AS-PATH* attributes from those routes. This applies to both inbound and outbound routes.
-* When using Route-maps, [do not use private ASNs for AS prpending](/expressroute/expressroute-optimize-routing.md#Solution:useASPATHprepending).
+* When using Route-maps, [do not use private ASNs for AS prpending](../expressroute/expressroute-optimize-routing.md).
 * When using Route-maps, do not use ASN's reserved by Azure for AS prepending:
   * Public ASNs: 8074, 8075, 12076
   * Private ASNs: 65515, 65517, 65518, 65519, 65520