We are excited to introduce the GA of Azure Machine Learning Python SDK v2. The Python SDK v2 introduces new SDK capabilities like standalone local jobs, reusable components for pipelines and managed online/batch inferencing. Python SDK v2 allows you to move from simple to complex tasks easily and incrementally. This is enabled by using a common object model which brings concept reuse and consistency of actions across various tasks. The SDK v2 shares its foundation with the CLI v2 which is also GA.

Source code|Package (PyPI)|Package (Conda)|API reference documentation|Product documentation|Samples

This package has been tested with Python 3.8, 3.9, 3.10, 3.11, 3.12 and 3.13.

For a more complete set of Azure libraries, seehttps://aka.ms/azsdk/python/all

Getting started

Prerequisites

• Python 3.7 or later is required to use this package.
• You must have anAzure subscription.
• AnAzure Machine Learning Workspace.

Install the package

Install the Azure ML client library for Python withpip:

pip install azure-ai-mlpip install azure-identity

Authenticate the client

from azure.ai.ml import MLClientfrom azure.identity import DefaultAzureCredentialml_client = MLClient(    DefaultAzureCredential(), subscription_id, resource_group, workspace)

Key concepts

Refer the below high level sequence diagram illustrating the package's workflow:

SDK Architecture Components

The sequence diagram above illustrates the architecture and workflow of the Azure ML Python SDK v2. Here's an explanation of the key components:

• User: You, the developer using the SDK to interact with Azure ML.
• Entity: Python classes representing Azure ML resources like Jobs, Models, Components, etc.
• Schema: Validation classes that ensure entities conform to expected structures and requirements.
• MLClient: The main entry point for all operations, providing access to various services.
• Operations: Specialized classes handling specific resource types (jobs, models, endpoints, etc.).
• Telemetry: Internal component for monitoring and collecting usage data (opt-out available).
• Serialization: Converts between Python objects and REST API formats.
• REST Client: Manages HTTP communications with Azure ML services.
• Authentication: Handles identity and access tokens via Azure Identity libraries.
• AzureML Service: The backend Azure Machine Learning service.

Workflow Description

The diagram depicts two main workflows:

1. Entity Creation and Validation:

   • Create entities directly using Python classes or load from YAML files
   • YAML files are validated against schemas to ensure correctness
   • Validation errors are reported immediately if found

2. Operation Execution:

   • Initialize MLClient with proper credentials
   • Request operations through the client (create, get, list, delete, etc.)
   • Operations are routed to specialized classes for handling
   • Entities are serialized into REST API format
   • Authenticated HTTP requests are sent to Azure ML services
   • Responses are deserialized back into entity objects
   • Results are returned to the user

Azure Machine Learning Python SDK v2 comes with many new features like standalone local jobs, reusable components for pipelines and managed online/batch inferencing. The SDK v2 brings consistency and ease of use across all assets of the platform. The Python SDK v2 offers the following capabilities:

• RunStandalone Jobs - run a discrete ML activity as Job. This job can be run locally or on the cloud. We currently support the following types of jobs:
  • Command - run a command (Python, R, Windows Command, Linux Shell etc.)
  • Sweep - run a hyperparameter sweep on your Command
• Run multiple jobs using ourimproved Pipelines
  • Run a series of commands stitched into a pipeline (New)
  • Components - run pipelines using reusable components (New)
• Use your models forManaged Online inferencing (New)
• Use your models for Managedbatch inferencing
• Manage AML resources – workspace, compute, datastores
• Manage AML assets - Datasets, environments, models
• AutoML - run standalone AutoML training for various ml-tasks:
  • Classification (Tabular data)
  • Regression (Tabular data)
  • Time Series Forecasting (Tabular data)
  • Image Classification (Multi-class) (New)
  • Image Classification (Multi-label) (New)
  • Image Object Detection (New)
  • Image Instance Segmentation (New)
  • NLP Text Classification (Multi-class) (New)
  • NLP Text Classification (Multi-label) (New)
  • NLP Text Named Entity Recognition (NER) (New)

Examples

• View oursamples.

Troubleshooting

General

Azure ML clients raise exceptions defined inAzure Core.

from azure.core.exceptions import HttpResponseErrortry:    ml_client.compute.get("cpu-cluster")except HttpResponseError as error:    print("Request failed: {}".format(error.message))

Logging

This library uses the standardlogging library for logging.Basic information about HTTP sessions (URLs, headers, etc.) is logged at INFOlevel.

Detailed DEBUG level logging, including request/response bodies and unredactedheaders, can be enabled on a client with thelogging_enable argument.

See full SDK logging documentation with exampleshere.

Telemetry

The Azure ML Python SDK includes a telemetry feature that collects usage and failure data about the SDK and sends it to Microsoft when you use the SDK in a Jupyter Notebook only.Telemetry willnot be collected for any use of the Python SDK outside of a Jupyter Notebook.

Telemetry data helps the SDK team understand how the SDK is used so it can be improved and the information about failures helps the team resolve problems and fix bugs.The SDK telemetry feature is enabled by default for Jupyter Notebook usage and cannot be enabled for non-Jupyter scenarios. To opt out of the telemetry feature in a Jupyter scenario, pass inenable_telemetry=False when constructing your MLClient object.

Next steps

• View oursamples.

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visitcla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted theMicrosoft Open Source Code of Conduct. For more information see theCode of Conduct FAQ or contactopencode@microsoft.com with any additional questions or comments.