renaming resource-create article to storage-mover-create and fixing all associated links

fauhse · fauhse · commit 72a26fedb9f9 · 2022-09-12T13:37:12.000-07:00
diff --git a/articles/storage-mover/TOC.yml b/articles/storage-mover/TOC.yml
@@ -19,7 +19,7 @@ items:
   - name: Deploy
     items: 
     - name: Create a storage mover resource
-      href: resource-create.md
+      href: storage-mover-create.md
     - name: Deploy a storage mover agent
       href: agent-deploy.md
   - name: Manage
diff --git a/articles/storage-mover/agent-register.md b/articles/storage-mover/agent-register.md
@@ -29,7 +29,7 @@ In this article you'll learn how to successfully register a previously deployed
 ## Prerequisites
 
 There are two prerequisites before you can register an Azure Storage Mover agent:
-1. You need to have an Azure Storage Mover resource deployed. <br />Follow the steps in the *[Create a storage mover resource](resource-create.md)* article to deploy this resource in an Azure subscription and region of your choice. <!-- In the Azure portal, open the portal menu (tope left corner) and select *Create a resource*. Search for *Azure Storage Mover* and select *Create*. The article *Create a storage mover resource* has more details. -->
+1. You need to have an Azure Storage Mover resource deployed. <br />Follow the steps in the *[Create a storage mover resource](storage-mover-create.md)* article to deploy this resource in an Azure subscription and region of your choice. <!-- In the Azure portal, open the portal menu (tope left corner) and select *Create a resource*. Search for *Azure Storage Mover* and select *Create*. The article *Create a storage mover resource* has more details. -->
 1. You need to deploy the Azure Storage Mover agent VM. <br /> Follow the steps in the [Azure Storage Mover agent VM deployment](agent-deploy.md) article to run the agent VM and to get it connected to the internet.
 
 ## Registration overview
diff --git a/articles/storage-mover/deployment-planning.md b/articles/storage-mover/deployment-planning.md
@@ -92,5 +92,5 @@ If you want to learn more about how the agent gets access to migrate the data, r
 <!-- Add a context sentence for the following links -->
 These articles can help you become more familiar with the Storage Mover service.
 - [Understanding the Storage Mover resource hierarchy](resource-hierarchy.md)
-- [Deploying a Storage Mover resource](resource-create.md)
+- [Deploying a Storage Mover resource](storage-mover-create.md)
 - [Deploying a Storage Mover agent](agent-deploy.md)
diff --git a/articles/storage-mover/migration-basics.md b/articles/storage-mover/migration-basics.md
@@ -167,5 +167,5 @@ Here are a few more recommendations:
 These articles can help you utilize Azure Storage Mover for your cloud migration:
 
 - [Become familiar with the Storage Mover resource hierarchy](resource-hierarchy.md)
-- [Learn how to deploy a Storage Mover in your Azure subscription](resource-create.md)
+- [Learn how to deploy a Storage Mover in your Azure subscription](storage-mover-create.md)
 - [Learn how to deploy a Storage Mover agent in your environment](agent-deploy.md)
diff --git a/articles/storage-mover/projects-manage.md b/articles/storage-mover/projects-manage.md
@@ -31,7 +31,7 @@ A Storage Mover project is used to organize migration jobs into logical tasks or
 
 When you define a project, it's a good idea to add all related, inter-dependent data sources into the same project so that they can be migrated together. You should add all the data sources necessary to migrate a single workload rather than create projects for each data source in your migration plan. You may also choose to create individual projects for each distinct group of data sources in your migration plan.
 
-This article guides you through the creation and management of Azure Storage Mover projects. To follow these examples, you'll need a top-level storage mover resource. If you haven't yet created one, follow the steps within the [Create a Storage Mover resource](resource-create.md) article before continuing.
+This article guides you through the creation and management of Azure Storage Mover projects. To follow these examples, you'll need a top-level storage mover resource. If you haven't yet created one, follow the steps within the [Create a Storage Mover resource](storage-mover-create.md) article before continuing.
 
 After you complete the steps within this article, you'll be able to create and manage projects using the Azure portal and Azure PowerShell.
 
diff --git a/articles/storage-mover/resource-hierarchy.md b/articles/storage-mover/resource-hierarchy.md
@@ -130,5 +130,5 @@ Endpoints are parented to the top-level storage mover resource and can be reused
 
 After understanding the resources involved in an Azure Storage Mover deployment, it's a good idea to start a proof-of-concept deployment. These articles may be good, next reads:
 
-- [Deploy a storage mover resource in your subscription.](resource-create.md)
+- [Deploy a storage mover resource in your subscription.](storage-mover-create.md)
 - [Deploy an Azure Storage Mover agent VM.](agent-deploy.md)
diff --git a/articles/storage-mover/storage-mover-create.md b/articles/storage-mover/storage-mover-create.md
@@ -51,6 +51,8 @@ To deploy a storage mover into a resource group, you must be a member of the *Co
 
 ### [PowerShell](#tab/powershell)
 
+Creating a storage mover requires you to decide on a subscription, a resource group, a region, and a name. The *[Planning for an Azure Storage Mover deployment](deployment-planning.md)* article shares best practices. Refer to the [resource naming convention](../azure-resource-manager/management/resource-name-rules.md#microsoftstoragesync) to choose a supported name.
+
 The `New-AzStorageMover` cmdlet is used to create new storage mover resource in a resource group. If you haven't yet installed the `Az.StorageMover` module:
 
 ```powershell
@@ -83,15 +85,18 @@ $description        = <Up to 1024 characters>
 ## Log into Azure with your Azure credentials
 Connect-AzAccount -SubscriptionId $subscriptionID
 
-## If this is the first storage mover resource deployed in this subscription, you need to manually register the resource provider namespaces Microsoft.StorageMover and Microsoft.HybridCompute with your subscription. This only needs to be done once per subscription. You must have at least Contributor permissions (RBAC role) on the subscription.
+## If this is the first storage mover resource deployed in this subscription:
+## You need to manually register the resource provider namespaces Microsoft.StorageMover and Microsoft.HybridCompute with your subscription. 
+## This only needs to be done once per subscription. You must have at least Contributor permissions (RBAC role) on the subscription.
 ## Register-AzResourceProvider -ProviderNamespace Microsoft.StorageMover
 ## Register-AzResourceProvider -ProviderNamespace Microsoft.HybridCompute
 
-## The value for the Azure region of your resource stems from an enum. To find the correct Location value for your selected Azure region, run:
+## The value for the Azure region of your resource stems from an enum. 
+## To find the correct Location value for your selected Azure region, run:
 ## Get-AzLocation | select displayname,location
 
 ## Create a storage mover resource
-New-AzStorageMover -Name $storageMoverName -ResourceGroupName $resourceGroupName -Location <Your Location value>
+New-AzStorageMover -Name $storageMoverName -ResourceGroupName $resourceGroupName -Location #<Your Location value>
 
 ```
 
