Merge branch 'MicrosoftDocs:main' into main

Author: ms-snarang

articles/active-directory-b2c/service-limits.md

@@ -196,7 +196,7 @@ As a protection for our customers, Microsoft places some restrictions on telepho
 | 233 |	Ghana|	10	| 30 |
 | 234 | Nigeria | 20 | 100 |
 | 236 |	Central African Republic  |	10	| 30 |
-| 238 | Cape Verde | 10 | 30 |
+| 238 | Cabo Verde | 10 | 30 |
 | 249 |  Sudan | 10  |  30  |
 | 251 |	Ethiopia  |	10	| 30 |
 | 252 |  Somalia   | 10  |  30  |  

articles/automation/delete-run-as-account.md

@@ -3,7 +3,7 @@ title: Delete an Azure Automation Run As account
 description: This article tells how to delete a Run As account with PowerShell or from the Azure portal.
 services: automation
 ms.subservice: process-automation
-ms.date: 09/13/2024
+ms.date: 04/08/2025
 ms.topic: how-to
 ms.service: azure-automation
 ---
@@ -19,30 +19,15 @@ Run As accounts in Azure Automation provide authentication for managing resource
 
 To configure or update or delete a Run As account and a Classic Run As accounts, you must either be:
 
-- An owner of the Microsoft Entra Application for the Run As Account
+- An owner of the Microsoft Entra Application for the Run As Account.
 
     (or)
 
-- A member in one of the following Microsoft Entra roles
+- A member in one of the following Microsoft Entra roles.
     - Application Administrator
     - Cloud Application Administrator
 
-## Delete a Run As or Classic Run As account
-
-1. In the Azure portal, open the Automation account.
-
-2. In the left pane, select **Run As Accounts** in the account settings section.
-
-3. On the Run As Accounts properties page, select either the Run As account or Classic Run As account that you want to delete.
-
-4. On the Properties pane for the selected account, click **Delete**.
-
-   ![Delete Run As account](media/delete-run-as-account/automation-account-delete-run-as.png)
-
-5. While the account is being deleted, you can track the progress under **Notifications** from the menu. Run As accounts can't be restored after deletion.
-
-> [!NOTE]
-> We recommend that you delete the Run As account from Automation account portal. Alternatively, you can delete the Service principal from the **Microsoft Entra ID** portal > **App registrations** > search and select your Automation account name and in the **Overview** page, select **Delete**.
+You can delete the Service principal from the **Microsoft Entra ID** portal > **App registrations** > search and select your Automation account name and in the **Overview** page, select **Delete**.
 
 ## Next steps
 

articles/azure-vmware/index.yml

@@ -21,9 +21,9 @@ highlightedContent:
     - title: What's Azure VMware Solution? 
       itemType: overview
       url: /azure/azure-vmware/introduction
-    - title: Architecture and design 
-      itemType: get-started
-      url: architecture-network-design-considerations.md
+    - title: What's Azure VMware Solution in an Azure Virtual Network (Public preview)
+      itemType: overview
+      url: /azure/azure-vmware/native-introduction
     - title: Networking
       itemType: how-to-guide
       url: tutorial-expressroute-global-reach-private-cloud.md

articles/azure-vmware/install-vmware-hcx.md

@@ -1,13 +1,13 @@
 ---
-title: Install and activate VMware HCX in Azure VMware Solution
+title: Install VMware HCX in Azure VMware Solution
 description: Install VMware HCX in your Azure VMware Solution private cloud.
 ms.topic: how-to
 ms.service: azure-vmware
 ms.custom: engagement-fy23
 ms.date: 02/26/2025
 ---
 
-# Install and activate VMware HCX in Azure VMware Solution
+# Install VMware HCX in Azure VMware Solution
 
 [VMware HCX](https://techdocs.broadcom.com/us/en/vmware-cis/hcx/vmware-hcx/4-10.html) is an application mobility platform designed for simplifying application migration, rebalancing workloads, and optimizing disaster recovery across data centers and clouds. 
 
@@ -23,7 +23,7 @@ This article also teaches you how to do the following tasks:
 * Download and deploy the VMware HCX Connector in on-premises.
 * Activate VMware HCX with a license key.
 
-After HCX is deployed, follow the recommended [Next steps](#next-steps). 
+ After deploying HCX, follow the recommended [Next steps](#next-steps).
 
 ## Prerequisite
 
@@ -36,13 +36,20 @@ After HCX is deployed, follow the recommended [Next steps](#next-steps).
 1. Select **Get started** for **HCX Workload Mobility**.
 
      :::image type="content" source="media/tutorial-vmware-hcx/add-hcx-workload-mobility.png" alt-text="Screenshot showing the Get started button for VMware HCX Workload Mobility." lightbox="media/tutorial-vmware-hcx/add-hcx-workload-mobility.png":::
+1.	If you're installing HCX add-on on Azure VMware Solution in an Azure virtual network, then follow this step:
+   
+      1. Specify a unique /24 CIDR address block for HCX uplink and management. This IP block is utilized for HCX service mesh appliances management and uplink interfaces.
+
+      :::image type="content" source="media/native-connectivity/native-hcx-install.png" alt-text="Screenshot showing how to install HCX add-on on an Azure VMware Solution in an Azure virtual network." lightbox="media/native-connectivity/native-hcx-install.png":::
 
 1. Select the **I agree with terms and conditions** checkbox and then select **Install**.
 
     Once installed, you should see the HCX Manager IP and the HCX keys required for the HCX on-premises connector site pairing on the **Migration using HCX** tab.
+    >[!NOTE]
+    > When initiating a site pair where source is Azure VMware Solution in an Azure Virtual Network, you can use IP address. If you need to use FQDN, raise a support case.
 
     > [!IMPORTANT]
-    > If you don't see the HCX key after installing, click the **ADD** button to generate the key which you can then use for site pairing.
+    > If you don't see the HCX key after installing, select the **ADD** button to generate the key which you can then use for site pairing.
 
    :::image type="content" source="media/tutorial-vmware-hcx/configure-hcx-appliance-for-migration-using-hcx-tab.png" alt-text="Screenshot showing the Migration using VMware HCX tab under Connectivity." lightbox="media/tutorial-vmware-hcx/configure-hcx-appliance-for-migration-using-hcx-tab.png":::
 
@@ -82,7 +89,9 @@ HCX offers various [services](https://techdocs.broadcom.com/us/en/vmware-cis/hcx
 - Downgrading from HCX Enterprise Edition to HCX Advanced is possible without redeploying. 
 
     1. Verify that you reverted to an HCX Advanced configuration state and you aren't using the Enterprise features. 
-    1. If you plan to downgrade, verify that no scheduled migrations, [Enterprise services](https://techdocs.broadcom.com/us/en/vmware-cis/hcx/vmware-hcx/4-10/vmware-hcx-user-guide-4-10/vmware-hcx-services.html) like RAV and HCX MON, etc. are in use. Open a [support request](https://rc.portal.azure.com/#create/Microsoft.Support) to request downgrade. 
+
+    1. If you plan to downgrade, verify that no scheduled migrations, [Enterprise services](https://techdocs.broadcom.com/us/en/vmware-cis/hcx/vmware-hcx/4-9/vmware-hcx-user-guide-4-9/vmware-hcx-services.html) like RAV or HCX MON, etc. are active. Open a [support request](https://rc.portal.azure.com/#create/Microsoft.Support) to request downgrade. 
+
 
 ## Download and deploy the VMware HCX Connector on-premises 
 
@@ -108,7 +117,7 @@ Use the following steps to download the VMware HCX Connector OVA file, and then
 
 1. Verify and then select **Finish** to deploy the VMware HCX Connector OVA. 
    >[!IMPORTANT] 
-   >You will need to turn on the virtual appliance manually.  After powering on, wait 10-15 minutes before proceeding to the next step. 
+   >You need to turn on the virtual appliance manually.  After powering on, wait 10-15 minutes before proceeding to the next step. 
 
 ## Activate VMware HCX 
 

articles/azure-vmware/introduction.md

@@ -23,13 +23,22 @@ The diagram shows the adjacency between private clouds and VNets in Azure, Azure
 
 You can deploy new or scale existing private clouds through the Azure portal or Azure CLI.
 
+## Azure VMware Solution deployment types
+
+Azure VMware Solution provides two different deployment types:
+
+1. Azure VMware Solution provides VMware vSphere clusters built from dedicated bare-metal hosts deployed in Azure datacenter facilities. Microsoft-managed **ExpressRoute circuits** provide connectivity between VMware vSphere hosts and native Azure resources deployed in Virtual Networks.
+
+2. [Azure VMware Solution in a Virtual Network](native-introduction.md) (Public Preview) provides VMware vSphere clusters built from dedicated Azure bare-metal hosts. Azure VMware Solution in an **Azure Virtual Network** features an updated network architecture whereby VMware vSphere hosts are directly attached to Azure Virtual Networks. This offering in only supported on the AV64 SKU. 
+
+
 ## Azure VMware Solution private cloud extension with AV64 node size
 
-The AV64 is a new Azure VMware Solution host SKU, which is available to expand (not to create) the Azure VMware Solution private cloud built with the existing AV36, AV36P, or AV52 SKU. Use the [Microsoft documentation](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=azure-vmware) to check for availability of the AV64 SKU in the region. 
+The AV64 is an Azure VMware Solution host SKU, which is available to expand the Azure VMware Solution private cloud built with the existing AV36, AV36P, or AV52 SKU. If you want to deploy AV64 directly, refer to [Azure VMWare Solution in an Azure Virtual Network](native-introduction.md). Use the [Microsoft documentation](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=azure-vmware) to check for availability of the AV64 SKU in the region. 
 
 :::image type="content" source="media/introduction/av64-mixed-sku-topology.png" alt-text="Diagram showing Azure VMware Solution private cloud with AV64 SKU in mixed SKU configuration." border="false" lightbox="media/introduction/av64-mixed-sku-topology.png":::
 
-### Prerequisite for AV64 usage 
+### Prerequisite for AV64 expansion on AV36, AV36P, and AV52 
 
 See the following prerequisites for AV64 cluster deployment.