Updated articles for GA

stevenmatthew · stevenmatthew · commit 55faed2765e5 · 2023-03-15T10:16:13.000-07:00
diff --git a/articles/storage-mover/agent-deploy.md b/articles/storage-mover/agent-deploy.md
@@ -5,7 +5,7 @@ author: stevenmatthew
 ms.author: shaas
 ms.service: storage-mover
 ms.topic: how-to
-ms.date: 09/12/2022
+ms.date: 03/14/2023
 ---
 
 <!-- 
@@ -39,7 +39,7 @@ This article will guide you through the steps necessary to successfully deploy a
 - A capable Windows Hyper-V host on which to run the agent VM. See the [Recommended compute and memory resources](#recommended-compute-and-memory-resources) section in this article for details about resource requirements for the agent VM.
 
 > [!NOTE]
-> During public preview, Windows Hyper-V is the only supported virtualization environment for your agent VM. Other virtualization environments have not been tested and are not supported at this time.
+> At present, Windows Hyper-V is the only supported virtualization environment for your agent VM. Other virtualization environments have not been tested and are not supported.
 
 ## Download the agent VM image
 
@@ -164,7 +164,7 @@ xdmsh> 4
 Select the option **4) Unregister**. You'll be prompted for confirmation.
 
 > [!WARNING]
-> Unregistration stops any running migration job on the agent and permanently removes the agent from the pool of available migration agents. Re-registration of a previously registered agent VM is not supported in public preview. If you need a new agent, you must use a new agent image that was never registered before and register this new agent VM. Do not reuse a previously unregistered agent VM.
+> Unregistration stops any running migration job on the agent and permanently removes the agent from the pool of available migration agents. Re-registration of a previously registered agent VM is not supported. If you need a new agent you should register a new, previously unregistered agent VM. Do not reuse a previously unregistered agent VM.
 
 # [Azure portal](#tab/azure-portal)
 
@@ -175,7 +175,7 @@ You can unregister an agent in the Azure portal by navigating to your storage mo
 - Select **Unregister agent** and wait for the operation to complete.
 
 > [!WARNING]
-> Unregistration stops any running migration job on the agent and permanently removes the agent from the pool of available migration agents. Re-registration of a previously registered agent VM is not supported in public preview. If you need a new agent, you must use a new agent image that was never registered before and register this new agent VM. Do not reuse a previously unregistered agent VM.
+> Unregistration stops any running migration job on the agent and permanently removes the agent from the pool of available migration agents. Re-registration of a previously registered agent VM is not supported. If you need a new agent, you must use a new agent image that was never registered before and register this new agent VM. Do not reuse a previously unregistered agent VM.
 
 # [PowerShell](#tab/powershell)
 
@@ -189,7 +189,7 @@ Unregister-AzStorageMoverAgent -ResourceGroupName <YourResourceGroupName> -Stora
 *-Force* is an optional parameter, suppressing the confirmation prompt.
 
 > [!WARNING]
-> Unregistration stops any running migration job on the agent and permanently removes the agent from the pool of available migration agents. Re-registration of a previously registered agent VM is not supported in public preview. New agent VMs must be created from a new agent image that has not been previously registered. Do not reuse a previously unregistered agent VM.
+> Unregistration stops any running migration job on the agent and permanently removes the agent from the pool of available migration agents. Re-registration of a previously registered agent VM is not supported. If you need a new agent you should register a new, previously unregistered agent VM. Do not reuse a previously unregistered agent VM.
 
 ---
 
@@ -202,11 +202,11 @@ Several things take place during the unregistration process:
   This behavior is standard, and not specific to Azure Storage Mover. You can observe the same behavior if you remove a different service principal from Azure AD and then check a former role assignment.
 
 > [!WARNING]
-> During public preview, unregistration of an offline agent is supported but the agent's Azure ARC resource isn't automatically deleted. Instead, you'll need to manually delete the resource after unregistering an offline agent. The lifecycle of the agent's managed identity is tied to this resource. Removing it removes the managed identity and service principal, as previously described.
+> Unregistration of an offline agent is supported, but the agent's Azure ARC resource isn't automatically deleted. Instead, you'll need to manually delete the resource after unregistering an offline agent. The lifecycle of the agent's managed identity is tied to this resource. Removing it removes the managed identity and service principal, as previously described.
 
 You can check that the unregistration process is complete when the agent disappears from the Azure portal and either Azure PowerShell or Azure CLI. You'll also need to confirm that the hybrid compute resource of type *Server - Azure Arc* is gone from the resource group.
 
-You can also use the agent's administrative shell to check that the agent is unregistered. To verify unregistration, navigate to any submenu and then return to the top-level menu. If unregistration was successful, you'll see the menu option toggle from *Unregister* to *Register*. As previously mentioned, re-registering isn't supported during the public preview.
+You can also use the agent's administrative shell to check that the agent is unregistered. To verify unregistration, navigate to any submenu and then return to the top-level menu. If unregistration was successful, you'll see the menu option toggle from *Unregister* to *Register*. As previously mentioned, re-registering isn't supported.
 
 You can stop the agent VM on your virtualization host after the unregistration is complete. It's best to delete the agent VM image since it was previously registered, retains some state, and must not be used again. If you need a new agent, deploy a new VM with a new agent image that had never been registered before.
 
diff --git a/articles/storage-mover/agent-register.md b/articles/storage-mover/agent-register.md
@@ -5,7 +5,7 @@ author: stevenmatthew
 ms.author: shaas
 ms.service: storage-mover
 ms.topic: how-to
-ms.date: 09/15/2022
+ms.date: 03/14/2023
 ---
 
 <!-- 
diff --git a/articles/storage-mover/deployment-planning.md b/articles/storage-mover/deployment-planning.md
@@ -6,7 +6,7 @@ author: stevenmatthew
 ms.service: storage-mover
 ms.author: shaas
 ms.topic: conceptual
-ms.date: 08/29/2022
+ms.date: 03/14/2023
 ---
 
 <!-- 
@@ -28,7 +28,7 @@ Deploying Azure Storage Mover in one of your Azure subscriptions is the first st
 
 ## Make sure the service works for your scenario
 
-Azure Storage Mover aspires to work for a wide range of migration scenarios. However, the service is new, currently in public preview, and supports limited migration scenarios. Check out the [supported sources and targets section](service-overview.md#supported-sources-and-targets) in the [Azure Storage Mover overview article](service-overview.md) to make sure the service works for you.
+Azure Storage Mover aspires to work for a wide range of migration scenarios. However, the service is new and therefore supports a relatively limited number of migration scenarios. Ensure that the service works for you by consulting the [supported sources and targets section](service-overview.md#supported-sources-and-targets) in the [Azure Storage Mover overview article](service-overview.md).
 
 ## Deployment basics
 
diff --git a/articles/storage-mover/performance-targets.md b/articles/storage-mover/performance-targets.md
@@ -5,7 +5,7 @@ author: stevenmatthew
 ms.author: shaas
 ms.service: storage-mover
 ms.topic: conceptual
-ms.date: 01/10/2023
+ms.date: 03/14/2023
 ---
 
 <!-- 
@@ -22,7 +22,7 @@ REVIEW Engineering: not reviewed
 
 # Azure Storage Mover scale and performance targets
 
-The performance of a storage migration service is a key aspect for any migration. Azure Storage Mover is a new service, in public preview. In this article, we share performance test results - your experience will vary.
+The performance of a storage migration service is a key aspect for any migration. In this article, we share performance test results, though because Azure Storage Mover is a new service, your experience may vary.
 
 ## Scale targets
 
diff --git a/articles/storage-mover/resource-hierarchy.md b/articles/storage-mover/resource-hierarchy.md
@@ -5,7 +5,7 @@ author: stevenmatthew
 ms.author: shaas
 ms.service: storage-mover
 ms.topic: conceptual
-ms.date: 09/12/2022
+ms.date: 03/14/2023
 ---
 
 <!-- 
@@ -105,15 +105,10 @@ The agent also emits additional information and migration results through the Az
 - **Metrics** are numerical values, recorded over time. They can be plotted using the Azure Monitor service. Some selected metrics are also directly available when managing the job definition / job runs in the portal.
 - **Copy logs** are optional. If enabled, every job run has its own copy log. A log entry is generated for each namespace item the agent encounters in the source that can't be copied.
 
-> [!NOTE]
-> At this time in the public preview, copy logs are not available in Azure. They are, however, available via manual download from the migration agent that completed the job run.
-
-<!-- 
-!########################################################
 > [!IMPORTANT]
 > Metric information is available by default, but you must opt-in to enable copy logs. That can be done as part of creating your storage mover resource and also later on. If you want to check if copy logs are enabled, or manage details, you can use the *Diagnostic settings* menu on the Azure portal page for your storage mover resource.
-!########################################################
 
+<!--
 Learn more about telemetry, metrics and logs in the job definition monitoring article.
 -->
 
diff --git a/articles/storage-mover/service-overview.md b/articles/storage-mover/service-overview.md
@@ -5,7 +5,7 @@ author: stevenmatthew
 
 ms.service: storage-mover
 ms.topic: overview
-ms.date: 09/12/2022
+ms.date: 03/14/2023
 ms.author: shaas
 ---
 
@@ -25,9 +25,7 @@ Document score: 100 (393 words and 0 issues)
 
 # What is Azure Storage Mover?
 
-Azure Storage Mover is a fully managed migration service that enables you to migrate your files and folders to Azure Storage while minimizing downtime for your workload. You can use Storage Mover for different migration scenarios such as *lift-and-shift*, and for cloud migrations that you'll have to repeat occasionally. Azure Storage Mover also helps maintain oversight and manage the migration of all your globally distributed file shares from a single storage mover resource.
-
-Azure Storage Mover is a new service, currently in public preview.
+Azure Storage Mover is a new, fully managed migration service that enables you to migrate your files and folders to Azure Storage while minimizing downtime for your workload. You can use Storage Mover for different migration scenarios such as *lift-and-shift*, and for cloud migrations that you'll have to repeat occasionally. Azure Storage Mover also helps maintain oversight and manage the migration of all your globally distributed file shares from a single storage mover resource.
 
 ## Supported sources and targets
 
