Skip to content

Commit b6edb6a

Browse files
authored
Merge pull request #189303 from tomkerkhove/tomkerkhove/config-v2
docs: Provide overview of self-hosted gateway v2 requirements in Azure API Management
2 parents 8f71ffe + 886a2e5 commit b6edb6a

File tree

1 file changed

+25
-5
lines changed

1 file changed

+25
-5
lines changed

articles/api-management/self-hosted-gateway-overview.md

Lines changed: 25 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -62,11 +62,8 @@ Self-hosted gateways require outbound TCP/IP connectivity to Azure on port 443.
6262

6363
To operate properly, each self-hosted gateway needs outbound connectivity on port 443 to the following endpoints associated with its cloud-based API Management instance:
6464

65-
* The public IP address of the API Management instance in its primary location
66-
* The hostname of the instance's management endpoint: `<apim-service-name>.management.azure-api.net`
67-
* The hostname of the instance's associated blob storage account: `<blob-storage-account-name>.blob.core.windows.net`
68-
* The hostname of the instance's associated table storage account: `<table-storage-account-name>.table.core.windows.net`
69-
* Public IP addresses from the Storage [service tag](../virtual-network/service-tags-overview.md) corresponding to the primary location of the API Management instance
65+
- [Gateway v2 requirements](#gateway-v2-requirements)
66+
- [Gateway v1 requirements](#gateway-v1-requirements)
7067

7168
> [!IMPORTANT]
7269
> * DNS hostnames must be resolvable to IP addresses and the corresponding IP addresses must be reachable.
@@ -79,6 +76,29 @@ If integrated with your API Management instance, also enable outbound connectivi
7976
* [Application Insights](api-management-howto-app-insights.md)
8077
* [External cache](api-management-howto-cache-external.md)
8178

79+
#### Gateway v2 requirements
80+
81+
The self-hosted gateway v2 requires the following:
82+
83+
* The public IP address of the API Management instance in its primary location
84+
* The hostname of the instance's configuration endpoint: `<apim-service-name>.configuration.azure-api.net`
85+
86+
Additionally,customers that use API inspector or quotas in their policies have to ensure that the following additional dependencies are accessible:
87+
88+
* The hostname of the instance's associated blob storage account: `<blob-storage-account-name>.blob.core.windows.net`
89+
* The hostname of the instance's associated table storage account: `<table-storage-account-name>.table.core.windows.net`
90+
* Public IP addresses from the Storage [service tag](../virtual-network/service-tags-overview.md) corresponding to the primary location of the API Management instance
91+
92+
#### Gateway v1 requirements
93+
94+
The self-hosted gateway v1 requires the following:
95+
96+
* The public IP address of the API Management instance in its primary location
97+
* The hostname of the instance's management endpoint: `<apim-service-name>.management.azure-api.net`
98+
* The hostname of the instance's associated blob storage account: `<blob-storage-account-name>.blob.core.windows.net`
99+
* The hostname of the instance's associated table storage account: `<table-storage-account-name>.table.core.windows.net`
100+
* Public IP addresses from the Storage [service tag](../virtual-network/service-tags-overview.md) corresponding to the primary location of the API Management instance
101+
82102
### Connectivity failures
83103

84104
When connectivity to Azure is lost, the self-hosted gateway is unable to receive configuration updates, report its status, or upload telemetry.

0 commit comments

Comments
 (0)