Skip to content

Commit 3539581

Browse files
American-DipperAmerican-Dipper
authored
Merge pull request #109740 from Juliako/limitations
updating limitations
2 parents a522a48 + ea8742c commit 3539581

File tree

3 files changed

+71
-54
lines changed

3 files changed

+71
-54
lines changed

‎articles/azure-resource-manager/management/azure-subscription-service-limits.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -239,7 +239,11 @@ The following table details the features and limits of the Basic, Standard, and
239239

240240
## Media Services limits
241241

242-
[!INCLUDE [azure-mediaservices-limits](../../../includes/azure-mediaservices-limits.md)]
242+
[!INCLUDE [azure-mediaservices-limits](../../../includes/media-servieces-limits-quotas-constraints.md)]
243+
244+
### Media Services v2 (legacy)
245+
246+
For limits specific to Media Services v2 (legacy), see [Media Services v2 (legacy)](https://docs.microsoft.com/azure/media-services/previous/media-services-quotas-and-limitations)
243247

244248
## Mobile Services limits
245249

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

Lines changed: 5 additions & 53 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Quotas and limitations in Azure Media Services v3 | Microsoft Docs
3-
description: This topic describes quotas and limitations in Microsoft Azure Media Services v3.
2+
title: Quotas and limitations in Azure Media Services
3+
description: This topic describes quotas and limitations in Microsoft Azure Media Services.
44
services: media-services
55
documentationcenter: ''
66
author: Juliako
@@ -10,61 +10,13 @@ editor: ''
1010
ms.service: media-services
1111
ms.workload:
1212
ms.topic: article
13-
ms.date: 10/17/2019
13+
ms.date: 03/31/2020
1414
ms.author: juliako
1515
---
1616

17-
# Quotas and limitations in Azure Media Services v3
17+
# Azure Media Services quotas and limitations
1818

19-
This article describes quotas and limitations in Azure Media Services v3.
20-
21-
| Resource | Default Limit |
22-
| --- | --- |
23-
| Assets per Azure Media Services account | 1,000,000|
24-
| Dynamic Manifest Filters|100|
25-
| Job inputs per Job | 50 (fixed)|
26-
| Job outputs per Job | 20 (fixed) |
27-
| Transform outputs in a Transform | 20 (fixed) |
28-
| Files per job input|10 (fixed)|
29-
| File size| In some scenarios, there is a limit on the maximum file size supported for processing in Media Services. <sup>(1)</sup> |
30-
| Jobs per Media Services account | 500,000 <sup>(2)</sup> (fixed)|
31-
| Live Events per Media Services account |5|
32-
| Media Services accounts in a single subscription | 25 (fixed) |
33-
| Live Outputs per Live Event |3 <sup>(3)</sup> |
34-
| Max Live Output duration | 25 hours |
35-
| Storage accounts | 100<sup>(4)</sup> (fixed) |
36-
| Streaming Endpoints (stopped or running) per Media Services account|2 (fixed)|
37-
| Streaming Policies | 100 <sup>(5)</sup> |
38-
| Transforms per Media Services account | 100 (fixed)|
39-
| Unique Streaming Locators associated with an Asset at one time | 100<sup>(6)</sup> (fixed) |
40-
| Options per Content Key Policy |30 |
41-
| Licenses per month for each of the DRM types on Media Services key delivery service per account|1,000,000|
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> This number includes queued, finished, active, and canceled Jobs. It does not include deleted Jobs.
54-
55-
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.
56-
57-
<sup>3</sup> Live Outputs start on creation and stop when deleted.
58-
59-
<sup>4</sup> The storage accounts must be from the same Azure subscription.
60-
61-
<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.
62-
63-
<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.
64-
65-
## Support ticket
66-
67-
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.
19+
[!INCLUDE [media-servieces-limits-quotas-constraints](../../../includes/media-servieces-limits-quotas-constraints.md)]
6820

6921
## Next steps
7022

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

Lines changed: 61 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,61 @@
1+
---
2+
author: Juliako
3+
ms.service: media-services
4+
ms.topic: include
5+
ms.date: 03/31/2020
6+
ms.author: juliako
7+
---
8+
9+
This section describes quotas and limitations in Azure Media Services.
10+
11+
> [!NOTE]
12+
> 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.
13+
14+
| Resource | Default Limit |
15+
| --- | --- |
16+
| Media Services accounts in a single subscription | 25 (fixed) |
17+
| 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+
| 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|
35+
36+
<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.
37+
38+
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.
39+
40+
|Media reserved unit type|Maximum input size (GB)|
41+
|---|---|
42+
|S1 | 26|
43+
|S2 | 60|
44+
|S3 |260|
45+
46+
<sup>2</sup> This number includes queued, finished, active, and canceled Jobs. It does not include deleted Jobs.
47+
48+
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.
49+
50+
<sup>3</sup> Live Outputs start on creation and stop when deleted.
51+
52+
<sup>4</sup> The storage accounts must be from the same Azure subscription.
53+
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.
55+
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.
57+
58+
### Support ticket
59+
60+
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)