World is now on Opti ID! Learn more

Pontus Hagman
Oct 18, 2016
  2863
(0 votes)

How to setup license for Episerver hosted in Azure

This article describes how to setup and activate the license for Episerver running on a Microsoft Azure web app.

 

Episerver Cloud license

Episerver running in an Azure web app will require a cloud license. The cloud license works differently than an ordinary license as it is not bound to MAC or IP. Instead the site “calls home” upon activation to register the server. (The server concept in this case is synonymous with a web app instance). As before, the license limits the number of sites and servers (instances) that can be run under that license.

 

Setup and activation

Let’s assume you have Episerver running in two environments, test and production. The same license file (license.config) should be used and deployed to both environments.

To avoid license error it’s important that you enter the same URL in both the test and production environment. The URL is found in Admin mode > Config > Manage websites > Web sites. (See screen dump below).

Cloud license

 

Now it´s time to activate the license. Navigate to admin mode > Config > Manage websites > Cloud license. Activate the license in both test and production with the activate button. (See screen dump below). The servers (azure instances) are counted towards the total number, limited by the license.

Cloud license activate

You should not activate the other host names, only the one listed that is the same as the main URL.

Since the cloud license is a floating license, you can deactivate instances and activate others as you see fit, as long as you do not exceed the total number of instances allowed by your license. For an example, if you have 3 instances for your production environment, 2 for pre-production and one for test, you can deactivate all non-production instances and use 6 instances in production in case you need to handle an increased amount of traffic for a period.

Oct 18, 2016

Comments

Please login to comment.
Latest blogs
Make Global Assets Site- and Language-Aware at Indexing Time

I had a support case the other day with a question around search on global assets on a multisite. This is the result of that investigation. This co...

dada | Jun 26, 2025

The remote server returned an error: (400) Bad Request – when configuring Azure Storage for an older Optimizely CMS site

How to fix a strange issue that occurred when I moved editor-uploaded files for some old Optimizely CMS 11 solutions to Azure Storage.

Tomas Hensrud Gulla | Jun 26, 2025 |

Enable Opal AI for your Optimizely products

Learn how to enable Opal AI, and meet your infinite workforce.

Tomas Hensrud Gulla | Jun 25, 2025 |

Deploying to Optimizely Frontend Hosting: A Practical Guide

Optimizely Frontend Hosting is a cloud-based solution for deploying headless frontend applications - currently supporting only Next.js projects. It...

Szymon Uryga | Jun 25, 2025

World on Opti ID

We're excited to announce that world.optimizely.com is now integrated with Opti ID! What does this mean for you? New Users:  You can now log in wit...

Patrick Lam | Jun 22, 2025

Avoid Scandinavian Letters in File Names in Optimizely CMS

Discover how Scandinavian letters in file names can break media in Optimizely CMS—and learn a simple code fix to automatically sanitize uploads for...

Henning Sjørbotten | Jun 19, 2025 |