Azure Server Transfer

Hello @SKJohn
To seamlessly transfer an active Azure App Service from a developer’s account to your own, the recommended and simplest approach is to transfer the subscription ownership, as Azure resources (including App Services, databases, and configurations) are tied to the subscription rather than being individually movable across accounts. The current owner (developer) needs to sign in to the Microsoft Azure Portal, navigate to Subscriptions, select the relevant subscription, and initiate a billing ownership transfer to your Azure account. Once you accept the transfer via email, all resources under that subscription including the live application will automatically be available in your account without downtime or reconfiguration. If transferring the subscription is not feasible, an alternative is for the developer to grant you Owner role access via Azure IAM, which provides full control but keeps billing under their account. For complete separation, the app can be redeployed into your subscription, but this requires manual setup of App Service, databases, and configurations.
https://learn.microsoft.com/en-us/azure/role-based-access-control/role-assignments-portal
https://learn.microsoft.com/en-us/azure/cost-management-billing/manage/billing-subscription-transfer

Hello @SKJohn

If you want to move Azure App Service web app from one subscription to another subscription, please follow below steps:

• Make sure you have Owner (or Contributor) rights on both the source and destination subscriptions.
• In the Azure portal, go to the resource group containing your web app and App Service Plan (they must be together and the only App Service resources in that group).
• Click Move>Move to another subscription, pick the web app, App Service Plan (and any certificates you need), then select your destination subscription and resource group.
• Confirm and start the operation. Note: free App Service-managed certificates can’t be moved; you’ll need to re-create those afterwards.

Detailed documentation is provided below.

https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/move-resource-group-and-subscription?tabs=azure-cli

If the answer is helpful, Please do click "Accept the answer” and Yes, this can be beneficial to other community members.

If you have any other questions, let me know in the "comments" and I would be happy to help you

For a seamless move from a developer’s Azure account to a personal Azure account, there are two main parts:

1. Transfer the Azure subscription/billing ownership (if possible).
2. Ensure the app and its resources (for example, Azure Database for MySQL) continue to run without downtime.

Because the app is “active” and already running, the simplest approach is usually to transfer the subscription billing ownership rather than rebuilding everything.

1. Plan the transfer

Before doing anything, clarify:

1. Why the transfer is needed (for example, moving from a developer’s personal billing to a company/personal billing).
2. When the transfer should happen (pick a low-traffic time in case any changes are needed).
3. What type of subscription the app is currently in and what type it will move to (Pay-As-You-Go, CSP, EA, etc.). The supported combinations and limitations are described in the Azure product transfer hub.
4. Confirm the developer has the required billing permissions on the current subscription and that the destination account (your account) also has the right billing role.
   • Only the billing administrator of an account can transfer subscription ownership.
5. Check if there are any reservations or savings plans attached to the subscription that should move with it.
6. Confirm the subscription does not have an active Microsoft Azure Consumption Commitment (MACC); if it does, it cannot be transferred until the MACC expires.

2. Decide what to transfer

There are two common options:

1. Transfer the entire subscription (recommended for non-technical users)
   • All resources (App Service, Azure Database for MySQL, storage, etc.) stay exactly as they are.
   • Only the billing ownership changes from the developer’s account to the new account.
   • No app changes, no connection string changes, and no resource moves are required.
2. Move individual resources to a different subscription/tenant
   • More complex and can affect resources.
   • Only needed if the subscription cannot be transferred (for example, due to offer type or MACC limitations).

If the developer and the destination account are in the same Microsoft Entra tenant, transferring billing ownership of the subscription does not affect running resources.

3. Have the developer initiate the subscription transfer

The developer (current owner) should:

1. Go to the Azure portal and open Cost Management + Billing.
2. Locate the subscription that hosts the app and Azure Database for MySQL.
3. Start a billing ownership transfer for that subscription (using the documented “Transfer billing ownership of an Azure subscription” flow referenced from the Azure product transfer hub).
4. Specify the destination account (your Azure account) as the new owner.
5. When sending the transfer request, the sender must select Send transfer request and thereby accept the terms:
   • After the transfer completes (Transition Date), the destination account is responsible for ongoing and scheduled billings.
   • Prepaid subscriptions (including reservations) move to the destination account and cannot be canceled.

4. Accept the transfer on the destination account

On the destination account (your account):

1. Open the email or portal notification about the transfer.
2. In the Azure portal, go to Cost Management + Billing → Transfers (or the equivalent transfer page).
3. Select the pending transfer and choose Review + validate.
4. Review the list of items (subscription, reservations, etc.).
5. Accept the transfer and confirm.

By accepting, the destination account agrees that:

• The items transfer as of the Transition Date.
• Any prepaid subscriptions (including reserved instances) move to the destination account.
• The source account is no longer responsible for ongoing payment obligations for those items.

5. Verify the app and database after transfer

Once the transfer completes:

1. Sign in with the destination account and verify the subscription is visible.
2. Open the resource group(s) and confirm:
   • The web app (App Service or other hosting) is present and running.
   • The Azure Database for MySQL instance is present and running.
3. Test the application from a browser or client to ensure it still connects to the database and functions as expected.

When only billing ownership changes and the subscription stays in the same Microsoft Entra tenant, all resources (VMs, App Service, databases, etc.) transfer together and continue running without downtime.

6. Important behavior and limitations

• No downtime expected: Transferring a product (subscription) to an account in the same Microsoft Entra tenant does not affect running resources.
• Resources move with the subscription: All resources (including the app and Azure Database for MySQL) move with the subscription when billing ownership changes.
• No historical billing data: The new account only sees usage and billing history from the time of transfer onward. Past billing history does not move.
• MACC limitation: If the subscription has an active MACC, it cannot be canceled or transferred until the MACC expires.

7. If the accounts are in different tenants or transfer is blocked

If the subscription cannot be transferred (for example, due to MACC or unsupported offer types), a more technical resource migration is required (moving the app and database into a new subscription/tenant). That process is more complex and typically requires an Azure administrator to:

• Create a new subscription in the destination account.
• Move or recreate the App Service and Azure Database for MySQL in the new subscription.
• Update DNS, connection strings, and possibly perform data migration.

In that case, involving a technical Azure administrator or partner is strongly recommended.

References:

• Azure product transfer hub
• Transfer an Azure subscription to an Enterprise Agreement (EA)