The Streaming origin endpoint is a core component of RMS streaming infrastructure that works in conjunction with Content Delivery Networks (CDNs) to deliver your streaming content. Before setting up your streaming endpoints, learn how RMS handles content delivery through CDNs: see CDN and custom domains in RMS.

When you stream content through RMS, the streaming origin endpoint acts as the primary source for your media, which CDNs then cache and distribute to viewers. This guide explains how to locate and configure your streaming origin endpoint, and outlines best practices for content delivery.

In this article:

Streaming origin in RMS

Security and performance

Integrate custom CDN with RMS streaming endpoint

Streaming origin in RMS

The streaming origin endpoint is a streaming server load balancer.

The streaming origin domain follows this format: i-rms.{RMS DNS zone}, where {RMS DNS zone} is your unique DNS identifier visible in the streaming endpoints settings.

Alternatively, find your RMS DNS zone in the Azure portal:

1. Navigate to your RMS resource group
2. In the resource list, use the Type filter and select DNS zone.
3. The DNS zone resource name is your RMS DNS zone.

RMS resource group typically contains a single DNS zone resource.

Security and performance

The streaming origin endpoint is public, however, direct usage is not recommended. This method uses the public internet for transport, which causes latency and security issues. Instead, use the Front Door Endpoint or a CDN endpoint mapped to the RMS streaming origin.

Endpoint privacy options

• If you use Azure Front Door or Azure Standard CDN (classic), Ravnur can configure the private endpoint and make it not accessible publicly.
• If you use another CDN provider, the endpoint cannot be private. Our team is actively working on a solution to support private endpoints before the Azure Standard CDN end-of-life on September 30, 2027.

CDN integration steps

• Map your CDN to the streaming origin endpoint.
• Do not map it to the RMS Front Door Endpoint. According to Microsoft's documentation, this is considered a bad practice.
• Use the Ignore Query String option for efficient caching.

  • To understand the impact, consider the following example URLs:

    https://domain/path/master.m3u8?token=token1

When Ignore Query String is enabled, the CDN will ignore anything after the "?" when caching content. This means the same cached response will be served regardless of parameters liketoken=token1 or token=token2, learn more.

• No other configurations are required.
• Update the streaming endpoint host name in the RMS Console.