Skip to content

Commit f6ffbc5

Browse files
authored
Merge pull request #287912 from KendalBond007/APIforFHIRbatch9_Oct24
APIforFHIRbatch9_Oct24
2 parents 258e4ce + 1dc9e59 commit f6ffbc5

File tree

6 files changed

+133
-133
lines changed

6 files changed

+133
-133
lines changed

articles/healthcare-apis/azure-api-for-fhir/move-fhir-service.md

Lines changed: 9 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -11,9 +11,9 @@ ms.author: kesheth
1111

1212
# Move Azure API for FHIR to a different subscription or resource group
1313

14-
[!INCLUDE [retirement banner](../includes/healthcare-apis-azure-api-fhir-retirement.md)]
14+
[!INCLUDE[retirement banner](../includes/healthcare-apis-azure-api-fhir-retirement.md)]
1515

16-
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.
1717

1818
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).
1919

@@ -22,40 +22,39 @@ Moving to a different region isn’t supported, though the option may be availab
2222
2323
## Move to another subscription
2424

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.
2626

2727
The **move** operation takes a few simple steps.
2828

2929
1. Select a FHIR service instance
3030

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.
3232

3333
:::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":::
3434

3535
2. Validate the move operation
3636

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.
3838

3939
:::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":::
4040

4141
3. Review and confirm the move operation
4242

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.
4444

4545
:::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":::
4646

4747
Optionally, you can check the activity log in the source subscription and target subscription.
4848

4949
## Move to another resource group
5050

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.
5252

5353
## Next steps
5454

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
5656

5757
>[!div class="nextstepaction"]
5858
>[Supported FHIR features](fhir-features-supported.md)
5959
60-
FHIR® is a registered trademark of [HL7](https://hl7.org/fhir/) and is used with the permission of HL7.
61-
60+
[!INCLUDE[FHIR trademark statement](../includes/healthcare-apis-fhir-trademark.md)]

0 commit comments

Comments
 (0)