Skip to content

Commit 9cde7b0

Browse files
author
Owen Duncan
committed
Revisions
1 parent 3fa56cd commit 9cde7b0

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/analysis-services/analysis-services-network-faq.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.reviewer: minewiskan
1111

1212
# Frequently asked questions about Analysis Services network connectivity
1313

14-
This article provides answers to some of the more common questions about connecting to storage accounts, data sources, firewalls, and IP addresses.
14+
This article provides answers to common questions about connecting to storage accounts, data sources, firewalls, and IP addresses.
1515

1616
## Backup and restore
1717

@@ -27,12 +27,12 @@ This article provides answers to some of the more common questions about connect
2727
**Answer** - Azure Analysis Services is unable to join a VNET. The best solution here is to install and configure an On-premises Data Gateway on the VNET, and then configure your Analysis Services servers with the **AlwaysUseGateway** server property. To learn more, see [Use gateway for data sources on an Azure Virtual Network (VNet)](analysis-services-vnet-gateway.md).
2828

2929
### I have a source database behind a firewall. How can I configure the firewall to allow my Analysis Services server to access it?
30-
**Answer** - Azure Analysis Services does not use fixed IP addresses or Service Tags. The range of IP addresses your Analysis Services servers use can be anything in the range of IP addresses for the **Azure region**. Because of this, you would have to provide the full range of IP addresses for the Azure region of your server in the source database firewall rules. Another, and possibly more secure, alternative is to configure an On-premises Data Gateway. You can then configure your Analysis Services servers with the [AlwaysUseGateway server property](analysis-services-vnet-gateway.md#configure-alwaysusegateway-property), and then ensure the On-premises Data Gateway has an IP address which is allowed by the firewall rules of the data source.
30+
**Answer** - Azure Analysis Services does not use fixed IP addresses or Service Tags. The range of IP addresses your Analysis Services servers use can be anything in the range of IP addresses for the **Azure region**. You have to provide the *full range* of IP addresses for the Azure region of your server in the source database firewall rules. Another, and possibly more secure, alternative is to configure an On-premises Data Gateway. You can then configure your Analysis Services servers with the [AlwaysUseGateway server property](analysis-services-vnet-gateway.md#configure-alwaysusegateway-property), and then ensure the On-premises Data Gateway has an IP address, which is allowed by the firewall rules of the data source.
3131

3232
## Azure apps with IP address
3333

3434
### I use an Azure-based application (for example, Azure Functions, Azure Data Factory) with an IP address that changes on the fly. How can I manage the Azure Analysis Services firewall rules to dynamically allow the IP address where my app is executing?
35-
**Answer** - Azure Analysis Services does not support Private Links, VNETs or Service Tags. There are some open source solutions (for example, https://github.com/mathwro/Scripts/blob/master/Azure/AllowAzure-AnalysisServer.ps1) that detect the IP address of the client application, and automatically and temporarily update the firewall rules.
35+
**Answer** - Azure Analysis Services does not support Private Links, VNETs, or Service Tags. There are some open-source solutions (for example, https://github.com/mathwro/Scripts/blob/master/Azure/AllowAzure-AnalysisServer.ps1) that detect the IP address of the client application, and automatically and temporarily update the firewall rules.
3636

3737

3838
## Next steps

0 commit comments

Comments
 (0)