A very common scenario is to use one Azure subscription for both production and non-production RMS deployments. When doing this, however, you'll need to make sure that there is enough vCPU in the VM quotas for the deployments.

vCPU quota is set at the subscription/region level, and all resources running in that subscription/region combination will share the quota you set. Therefore, when you add another RMS deployment to your subscription, you'll need to check the quota and increase it if necessary.

Contact Ravnur Support if you deploy another RMS instance into the same subscription. We'll provide your vCPU quota estimate.

Here's an example of what this means in practice: A customer has deployed a non-production RMS instance to Central US. The encoding pool uses F8als_v7 VMs (8 vCPUs each), and the scaling rule is set to 10 VMs. The system pool uses D2as_v5 VMs (2 vCPUs each), and the scaling rule is set to 10. For this subscription, the customer requires a minimum of 80 vCPUs for the Standard Falsv7 Family and 20 vCPUs for the Standard DASv5 Family in the Central US region.

Now the customer deploys a production instance in the Central US region in the same subscription. The customer wants the production instance to scale to 20 encoders and 20 system pool VMs. This requires adding 160 vCPUs for the Standard Falsv7 Family and 40 vCPUs for the Standard DASv5 Family in Central US.

The total quota should be at least 240 vCPUs for the Falsv7 family and 60 vCPUs for the DASv5 family.