Unable to move Azure Subscription to another Subscription on the same tenant

When moving an Azure subscription, certain resource types may not be supported for the move operation, which appears to be the case with your Bastion host. The error message indicates that the resource type Microsoft.Network/bastionHosts cannot be moved. Here are some steps you can take to resolve the issue:

1. Check Resource Dependencies: Ensure that there are no dependencies or associated resources that might be preventing the move. Sometimes, other resources linked to the Bastion host can cause validation failures.
2. Remove Unsupported Resources: Since you mentioned removing the Bastion hosts, ensure that all instances of Microsoft.Network/bastionHosts are indeed removed from the subscription you are trying to move. You may also want to check for any other unsupported resources.
3. Review Move Requirements: Familiarize yourself with the specific requirements for moving resources between subscriptions. Not all resources can be moved, and it’s important to ensure that the resources you are trying to move comply with Azure's guidelines.
4. Use Azure Portal for Validation: Sometimes, using the Azure portal to initiate the move can provide more detailed validation feedback or guidance on what needs to be addressed.
5. Contact Azure Support: If you continue to face issues, consider reaching out to Azure support for assistance. They can provide more detailed insights based on the tracking ID and correlation ID you received in the error message.

By following these steps, you should be able to identify the cause of the validation failure and take appropriate actions to resolve it.

Hello VLT Administrator,

Thanks for posting your question in Microsoft Q&A forum

Based on your error & Microsoft official document we are not supported to move Microsoft.Network/bastionHosts between subscriptions.
Refer document: https://dori-uw-1.kuma-moon.com/en-us/azure/azure-resource-manager/management/move-support-resources#microsoftnetwork

Even after deletion, Azure sometimes retains metadata or internal references to the resource, which continue to block move validation.

• Ensure the Bastion host and all dependent or associated resources are permanently deleted from the resource group; check for soft-deleted or hidden resources.
• Verify Resource Clean-Up-List all deleted and existing Bastion hosts in the source resource group. az resource list --resource-group <source-group> --resource-type Microsoft.Network/bastionHosts Confirm no Bastion Host resources or hidden dependencies exist.
• verify the resource’s internal hosting relationship using the following command: YAML

    az resource show --ids <resource-id> --query properties.hostingResourceGroupName
  

• If all checks are clear, retry the move via Portal or CLI
• still If you are unable to move the subscription or if the move continues to fail, open a Microsoft Support ticket create an Azure support request, Azure portal.

Referral documents:

• Move Azure resources to a new resource group or subscription - Azure Resource Manager | Microsoft L…
• Manage an Azure support request - Azure supportability | Microsoft Learn
• https://dori-uw-1.kuma-moon.com/en-us/azure/bastion/bastion-faq

I hope the provided answer is helpful, do let me know if you have any further questions on this Please accept as Yes if the answer is helpful so that it can help others in the community.