Skip to content

Commit 1ff99a4

Browse files
authored
Update how-to-side-by-side-migrate.md
1 parent fb0cab3 commit 1ff99a4

File tree

1 file changed

+10
-2
lines changed

1 file changed

+10
-2
lines changed

articles/app-service/environment/how-to-side-by-side-migrate.md

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -233,10 +233,18 @@ You have two App Service Environments at this stage in the migration process. Yo
233233
> During the preview, the new inbound IP might be returned incorrectly due to a known bug. Open a support ticket to receive the correct IP addresses for your App Service Environment v3.
234234
>
235235
236-
You can get the new inbound IP address for your new App Service Environment v3 by running the following command. It's your responsibility to make any necessary updates.
236+
You can get the new inbound IP address for your new App Service Environment v3 by running the following command that corresponds to your App Service Environment load balancer type. It's your responsibility to make any necessary updates.
237+
238+
For ILB App Service Environments, get the private inbound IP address by running the following command:
239+
240+
```azurecli
241+
az rest --method get --uri "${ASE_ID}?api-version=2022-03-01" --query properties.internalInboundIpAddresses
242+
```
243+
244+
For ELB App Service Environments, get the public inbound IP address by running the following command:
237245

238246
```azurecli
239-
az rest --method get --uri "${ASE_ID}?api-version=2022-03-01" --query properties.networkingConfiguration
247+
az rest --method get --uri "${ASE_ID}?api-version=2022-03-01" --query properties.externalInboundIpAddresses
240248
```
241249

242250
## 11. Redirect customer traffic and complete migration

0 commit comments

Comments
 (0)