Skip to content

Commit 9789858

Browse files
Merge pull request #282053 from Blackmist/fqdn-warning
reducing number of warnings per PM feedback
2 parents fd93ca6 + 5b32f8e commit 9789858

File tree

1 file changed

+1
-25
lines changed

1 file changed

+1
-25
lines changed

articles/ai-studio/how-to/configure-managed-network.md

Lines changed: 1 addition & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ There are three different configuration modes for outbound traffic from the mana
4848
> While you can create a private endpoint for Azure AI Search, the connected services must allow public networking. For more information, see [Connectivity to other services](#connectivity-to-other-services).
4949
5050
* You must add rules for each outbound connection you need to allow.
51-
* Adding FQDN outbound rules __increase your costs__ as this rule type uses Azure Firewall.
51+
* Adding FQDN outbound rules __increase your costs__ as this rule type uses Azure Firewall. If you use outbound FQDN rules, charges for Azure Firewall are included in your billing. For more information, see [Pricing](#pricing).
5252
* The default rules for _allow only approved outbound_ are designed to minimize the risk of data exfiltration. Any outbound rules you add might increase your risk.
5353

5454
The managed virtual network is preconfigured with [required default rules](#list-of-required-rules). It's also configured for private endpoint connections to your hub, the hub's default storage, container registry, and key vault if they're configured as private or the hub isolation mode is set to allow only approved outbound. After choosing the isolation mode, you only need to consider other outbound requirements you might need to add.
@@ -380,9 +380,6 @@ To configure a managed virtual network that allows internet outbound communicati
380380

381381
If the destination type is __FQDN__, provide the following information:
382382

383-
> [!WARNING]
384-
> FQDN outbound rules are implemented using Azure Firewall. If you use outbound FQDN rules, charges for Azure Firewall are included in your billing. For more information, see [Pricing](#pricing).
385-
386383
* __FQDN destination__: The fully qualified domain name to add to the approved outbound rules.
387384

388385
Select __Save__ to save the rule. You can continue using __Add user-defined outbound rules__ to add rules.
@@ -415,9 +412,6 @@ You can also define _outbound rules_ to define approved outbound communication.
415412
> * Adding an outbound for a service tag or FQDN is only valid when the managed VNet is configured to `allow_only_approved_outbound`.
416413
> * If you add outbound rules, Microsoft can't guarantee data exfiltration.
417414

418-
> [!WARNING]
419-
> FQDN outbound rules are implemented using Azure Firewall. If you use outbound FQDN rules, charges for Azure Firewall are added to your billing. For more information, see [Pricing](#pricing).
420-
421415
```yaml
422416
managed_network:
423417
isolation_mode: allow_only_approved_outbound
@@ -476,9 +470,6 @@ You can configure a managed virtual network using either the `az ml workspace cr
476470

477471
The following YAML file defines a managed virtual network for the hub. It also demonstrates how to add an approved outbound to the managed virtual network. In this example, an outbound rule is added for both a service tag:
478472

479-
> [!WARNING]
480-
> FQDN outbound rules are implemented using Azure Firewall. If you use outbound FQDN rules, charges for Azure Firewall are added to your billing. For more information, see [Pricing](#pricing).
481-
482473
```yaml
483474
name: myhub_dep
484475
managed_network:
@@ -522,9 +513,6 @@ To configure a managed virtual network that allows only approved outbound commun
522513
> * Adding an outbound for a service tag or FQDN is only valid when the managed VNet is configured to `IsolationMode.ALLOW_ONLY_APPROVED_OUTBOUND`.
523514
> * If you add outbound rules, Microsoft can't guarantee data exfiltration.
524515

525-
> [!WARNING]
526-
> FQDN outbound rules are implemented using Azure Firewall. If you use outbound FQDN rules, charges for Azure Firewall are added to your billing. For more information, see [Pricing](#pricing).
527-
528516
```python
529517
# Basic managed VNet configuration
530518
network = ManagedNetwork(isolation_mode=IsolationMode.ALLOW_ONLY_APPROVED_OUTBOUND)
@@ -587,9 +575,6 @@ To configure a managed virtual network that allows only approved outbound commun
587575

588576
> [!TIP]
589577
> Adding an outbound for a service tag or FQDN is only valid when the managed VNet is configured to `IsolationMode.ALLOW_ONLY_APPROVED_OUTBOUND`.
590-
591-
> [!WARNING]
592-
> FQDN outbound rules are implemented using Azure Firewall. If you use outbound FQDN rules, charges for Azure Firewall are added to your billing. For more information, see [Pricing](#pricing).
593578

594579
```python
595580
# Get the existing hub
@@ -728,9 +713,6 @@ __Inbound__ service tag rules:
728713

729714
To allow installation of __Python packages for training and deployment__, add outbound _FQDN_ rules to allow traffic to the following host names:
730715

731-
> [!WARNING]
732-
> FQDN outbound rules are implemented using Azure Firewall. If you use outbound FQDN rules, charges for Azure Firewall are included in your billing. For more information, see [Pricing](#pricing).
733-
734716
> [!NOTE]
735717
> This is not a complete list of the hosts required for all Python resources on the internet, only the most commonly used. For example, if you need access to a GitHub repository or other host, you must identify and add the required hosts for that scenario.
736718

@@ -748,9 +730,6 @@ Visual Studio Code relies on specific hosts and ports to establish a remote conn
748730
#### Hosts
749731
If you plan to use __Visual Studio Code__ with the hub, add outbound _FQDN_ rules to allow traffic to the following hosts:
750732

751-
> [!WARNING]
752-
> FQDN outbound rules are implemented using Azure Firewall. If you use outbound FQDN rules, charges for Azure Firewall are included in your billing. For more information, see [Pricing](#pricing).
753-
754733
* `*.vscode.dev`
755734
* `vscode.blob.core.windows.net`
756735
* `*.gallerycdn.vsassets.io`
@@ -773,9 +752,6 @@ You must allow network traffic to ports 8704 to 8710. The VS Code server dynamic
773752

774753
If you plan to use __HuggingFace models__ with the hub, add outbound _FQDN_ rules to allow traffic to the following hosts:
775754

776-
> [!WARNING]
777-
> FQDN outbound rules are implemented using Azure Firewall. If you use outbound FQDN rules, charges for Azure Firewall are included in your billing. For more information, see [Pricing](#pricing).
778-
779755
* docker.io
780756
* *.docker.io
781757
* *.docker.com

0 commit comments

Comments
 (0)