Add Microsoft.AzureArcData

One of the most common customer support cases that we get in Arc-enabled SQL Server is when the customer has deployed the SQL Server extension to an Arc agent but the SQL Server resource doesnt show up.  Most times this is caused by the Microsoft.AzureArcData RP not being registered. If we can tell customers earlier on in the onboarding process to also register that RP as part of the onboarding process if they plan to Arc enable their SQL Servers, then hopefully we can reduce the occurrence of this type of support case.

Author: twright-msft

articles/azure-arc/servers/learn/quick-enable-hybrid-vm.md

@@ -16,7 +16,7 @@ In this quickstart, you'll deploy and configure the Azure Connected Machine agen
 
 * An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
 * Deploying the Connected Machine agent on a machine requires that you have administrator permissions to install and configure the agent. On Linux this is done by using the root account, and on Windows, with an account that is a member of the Local Administrators group.
-* The Microsoft.HybridCompute, Microsoft.GuestConfiguration, and Microsoft.HybridConnectivity resource providers must be registered on your subscription. Please [register these resource providers ahead of time](../prerequisites.md#azure-resource-providers).
+* The Microsoft.HybridCompute, Microsoft.GuestConfiguration, Microsoft.HybridConnectivity, and Microsoft.AzureArcData resource providers must be registered on your subscription. Please [register these resource providers ahead of time](../prerequisites.md#azure-resource-providers).
 * Before you get started, be sure to review the [agent prerequisites](../prerequisites.md) and verify the following:
   * Your target machine is running a supported [operating system](../prerequisites.md#supported-operating-systems).
   * Your account has the [required Azure built-in roles](../prerequisites.md#required-permissions).