Skip to content

Commit cb39a50

Browse files
authored
Merge pull request #288471 from yousefi-msft/limits-quotas-20241015
limits and quotas
2 parents 5b7e45a + 1f912c9 commit cb39a50

File tree

2 files changed

+74
-0
lines changed

2 files changed

+74
-0
lines changed

articles/modeling-simulation-workbench/index.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -80,6 +80,8 @@ landingContent:
8080
url: ./resources-troubleshoot.md
8181
- text: Known issues
8282
url: ./troubleshoot-known-issues.md
83+
- text: Limits and quotas
84+
url: ./limits-quotas.md
8385
- text: Business continuity
8486
url: ./disaster-recovery.md
8587
- text: Get support
Lines changed: 72 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,72 @@
1+
---
2+
title: "Limits and quotas: Azure Modeling and Simulation Workbench"
3+
description: "Learn about limits and quotas in the Azure Modeling and Simulation Workbench."
4+
author: yousefi-msft
5+
ms.author: yousefi
6+
ms.service: modeling-simulation-workbench
7+
ms.topic: limits-and-quotas
8+
ms.date: 10/15/2024
9+
10+
#customer intent: As a user in Azure Modeling and Simulation Workbench, I want to learn about limitations and quotas in the environment.
11+
---
12+
13+
# Azure Modeling and Simulation Workbench limits and quotas
14+
15+
The Modeling and Simulation Workbench has various quotas and limitations on deploying resources or configurations. Workbenches and chambers have overhead which might affect some of the available resource quotas. Those cases are called out in this article.
16+
17+
Resources, such as chambers and virtual machines, appear in your user subscription, but are deployed into a Microsoft managed environment and subscription. Quotas applied to your own subscription don't apply to Modeling and Simulation Workbench.
18+
19+
## Chambers
20+
21+
| Item | Quota or limit | Notes |
22+
|--------------------------------------|-------------------|--------------------------------------------------------------------------------------------------------------|
23+
| Chambers per workbench | Limit 3 | |
24+
| Users per chamber | No limit | |
25+
| Supports parallel deployment? | No | Only one chamber can be deployed at any given time. |
26+
| Identity and Access Management (IAM) | Users only | Chambers don't support Azure Groups. Individual user role assignments only. |
27+
| Deployment location | Same as workbench | Chambers and dependent resources are deployed to the workbench's location, regardless of requested location. |
28+
29+
## Virtual machines
30+
31+
Virtual machines (VM) are limited by a different subscription quota than your customer quota. Requesting quota increases to your customer subscription doesn't affect your VM quota in Modeling and Simulation Workbench. Modeling and Simulation Workbench provides a select set of high-performance and general computing VMs. To learn about which offerings and families are available, see the [VM offerings](./concept-vm-offerings.md) guide. The following table lists the quota by family.
32+
33+
The table lists quota by virtual CPUs (vCPU), where each physical CPU is equivalent to two vCPUs. Consult the VM guide to determine how many vCPUs each VM has.
34+
35+
vCPU quotas listed are initial default. More capacity can be requested.
36+
37+
| Item | Quota or limit | Notes |
38+
|-------------------------------|--------------------|--------------------------------------------------------------------------------------------------|
39+
| D-series | 156 vCPUs | D-series are used in workbench infrastructure. Creating more chambers reduces D-series quantity. |
40+
| E-series | 256 vCPUs | Initial quota, more can be requested. |
41+
| F-series | 100 vCPUs | Initial quota, more can be requested. |
42+
| M-series | 128 vCPUs | Initial quota, more can be requested. |
43+
| Supports parallel deployment? | Yes | Multiple VMs can be deployed simultaneously. |
44+
| Deployment location | Same as workbench. | |
45+
46+
## Storage
47+
48+
| Item | Quota or limit | Notes |
49+
|----------------------------------|--------------------------------------------|---------------------------------------------|
50+
| Home volume quota | 200-GB limit | For entire volume, shared across all users. |
51+
| `datain` volume | 1-TB limit | |
52+
| `dataout` volume | 1-TB limit | |
53+
| File size limit on data pipeline | 100-GB limit per file | |
54+
| Chamber storage volumes | 4 TB initial, 4-TB increments, 20-TB quota | More quota can be requested. |
55+
| Shared storage volumes | 4 TB initial, 4-TB increments, 20-TB quota | More quota can be requested. |
56+
57+
## Networking
58+
59+
| Item | Quota or limit | Notes |
60+
|----------------------------------------------------|----------------|----------------------------------------------------------------------|
61+
| Connectors per chamber | 1 | Limit one connector per chamber. |
62+
| Number of allowlist entries (public IP connector) | 200 | Max. limit on entries in the table. Subnets ranges can be specified. |
63+
| Maximum subnet mask (public IP connector) | /24 | |
64+
65+
## License service
66+
67+
* Limit of one license file can be uploaded to each license server at a time. Subsequent uploads overwrite the current file.
68+
69+
## Related content
70+
71+
* [VM Offerings in Azure Modeling and Simulation Workbench](concept-vm-offerings.md)
72+
* [Storage and access in Azure Modeling and Simulation Workbench](concept-storage.md)

0 commit comments

Comments
 (0)