Apply suggestions from code review

pam's suggestions

Co-authored-by: Pam Lahoud <32913866+bluefooted@users.noreply.github.com>

Update frequently-asked-questions-faq.yml

Clarified how to add SQL Server to an existing VM

staging more stuff

Added Microsoft Entra to benefits & improved limitations

fixing links

recommended changes

changing checklist

editing checklist

adding space

fixing spaces

stuff

adding t-log changes

acrolinx

fixing warning

fixing things

Apply suggestions from code review

randolphs changes

Co-authored-by: Randolph West MSFT <97149825+rwestMSFT@users.noreply.github.com>

fixing link

adding pam's changes

updated to pane

fixing acrolinx

Author: MashaMSFT

azure-sql/includes/sql-vm-feature-benefits.md

@@ -12,7 +12,7 @@ ms.topic: include
 | **Automated backup** |Automates the scheduling of backups for all databases for either the default instance or a [properly installed named instance](../virtual-machines/windows/frequently-asked-questions-faq.yml#can-i-use-a-named-instance-of-sql-server-with-the-iaas-extension-) of SQL Server on the VM. For more information, see [Automated backup for SQL Server in Azure virtual machines (Resource Manager)](../virtual-machines/windows/automated-backup-sql-2014.md). <br /> <br /> Requires SQL IaaS Agent extension. |
 | **Automated patching** |Configures a maintenance window during which important Windows and SQL Server security updates to your VM can take place, so you can avoid updates during peak times for your workload. For more information, see [Automated patching for SQL Server in Azure virtual machines (Resource Manager)](../virtual-machines/windows/automated-patching.md). <br /> <br /> Requires SQL IaaS Agent extension. |
 | **Azure Key Vault integration** |Enables you to automatically install and configure Azure Key Vault on your SQL Server VM. For more information, see [Configure Azure Key Vault integration for SQL Server on Azure Virtual Machines (Resource Manager)](../virtual-machines/windows/azure-key-vault-integration-configure.md). <br /> <br /> Requires SQL IaaS Agent extension. |
-| **Azure Update Manager integration** | Since Automated Patching doesn't install Cumulative Updates for SQL Server, you can replace it with by integrating [Azure Update Manager](../virtual-machines/azure-update-manager-sql-vm.md) into your SQL virtual machines resource, which adds improved patching functionality for your SQL Server VMs.  <br /> <br /> Requires SQL IaaS Agent extension.  | 
+| **Azure Update Manager integration** | Since Automated Patching doesn't install Cumulative Updates for SQL Server, you can replace it by integrating [Azure Update Manager](../virtual-machines/azure-update-manager-sql-vm.md) into your [SQL virtual machines](../virtual-machines/windows/manage-sql-vm-portal.md) resource, which adds improved patching functionality for your SQL Server VMs.  <br /> <br /> Requires SQL IaaS Agent extension.  | 
 | **Configure tempdb** | You can [configure your tempdb](../virtual-machines/windows/manage-sql-vm-portal.md#storage-configuration) directly from the Azure portal, such as specifying the number of files, their initial size, their location, and the autogrowth ratio. Restart your SQL Server service for the changes to take effect. <br /> <br /> Requires SQL IaaS Agent extension.  | 
 | **Defender for Cloud portal integration** | If you've enabled [Microsoft Defender for SQL](/azure/defender-for-cloud/defender-for-sql-usage), then you can view Defender for Cloud recommendations directly in the [SQL virtual machines](../virtual-machines/windows/manage-sql-vm-portal.md) resource of the Azure portal. See [Security best practices](../virtual-machines/windows/security-considerations-best-practices.md) to learn more. <br /> <br /> Requires SQL IaaS Agent extension. |
 | **Flexible licensing** | Save on cost by [seamlessly transitioning](../virtual-machines/windows/licensing-model-azure-hybrid-benefit-ahb-change.md) from the bring-your-own-license (also known as the Azure Hybrid Benefit) to the pay-as-you-go licensing model and back again. <br /> <br /> Included with basic registration. | 

azure-sql/includes/virtual-machines-best-practices-storage.md

@@ -23,7 +23,7 @@ ms.topic: include
 - Set [host caching](/azure/virtual-machines/disks-performance#virtual-machine-uncached-vs-cached-limits) to **none** for log file disks.
   - Don't enable read/write caching on disks that contain SQL Server data or log files.
   - Always stop the SQL Server service before changing the cache settings of your disk.
-- In certain circumstances, using an [Azure Elastic SAN](../virtual-machines/windows/performance-guidelines-best-practices-storage.md#azure-elastic-san) for SQL Server workloads can save on cost due to storage consolidation, shared dynamic performance and the ability to drive higher storage throughput without needing to upgrade a VM. However, when using Azure Elastic SAN, achieving desired IOPS/throughput for SQL Server workloads often requires overprovisioning capacity. While not typically appropriate for single SQL Server workloads, you can attain a cost-effective solution when combining low-performance workloads with SQL Server.
+- When migrating several different workloads to the cloud, [Azure Elastic SAN](../virtual-machines/windows/performance-guidelines-best-practices-storage.md#azure-elastic-san) can be a cost-effective consolidated storage solution. However, when using Azure Elastic SAN, achieving desired IOPS/throughput for SQL Server workloads often requires overprovisioning capacity. While not typically appropriate for single SQL Server workloads, you can attain a cost-effective solution when combining low-performance workloads with SQL Server.
 - For development and test workloads, and long-term backup archival consider using standard storage. It isn't recommended to use Standard HDD/SSD for production workloads.
 - [Credit-based Disk Bursting](/azure/virtual-machines/disk-bursting#credit-based-bursting) (P1-P20) should only be considered for smaller dev/test workloads and departmental systems.
 - To optimize storage performance, plan for highest uncached IOPS available, and use data caching as a performance feature for data reads while avoiding [virtual machine and disks capping/throttling](/azure/virtual-machines/premium-storage-performance#throttling).

azure-sql/virtual-machines/windows/configure-azure-ad-authentication-for-sql-vm.md

@@ -270,7 +270,7 @@ The following output indicates Microsoft Entra authentication has been enabled w
 
 Consider the following limitations: 
 
-- Microsoft Entra authentication is only supported with SQL Server 2022 running on Windows VMs registered with the [SQL IaaS Agent extension](sql-server-iaas-agent-extension-automate-management.md) and deployed to the public cloud. Only supported scenarios of the SQL IaaS Agent extension are supported, such as a default instance, or a single named instance.
+- Microsoft Entra authentication is only supported with SQL Server 2022 running on Windows VMs registered with the [SQL IaaS Agent extension](sql-server-iaas-agent-extension-automate-management.md) and deployed to the public cloud. Only supported scenarios of the SQL IaaS Agent extension are supported, such as a default instance, or a single named instance. Failover cluster instances are not supported. 
 - The identity you choose to authenticate to SQL Server has to have either the **Directory Readers** role in Microsoft Entra ID or the following three Microsoft Graph application permissions (app roles): `User.Read.All`, `GroupMember.Read.All`, and `Application.Read.All`. 
 - Once Microsoft Entra authentication is enabled, there's no way to disable it. 
 - Currently, authenticating to SQL Server on Azure VMs through Microsoft Entra authentication using the [FIDO2 method](/azure/active-directory/authentication/howto-authentication-passwordless-faqs) isn't supported. 

azure-sql/virtual-machines/windows/frequently-asked-questions-faq.yml

@@ -54,7 +54,7 @@ sections:
       - question: |
           Is it possible to create a generalized Azure Marketplace SQL Server image of my SQL Server VM and use it to deploy VMs?
         answer: |
-             Yes, but you must then [register each SQL Server VM with the SQL IaaS Agent extension](sql-agent-extension-manually-register-single-vm.md) to manage your SQL Server VM in the portal, as well as utilize features such as automated patching and automatic backups. When registering with the extension, you'll also need to specify the license type for each SQL Server VM.
+             Yes, but you must then [register each SQL Server VM with the SQL IaaS Agent extension](sql-agent-extension-manually-register-single-vm.md) to manage your SQL Server VM in the portal, as well as utilize features such as automated patching and automatic backups. When registering with the extension, you also need to specify the license type for each SQL Server VM.
           
       - question: |
           How do I generalize SQL Server on Azure VM and use it to deploy new VMs?
@@ -245,7 +245,7 @@ sections:
       - question: |
           How do I get the SQL Server installation media? 
         answer: |             
-             For SQL Server VMs deployed through Azure Marketplace, the installation media is located at `C:\SQLServerFull`. You can run `Setup.exe`` from that location to add new SQL Server instances or to change other installed features of SQL Server on the machine. You can also copy this setup media to other virtual machines to install, or upgrade, that same version, and edition of SQL Server.  Customers who have [Software Assurance](https://www.microsoft.com/licensing/licensing-programs/software-assurance-default?rtc=1&activetab=software-assurance-default-pivot%3aprimaryr3) can obtain their installation media from the [Volume Licensing Center](https://www.microsoft.com/Licensing/servicecenter/default.aspx). 
+             For SQL Server VMs deployed through Azure Marketplace, the installation media is located at `C:\SQLServerFull`. You can run `Setup.exe` from that location to add new SQL Server instances or to change other installed features of SQL Server on the machine. You can also copy this setup media to other virtual machines to install, or upgrade, that same version, and 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). 
              
       - question: |
           How do I install SQL Server for PAYG licensing to an existing Azure VM? 

azure-sql/virtual-machines/windows/licensing-model-azure-hybrid-benefit-ahb-change.md

@@ -99,7 +99,7 @@ Update-AzSqlVM -ResourceGroupName <resource_group_name> -Name <VM_name> -License
 
 - Move all pay-as-you-go (full price) SQL PaaS/IaaS workloads to take advantage of your Azure Hybrid Benefits without have to individually configure them to enable the benefit.
 - Ensure that all your SQL workloads are licensed in compliance with the existing license agreements.
-- Separate the license compliance management roles from devops roles using RBAC
+- Separate the license compliance management roles from devops roles using RBAC.
 - Take advantage of free business continuity by ensuring that your passive & disaster recovery (DR) environments are properly identified.
 - Use MSDN licenses in Azure for non-production environments.
 
@@ -143,7 +143,7 @@ Additionally, changing the license model to **Azure Hybrid Benefit** requires [S
 
 To avoid being charged for your SQL Server instance, see [Pricing guidance for SQL Server on Azure VMs](pricing-guidance.md).
 
-To remove a SQL Server instance and associated billing from a Pay-As-You-Go SQL Server VM, or if you're being charged for a SQL instance after uninstalling it:
+To remove a SQL Server instance and associated billing from a pay-as-you-go SQL Server VM, or if you're being charged for a SQL instance after uninstalling it:
 
 1. Back up your data.
 1. If necessary, uninstall SQL Server, including the SQL IaaS Agent extension.