Enable assets for streaming

Once you have assets in MK.IO — whether imported from Azure Media Services, uploaded from your device, or created directly — you need two components before viewers can play them:

• A Streaming Endpoint — the origin server that serves content to players and CDNs
• A Streaming Locator — attached to each asset, it generates playback URLs and controls access

For full step-by-step instructions including configuration options, streaming policies, and DRM, see Publish content for streaming.

Quick steps

Create and start a streaming endpoint

Go to Streaming Endpoints and click + Create Streaming Endpoint. Give it a name, choose Shared for testing or Dedicated for production, and start it.

Running streaming endpoints incur costs even when idle. Stop endpoints you are not actively using.

Create a streaming locator on your asset

Open the asset, scroll to Streaming Locators, and click + Add Streaming Locator. Give it a unique name and select Predefined_ClearStreamingOnly for basic unprotected streaming.

Apply and get playback URLs

Select your running endpoint and the locator from the dropdowns on the asset page, then click Apply. MK.IO generates HLS and DASH playback URLs immediately.

Test playback

Use the built-in MKPlayer on the asset page to verify the stream plays correctly before distributing the URLs.

Migrating from Azure Media Services

If you are enabling playback for assets imported from AMS:

• Your existing content does not need to be re-encoded — MK.IO streams files directly from your connected Azure storage.
• Streaming locator names from AMS are not automatically carried over. Create new locators with your preferred names in MK.IO.
• If you previously used AMS streaming endpoints, note that MK.IO endpoint names form part of the playback URL — choose names that reflect your production setup.

For large-scale AMS migrations, see Bulk asset migration from AMS storage.