Skip to content

Commit b7449de

Browse files
Merge pull request #235059 from KarlErickson/bowen5-patch-4
edit "chore: Enhance Azure Spring Apps VNet Injection doc #234834"
2 parents f535aeb + e2d364c commit b7449de

File tree

2 files changed

+119
-110
lines changed

2 files changed

+119
-110
lines changed

articles/spring-apps/access-app-virtual-network.md

Lines changed: 39 additions & 35 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: "Azure Spring Apps access app in virtual network"
3-
description: Access app in Azure Spring Apps in a virtual network.
2+
title: Access your application in a private network
3+
description: Access an app in Azure Spring Apps in a virtual network.
44
author: karlerickson
55
ms.author: karler
66
ms.service: spring-apps
@@ -15,7 +15,7 @@ ms.devlang: azurecli
1515
> [!NOTE]
1616
> Azure Spring Apps is the new name for the Azure Spring Cloud service. Although the service has a new name, you'll see the old name in some places for a while as we work to update assets such as screenshots, videos, and diagrams.
1717
18-
**This article applies to:** ✔️ Basic/Standard tier ✔️ Enterprise tier
18+
**This article applies to:** ✔️ Basic/Standard ✔️ Enterprise
1919

2020
This article explains how to access an endpoint for your application in a private network.
2121

@@ -29,27 +29,30 @@ When **Assign Endpoint** on applications in an Azure Spring Apps service instanc
2929

3030
2. In the **Connected devices** search box, enter *kubernetes-internal*.
3131

32-
3. In the filtered result, find the **Device** connected to the service runtime **Subnet** of the service instance, and copy its **IP Address**. In this sample, the IP Address is *10.1.0.7*.
32+
3. In the filtered result, find the **Device** connected to the **Service Runtime Subnet** of the service instance, and copy its **IP Address**. In this sample, the IP Address is *10.1.0.7*.
33+
34+
> [!WARNING]
35+
> Be sure that the IP Address belongs to **Service Runtime subnet** instead of **Spring Boot microservice apps subnet**. Subnet specifications are provided when you deploy an Azure Spring Apps instance. For more information, see the [Deploy an Azure Spring Apps instance](./how-to-deploy-in-azure-virtual-network.md#deploy-an-azure-spring-apps-instance) section of [Deploy Azure Spring Apps in a virtual network](./how-to-deploy-in-azure-virtual-network.md).
3336
3437
:::image type="content" source="media/spring-cloud-access-app-vnet/create-dns-record.png" alt-text="Screenshot of the Azure portal showing the Connected devices page for a virtual network, filtered for kubernetes-internal devices, with the IP Address for the service runtime subnet highlighted." lightbox="media/spring-cloud-access-app-vnet/create-dns-record.png":::
3538

3639
#### [CLI](#tab/azure-CLI)
3740

3841
Find the IP Address for your Spring Cloud services. Customize the value of your Azure Spring Apps instance name based on your real environment.
3942

40-
```azurecli
41-
SPRING_CLOUD_NAME='spring-cloud-name'
42-
SERVICE_RUNTIME_RG=`az spring show \
43-
--resource-group $RESOURCE_GROUP \
44-
--name $SPRING_CLOUD_NAME \
45-
--query "properties.networkProfile.serviceRuntimeNetworkResourceGroup" \
46-
--output tsv`
47-
IP_ADDRESS=`az network lb frontend-ip list \
48-
--lb-name kubernetes-internal \
49-
--resource-group $SERVICE_RUNTIME_RG \
50-
--query "[0].privateIpAddress" \
51-
--output tsv`
52-
```
43+
```azurecli
44+
SPRING_CLOUD_NAME='spring-cloud-name'
45+
SERVICE_RUNTIME_RG=`az spring show \
46+
--resource-group $RESOURCE_GROUP \
47+
--name $SPRING_CLOUD_NAME \
48+
--query "properties.networkProfile.serviceRuntimeNetworkResourceGroup" \
49+
--output tsv`
50+
IP_ADDRESS=`az network lb frontend-ip list \
51+
--lb-name kubernetes-internal \
52+
--resource-group $SERVICE_RUNTIME_RG \
53+
--query "[0].privateIpAddress" \
54+
--output tsv`
55+
```
5356

5457
---
5558

@@ -58,7 +61,7 @@ Find the IP Address for your Spring Cloud services. Customize the value of your
5861
If you have your own DNS solution for your virtual network, like Active Directory Domain Controller, Infoblox, or another, you need to point the domain `*.private.azuremicroservices.io` to the [IP address](#find-the-ip-for-your-application). Otherwise, you can follow the following instructions to create an **Azure Private DNS Zone** in your subscription to translate/resolve the private fully qualified domain name (FQDN) to its IP address.
5962

6063
> [!NOTE]
61-
> If you are using Azure China, please replace `private.azuremicroservices.io` with `private.microservices.azure.cn` in this article. Learn more about [Check Endpoints in Azure](/azure/china/resources-developer-guide#check-endpoints-in-azure).
64+
> If you're using Azure China, be sure to replace `private.azuremicroservices.io` with `private.microservices.azure.cn` in this article. Learn more about [Check Endpoints in Azure](/azure/china/resources-developer-guide#check-endpoints-in-azure).
6265
6366
## Create a private DNS zone
6467

@@ -111,7 +114,7 @@ To link the private DNS zone to the virtual network, you need to create a virtua
111114

112115
#### [Portal](#tab/azure-portal)
113116

114-
1. Select the private DNS zone resource created above: *private.azuremicroservices.io*
117+
1. Select the private DNS zone resource you created previously: *private.azuremicroservices.io*
115118

116119
2. On the left pane, select **Virtual network links**, then select **Add**.
117120

@@ -127,14 +130,15 @@ To link the private DNS zone to the virtual network, you need to create a virtua
127130

128131
Link the private DNS zone you created to the virtual network holding your Azure Spring Apps service.
129132

130-
```azurecli
131-
az network private-dns link vnet create \
132-
--resource-group $RESOURCE_GROUP \
133-
--name azure-spring-apps-dns-link \
134-
--zone-name private.azuremicroservices.io \
135-
--virtual-network $VIRTUAL_NETWORK_NAME \
136-
--registration-enabled false
137-
```
133+
```azurecli
134+
az network private-dns link vnet create \
135+
--resource-group $RESOURCE_GROUP \
136+
--name azure-spring-apps-dns-link \
137+
--zone-name private.azuremicroservices.io \
138+
--virtual-network $VIRTUAL_NETWORK_NAME \
139+
--registration-enabled false
140+
```
141+
138142
---
139143

140144
## Create DNS record
@@ -143,7 +147,7 @@ To use the private DNS zone to translate/resolve DNS, you must create an "A" typ
143147

144148
#### [Portal](#tab/azure-portal)
145149

146-
1. Select the private DNS zone resource created above: *private.azuremicroservices.io*.
150+
1. Select the private DNS zone resource you created previously: *private.azuremicroservices.io*.
147151

148152
1. Select **Record set**.
149153

@@ -165,13 +169,13 @@ To use the private DNS zone to translate/resolve DNS, you must create an "A" typ
165169

166170
Use the [IP address](#find-the-ip-for-your-application) to create the A record in your DNS zone.
167171

168-
```azurecli
169-
az network private-dns record-set a add-record \
170-
--resource-group $RESOURCE_GROUP \
171-
--zone-name private.azuremicroservices.io \
172-
--record-set-name '*' \
173-
--ipv4-address $IP_ADDRESS
174-
```
172+
```azurecli
173+
az network private-dns record-set a add-record \
174+
--resource-group $RESOURCE_GROUP \
175+
--zone-name private.azuremicroservices.io \
176+
--record-set-name '*' \
177+
--ipv4-address $IP_ADDRESS
178+
```
175179

176180
---
177181

0 commit comments

Comments
 (0)