Skip to content

Commit 993cccd

Browse files
authored
Clarify between local and Azure deployment
1 parent f8e6753 commit 993cccd

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

articles/machine-learning/how-to-deploy-online-endpoints.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -622,7 +622,8 @@ Next, deploy your online endpoint to Azure. As a best practice for production, w
622622
Before you deploy your model to Azure, you are advised to register the model and environment in advance and specify their registered names and versions during deployment. This allows you to reuse registered assets without uploading them every time you create deployments, and to increase reproducibility and traceability.
623623

624624
> [!NOTE]
625-
> Unlike deployment to Azure, local deployment doesn't support using registered models and environments. Rather, local deployment uses local model files and environments with local files only. For an example of a deployment configuration that uploads local files to use for local deployment, see [Configure a deployment](#configure-a-deployment).
625+
> Unlike deployment to Azure, local deployment doesn't support using registered models and environments. Rather, local deployment uses local model files and environments with local files only.
626+
> For deployment to Azure, you can use either local model/environment or registered ones. Below example uses registered assets, but you have the option of using the local assets instead. For an example of a deployment configuration that uploads local files to use for local deployment, see [Configure a deployment](#configure-a-deployment).
626627
627628
# [Azure CLI](#tab/cli)
628629

0 commit comments

Comments
 (0)