You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/app-service/environment/how-to-side-by-side-migrate.md
+10-2Lines changed: 10 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -233,10 +233,18 @@ You have two App Service Environments at this stage in the migration process. Yo
233
233
> 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.
234
234
>
235
235
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:
237
245
238
246
```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
240
248
```
241
249
242
250
## 11. Redirect customer traffic and complete migration
0 commit comments