Menu
Products
Products
Video Hosting
Upload and manage your videos in a centralized video library.
Image Hosting
Upload and manage all your images in a centralized library.
Galleries
Choose from 100+templates to showcase your media in style.
Video Messaging
Record, and send personalized video messages.
CincoTube
Create your own community video hub your team, students or fans.
Pages
Create dedicated webpages to share your videos and images.
Live
Create dedicated webpages to share your videos and images.
For Developers
Video API
Build a unique video experience.
DeepUploader
Collect and store user content from anywhere with our file uploader.
Solutions
Solutions
Enterprise
Supercharge your business with secure, internal communication.
Townhall
Webinars
Team Collaboration
Learning & Development
Creative Professionals
Get creative with a built in-suite of editing and marketing tools.
eCommerce
Boost sales with interactive video and easy-embedding.
Townhall
Webinars
Team Collaboration
Learning & Development
eLearning & Training
Host and share course materials in a centralized portal.
Sales & Marketing
Attract, engage and convert with interactive tools and analytics.
"Cincopa helped my Enterprise organization collaborate better through video."
Book a Demo
Resources
Resources
Blog
Learn about the latest industry trends, tips & tricks.
Help Centre
Get access to help articles FAQs, and all things Cincopa.
Partners
Check out our valued list of partners.
Product Updates
Stay up-to-date with our latest greatest features.
Ebooks, Guides & More
Customer Stories
Hear how we've helped businesses succeed.
Boost Campaign Performance Through Video
Discover how to boost your next campaign by using video.
Download Now
Pricing
Log in
Get a demo
Get Started
Microsoft PlayReady DRM on Windows and Xbox provides a structured way to protect digital video so it can be delivered and viewed without unauthorized access. It works as the security layer that guards content as it travels from services to devices. On both Windows and Xbox, it keeps playback stable by controlling how media is decrypted and used. This matters because streaming services, game publishers, and media apps need a reliable system that keeps content safe while still allowing smooth playback for users. Prerequisites To implement PlayReady DRM, you need both legal authorization and technical setup. Ensure you have: A Microsoft account and access to the Microsoft PlayReady Portal . A computer running Windows 10 or later for development and testing Basic knowledge of HTTP , REST APIs , and C# . Access to a web server or Azure cloud environment for hosting your PlayReady License Server. Visual Studio or another IDE for building your Windows or Xbox app Optionally, media packaging tools (such as Azure Media Services, Shaka Packager, or FFmpeg with CENC encryption support) Obtain a PlayReady License Using PlayReady requires obtaining a license agreement from Microsoft. This is not a simple key-based signup process—it's a formal licensing arrangement that grants permission to use PlayReady technology in your applications or services. Step 1 : Visit the PlayReady Licensing Portal . Step 2 : Complete the license request form with your organization's details and intended use case. Step 3 : After Microsoft reviews and approves your application, you'll gain access to the PlayReady Compliance and Robustness Rules, SDK documentation, and test tools. Step 4 : Choose the appropriate license type: Application Developer License for apps that use existing PlayReady client runtimes. Service Provider License for operating a custom PlayReady license server. Step 5 : Download the PlayReady Server SDK from the portal after approval. This agreement is required for production deployments. For initial learning or non-commercial testing, you can use the public PlayReady Test Server. Set Up Your License Server The license server is responsible for issuing licenses that grant playback rights to authorized devices. Instead of writing this logic manually, Microsoft provides the PlayReady Server SDK, which includes modules for license generation and policy enforcement. Step 1 : Install the PlayReady Server SDK provided by Microsoft. Step 2 : Deploy it to your preferred environment (on-premises or Azure-based Windows Server). Step 3 : Configure your IIS web server or ASP.NET Core service to handle HTTPS requests. Step 4 : Integrate your authentication and entitlement logic into the SDK’s sample server code. Common methods include user tokens, OAuth, or account validation. Step 5 : Set up a secure database to associate users and content entitlement data. Step 6 : Configure PlayReady policies (rental period, output restrictions, expiration time, etc.) through XML or API parameters. Step 7 : Test license issuance using the official PlayReady Test Client or a custom HTTP request. For development, you may use Microsoft’s PlayReady Test Server at: https://playready.microsoft.com/TestServer/ Generate PlayReady Certificates and Keys Certificates and keys in PlayReady authenticate your license server and encrypt communication with clients. Step 1 : For production servers, request server certificates directly through the PlayReady team during your licensing process. Step 2 : For staging or testing, use the PlayReady Test Certificates available in the SDK package. Step 3 : Install the certificate’s .pfx file on your web server and reference it in your PlayReady Server configuration. Step 4 : Set strong passwords for your private key files and limit file access to the server process. Step 5 : Configure your SDK application to use the certificate for: Signing license responses. Establishing SSL (HTTPS) connections. Encrypting content keys for device playback. Certificates are critical for preventing tampering and unauthorized license generation. Package Content with PlayReady Protection Before video playback can use PlayReady, content must be encrypted and packaged with the Common Encryption (CENC) standard supported by MP4, DASH, or HLS formats. Step 1 : Use a tool or service that supports PlayReady encryption, such as Azure Media Services, Shaka Packager, or FFmpeg (compiled with PlayReady CENC parameters). Step 2 : During packaging: Generate a content encryption key (CEK). Add PlayReady-specific metadata in the PSSH (Protection System Specific Header) field. Store the CEK securely on your license server. Step 3 : Verify that your output media includes PlayReady headers with the correct system ID (9a04f079-9840-4286-ab92-e65be0885f95). After packaging, your media content can be streamed through a compatible player or app that supports PlayReady decryption. Integrate PlayReady into Your App Apps on Windows and Xbox use built-in PlayReady components for DRM playback. On each platform, integration differs slightly. For Windows (UWP or WinUI apps): Step 1 : Open your project in Visual Studio. Step 2 : Use Windows.Media.Protection.PlayReady or Windows.Media.Playback namespaces. Step 3 : Create a MediaProtectionManager to handle DRM events. Step 4 : Configure a license acquisition URL linking to your PlayReady License Server. Step 5 : Implement a MediaPlayer or MediaElement to play encrypted content. Step 6 : Handle asynchronous errors like license rejection or expired policies. For Xbox (Game Development Kit): Step 1 : Use the Microsoft GDK PlayReady API integrated in the Xbox media framework. Step 2 : Define your DRM URLs and entitlement logic within the game’s media playback module. Step 3 : Follow GDK-specific content policies for HDCP and output protection. Step 4 : Test using partner-provided Xbox developer kits (XDK/GDK dev units). Test and Deploy Your Setup Testing ensures that your end-to-end DRM workflow performs correctly and resists unauthorized playback. Step 1 : Test playback using both PlayReady Test Certificates and production keys. Step 2 : Validate that: Licenses are granted only for authorized users. Expired or mismatched licenses block playback. Revoked certificates deny further license requests. Step 3 : Simulate interruptions (offline mode, network loss) to confirm proper recovery behavior. Step 4 : Use logs from your PlayReady Server SDK instance for debugging license responses. Step 5 : Submit your app for certification via the Microsoft Partner Center (for Windows Store or Xbox app distribution). Step 6 : Deploy your production license server on Azure or an equivalent secure hosting environment. Step 7 : Regularly rotate keys and certificates for long-term security.