Merge pull request #187230 from zxue/master

Revise workspace and autoscale doc

Author: Court72

articles/healthcare-apis/fhir/fhir-service-autoscale.md

@@ -5,7 +5,7 @@ author: stevewohl
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: conceptual
-ms.date: 11/16/2021
+ms.date: 2/2/2022
 ms.author: zxue
 ---
 
@@ -19,11 +19,9 @@ The autoscale feature for the FHIR service is designed to provide optimized serv
 
 ## How does FHIR service autoscale work?  
 
-When transaction workloads are high, the autoscale feature increases computing resources automatically. When transaction workloads are low, it decreases computing resources accordingly.  
+The autoscale feature adjusts computing resources automatically to optimize the overall service scalability. It requires no action from customers. 
 
-The autoscale feature adjusts computing resources automatically to optimize the overall service scalability. Whether you are performing read requests that include simple queries like getting patient information using a patient ID, and advanced queries like getting all `DiagnosticReport` resources for patients whose name is "Sarah", or you're creating or updating FHIR resources, the autoscale feature manages the dynamics and complexity of resource allocation to ensure high scalability.
-
-The autoscale feature is part of the managed service and requires no action from customers. However, customers are encouraged to share their feedback to help improve the feature. Customers can also raise a support ticket to address any scalability issue they may have experienced.  
+When transaction workloads are high, the autoscale feature increases computing resources automatically. When transaction workloads are low, it decreases computing resources accordingly. Whether you are performing read requests that include simple queries like getting patient information using a patient ID, and advanced queries like getting all DiagnosticReport resources for patients whose name is "Sarah", or you're creating or updating FHIR resources, the autoscale feature manages the dynamics and complexity of resource allocation to ensure high scalability.
 
 ### What is the cost of the FHIR service autoscale?  
 

articles/healthcare-apis/workspace-overview.md

@@ -5,7 +5,7 @@ author: stevewohl
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: overview
-ms.date: 07/12/2021
+ms.date: 2/2/2022
 ms.author: ginle
 ---
 
@@ -24,6 +24,8 @@ One or more workspaces can be created in a resource group from the Azure portal,
 
 A workspace can't be deleted unless all child service instances within the workspace have been deleted. This feature helps prevent any accidental deletion of service instances. However, when a workspace resource group is deleted, all the workspaces and child service instances within the workspace resource group get deleted. 
 
+Workspace names can be re-used in the same Azure subscription, but not in a different Azure subscription, after deletion. However, when the move operation is supported and enabled, workspaces and its child resources can be moved from one subscription to another subscription if certain requirements are met. One requirement is that the two subscriptions must be part of the same Azure Active Directory (Azure AD) tenant. Another requirement is that the Private Link configuration is not enabled. Names for FHIR services, DICOM services and IoT connectors can be re-used in the same or different subscription after deletion if there is no collision with the URLs of any existing services.
+
 ## Workspace and Azure region selection 
 
 When you create a workspace, it must be configured for an Azure region, which can be the same as or different from the resource group. The region cannot be changed after the workspace is created. Within each workspace, all Healthcare APIs services (FHIR service, DICOM service, and IoT Connector service) must be created in the region of the workspace and cannot be moved to a different workspace. 
@@ -76,4 +78,4 @@ to. For more information, see [Azure RBAC](../role-based-access-control/index.ym
 To start working with the Azure Healthcare APIs, follow the 5-minute quick start to deploying a workspace.
 
 >[!div class="nextstepaction"]
->[Deploy workspace in the Azure portal](healthcare-apis-quickstart.md)
+>[Deploy workspace in the Azure portal](healthcare-apis-quickstart.md)