Skip to content

Commit f94380d

Browse files
authored
Merge pull request #47894 from tdykstra/patch-66
remove link to diagnostics panel
2 parents 0e6aa97 + 74564d8 commit f94380d

File tree

1 file changed

+0
-8
lines changed

1 file changed

+0
-8
lines changed

articles/azure-functions/ip-addresses.md

Lines changed: 0 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -35,20 +35,12 @@ Each function app has a single inbound IP address. To find that IP address:
3535
3. Select **Platform features**.
3636
4. Select **Properties**, and the inbound IP address appears under **Virtual IP address**.
3737

38-
Under **Platform features**, an alternative way to find IP addresses is to select **Diagnose and Solve Problems > Check IP Configuration**.
39-
4038
## Function app outbound IP addresses
4139

4240
Each function app has a set of available outbound IP addresses. Any outbound connection from a function, such as to a back-end database, uses one of the available outbound IP addresses as the origin IP address. You can't know beforehand which IP address a given connection will use. For this reason, your back-end service must open its firewall to all of the function app's outbound IP addresses.
4341

4442
To find the outbound IP addresses available to a function app:
4543

46-
1. Sign in to the [Azure portal](https://portal.azure.com).
47-
2. Navigate to the function app.
48-
3. Select **Platform features > Diagnose and Solve Problems > Check IP Configuration**.
49-
50-
To find the IP addresses that would be available when the function app scales to other pricing tiers:
51-
5244
1. Sign in to the [Azure Resource Explorer](https://resources.azure.com).
5345
2. Select **subscriptions > {your subscription} > providers > Microsoft.Web > sites**.
5446
3. In the JSON panel, find the site with an `id` property that ends in the name of your function app.

0 commit comments

Comments
 (0)