Merge pull request #298686 from MicrosoftDocs/main

PMEds28 · web-flow · commit ed596c941865 · 2025-04-23T12:11:32.000+01:00
Publish to live, Wednesday 4AM PST, 4/23
diff --git a/articles/app-service/overview-private-endpoint.md b/articles/app-service/overview-private-endpoint.md
@@ -4,7 +4,7 @@ description: Learn how to connect privately to Azure App Service apps using a pr
 author: madsd
 ms.author: madsd
 ms.topic: overview
-ms.date: 01/31/2025
+ms.date: 04/23/2025
 ms.custom: msangapu
 ms.assetid: 2dceac28-1ba6-4904-a15d-9e91d5ee162c
 
@@ -77,7 +77,7 @@ For example, the name resolution is:
 | `clustername.azurewebsites.windows.net` | `CNAME` | `cloudservicename.cloudapp.net` | |
 | `cloudservicename.cloudapp.net` | `A` | `192.0.2.13` | <--This public IP isn't your private endpoint. You receive a 403 error. |
 
-You must set up a private DNS server or an Azure DNS private zone. For tests, you can modify the host entry of your test machine. The DNS zone that you need to create is: `privatelink.azurewebsites.net`. Register the record for your app with an `A` record and the private endpoint IP.
+You must set up a private DNS server or an Azure DNS private zone. For tests, you can modify the host entry of your test machine. The DNS zone that you need to create is: `privatelink.azurewebsites.net`. Register the record for your app with an `A` record and the private endpoint IP. With [Azure Private DNS Zone Groups](../private-link/private-endpoint-dns-integration.md#private-dns-zone-group), the DNS records are automatically added to the Private DNS zone.
 
 For example, the name resolution is:
 
@@ -88,9 +88,15 @@ For example, the name resolution is:
 
 When you set up this DNS configuration, you can reach your app privately with the default name `mywebapp.azurewebsites.net`. You must use this name, because the default certificate is issued for `*.azurewebsites.net`.
 
-If you need to use a custom DNS name, add the custom name in your app. You must validate the custom name like any custom name, by using public DNS resolution. For more information, see [custom DNS validation](./app-service-web-tutorial-custom-domain.md).
+### Custom domain name
 
-For the Kudu console, or Kudu REST API (for deployment with Azure DevOps Services self-hosted agents, for example) you must create two records pointing to the private endpoint IP in your Azure DNS private zone or your custom DNS server. The first is for your app and the second is for the SCM (source control management) of your app.
+If you need to use a custom domain name, add the custom name in your app. You must validate the custom name like any custom name, by using public DNS resolution. For more information, see [custom DNS validation](./app-service-web-tutorial-custom-domain.md).
+
+In your custom DNS zone, you need to update the DNS record to point to the private endpoint. If your app is already configured with DNS resolution for the default host name, the preferred way is to add a `CNAME` record for the custom domain pointing to `mywebapp.azurewebsites.net`. If you only want the custom domain name to resolve to the private endpoint, you can add an `A` record with the private endpoint IP directly.
+
+### Kudu/scm endpoint
+
+For the Kudu console, or Kudu REST API (for deployment with Azure DevOps Services self-hosted agents, for example) you must create a second record pointing to the private endpoint IP in your Azure DNS private zone or your custom DNS server. The first is for your app and the second is for the SCM (source control management) of your app. With Azure Private DNS Zone groups, the scm endpoint is automatically added.
 
 | Name | Type | Value |
 |-----|-----|-----|
@@ -131,5 +137,5 @@ For up-to-date information about limitations, see [this documentation](../privat
 - [Quickstart: Create a private endpoint by using the Azure CLI](../private-link/create-private-endpoint-cli.md)
 - [Quickstart: Create a private endpoint by using Azure PowerShell](../private-link/create-private-endpoint-powershell.md)
 - [Quickstart: Create a private endpoint by using an ARM template](../private-link/create-private-endpoint-template.md)
-- [Quickstart template for connecting a front-end app to a secured back-end app with virtual network integration and a private endpoint](https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.web/webapp-privateendpoint-vnet-injection)
-- [Create two web apps connected securely with a private endpoint and virtual network integration (Terraform)](./scripts/terraform-secure-backend-frontend.md)
+- [Quickstart: Template for connecting a front-end app to a secured back-end app with virtual network integration and a private endpoint](https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.web/webapp-privateendpoint-vnet-injection)
+- [Script: Create two web apps connected securely with a private endpoint and virtual network integration (Terraform)](./scripts/terraform-secure-backend-frontend.md)
diff --git a/articles/migrate/prepare-for-migration.md b/articles/migrate/prepare-for-migration.md
@@ -6,7 +6,7 @@ ms.author: sunishvohra
 ms.manager: vijain
 ms.service: azure-migrate
 ms.topic: how-to
-ms.date: 12/04/2024
+ms.date: 04/17/2025
 ms.custom: engagement-fy25
 ---
 
@@ -108,12 +108,14 @@ Configure this setting manually as follows:
 
 Azure Migrate completes these actions automatically for these versions
 
-- Red Hat Enterprise Linux  9.x, 8.x, 7.9, 7.8, 7.7, 7.6, 7.5, 7.4, 7.3, 7.2, 7.1, 7.0, 6.x (Azure Linux VM agent is also installed automatically during migration)
+- Red Hat Enterprise Linux  9.5, 9.x, 8.x, 7.9, 7.8, 7.7, 7.6, 7.5, 7.4, 7.3, 7.2, 7.1, 7.0, 6.x (Azure Linux VM agent is also installed automatically during migration)
 - CentOS Stream (Azure Linux VM agent is also installed automatically during migration)
 - SUSE Linux Enterprise Server 15 SP4, 15 SP3, 15 SP2, 15 SP1, 15 SP0, 12, 11 SP4, 11 SP3
 - Ubuntu 22.04, 21.04, 20.04, 19.04, 19.10, 18.04LTS, 16.04LTS, 14.04LTS (Azure Linux VM agent is also installed automatically during migration)
 - Debian 11, 10, 9, 8, 7
 - Oracle Linux 9, 8, 7.7-CI, 7.7, 6
+- Alma Linux 8.x, 9.x
+- Rocky Linux 8.x, 9.x
 
 For other versions, prepare machines as summarized in the table. 
 > [!Note]
diff --git a/articles/migrate/toc.yml b/articles/migrate/toc.yml
@@ -192,15 +192,15 @@ items:
         - name: Migrate to Azure Cloud
           href: tutorial-migrate-vmware.md
         - name: Migrate to Azure Local 
-          href: /azure-local/migrate/migration-azure-migrate-vmware-overview?toc=/azure/migrate/toc.json&bc=/azure/migrate/breadcrumb/toc.json
+          href: /azure/azure-local/migrate/migration-azure-migrate-vmware-overview?toc=/azure/migrate/toc.json&bc=/azure/migrate/breadcrumb/toc.json
     - name: Migrate Hyper-V servers 
       items:
 #       - name: Create Business case and assessment
 #         href: tutorial-assess-hyper-v.md
         - name: Migrate to Azure Cloud
           href: tutorial-migrate-hyper-v.md
         - name: Migrate to Azure Local
-          href: /azure-local/migrate/migration-azure-migrate-overview?toc=/azure/migrate/toc.json&bc=/azure/migrate/breadcrumb/toc.json
+          href: /azure/azure-local/migrate/migration-azure-migrate-overview?toc=/azure/migrate/toc.json&bc=/azure/migrate/breadcrumb/toc.json
     - name: Migrate physical servers
       items:
         - name: Create Business case and assessment
diff --git a/articles/migrate/vmware/prepare-for-agentless-migration.md b/articles/migrate/vmware/prepare-for-agentless-migration.md
@@ -5,7 +5,7 @@ author: vijain
 ms.author: vijain
 ms.topic: conceptual
 ms.service: azure-migrate
-ms.date: 10/25/2024
+ms.date: 04/17/2025
 ms.custom: vmware-scenario-422, engagement-fy23, linux-related-content
 ---
 
@@ -27,14 +27,15 @@ Azure Migrate automatically handles these configuration changes for the followin
 **Operating system versions supported for hydration**
 
 - Windows Server 2008 or later
-- Red Hat Enterprise Linux 9.x, 8.x, 7.9, 7.8, 7.7, 7.6, 7.5, 7.4, 7.3, 7.2, 7.1, 7.0, 6.x
+- Red Hat Enterprise Linux 9.5, 9.x, 8.x, 7.9, 7.8, 7.7, 7.6, 7.5, 7.4, 7.3, 7.2, 7.1, 7.0, 6.x
 - CentOS Stream
 - SUSE Linux Enterprise Server 15 SP6, 15 SP5, 15 SP4, 15 SP3, 15 SP2, 15 SP1, 15 SP0, 12, 11 SP4, 11 SP3
 - Ubuntu 22.04, 21.04, 20.04, 19.04, 19.10, 18.04LTS, 16.04LTS, 14.04LTS
 - Kali Linux (2016, 2017, 2018, 2019, 2020, 2021, 2022)
 - Debian 11, 10, 9, 8, 7
 - Oracle Linux 9, 8, 7.7-CI, 7.7, 6
-
+- Alma Linux 8.x, 9.x
+- Rocky Linux 8.x, 9.x
 You can also use this article to manually prepare the VMs for migration to Azure for operating systems versions not listed above. At a high level, these changes include:
 
 - Validate the presence of the required drivers
diff --git a/articles/site-recovery/replication-appliance-support-matrix.md b/articles/site-recovery/replication-appliance-support-matrix.md
@@ -3,7 +3,7 @@ title: Support requirements for Azure Site Recovery replication appliance
 description: This article describes support and requirements when deploying the replication appliance for VMware disaster recovery to Azure with Azure Site Recovery - Modernized
 ms.service: azure-site-recovery
 ms.topic: faq
-ms.date: 12/20/2024
+ms.date: 04/23/2025
 ms.author: ankitadutta
 author: ankitaduttaMSFT
 ---
@@ -37,7 +37,7 @@ Number of disks | 2, including the OS disk - 80 GB and a data disk - 620 GB
 
 **Component** | **Requirement**
 --- | ---
-Operating system | Windows Server 2019
+Operating system | Windows Server 2022
 Operating system locale | English (en-*)
 Windows Server roles | Don't enable these roles: <br> - Active Directory Domain Services <br>- Internet Information Services <br> - Hyper-V
 Group policies | Don't enable these group policies: <br> - Prevent access to the command prompt. <br> - Prevent access to registry editing tools. <br> - Trust logic for file attachments. <br> - Turn on Script Execution. <br> [Learn more](/previous-versions/windows/it-pro/windows-7/gg176671(v=ws.10))
