updated as per PR comments

Author: vrvkrajesh

articles/backup/backup-azure-file-folder-backup-faq.md

@@ -154,14 +154,14 @@ The Azure Backup agent requires a passphrase (that you provided during registrat
 
 | Original Machine <br> *(source machine where backups were taken)* | Passphrase | Available Options |
 | --- | --- | --- |
-| Available |Lost |If your original machine (where backups were taken) is available and still registered with the same Recovery Services vault, then you will be able to regenerate the passphrase by following these <steps>  |
+| Available |Lost |If your original machine (where backups were taken) is available and still registered with the same Recovery Services vault, then you will be able to regenerate the passphrase by following these [steps](https://docs.microsoft.com/azure/backup/backup-azure-manage-mars#re-generate-passphrase).  |
 | Lost |Lost |Not possible to recover the data or data is not available |
 
 Consider the following conditions:
 - If you uninstall & re-register the agent on the same original machine with
   - *Same passphrase*, then you will be able to restore your backed up data.<br>
   - *Different passphrase*, then you will not be able to restore your backed up data.
--	If you install the agent on a *different machine* with<br>
+-	If you install the agent on a *different machine* with,<br>
   - the same passphrase (used in the original machine), then you will be able to restore your backed up data.<br>
   - a different passphrase, you will not be able to restore your backed up data.<br>
 -	Additionally, if your original machine is corrupted (preventing you from regenerating the passphrase through the MARS console); but you are able to restore/access the original scratch folder used by the MARS agent, then you might be able to restore (if you forgot the password). For more assistance, contact Customer Support.
@@ -172,7 +172,7 @@ If you have the same passphrase (that you provided during registration) of the o
 
 | Original Machine | Passphrase | Available Options |
 | --- | --- | --- |
-| Lost |Available |You can install and register the MARS agent on another machine with the same passphrase that you provided during registration of the original machine. Choose **Recovery Option** > **Another location** to perform your restore. For more information, see
+| Lost |Available |You can install and register the MARS agent on another machine with the same passphrase that you provided during registration of the original machine. Choose **Recovery Option** > **Another location** to perform your restore. For more information, refer this [article](https://docs.microsoft.com/azure/backup/backup-azure-restore-windows-server#use-instant-restore-to-restore-data-to-an-alternate-machine).
 | Lost |Lost |Not possible to recover the data or data is not available |
 
 

articles/backup/backup-sql-server-azure-troubleshoot.md

@@ -16,15 +16,22 @@ For more information about the backup process and limitations, see [About SQL Se
 To configure protection for a SQL Server database on a virtual machine, you must install the **AzureBackupWindowsWorkload** extension on that virtual machine. If you get the error **UserErrorSQLNoSysadminMembership**, it means your SQL Server instance doesn't have the required backup permissions. To fix this error, follow the steps in [Set VM permissions](backup-azure-sql-database.md#set-vm-permissions).
 
 ## Troubleshooting Discover and Configure issues
-After creating and configuring a Recovery Services vault. Discovering databases and configuring backup is a two-step process.<br>
+After creating and configuring a Recovery Services vault, discovering databases and configuring backup is a two-step process.<br>
 
 ![sql](./media/backup-azure-sql-database/sql.png)
 
-The SQL VM and its instances will be not visible in **Step 1: Discovery DBs in VMs** and **Step 2: Configure Backup** for backup configuration because the VM might have already been registered/discovered (**Step 1: Discovery DBs in VMs**) in another other vault and you are trying to configure backup of that SQL VM's instances/database (**Step 2: Configure Backup**) to another different vault.<br>
-- Ensure the VM is not listed in the discovered VM list, then ensure the VM is not already registered for SQL backup in another vault.<br>
-- Ensure vault in which the SQL VM is registered is the same vault used to protect the databases using **Step 2: Configure Backup**.<br>
+During the backup configuration, if the SQL VM and its instances are not visible in the **Discovery DBs in VMs** and **Configure Backup** (refer to above image) because of the following steps.
+
+**Step 1: Discovery DBs in VMs**
+<br>
+- If the VM is not listed in the discovered VM list and also not registered for SQL backup in another vault, then follow the [Discovery SQL Server backup](https://docs.microsoft.com/azure/backup/backup-sql-server-database-azure-vms#discover-sql-server-databases) steps.<br>
+
+**Step 2: Configure Backup**
+<br>
+- If the vault in which the SQL VM is registered in the same vault used to protect the databases, then follow the [Configure Backup](https://docs.microsoft.com/azure/backup/backup-sql-server-database-azure-vms#configure-backup) steps.<br>
+
+If the SQL VM needs to be registered in the new vault, then it must be unregistered from the old vault.  Unregistration of a SQL VM from a vault requires all the protected data sources to be stop protected and then delete backed up data. Deleting backed up data is a destructive operation.  After you have reviewed and taken all the precautions to proceed further to unregister the SQL VM, then register this same VM with a new vault and retry the backup operation.
 
-If the SQL VM needs to be registered in the new vault, then it must be unregistered from the old vault.  Unregistration of a SQL VM from a vault requires all the protected data sources to be stop protected and then delete backed up data. Deleting backed up data is a destructive operation.  After you have reviewed and taken all the precautions to proceed further to unregister the SQL VM, then register this same VM with a new vault and retry backup operation.
 
 
 ## Error messages
@@ -136,7 +143,7 @@ Operation is blocked as the vault has reached its maximum limit for such operati
 
 | Error message | Possible causes | Recommended action |
 |---|---|---|
-VM is not able to contact Azure Backup service due to internet connectivity issues. | VM needs outbound connectivity to Azure Backup Service, Azure Storage or Azure Active Directory services.| - If you use NSG to restrict connectivity, then you should use the AzureBackup service tag to allows outbound access to Azure Backup to Azure Backup Service, Azure Storage or Azure Active Directory services. Follow these [steps](https://aka.ms/nsgrulesforsqlbackup) to grant access.<br>- Ensure DNS is resolving Azure endpoints.<br>- Check if VM is behind a Load balancer blocking Internet access. By assigning public IP to the VMs, discovery will work.<br>- Verify there is no firewall/antivirus/proxy that is blocking calls to the above three target services.
+The VM is not able to contact Azure Backup service due to internet connectivity issues. | The VM needs outbound connectivity to Azure Backup Service, Azure Storage or Azure Active Directory services.| - If you use NSG to restrict connectivity, then you should use the AzureBackup service tag to allows outbound access to Azure Backup to Azure Backup Service, Azure Storage or Azure Active Directory services. Follow these [steps](https://aka.ms/nsgrulesforsqlbackup) to grant access.<br>- Ensure DNS is resolving Azure endpoints.<br>- Check if the VM is behind a Load balancer blocking Internet access. By assigning public IP to the VMs, discovery will work.<br>- Verify there is no firewall/antivirus/proxy that is blocking calls to the above three target services.
 
 
 ## Re-registration failures

articles/backup/backup-sql-server-database-azure-vms.md

@@ -38,10 +38,10 @@ For all operations, a SQL Server VM requires connectivity to Azure public IP add
 Establish connectivity by using one of the following options:
 
 #### **Allow the Azure datacenter IP ranges**.
-This option allows [IP ranges](https://www.microsoft.com/download/details.aspx?id=41653) in the download. To access a network security group (NSG), use the Set-AzureNetworkSecurityRule cmdlet. If you're safe recipients list only region-specific IPs, you'll also need to update the safe recipients list the Azure Active Directory (Azure AD) service tag to enable authentication.
+This option allows the [IP ranges](https://www.microsoft.com/download/details.aspx?id=41653) in the downloaded file. To access a network security group (NSG), use the Set-AzureNetworkSecurityRule cmdlet. If your safe recipient's list only includes region-specific IPs, you'll also need to update the safe recipients list the Azure Active Directory (Azure AD) service tag to enable authentication.
 
 #### **Allow access using NSG tags**.
-If you use NSG to restrict connectivity, then you should use AzureBackup service tag to allows outbound access to Azure Backup. In addition, you should also allow connectivity for authentication and data transfer by using [rules](https://docs.microsoft.com/azure/virtual-network/security-overview#service-tags)  for Azure AD and Azure Storage. This can be done from portal or PowerShell.
+If you use NSG to restrict connectivity, then you should use AzureBackup service tag to allows outbound access to Azure Backup. In addition, you should also allow connectivity for authentication and data transfer by using [rules](https://docs.microsoft.com/azure/virtual-network/security-overview#service-tags)  for Azure AD and Azure Storage. This can be done from the Azure portal or via PowerShell.
 
 To create a rule using the portal: