Skip to content

Latest commit

 

History

History
49 lines (35 loc) · 3.1 KB

stream-streaming-policy-concept.md

File metadata and controls

49 lines (35 loc) · 3.1 KB
Raw
title description author ms.service ms.topic ms.date ms.author
Streaming Policies in Azure Media Services
This article gives an explanation of what Streaming Policies are, and how they are used by Azure Media Services.
IngridAtMicrosoft
media-services
conceptual
01/09/2023
inhenkel

Streaming Policies

In Azure Media Services v3, Streaming Policies enable you to define streaming protocols and encryption options for your Streaming Locators. Media Services v3 provides some predefined Streaming Policies so that you can use them directly for trial or production.

The currently available predefined Streaming Policies:

  • Predefined_DownloadOnly. For allowing downloading only.
  • Predefined_ClearStreamingOnly. For allowing clear streaming only.
  • Predefined_DownloadAndClearStreaming. For allowing both downloading and clear streaming.
  • Predefined_ClearKey. For allowing HLS/DASH/Smooth encrypted with envelopeEncryption with Media Services issuing the content key.
  • Predefined_MultiDrmCencStreaming. For allowing streaming with DASH/Smooth encrypted with commonEncryptionCenc with Media Services issuing the PlayReady and Widevine licenses.
  • Predefined_MultiDrmStreaming. For allowing streaming with DASH/Smooth encrypted with commonEncryptionCenc with Media Services issuing the PlayReady and Widevine licenses, or for allowing streaming with HLS encrypted with commonEncryptionCbcs with Media Services issuing the FairPlay license.
  • If none of the above meets your needs, create a new streaming policy.

Important

  • Properties of Streaming Policies that are of the Datetime type are always in UTC format.
  • You should design a limited set of policies for your Media Service account and reuse them for your Streaming Locators whenever the same options are needed. For more information, see Quotas and limits.

If encrypting your content, you need to create a Content Key Policy.

If you have special requirements (for example, if you want to specify different protocols, need to use a custom key delivery service, or need to use an unencrypted audio track), you can create a custom Streaming Policy.

Clear Key Common Encryption (CENC)

A Content Key Policy is not needed for unencrypted streaming or downloading. CENC allows you to have common encryption without digital rights management for when you need encryption but your player doesn't support AES envelope encryption.

Players that allow CENC encryption include:

  • dash.js from version 4.5.0
  • Shaka player from v4.0.0 (2022-04-30)
  • Android’s Exoplayer from version r2.18.1
  • Bitmovin
  • Theo Player

Filtering, ordering, paging

See Filtering, ordering, paging of Media Services entities.

[!INCLUDE media-services-community]