fixing more things

Author: MashaMSFT

.openpublishing.redirection.json

@@ -19210,7 +19210,7 @@
         },
         {
             "source_path": "articles/virtual-machines/windows/sql/virtual-machines-windows-sql-register-with-rp.md",
-            "redirect_url": "/azure/virtual-machines/windows/sql/sql-resource-provider-register",
+            "redirect_url": "/azure/azure-sql/virtual-machines/windows/sql-vm-resource-provider-register",
             "redirect_document_id": false
         },
         {
@@ -53519,7 +53519,7 @@
         },
         {
             "source_path": "articles/virtual-machines/windows/sql/virtual-machines-windows-sql-bulk-register-with-resource-provider.md",
-            "redirect_url": "/azure/azure-sql/virtual-machines/windows/sql-resource-provider-bulk-register",
+            "redirect_url": "/azure/azure-sql/virtual-machines/windows/sql-vm-resource-provider-bulk-register",
             "redirect_document_id": true
         },
         {
@@ -53584,7 +53584,7 @@
         },
         {
             "source_path": "articles/virtual-machines/windows/sql/virtual-machines-windows-sql-register-with-resource-provider.md",
-            "redirect_url": "/azure/azure-sql/virtual-machines/windows/sql-resource-provider-register",
+            "redirect_url": "/azure/azure-sql/virtual-machines/windows/sql-vm-resource-provider-register",
             "redirect_document_id": true
         },
         {

articles/azure-sql/virtual-machines/windows/TOC.yml

@@ -1,15 +1,15 @@
 - name: Overview
   items:
   - name: What is a SQL Server VM?
-    href: what-is-sql-on-azure-vm-iaas-overview.md
+    href: sql-server-on-azure-vm-iaas-what-is-overview.md
   - name: Doc changes
     href: doc-changes-updates-release-notes.md
 - name: Quickstarts
   items:
   - name: Create SQL VM - Portal
-    href: quickstart-create-sql-vm-portal.md
+    href: sql-vm-create-portal-quickstart.md
   - name: Create SQL VM - PowerShell
-    href: quickstart-create-sql-vm-powershell.md
+    href: sql-vm-create-powershell-quickstart.md
 - name: Concepts
   items:
   - name: Best practices
@@ -25,7 +25,7 @@
     - name: High availability options
       href: business-continuity-high-availability-disaster-recovery-hadr-overview.md
     - name: Always On availability group
-      href: manually-configure-availability-group-multiple-regions.md
+      href: availability-group-manually-configure-multiple-regions.md
     - name: Backup and restore
       href: backup-restore.md
     - name: Automated backup for SQL Server 2014
@@ -51,7 +51,7 @@
       - name: Automated Patching
         href: automated-patching.md
       - name: Configure Azure Key Vault Integration
-        href: configure-azure-key-vault-integration.md
+        href: azure-key-vault-integration-configure.md
 - name: How-to guides
   items:
   - name: Create SQL VM
@@ -64,19 +64,19 @@
     displayName: resource provider, registration
     items:
     - name: Single VM
-      href: register-with-sql-resource-provider.md
+      href: sql-vm-resource-provider-register.md
     - name: Bulk register multiple VMs
-      href: bulk-register-with-sql-resource-provider.md
+      href: sql-vm-resource-provider-bulk-register.md
   - name: Manage
     items: 
     - name: Licensing model
       displayName: ahb, ahub, payg, change, modify, update
-      href: change-licensing-model-azure-hybrid-benefit-ahb.md
+      href: licensing-model-azure-hybrid-benefit-ahb-change.md
     - name: Edition 
       displayName: change, modify, update
       href: change-sql-server-edition.md
     - name: Azure Storage for backup & restore
-      href: use-azure-storage-sql-server-backup-restore.md
+      href: azure-storage-sql-server-backup-restore-use.md
   - name: Migrate
     items:
     - name: SQL Server database to VM
@@ -88,31 +88,31 @@
     - name: Always On availability group
       items:
       - name: Azure SQL VM CLI
-        href: configure-availability-group-az-cli.md
+        href: availability-group-az-cli-configure.md
       - name: Azure portal template
-        href: configure-availability-group-azure-marketplace-template.md
+        href: availability-group-azure-marketplace-template-configure.md
       - name: Azure Quickstart templates
-        href: configure-availability-group-quickstart-template.md
+        href: availability-group-quickstart-template-configure.md
       - name: Multiple regions
-        href: manually-configure-availability-group-multiple-regions.md
+        href: availability-group-manually-configure-multiple-regions.md
       - name: Domain-independent (workgroup)
-        href: configure-clusterless-workgroup-availability-group.md
+        href: availability-group-clusterless-workgroup-configure.md
       - name: Configure manually
         items:
         - name: Prerequisites
-          href: tutorial-prerequisites-manually-configure-availability-group.md
+          href: availability-group-manually-configure-prerequisites-tutorial.md
         - name: Tutorial
-          href: tutorial-manually-configure-availability-group.md
+          href: availability-group-manually-configure-tutorial.md
         - name: Load balancer - Azure portal
-          href: configure-availability-group-load-balancer-portal.md
+          href: availability-group-load-balancer-portal-configure.md
         - name: Load balancer - Azure PowerShell
-          href: configure-availability-group-listener-powershell.md
+          href: availability-group-listener-powershell-configure.md
     - name: Failover Cluster Instance
       items:
       - name: With Storage Spaces Direct
-        href: manually-configure-failover-cluster-instance-storage-spaces-direct.md
+        href: failover-cluster-instance-storage-spaces-direct-manually-configure.md
       - name: With Premium File Share
-        href: manually-configure-failover-cluster-instance-premium-file-share.md
+        href: failover-cluster-instance-premium-file-share-manually-configure.md
 - name: Reference
   items:
   - name: Azure PowerShell

articles/azure-sql/virtual-machines/windows/availability-group-az-cli-configure.md

@@ -24,7 +24,7 @@ This article describes how to use the [Azure CLI](/cli/azure/sql/vm?view=azure-c
 To automate the setup of an Always On availability group by using the Azure CLI, you must have the following prerequisites: 
 - An [Azure subscription](https://azure.microsoft.com/free/).
 - A resource group with a domain controller. 
-- One or more domain-joined [VMs in Azure running SQL Server 2016 (or later) Enterprise edition](https://docs.microsoft.com/azure/virtual-machines/windows/sql/virtual-machines-windows-portal-sql-server-provision) in the *same availability set or different availability zones* that have been [registered with the SQL VM resource provider](sql-resource-provider-register.md).  
+- One or more domain-joined [VMs in Azure running SQL Server 2016 (or later) Enterprise edition](https://docs.microsoft.com/azure/virtual-machines/windows/sql/virtual-machines-windows-portal-sql-server-provision) in the *same availability set or different availability zones* that have been [registered with the SQL VM resource provider](sql-vm-resource-provider-register.md).  
 - The [Azure CLI](/cli/azure/install-azure-cli). 
 - Two available (not used by any entity) IP addresses. One is for the internal load balancer. The other is for the availability group listener within the same subnet as the availability group. If you're using an existing load balancer, you need only one available IP address for the availability group listener. 
 

articles/azure-sql/virtual-machines/windows/availability-group-quickstart-template-configure.md

@@ -34,7 +34,7 @@ Other parts of the availability group configuration must be done manually, such
 To automate the setup of an Always On availability group by using quickstart templates, you must have the following prerequisites: 
 - An [Azure subscription](https://azure.microsoft.com/free/).
 - A resource group with a domain controller. 
-- One or more domain-joined [VMs in Azure running SQL Server 2016 (or later) Enterprise edition](https://docs.microsoft.com/azure/virtual-machines/windows/sql/virtual-machines-windows-portal-sql-server-provision) that are in the same availability set or availability zone and that have been [registered with the SQL VM resource provider](sql-resource-provider-register.md).  
+- One or more domain-joined [VMs in Azure running SQL Server 2016 (or later) Enterprise edition](https://docs.microsoft.com/azure/virtual-machines/windows/sql/virtual-machines-windows-portal-sql-server-provision) that are in the same availability set or availability zone and that have been [registered with the SQL VM resource provider](sql-vm-resource-provider-register.md).  
 - Two available (not used by any entity) IP addresses: one for the internal load balancer, and one for the availability group listener within the same subnet as the availability group. If an existing load balancer is being used, you need only one available IP address.  
 
 ## Permissions

articles/azure-sql/virtual-machines/windows/change-sql-server-edition.md

@@ -30,7 +30,7 @@ Once the edition of SQL Server has been changed internally to the SQL Server VM,
 To do an in-place change of the edition of SQL Server, you need the following: 
 
 - An [Azure subscription](https://azure.microsoft.com/free/).
-- A [SQL Server VM on Windows](https://docs.microsoft.com/azure/virtual-machines/windows/sql/virtual-machines-windows-portal-sql-server-provision) registered with the [SQL VM resource provider](sql-resource-provider-register.md).
+- A [SQL Server VM on Windows](https://docs.microsoft.com/azure/virtual-machines/windows/sql/virtual-machines-windows-portal-sql-server-provision) registered with the [SQL VM resource provider](sql-vm-resource-provider-register.md).
 - Setup media with the **desired edition** of SQL Server. Customers who have [Software Assurance](https://www.microsoft.com/licensing/licensing-programs/software-assurance-default) can obtain their installation media from the [Volume Licensing Center](https://www.microsoft.com/Licensing/servicecenter/default.aspx). Customers who don't have Software Assurance can use the setup media from an Azure Marketplace SQL Server VM image that has their desired edition (typically located in `C:\SQLServerFull`). 
 
 
@@ -71,7 +71,7 @@ After the SQL Server edition is downgraded, modify the edition property of the S
 
 ## Change edition in portal 
 
-Once you've changed the edition of SQL Server using the installation media, and you've registered your SQL Server VM with the [SQL VM resource provider](sql-resource-provider-register.md), you can then use the Azure portal to modify the Edition property of the SQL Server VM for billing purposes. To do so, follow these steps: 
+Once you've changed the edition of SQL Server using the installation media, and you've registered your SQL Server VM with the [SQL VM resource provider](sql-vm-resource-provider-register.md), you can then use the Azure portal to modify the Edition property of the SQL Server VM for billing purposes. To do so, follow these steps: 
 
 1. Sign in to the [Azure portal](https://portal.azure.com). 
 1. Go to your SQL Server virtual machine resource. 
@@ -87,7 +87,7 @@ Once you've changed the edition of SQL Server using the installation media, and
 
 - The edition property for the SQL Server VM must match the edition of the SQL Server instance installed for all SQL Server virtual machines, including both pay-as-you-go and bring-your-own-license types of licenses.
 - If you drop your SQL Server VM resource, you will go back to the hard-coded edition setting of the image.
-- The ability to change the edition is a feature of the SQL VM resource provider. Deploying an Azure Marketplace image through the Azure portal automatically registers a SQL Server VM with the resource provider. However, customers who are self-installing SQL Server will need to manually [register their SQL Server VM](sql-resource-provider-register.md).
+- The ability to change the edition is a feature of the SQL VM resource provider. Deploying an Azure Marketplace image through the Azure portal automatically registers a SQL Server VM with the resource provider. However, customers who are self-installing SQL Server will need to manually [register their SQL Server VM](sql-vm-resource-provider-register.md).
 - Adding a SQL Server VM to an availability set requires re-creating the VM. Any VMs added to an availability set will go back to the default edition, and the edition will need to be modified again.
 
 ## Next steps

articles/azure-sql/virtual-machines/windows/doc-changes-updates-release-notes.md

@@ -31,14 +31,14 @@ Azure allows you to deploy a virtual machine (VM) with an image of SQL Server bu
 |Changes | Details |
  --- | --- |
 | **Free DR replica in Azure** | You can host a [free passive instance](business-continuity-high-availability-disaster-recovery-hadr-overview.md#free-dr-replica-in-azure) for disaster recovery in Azure for your on-premises SQL Server instance if you have [Software Assurance](https://www.microsoft.com/licensing/licensing-programs/software-assurance-default?rtc=1&activetab=software-assurance-default-pivot:primaryr3). | 
-| **Bulk resource provider registration** | You can now [bulk register](sql-resource-provider-bulk-register.md) SQL virtual machines with the resource provider. | 
+| **Bulk resource provider registration** | You can now [bulk register](sql-vm-resource-provider-register-bulk.md) SQL virtual machines with the resource provider. | 
 |**Performance Optimized Storage Configuration** | You can now [fully customize your storage configuration](storage-configuration.md#new-vms) when creating a new SQL Server VM. |
 |**Premium file share for FCI** | You can now create a failover cluster instance using a [Premium File Share](failover-cluster-instance-premium-file-share-manually-configure.md) instead of the original method of [Storage Spaces Direct](failover-cluster-instance-storage-spaces-direct-manually-configure.md). 
 | **Azure dedicated host** | You can run your SQL Server VM on an [Azure Dedicated Host](dedicated-host.md). | 
 | **Move SQL VM to different region** | Use Azure Site Recovery to [migrate your SQL Server VM from one region to another](move-sql-vm-different-region.md). |
 |  **New SQL IaaS installation modes** | It's now possible to install the SQL Server IaaS extension in [lightweight mode](sql-server-iaas-agent-extension-automate-management.md) to avoid restarting the SQL Server service.  |
 | **SQL Server edition modification** | You can now change the [edition property](change-sql-server-edition.md) for your SQL Server VM. |
-| **Changes to SQL VM resource provider** | You can [register your SQL Server VM with the SQL VM resource provider](sql-resource-provider-register.md) by using the new SQL IaaS modes. This capability includes [Windows Server 2008](sql-resource-provider-register.md#management-modes) images.|
+| **Changes to SQL VM resource provider** | You can [register your SQL Server VM with the SQL VM resource provider](sql-vm-resource-provider-register.md) by using the new SQL IaaS modes. This capability includes [Windows Server 2008](sql-vm-resource-provider-register.md#management-modes) images.|
 | **Bring-your-own-license images using Azure Hybrid Benefit** | Bring-your-own-license images deployed from Azure Marketplace can now switch their [license type to pay-as-you-go](licensing-model-azure-hybrid-benefit-ahb-change.md#remarks).| 
 | **New SQL Server VM management in Azure portal** | There's now a way to manage your SQL Server VM in the Azure portal. For more information, see [Manage SQL Server VMs in the Azure portal](manage-sql-vm-portal.md).  | 
 | **Extended support for SQL Server 2008/2008 R2** | [Extend support](sql-server-2008-extend-end-of-support.md) for SQL Server 2008 and SQL Server 2008 R2 by migrating *as is* to an Azure VM. | 
@@ -55,8 +55,8 @@ Azure allows you to deploy a virtual machine (VM) with an image of SQL Server bu
 | --- | --- |
 |  **New resource provider for a SQL Server cluster** | A new resource provider (Microsoft.SqlVirtualMachine/SqlVirtualMachineGroups) defines the metadata of the Windows failover cluster. Joining a SQL Server VM to *SqlVirtualMachineGroups* bootstraps the Windows Server Failover Cluster (WSFC) service and joins the VM to the cluster.  |
 | **Automated setup of an availability group deployment with Azure quickstart templates** |It's now possible to create the Windows failover cluster, join SQL Server VMs to it, create the listener, and configure the internal load balancer with two Azure quickstart templates. For more information, see [Use Azure quickstart templates to configure an Always On availability group for SQL Server on an Azure VM](availability-group-quickstart-template-configure.md). | 
-| **Automatic registration to the SQL VM resource provider** | SQL Server VMs deployed after this month are automatically registered with the new SQL Server resource provider. SQL Server VMs deployed before this month still need to be manually registered. For more information, see [Register a SQL Server virtual machine in Azure with the SQL VM resource provider](sql-resource-provider-register.md).|
-|**New SQL VM resource provider** |  A new resource provider (Microsoft.SqlVirtualMachine) provides better management of your SQL Server VMs. For more information on registering your VMs, see [Register a SQL Server virtual machine in Azure with the SQL VM resource provider](sql-resource-provider-register.md). |
+| **Automatic registration to the SQL VM resource provider** | SQL Server VMs deployed after this month are automatically registered with the new SQL Server resource provider. SQL Server VMs deployed before this month still need to be manually registered. For more information, see [Register a SQL Server virtual machine in Azure with the SQL VM resource provider](sql-vm-resource-provider-register.md).|
+|**New SQL VM resource provider** |  A new resource provider (Microsoft.SqlVirtualMachine) provides better management of your SQL Server VMs. For more information on registering your VMs, see [Register a SQL Server virtual machine in Azure with the SQL VM resource provider](sql-vm-resource-provider-register.md). |
 |**Switch licensing model** | You can now switch between the pay-per-usage and bring-your-own-license models for your SQL Server VM by using the Azure CLI or PowerShell. For more information, see [How to change the licensing model for a SQL Server virtual machine in Azure](licensing-model-azure-hybrid-benefit-ahb-change.md). | 
 |   |   |
 

articles/azure-sql/virtual-machines/windows/failover-cluster-instance-premium-file-share-manually-configure.md

@@ -40,7 +40,7 @@ You should also have a general understanding of these technologies:
 - [Azure resource groups](../../../azure-resource-manager/management/manage-resource-groups-portal.md)
 
 > [!IMPORTANT]
-> At this time, SQL Server failover cluster instances on Azure virtual machines are only supported with the [lightweight management mode](sql-resource-provider-register.md#management-modes) of the [SQL Server IaaS Agent Extension](sql-server-iaas-agent-extension-automate-management.md). To change from full extension mode to lightweight, delete the **SQL Virtual Machine** resource for the corresponding VMs and then register them with the SQL VM resource provider in lightweight mode. When deleting the **SQL Virtual Machine** resource using the Azure portal, **clear the checkbox next to the correct Virtual Machine**. The full extension supports features such as automated backup, patching, and advanced portal management. These features will not work for SQL VMs after the agent is reinstalled in lightweight management mode.
+> At this time, SQL Server failover cluster instances on Azure virtual machines are only supported with the [lightweight management mode](sql-vm-resource-provider-register.md#management-modes) of the [SQL Server IaaS Agent Extension](sql-server-iaas-agent-extension-automate-management.md). To change from full extension mode to lightweight, delete the **SQL Virtual Machine** resource for the corresponding VMs and then register them with the SQL VM resource provider in lightweight mode. When deleting the **SQL Virtual Machine** resource using the Azure portal, **clear the checkbox next to the correct Virtual Machine**. The full extension supports features such as automated backup, patching, and advanced portal management. These features will not work for SQL VMs after the agent is reinstalled in lightweight management mode.
 
 Premium file shares provide IOPS and throughput capacities that will meet the needs of many workloads. For IO-intensive workloads, consider [SQL Server Failover Cluster Instances with Storage Spaces Direct](failover-cluster-instance-storage-spaces-direct-manually-configure.md), based on managed premium disks or ultra disks.