Skip to content

Commit 46a8c62

Browse files
Merge pull request #289510 from dlepow/misc
[APIM][release-preview-apim-premv2] Updates to regions, endpoints
2 parents a08d3cd + a7e4e79 commit 46a8c62

File tree

2 files changed

+7
-9
lines changed

2 files changed

+7
-9
lines changed

articles/api-management/api-management-region-availability.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ API Management [v2 tiers](v2-service-tiers-overview.md) and API Management [work
2020

2121
## Supported regions for v2 tiers and workspace gateways
2222

23-
Information in the following table is updated regularly.
23+
Information in the following table is updated regularly. Capacity availability in Azure regions may vary.
2424

2525

2626
| Region | Basic v2 | Standard v2 | Premium v2 (preview) | Workspace gateway (Premium) |
@@ -32,7 +32,7 @@ Information in the following table is updated regularly.
3232
| Central India ||| | |
3333
| Central US | | || |
3434
| East Asia |||||
35-
| East US | | | | |
35+
| East US | | | | |
3636
| East US 2 ||| ||
3737
| France Central |||||
3838
| Germany West Central |||||

articles/api-management/inject-vnet-v2.md

Lines changed: 5 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ This article guides you through the requirements to inject your Azure API Manage
1919
2020
When an API Management Premium v2 instance is injected in a virtual network:
2121

22-
* The API Management gateway and developer portal endpoints are accessible through the virtual network at a private IP address.
22+
* The API Management gateway endpoint is accessible through the virtual network at a private IP address.
2323
* API Management can make outbound requests to API backends that are isolated in the network.
2424

2525
This configuration is recommended for scenarios where you want to isolate network traffic to both the API Management instance and the backend APIs.
@@ -98,22 +98,20 @@ We recommend:
9898

9999
Learn how to [set up a private zone in Azure DNS](../dns/private-dns-getstarted-portal.md).
100100

101-
### Endpoint access on default hostnames
101+
### Endpoint access on default hostname
102102

103-
When you create an API Management instance in the Premium v2 tier, the following endpoints are assigned default hostnames:
103+
When you create an API Management instance in the Premium v2 tier, the following endpoint is assigned a default hostname:
104104

105105
* **Gateway** - example: `contoso-apim.azure-api.net`
106-
* **Developer portal** - example: `contoso-apim.portal.azure-api.net`
107106

108-
### Configure DNS records
107+
### Configure DNS record
109108

110-
Create A records in your DNS server to access the API Management instance from within your virtual network. Map the endpoint records to the private VIP address of your API Management instance.
109+
Create an A record in your DNS server to access the API Management instance from within your virtual network. Map the endpoint record to the private VIP address of your API Management instance.
111110

112111
For testing purposes, you might update the hosts file on a virtual machine in a subnet connected to the virtual network in which API Management is deployed. Assuming the private virtual IP address for your API Management instance is 10.1.0.5, you can map the hosts file as shown in the following example. The hosts mapping file is at `%SystemDrive%\drivers\etc\hosts` (Windows) or `/etc/hosts` (Linux, macOS). For example:
113112

114113
| Internal virtual IP address | Gateway hostname |
115114
| ----- | ----- |
116-
| 10.1.0.5 | `contoso-apim.azure-api.net` |
117115
| 10.1.0.5 | `contoso-apim.portal.azure-api.net` |
118116

119117
## Related content

0 commit comments

Comments
 (0)