Skip to content

Commit bf929a2

Browse files
authored
Update backup-sql-server-database-azure-vms.md
1 parent b03d88b commit bf929a2

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -81,7 +81,7 @@ To create a rule using PowerShell:
8181

8282
**Allow access by using Azure Firewall tags**. If you're using Azure Firewall, create an application rule by using the AzureBackup [FQDN tag](https://docs.microsoft.com/azure/firewall/fqdn-tags). This allows outbound access to Azure Backup.
8383

84-
**Deploy an HTTP proxy server to route traffic**. When you back up a SQL Server database on an Azure VM, the backup extension on the VM uses the HTTPS APIs to send management commands to Azure Backup and data to Azure Storage. The backup extension also uses Azure AD for authentication. Route the backup extension traffic for these three services through the HTTP proxy. The extensions are the only component that's configured for access to the public internet.
84+
**Deploy an HTTP proxy server to route traffic**. When you back up a SQL Server database on an Azure VM, the backup extension on the VM uses the HTTPS APIs to send management commands to Azure Backup and data to Azure Storage. The backup extension also uses Azure AD for authentication. Route the backup extension traffic for these three services through the HTTP proxy. There are no wildcard domains in use with Azure Backup to whitelist for your proxy rules, you will need to utilize the Public IP ranges for these services provided by Azure. The extensions are the only component that's configured for access to the public internet.
8585

8686
Connectivity options include the following advantages and disadvantages:
8787

0 commit comments

Comments
 (0)