Move Azure API for FHIR to a different subscription or resource group
In this article, you'll learn how to move an Azure API for FHIR instance to a different subscription or another resource group.
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.
Moving an instance of Azure API for FHIR between subscriptions or resource groups is supported, as long as Private Link is NOT enabled and no IoMT connectors are created.
Move to another subscription
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.
The move operation takes a few simple steps.
- Select a FHIR service instance
Select the FHIR service from the source subscription and then the target subscription.
- Validate the move operation
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.
- Review and confirm the move operation
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.
Optionally, you can check the activity log in the source subscription and target subscription.
Move to another resource group
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.
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
FHIR® is a registered trademark of HL7 and is used with the permission of HL7.
Submit and view feedback for