You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<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
44
@@ -56,10 +56,10 @@ The following table shows the limits on the media reserved units S1, S2, and S3.
56
56
57
57
| Resource | Default Limit |
58
58
| --- | --- |
59
-
| Jobs per Media Services account | 500,000 <sup>(3)</sup> (fixed)|
59
+
|[Jobs](transforms-jobs-concept.md) per Media Services account | 500,000 <sup>(3)</sup> (fixed)|
60
60
| Job inputs per Job | 50 (fixed)|
61
61
| Job outputs per Job | 20 (fixed) |
62
-
| Transforms per Media Services account | 100 (fixed)|
62
+
|[Transforms](transforms-jobs-concept.md) per Media Services account | 100 (fixed)|
63
63
| Transform outputs in a Transform | 20 (fixed) |
64
64
| Files per job input|10 (fixed)|
65
65
@@ -71,22 +71,22 @@ Any Job record in your account older than 90 days will be automatically deleted,
71
71
72
72
| Resource | Default Limit |
73
73
| --- | --- |
74
-
| Live Events <sup>(4)</sup> per Media Services account |5|
74
+
|[Live Events](live-events-outputs-concept.md) <sup>(4)</sup> per Media Services account |5|
75
75
| Live Outputs per Live Event |3 <sup>(5)</sup> |
76
76
| Max Live Output duration | 25 hours |
77
77
78
-
<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).
78
+
<sup>4</sup> For detailed information about Live Event limitations, see [Live Event types comparison and limitations](live-event-types-comparison.md).
79
79
80
80
<sup>5</sup> Live Outputs start on creation and stop when deleted.
81
81
82
82
## Packaging & delivery limits
83
83
84
84
| Resource | Default Limit |
85
85
| --- | --- |
86
-
| Streaming Endpoints (stopped or running) per Media Services account|2 (fixed)|
87
-
| Dynamic Manifest Filters|100|
88
-
| Streaming Policies | 100 <sup>(6)</sup> |
89
-
| Unique Streaming Locators associated with an Asset at one time | 100<sup>(7)</sup> (fixed) |
86
+
|[Streaming Endpoints](streaming-endpoint-concept.md) (stopped or running) per Media Services account|2 (fixed)|
| Unique [Streaming Locators](streaming-locators-concept.md) associated with an Asset at one time | 100<sup>(7)</sup> (fixed) |
90
90
91
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
92
@@ -96,7 +96,7 @@ Any Job record in your account older than 90 days will be automatically deleted,
96
96
97
97
| Resource | Default Limit |
98
98
| --- | --- |
99
-
| Options per Content Key Policy |30 |
99
+
| Options per [Content Key Policy](content-key-policy-concept.md)|30 |
100
100
| Licenses per month for each of the DRM types on Media Services key delivery service per account|1,000,000|
0 commit comments