Merge pull request #228860 from lgayhardt/amlmovefileslg

 Moving files to V1 folder

Author: JamesJBarnett

articles/machine-learning/.openpublishing.redirection.machine-learning.json

@@ -3714,7 +3714,66 @@
         "source_path_from_root": "/articles/machine-learning/how-to-trigger-published-pipelines.md",
         "redirect_url": "/azure/machine-learning/v1/how-to-trigger-published-pipeline",
         "redirect_document_id": false
+    },
+    {
+        "source_path_from_root": "/articles/machine-learning/how-to-machine-learning-fairness-aml.md",
+        "redirect_url": "/azure/machine-learning/v1/how-to-machine-learning-fairness-aml",
+        "redirect_document_id": true
+    },
+    {
+        "source_path_from_root": "/articles/machine-learning/how-to-machine-learning-interpretability-aml.md",
+        "redirect_url": "/azure/machine-learning/v1/how-to-machine-learning-interpretability-aml",
+        "redirect_document_id": true
+    },
+    {
+        "source_path_from_root": "/articles/machine-learning/how-to-track-designer-experiments.md",
+        "redirect_url": "/azure/machine-learning/v1/how-to-track-designer-experiments",
+        "redirect_document_id": true
+    },
+    {
+        "source_path_from_root": "/articles/machine-learning/migrate-execute-r-script.md",
+        "redirect_url": "/azure/machine-learning/v1/migrate-execute-r-script",
+        "redirect_document_id": true
+    },
+    {
+        "source_path_from_root": "/articles/machine-learning/migrate-overview.md",
+        "redirect_url": "/azure/machine-learning/v1/migrate-overview",
+        "redirect_document_id": true
+    },
+    {
+        "source_path_from_root": "/articles/machine-learning/migrate-rebuild-experiment.md",
+        "redirect_url": "/azure/machine-learning/v1/migrate-rebuild-experiment",
+        "redirect_document_id": true
+    },
+    {
+        "source_path_from_root": "/articles/machine-learning/migrate-rebuild-integrate-with-client-app.md",
+        "redirect_url": "/azure/machine-learning/v1/migrate-rebuild-integrate-with-client-app",
+        "redirect_document_id": true
+    },
+    {
+        "source_path_from_root": "/articles/machine-learning/migrate-rebuild-web-service.md",
+        "redirect_url": "/azure/machine-learning/v1/migrate-rebuild-web-service",
+        "redirect_document_id": true
+    },
+    {
+        "source_path_from_root": "/articles/machine-learning/migrate-register-dataset.md",
+        "redirect_url": "/azure/machine-learning/v1/migrate-register-dataset",
+        "redirect_document_id": true
+    },
+    {
+        "source_path_from_root": "/articles/machine-learning/how-to-change-storage-access-key.md",
+        "redirect_url": "/azure/machine-learning/v1/how-to-change-storage-access-key",
+        "redirect_document_id": true
+    },
+    {
+        "source_path_from_root": "/articles/machine-learning/how-to-high-availability-machine-learning.md",
+        "redirect_url": "/azure/machine-learning/v1/how-to-high-availability-machine-learning",
+        "redirect_document_id": true
+    },
+    {
+        "source_path_from_root": "/articles/machine-learning/overview-what-happened-to-workbench.md",
+        "redirect_url": "/azure/machine-learning",
+        "redirect_document_id": false
     }
-    
 ]
 }

articles/machine-learning/overview-what-happened-to-workbench.md

@@ -14,22 +14,22 @@ ms.custom: cliv1, sdkv1, event-tier1-build-2022, ignite-2022
 ---
 
 # Regenerate storage account access keys
-[!INCLUDE [cli v1](../../includes/machine-learning-dev-v1.md)]
+[!INCLUDE [cli v1](../../../includes/machine-learning-dev-v1.md)]
 
 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.
 
 For security purposes, you may need to change the access keys for an Azure Storage account. When you regenerate the access key, Azure Machine Learning must be updated to use the new key. Azure Machine Learning may be using the storage account for both model storage and as a datastore.
 
 > [!IMPORTANT]
-> Credentials registered with datastores are saved in your Azure Key Vault associated with the workspace. If you have [soft-delete](../key-vault/general/soft-delete-overview.md) enabled for your Key Vault, this article provides instructions for updating credentials. If you unregister the datastore and try to re-register it under the same name, this action will fail. See [Turn on Soft Delete for an existing key vault](../key-vault/general/soft-delete-change.md#turn-on-soft-delete-for-an-existing-key-vault) for how to enable soft delete in this scenario.
+> Credentials registered with datastores are saved in your Azure Key Vault associated with the workspace. If you have [soft-delete](../../key-vault/general/soft-delete-overview.md) enabled for your Key Vault, this article provides instructions for updating credentials. If you unregister the datastore and try to re-register it under the same name, this action will fail. See [Turn on Soft Delete for an existing key vault](../../key-vault/general/soft-delete-change.md#turn-on-soft-delete-for-an-existing-key-vault) for how to enable soft delete in this scenario.
 
 ## Prerequisites
 
-* An Azure Machine Learning workspace. For more information, see the [Create workspace resources](quickstart-create-resources.md) article.
+* An Azure Machine Learning workspace. For more information, see the [Create workspace resources](../quickstart-create-resources.md) article.
 
 * The [Azure Machine Learning SDK](/python/api/overview/azure/ml/install).
 
-* The [Azure Machine Learning CLI extension v1](v1/reference-azure-machine-learning-cli.md).
+* The [Azure Machine Learning CLI extension v1](reference-azure-machine-learning-cli.md).
 
 > [!NOTE]
 > The code snippets in this document were tested with version 1.0.83 of the Python SDK.
@@ -82,7 +82,7 @@ To update Azure Machine Learning to use the new key, use the following steps:
 > [!IMPORTANT]
 > Perform all steps, updating both the workspace using the CLI, and datastores using Python. Updating only one or the other may cause errors until both are updated.
 
-1. Regenerate the key. For information on regenerating an access key, see [Manage storage account access keys](../storage/common/storage-account-keys-manage.md). Save the new key.
+1. Regenerate the key. For information on regenerating an access key, see [Manage storage account access keys](../../storage/common/storage-account-keys-manage.md). Save the new key.
 
 1. The Azure Machine Learning workspace will automatically synchronize the new key and begin using it after an hour. To force the workspace to synch to the new key immediately, use the following steps:
 
@@ -92,15 +92,15 @@ To update Azure Machine Learning to use the new key, use the following steps:
         az login
         ```
 
-        [!INCLUDE [select-subscription](../../includes/machine-learning-cli-subscription.md)]
+        [!INCLUDE [select-subscription](../../../includes/machine-learning-cli-subscription.md)]
 
     1. To update the workspace to use the new key, use the following command. Replace `myworkspace` with your Azure Machine Learning workspace name, and replace `myresourcegroup` with the name of the Azure resource group that contains the workspace.
 
         ```azurecli-interactive
         az ml workspace sync-keys -w myworkspace -g myresourcegroup
         ```
 
-        [!INCLUDE [install extension](../../includes/machine-learning-service-install-extension.md)]
+        [!INCLUDE [install extension](../../../includes/machine-learning-service-install-extension.md)]
 
         This command automatically syncs the new keys for the Azure storage account used by the workspace.