Merge pull request #277448 from dem108/patch-29

prmerger-automator[bot] · web-flow · commit 1eae7cbf861a · 2024-06-18T22:48:02.000Z
Clarify on deployment limitation of classic prebuilt (v1) Designer
diff --git a/articles/machine-learning/concept-designer.md b/articles/machine-learning/concept-designer.md
@@ -21,7 +21,7 @@ Designer in Azure Machine Learning studio is a drag-and-drop user interface for
 > 
 > - **Custom components (v2)** let you wrap your own code as components, enabling sharing across workspaces and seamless authoring across Azure Machine Learning studio, CLI v2, and SDK v2 interfaces. It's best to use custom components for new projects, because they're compatible with Azure Machine Learning v2 and continue to receive new updates.
 > 
-> - **Classic prebuilt components (v1)** support typical data processing and machine learning tasks like regression and classification. Azure Machine Learning continues to support the existing classic prebuilt components, but no new classic prebuilt components are being added. For information about classic prebuilt components and the v1 designer, see [Azure Machine Learning designer (v1)](v1/concept-designer.md?view=azureml-api-1&preserve-view=true).
+> - **Classic prebuilt components (v1)** support typical data processing and machine learning tasks like regression and classification. Azure Machine Learning continues to support the existing classic prebuilt components, but no new classic prebuilt components are being added. Also, deployment of classic prebuilt (v1) components doesn't support managed online endpoints (v2). For more information about classic prebuilt components and the v1 designer, see [Azure Machine Learning designer (v1)](v1/concept-designer.md?view=azureml-api-1&preserve-view=true).
 
 The following animated GIF shows how you can build a pipeline visually in Designer by dragging and dropping assets and connecting them.
 
diff --git a/articles/machine-learning/how-to-create-component-pipelines-ui.md b/articles/machine-learning/how-to-create-component-pipelines-ui.md
@@ -37,7 +37,7 @@ In this article, you'll learn how to create and run [machine learning pipelines]
 >[!Note]
 > Designer supports two types of components, classic prebuilt components（v1） and custom components(v2). These two types of components are NOT compatible.
 >
->Classic prebuilt components provide prebuilt components majorly for data processing and traditional machine learning tasks like regression and classification. This type of component continues to be supported but will not have any new components added. 
+>Classic prebuilt components provide prebuilt components majorly for data processing and traditional machine learning tasks like regression and classification. Classic prebuilt components continue to be supported but won't have any new components added. Also, deployment of classic prebuilt (v1) components doesn't support managed online endpoints (v2).
 >
 >Custom components allow you to wrap your own code as a component. It supports sharing components across workspaces and seamless authoring across studio, CLI v2, and SDK v2 interfaces.
 >
diff --git a/articles/machine-learning/v1/concept-designer.md b/articles/machine-learning/v1/concept-designer.md
@@ -20,7 +20,7 @@ The Azure Machine Learning designer is a drag-and-drop interface used to train a
 > [!IMPORTANT]
 > Designer in Azure Machine Learning supports two types of pipelines that use classic prebuilt (v1) or custom (v2) components. The two component types aren't compatible within pipelines, and designer v1 isn't compatible with CLI v2 and SDK v2. **This article applies to pipelines that use classic prebuilt (v1) components.**
 > 
-> - **Classic prebuilt components (v1)** include typical data processing and machine learning tasks like regression and classification. Azure Machine Learning continues to support the existing classic prebuilt components, but no new prebuilt components are being added.
+> - **Classic prebuilt components (v1)** include typical data processing and machine learning tasks like regression and classification. Azure Machine Learning continues to support the existing classic prebuilt components, but no new prebuilt components are being added. Also, deployment of classic prebuilt (v1) components doesn't support managed online endpoints (v2). 
 > 
 > - **Custom components (v2)** let you wrap your own code as components, enabling sharing across workspaces and seamless authoring across Azure Machine Learning studio, CLI v2, and SDK v2 interfaces. It's best to use custom components for new projects, because they're compatible with Azure Machine Learning v2 and continue to receive new updates. For more information about custom components and Designer (v2), see [Azure Machine Learning designer (v2)](../concept-designer.md?view=azureml-api-2&preserve-view=true).
 

Original file line number	Diff line number	Diff line change
`@@ -21,7 +21,7 @@ Designer in Azure Machine Learning studio is a drag-and-drop user interface for`
`21`	`21`	`>`
`22`	`22`	`> - Custom components (v2) let you wrap your own code as components, enabling sharing across workspaces and seamless authoring across Azure Machine Learning studio, CLI v2, and SDK v2 interfaces. It's best to use custom components for new projects, because they're compatible with Azure Machine Learning v2 and continue to receive new updates.`
`23`	`23`	`>`
`24`		`-> - Classic prebuilt components (v1) support typical data processing and machine learning tasks like regression and classification. Azure Machine Learning continues to support the existing classic prebuilt components, but no new classic prebuilt components are being added. For information about classic prebuilt components and the v1 designer, see [Azure Machine Learning designer (v1)](v1/concept-designer.md?view=azureml-api-1&preserve-view=true).`
	`24`	+> - Classic prebuilt components (v1) support typical data processing and machine learning tasks like regression and classification. Azure Machine Learning continues to support the existing classic prebuilt components, but no new classic prebuilt components are being added. Also, deployment of classic prebuilt (v1) components doesn't support managed online endpoints (v2). For more information about classic prebuilt components and the v1 designer, see [Azure Machine Learning designer (v1)](v1/concept-designer.md?view=azureml-api-1&preserve-view=true).
`25`	`25`
`26`	`26`	`The following animated GIF shows how you can build a pipeline visually in Designer by dragging and dropping assets and connecting them.`
`27`	`27`
Original file line number	Diff line number	Diff line change
`@@ -37,7 +37,7 @@ In this article, you'll learn how to create and run [machine learning pipelines]`
`37`	`37`	`>[!Note]`
`38`	`38`	`> Designer supports two types of components, classic prebuilt components（v1） and custom components(v2). These two types of components are NOT compatible.`
`39`	`39`	`>`
`40`		`->Classic prebuilt components provide prebuilt components majorly for data processing and traditional machine learning tasks like regression and classification. This type of component continues to be supported but will not have any new components added.`
	`40`	`+>Classic prebuilt components provide prebuilt components majorly for data processing and traditional machine learning tasks like regression and classification. Classic prebuilt components continue to be supported but won't have any new components added. Also, deployment of classic prebuilt (v1) components doesn't support managed online endpoints (v2).`
`41`	`41`	`>`
`42`	`42`	`>Custom components allow you to wrap your own code as a component. It supports sharing components across workspaces and seamless authoring across studio, CLI v2, and SDK v2 interfaces.`
`43`	`43`	`>`
Original file line number	Diff line number	Diff line change
`@@ -20,7 +20,7 @@ The Azure Machine Learning designer is a drag-and-drop interface used to train a`
`20`	`20`	`> [!IMPORTANT]`
`21`	`21`	`> Designer in Azure Machine Learning supports two types of pipelines that use classic prebuilt (v1) or custom (v2) components. The two component types aren't compatible within pipelines, and designer v1 isn't compatible with CLI v2 and SDK v2. This article applies to pipelines that use classic prebuilt (v1) components.`
`22`	`22`	`>`
`23`		`-> - Classic prebuilt components (v1) include typical data processing and machine learning tasks like regression and classification. Azure Machine Learning continues to support the existing classic prebuilt components, but no new prebuilt components are being added.`
	`23`	`+> - Classic prebuilt components (v1) include typical data processing and machine learning tasks like regression and classification. Azure Machine Learning continues to support the existing classic prebuilt components, but no new prebuilt components are being added. Also, deployment of classic prebuilt (v1) components doesn't support managed online endpoints (v2).`
`24`	`24`	`>`
`25`	`25`	> - Custom components (v2) let you wrap your own code as components, enabling sharing across workspaces and seamless authoring across Azure Machine Learning studio, CLI v2, and SDK v2 interfaces. It's best to use custom components for new projects, because they're compatible with Azure Machine Learning v2 and continue to receive new updates. For more information about custom components and Designer (v2), see [Azure Machine Learning designer (v2)](../concept-designer.md?view=azureml-api-2&preserve-view=true).
`26`	`26`