Skip to content

Commit 35c5d7e

Browse files
authored
Merge branch 'MicrosoftDocs:main' into Broken-link-fix-TOC
2 parents 0f11faa + bfeed81 commit 35c5d7e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/machine-learning/concept-endpoints.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ In this article, you learn about:
3333

3434
After you train a machine learning model, you need to deploy the model so that others can use it to do inferencing. In Azure Machine Learning, you can use **endpoints** and **deployments** to do so.
3535

36-
An **endpoint** is an HTTPS endpoint that clients can call to receive the inferencing (scoring) output of a trained model. It provides:
36+
An **endpoint**, in this context, is an HTTPS path that provides an interface for clients to send requests (input data) and receive the inferencing (scoring) output of a trained model. An endpoint provides:
3737
- Authentication using "key & token" based auth
3838
- SSL termination
3939
- A stable scoring URI (endpoint-name.region.inference.ml.azure.com)
@@ -43,7 +43,7 @@ A **deployment** is a set of resources required for hosting the model that does
4343

4444
A single endpoint can contain multiple deployments. Endpoints and deployments are independent Azure Resource Manager resources that appear in the Azure portal.
4545

46-
Azure Machine Learning uses the concept of endpoints and deployments to implement different types of endpoints: [online endpoints](#what-are-online-endpoints) and [batch endpoints](#what-are-batch-endpoints).
46+
Azure Machine Learning allows you to implement both [online endpoints](#what-are-online-endpoints) and [batch endpoints](#what-are-batch-endpoints).
4747

4848
### Multiple developer interfaces
4949

0 commit comments

Comments
 (0)