Impact to SQL Server access when moving Subscription and SQL Server Database Resources

Question

Impact to SQL Server access when moving Subscription and SQL Server Database Resources

Glenn Seehausen 20

I am about to have Microsoft move a Subscription and all of its resources from one Account to another. The SQL Server Databases are constantly being accessed via direct calls by my customers using SELECT, INSERT, UPDATE, and DELETE SQL Statement. Their IP Addresses are being white-listed so they can do this. All other security is not managed within Azure for these SQL Databases, and is instead managed in the SQL Server Database using DB Logins and Passwords so they can use the SQL Statement to read and modify data in them.

Will moving the Subscription and Resource cause customers to no longer be able to access the SQL Database? Or will it seamlessly move, including all white-listed IPs and all SQL Server managed security?

0 comments

Answer accepted by question author

0 additional answers

Your answer

Answer 1

Manoj Kumar Boyini 13,600 Microsoft External Staff Moderator

Hi @Glenn Seehausen

The impact depends mainly on whether the subscription move happens within the same Microsoft Entra tenant or across tenants.

For a move within the same tenant, Azure performs a control-plane reassignment (not a redeployment). In this case, your Azure SQL Database remains unchanged from a connectivity perspective:

The server endpoint (e.g., yourserver.database.windows.net) stays the same
Server-level firewall rules (IP whitelisting) are preserved
SQL logins, users, and passwords inside the database are not affected

So your customers should generally continue accessing the database without changes. Typically there is minimal impact, although a brief transient connection interruption can occur during the move.

However, if the subscription is moved across tenants, additional considerations apply:

Azure RBAC permissions are not carried over and must be reassigned
Microsoft Entra configurations (if any) require reconfiguration in the target tenant
Managed identities are not preserved
Some validation or reconfiguration may be needed post-move

These do not impact SQL authentication directly (as in your scenario), but they can affect administrative access and integrations.

Also note that the resource ID changes after the move, so any scripts, automation, or tools referencing the old resource ID should be updated.

References:
https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/move-resource-group-and-subscription?tabs=azure-cli
https://learn.microsoft.com/en-us/azure/role-based-access-control/transfer-subscription
https://learn.microsoft.com/en-us/azure/azure-sql/database/logical-servers?view=azuresql&tabs=portal

Please let us know if you have any questions or concerns.

Glenn Seehausen 20 Reputation points

2026-04-28T17:49:29.6733333+00:00

I do not know if the request I am making to move my Subscription and associated Resources is considered a "tenant" change. I have asked the person at Microsoft that is helping me with this "move" to clarify this, but is there a way for me to know?

Also, your last statement...

"Also note that the resource ID changes after the move, so any scripts, automation, or tools referencing the old resource ID should be updated."

...concerns me. Do you know if the Server Name for my SQL Database (they are all on the same "server") will change? Does this also depend on whether I am moving "tenants"?
Manoj Kumar Boyini 13,600 Reputation points Microsoft External Staff Moderator

2026-04-28T18:02:41.17+00:00
Hi @Glenn Seehausen

If Microsoft is moving resources between subscriptions, then it is a same-tenant move as long as both subscriptions belong to the same Microsoft Entra ID tenant. Resource moves across subscriptions are supported in this scenario.

If instead the subscription is being transferred to a different Microsoft Entra directory, then it is considered a cross-tenant move. You can verify this by checking the Tenant ID in the Azure portal (Subscriptions → Properties) before and after the move, or via CLI (az account show).

For your Azure SQL Database:

The server name (e.g., <serverName>.database.windows.net) remains the same during supported move operations, so connection strings do not need to change

Firewall rules and SQL logins are generally preserved as part of the logical server configuration

The main differences in a cross-tenant move are related to identity and access:

Azure RBAC role assignments are removed and must be reassigned

Managed identities are not preserved

If Microsoft Entra authentication is used, it must be reconfigured in the target tenant

Key takeaway:
SQL connectivity (server name, connection strings, SQL authentication) continues to work as expected Identity-related configurations may require reconfiguration if this is a cross-tenant move

Please let us know if you have any questions or concerns.
Glenn Seehausen 20 Reputation points

2026-04-28T18:10:56.43+00:00

Okay, this sounds promising. I am not concerned about RBAC role assignments or managed identities, since I was not using that approach to my SQL Database Security and I am the only manager and user of the Azure Portal for this Subscription and all of its resources .

If I understand your response correctly, even in a cross-tenant move, it sounds like my customers should not experience any "outage" at all, since the white-listed IPs should remain intact, the SQL Server name and connection strings should remain the same, and all "internal" SQL Database Security Users/Roles/Permissions will also remain. Did I get that right?
Manoj Kumar Boyini 13,600 Reputation points Microsoft External Staff Moderator

2026-04-28T18:17:29.18+00:00

Hi @Glenn Seehausen

You’re right, Your customers will continue to connect normally (same server name, same IP rules, same SQL logins). No reconfiguration is needed from their side.

The only thing to expect is a very brief connection interruption during the move (for example, dropped connections or retries). This is common with Azure operations and usually resolves within seconds.

Share via

Impact to SQL Server access when moving Subscription and SQL Server Database Resources

0 additional answers

Your answer