(csp:request-quota)=
# Request Azure backend quota

After the workspace is created, the next step is to request the computation resource quota for the workspace. The SeqsLab workspace uses Azure Batch as the backend computation management service on Azure. 

The Batch account is deployed
in [Subscription Service Node](https://docs.microsoft.com/en-us/azure/batch/best-practices#pools). The global
administrator needs to request for the computation quota to ensure that the batch account has sufficient computation
resources. On [Subscription Mode](https://learn.microsoft.com/en-us/azure/batch/batch-quota-limit#core-quotas-in-user-subscription-mode), computing quotas are limited by regional computing cores, per-series computing cores, and other resource subscriptions. 
Details are available for [regional vCPU quotas](https://learn.microsoft.com/en-us/azure/quotas/regional-quota-requests), [per-vm-quota-requests](https://learn.microsoft.com/en-us/azure/quotas/per-vm-quota-requests), and [spot-quota](https://learn.microsoft.com/en-us/azure/quotas/spot-quota).
The following are the recommended resource quotas for common scenarios:

* Staging or small-scale production testing

    | Item | Quota | 
    | :-- | :-- |
    | Regional vCPUs | 2,300 |
    | Spot VMs | 1,000 |
    | Dv2-series VMs | 1,000 |
    | NCv3-series VMs | 300 |
    | Active jobs and job schedules per Batch account | 100 |
    | Pools per Batch account | 100 |
    | Public IP addresses |  Basic: 100 / Standard: 100 |

    ```{note}
    Up to 2,300 CPU cores and 50 NVIDIA Tesla V100 GPU cards can be allocated as 100 distinct batch clusters simultaneously.
    ```

* Running jobs

    | Item | Quota | 
    | :-- |:------|
    | Regional vCPUs | 4,000 |
    | Spot VMs | 2,000 |
    | Dv2-series VMs | 2,000 |
    | Active jobs and job schedules per Batch account | 300   |
    | Pools per Batch account | 300   |
    | Public IP addresses |  Basic: 600 / Standard: 600 |

* Running GPUs

    | Item | Quota | 
    | :-- | :-- |
    | Regional vCPUs | 6,000 |
    | Spot VMs | 2,000 |
    | NCasT4_v3-series | 2,000 |
    | Dv2-series VMs | 2,000 |
    | Active jobs and job schedules per Batch account | 500 |
    | Pools per Batch account | 500 |
    | Public IP addresses |  Basic: 1000 / Standard: 1000 |

For other use cases, such as when conducting an extra large population cohort study workflow or GPU intensive workflows, [contact SeqsLab support](https://webchat.botframework.com/embed/seqslab-support-bot?s=iVCQweRG-ow.jW4ai75IjHY7gNGZBoXeKzz_tx4Zo_OKf46mchw0KyE) for a detailed computation scaling consultation.

To request a [quota increase on Azure](https://docs.microsoft.com/en-us/azure/batch/batch-quota-limit#increase-a-quota)(![external link](../images/external-link.png)), reach out to Azure support. This process typically takes a few business days to complete.

## Next steps

The Global Administrator must complete the following to enable data processing on SeqsLab.  

1. [Manage SeqsLab users](cli:manage-users)
1. Recommend: [Manage Container Registry](tutorials:cli-container-registry)
1. Optional: [Configure storage log access](csp:azure-log-access)