Skip to content

Commit 17ee4bc

Browse files
author
gitName
committed
validation
1 parent c395ef3 commit 17ee4bc

File tree

2 files changed

+6
-6
lines changed

2 files changed

+6
-6
lines changed

articles/api-management/private-endpoint.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -32,13 +32,13 @@ You can configure an inbound [private endpoint](../private-link/private-endpoint
3232
* Only the API Management instance's Gateway endpoint supports inbound Private Link connections.
3333
* Each API Management instance supports at most 100 Private Link connections.
3434
* Connections aren't supported on the [self-hosted gateway](self-hosted-gateway-overview.md) or on a [workspace gateway](workspaces-overview.md#workspace-gateway).
35-
* In the classic API Management tiers, private endpoints are not supported in instances injected in an internal or external virtual network.
35+
* In the classic API Management tiers, private endpoints aren't supported in instances injected in an internal or external virtual network.
3636

3737

3838
## Prerequisites
3939

4040
- An existing API Management instance. [Create one if you haven't already](get-started-create-service-instance.md).
41-
- When using an instance in the classic Developer or Premium tier, do not deploy (inject) the instance into an [external](api-management-using-with-vnet.md) or [internal](api-management-using-with-internal-vnet.md) virtual network.
41+
- When using an instance in the classic Developer or Premium tier, don't deploy (inject) the instance into an [external](api-management-using-with-vnet.md) or [internal](api-management-using-with-internal-vnet.md) virtual network.
4242
- A virtual network containing a subnet to host the private endpoint. The subnet may contain other Azure resources.
4343
- (Recommended) A virtual machine in the same or a different subnet in the virtual network, to test the private endpoint.
4444
[!INCLUDE [azure-cli-prepare-your-environment-no-header.md](~/reusable-content/azure-cli/azure-cli-prepare-your-environment-no-header.md)]
@@ -210,7 +210,7 @@ You can also use the API Management [Private Endpoint Connection - Create Or Upd
210210
| Resource | Select your API Management Standard v2 instance. |
211211
| Target sub-resource | Select **Gateway**. |
212212

213-
:::image type="content" source="media/private-endpoint-v2-tiers/create-private-endpoint.png" alt-text="Screenshot showing settings to create a private endpoint in the Azure portal.":::
213+
:::image type="content" source="media/private-endpoint/create-private-endpoint.png" alt-text="Screenshot showing settings to create a private endpoint in the Azure portal.":::
214214

215215
> [!IMPORTANT]
216216
> Only the **Gateway** sub-resource is supported for API Management. Other sub-resources aren't supported.
@@ -309,7 +309,7 @@ API calls initiated within the virtual network to the default Gateway endpoint s
309309
From outside the private endpoint path, attempt to call the API Management instance's default Gateway endpoint. If public access is disabled, output includes an error with status code `403` and a message similar to:
310310

311311
```
312-
Request originated from client public IP address xxx.xxx.xxx.xxx, public network access on this 'Microsoft.ApiManagement/service/my-apim-service' is disabled.
312+
Request originated from client public IP address 192.0.2.12, public network access on this 'Microsoft.ApiManagement/service/my-apim-service' is disabled.
313313
314314
To connect to 'Microsoft.ApiManagement/service/my-apim-service', please use the Private Endpoint from inside your virtual network.
315315
```

includes/api-management-private-endpoint.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,9 +16,9 @@ With a private endpoint and Private Link, you can:
1616

1717
- Limit incoming traffic only to private endpoints, preventing data exfiltration.
1818

19-
- Combine inbound private endpoints to Standard v2 instances with outbound [virtual network integration](integrate-vnet-outbound.md) to provide end-to-end network isolation of your API Management clients and backend services.
19+
- Combine inbound private endpoints to Standard v2 instances with outbound [virtual network integration](../articles/api-management/integrate-vnet-outbound.md) to provide end-to-end network isolation of your API Management clients and backend services.
2020

21-
:::image type="content" source="../articles/api-management/media/private-endpoint-v2-tiers/private-endpoint.png" alt-text="Diagram that shows a secure inbound connection to API Management Standard v2 using private endpoint.":::
21+
:::image type="content" source="../articles/api-management/media/private-endpoint/private-endpoint.png" alt-text="Diagram that shows a secure inbound connection to API Management Standard v2 using private endpoint.":::
2222

2323

2424
> [!IMPORTANT]

0 commit comments

Comments
 (0)