Create, review, and deploy automated machine learning models with Azure Machine Learning
APPLIES TO: Basic edition Enterprise edition (Upgrade to Enterprise)
In this article, you learn how to create, explore, and deploy automated machine learning models without a single line of code in Azure Machine Learning's studio interface. Automated machine learning is a process in which the best machine learning algorithm to use for your specific data is selected for you. This process enables you to generate machine learning models quickly. Learn more about automated machine learning.
For an end to end example, try the tutorial for creating a classification model with Azure Machine Learning's automated ML interface.
For a Python code-based experience, configure your automated machine learning experiments with the Azure Machine Learning SDK.
An Azure subscription. If you don't have an Azure subscription, create a free account before you begin. Try the free or paid version of Azure Machine Learning today.
An Azure Machine Learning workspace with a type of Enterprise edition. See Create an Azure Machine Learning workspace. To upgrade an existing workspace to Enterprise edition, see Upgrade to Enterprise edition.
Sign in to Azure Machine Learning at https://ml.azure.com.
Select your subscription and workspace.
Navigate to the left pane. Select Automated ML under the Author section.
If this is your first time doing any experiments, you'll see an empty list and links to documentation.
Otherwise, you'll see a list of your recent automated machine learning experiments, including those created with the SDK.
Create and run experiment
Select + New automated ML run and populate the form.
Select a dataset from your storage container, or create a new dataset. Datasets can be created from local files, web urls, datastores, or Azure open datasets.
Requirements for training data:
- Data must be in tabular form.
- The value you want to predict (target column) must be present in the data.
To create a new dataset from a file on your local computer, select Browse and then select the file.
Give your dataset a unique name and provide an optional description.
Select Next to open the Datastore and file selection form. On this form you select where to upload your dataset; the default storage container that's automatically created with your workspace, or choose a storage container that you want to use for the experiment.
Review the Settings and preview form for accuracy. The form is intelligently populated based on the file type.
Field Description File format Defines the layout and type of data stored in a file. Delimiter One or more characters for specifying the boundary between separate, independent regions in plain text or other data streams. Encoding Identifies what bit to character schema table to use to read your dataset. Column headers Indicates how the headers of the dataset, if any, will be treated. Skip rows Indicates how many, if any, rows are skipped in the dataset.
The Schema form is intelligently populated based on the selections in the Settings and preview form. Here configure the data type for each column, review the column names, and select which columns to Not include for your experiment.
The Confirm details form is a summary of the information previously populated in the Basic info and Settings and preview forms. You also have the option to create a data profile for your dataset using a profiling enabled compute. Learn more about data profiling.
Select your newly created dataset once it appears. You are also able to view a preview of the dataset and sample statistics.
On the Configure run form, enter a unique experiment name.
Select a target column; this is the column that you would like to do predictions on.
Select a compute for the data profiling and training job. A list of your existing computes is available in the dropdown. To create a new compute, follow the instructions in step 7.
Select Create a new compute to configure your compute context for this experiment.
Field Description Compute name Enter a unique name that identifies your compute context. Virtual machine size Select the virtual machine size for your compute. Min / Max nodes (in Advanced Settings) To profile data, you must specify 1 or more nodes. Enter the maximum number of nodes for your compute. The default is 6 nodes for an AML Compute.
Select Create. Creation of a new compute can take a few minutes.
Your compute name will indicate if the compute you select/create is profiling enabled. (See the section data profiling for more details).
On the Task type and settings form, select the task type: classification, regression, or forecasting. See how to define task types for more information.
For classification, you can also enable deep learning which is used for text featurizations.
Select time column: This column contains the time data to be used.
Select forecast horizon: Indicate how many time units (minutes/hours/days/weeks/months/years) will the model be able to predict to the future. The further the model is required to predict into the future, the less accurate it will become. Learn more about forecasting and forecast horizon.
(Optional) View addition configuration settings: additional settings you can use to better control the training job. Otherwise, defaults are applied based on experiment selection and data.
Additional configurations Description Primary metric Main metric used for scoring your model. Learn more about model metrics. Automatic featurization Select to enable or disable the featurization done by automated machine learning. Automatic featurization includes automatic data cleansing, preparing, and transformation to generate synthetic features. Not supported for the time series forecasting task type. Learn more about featurization. Explain best model Select to enable or disable to show explainability of the recommended best model Blocked algorithm Select algorithms you want to exclude from the training job. Exit criterion When any of these criteria are met, the training job is stopped.
Training job time (hours): How long to allow the training job to run.
Metric score threshold: Minimum metric score for all pipelines. This ensures that if you have a defined target metric you want to reach, you do not spend more time on the training job than necessary.
Validation Select one of the cross validation options to use in the training job. Learn more about cross validation. Concurrency Max concurrent iterations: Maximum number of pipelines (iterations) to test in the training job. The job will not run more than the specified number of iterations.
(Optional) View featurization settings: if you choose to enable Automatic featurization in the Additional configuration settings form, default featurization techniques are applied. In the View featurization settings you can change these defaults and customize accordingly. Learn how to customize featurizations.
Data profiling & summary stats
You can get a vast variety of summary statistics across your data set to verify whether your data set is ML-ready. For non-numeric columns, they include only basic statistics like min, max, and error count. For numeric columns, you can also review their statistical moments and estimated quantiles. Specifically, our data profile includes:
Blank entries appear for features with irrelevant types.
|Feature||Name of the column that is being summarized.|
|Profile||In-line visualization based on the type inferred. For example, strings, booleans, and dates will have value counts, while decimals (numerics) have approximated histograms. This allows you to gain a quick understanding of the distribution of the data.|
|Type distribution||In-line value count of types within a column. Nulls are their own type, so this visualization is useful for detecting odd or missing values.|
|Type||Inferred type of the column. Possible values include: strings, booleans, dates, and decimals.|
|Min||Minimum value of the column. Blank entries appear for features whose type does not have an inherent ordering (e.g. booleans).|
|Max||Maximum value of the column.|
|Count||Total number of missing and non-missing entries in the column.|
|Not missing count||Number of entries in the column that are not missing. Empty strings and errors are treated as values, so they will not contribute to the "not missing count."|
|Quantiles||Approximated values at each quantile to provide a sense of the distribution of the data.|
|Mean||Arithmetic mean or average of the column.|
|Standard deviation||Measure of the amount of dispersion or variation of this column's data.|
|Variance||Measure of how far spread out this column's data is from its average value.|
|Skewness||Measure of how different this column's data is from a normal distribution.|
|Kurtosis||Measure of how heavily tailed this column's data is compared to a normal distribution.|
In the Featurization form, you can enable/disable automatic featurization and customize the automatic featurization settings for your experiment. To open this form, see step 10 in the Create and run experiment section.
The following table summarizes the customizations currently available via the studio.
|Included||Specifies which columns to include for training.|
|Feature type||Change the value type for the selected column.|
|Impute with||Select what value to impute missing values with in your data.|
Run experiment and view results
Select Finish to run your experiment. The experiment preparing process can take up to 10 minutes. Training jobs can take an additional 2-3 minutes more for each pipeline to finish running.
View experiment details
The Run Detail screen opens to the Details tab. This screen shows you a summary of the experiment run including a status bar at the top next to the run number.
The Models tab contains a list of the models created ordered by the metric score. By default, the model that scores the highest based on the chosen metric is at the top of the list. As the training job tries out more models, they are added to the list. Use this to get a quick comparison of the metrics for the models produced so far.
View training run details
Drill down on any of the completed models to see training run details, like run metrics on the Model details tab or performance charts on the Visualizations tab. Learn more about charts.
Deploy your model
Once you have the best model at hand, it is time to deploy it as a web service to predict on new data.
Automated ML helps you with deploying the model without writing code:
You have a couple options for deployment.
Option 1: To deploy the best model (according to the metric criteria you defined), select the Deploy best model button on the Details tab.
Option 2: To deploy a specific model iteration from this experiment, drill down on the model to open its Model details tab and select Deploy model.
Populate the Deploy model pane.
Field Value Name Enter a unique name for your deployment. Description Enter a description to better identify what this deployment is for. Compute type Select the type of endpoint you want to deploy: Azure Kubernetes Service (AKS) or Azure Container Instance (ACI). Compute name Applies to AKS only: Select the name of the AKS cluster you wish to deploy to. Enable authentication Select to allow for token-based or key-based authentication. Use custom deployment assets Enable this feature if you want to upload your own scoring script and environment file. Learn more about scoring scripts.
File names must be under 32 characters and must begin and end with alphanumerics. May include dashes, underscores, dots, and alphanumerics between. Spaces are not allowed.
The Advanced menu offers default deployment features such as data collection and resource utilization settings. If you wish to override these defaults do so in this menu.
Select Deploy. Deployment can take about 20 minutes to complete. Once deployment begins, the Model details tab appears. See the deployment progress under the Deploy status section of the Properties pane.
Now you have an operational web service to generate predictions! You can test the predictions by querying the service from Power BI's built in Azure Machine Learning support.