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/ai-foundry/how-to/configure-private-link.md
+62Lines changed: 62 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -257,6 +257,68 @@ az extension add --name ml
257
257
258
258
---
259
259
260
+
## Enable Public Access only from internet IP ranges
261
+
262
+
You can use IP network rules to allow access to your secured hub from specific public internet IP address ranges by creating IP network rules. Each Azure AI Foundry hub supports up to 200 rules. These rules grant access to specific internet-based services and on-premises networks and block general internet traffic.
263
+
264
+
> [!WARNING]
265
+
> * Enable your endpoint's public network access flag if you want to allow access to your endpoint from specific public internet IP address ranges.
266
+
> * You can only use IPv4 addresses.
267
+
268
+
# [Portal](#tab/azure-portal)
269
+
270
+
1. From the [Azure portal](https://portal.azure.com), select your Azure Machine AI Foundry hub.
271
+
1. From the left side of the page, select __Networking__ and then select the __Public access__ tab.
272
+
1. Select __Enabled from selected IP addresses__, input address ranges and then select __Save__.
273
+
274
+
<!-- :::image type="content" source="./media/how-to-configure-private-link/workspace-public-access-ip-ranges.png" alt-text="Screenshot of the UI to enable access from internet IP ranges."::: -->
275
+
276
+
# [Azure CLI](#tab/cli)
277
+
278
+
279
+
Use the `az ml workspace network-rule` Azure CLI command to manage public access from an IP address or address range:
280
+
281
+
> [!TIP]
282
+
> The configurations for the selected IP addresses are stored in the hub's properties, under `network_acls`:
283
+
> ```yml
284
+
> properties:
285
+
> # ...
286
+
> network_acls:
287
+
> description: "The network ACLS for this hub, enforced when public_network_access is set to Enabled."
288
+
> $ref: "3/defintions/networkAcls"
289
+
> ```
290
+
291
+
- __List IP network rules__: `az ml workspace network-rule list --resource-group "myresourcegroup" --workspace-name "myWS" --query ipRules`
292
+
- __Add a rule for a single IP address__: `az ml workspace network-rule add --resource-group "myresourcegroup" --workspace-name "myWS" --ip-address "16.17.18.19"`
293
+
- __Add a rule for an IP address range__: `az ml workspace network-rule add --resource-group "myresourcegroup" --workspace-name "myWS" --ip-address "16.17.18.0/24"`
294
+
- __Remove a rule for a single IP address__: `az ml workspace network-rule remove --resource-group "myresourcegroup" --workspace-name "myWS" --ip-address "16.17.18.19"`
295
+
- __Remove a rule for an IP address range__: `az ml workspace network-rule remove --resource-group "myresourcegroup" --workspace-name "myWS" --ip-address "16.17.18.0/24"`
296
+
297
+
---
298
+
299
+
You can also use the [Workspace](/python/api/azure-ai-ml/azure.ai.ml.entities.workspace) class from the Azure Machine Learning [Python SDK](/python/api/overview/azure/ai-ml-readme) to define which IP addresses are allowed inbound access:
The following restrictions apply to IP address ranges:
310
+
311
+
- IP network rules are allowed only for _public internet_ IP addresses.
312
+
313
+
[Reserved IP address ranges](https://en.wikipedia.org/wiki/Reserved_IP_addresses) aren't allowed in IP rules such as private addresses that start with 10, 172.16 to 172.31, and 192.168.
314
+
315
+
- You must provide allowed internet address ranges by using [CIDR notation](https://tools.ietf.org/html/rfc4632) in the form 16.17.18.0/24 or as individual IP addresses like 16.17.18.19.
316
+
317
+
- Only IPv4 addresses are supported for configuration of storage firewall rules.
318
+
319
+
- When this feature is enabled, you can test public endpoints using any client tool such as Curl, but the Endpoint Test tool in the portal isn't supported.
320
+
321
+
- You can only set the IP addresses for the workspace after the workspace has been created.
0 commit comments