Skip to content

Commit 0c4a1be

Browse files
authored
Update content-protection-overview.md
1 parent f09b553 commit 0c4a1be

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

articles/media-services/latest/content-protection-overview.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -53,12 +53,11 @@ To successfully complete your "content protection" system/application design, yo
5353
2. Create a [Streaming Locator](https://docs.microsoft.com/rest/api/media/streaminglocators) that is configured to stream the encrypted asset.
5454
5555
The **Streaming Locator** has to be associated with a [Streaming Policy](https://docs.microsoft.com/rest/api/media/streamingpolicies). In the example, we set
56-
StreamingLocator.StreamingPolicyName to the "Predefined_MultiDrmCencStreaming" policy. This policy indicates that we want
57-
for two content keys (envelope and CENC) to get generated and set on the locator. Thus, the envelope, PlayReady, and
56+
StreamingLocator.StreamingPolicyName to the "Predefined_MultiDrmCencStreaming" policy. The PlayReady and
5857
Widevine encryptions are applied (the key is delivered to the playback client based on the configured DRM licenses). If
5958
you also want to encrypt your stream with CBCS (FairPlay), use "Predefined_MultiDrmStreaming".
6059
61-
Since we want to encrypt the video, the **Content Key Policy** that we configured earlier also has to be associated with the **Streaming Locator**.
60+
You need to create a **Content Key Policy** to configure how the content key (that provides secure access to your Assets) is delivered to end clients.
6261
6362
3. Create a test token.
6463

0 commit comments

Comments
 (0)