You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/api-management/self-hosted-gateway-overview.md
+8-2Lines changed: 8 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ author: dlepow
6
6
7
7
ms.service: api-management
8
8
ms.topic: conceptual
9
-
ms.date: 02/28/2024
9
+
ms.date: 05/15/2024
10
10
ms.author: danlep
11
11
---
12
12
@@ -110,7 +110,7 @@ To operate properly, each self-hosted gateway needs outbound connectivity on por
110
110
| Endpoints for [Event Hubs integration](api-management-howto-log-event-hubs.md)| Optional<sup>5</sup> | Optional<sup>5</sup> | Learn more in [Azure Event Hubs docs](../event-hubs/network-security.md)|
111
111
| Endpoints for [external cache integration](api-management-howto-cache-external.md)| Optional<sup>5</sup> | Optional<sup>5</sup> | This requirement depends on the external cache that is being used |
112
112
113
-
<sup>1</sup>For an API Management instance in an internal virtual network, enable private connectivity to the v2 configuration endpoint from the location of the self-hosted gateway, for example, using a private DNS in a peered network.<br/>
113
+
<sup>1</sup>For an API Management instance in an internal virtual network, see [Connectivity in an internal virtual network](#connectivity-in-internal-virtual-network)
114
114
<sup>2</sup>Only required in v2 when API inspector or quotas are used in policies.<br/>
115
115
<sup>3</sup>Only required when using Microsoft Entra authentication to verify RBAC permissions.<br/>
116
116
<sup>4</sup>Only required when using Microsoft Entra authentication or Microsoft Entra related policies.<br/>
@@ -121,6 +121,12 @@ To operate properly, each self-hosted gateway needs outbound connectivity on por
121
121
> * The associated storage account names are listed in the service's **Network connectivity status** page in the Azure portal.
122
122
> * Public IP addresses underlying the associated storage accounts are dynamic and can change without notice.
123
123
124
+
### Connectivity in internal virtual network
125
+
126
+
***Private connectivity** - If the self-hosted gateway is deployed in a virtual network, enable private connectivity to the v2 configuration endpoint from the location of the self-hosted gateway, for example, using a private DNS in a peered network.
127
+
128
+
***Internet connectivity** - If the self-hosted gateway needs to connect to the v2 configuration endpoint over the internet, configure a custom hostname for the configuration endpoint, and expose the endpoint using Application Gateway.<br/>
129
+
124
130
### Authentication options
125
131
126
132
To authenticate the connection between the self-hosted gateway and the cloud-based API Management instance's configuration endpoint, you have the following options in the gateway container's [configuration settings](self-hosted-gateway-settings-reference.md).
0 commit comments