Merge pull request #301282 from MicrosoftDocs/main

Merged by Learn.Build PR Management system

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

articles/azure-functions/functions-create-your-first-function-visual-studio.md

@@ -79,6 +79,7 @@ Your function definition should now look like the following code:
 [Function("HttpExample")]
 public IActionResult Run([HttpTrigger(AuthorizationLevel.Anonymous, "get", "post")] HttpRequest req)
 {
+    _logger. LogInformation("C# HTTP trigger function processed a request.");
     return new OkObjectResult("Hello, functions");
 }
 ```

articles/azure-maps/geocoding-coverage.md

@@ -4,7 +4,7 @@ titleSuffix: Microsoft Azure Maps
 description: See which regions Azure Maps Search covers. Geocoding categories include address points, house numbers, street level, city level, and points of interest.
 author: farazgis
 ms.author: fsiddiqui
-ms.date: 11/30/2021
+ms.date: 06/12/2025
 ms.topic: reference
 ms.service: azure-maps
 ms.subservice: search
@@ -146,7 +146,7 @@ The ability to geocode in a country/region is dependent upon the road data cover
 | Vietnam                                             |        ✓        |                |       ✓     |      ✓     |       ✓        |
 | Wallis & Futuna                                     |                 |                |              |      ✓     |       ✓        |
 
-<sup>1</sup> Coverage is dependent on enabling data processing in South Korea. For more information, see [Enable South Korea addresses in Azure Maps](how-to-manage-consent.md).
+<sup>1</sup> Coverage is dependent on enabling data processing in South Korea. For more information, see [Configure global data processing](how-to-manage-consent.md).
 
 ## Europe
 

articles/azure-maps/routing-coverage.md

@@ -60,6 +60,7 @@ Here's a high-level summary of the data-flow steps for copying with a self-hoste
   - Windows Server 2016
   - Windows Server 2019
   - Windows Server 2022
+  - Windows Server 2025
 
 Installation of the self-hosted integration runtime on a domain controller isn't supported.
 

articles/azure-maps/supported-languages.md

@@ -7,7 +7,7 @@ author: alkohli
 ms.service: azure-stack-edge
 ms.custom: linux-related-content
 ms.topic: how-to
-ms.date: 05/01/2023
+ms.date: 06/12/2025
 ms.author: alkohli
 # Customer intent: As an IT admin, I need to understand how to configure compute on an Azure Stack Edge Pro GPU device so that I can use it to transform data before I send it to Azure.
 ---
@@ -19,7 +19,7 @@ ms.author: alkohli
 You can create and manage virtual machines (VMs) on an Azure Stack Edge Pro GPU device by using the Azure portal, templates, and Azure PowerShell cmdlets, and via the Azure CLI or Python scripts. This article describes how to create and manage a VM on your Azure Stack Edge Pro GPU device by using the Azure portal.
 
 > [!IMPORTANT] 
-> You will need to enable multifactor authentication for the user who manages the VMs and images that are deployed on your device from the cloud. The cloud operations will fail if the user doesn't have multifactor authentication enabled. For steps to enable multifactor authentication, see [Enable Microsoft Entra multifactor authentication](/training/modules/secure-aad-users-with-mfa/4-exercise-mfa).
+> You'll need to enable multifactor authentication for the user who manages the VMs and images that are deployed on your device from the cloud. The cloud operations fail if the user doesn't have multifactor authentication enabled. For steps to enable multifactor authentication, see [Enable Microsoft Entra multifactor authentication](/training/modules/secure-aad-users-with-mfa/4-exercise-mfa).
 
 ## VM deployment workflow
 
@@ -45,16 +45,16 @@ The high-level summary of the deployment workflow is as follows:
 
 Before you begin to create and manage VMs on your device via the Azure portal, make sure that:
 
-1. You've completed the network settings on your Azure Stack Edge Pro GPU device as described in [Step 1: Configure an Azure Stack Edge Pro GPU device](./azure-stack-edge-gpu-connect-resource-manager.md#step-1-configure-azure-stack-edge-device).
+1. You complete the network settings on your Azure Stack Edge Pro GPU device as described in [Step 1: Configure an Azure Stack Edge Pro GPU device](./azure-stack-edge-gpu-connect-resource-manager.md#step-1-configure-azure-stack-edge-device).
 
-    1. You've enabled a network interface for compute. This network interface IP is used to create a virtual switch for the VM deployment. In the local UI of your device, go to **Compute**. Select the network interface that you'll use to create a virtual switch.
+    1. You enable a network interface for compute. This network interface IP is used to create a virtual switch for the VM deployment. In the local UI of your device, go to **Compute**. Select the network interface that you use to create a virtual switch.
 
         > [!IMPORTANT] 
         > You can configure only one port for compute.
 
     1. Enable compute on the network interface. Azure Stack Edge Pro GPU creates and manages a virtual switch corresponding to that network interface.
 
-1. You have access to a Windows or Linux VHD that you'll use to create the VM image for the VM you intend to create.
+1. You have access to a Windows or Linux VHD that you use to create the VM image for the VM you intend to create.
 
 ## Deploy a VM
 
@@ -72,11 +72,11 @@ Follow these steps to create a VM on your Azure Stack Edge Pro GPU device.
 
     ![Screenshot showing the Overview pane of an Azure Stack Edge device, with the Virtual machines option, under Edge Services, highlighted.](media/azure-stack-edge-gpu-deploy-virtual-machine-portal/add-virtual-machine-image-1.png)
 
-1. On the **Overview** page. Select **Enable** to enable virtual machine cloud management. 
+1. On the **Overview** page, select **Enable** to enable virtual machine cloud management. 
 
     ![Screenshot of the Overview pane in Virtual Machines view for an Azure Stack Edge device. The Enable button, to enable VM cloud management, is highlighted.](media/azure-stack-edge-gpu-deploy-virtual-machine-portal/add-virtual-machine-image-2.png)
 
-1. The first step is to add a VM image. You've already uploaded a VHD into the storage account in the earlier step. You'll use this VHD to create a VM image.
+1. The first step is to add a VM image. You already uploaded a VHD into the storage account in the earlier step. Use this VHD to create a VM image.
 
     Select **+ Add image** to download the VHD from the storage account and add it to the device. The download process takes several minutes depending on the size of the VHD and the internet bandwidth available for the download. 
 
@@ -90,13 +90,13 @@ Follow these steps to create a VM on your Azure Stack Edge Pro GPU device.
     |Download to    | Automatically set to the current device where you're deploying the VM.        |
     |Edge resource group  |Select the resource group to add the image to. |
     |Save image as      | The name for the VM image that you're creating from the VHD you uploaded to the storage account.        |
-    |OS type     |Choose from Windows or Linux as the operating system of the VHD you'll use to create the VM image.         |
-    |VM generation    |Choose Gen 1 or Gen 2 as the generation of the image you'll use to create the VM. For Gen 2 VMs, secure boot is enabled by default.        |
+    |OS type     |Choose from Windows or Linux as the operating system of the VHD you use to create the VM image.         |
+    |VM generation    |Choose Gen 1 or Gen 2 as the generation of the image you use to create the VM. For Gen 2 VMs, secure boot is enabled by default.        |
 
 
     ![Screenshot showing the Add image page for a virtual machine with the Add button highlighted.](media/azure-stack-edge-gpu-deploy-virtual-machine-portal/add-virtual-machine-image-6.png)
 
-1. The VHD is downloaded, and the VM image is created. Image creation takes several minutes to complete. You'll see a notification for the successful completion of the VM image.<!--There's a fleeting notification that image creation is in progress, but I didn't see any notification that image creation completed successfully.-->
+1. The VHD is downloaded, and the VM image is created. Image creation takes several minutes to complete. You see a notification for the successful completion of the VM image.<!--There's a fleeting notification that image creation is in progress, but I didn't see any notification that image creation completed successfully.-->
 
     ![Screenshot of the Overview for Virtual machines on an Azure Stack Edge device. On the Images pane, a newly created VM is highlighted.](media/azure-stack-edge-gpu-deploy-virtual-machine-portal/add-virtual-machine-image-8.png)
 
@@ -140,7 +140,7 @@ Follow these steps to create a VM after you've created a VM image.
 
     Select **Next: Disks**.
 
-1. On the **Disks** tab, you'll attach disks to your VM. 
+1. On the **Disks** tab, attach disks to your VM. 
 
     1. You can choose to **Create and attach a new disk** or **Attach an existing disk**.
 
@@ -152,7 +152,7 @@ Follow these steps to create a VM after you've created a VM image.
 
     1. Repeat the preceding process to add more disks. After the disks are created, they show up on the **Disks** tab. Select **Next: Networking**.
 
-1. On the **Networking** tab, you'll configure the network connectivity for your VM.
+1. On the **Networking** tab, configure the network connectivity for your VM.
 
     |Parameter  |Description |
     |---------|---------|
@@ -198,7 +198,7 @@ Follow these steps to create a VM after you've created a VM image.
 
     ![Screenshot that shows the Details tab on the Overview pane for a virtual machine in Azure Stack Edge. The Overview label and the IP Address in Networking are highlighted.](media/azure-stack-edge-gpu-deploy-virtual-machine-portal/add-virtual-machine-details-1.png)
 
-    You'll use the IP address for the network interface to connect to the VM.
+    Use the IP address for the network interface to connect to the VM.
 
 ## Connect to a VM
 

articles/data-factory/create-self-hosted-integration-runtime.md

@@ -6,7 +6,7 @@ author: alkohli
 
 ms.service: azure-stack-edge
 ms.topic: how-to
-ms.date: 06/25/2021
+ms.date: 06/12/2025
 ms.author: alkohli
 #Customer intent: As an IT admin, I need to be able to quickly deploy new Windows virtual machines on my Azure Stack Edge Pro GPU device, and I want to use an ISO image for OS installation.
 ---
@@ -45,15 +45,15 @@ Before you can create a generalized Windows VHD by using an ISO image, make sure
 
 - You have access to a Windows client with Hyper-V Manager installed.
 
-- You have access to an Azure blob storage account to store your VHD after it is prepared.
+- You have access to an Azure blob storage account to store your VHD after it's prepared.
 
 ## Prepare source VM using an ISO
 
 When you use an ISO image to install the operating system on your VM image, you start by creating a blank, fixed-size VHD in Hyper-V Manager. You then use that VHD to create a virtual machine. Then you attach the ISO image to the VM.
 
 #### Create new VHD in Hyper-V Manager
 
-Your first step is to create a new Generation 1 VHD in Hyper-V Manager, which will be the source VHD for a new virtual machine.
+Your first step is to create a new Generation 1 VHD in Hyper-V Manager, which is the source VHD for a new virtual machine.
 
 To create the VHD, follow these steps:
 
@@ -73,17 +73,17 @@ To create the VHD, follow these steps:
 
    ![Enter the name and location for the VHD](./media/azure-stack-edge-gpu-prepare-windows-generalized-image-iso/vhd-from-iso-04.png)
 
-4. Under **Configure Disk**, select **Create a new blank virtual hard disk**, and enter the size of disk you would like to create (generally 20 GB and above for Windows Server). Then select **Next >**.
+4. Under **Configure Disk**, select **Create a new blank virtual hard disk**, and enter the size of disk you would like to create (generally 20 GB or more for Windows Server). Then select **Next >**.
 
    ![Settings for creating a new blank virtual hard disk and specifying the size](./media/azure-stack-edge-gpu-prepare-windows-generalized-image-iso/vhd-from-iso-05.png)
 
-5. Under **Summary**, review your selections, and select **Finish** to create the new VHD. The process will take five or more minutes depending on the size of the VHD created.
+5. Under **Summary**, review your selections, and select **Finish** to create the new VHD. The process takes five or more minutes depending on the size of the VHD created.
 
    ![Summary of VHD settings](./media/azure-stack-edge-gpu-prepare-windows-generalized-image-iso/vhd-from-iso-06.png)
 
 #### Create Hyper-V VM from VHD
 
-Now you'll use the VHD you just created to create a new virtual machine.
+Now use the VHD you just created to create a new virtual machine.
 
 To create your new virtual machine, follow these steps:
 
@@ -119,7 +119,7 @@ To create your new virtual machine, follow these steps:
 
 After creating the new virtual machine, follow these steps to mount your ISO image on the DVD drive of the virtual machine:
 
-1. In Hyper-V Manager, select the VM you just created, and then select **Settings**.
+1. In Hyper-V Manager, select the VM you created, and then select **Settings**.
 
    ![In Hyper-V Manager, open Settings for your virtual machine](./media/azure-stack-edge-gpu-prepare-windows-generalized-image-iso/vhd-from-iso-13.png)
 
@@ -141,7 +141,7 @@ To finish building your virtual machine, you need to start the virtual machine a
 [!INCLUDE [Connect to Hyper-V VM](../../includes/azure-stack-edge-connect-to-hyperv-vm.md)]
 
 > [!NOTE]
-> If you installed the Windows Server 2019 Standard operating system on your virtual machine, you'll need to change the **BIOS** setting to **IDE** before you [generalize the VHD](#generalize-the-vhd). 
+> If you installed the Windows Server 2019 Standard operating system on your virtual machine, you must change the **BIOS** setting to **IDE** before you [generalize the VHD](#generalize-the-vhd). 
 
 ## Generalize the VHD
 

articles/databox-online/azure-stack-edge-gpu-deploy-virtual-machine-portal.md

@@ -6,7 +6,7 @@ author: alkohli
 
 ms.service: azure-stack-edge
 ms.topic: how-to
-ms.date: 05/18/2022
+ms.date: 06/12/2025
 ms.author: alkohli
 #Customer intent: As an IT admin, I need to understand how to create and upload Azure VM images that I can use to deploy virtual machines on my Azure Stack Edge Pro GPU device.
 ---
@@ -42,18 +42,18 @@ Before you prepare a Windows VHD for use as a generalized image on an Azure Stac
 
 - You have a VHD or a VHDX containing a supported version of Windows. 
 - You have access to a Windows client with Hyper-V Manager installed. 
-- You have access to an Azure Blob storage account to store your VHD after it is prepared.
+- You have access to an Azure Blob storage account to store your VHD after it's prepared.
 
 ## Prepare source VM from Windows VHD
 
-When your VM source is a Windows VHD or VHDX, you first need to convert the Windows VHD to a fixed-size VHD. You will use the fixed-size VHD to create a new virtual machine.
+When your VM source is a Windows VHD or VHDX, you first need to convert the Windows VHD to a fixed-size VHD. You'll use the fixed-size VHD to create a new virtual machine.
 
 > [!IMPORTANT]
-> These procedures do not cover cases where the source VHD is configured with custom configurations and settings. For example, additional actions may be required to generalize a VHD containing custom firewall rules or proxy settings. For more information on these additional actions, see [Prepare a Windows VHD to upload to Azure - Azure Virtual Machines](/azure/virtual-machines/windows/prepare-for-upload-vhd-image).
+> These procedures don't cover cases where the source VHD is configured with custom configurations and settings. For example, additional actions may be required to generalize a VHD containing custom firewall rules or proxy settings. For more information on these additional actions, see [Prepare a Windows VHD to upload to Azure - Azure Virtual Machines](/azure/virtual-machines/windows/prepare-for-upload-vhd-image).
 
 #### Convert source VHD to a fixed-size VHD
 
-For your device, you'll need fixed-size VHDs to create VM images. You'll need to convert your source Windows VHD or VHDX to a fixed VHD. 
+For your device, you need fixed-size VHDs to create VM images. You must convert your source Windows VHD or VHDX to a fixed VHD. 
 
 Follow these steps:
 
@@ -93,7 +93,7 @@ Follow these steps:
     Convert-VHD -Path <source VHD path> -DestinationPath <destination-path.vhd> -VHDType Fixed 
     ```
 -->
-You'll use this fixed-size VHD for all the subsequent steps in this article.
+Use this fixed-size VHD for all the subsequent steps in this article.
 
 #### Create Hyper-V VM from the fixed-size VHD
 

articles/databox-online/azure-stack-edge-gpu-prepare-windows-generalized-image-iso.md

@@ -10,7 +10,7 @@ metadata:
   ms.topic: landing-page
   author: alkohli
   ms.author: alkohli
-  ms.date: 02/09/2022
+  ms.date: 06/10/2025
 
 # linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | whats-new
 
@@ -133,5 +133,5 @@ landingContent:
             url: azure-stack-edge-gpu-connect-powershell-interface.md#debug-kubernetes-issues-related-to-iot-edge            
           - text: Return Azure Stack Edge Pro GPU
             url: azure-stack-edge-return-device.md
-          - text: Open Support ticket
+          - text: Open a Support ticket
             url: azure-stack-edge-contact-microsoft-support.md

articles/databox-online/azure-stack-edge-gpu-prepare-windows-vhd-generalized-image.md

@@ -73,11 +73,11 @@ Follow these steps to set up a dev tunnel and connect to your dev box using VS C
 
 - Why do I need to sign-in to the Dev Box before enabling the tunnel?
 
-   This step is required to establish a user session for setting up the tunnel. After the initial sign-in, you can just disconnect from the Dev Box. Then you can enable or connect 
+   This step is required to establish a user session for setting up the tunnel. After the initial sign-in, you can just disconnect from the Dev Box. Then you can enable or connect to the tunnel without logging in again, unless the Dev Box is shut down or restarted. 
 
 - Why can't I connect to the Dev Box even if the tunnel is enabled?
 
-   Refresh the Dev Box extension explorer view with the button in the top right corner to check the latest status of the tunnel. If the tunnel is enabled, but you still can't connect, try disabling the tunnel, signing in to the Dev Box, and then re-enabling the tunnel.nnect, try disabling the tunnel, logging into the Dev Box, and then re-enabling the tunnel.
+   Refresh the Dev Box extension explorer view with the button in the top right corner to check the latest status of the tunnel. If the tunnel is enabled, but you still can't connect, try disabling the tunnel, signing in to the Dev Box, and then re-enabling the tunnel.
 
 ## Related content
 - [Configure Conditional Access Policies for Dev Tunnels](how-to-conditional-access-dev-tunnels-service.md)