How to Move ACS SMS Number to a New Azure Subscription

Select Language:

If you’re wondering whether it’s possible to move or transfer an Azure Communication Services (ACS) phone number from one resource or subscription to another, unfortunately, the answer is no. Microsoft’s documentation clearly states that ACS phone numbers are tied to a specific resource and cannot be transferred or moved between different ACS resources or subscriptions. This also means they can’t be moved with the resource itself during subscription changes.

Since the phone numbers are bound to a specific resource, the usual Azure move operations don’t support relocating ACS numbers. If you’re trying to switch your number to a new subscription, simply moving the resource won’t work, and you might risk losing the number entirely.

So, what are your options if you want to keep the same phone number but need to switch to a new subscription? There are two main approaches: port the number or release and then reacquire it.

Porting the number is the best method if the number belongs to an external carrier. You can bring in your existing number from your current provider into a new ACS resource. Keep in mind, this option only supports numbers outside of Azure, and the process involves working with your current provider to transfer the number.

However, if your number is already inside Azure, there isn’t a supported way to port it directly from one ACS resource to another—even if both resources are under the same Azure tenant.

The alternative is to release the number from the current ACS resource and then try to get it again. Be warned though, this method carries risks. Releasing your number means deleting the resource, which immediately stops all SMS and calling services associated with that number. There’s also a chance you might not be able to reclaim the same number afterward, leading to potential service downtime and permanent loss.

To minimize disruption during your transition, follow these steps:

Set up a new ACS resource in your target subscription.
Provision a new phone number in that resource.
Update your applications and systems to use the new number.
Keep the old ACS resource active until your migration is fully complete, and you’re confident everything is working with the new number.

This approach keeps your services running smoothly without risking the loss of your current number until everything is ready to switch over.

For more detailed information, you can visit these official resources:

Microsoft documentation on resource movement: Azure move support for communication resources
Guides on porting and acquiring phone numbers: Porting phone numbers into ACS and Getting a new phone number

If you have more questions or need any further help, please let us know. Your feedback on whether this information was useful is appreciated, as it helps other users too.