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
In this article, you'll learn how to move an Azure API for FHIR instance to a different subscription or another resource group.
16
+
In this article, you learn how to move an Azure API for FHIR® instance to a different subscription or another resource group.
17
17
18
18
Moving to a different region isn’t supported, though the option may be available from the list. For more information, see [Move operation support for resources](../../azure-resource-manager/management/move-support-resources.md).
19
19
@@ -22,40 +22,39 @@ Moving to a different region isn’t supported, though the option may be availab
22
22
23
23
## Move to another subscription
24
24
25
-
You can move an Azure API for FHIR instance to another subscription from the portal. However, the runtime and data for the service aren’t moved. On average the **move** operation takes approximately 15 minutes or so, and the actual time may vary.
25
+
You can move an Azure API for FHIR instance to another subscription from the portal. However, the runtime and data for the service aren’t moved. On average the **move** operation takes approximately 15 minutes. The actual time may vary.
26
26
27
27
The **move** operation takes a few simple steps.
28
28
29
29
1. Select a FHIR service instance
30
30
31
-
Select the FHIR service from the source subscription and then the target subscription.
31
+
Select the FHIR service from the source subscription, and then the target subscription.
32
32
33
33
:::image type="content" source="media/move/move-source-target.png" alt-text="Screenshot of Move to another subscription with source and target." lightbox="media/move/move-source-target.png":::
34
34
35
35
2. Validate the move operation
36
36
37
-
This step validates whether the selected resource can be moved. It takes a few minutes and returns a status from**Pending validation** to **Succeeded** or **Failed**. If the validation failed, you can view the error details, fix the error, and restart the **move** operation.
37
+
This step validates whether the selected resource can be moved. It takes a few minutes and returns a status of**Pending validation**, **Succeeded**, or **Failed**. If the validation failed, you can view the error details, fix the error, and restart the **move** operation.
38
38
39
39
:::image type="content" source="media/move/move-validation.png" alt-text="Screenshot of Move to another subscription with validation." lightbox="media/move/move-validation.png":::
40
40
41
41
3. Review and confirm the move operation
42
42
43
-
After reviewing the move operation summary, select the confirmation checkbox at the bottom of the screen and press the Move button to complete the operation.
43
+
After reviewing the move operation summary, select the confirmation checkbox at the bottom of the screen and select **Move** to complete the operation.
44
44
45
45
:::image type="content" source="media/move/move-review.png" alt-text="Screenshot of Move to another subscription with confirmation." lightbox="media/move/move-review.png":::
46
46
47
47
Optionally, you can check the activity log in the source subscription and target subscription.
48
48
49
49
## Move to another resource group
50
50
51
-
The process works similarly to **Move to another subscription**, except the selected FHIR service will be moved to a different resource group in the same subscription.
51
+
The process works similarly to **Move to another subscription**, except the selected FHIR service is moved to a different resource group in the same subscription.
52
52
53
53
## Next steps
54
54
55
-
In this article, you've learned how to move the Azure API for FHIR instance. For more information about the supported FHIR features in Azure API for FHIR, see
55
+
In this article, you learned how to move the Azure API for FHIR instance. For more information about the supported FHIR features in Azure API for FHIR, see
0 commit comments