You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/machine-learning/how-to-connection.md
+18-12Lines changed: 18 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ ms.topic: how-to
9
9
ms.author: franksolomon
10
10
author: fbsolo-ms1
11
11
ms.reviewer: ambadal
12
-
ms.date: 06/19/2023
12
+
ms.date: 07/24/2024
13
13
ms.custom: data4ml, devx-track-azurecli
14
14
# Customer intent: As an experienced data scientist with Python skills, I have data located in external sources outside of Azure. I need to make that data available to the Azure Machine Learning platform, to train my machine learning models.
In this article, you'll learn how to connect to data sources located outside of Azure, to make that data available to Azure Machine Learning services. Azure connections serve as key vault proxies, and interactions with connections are actually direct interactions with an Azure key vault. Azure Machine Learning connections store username and password data resources securely, as secrets, in a key vault. The key vault RBAC controls access to these data resources. For this data availability, Azure supports connections to these external sources:
21
+
In this article, learn how to connect to data sources located outside of Azure, to make that data available to Azure Machine Learning services. Azure connections serve as key vault proxies, and interactions with connections are direct interactions with an Azure key vault. An Azure Machine Learning connection securely stores username and password data resources, as secrets, in a key vault. The key vault RBAC controls access to these data resources. For this data availability, Azure supports connections to these external sources:
22
+
22
23
- Snowflake DB
23
24
- Amazon S3
24
25
- Azure SQL DB
@@ -34,10 +35,10 @@ In this article, you'll learn how to connect to data sources located outside of
34
35
- An Azure Machine Learning workspace.
35
36
36
37
> [!IMPORTANT]
37
-
> An Azure Machine Learning connection securely stores the credentials passed during connection creation in the Workspace Azure Key Vault. A connection references the credentials from the key vault storage location for further use. You won't need to directly deal with the credentials after they are stored in the key vault. You have the option to store the credentials in the YAML file. A CLI command or SDK can override them. We recommend that you **avoid** credential storage in a YAML file, because a security breach could lead to a credential leak.
38
+
> An Azure Machine Learning connection securely stores the credentials passed during connection creation in the Workspace Azure Key Vault. A connection references the credentials from the key vault storage location for further use. You don't need to directly deal with the credentials after they are stored in the key vault. You have the option to store the credentials in the YAML file. A CLI command or SDK can override them. We recommend that you **avoid** credential storage in a YAML file, because a security breach could lead to a credential leak.
38
39
39
40
> [!NOTE]
40
-
> For a successful data import, please verify that you have installed the latest azure-ai-ml package (version 1.5.0 or later) for SDK, and the ml extension (version 2.15.1 or later).
41
+
> For a successful data import, please verify that you installed the latest **azure-ai-ml** package (version 1.5.0 or later) for SDK, and the ml extension (version 2.15.1 or later).
41
42
>
42
43
> If you have an older SDK package or CLI extension, please remove the old one and install the new one with the code shown in the tab section. Follow the instructions for SDK and CLI as shown here:
43
44
@@ -275,7 +276,6 @@ from azure.ai.ml import MLClient, load_workspace_connection
The following connection types can be used to connect to Git, Python feed, Azure Container Registry, and a connection that uses an API key. These connections are not data connections, but are used to connect to external services for use in your code.
321
+
You can use these connection types to connect to Git:
322
+
323
+
- Python feed
324
+
- Azure Container Registry
325
+
- a connection that uses an API key
326
+
327
+
These connections aren't data connections, but are used to connect to external services for use in your code.
322
328
323
329
### Git
324
330
@@ -357,7 +363,7 @@ az ml connection create --file connection.yaml
357
363
358
364
# [Python SDK](#tab/python)
359
365
360
-
The following example creates a Git connection to a GitHub repo. This connection is authenticated with a Personal Access Token (PAT):
366
+
The following example creates a Git connection to a GitHub repo. A Personal Access Token (PAT) authenticates the connection:
361
367
362
368
```python
363
369
from azure.ai.ml.entities import WorkspaceConnection
@@ -387,7 +393,7 @@ You can't create a Git connection in studio.
387
393
388
394
# [Azure CLI](#tab/cli)
389
395
390
-
Create a connection to a Python feed with one of following YAML file. Be sure to update the appropriate values:
396
+
Create a connection to a Python feed with one of following YAML files. Be sure to update the appropriate values:
391
397
392
398
* Connect using a personal access token (PAT):
393
399
@@ -430,7 +436,7 @@ az ml connection create --file connection.yaml
430
436
431
437
# [Python SDK](#tab/python)
432
438
433
-
The following example creates a Python feed connection. This connection is authenticated with a personal access token (PAT) or a username and password:
439
+
The following example creates a Python feed connection. A Personal Access Token (PAT), or a user name and password, authenticates the connection:
434
440
435
441
```python
436
442
from azure.ai.ml.entities import WorkspaceConnection
@@ -463,7 +469,7 @@ You can't create a Python feed connection in studio.
463
469
464
470
# [Azure CLI](#tab/cli)
465
471
466
-
Create a connection to an Azure Container Registry with one of following YAML file. Be sure to update the appropriate values:
472
+
Create a connection to an Azure Container Registry with one of following YAML files. Be sure to update the appropriate values:
467
473
468
474
* Connect using Microsoft Entra ID authentication:
469
475
@@ -497,7 +503,7 @@ az ml connection create --file connection.yaml
497
503
498
504
# [Python SDK](#tab/python)
499
505
500
-
The following example creates an Azure Container Registry connection. This connection is authenticated using a managed identity:
506
+
The following example creates an Azure Container Registry connection. A managed identity authenticates this connection:
501
507
502
508
```python
503
509
from azure.ai.ml.entities import WorkspaceConnection
0 commit comments