Skip to content

Commit fbe4c3d

Browse files
authored
add web sockets info for compute instance
1 parent b0710a7 commit fbe4c3d

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

articles/machine-learning/how-to-enable-virtual-network.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -84,6 +84,7 @@ To use either a [managed Azure Machine Learning **compute target**](concept-comp
8484
> * Check to see whether your security policies or locks on the virtual network's subscription or resource group restrict permissions to manage the virtual network. If you plan to secure the virtual network by restricting traffic, leave some ports open for the compute service. For more information, see the [Required ports](#mlcports) section.
8585
> * If you're going to put multiple compute instances or clusters in one virtual network, you might need to request a quota increase for one or more of your resources.
8686
> * If the Azure Storage Account(s) for the workspace are also secured in a virtual network, they must be in the same virtual network as the Azure Machine Learning compute instance or cluster.
87+
> * For compute instance Jupyter functionality to work, please ensure that web socket communication is not disabled.
8788
8889
> [!TIP]
8990
> The Machine Learning compute instance or cluster automatically allocates additional networking resources __in the resource group that contains the virtual network__. For each compute instance or cluster, the service allocates the following resources:

0 commit comments

Comments
 (0)