Skip to content

Commit 9c9efd9

Browse files
GitHubber17GitHubber17
authored
Merge pull request #109782 from Juliako/patch-21
Update media-servieces-limits-quotas-constraints.md
2 parents 36eccb0 + 2a89376 commit 9c9efd9

File tree

2 files changed

+142
-26
lines changed

2 files changed

+142
-26
lines changed

‎articles/media-services/latest/limits-quotas-constraints.md

Lines changed: 87 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,9 +14,94 @@ ms.date: 03/31/2020
1414
ms.author: juliako
1515
---
1616

17-
# Azure Media Services quotas and limitations
17+
# Azure Media Services quotas and limits
1818

19-
[!INCLUDE [media-servieces-limits-quotas-constraints](../../../includes/media-servieces-limits-quotas-constraints.md)]
19+
This article lists some of the most common Microsoft Azure Media Services limits, which are also sometimes called quotas.
20+
21+
> [!NOTE]
22+
> For resources that aren't fixed, open a support ticket to ask for an increase in the quotas. Don't create additional Azure Media Services accounts in an attempt to obtain higher limits.
23+
24+
## Account limits
25+
26+
| Resource | Default Limit |
27+
| --- | --- |
28+
| [Media Services accounts](media-services-account-concept.md) in a single subscription | 25 (fixed) |
29+
30+
## Asset limits
31+
32+
| Resource | Default Limit |
33+
| --- | --- |
34+
| [Assets](assets-concept.md) per Media Services account | 1,000,000|
35+
36+
## Storage limits
37+
38+
| Resource | Default Limit |
39+
| --- | --- |
40+
| File size| In some scenarios, there is a limit on the maximum file size supported for processing in Media Services. <sup>(1)</sup> |
41+
| [Storage accounts](storage-account-concept.md) | 100<sup>(2)</sup> (fixed) |
42+
43+
<sup>1</sup> The maximum size supported for a single blob is currently up to 5 TB in Azure Blob Storage. Additional limits apply in Media Services based on the VM sizes that are used by the service. The size limit applies to the files that you upload and also the files that get generated as a result of Media Services processing (encoding or analyzing). If your source file is larger than 260-GB, your Job will likely fail.
44+
45+
The following table shows the limits on the media reserved units S1, S2, and S3. If your source file is larger than the limits defined in the table, your encoding job fails. If you encode 4K resolution sources of long duration, you're required to use S3 media reserved units to achieve the performance needed. If you have 4K content that's larger than the 260-GB limit on the S3 media reserved units, open a support ticket.
46+
47+
|Media reserved unit type|Maximum input size (GB)|
48+
|---|---|
49+
|S1 | 26|
50+
|S2 | 60|
51+
|S3 |260|
52+
53+
<sup>2</sup> The storage accounts must be from the same Azure subscription.
54+
55+
## Jobs (encoding & analyzing) limits
56+
57+
| Resource | Default Limit |
58+
| --- | --- |
59+
| [Jobs](transforms-jobs-concept.md) per Media Services account | 500,000 <sup>(3)</sup> (fixed)|
60+
| Job inputs per Job | 50 (fixed)|
61+
| Job outputs per Job | 20 (fixed) |
62+
| [Transforms](transforms-jobs-concept.md) per Media Services account | 100 (fixed)|
63+
| Transform outputs in a Transform | 20 (fixed) |
64+
| Files per job input|10 (fixed)|
65+
66+
<sup>3</sup> This number includes queued, finished, active, and canceled Jobs. It does not include deleted Jobs.
67+
68+
Any Job record in your account older than 90 days will be automatically deleted, even if the total number of records is below the maximum quota.
69+
70+
## Live streaming limits
71+
72+
| Resource | Default Limit |
73+
| --- | --- |
74+
| [Live Events](live-events-outputs-concept.md) <sup>(4)</sup> per Media Services account |5|
75+
| Live Outputs per Live Event |3 <sup>(5)</sup> |
76+
| Max Live Output duration | 25 hours |
77+
78+
<sup>4</sup> For detailed information about Live Event limitations, see [Live Event types comparison and limitations](live-event-types-comparison.md).
79+
80+
<sup>5</sup> Live Outputs start on creation and stop when deleted.
81+
82+
## Packaging & delivery limits
83+
84+
| Resource | Default Limit |
85+
| --- | --- |
86+
| [Streaming Endpoints](streaming-endpoint-concept.md) (stopped or running) per Media Services account|2 (fixed)|
87+
| [Dynamic Manifest Filters](filters-dynamic-manifest-overview.md)|100|
88+
| [Streaming Policies](streaming-policy-concept.md) | 100 <sup>(6)</sup> |
89+
| Unique [Streaming Locators](streaming-locators-concept.md) associated with an Asset at one time | 100<sup>(7)</sup> (fixed) |
90+
91+
<sup>6</sup> When using a custom [Streaming Policy](https://docs.microsoft.com/rest/api/media/streamingpolicies), you should design a limited set of such policies for your Media Service account, and re-use them for your StreamingLocators whenever the same encryption options and protocols are needed. You should not be creating a new Streaming Policy for each Streaming Locator.
92+
93+
<sup>7</sup> Streaming Locators are not designed for managing per-user access control. To give different access rights to individual users, use Digital Rights Management (DRM) solutions.
94+
95+
## Protection limits
96+
97+
| Resource | Default Limit |
98+
| --- | --- |
99+
| Options per [Content Key Policy](content-key-policy-concept.md) |30 |
100+
| Licenses per month for each of the DRM types on Media Services key delivery service per account|1,000,000|
101+
102+
## Support ticket
103+
104+
For resources that are not fixed, you may ask for the quotas to be raised, by opening a [support ticket](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest). Include detailed information in the request on the desired quota changes, use-case scenarios, and regions required. <br/>Do **not** create additional Azure Media Services accounts in an attempt to obtain higher limits.
20105

21106
## Next steps
22107

‎includes/media-servieces-limits-quotas-constraints.md

Lines changed: 55 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -6,32 +6,27 @@ ms.date: 03/31/2020
66
ms.author: juliako
77
---
88

9-
This section describes quotas and limitations in Azure Media Services.
10-
119
> [!NOTE]
1210
> For resources that aren't fixed, open a support ticket to ask for an increase in the quotas. Don't create additional Azure Media Services accounts in an attempt to obtain higher limits.
1311
12+
### Account limits
13+
1414
| Resource | Default Limit |
1515
| --- | --- |
1616
| Media Services accounts in a single subscription | 25 (fixed) |
17+
18+
### Asset limits
19+
20+
| Resource | Default Limit |
21+
| --- | --- |
1722
| Assets per Media Services account | 1,000,000|
18-
| Dynamic Manifest Filters|100|
19-
| Job inputs per Job | 50 (fixed)|
20-
| Job outputs per Job | 20 (fixed) |
21-
| Transform outputs in a Transform | 20 (fixed) |
22-
| Files per job input|10 (fixed)|
23+
24+
### Storage limits
25+
26+
| Resource | Default Limit |
27+
| --- | --- |
2328
| File size| In some scenarios, there is a limit on the maximum file size supported for processing in Media Services. <sup>(1)</sup> |
24-
| Jobs per Media Services account | 500,000 <sup>(2)</sup> (fixed)|
25-
| Live Events per Media Services account |5|
26-
| Live Outputs per Live Event |3 <sup>(3)</sup> |
27-
| Max Live Output duration | 25 hours |
28-
| Storage accounts | 100<sup>(4)</sup> (fixed) |
29-
| Streaming Endpoints (stopped or running) per Media Services account|2 (fixed)|
30-
| Streaming Policies | 100 <sup>(5)</sup> |
31-
| Transforms per Media Services account | 100 (fixed)|
32-
| Unique Streaming Locators associated with an Asset at one time | 100<sup>(6)</sup> (fixed) |
33-
| Options per Content Key Policy |30 |
34-
| Licenses per month for each of the DRM types on Media Services key delivery service per account|1,000,000|
29+
| Storage accounts | 100<sup>(2)</sup> (fixed) |
3530

3631
<sup>1</sup> The maximum size supported for a single blob is currently up to 5 TB in Azure Blob Storage. Additional limits apply in Media Services based on the VM sizes that are used by the service. The size limit applies to the files that you upload and also the files that get generated as a result of Media Services processing (encoding or analyzing). If your source file is larger than 260-GB, your Job will likely fail.
3732

@@ -43,19 +38,55 @@ The following table shows the limits on the media reserved units S1, S2, and S3.
4338
|S2 | 60|
4439
|S3 |260|
4540

46-
<sup>2</sup> This number includes queued, finished, active, and canceled Jobs. It does not include deleted Jobs.
41+
<sup>2</sup> The storage accounts must be from the same Azure subscription.
42+
43+
### Jobs (encoding & analyzing) limits
44+
45+
| Resource | Default Limit |
46+
| --- | --- |
47+
| Jobs per Media Services account | 500,000 <sup>(3)</sup> (fixed)|
48+
| Job inputs per Job | 50 (fixed)|
49+
| Job outputs per Job | 20 (fixed) |
50+
| Transforms per Media Services account | 100 (fixed)|
51+
| Transform outputs in a Transform | 20 (fixed) |
52+
| Files per job input|10 (fixed)|
53+
54+
<sup>3</sup> This number includes queued, finished, active, and canceled Jobs. It does not include deleted Jobs.
4755

4856
Any Job record in your account older than 90 days will be automatically deleted, even if the total number of records is below the maximum quota.
4957

50-
<sup>3</sup> Live Outputs start on creation and stop when deleted.
58+
### Live streaming limits
59+
60+
| Resource | Default Limit |
61+
| --- | --- |
62+
| Live Events <sup>(4)</sup> per Media Services account |5|
63+
| Live Outputs per Live Event |3 <sup>(5)</sup> |
64+
| Max Live Output duration | 25 hours |
65+
66+
<sup>4</sup> For detailed information about Live Event limitations, see [Live Event types comparison and limitations](../articles/media-services/latest/live-event-types-comparison.md).
67+
68+
<sup>5</sup> Live Outputs start on creation and stop when deleted.
5169

52-
<sup>4</sup> The storage accounts must be from the same Azure subscription.
70+
### Packaging & delivery limits
5371

54-
<sup>5</sup> When using a custom [Streaming Policy](https://docs.microsoft.com/rest/api/media/streamingpolicies), you should design a limited set of such policies for your Media Service account, and re-use them for your StreamingLocators whenever the same encryption options and protocols are needed. You should not be creating a new Streaming Policy for each Streaming Locator.
72+
| Resource | Default Limit |
73+
| --- | --- |
74+
| Streaming Endpoints (stopped or running) per Media Services account|2 (fixed)|
75+
| Dynamic Manifest Filters|100|
76+
| Streaming Policies | 100 <sup>(6)</sup> |
77+
| Unique Streaming Locators associated with an Asset at one time | 100<sup>(7)</sup> (fixed) |
78+
79+
<sup>6</sup> When using a custom [Streaming Policy](https://docs.microsoft.com/rest/api/media/streamingpolicies), you should design a limited set of such policies for your Media Service account, and re-use them for your StreamingLocators whenever the same encryption options and protocols are needed. You should not be creating a new Streaming Policy for each Streaming Locator.
80+
81+
<sup>7</sup> Streaming Locators are not designed for managing per-user access control. To give different access rights to individual users, use Digital Rights Management (DRM) solutions.
5582

56-
<sup>6</sup> Streaming Locators are not designed for managing per-user access control. To give different access rights to individual users, use Digital Rights Management (DRM) solutions.
83+
### Protection limits
84+
85+
| Resource | Default Limit |
86+
| --- | --- |
87+
| Options per Content Key Policy |30 |
88+
| Licenses per month for each of the DRM types on Media Services key delivery service per account|1,000,000|
5789

5890
### Support ticket
5991

6092
For resources that are not fixed, you may ask for the quotas to be raised, by opening a [support ticket](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest). Include detailed information in the request on the desired quota changes, use-case scenarios, and regions required. <br/>Do **not** create additional Azure Media Services accounts in an attempt to obtain higher limits.
61-

0 commit comments

Comments
 (0)