Skip to content

Commit 41a92ea

Browse files
committed
revising
1 parent a61e5b1 commit 41a92ea

File tree

1 file changed

+1
-3
lines changed

1 file changed

+1
-3
lines changed

articles/machine-learning/how-to-migrate-from-v1.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -22,9 +22,7 @@ Azure Machine Learning's v2 REST APIs, Azure CLI extension, and Python SDK intro
2222
> [!IMPORTANT]
2323
> The designations "v1" and "v2" refer to the API, SDK, and CLI extension used by clients to interact with the service, and not the Azure Machine Learning service itself. There is no upgrade process for the service or your existing workspaces, only for your client code. Your Azure Machine Learning workspaces can be used with both the v1 and v2 APIs. However, new features will only be available through the v2 APIs.
2424
>
25-
> For example, if you want to use the managed online endpoints feature in Azure Machine Learning, you must use the v2 APIs. If you have existing Python code that deploys models using the v1 SDK, the code would need to be rewritten (or new code developed) against the v2 SDK to use the managed online endpoints feature.
26-
>
27-
> For more information on v2, see [what is v2?](concept-v2.md?view=azureml-api-2&preserve-view=true). For a mapping of differences between v1 and v2 SDKs, with links to articles with example code, see [Mapping of Python SDK v1 to v2](#mapping-of-python-sdk-v1-to-v2).
25+
> For more information on v2, see [what is v2](concept-v2.md?view=azureml-api-2&preserve-view=true). For a mapping of differences between v1 and v2 SDKs, with links to articles with example code, see [Mapping of Python SDK v1 to v2](#mapping-of-python-sdk-v1-to-v2).
2826
2927
## Prerequisites
3028

0 commit comments

Comments
 (0)