I'm trying to move my custom domain from one subscription to another subscription [Pay-As-You-Go] perhaps it keeps showing me the error of insufficient payment history.
Upon contacting, an update was received from the web apps team that 35$ for the subscription to be considered with sufficient history. Hence, need to deploy some resources on the subscription and have a sufficient payment history.
Kindly guide how to handle this situation. Hence payments don't have to make just to migrate the resource.

Saravanan GanesanPosted Aug 4, 2023, 8:17 PM
Handling the situation of insufficient payment history for moving your custom domain from one Azure subscription to another without making additional payments can be achieved by following these steps:
Add a Payment Method to the Target Subscription:
Verify Sufficient Payment History:
Perform the Domain Migration:
Register the Custom Domain in the Target Subscription:
By following these steps, you can migrate the custom domain from one subscription to another without incurring additional payments. The crucial part is to have a valid payment method on the target subscription and wait for sufficient payment history to build up before performing the domain migration.
Tuhin PaulPosted Mar 18, 2023, 12:41 PM
The reply from Manikandan is a good starting point to resolve the issue of insufficient payment history when trying to move a custom domain from one Azure subscription to another. However, it is important to note that this may not solve the issue in all cases. There could be other reasons why the migration is not successful, such as issues with the custom domain DNS records, resource dependencies, or resource conflicts between the source and destination subscriptions.
Manikandan MurugesanPosted Mar 18, 2023, 5:35 AM
If you are trying to move your custom domain from one subscription to another, and you are facing an error of insufficient payment history, there are a few things that you can try to resolve the issue without having to make additional payments just to migrate the resource. Here are some suggestions:
Check your billing history: Review your billing history for the subscription that you are trying to move your custom domain to. Make sure that all the payments for the subscription have been processed and that there are no outstanding balances.
Deploy a free resource: One way to establish a payment history is by deploying a free resource on the subscription. For example, you can deploy a free Azure Web App or a free Azure Function. This will show activity on the subscription and help establish a payment history.
Upgrade an existing resource: If you already have a resource deployed on the subscription, you can try upgrading it to a paid tier. This will also show activity on the subscription and help establish a payment history.
Contact Azure support: If you have tried the above options and are still facing issues, you can contact Azure support for further assistance. They may be able to provide you with additional options or work with you to resolve the issue.
Overall, the key is to establish a payment history on the subscription so that Azure can verify that you have a reliable payment method on file. Once you have established a payment history, you should be able to move your custom domain to the new subscription without any issues.
Tuhin PaulPosted Mar 18, 2023, 1:51 AM
To handle this situation and migrate your custom domain to another subscription without having to make payments:
You can create new resources such as a new virtual machine, a storage account, or a web app in the destination subscription to build a payment history. This will allow the subscription to be considered with sufficient payment history. Once you have deployed some resources in the destination subscription, you can check the payment history by navigating to the billing section in the Azure portal. Ensure that the payment history is sufficient before attempting to move the custom domain.
Once you have a sufficient payment history in the destination subscription, you can then proceed to move the custom domain to the new subscription. To do this, you will need to follow the steps outlined in the Azure documentation on how to move resources between subscriptions. After moving the custom domain, you should verify that it is working as expected. You can do this by navigating to the custom domain in the destination subscription and checking that it is pointing to the correct resources.