Merge pull request #226385 from Blackmist/fix0206-1

prmerger-automator[bot] · web-flow · commit 297beebed947 · 2023-02-06T14:11:11.000Z
adding year
diff --git a/articles/machine-learning/how-to-secure-training-vnet.md b/articles/machine-learning/how-to-secure-training-vnet.md
@@ -97,7 +97,7 @@ In this article you learn how to secure the following training compute resources
 ## Compute instance/cluster with no public IP
 
 > [!IMPORTANT]
-> If you have been using compute instances or compute clusters configured for no public IP without opting-in to the preview, you will need to delete and recreate them after January 20 (when the feature is generally available).
+> If you have been using compute instances or compute clusters configured for no public IP without opting-in to the preview, you will need to delete and recreate them after January 20, 2023 (when the feature is generally available).
 > 
 > If you were previously using the preview of no public IP, you may also need to modify what traffic you allow inbound and outbound, as the requirements have changed for general availability:
 > * Outbound requirements - Two additional outbound, which are only used for the management of compute instances and clusters. The destination of these service tags are owned by Microsoft:
diff --git a/articles/machine-learning/v1/how-to-secure-training-vnet.md b/articles/machine-learning/v1/how-to-secure-training-vnet.md
@@ -107,7 +107,7 @@ For more information on using Azure Databricks in a virtual network, see [Deploy
 ## Compute instance/cluster with no public IP
 
 > [!IMPORTANT]
-> If you have been using compute instances or compute clusters configured for no public IP without opting-in to the preview, you will need to delete and recreate them after January 20 (when the feature is generally available).
+> If you have been using compute instances or compute clusters configured for no public IP without opting-in to the preview, you will need to delete and recreate them after January 20, 2023 (when the feature is generally available).
 > 
 > If you were previously using the preview of no public IP, you may also need to modify what traffic you allow inbound and outbound, as the requirements have changed for general availability:
 > * Outbound requirements - Two additional outbound, which are only used for the management of compute instances and clusters. The destination of these service tags are owned by Microsoft:

Original file line number	Diff line number	Diff line change
`@@ -97,7 +97,7 @@ In this article you learn how to secure the following training compute resources`
`97`	`97`	`## Compute instance/cluster with no public IP`
`98`	`98`
`99`	`99`	`> [!IMPORTANT]`
`100`		`-> If you have been using compute instances or compute clusters configured for no public IP without opting-in to the preview, you will need to delete and recreate them after January 20 (when the feature is generally available).`
	`100`	`+> If you have been using compute instances or compute clusters configured for no public IP without opting-in to the preview, you will need to delete and recreate them after January 20, 2023 (when the feature is generally available).`
`101`	`101`	`>`
`102`	`102`	`> If you were previously using the preview of no public IP, you may also need to modify what traffic you allow inbound and outbound, as the requirements have changed for general availability:`
`103`	`103`	`> * Outbound requirements - Two additional outbound, which are only used for the management of compute instances and clusters. The destination of these service tags are owned by Microsoft:`
Original file line number	Diff line number	Diff line change
`@@ -107,7 +107,7 @@ For more information on using Azure Databricks in a virtual network, see [Deploy`
`107`	`107`	`## Compute instance/cluster with no public IP`
`108`	`108`
`109`	`109`	`> [!IMPORTANT]`
`110`		`-> If you have been using compute instances or compute clusters configured for no public IP without opting-in to the preview, you will need to delete and recreate them after January 20 (when the feature is generally available).`
	`110`	`+> If you have been using compute instances or compute clusters configured for no public IP without opting-in to the preview, you will need to delete and recreate them after January 20, 2023 (when the feature is generally available).`
`111`	`111`	`>`
`112`	`112`	`> If you were previously using the preview of no public IP, you may also need to modify what traffic you allow inbound and outbound, as the requirements have changed for general availability:`
`113`	`113`	`> * Outbound requirements - Two additional outbound, which are only used for the management of compute instances and clusters. The destination of these service tags are owned by Microsoft:`