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
Learn how to change the access keys for Azure Storage accounts used by Azure Machine Learning. Azure Machine Learning can use storage accounts to store data or trained models.
20
20
@@ -100,7 +100,7 @@ To update Azure Machine Learning to use the new key, use the following steps:
100
100
az ml workspace sync-keys -w myworkspace -g myresourcegroup
Copy file name to clipboardExpand all lines: articles/machine-learning/v1/how-to-high-availability-machine-learning.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -107,7 +107,7 @@ Depending on your needs, you may have more compute or data services that are use
107
107
108
108
__Compute resources__
109
109
110
-
***Azure Kubernetes Service**: See [Best practices for business continuity and disaster recovery in Azure Kubernetes Service (AKS)](../aks/operator-best-practices-multi-region.md) and [Create an Azure Kubernetes Service (AKS) cluster that uses availability zones](../aks/availability-zones.md). If the AKS cluster was created by using the Azure Machine Learning Studio, SDK, or CLI, cross-region high availability is not supported.
110
+
***Azure Kubernetes Service**: See [Best practices for business continuity and disaster recovery in Azure Kubernetes Service (AKS)](../../aks/operator-best-practices-multi-region.md) and [Create an Azure Kubernetes Service (AKS) cluster that uses availability zones](../../aks/availability-zones.md). If the AKS cluster was created by using the Azure Machine Learning Studio, SDK, or CLI, cross-region high availability is not supported.
111
111
***Azure Databricks**: See [Regional disaster recovery for Azure Databricks clusters](/azure/databricks/scenarios/howto-regional-disaster-recovery).
112
112
***Container Instances**: An orchestrator is responsible for failover. See [Azure Container Instances and container orchestrators](../../container-instances/container-instances-orchestrator-relationship.md).
113
113
***HDInsight**: See [High availability services supported by Azure HDInsight](../../hdinsight/hdinsight-high-availability-components.md).
@@ -153,7 +153,7 @@ Jobs in Azure Machine Learning are defined by a job specification. This specific
153
153
154
154
* Manage configurations as code.
155
155
156
-
* Avoid hardcoded references to the workspace. Instead, configure a reference to the workspace instance using a [config file](../how-to-configure-environment.md#local-and-dsvm-only-create-a-workspace-configuration-file) and use [Workspace.from_config()](/python/api/azureml-core/azureml.core.workspace.workspace#remarks) to initialize the workspace. To automate the process, use the [Azure CLI extension for machine learning](v1/reference-azure-machine-learning-cli.md) command [az ml folder attach](/cli/azure/ml(v1)/folder#az-ml(v1)-folder-attach).
156
+
* Avoid hardcoded references to the workspace. Instead, configure a reference to the workspace instance using a [config file](../how-to-configure-environment.md#local-and-dsvm-only-create-a-workspace-configuration-file) and use [Workspace.from_config()](/python/api/azureml-core/azureml.core.workspace.workspace#remarks) to initialize the workspace. To automate the process, use the [Azure CLI extension for machine learning](reference-azure-machine-learning-cli.md) command [az ml folder attach](/cli/azure/ml(v1)/folder#az-ml(v1)-folder-attach).
157
157
* Use job submission helpers such as [ScriptRunConfig](/python/api/azureml-core/azureml.core.scriptrunconfig) and [Pipeline](/python/api/azureml-pipeline-core/azureml.pipeline.core.pipeline(class)).
158
158
* Use [Environments.save_to_directory()](/python/api/azureml-core/azureml.core.environment(class)#save-to-directory-path--overwrite-false-) to save your environment definitions.
159
159
* Use a Dockerfile if you use custom Docker images.
@@ -177,7 +177,7 @@ Azure Machine Learning cannot sync or recover artifacts or metadata between work
177
177
178
178
Depending on your recovery approach, you may need to copy artifacts such as dataset and model objects between the workspaces to continue your work. Currently, the portability of artifacts between workspaces is limited. We recommend managing artifacts as code where possible so that they can be recreated in the failover instance.
179
179
180
-
The following artifacts can be exported and imported between workspaces by using the [Azure CLI extension for machine learning](v1/reference-azure-machine-learning-cli.md):
180
+
The following artifacts can be exported and imported between workspaces by using the [Azure CLI extension for machine learning](reference-azure-machine-learning-cli.md):
In this how-to guide, you will learn to use the [Fairlearn](https://fairlearn.github.io/) open-source Python package with Azure Machine Learning to perform the following tasks:
21
21
22
-
* Assess the fairness of your model predictions. To learn more about fairness in machine learning, see the [fairness in machine learning article](concept-fairness-ml.md).
22
+
* Assess the fairness of your model predictions. To learn more about fairness in machine learning, see the [fairness in machine learning article](../concept-fairness-ml.md).
23
23
* Upload, list and download fairness assessment insights to/from Azure Machine Learning studio.
24
24
* See a fairness assessment dashboard in Azure Machine Learning studio to interact with your model(s)' fairness insights.
25
25
26
26
>[!NOTE]
27
27
> Fairness assessment is not a purely technical exercise. **This package can help you assess the fairness of a machine learning model, but only you can configure and make decisions as to how the model performs.** While this package helps to identify quantitative metrics to assess fairness, developers of machine learning models must also perform a qualitative analysis to evaluate the fairness of their own models.
For more information on the supported interpretability techniques and machine learning models, see [Model interpretability in Azure Machine Learning](../how-to-machine-learning-interpretability.md) and [sample notebooks](https://github.com/Azure/MachineLearningNotebooks/tree/master/how-to-use-azureml/explain-model).
Copy file name to clipboardExpand all lines: articles/machine-learning/v1/migrate-overview.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -50,7 +50,7 @@ To migrate to Azure Machine Learning, we recommend the following approach:
50
50
>[!NOTE]
51
51
> The **designer** feature in Azure Machine Learning provides a similar drag-and-drop experience to Studio (classic). However, Azure Machine Learning also provides robust [code-first workflows](../concept-model-management-and-deployment.md) as an alternative. This migration series focuses on the designer, since it's most similar to the Studio (classic) experience.
3. Verify that your critical Studio (classic) modules are supported in Azure Machine Learning designer. For more information, see the [Studio (classic) and designer component-mapping](#studio-classic-and-designer-component-mapping) table below.
Copy file name to clipboardExpand all lines: articles/machine-learning/v1/migrate-rebuild-web-service.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ Use Azure Machine Learning pipeline endpoints to make predictions, retrain model
23
23
This article is part of the Studio (classic) to Azure Machine Learning migration series. For more information on migrating to Azure Machine Learning, see the [migration overview article](migrate-overview.md).
24
24
25
25
> [!NOTE]
26
-
> This migration series focuses on the drag-and-drop designer. For more information on deploying models programmatically, see [Deploy machine learning models in Azure](v1/how-to-deploy-and-where.md).
26
+
> This migration series focuses on the drag-and-drop designer. For more information on deploying models programmatically, see [Deploy machine learning models in Azure](how-to-deploy-and-where.md).
Copy file name to clipboardExpand all lines: articles/machine-learning/v1/migrate-register-dataset.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -82,7 +82,7 @@ After you download the data file, you can register it as a data asset in Azure M
82
82
1. Navigate to [Azure Machine Learning studio](https://ml.azure.com)
83
83
84
84
1. Under __Assets__ in the left navigation, select __Data__. On the Data assets tab, select Create
85
-
:::image type="content" source="./media/how-to-create-data-assets/data-assets-create.png" alt-text="Screenshot highlights Create in the Data assets tab.":::
85
+
:::image type="content" source="./media/migrate-register-dataset/data-assets-create-2.png" alt-text="Screenshot highlights Create in the Data assets tab.":::
86
86
87
87
1. Give your data asset a name and optional description. Then, select the **Tabular** option under **Type**, in the **Dataset types** section of the dropdown.
0 commit comments