Skip to content

Commit 2477bb9

Browse files
author
Larry Franks
committed
updating form link
1 parent 372516c commit 2477bb9

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/machine-learning/how-to-secure-training-vnet.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -122,7 +122,7 @@ In this article you learn how to secure the following training compute resources
122122
> [!IMPORTANT]
123123
> On October TBD, the public preview for no public IP configuration for compute cluster and compute instance moved to a new architecture. This new architecture removes limitations, such as the requirement for inbound access from the Azure Batch management and Azure Machine Learning services. However, the new architecture requires you to opt-in. Before opting in to this preview, you must have created a workspace and a compute instance on the subscription you plan to use. You can delete the compute instance and/or workspace after creating them.
124124
>
125-
> Use the form at [https://forms.office.com/r/1TraBek7LV](https://forms.office.com/r/1TraBek7LV) to opt in to this Azure Machine Learning preview. Microsoft will contact you once your subscription has been allowlisted to the preview. It may take one to two weeks to allowlist your subscription.
125+
> Use the form at [https://forms.office.com/r/0Rw6mXTT07](https://forms.office.com/r/0Rw6mXTT07) to opt in to this Azure Machine Learning preview. Microsoft will contact you once your subscription has been allowlisted to the preview. It may take one to two weeks to allowlist your subscription.
126126
127127
> [!TIP]
128128
> If you have existing compute instances configured for no public IP, you will need to delete and recreate them after your subscription has been allowlisted to take advantage of the new architecture. For existing compute clusters configured for no public IP, once the cluster has been reduced to 0 nodes (requires the minimum nodes to be configured as 0), it will take advantage of the new architecture the next time nodes are allocated after the subscription is allowlisted.

0 commit comments

Comments
 (0)