cannot deploy an lcs environment using azure subscription despite setting everything up correctly

Question

Hello,

I am consistently facing an error deploying an LCS development environment against my subscription: it fails the first hurdle almost as if pre-validation checks are failing immediately so it may be something to do with my quotas:

I have already check that:

Microsoft.Compute/Network/Resource etc providers in the resource providers are registered. The azure connector is setup against my azure subscription ID and the project settings are authorized with ARM. The region is set to "central india" with a storage account for my developers convenience. I simply keep getting the above error. I have made several requests to increase the quotas (not against the provider "microsoft.network" because I can't find it in the list)

What am I missing here? why isn't my D365 F&O environment setting up here?

Answer 1

Hello @M Khan ,

Thank you again for your time during the team call. Adding the summary of what we discussed through the call below:

We attempted to deploy several VM sizes through Microsoft Dynamics Lifecycle Services but encountered the same error each time. This was unexpected, as the available quota in the Microsoft Azure Portal indicated sufficient resources.

To rule out a Compute quota issue, we tested by creating a VM directly in the Central India region via the Azure Portal (outside Lifecycle Services), and it was successful. This confirms that:

• The subscription has enough quota.
• The Central India region is accessible.
• The issue is not related to overall Azure capacity.

We then checked that the VM size selected in Lifecycle Services matched the correct Azure VM family by searching online and reviewing the official documentation for the Dadsv7 size series – Azure Virtual Machines. This ensured we were verifying the appropriate quota type.

During our discussion, we noticed the customer was using a five-year-old YouTube tutorial. As the platform has changed, we suggested reviewing the latest guidance and considering Microsoft Power Platform if relevant.

For further technical issues related to Lifecycle Services, we recommended using the official Microsoft Dynamics 365 Community forum, which is monitored and serves as the recommended support channel.

References:  https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/fin-ops/lcs/lcs-support

Answer 2

M Khan hi,

from ur screenshots this doest look like a generic provider registration problem but much more like a compute quota or subscription type restriction that lcs is failing during pre validation.

D365 f and o dev environments require specific vm sizes typically d series such as d13 or similar and lcs performs a silent check for available regional vcpus before it even starts provisioning.

even if total regional vcpus shows available in usage plus quotas that does not automatically mean the specific vm family required for f and o is enabled in that region for ur subscription.

look to usage plus quotas then filter by provider compute and specifically check standard dsv or d family vcpu quota in central india not just total regional vcpus. if the vm family quota is zero lcs will fail immediately without a clear message.

is ur subscription is not a visual studio or student subscription because many of those block high memory d series machines required by f and o.

May be that central india does not always have sufficient capacity for specific vm skus so try west europe or another recommended region to test whether it is regional capacity rather than config. lcs does not surface azure capacity errors clearly so this kind of failure often appears as generic pre validation error even though the root cause is vm family quota or subscription restriction.

rgds,

Alex