Skip to content

Commit ca1752f

Browse files
committed
copyedits for inbound PE
1 parent 427daa1 commit ca1752f

File tree

3 files changed

+10
-10
lines changed

3 files changed

+10
-10
lines changed

articles/api-management/private-endpoint.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ ms.service: api-management
55
author: dlepow
66
ms.author: danlep
77
ms.topic: how-to
8-
ms.date: 02/23/2023
8+
ms.date: 03/09/2023
99

1010
---
1111

@@ -235,7 +235,7 @@ To connect to 'Microsoft.ApiManagement/service/my-apim-service', please use the
235235
## Next steps
236236

237237
* Use [policy expressions](api-management-policy-expressions.md#ref-context-request) with the `context.request` variable to identify traffic from the private endpoint.
238-
* Learn more about [private endpoints](../private-link/private-endpoint-overview.md) and [Private Link](../private-link/private-link-overview.md).
238+
* Learn more about [private endpoints](../private-link/private-endpoint-overview.md) and [Private Link](../private-link/private-link-overview.md), including [Private Link pricing](https://azure.microsoft.com/pricing/details/private-link/).
239239
* Learn more about [managing private endpoint connections](../private-link/manage-private-endpoint.md).
240240
* [Troubleshoot Azure private endpoint connectivity problems](../private-link/troubleshoot-private-endpoint-connectivity.md).
241241
* Use a [Resource Manager template](https://azure.microsoft.com/resources/templates/api-management-private-endpoint/) to create an API Management instance and a private endpoint with private DNS integration.

articles/api-management/virtual-network-concepts.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: dlepow
55

66
ms.service: api-management
77
ms.topic: conceptual
8-
ms.date: 02/06/2023
8+
ms.date: 03/09/2023
99
ms.author: danlep
1010
ms.custom:
1111
---
@@ -17,15 +17,15 @@ API Management provides several options to secure access to your API Management
1717

1818
You can choose one of two integration modes: *external* or *internal*. They differ in whether inbound connectivity to the gateway and other API Management endpoints is allowed from the internet or only from within the virtual network.
1919

20-
* **Enabling secure and private connectivity** to the API Management gateway using a *private endpoint* (preview).
20+
* **Enabling secure and private inbound connectivity** to the API Management gateway using a *private endpoint*.
2121

2222
The following table compares virtual networking options. For more information, see later sections of this article and links to detailed guidance.
2323

2424
|Networking model |Supported tiers |Supported components |Supported traffic |Usage scenario |
2525
|---------|---------|---------|---------|----|
2626
|**[Virtual network - external](#virtual-network-integration)** | Developer, Premium | Azure portal, gateway, management plane, and Git repository | Inbound and outbound traffic can be allowed to internet, peered virtual networks, Express Route, and S2S VPN connections. | External access to private and on-premises backends
2727
|**[Virtual network - internal](#virtual-network-integration)** | Developer, Premium | Developer portal, gateway, management plane, and Git repository. | Inbound and outbound traffic can be allowed to peered virtual networks, Express Route, and S2S VPN connections. | Internal access to private and on-premises backends
28-
|**[Private endpoint](#private-endpoint)** | Developer, Basic, Standard, Premium | Gateway only (managed gateway supported, self-hosted gateway not supported). | Only inbound traffic can be allowed from internet, peered virtual networks, Express Route, and S2S VPN connections. | Secure client connection to API Management gateway |
28+
|**[Inbound private endpoint](#inbound-private-endpoint)** | Developer, Basic, Standard, Premium | Gateway only (managed gateway supported, self-hosted gateway not supported). | Only inbound traffic can be allowed from internet, peered virtual networks, Express Route, and S2S VPN connections. | Secure client connection to API Management gateway |
2929

3030
## Virtual network integration
3131
With Azure virtual networks (VNets), you can place ("inject") your API Management instance in a non-internet-routable network to which you control access. In a virtual network, your API Management instance can securely access other networked Azure resources and also connect to on-premises networks using various VPN technologies. To learn more about Azure VNets, start with the information in the [Azure Virtual Network Overview](../virtual-network/virtual-networks-overview.md).
@@ -141,19 +141,19 @@ Some virtual network limitations differ depending on the version (`stv2` or `stv
141141
* A subnet containing API Management instances can't be moved across subscriptions.
142142
* For multi-region API Management deployments configured in internal VNet mode, users own the routing and are responsible for managing the load balancing across multiple regions.
143143
* To import an API to API Management from an [OpenAPI specification](import-and-publish.md), the specification URL must be hosted at a publicly accessible internet address.
144-
* Due to platform limitations, connectivity between a resource in a globally peered VNet in another region and an API Management service in internal mode won't work. For more information, see the [virtual network documentation](../virtual-network/virtual-network-manage-peering.md#requirements-and-constraints).
144+
* Due to platform limitations, connectivity between a resource in a globally peered VNet in another region and an API Management service in internal mode doesn't work. For more information, see the [virtual network documentation](../virtual-network/virtual-network-manage-peering.md#requirements-and-constraints).
145145

146146
---
147147

148-
## Private endpoint
148+
## Inbound private endpoint
149149

150-
API Management supports [private endpoints](../private-link/private-endpoint-overview.md). A private endpoint enables secure client connectivity to your API Management instance using a private IP address from your virtual network and Azure Private Link.
150+
API Management supports [private endpoints](../private-link/private-endpoint-overview.md) for secure inbound client connections to your API Management instance. Each secure connection uses a private IP address from your virtual network and Azure Private Link.
151151

152152
:::image type="content" source="media/virtual-network-concepts/api-management-private-endpoint.png" alt-text="Diagram showing a secure connection to API Management using private endpoint." lightbox="media/virtual-network-concepts/api-management-private-endpoint.png":::
153153

154154
[!INCLUDE [api-management-private-endpoint](../../includes/api-management-private-endpoint.md)]
155155

156-
For more information, see [Connect privately to API Management using a private endpoint](private-endpoint.md).
156+
For more information, see [Connect privately to API Management using an inbound private endpoint](private-endpoint.md).
157157

158158
## Advanced networking configurations
159159

includes/api-management-private-endpoint.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
author: dlepow
33
ms.service: api-management
44
ms.topic: include
5-
ms.date: 02/06/2023
5+
ms.date: 03/09/2023
66
ms.author: danlep
77
---
88

0 commit comments

Comments
 (0)