Skip to content

Commit f654de5

Browse files
committed
Acrolinx fixes
1 parent a97c84a commit f654de5

File tree

2 files changed

+109
-106
lines changed

2 files changed

+109
-106
lines changed

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

Lines changed: 37 additions & 36 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

@@ -31,28 +31,28 @@ When **Assign Endpoint** on applications in an Azure Spring Apps service instanc
3131

3232
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*.
3333

34-
> [!Warning]
35-
> Please make sure the IP Address belongs to **Service Runtime subnet** instead of **Spring Boot microservice apps subnet**. (Subnet specifications are provided when [Deploy an Azure Spring Apps instance](./how-to-deploy-in-azure-virtual-network.md#deploy-an-azure-spring-apps-instance).
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).
3636
3737
:::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":::
3838

3939
#### [CLI](#tab/azure-CLI)
4040

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

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-
```
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+
```
5656

5757
---
5858

@@ -61,7 +61,7 @@ Find the IP Address for your Spring Cloud services. Customize the value of your
6161
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.
6262

6363
> [!NOTE]
64-
> 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).
6565
6666
## Create a private DNS zone
6767

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

115115
#### [Portal](#tab/azure-portal)
116116

117-
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*
118118

119119
2. On the left pane, select **Virtual network links**, then select **Add**.
120120

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

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

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-
```
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+
141142
---
142143

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

147148
#### [Portal](#tab/azure-portal)
148149

149-
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*.
150151

151152
1. Select **Record set**.
152153

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

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

171-
```azurecli
172-
az network private-dns record-set a add-record \
173-
--resource-group $RESOURCE_GROUP \
174-
--zone-name private.azuremicroservices.io \
175-
--record-set-name '*' \
176-
--ipv4-address $IP_ADDRESS
177-
```
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+
```
178179

179180
---
180181

0 commit comments

Comments
 (0)