Clarify on deployment limitation of classic prebuilt (v1) Designer

dem108 · web-flow · commit d7207baefb4c · 2024-06-06T09:05:13.000-07:00
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 endpoint (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
`@@ -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 endpoint (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`