Deploy Ravnur Media Services in under an hour. This guide walks you through setting up a fully functional RMS instance on Azure - complete with live streaming, on-demand video encoding, and API access for custom workflows. Whether you're building a media platform, scaling live event delivery, or testing encoding solutions with fine-tuned API control, this deployment provides immediate access to live streaming, VOD encoding, and streaming endpoint management through both UI and API.

Want to test RMS before committing? Start with the RMS Free Trial to get up and running in minutes.

Follow the setup guide for detailed guidance.

If you encounter any deployment failures or issues, you can submit a support ticket from the home page of this documentation site, or contact Ravnur Support at support@ravnur.com.

Before you begin

1. Register resource providers in the subscription. Estimate: 5 minutes.

This article describes the process for registering resource providers. It also has a CloudShell script that automates the resource provider registration, which can save you time. Your subscription must have the following resource providers registered for the deployment to succeed: 

Microsoft.Insights
Microsoft.KeyVault
Microsoft.AAD
Microsoft.CDN
Microsoft.Storage
Microsoft.ServiceBus
Microsoft.ManagedIdentity
Microsoft.Compute
Microsoft.OperationalInsights
Microsoft.Web
Microsoft.App
Microsoft.SQL
Microsoft.ContainerInstance
Microsoft.CognitiveServices
Microsoft.Insights
Microsoft.ContainerService
Microsoft.ContainerInstance
Microsoft.CognitiveServices
Microsoft.Insights
Microsoft.ContainerService
Microsoft.EventGrid
Microsoft.Network
Microsoft.AlertsManagement 

2. Verify availability of VMs and add VM core quota for the encoders. Estimate: 5 minutes.

The default VM for encoding uses F16s_v2 VMs that have 16 cores per VM. You need to have at least 160 cores in your quota for the Standard FSv2 Family in your selected deployment region for the deployment to succeed. Adding quota does not incur costs. The vCPU quota is needed to permit scaling. This article describes how to check the quota and increase it as needed. 

3. Verify availability of VMs and add core quota for the API and streaming servers.

Estimate: 5 minutes.

The AKS node pools for the API and streaming servers use the D2as_v5 VMs with two cores each. Ensure that the Standard D2as_v5 family quota for the region where RMS is running has at least 20 cores. Adding quota does not incur costs. The vCPU quota is needed to permit scaling. This article describes how to check the quota and increase it as needed. 

If you are deploying RMS to a subscription that already has an RMS instance (for example, a non-production instance), consider the total vCPU quota required by all RMS instances in the subscription and region. See this article for more details.

4. Region selection considerations. Estimate: 1 minute.

Not recommended due to potential deployment issues:

• US East 
• West Europe 

Contact Ravnur if you encounter problems after selecting this region.

Do not deploy:

• East Asia - contact Ravnur for manual implementation from another region.

Deployment Instructions

Deploying RMS to your Azure tenant takes approximately one hour.

These instructions describe the process of deploying using a Private Plan that Ravnur created for you or the Public Standard Subscription offer.

After the deployment is complete, you can retrieve the API access credentials for your application and begin using the RMS API (step 8).

Step 1 – Create Resource Group (1 minute)

Step 2 – Find Ravnur Media Services in the Azure Marketplace (1 minute)

Step 3 – Select the Ravnur Media Services Plan (1 minute)

Step 4 – Configure the Deployment (2 minutes)

Step 5 – Accept the Terms and Conditions (1 minute)

Step 6 - Deploy the Application (45 minutes)

Step 7 – Link the deployment in RMS Console (2 minutes)

Step 8 – Copy the API Credentials (2 minutes)

Step 1 – Create Resource Group

Create a resource group in the subscription where you will deploy the managed application package. Please avoid West Europe, the US East, and East Asia, as there is a high likelihood the deployment will fail in these regions. Choose any other option.

Step 2 – Find Ravnur Media Services in the Azure Marketplace

Go to your newly created resource group and click on + Create as indicated in the image below.

This will open the Azure Marketplace. You'll find RMS available in two ways:

• Option 1: Public Offer (production deployment). Search for "Ravnur Media Services - the AMS Replacement for Live and On-Demand Video".

• Option 2: Private Plan. If Ravnur has created a specific private plan for you, click "View private plans" or navigate to "Private Plans" under "My Marketplace" in the left sidebar menu.

A free trial option is also available directly in the Azure Marketplace. For a quicker trial experience, use the RMS Console Free Trial option (recommended).

Step 3 – Select the Ravnur Media Services Plan

Clicking on the tile for Ravnur Media Services opens the private plan page. Click on Create to begin the deployment.

Step 4 – Configure the Deployment

There are a few configuration entries that must be reviewed and updated as necessary.

1. Subscription. Ensure the correct subscription for the resource group is selected.

2. Resource group. The available resource groups will depend on the subscription you selected above.

3. Region. Choose the Azure region that's right for you and your customers. Not every resource is available in every region.

4. Failover (Optional). SQL failover is a good idea for production deployments - check the box.

5. System pool

System pool VM size. The preferred VM is the Standard D2as_v5. Ensure that the Standard DASv5 Family has sufficient vCPU quota in the resource group's region as described above in Before you begin.

6. Encoding pool

Encoding pool VM size. This defaults to Standard F16s_v2. Ensure that the Standard FSv2 Family has sufficient vCPU quota in the resource group's region as described above in Before you begin.

7. Application name. Enter a name for the application, e. g. mycompanymediaservices.

8. Managed resource group. The managed resource group name is automatically created for you. You can change it, but that's not necessary.

9. Click on Review + create.

Step 5 – Accept the Terms and Conditions

Select the checkbox to accept the terms and conditions for the offer. The Terms and Conditions and Privacy Policy can be accessed on this page by clicking on the Terms of Use and Privacy Policy links located below the Price section.

Click on Create to start the deployment.

Step 6 - Deploy the Application

After clicking on Create, the deployment will begin. This process can take up to 45 minutes.

Need help? Contact support@ravnur.com if any errors appear.

Step 7 – Link the deployment in RMS Console

After deployment is completed, locate the values of your application (open the details as shown above):

• Subscription ID - click the Subscription link and copy the Subscription ID
• Managed Resource Group Name - copy from the Azure page once deployment is complete

1. Once deployment is complete, navigate to apps.ravnur.com to access your RMS Console.

2. Authenticate via MFA (Multi-Factor Authentication) to access the RMS Console.

3. Accept required permissions.

4. You'll land on the RMS Welcome page. Select Link RMS instance from the available options.

5. In the pop-up dialog, enter:

• Subscription ID: Enter the Azure subscription ID used for the deployment.
• Managed Resource Group Name: Enter the managed resource group name used for the deployment.

• Tenant ID (optional): if your account doesn't belong to the subscription ID you're using, you may need to provide a tenant ID. 

6. Click Link to establish the connection between your Azure deployment and RMS Console.

The initiator of the RMS connection to the RMS Console is automatically assigned the Owner role for administrative control. See learn more.

If you need to resume the linking process later (for example, if you didn't complete it immediately after deployment), you can find your managed RMS application in Azure Portal > Managed applications and continue the setup. Otherwise, you'll land here right after the completed deployment:

Your RMS deployment is now linked and ready to use.

Step 8 – Copy the API Credentials

To configure API access, you'll need to set the environment variables.

Access RMS Console > Api Key Management tab:

Find the following configuration values:

{
"AZURE_SUBSCRIPTION_ID": "<RMS account subscription ID>",
"AZURE_RESOURCE_GROUP": "<RMS account resource group name>",
"RAVNUR_MEDIA_SERVICES_ACCOUNT_NAME": "<RMS account name>",
"RAVNUR_API_ENDPOINT": "<RMS instance API endpoint>",
"RAVNUR_API_KEY": "<API KEY>"
}

Variable descriptions:

• AZURE_SUBSCRIPTION_ID: The Azure subscription ID where RMS is deployed.
• AZURE_RESOURCE_GROUP: The name of the managed resource group for your RMS account.
• RAVNUR_MEDIA_SERVICES_ACCOUNT_NAME: The name of your RMS account.
• RAVNUR_API_ENDPOINT: The fully qualified domain name (FQDN) of the API URL.
• RAVNUR_API_KEY: Required for authentication - use your actual API key value for this placeholder, learn more.

You are now ready to update your SDK to connect to RMS.

Alternatively, manage RMS directly using the RMS Console.