ASR not working receiving error Error ID 310015

Question

ASR not working receiving error Error ID 310015

William Rosenblath 5

Error ID 310015
Error Message Failed to enable replication of the machine 'WMS2.ans2.local'.
Possible causes There is no access to create new VMs with specified configurations in the target location 'canadaeast' for the selected target subscription 'e9354719-1532-4c04-aeca-3b3293fccf96'.
Recommendation You can contact support to enable your subscription to create VMs in target location 'canadaeast' and retry the operation. To contact, go to https://aka.ms/getazuresupport, choose issue as Service and subscription limits (quotas) and provide necessary details.
Related links
- https://aka.ms/getazuresupport
First Seen At 2025-09-18, 2:13:42 p.m.

William Rosenblath 5 Reputation points

2025-09-18T20:56:34.6233333+00:00

Note I am in the owner role for this, so have all permissions.

I don't see any issues with the setup so far unless something isn't being created in the resource group that is required.
Bharath Y P 1,350 Reputation points Microsoft External Staff Moderator

2025-09-18T22:56:16.4633333+00:00
Hello William Rosenblath,

You're encountering an error while trying to enable replication for the machine WMS2.ans2.local using Azure Site Recovery. The error explicitly states: "No access to create new VMs with specified configurations in target location 'canadaeast' for the selected subscription."

Azure subscriptions have limits on the resources you can deploy in a given region. These limits, known as quotas, are in place to manage resource consumption and prevent overuse. The error "Failed to enable replication...There is no access to create new VMs" is a common indication that you've hit one of these quotas. This isn't a problem with your user role or permissions; it's a subscription-level restriction.

When you enable replication, ASR needs to pre-validate the ability to create a replica VM in the target region. If the region is disabled for your subscription, The VM family/size quota is exhausted, or There are policy restrictions (like Azure Policy or RBAC). ASR cannot proceed and throws this error.

Check subscription quotas in Canada East

Go to Azure Portal > Subscriptions > Under Settings > Usage + quotas.

Check for the region Canada East.

Look at Core quotas (Standard DSv2, FS, etc.) in Canada East.

Confirm you have enough VM cores and the required VM family available.

Request Quota Increase or Enable VM Creation:

If quotas are insufficient or the capability to create VMs in "canadaeast" is not enabled, Contact Azure billing support to enable your subscription to create VMs of the required sizes in the target location.

Use this link: https://aka.ms/getazuresupport

Select issue type: Service and subscription limits (quotas).

Provide details about the required VM configuration and region.

After quota increase or enabling VM creation, retry the replication operation from Azure Site Recovery.

If the target location has a capacity constraint, disable replication to that location. Then, enable replication to a different location where your subscription has a sufficient quota to create VMs of the required sizes.

Follow the link below for a better understanding,

https://free.blessedness.top/en-us/azure/site-recovery/azure-to-azure-troubleshoot-errors

Hope this helps! Please let us know if you need further assistance with this.
Bharath Y P 1,350 Reputation points Microsoft External Staff Moderator

2025-09-19T23:50:52.2133333+00:00
Hello William Rosenblath,

As you mentioned, looks like you just starting with replication and testing in Azure, but all resources are being created in Canada East. You see issues that seem location related (likely capacity/availability constraints in Canada East). You haven’t hit any quotas because this is your first attempt to deploy.

By understanding that this looks like is a regional capacity issue and not a problem with your subscription, you can choose the best path forward to get your initial environment up and running

Understanding Regional Capacity

Azure operates a global network of data centers, and each region (like Canada East) has a finite amount of physical hardware. While Azure tries to meet demand, there are times when a specific service or VM size is in high demand and resources are temporarily unavailable. This is different from a subscription quota, which is a limit on the number of resources you can deploy. A regional capacity issue is a limit on the number of resources Azure can provide in that location at that specific moment.

You'll typically see an error message like "The requested size is currently not available in location Canada East" or a similar error indicating a resource constraint.

Current recommended action:

Try a Different VM Size: This is the easiest and most common solution. The capacity issue might be specific to the VM size you're trying to deploy. Try a similar VM size within the same family (e.g., if Standard_D8s_v3 is unavailable, try Standard_D4s_v3 or Standard_D16s_v3). You can also check other compatible VM families.

Choose a Different Region: Since you're just starting your replication and testing, using a different Azure region is the most reliable way to get immediate access to resources.

Check Azure Service Health:

Go to Azure Service Health see if Canada East has capacity or availability issues.
Bharath Y P 1,350 Reputation points Microsoft External Staff Moderator

2025-09-22T17:27:36.4466667+00:00

Hello William Rosenblath, Just checking in to see if the solution shared above help you to resolve your issue. please reach out to us If you have any further questions. Thanks
William Rosenblath 5 Reputation points

2025-09-22T17:37:59.55+00:00

Can I replicate to another region even though my resource group and all of the other items are Canada east. Canada East represents the best location to reduce any latency vs Canada Central for example. I don't understand the sizing info enough to know what to do there. I have a support ticket opened as well.
Bharath Y P 1,350 Reputation points Microsoft External Staff Moderator

2025-09-22T21:47:43.0966667+00:00
Hello William Rosenblath,

Yes, you can replicate it to a different region, but there are some important considerations:

Azure Site Recovery (ASR) allows replication to any supported Azure region, regardless of the resource group’s location.

Your resource group, storage, and VNet can remain in Canada East; the replicated VM will be deployed in the target region.

The replicated VM will have a separate VNet and storage account in the target region.

Check quotas in the alternative region first then replicate to Canada Central temporarily later, you can migrate the failover VM to Canada East once quotas are approved.
William Rosenblath 5 Reputation points

2025-09-23T14:55:49.1133333+00:00

Can I get some assistance doing this. It seems to be choosing east on it's own , perhaps it's based on the recovery services vault, I'm not sure. I just don't know how to make it go to a different target. I tried telling it not to go to a network, just replication to the vault but it still fails, I need more details on how to make this work.
Bharath Y P 1,350 Reputation points Microsoft External Staff Moderator

2025-09-23T19:37:09.6033333+00:00
Hello William Rosenblath, Thanks for the update

ASR requires a target NIC and VNet to attach the replicated VM. If you leave it blank, the job fails because it cannot map the source NIC to anything in the target region. Even if you “just want replication to the vault”, the platform needs a target region + target network defined, otherwise it can’t complete protection.

Vault Location vs. VM Location: The Recovery Services vault's location (e.g., Canada East) does not automatically lock you to that region for your replicated VMs. The vault is a management plane, a central hub for your recovery settings and policies. It contains the metadata for your replicated items, but the actual replicated data (the disks) and the failover VMs reside in the target region you specify during the replication wizard.

Network Is Not Optional: The wizard fails without a target network is the most critical point. ASR is not just replicating data to a black box. It’s preparing a complete, functional VM in a secondary region. When a disaster happens, that VM needs a network interface (NIC) and a virtual network (VNet) to connect to so it can come online and serve traffic. The "just replication to the vault" mindset is a common pitfall because the service is more than just a backup; it's a full disaster recovery solution.

Even if you don't intend to use the replicated VM for any purpose other than testing, ASR still requires a target VNet and subnet to attach the VM to.

Vault Location ≠ Target Region

The Recovery Services Vault location (e.g., Canada East) only determines where metadata and backup data are stored.

You can replicate VMs to any supported region, as long as you configure the target correctly.

Re-run the Replication Wizard with Full Target Details

Go to your VM > Disaster Recovery blade > Enable Replication and make sure to:

Target Region: Choose the region you want the replica VM to live in (e.g., Canada Central).

Target Subscription & Resource Group: Select the correct subscription and an existing resource group in the target region.

Target Virtual Network (VNet): This is critical:

Pick an existing VNet in the target region.

Or create a new one before running the wizard.

Without a VNet, ASR cannot create the target NIC, and the job will fail.

Confirm Prerequisites in Target Region: Before retrying replication, double-check:

VM Size Availability: Use Azure VM Size Availability to confirm your VM SKU is supported in the target region.

Quota: Go to Azure Quota Support and request quota for the VM size in the target region.

Resource Group & VNet: Ensure both exist in the target region and are visible to the wizard.

Then decide which region you want to replicate. Create a target resource group + VNet in that region. Re-enable replication, and in the wizard select:

Target region = your chosen region

Target resource group = the RG you just created

Target virtual network = the VNet you just created

Hope this helps! Please let us know if you need further assistance with this
William Rosenblath 5 Reputation points

2025-09-24T12:44:35.5866667+00:00

Alright, so I don't need a vault in central region and one vault in canada east will do, modify the ASR to point to a vnet in the target region. Got it.

I'll give that a try.
William Rosenblath 5 Reputation points

2025-09-24T18:37:06.9+00:00

So I tried this and Azure doesn't see the central hub & subnet I created when I try to enable replication from the existing vault, it only shows items in the east vault. I create a new vault, but then that would require me to redo the asr completely which is a lot of unnecessary work. So far I am not very impressed with Azure. It's over complicated and not well documented. The documentation seems behind the working items like the ASR for example.

I need someone who says they know how this works to try it. Where can I get some help? This back and forth is just wasting my time.
Sandhya Kommineni 1,575 Reputation points Microsoft External Staff Moderator

2025-09-30T07:40:20.6733333+00:00

Hi William Rosenblath, Thanks for your patience

We are checking on your issue, will get back to you

Your answer

William Rosenblath 5 Reputation points

2025-09-18T20:56:34.6233333+00:00

Note I am in the owner role for this, so have all permissions.

I don't see any issues with the setup so far unless something isn't being created in the resource group that is required.
Bharath Y P 1,350 Reputation points Microsoft External Staff Moderator

2025-09-22T17:27:36.4466667+00:00

Hello William Rosenblath, Just checking in to see if the solution shared above help you to resolve your issue. please reach out to us If you have any further questions. Thanks
William Rosenblath 5 Reputation points

2025-09-22T17:37:59.55+00:00

Can I replicate to another region even though my resource group and all of the other items are Canada east. Canada East represents the best location to reduce any latency vs Canada Central for example. I don't understand the sizing info enough to know what to do there. I have a support ticket opened as well.
Bharath Y P 1,350 Reputation points Microsoft External Staff Moderator

2025-09-22T21:47:43.0966667+00:00

Hello William Rosenblath,

Yes, you can replicate it to a different region, but there are some important considerations:

Azure Site Recovery (ASR) allows replication to any supported Azure region, regardless of the resource group’s location.

Your resource group, storage, and VNet can remain in Canada East; the replicated VM will be deployed in the target region.

The replicated VM will have a separate VNet and storage account in the target region.

Check quotas in the alternative region first then replicate to Canada Central temporarily later, you can migrate the failover VM to Canada East once quotas are approved.
William Rosenblath 5 Reputation points

2025-09-23T14:55:49.1133333+00:00

Can I get some assistance doing this. It seems to be choosing east on it's own , perhaps it's based on the recovery services vault, I'm not sure. I just don't know how to make it go to a different target. I tried telling it not to go to a network, just replication to the vault but it still fails, I need more details on how to make this work.
William Rosenblath 5 Reputation points

2025-09-24T12:44:35.5866667+00:00

Alright, so I don't need a vault in central region and one vault in canada east will do, modify the ASR to point to a vnet in the target region. Got it.

I'll give that a try.
William Rosenblath 5 Reputation points

2025-09-24T18:37:06.9+00:00

So I tried this and Azure doesn't see the central hub & subnet I created when I try to enable replication from the existing vault, it only shows items in the east vault. I create a new vault, but then that would require me to redo the asr completely which is a lot of unnecessary work. So far I am not very impressed with Azure. It's over complicated and not well documented. The documentation seems behind the working items like the ASR for example.

I need someone who says they know how this works to try it. Where can I get some help? This back and forth is just wasting my time.
Sandhya Kommineni 1,575 Reputation points Microsoft External Staff Moderator

2025-09-30T07:40:20.6733333+00:00

Hi William Rosenblath, Thanks for your patience

We are checking on your issue, will get back to you

Share via

ASR not working receiving error Error ID 310015

Your answer