The Sustainability Dashboard is designed to help users monitor and improve the environmental impact of their websites on Umbraco Cloud. The dashboard provides insights and metrics related to carbon footprint and sustainable practices, enabling organizations to align their digital presence with their sustainability goals.

Key Features

• Daily CO2 emission calculation: The dashboard is updated daily with new CO2 emission estimates.

• Historical data: The dashboard tracks monthly and yearly CO2 emission estimates, allowing for trend analysis over time

• Comparative analysis: Users can compare CO2 emissions across their projects to identify high-impact areas and improvement opportunities.

CO2 emission calculation methodology

To estimate CO2 emissions from the infrastructure deployed to host Umbraco Cloud websites, we use Cloud Carbon Footprint (CCF). followed by dividing CO2 emissions among websites according to their shared resource usage.

In order to improve the estimate for websites that are running in shared pools we divide emissions based on metrics/usage coefficients.

In its current iteration the sustainability dashboard shows CO2 emissions emitted by backend compute infrastructure - Azure App Service. The dashboard does not show emissions generated by networking, frontend website impressions or emissions generated by the Umbraco Cloud Service.

The summarized algorithm currently in use is:

Project CO2 emissions = Sum of environment CO2 emissions
Environment CO2 emissions = Total CO2 emissions of backend compute infrastructure * Usage coefficient of the environemnts compute resources

Cloud Carbon Footprint

Cloud Carbon Footprint(CCF) provides a comprehensive methodology for estimating CO2 emissions in their documentation. We use CCF to calculate the Sum of environmental CO2 emissions.

CCF CO2 emissions = Operational emissions + Embodied emissions

Operational emissions = (Cloud provider service usage) x (Cloud energy conversion factors [kWh]) x (Cloud provider Power Usage Effectiveness (PUE)) x (grid emissions factors [metric tons CO2e])
Embodied emissions = Estimated metric tons CO2 emissions from the manufacturing of the datacenter

Umbraco Cloud Usage

For websites on shared infrastructure in Umbraco Cloud, we calculate a usage coefficient to improve the accuracy of CO2 emission estimates. This coefficient divides the CO2 emissions of the shared pool among the websites using it.

The usage coefficient for a website is based on metrics such as:

• CPU

• Memory usage

The usage coefficient for a database is based on DTUs used etc.

Website CO2 emissions = Usage coefficient * CCF CO2 emissions
Usage coefficient =  Website resource usage / Total pool usage

Website Resource Usage: For compute resources we evaluate metrics such as CPU, memory or disk, for storage resources DTUs and disk are considered. Total Pool Usage: The total resource usage of the shared pool of resources.

Getting Started

Accessing the Dashboard

1. Log in to Umbraco Cloud: Use your credentials to log in to your Umbraco Cloud account.

2. Navigate to the Organization view

3. Navigate to the Dashboard: From the left menu, select Sustainability.

Decreasing Carbon Emission Impact

• Monitor Regularly: Regularly check the Sustainability Dashboard to stay informed about your website's carbon footprint.

• Implement Recommendations: Follow up to date sustainability best practices.

• Optimize Resource Usage: Analyze websites resource usage and identify high-consumption areas to optimize resource usage

In this article you can find information about security on Umbraco Cloud.

HTTPS & Certificates

All Umbraco Cloud websites use HTTPS by default. Both the default {projectName}.{region}.umbraco.io and custom domains are protected by periodically renewed certificates issued by Cloudflare. This service is offered as part of Umbraco Cloud for all plans.

Custom Certificates

Custom certificates can be used with all custom domains. Please refer to our Managing Custom Certificates documentation.

TLS support

As of April 2020, we've deprecated support for TLS 1.0 & TLS 1.1.

TLS 1.2 is now the default supported TLS protocol going forward.

On the Security page for your cloud project, you can change the default settings for both TLS and HTTP.

Learn more about how this in the Manage Security article.

TLS Ciphers support

Umbraco Cloud Websites support the following TLS ciphers in this order:

• TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384

• TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256

• TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA

• TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA

• TLS_DHE_RSA_WITH_AES_256_GCM_SHA384

• TLS_DHE_RSA_WITH_AES_128_GCM_SHA256

• TLS_DHE_RSA_WITH_AES_256_CBC_SHA

• TLS_DHE_RSA_WITH_AES_128_CBC_SHA

The different Ciphers can be enabled or disabled on the security project settings page for your Cloud projects.

HSTS - HTTP Strict Transport Security

It's possible to enforce HSTS: HTTP Strict Transport Security by adding the headers to your website. This grants Umbraco Cloud Websites an A+ security rating on sslabs (March 2020).

You can add the header by modifying system.webServer/rewrite/outboundRules section in your web.config:

 <outboundRules>
  <rule name="Add Strict-Transport-Security when HTTPS" enabled="true">
  <match serverVariable="RESPONSE_Strict_Transport_Security" pattern=".*" />
  <conditions>
   <add input="{HTTPS}" pattern="on" ignoreCase="true" />
   <add input="{HTTP_HOST}" pattern="localhost" negate="true" />
  </conditions>
  <action type="Rewrite" value="max-age=63072000; includeSubDomains; preload" />
  </rule>
 </outboundRules>

Alternatively this can be done in Startup.cs inside of the ConfigureServices method with the following C#:

public void ConfigureServices(IServiceCollection services)
        {
            services.AddUmbraco(_env, _config)
                .AddBackOffice()
                .AddWebsite()
                .AddComposers()
                .Build();

            services.AddHsts(options =>
            {
                options.MaxAge = TimeSpan.FromDays(730);
                options.IncludeSubDomains = true;
                options.Preload = true;
            });
        }

This adds the "Strict-Transport-Security" header telling browsers how long the browser should not make any HTTP requests to this domain. In this example 63072000 seconds or 730 days is two years.

TLS 1.2 by default in external services

In order to integrate older external applications to access Umbraco Cloud Websites you might have to modify the TLS support in the .Net application.

For ASP.NET applications, inspect the <system.web><httpRuntime targetFramework> element of web.config to find the version of the .NET Framework your application is using. .NET applications on .NET 4.7+ are using the OS specified TLS protocols. In Windows 8 & 10, Windows Server 2012 & 2016 TLS 1.2+ is used by default, therefore no actions necessary. .NET applications lower then 4.7 require updates to ensure they can communicate using TLS 1.2 by default.

More information specifically from Microsoft about .Net applications and Transport Layer Security (TLS) support can be found in Microsoft's official docs. For other application frameworks/languages we encourage to lookup their respective documentations.

HTTP

Naked HTTP urls without HTTPS are supported but not used by default on Umbraco Cloud Websites. If you'd like to keep using HTTP, which we strongly discourage, you'll need to remove a web.config transform as specified in Rewrite rules on Umbraco Cloud

Umbraco Cloud supports both HTTP2 and HTTP3 protocols.

Ports

By default, all ports are closed to secure them against external attacks. This is done for all ports apart from 80 (HTTP) and 443 (HTTPS).

Firewall & Restricting public access to Umbraco Cloud resources

Umbraco Cloud offers a multitude of features allowing you to block access to different resources.

• Basic Authentication allows access to the Backoffice & Frontend of Umbraco Cloud Websites for authenticated users only.

• IP based list allowing access to Frontend & Backoffice

• IP based list allowing access to website database

Cookies and security

On Umbraco Cloud sites, you will find an ARRAffinity cookie. This is not sent over HTTPS, and might to some, look like a security risk.

It is not a security risk. This cookie is set by the load balancer (LB) and only used by the LB to track which server your site is on. It is set by the software we use (Azure App Service) and only useful when your website is being scaled to multiple servers. In Umbraco Cloud we cannot scale your site to multiple servers so the cookie is effectively unused.

There is no vulnerable data in this cookie and manipulating or stealing this cookie can not lead to any security issues.

In the future, the cookie will be set to HttpOnly on Umbraco Cloud to conform to best practices. This does not mean that there's anything wrong with the current way it is set.

For more information see the related GitHub issue.

Deny specific IPs from accessing your website

You can block people and bots(e.g. a malicious scanning bot) from accessing your website by adding their IP addresses to a deny-list.

The following rule can be added to your web.config file in the system.webServer/rewrite/rules/ section.

<rule name="RequestBlockByIP" patternSyntax="Wildcard" stopProcessing="true">
    <match url="*"/>
    <conditions>
    <add input="{HTTP_CF_Connecting_IP}" negate="false" pattern="123.123.123.123"/>
    </conditions>
    <action type="AbortRequest"/>
</rule>

For anyone using the 123.123.123.123 IP, this will result in them getting a 502 error. You can choose your own error.

Umbraco Cloud is our hosting option for your favorite Umbraco CMS. Built on the Microsoft Azure Cloud and encompassing web standard approaches, Umbraco Cloud is familiar to Umbraco's new and old users. With Umbraco Cloud, there are no limits to what you can accomplish. Anything you can do with Umbraco and web technology you can do with Umbraco Cloud.

Umbraco Cloud Plans

Umbraco Cloud offers shared hosting in 3 different plans:

• Starter

• Standard

• Professional

You can learn more about quotas that are put in place to ensure the stability of your website.

Umbraco Cloud Project

The easiest way to get started with an Umbraco Cloud project is to take a 14-day free trial. The project is automatically created and you are ready to get started within a few minutes.

Since we set up the entire project, we recommend that you get to know your project before you start building.

To start working with and building your site, you can either work directly in the backoffice on the Cloud environment or you can clone down the project to your local machine.

Umbraco Cloud Portal Project

To create a project in Umbraco Cloud Portal:

1. Log in to the Umbraco Cloud Portal with your credentials.

2. Click Create Project.
3. Select Umbraco Cloud from the list of projects.

4. Choose a Plan Selection as per your choice.

5. Choose the Umbraco version for your Project.

6. Enter the Project Name.

7. Choose a Region.

8. Choose a Project Owner.

9. Add a Technical Contact to your project.

10. Click Continue.

11. Verify that everything looks correct.

12. Check I have read and agree to the terms and conditions and the Data Processing Agreement.

13. Click Create Project.

Naming a Project

When you create a:

• Trial project for the first time - a unique project name will be generated for you.

• Project from the Umbraco Cloud Portal - you will get to choose a name for the project.

To rename the project file and folder, see the Renaming the Project file and folder article.

An Umbraco Cloud project name is unique, which means if a project with the name you choose already exists, you will need to choose another name before you can create the project.

Project Overview

Once a project is created, you can view its overview in Umbraco Cloud Portal:

1. Log in to the Umbraco Cloud Portal with your credentials.

2. Select your Project from the Projects dashboard.

3. Click on Overview from the left side menu..

The Overview menu consists of:

Environments:

From the environment overview, you can see the environments you have for your project.

You can access your project's frontend, the backoffice, access kudu, or clone it to your local machine.

You can also add new environments from here.

Team:

From the Team Overview, you can see the following:

• Who is a part of your project

• What kind of access do they have on the project

• Umbraco Backoffice User Groups

• Add or remove users from the project

• Pending invites

• View and add technical contacts

Summary:

The summary page consists of the following:

• Name - The name of the project.

• Alias - The alias of the project.

• Plan - The plan selected for the project. Available plans are Starter, Standard, or Professional.

• Region - The region the project is hosted in.

• Payment status - The payment status of the project.

• Created by - The name and email of the project creator.

• Creation date - The date the project was created.

Umbraco Cloud takes care of installation, infrastructure, and security. You will also get the tools to work with your project in the Cloud or locally. Local development starts with cloning the project down to your PC or Linux/macOS.

When you are ready to show your work to the world, Umbraco Cloud provides a safe deployment mechanism that lets you publish to the web. When you have changes or updates to your site, Umbraco Cloud follows the process of moving, testing, and deploying your changes to your public site.

Different ways to start an Umbraco Cloud project

Umbraco Training

Umbraco HQ offers a full-day training course covering best practices for developing with Umbraco Cloud. The course targets frontend and backend developers who currently work or plan to work with Umbraco Cloud.

Explore the Umbraco Cloud Developer Training Course to learn more about the topics covered and how it can enhance your Umbraco development skills.

On Umbraco Cloud it is possible to setup an Organization. An organization is handy if you are managing many projects for different customers. It is also handy if you need to manage permissions for multiple users (such as developers, content editors etc.).

With an organization, you get an overview of all projects and members that are part of it. You can also manage payment methods for projects, as well as many other functions outlined on this page.

In the following sections, we will go through the different options that are available to an Organization:

Information

In the Information section of the Organization, you can find all the details about your Organization. If there are any changes to your details, you can change them here.

Members

In the Members section, you can view current members, pending invites, and see the Multi-Factor Authentication (MFA) status for the Members of your Organization. You can also set up different permissions for your Members, such as Read, Write, and Administrators for your organization by adjusting their Roles.

Members added to your organization can see different details about their organization based on the user group they are added to. Currently there are three different groups, Read, Write and Admin. Below you can see what each user group has access to under the organization they are a part of.

Organization Members with Admin Access can do the following in the organization:

• Update the organization's information

• Invite others to the organization

• Invite Users to project under the organization

• Edit organization team

• See pending invitations

• See organization information

• See organization projects

• See payment history

• See subscriptions

• See organization Members

• See payment history

• Handle Multi-Factor Authentication (MFA) for users

• Handle payment methods

• Change permissions for Members

• Remove role from users

Organization members with Write Access can do the following in the organization:

• See Organization information

• See Organization Members

• Invite to the organization

• See pending invitations

Organization Members with Read Access can do the following in the organization:

• See Organization information

• See Organization Members

Multi-Factor Authentication (MFA) enforcement

When working in organizations on Umbraco Cloud, as a company, you can enforce a certain type of Multi-Factor Authentication (MFA) method for members.

Administrators of Organizations on Umbraco Cloud can enforce MFA for specific members of their organization.

To enforce a certain MFA for a member, follow these steps:

1. Go to the Organizations tab under your user on Umbraco Cloud.

2. Go to the Members tab under Organization.

3. Go to Multi-Factor Authentication.

4. Find the member that needs to have MFA enabled.

5. Click on the cogwheel and select the Enforced MFA Method from the drop-down list for the member.

Once it has been enabled, the next time the member logs in, they will be forced to setup the chosen Multi-Factor Authentication (MFA) method. It is possible for an administrator to reset the authenticator app settings for members of the organization.

Projects

In the Projects section, you can get an overview of all the Projects that have been created in your Organization.

It is possible to see the plan, project status, payment status, creation date, region, and number of environments for each of your projects.

As an administrator, you can invite members of your organization to the different projects under the organization.

Access Rights

In the Access Rights section, you can get a list of all the Access Rights your Members have to each Project in your Organization.

Payment methods

In the Payment Methods section, you can view the payment methods for your organization. From here, you can add or delete credit card details for your Organization. These payment options will be used, when you create new projects under your organization.

Payment History

In the Payment History section, you can see the payment history for your organization.

Subscriptions

In the Subscriptions section, you can see the current active subscriptions that are running under the Umbraco Cloud organization.

The Umbraco Cloud Portal helps you manage your Umbraco Cloud project. From here, you can view and manage all your Cloud projects in one place.

Umbraco Cloud Portal Overview

When you log in to the Umbraco Cloud Portal, the projects dashboard gives an overview of all your Umbraco Cloud projects. Here, you can view all the projects you've created or have been added to as a team member.

You can see the project's environments, usage for each project, and which plans it is on. You can also see whether it is a baseline or baseline-child project.

In the top-right corner of the Umbraco Cloud Portal, you will find:

• Create New Project - Allows you to create more projects using the plan you wish and a project will be ready for you within a few minutes.

• Notifications - You can also see notifications for your different projects. For example: if your project has been automatically updated or if an upgrade has failed.

• Profile - Manage projects, subscriptions, pending invites, organization information, profile details, view release notes, and log out of the portal.

Project Groups

Settings

In the right-side corner of the Umbraco Cloud Portal, you can enable Show environments and Show usage of the project from the Settings option.

Collapse Groups

Collapse Groups allows you to collapse the groups on the project Dashboard. You can also expand the groups depending on the view you prefer.

Edit Groups

To get a better overview of your projects, it is possible to sort your projects into Groups. This can be done by clicking the Edit Groups button on the top right side of the Umbraco Cloud Portal.

After clicking on Edit Groups, you can create new Groups to sort your project in and create a better overview for yourself.

Click Add Group to give the group a name and then drag and drop your projects into the group of your choice.

Chat Feature

In the bottom-right corner of the Umbraco Cloud Portal, you'll find a chat bubble. This is where you can reach out to the Umbraco HQ Support Warriors, should you have any questions regarding your Umbraco Cloud projects.

With the Starter and Standard plan, you are only entitled to support regarding specific issues regarding the Cloud platform. If you are on a Professional plan, you are entitled to support through the chat regarding implementation and issues with the CMS. For more information on plans and pricing, see Umbraco Cloud plans.

Profile Options

When you click on the User Profile link, you will find the following options:

• Projects

• Manage Subscriptions

• Pending Invites

• Organizations

• Profile

• Release Notes

• Logout

Project Management

Managing your projects has been made even simpler with Umbraco Cloud. If you go to a particular project, you can get a quick overview of the environments in your project.

• Project Name along with the options to Create environments, Invite User, or Settings section.

• Environment name along with the option to Restart the environment, view Error Logs and Logs, Clone project, and access Power Tools (Kudu).

• Links to View errors, View page (frontend), Go to backoffice, and the Environment history.

• Option to view change details.

While managing the environments on your project, click on Create Environments to add and/or remove environments as needed. Read more about how the number of environments varies depending on the plan you are on, in the Project Overview article.

Aside from these features, it's also from the project view that changes are deployed from one Cloud environment to another. Find out more in the Cloud-to-Cloud article.

In the Settings section, you will find a lot more options to configure your project.

Pending Invites

On Umbraco Cloud, you can receive an invitation from different projects. These project details are available in the Pending Invites tab. On the Pending Invites page, as a user, you will see the following details:

• Project Name

• Invited by

• The expiration date of the invite

• Invitation status

• Options to approve, reject, or delete the invitations that have expired.

Organizations

On Umbraco Cloud, it is possible to get an organization to manage your company's projects. The Organization Projects page displays an overview of all the projects created by you and members of your company. Find out more in the Organization article.

The organization page contains sections displaying information about:

• Members

• Projects

• Access Rights

• Payment Methods

• Sustainability

• Payment History

• Subscriptions

Profile

The Profile consists of the following information:

• Name: The name that is displayed on Umbraco Cloud.

• Email: This email address is used for logging in to Umbraco Cloud and will receive email notifications from the Umbraco Cloud Portal.

  It is not possible to change this email address at a later point.

* Telephone: The contact number of the user. * Edit profile: Allows you to update and ensure that your information is valid and up to date for your Umbraco Cloud profile. * Change Password: Change the password for your Umbraco Cloud account from here.

Release Notes

On the Umbraco Cloud portal, you can now find the link to the Release Notes in the Profile dropdown. Release notes are published every month and list the most relevant fixes and features added to the portal.

Environment error log

Each environment has an error log that appears only if you have any unread errors in that specific environment. You can view the errors by clicking on View errors in the environment menu.

Once you're there, you can manually mark each error as read which will move it from the "New" section to the "Read" section. Errors marked as read will be permanently deleted after 30 days.

During development, you can happen to gather a large number of errors which might cause the error page to load slowly. A fix for that would be to locally connect to the database for that specific environment and delete the errors. You can read more about connecting to the environment database locally in the section about Database on Umbraco Cloud.

Environment errors are stored in the UCErrorLog table.

The query below will delete 90% of the errors. The query will always delete the oldest errors first. You can tweak the query to delete any percentage of errors by changing the number in the first row.

DELETE TOP(90) PERCENT
  FROM [dbo].[UCErrorLog]
  WHERE [Read] = 0

What is an environment?

An environment on an Umbraco Cloud project can be defined as a workspace and is at the same time a Git repository. When you have more than one environment on your project, these environments will act as branches of the main repository.

Umbraco Cloud uses a deployment model that relies on Git and other core technology, which gives you the option to move both content and structure files from one environment to another. Learn more in the .

When you have multiple environments in your Umbraco Cloud project:

• The Development environment is the first environment in the workflow.

  This is the environment you are going to work with when building the structure of your website. This is also the environment you clone down when you want to work on your project locally.

  The Development environment is included in the Standard and Professional plans on Umbraco Cloud. In the Starter plan, you have the option to add the Development environment.

• The environment next in line in the workflow is the Staging environment.

  This environment enables you to give your team members different workspaces - the developers can work with code in the Development environment while content editors can work with content in the Staging environment. All of this without affecting the actual public site.

  The Staging environment is included in the Professional plan. In the Standard plan, you have the option to add the Staging environment.

• The final environment is the Live environment.

  This is your live site - the site that's visible to the public. When you are in trial mode the Live environment will be protected by basic authentication - this will be removed as soon as you set up a subscription for the project.

  The Live environment is included in the Standard and Professional plans on Umbraco Cloud.

For more information about the workflow on Umbraco Cloud, see the article. Below you will find a technical overview of the different parts that make up an environment on your Umbraco Cloud project:

Site and Git Repository

Each environment on Umbraco Cloud has both a Git repository and a folder with your actual live site. The Git repository is what you clone down when you work with the project locally, and it's where your changes are pushed to.

The live site (/site/wwwroot/) contains the files used to show your website to the world. When you push changes from your local machine, they are pushed to the Git repository (/site/repository/), and when this finishes successfully the changes are copied into the live site.

Team Members/Invite Users

All the team members you add through the Umbraco Cloud Portal will also be added as backoffice users in your environments. As with any other Umbraco CMS installation, you can also add users directly in the backoffice of your Umbraco Cloud environments. If you do this, the user will not have the option to deploy changes between the environments.

SQL Database

Each of your Umbraco Cloud environments has its own SQL Azure database. You have full access to the databases, and you can create custom tables as you'd expect from any other hosting provider.

Power Tools (Kudu)

Aside from viewing the files on your Umbraco Cloud environments when cloning down the project to your local machine, you also have access to what we call Power Tools - Kudu.

This is a dashboard that allows you to browse, view, and edit all the files in your Umbraco Cloud environment. We recommend using the tool only when you are following one of our guides in the Troubleshooting section.

Environment History

Each of your Umbraco Cloud environments has a Git repository and therefore also a Git history. We've made a simplified view of this Git history in the Umbraco Cloud Portal - the Environment History.

In this view, you'll be able to see what file changes have been made in each environment.

Here we outline how to manually resolve a merge conflict after having updated the children for a Baseline project.

On a Baseline project you can click to “Manage updates here”, which enables you to push updates to your child projects from the Live environment of the Baseline project.

Select the child projects you want to upgrade, and click Update selected children. The overview will then change to show the progress and status for updating the various child projects.

The outcome of the update will result in one of three statuses:

• Updated has completed

• Error while updating from upstream

• Encountered a merge conflict so abandoning update

A merge conflict is something you currently need to handle manually in order to push future updates to the child project, which encountered a merge conflict upon updating.

Resolving merge conflicts

Note: Since the following documentation was outlined we've made quite a few improvements to the Baseline workflow. For the most part this documentation is still relevant and we are working on getting them updated with the latest details.

In order to resolve the conflict you need to go to the child site open up the SCM / Kudu site for the development environment. Click the “[link]” (see screenshot above) for the project (see screenshot above) and find clone url for the development site, which is similar to this: https://dev-my-website-alias.scm.umbraco.io/c565ead8-7a27-4696-9ab4-dad7eba2cd2c.git and remove everything after the last slash, so you have a url that looks like this: https://dev-my-website-alias.scm.umbraco.io

You will be prompted to login to the SCM / Kudu site - use the credentials you normally use to login to the Umbraco Cloud portal. Now click “Debug console” from the top menu and select “CMD”. This will take you to a command line interface from where you need to navigate to the repository folder: site / repository

From here you need to merge the branch (upstream/master), which contains the updates which were fetched from the Baseline project. In the console enter: git merge upstream/master

This will result in an output showing the files, which contains conflicts that you need to resolve in order to fully merge the two branches:

In the above output two files are listed and we want to pick the ones that comes from the current project (the child) - in other words we want to keep our files, as these are content changes. We use the following commands to achieve that:

Note: If you wanted to select the files from the Baseline project instead of the ones from the current project, you should write “--theirs” instead of “--ours” in the command from above. “Ours” corresponds to the current project (the development site) and “Theirs” corresponds to the Baseline project.

Now you need to add the (modified) files to Git and finally commit the changes using the following commands:

The merge conflict has now been resolved, and you can update your local repository with the latest changes by pulling from the development site. Please note that the changes from the commit haven’t been deployed to the website yet, as we have only applied the changes to the Git repository. In order to deploy the recent changes to the website you can push your local changes to the development site or you can use the Kudu api to trigger a deployment. You can use the following command from the Kudu Debug Console to deploy the latest changes:

When you are doing your normal development process, you'd be updating the configuration files in your solution as usual. When you are working with a Baseline setup there are a few things to keep in mind.

When you are deploying updates from the Baseline project to the Child projects, all solvable merge conflicts on configuration files will be solved by using the setting on the Child project.

That also means that if a file has been changed in both the Baseline and in the Child project, the change from the Baseline won’t be applied to the Child. To have custom settings on the Child project, you should take advantage of the vendor-specific transform files.

On Umbraco Cloud, it is possible to create transform files that will be applied to certain environments by naming them like web.live.xdt.config (see ). This should be used when a Child project needs different settings than the Baseline project.

It can be achieved by using a configuration file that is specific to the Child Project, naming it like child.web.live.xdt.config. This file should only be in the Child projects repository, which can be achieved by creating the file locally and pushing it directly to the Child project. Read the article to learn more about how this is done.

Following this workflow will ensure that when the Child is updated from the Baseline, the settings won’t be overwritten.

This practice is especially important when the Baseline project gets major new functionality, like new code that is dependent on the configuration files or when upgrades are applied.

Examples

Here is a few examples of what could be transformed in the child sites.

Adding or updating appsettings (i.e. child-appsettings.web.live.xdt.config)

Setting the SMTP settings for the child project (i.e. child-smtpsettings.web.live.xdt.config)

Setting custom rewrite rules for the child project (i.e. child-iisrewrite.web.live.xdt.config)

The above could either be added to its config files or be split up into one config file per setting. Umbraco Cloud will run through all the config files for the project. i.e. in one file

• child.web.live.xdt.config

or having multiple files

• child-appsettings.web.live.xdt.config

• child-iisrewrite.web.live.xdt.config

• child-smtpsettings.web.live.xdt.config

Umbraco Cloud Projects are made of three major components: Environments, Team Members/Invite Users, and a Settings section.

Environments

The number of Environments in your project is dependent on which plan you are on:

• With the Starter Plan, you have the option to add a Development environment.

• With the Standard Plan, you get a Development and a Live environment with the option to add a Staging environment. You can add/remove environments as needed

• With the Professional Plan, you get a Development, a Staging, and a Live environment - as with the Standard Plan you can add/remove environments as needed.

• With the Enterprise Plan, you get a Development, a Staging, and a Live environment - as with the Professional Plan you can add/remove environments as needed.

Team Members/Invite Users

Settings

A Baseline Child project is very similar to a Fork (forked repository) on GitHub where we create a clone of an existing project while maintaining a connection between the two projects. The connection exists between the Live environment of the existing project, the Baseline project, and the Development or Live environment - of the newly created project, the Child project.

Any project can act as a Baseline project.

The basic idea is that you have a project that contains all your standard Umbraco packages/components, maybe even configured with some default Document Types, which you want to use as a baseline for future projects. When you've made changes to your Baseline project, you can then push these changes out to all the Child projects with a click of a button.

Video Tutorial

Creating a Child Project

To create a child project:

2. Click the Create New Project button.

3. Select Baseline Project.

4. Open the Choose baseline drop-down list and select the Cloud project, the new project should be based on.

5. Choose either Starter, Standard or Professional plan from the Plan Selection window.

6. Enter the Project Name in the Project Information window.

1. Choose an Owner from the drop-down list.

2. Enter your Name, Email, and Telephone in the Technical Contact section.

3. Click Continue.

4. Review the entered information and select I have read and agree to the terms and conditions and the Data Processing Agreement.

5. Click Create Project.

It might take couple of minutes for the project to spin up before your environments are ready. When your environments are ready, you will see a green light next to the environment name.

Restore content from the Baseline project

When you've created the Child project you can choose to restore content from your Baseline project:

1. Go to the Content section.

2. Right-click the top of the Content tree in the Umbraco backoffice.

3. Choose Workspace Restore.

4. The Baseline project should already be selected as the environment to restore from

5. Click Restore from Baseline

If you do not see the content, Reload the content tree once the restore is complete.

As with any Git repository-based development, it is not uncommon to have merge conflicts as the repositories begin to differ. Read this article for more on the merge strategy we use and how to approach resolving these conflicts.

In this article, you'll find a guide on how to upgrade your Child project with changes from your Baseline project.

When you are working with Baseline Child projects you might sometimes want to have an individual configuration for each project - this can be handled using config transforms.

In this article, we will look at how to break the connection between the baseline and one of its child projects.

Here you will find answers to the questions we most commonly hear from people who are wondering if Umbraco Cloud is the right fit for their project. The answers you will find here are of a more technical nature and are directed at developers.

If you are interested in more general information about the product, you should .

General

Can I try before I pay?

Yes, you can and test it for 14 days with no obligation to buy.

Is it a special version of Umbraco that’s used?

No. It's the same as the latest version of Umbraco that you can download.

Can I run my high-traffic site on Umbraco Cloud?

Currently, we have benchmarked a "well-built" site with approximately 50,000 unique visitors per day (~1.5 million per month) that performs well. For business-critical, high-traffic sites, we recommend that you look into Umbraco Cloud Professional and Enterprise possibly in combination with a dedicated server.

Can my site auto-scale or use dedicated worker resources?

Your site can't currently auto-scale, but it is something we’re investigating as a future feature. We do offer dedicated worker resources. .

Can I set up a load-balanced Umbraco Cloud site?

Not currently.

Can I move my site from Umbraco Cloud?

Yes, you can. Umbraco Cloud uses the same Umbraco version that you can download and use on your own. If you decide that Umbraco Cloud is not right for you, you can take some actions alone. You can clone your site, restore your data locally, and delete your Umbraco Cloud project. We will be sad to see you go. But we understand there are some requirements we might be unable to fulfill. So we support and encourage you to choose the best solution for your specific site needs.

Can I move my existing site to Umbraco Cloud?

What languages are available for content localization on Umbraco Cloud?

Umbraco Cloud relies on the underlying Azure infrastructure for content localization in Umbraco CMS. Find the available languages in the dropdown below.

Technology

On what kind of server environment does my Cloud site run?

All available Umbraco Cloud plans are utilizing P1V3 Azure App Service Plans as their underlying infrastructure. A P1V3 Azure App Service Plan offers in total

• 2 CPU Cores

• 8GB of RAM

• 250 GB Disk space

• 1,920 TCP connections

How many resources do I have available for my website?

In our experience, there are only a few Cloud sites that have experienced these limitations and we're happy to work with people who have sites affected by these limitations.

Can I use Cloudflare in front of my Umbraco Cloud site

Yes, you can. Please note that Umbraco Cloud also uses Cloudflare for DNS, so you need to enroll your hostname as 'DNS Only' with a CNAME pointing to dns.umbraco.io. Once you can see the hostname is marked with 'Protected' under the Project / Hostname subpage you can turn on 'Proxying' for the hostname in your Cloudflare account if you need to use specific Cloudflare features like Page Rules.

Does Cloudflare add any additional HTTP request headers?

HTTP headers are bits of information that are passed along within every communication between (web) servers and (browser) clients. All HTTP requests to custom hostnames on Umbraco Cloud pass through Cloudflare.

HTTP requests headers can be useful for for example multilingual purposes to redirect users of certain languages to a specific URL. Here, the collection of visitor location headers below will be helpful. The values for these location headers are derived from the visitor's IP address.

• cf-ipcity: The visitor's city

• cf-ipcontinent: The visitor's continent

• cf-iplatitude: The visitor's latitude

• cf-iplongitude: The visitor's longitude

Note, the HTTP requests headers are available on all custom hostnames created through Umbraco Cloud. But not the default hostname for the Umbraco Cloud project such as project.euwest01.umbraco.io.

Which Umbraco versions are available on Umbraco Cloud?

Upgrades

When does Umbraco get upgraded in the different projects?

We upgrade when we're confident the release is solid.

How do Automated Upgrades work?

We automatically upgrade Cloud projects to the latest patch and minor version of Umbraco CMS, Umbraco Forms, and Umbraco Deploy. When we make a new patch version, we first run it through our test suite, then test it on 10 test sites. When all that passes, we roll out the upgrade in batches of 100 to customer accounts.

My project didn't receive the auto-upgrade. Why?

When we roll out auto-upgrades to Umbraco Cloud projects the first thing that happens is a check of all environments on a project. This check will verify whether the environments are responding and do not return an HTTP status error. If the auto-upgrader encounters HTTP status errors on any of the environments during this check, the upgrade process is aborted. Your project will not receive the upgrade should this happen.

Another reason why your project wasn't auto-upgraded could be, that it failed the test we perform after applying the auto-upgrade. This test compares the state of an environment from before the upgrade with the state of the same environment after the upgrade. If they don't match, we take the appropriate measures to rollback the environment to its previous state. Then the upgrade is aborted of any remaining environments.

Other reasons why you didn't receive the auto-upgrade:

• If you are doing a deployment at the time we tried to run the auto-upgrader on your project.

• If your environments aren't running the same minor version. For example, if you are in the middle of upgrading to a new minor version, and one environment is running 7.6.x while another environment on the same project is running 7.7.x.

Does leaving pending commits (dev to live) derail the upgrade process?

Pending commits won't stop the auto-upgrade.

Is it OK to do manual updates? For example, if a project on 9.4.3 is updated locally to 9.4.4, can we commit back to dev?

Yes, that’s fine. In some cases, you may want to upgrade sooner than the scheduled service upgrade or you may have a site we couldn't upgrade automatically for one reason or another.

Do note, however, that you will need to step through the upgrade installer manually on each environment, including live. Our automated upgrader makes sure that visitors to your live site will not be prompted to log in to the upgrade installer.

I have customized files that Umbraco ships with, will they be overwritten during upgrades?

You will have to assume that every time we upgrade your site, any file that comes with Umbraco by default will be overwritten. Generally, we only overwrite the files that have been changed in the newest release but there is no guarantee for that. So if you (for example) have customized the login page then you can assume it will be reverted on each upgrade.

Testing

Are we allowed to perform penetration tests on our Umbraco Cloud site?

Yes, we're happy for people to do penetration testing on the sites they have built on Cloud. We do ask you to please tell us about these tests beforehand so our support staff knows to look out for possible strange things happening on your site.

We are also happy to receive any test results you receive so that we can improve security in Umbraco where necessary.

Are we allowed to do (D)DOS testing on our Umbraco Cloud site?

It is strictly forbidden to attempt to do a denial of service attack on your Cloud sites.

Can Umbraco Cloud support my website?

The ability of Umbraco Cloud to support your website depends on different factors. This includes the number of visitors and the media storage your site requires.

These details alone do not fully determine whether Umbraco Cloud is the right fit for your needs.

Each website can have different performance requirements based on how it is built and configured. We recommend running a load test, to learn whether Umbraco Cloud can handle your specific website. This test simulates real-world traffic and can help you understand the computation power and resources your website will require.

Are we allowed to do load testing on our Umbraco Cloud site?

We would like to talk to you beforehand about your test plan for a load test on your Cloud site.

Security and encryption

Does Umbraco Cloud support TLS / HTTPS?

Yes, in fact, Umbraco Cloud provides automatic Transport Layer Security (TLS)/HTTPS certificates for all hostnames added to an Umbraco Cloud Project's environment. Umbraco Cloud will automatically renew the certificates, which are issued by Cloudflare. By default, the certificates are valid for 90 days and are then automatically renewed for as long as the hostname is active on Umbraco Cloud.

Does Umbraco Cloud support custom certificates?

Yes. Pro and Enterprise Plans can add custom certificates for each of their custom hostnames in order to override the certificates that are provided by Umbraco Cloud by default.

Does Umbraco Cloud support HTTP/2?

By default, Umbraco Cloud supports HTTP/2.

There's an ARRAffinity cookie on my site which is not sent over HTTPS, is this a security risk?

No this is not a security risk. This cookie is set by the load balancer (LB) and is only used by the LB to track which server your site is on. ARRAffinity cookie is a built-in feature of Azure App Service and is only useful when your website is being scaled to multiple servers. In Umbraco Cloud, we cannot scale your site to multiple servers so the cookie is effectively unused.

Can I use wildcard certificates on Umbraco Cloud? How about an EV, DV, or OV certificate?

Yes. You can use any valid certificate on Umbraco Cloud.

I get a warning that "your connection is not private" and the certificate is served for *.umbraco.io

How can I control who accesses my backoffice using IP filtering?

Yes. On Cloud, you can add an IP filter of your choosing. There are a few things you need to pay attention to though. Umbraco Deploy will still need to be able to talk to the different environments in your Cloud website and you should still be able to use the site locally.

Does Umbraco Cloud use Transparent Data Encryption (TDE) for databases?

Yes, every site created after May 2nd, 2017 will have TDE enabled by default. For older sites, we can enable this by request.

Building and deploying

Umbraco Cloud creates a SQL/LocalDb database for me, can I use a shared SQL Server for my development team instead?

No, you should not use a shared database for your team. Umbraco Cloud is made so that each team member can safely make any changes they need and then send them to your development environment on Cloud. Another developer can do the same and also send their changes to the dev to test. Once you're happy with all of the changes, each developer can pull down the changes from development and continue working on the next change.

Not only does this promote working in small increments it also prevents two problems:

2. Our deployment engine (Umbraco Deploy) is not made for this and your local site will quickly get out of sync with the changes both developers are making. Once you push your changes up to your Cloud instance you can expect to see errors and mismatches because changes have not been saved correctly.

Can I use a custom .NET code?

Yes, you can make your Umbraco implementations as you're used to, including custom .NET assemblies.

Umbraco Cloud sites run on IIS 8.5 so most things you can normally do on IIS, you can do on Umbraco Cloud. We don't, however, offer support for custom components that have to be installed on the server itself. If you can ship it in the bin folder, it should generally work on Cloud.

If you have any experience with Azure Web Apps, Cloud works in the same way. So if you can make it run on Azure Web Apps, you can make it run on Umbraco Cloud.

Is it possible to add my own custom DLLs for extending the Umbraco Backoffice?

Yes, an Umbraco Cloud project is similar to a normal Umbraco website where we give you multiple environments and deployment of code and content between these environments. You can run your site locally (via Git) which is the best way to add your own code (templates, cs files, packages, DLLs, and so forth).

Is it possible to add custom tables in addition to the Umbraco Cloud database?

Yes, you can create custom tables in the database. Find the connection strings to the databases on the different environments on the "Connection Details" page found in the "Settings" menu.

Note that custom database tables and data do not replicate automatically across Cloud environments. You might want to use Umbraco Migrations and our PetaPoco data layer to make the deployment of your custom data more automated.

I would love to use Websockets on my site, is this possible?

Yes, it is! Websockets are enabled on all sites.

My deletions are not picked up when deployed to the next environment

When you've deleted something (e.g. content, media, or schema) on one environment, the deletions will not be picked up on the next environment when you deploy.

This is intended behavior.

We will only delete the files and not the database entries, as this could potentially cause you to lose data on your Live/production environment.

Package support

Do you support package "x" on Umbraco Cloud?

Umbraco Cloud uses Azure App Service Plans for website hosting services. This is a typical platform used for hosting web applications and it offers all features necessary for running Umbraco websites.

Given that, packages that run in your local development environment, or on other hosting platforms, are likely to also be supported on Umbraco Cloud.

The only potential issue to be aware of is if your package stores custom data in the Umbraco database. Most packages don't do this, either purely adding functionality, or using existing Umbraco services for any data storage they require.

If a package does save data into a custom table within the Umbraco database, it will still operate as expected on Umbraco Cloud. However, unless the package developer has taken additional steps to support this, you won't be able to transfer the saved information between environments.

In some cases though, you may want to be able to transfer data prepared in a staging environment to production. Or conversely, to restore it into a local development environment for debugging purposes. The package may or may not be built to support this.

If you find you are unable to move information between the environments you should contact the package's developer to ask about plans for support. How a package developer can offer this feature is described in the following section.

How do I make my package support Umbraco Cloud?

As discussed in the section above, most packages will work fine in Umbraco Cloud without any modification.

Some packages save data into custom Umbraco database tables, and if so, it may be useful to be able to transfer that data between environments. If this is the case, then there is an extra step you should take to fully support usage of your package on Umbraco Cloud.

In order to support custom data transfer between environments, the package or solution developer needs to build an add-on to their package. This extends Umbraco Deploy with a "connector" that details of how the data for the package should be handled.

Specific care needs to be taken when developing the connector if the package stores references to content nodes, media items, or members in Umbraco.

There are two challenges here:

1. Your package is referring to an integer identifier, for example, a content item with the id 1023. On the next environment that same content item exists but since the content is a bit different there, the id is 1039 instead. Umbraco Deploy needs to know how to connect the correct identifier.

2. Even if the identifier is correct in both environments your package might rely on the other item (the one you're referring to) to exist in the next environment. So if the content item you're referring to (1023) does not exist in the environment where you're pushing the content you might see errors in your package.

Umbraco Deploy Contrib is included in all Cloud sites and we keep it upgraded to the latest version for every site.

The code in these projects should also help you understand the steps and how to build something similar for your own package.

If you need help with this, don't hesitate to reach out to us and we'll be happy to give you some tips.

Regions

Can I choose which region my projects run in?

Yes, you can choose between West Europe, East US, South UK, and East Australia regions.

Can I move my existing project created on Cloud in the EU region to other regions?

How do I select a region when creating projects on Cloud?

You can choose a region from the Region drop-down list when creating a new project.

Can I have a Baseline master project in the EU and a Baseline child project in the US?

No. Baseline projects are bound to a region for now.

Will my sites receive automatic patch upgrades of CMS, Deploy, and Forms when new releases are available?

Yes. The US region is no different than normal Cloud other than its regional location. That means that the patch-upgrade functionality will work in whichever region you choose.

Can you create Umbraco Heartcore projects in other regions besides EU?

Not at the moment.

Are all the features we have in Umbraco Cloud available in the US and UK regions?

Baseline functionality is not supported in the US and UK regions at the moment. Other than that, all features are fully supported.

Are you planning to add other regions in the future?

Yes. Once we have specific plans, we will announce them publicly.

Where can I see what region my project was created in?

The hostnames contain the region your project is hosted on. Currently, there are 3 options available when choosing a region for your Umbraco project:

• West Europe (euwest01). For example, https://west-europe-project.euwest01.umbraco.io/

• East US (useast01). For example, https://east-us-project.useast01.umbraco.io/

• South UK (uksouth01). For example, https://south-uk-project.uksouth01.umbraco.io/

• East Australia (aueast01). For example, <https://east-australia-project.aueast01.umbraco.io/>

Backups and data retention

What backup and restore options are available on Umbraco Cloud?

Database

By default, a 35-day point-in-time database restore is available for your projects. It is also possible to restore a .bacpac file to your cloud environments.

Filesystem

Umbraco Cloud keeps 30 days of snapshots of the filesystem for disaster recovery purposes.

Blob Storage containers

Umbraco Cloud keeps 35 days of snapshots of the Blob Storage container for disaster recovery purposes.

When a project has one or more Child Projects it will appear on the Project page and the user can click to get an overview of all the Child Projects based on the current project.

From this page, you will have an overview of all the Child Projects this Baseline project has. This is also where you go when you want to push upgrades from your Baseline Project to the Child Projects.

To do a minor or major upgrade of a Baseline project and its Child projects, the first task is to run the upgrade on the Baseline project itself.

Once the upgrade has been verified on the Baseline project, follow the guides outlined here to push the upgrade to the child projects.

Upgrading Child Projects to a New Major Version

1. Go to the child projects you are upgrading.

2. Go to the Advanced Setting tab.

3. Update the .NET version to the corresponding one for the major version upgrading to.

4. Go to the Baseline Project.

5. Click on "Manage updates here".

6. Select the Child Projects you want to push your upgrades to - you can select as many or as few as you like.

7. Click Update all child projects or Update selected.

8. Click Confirm once the selection looks correct.

If the upgrade has been completed successfully, the Child Projects will be displayed under the Successful Updates/upgrades section.

Deploying Minor upgrades to Child projects

1. Go to the Manage child projects page on the Baseline.

On this page, the Child projects will have an available upgrade.

1. Select the projects you want to upgrade.

2. Click the "Upgrade selected children" button.

First, any pending changes made on the Baseline will be deployed to the child site.

Once the changes have been deployed, the child site will be upgraded to the same version as the Baseline site.

The upgrade itself will happen once you click the upgrade button. This will start by triggering the update, where all the files are updated on the children from the baseline.

Once the files are in place, we also run the upgrade process, making sure that the children are fully upgraded.

The reason for this is that the Child Projects config files will be merged by choosing the parent's config files first. That is to ensure that changes to config files, that have been made in the minor upgrade, will also be applied to the child projects.

Errors while upgrading children from baseline

If the upgrade of a Child project fails, or the Child project is left in a bad state, it is most likely because the Child project was unable to be merged properly.

When updating Child projects from a Baseline project, a configuration from the Child project will take precedence over the Baseline project configuration. This means that when the update from the baseline to the child runs, the configuration file sometimes won’t be changed.

If the flow isn't used, then the repository will be in a state where the code has been updated, but the configuration files haven’t been updated. The solution is to manually fix the configuration files on the child project. Do a comparison of the configuration files on the baseline and the child, and make sure that all changes have been added to the child’s configuration files.

Now that you've created a project, there are a few things you may want to do to make working with your project easier. As you get ready to launch your live site, there are some other considerations to consider as well.

Most of the set up can be accomplished by using the options from your project's Settings drop-down. Some of the setups apply to all your projects, so you'll make these updates from your Profile section.

Managing your project

Articles about configuring settings on your project, as well as managing members, domains, and certificates.

• Going Live

• Project Settings

• Adding Team Members

• SMTP Settings

• Manage Hostnames

• Manage Environments

• Manage Transport Security

Working with your Umbraco Cloud project

Articles about how to work locally with your Umbraco Cloud project.

• Working with your site locally

Related topics

• Media on Umbraco Cloud

• Power Tools (Kudu)

• Config transforms for each environment

In this article, we will look at some of the best practices and recommendations when you are working in teams on your Umbraco Cloud projects.

Working with Git in Teams

Pull before you Push

Always start by making a pull request from your project before you push anything back up to Cloud. This way you ensure that you do not accidentally overwrite the work that someone else in your team has worked with.

Create branches locally

Umbraco Cloud is built on top of Git which means that you can create branches locally as either a feature or developer branch. You can then work on the project and test out the new features before merging it into the master branch. The branch can then be pushed up to your cloud environments.

Working with Environments in a team

Set up a Development environment

We highly recommend that you use a Development environment when you are working in teams. With the Development environment, members of a team can work on their local version of the project. They can then push back up to the development environment to be tested and approved before being deployed to either the staging or the live environment.

Set up a Staging environment

When working in a bigger team with both developers and content editors, we highly recommend that you set up a Staging environment. This way the developers can continue developing in the Development environment, while the content editors can focus on creating delightful content in the Staging environment.

Team development workflow On Cloud

For a more in-depth example of how to work in teams on Umbraco Cloud projects, Our Gold Partner ProWorks have created an article about how they have set up a Team development workflow on Umbraco Cloud.

This article can serve as inspiration if you are an agency and are looking into setting up a bigger project where several people will be working on Umbraco Cloud.

Umbraco Cloud plans Starter, Standard, and Professional are running on shared infrastructure, referred to as pools. To ensure performance and prevent exhaustion of a given pool, each website is assigned a resource quota, depending on the plan, and resource usage is continuously monitored.

The shared resources used by the Umbraco Cloud websites are:

• CPU

• RAM/Memory

• Disk space

• TCP connections

Currently, all available Umbraco Cloud plans are utilizing P1V3 Azure App Service Plans as their underlying infrastructure. A P1V3 Azure App Service Plan offers in total

• 2 CPU Cores

• 8GB of RAM

• 250 GB of Disk space

• 1,920 TCP connections

To ensure stable performance of all websites hosted on Umbraco Cloud shared plans, soft and hard quotas were implemented. Quotas per site and the number of sites in the pool vary per Umbraco Cloud Plan.

Plan quotas for shared Umbraco Cloud Plans

Whenever a CPU or memory plan quota is met, the website will be restarted within a minute to ensure stable performance for all websites in the pool. Meeting a disk quota will result in errors whenever performing write operations to disk. No plan limits exist for TCP connections per site, besides the total amount of TCP connections available to all sites in the pool set at 1,920, attempting to open new TCP connections afterwards will result in errors.

Umbraco Cloud Starter plan

• CPU - 20% (120 sec of CPU time for a 5-minute period)

• Memory - 1500 MB (in private bytes)

• Disk - 7800 MB

Umbraco Cloud Standard plan

• CPU - 35% (210 sec of CPU time for a 5-minute period)

• Memory - 1800 MB (in private bytes)

• Disk - 9600 MB

Umbraco Cloud Professional plan

• CPU - 50% (210 sec of CPU time for a 5-minute period)

• Memory - 2000 MB (in private bytes)

• Disk - 10400 MB

These are hard plan quotas that cannot be exceeded for more than a 5-minute interval. When a cloud environment surpasses the CPU or memory limits defined by the plan quota, the app service hosting the environment will automatically restart. If the app service experiences multiple restarts, we will relocate it to a dedicated environment. This ensures other tenants in the shared pool are not negatively impacted.

You can look at the pricing, plans, and features on the Umbraco Cloud Pricing page.

One way to start your Umbraco Cloud journey is to migrate an existing Umbraco CMS project to the platform. There are some requirements that this project needs to meet as well as some specific steps to follow.

In this article, you can find all the information you need to migrate your existing Umbraco CMS project to Umbraco Cloud.

Requirements

To properly migrate your Umbraco CMS project to Umbraco Cloud it is important to ensure that your project meets the requirements.

Each requirement outlined below is presented with recommended suggestions when a project does not meet the requirements.

Prepare your project

Before initiating the migration, the project should be cleared of unnecessary files and data. This includes emptying recycle bins in the Umbraco backoffice and deleting temporary files in the project repository.

1. Run the project.

2. Access the Umbraco Backoffice.

3. Empty the Recycle bin in the Content section.

4. Empty the Recycle bin in the Media section.

5. Stop the project.

6. Delete the following folders from the project directory:

   • umbraco/Data/TEMP

   • umbraco/Logs

Create a database backup file

The data from the Umbraco CMS project will be migrated to Umbraco Cloud by uploading a database .bacpac file. The next steps will guide you through creating a .bacpac file from the project database.

1. Use Microsoft SQL Server Management Studio or a similar tool to export a .bacpac file of your project database.

2. Save the .bacpac file on your machine.

Create a new project on Umbraco Cloud

When migrating a project to Umbraco Cloud it is important to do so with a clean project. Using a clean project ensures that no unknown factors can come into play during the migration.

You can create a new Umbraco Cloud project in one of the two ways:

• Create an Umbraco Cloud Trial project.

  • The project will be free for 14 days, whereafter a subscription is required.

• Create a new Umbraco Cloud project from the Umbraco Cloud Portal.

  • Follow the setup instructions detailed below.

Create a new project

1. Click Create project in the Umbraco Cloud Portal.

2. Choose Umbraco Cloud as the Type.

3. Choose a plan that enables you to add a Development environment.

4. Select the version that matches the project you want to migrate.

5. Give the project a name.

6. Choose from which Region the site should be hosted.

7. Select a project owner.

8. Ensure a Technical contact is added.

9. Click Continue.

10. Verify all the information is correct.

11. Check the "Terms and conditions" box.

12. Click Create Project.

Once the project is set up, add a Development environment. This will enable you to start over with the migration, should something go amiss.

With the Cloud project set up and ready, the migration can start in the next step.

Upload the database to Umbraco Cloud

The database is uploaded to the Umbraco Cloud project via the Umbraco Cloud Portal.

Follow the Upload Database and Restore Database sections in the Database Backups article to complete this step in the migration.

The Umbraco Cloud project is now ready for the next step where the two projects will be merged.

Merge the projects

To continue the migration the next step is to clone down the Umbraco Cloud environment to merge it with the Umbraco CMS project.

Follow the steps outlined in the Working with a Local Clone article to clone down the Development environment of the Umbraco Cloud project.

In the following steps, the Umbraco CMS project will be merged into the Umbraco Cloud project.

1. Move the following files from the Umbraco CMS project into the cloned Cloud project:

   • View files in ~/Views (.cshtml)

   • Controllers and Models

   • CSS files and scripts in ~/wwwroot

2. Merge the relevant configuration files.

   • Use a tool like DiffMerge to identify which configurations to merge.

   • Do not merge the following configuration keys in appSettings.json:

     • Umbraco:CMS:Global:Id

     • Umbraco:CMS:Global:UseHttps

     • Umbraco:CMS:Global:NoNodesViewPath

     • ConnectionStrings:umbracoDbDSN

     • ConnectionStrings:umbracoDbDSN_ProviderName

3. Merge custom code in the Program.cs file.

4. Open the appSettings.json file.

5. Connect the Cloud clone to the Umbraco CMS project database by adding a new connection string:

"ConnectionStrings": {
    "umbracoDbDSN": "Server=myServerAddress;Database=myDataBase;User Id=myUsername;Password=myPassword;TrustServerCertificate=true;",
    "umbracoDbDSN_ProviderName": "System.Data.SqlClient"
  }

1. Run the project locally.

All data, content, and configuration have been merged into the cloned Cloud environment.

The next step in the migration is to generate data files needed to synchronize with the Cloud project.

Generate data files

1. Access the backoffice of the local Cloud clone using Umbraco ID.

1. Navigate to the Deploy dashboard in the Settings section.

2. Locate the Export Schema to Data Files in the Deploy Operation section.

3. Click Export Schema to initiate the export.

1. Use the Deploy Status section at the top to determine when the export is complete.

1. Stop the project.

2. Add and commit the changes through Git.

   • Learn more about working with a local Cloud clone in the Deploying Changes article.

3. Push the migration to the Cloud environment.

All content, data, and configuration, except for the media files, have been migrated to the Cloud project.

The next step will be to add the media files to the Cloud project using Azure Blob Storage.

Migrate media files

All media on Umbraco Cloud projects are stored in a dedicated Azure Blob Storage container.

Follow the guide in the Connect to Azure Storage Explorer article to access the Azure Blob Storage container connected to the Development environment.

1. Locate the media files for your Umbraco CMS project.

2. Copy the ~/wwwroot/media folder into the Azure Storage Explorer.

1. Reload the front end and backoffice of the Umbraco Cloud project to verify that the images have been added correctly.

The Umbraco CMS project has now been migrated to an Umbraco Cloud project.

Verify the migration

Verifying the migration by cloning the Development environment to your local machine is recommended.

This needs to be a new clone. The clone used throughout the migration steps can be deleted.

Follow the steps outlined in the Working with a Local Clone article to clone down, restore, and run the Development environment locally.

Next steps

The Umbraco CMS project has now been migrated onto Umbraco Cloud.

Deploy the migration to the Live environment

Following this guide, the Umbraco CMS project has been migrated to the Umbraco Cloud Development environment. For the migration to be complete, it should be deployed to the Umbraco Cloud Live environment.

Publish the website

To publish the website to the web, attach a hostname to the Live environment.

Once you have added your custom hostnames to your Umbraco Cloud project, it's possible to configure certain transport security options for all or specific custom hostnames within your project. These security options all relate to the traffic that goes through your hostname from the origin (Umbraco Cloud) to the end-user - meaning the protocols and encryption used to transport your website and assets from the webserver to the browser.

Currently, these options are available:

• HTTP/2 (default: on)

• TLS 1.3 (default: off)

• Minimum TLS Version (default: 1.2)

When a new custom hostname is added to a Project it will have the default settings applied. But you can change the defaults for your Project, so new custom hostnames will get the default settings you have chosen.

HTTP/2 Explained

The first usable version of HTTP was created in 1997. Because it went through different stages of development, this first version of HTTP was called HTTP/1.1. This version is still in use on the web. In 2015, a new version of HTTP called HTTP/2 was created. HTTP/2 progressively enhances your website’s performance. When a browser supports HTTP/2, Umbraco Cloud will take full advantage of HTTP/2 performance benefits end to end. For older browsers or non-HTTPS requests, the traffic will fall back to HTTP/1.1. You don’t need to choose between better performance and backward compatibility, which is why HTTP/2 is enabled by default for all new custom hostnames added to a Umbraco Cloud project.

TLS 1.3 Explained

Transport Layer Security (TLS) TLS 1.3 is the newest, fastest, and most secure version of the TLS protocol. SSL/TLS is the protocol that encrypts communication between users and your website. When web traffic is encrypted with TLS, users will see the green padlock in their browser window. By turning on the TLS 1.3 option, traffic to and from your website will be served over the TLS 1.3 protocol when supported by clients. TLS 1.3 protocol has improved latency over older versions, has several new features, and is currently supported in both Chrome (starting with release 66), Firefox (starting with release 60), and in development for Safari and Edge browsers.

Minimum TLS Version Explained

Minimum TLS Version only allows HTTPS connections from visitors that support the selected TLS protocol version or newer. This option relates to the TLS versions mentioned above and the current default, which is TLS 1.2. If you want your website traffic to only use TLS 1.3 you can change the minimum version. But be mindful of the implications that this might have (see browser support above). You don't need to change the minimum version to use TLS 1.3.

Plan specific features

Access to the different options varies depending on the Umbraco Cloud plan your project is on. Currently, the features are available as follows:

• Starter: HTTP/2

• Standard: HTTP/2, TLS 1.3, Minimum TLS Version

• Professional: HTTP/2, TLS 1.3, Minimum TLS Version

Security subpage

Click Security from the Settings dropdown on your Umbraco Cloud Project. The Security settings are scoped per environment, so if you have multiple environments and add your custom hostnames to different environments you can select the environment at the top of the page.

Aside from the environments, the Security page is divided into 'Default Settings' and 'Hostname Specific Settings'. Use the Default Settings to configure what should be applied to new and existing custom hostnames by default.

If you want to have different security options for different custom hostnames, then select the custom hostname under Hostname Specific Settings and adjust the options for that specific hostname. This might be useful if you want to test the different options on another custom hostname than your primary hostname.

Cipher Suite Management

On the security page, it's possible to enable or disable the different cipher suites for your project.

Enabling or disabling the different ciphers can be done under the minimum TLS version in the Ciphers drop-down:

Like the other Hostname Specific Settings, you can enable/disable specific ciphers for your custom hostname based on your needs.

When you create an Umbraco Cloud project, the project URLs are based on the name of your project.

Let's say you have a project named Snoopy. The default hostnames will be:

• Umbraco Cloud Portal - www.s1.umbraco.io/project/snoopy

• Live site - snoopy.euwest01.umbraco.io

• Development environment - dev-snoopy.euwest01.umbraco.io

• Staging environment - stage-snoopy.euwest01.umbraco.io

The hostnames contain the region on which your project is hosted. Currently, there are four options available when choosing a region for your Umbraco project:

• West Europe (euwest01),

• East US (useast01),

• South UK (uksouth01), and

• Australian East (aueast01)

To access the backoffice, add /umbraco at the end of the Live, Development, or Staging URL.

Domains

To add and manage your hostnames on Umbraco Cloud, follow the steps below:

1. Go to your project on Umbraco Cloud.

2. Go to Configuration in the side menu.

3. Click on Hostnames in the menu.

4. Click Add new hostname to add a new hostname.

Ensure that the hostname you are binding to your Umbraco Cloud environment has a DNS entry that resolves to the Umbraco Cloud service. The DNS settings can either use a CNAME or an A & AAAA record:

• CNAME: Usually used for domains with "www" in the URL.

This is recommended to use, if possible, as the record is not changed as often as A & AAAA IPs are. When setting up a CNAME it needs to point to dns.umbraco.io.

• A & AAAA records: Are usually used for the Apex domain (without "www" in the URL).

It needs to be created at the root of your domain.

• A-records to either or both IPv4 addresses:

  • 162.159.140.127

  • 172.66.0.125

• AAAA records to either or both IPv6 addresses (to support IPv6 connectivity):

  • 2606:4700:7::7d

  • 2a06:98c1:58::7d

Check with your DNS host or hostname registrar regarding configuration details for your Hostnames.

To specify the hostname for each root node using a multisite setup, follow these steps:

1. Go to the Backoffice of the project.

2. Right-click the root content node.

3. Select Culture and Hostnames.

4. Click Add New Domain in the Culture and Hostnames window.

5. Enter your Domain name and select the Language from the drop-down list.

1. Click Save.

Using special characters

Umbraco Cloud supports Internationalized Domain Names (IDN) allowing you to configure domain names including special characters.

When using an IDN direct access to the Umbraco backoffice from that domain is unavailable. If you have configured måneskin.dk as a domain, you cannot access the backoffice using måneskin.dk/umbraco. The backoffice will still be accessible using the default Cloud URL (maaneskin.euwest01.umbraco.io/umbraco), or from other domain names that do not include special characters.

Automatic Transport Layer Security (TLS)

All hostnames added to an Umbraco Cloud project's environment will get a TLS (HTTPS) certificate added, by default. The certificate is issued by Cloudflare and valid for 90 days after which it will be automatically renewed. Everything around certificates and renewals is handled for you and you only need to ensure the DNS records are configured according to our recommendations above.

Is your Domain hosted on your own Cloudflare account?

Cloudflare is a popular DNS provider, which offers a variety of different services to improve performance and security. We also use it for DNS and Hostnames on Umbraco Cloud.

When adding a hostname to your project hosted on Umbraco Cloud, using your own Cloudflare account the process is slightly different.

1. Set Proxy Status to DNS Only when creating a CNAME or A-record for your hostname in Cloudflare.

2. Change Proxy Status to Proxied once your hostname is Protected on the Hostname page for your Cloud project. Also, make sure the website is accessible through the hostname.

The above is primarily relevant when you need to use specific Cloudflare services like Page Rules, Workers, and so on.

Using Certificate Authority Authorization (CAA) for your domain?

This is necessary because Google Trust Services is the Certificate Authority for the certificates issued on Umbraco Cloud.

CAA records can be set on the subdomain, but it's not something that is commonly used. If there’s a CAA record at, e.g., app.example.com, you’ll need to remove or update it. If you want to use wildcards and allow certificates for any subdomain, the CAA record should look like this:

On the Professional and Enterprise plans, you can manually add your certificate to your project and bind it to one of the configured hostnames.

Using your Web Application Firewall (WAF) on Umbraco Cloud

If you need to use WAF in front of your Umbraco Cloud website this section will highlight some of the common configurations needed.

In most cases, you need to ensure that the WAF and Umbraco Cloud are using the same certificate on the specific hostname. Custom certificates are a plan-specific feature on Umbraco Cloud, so make sure that you have access to upload certificates.

• Make sure the hostname is pointing to Umbraco Cloud (dns.umbraco.io).

• Certificate issued for the actual hostname. A custom certificate is required for a WAF hostname.

When configuring the hostname and certificate on Umbraco Cloud it will be necessary to validate the hostname using a TXT record. This is needed because in most cases the WAF will hide that the website is running on Umbraco Cloud. This means that the usual domain ownership verification cannot be performed. This same approach can also be used to configure a hostname before updating the DNS for the hostname.

Adding a hostname on a Cloud project is possible before a DNS change. It can take up to approx. 14 days before it's removed. That means that you have 14 days to add a TXT record in your DNS settings.

Reach out to support and they will assist you with the details needed to be in the TXT record. We will first be able to see what you need to add to the TXT record when you have added the hostname.

When that is added it should work immediately.

Learn more about best practices for working with rewrite rules on Umbraco Cloud projects.

Each Umbraco Cloud project can have multiple environments: Development, Staging, and Live depending on your Cloud project plan. Each environment has its own git repository that is hosted on Umbraco’s Cloud platform.

Ideally, your Umbraco Cloud setup should look like this:

• A source control repository with your own code

• A Umbraco Cloud source control repository with the locally cloned Umbraco project

A source control repository with your own code

Source control is a way to control changes to files and directories. You can keep a record of changes and revert to specific versions of a file in the event you would like to back up to an earlier time. A source control repository is used as the single source of truth that has the latest version of your project source code with all the git branches.

There are different source code management tools that you can use such as GitHub, Git, GitLab, Apache Subversion (SVN), Mercurial, etc.

A Git Umbraco Cloud source control repository with the locally cloned Umbraco project

We recommend creating a Cloud project with at least two environments: a Development environment and a Live environment. To work with a local copy of your site, you then clone down the Development environment using the Clone project option from the Cloud Portal and start building your website locally. This repository is different from your source control repository.

Once you're happy with the results or wish to see how your website has progressed, you push the changes back to the Development environment. If everything is working as expected you then deploy your changes to the Live environment.

Creating a project on Umbraco Cloud, you can choose to host the project in different regions: East US, West EU, South UK, or East Australia.

In some cases, you might want to migrate your project(s) from one region to another. This article will outline the steps to do this.

The East US and West EU regions will be used as examples in this article.

Prerequisites

• Admin access and deployment rights on the project that is to be migrated.

• A clone of both East US and West EU projects.

• A local setup that can run an Umbraco instance. Learn more about this in the Requirements article.

Prepare your projects

The first step in this process is to create a new Umbraco Cloud project in the region you want to migrate your existing project to. In this case that will be the East US region.

This is done by selecting East US from the Region dropdown when creating the Cloud project.

The new project in the US region will run the latest version of Umbraco CMS, Umbraco Forms, and Umbraco Deploy. You will need to ensure that the project you are migrating is running the exact same version of each product before initiating the migration process.

Find more details on how to upgrade your project in the Upgrades documentation.

Migrate the project

The following steps will guide you through the migration process.

Step 1: Create and Restore Database Backup

1. Go to Configuration > Backups on the West EU Cloud project.

2. Create a backup of the projects database.

3. Download the backup to your local machine.

4. Go to the East US project.

5. Go to Configuration > Backups.

6. Upload the database backup that you created in the previous step to the project.

7. Restore the backup to your environment

   • Optional: Create a backup of the environment before restoring the backup.

8. Run Export Schema from the Deploy Dashboard in the Settings section of the East US project.

9. Run Update Umbraco Schema from the Deploy Dashboard in the Settings section of the East US project.