Connect to Managed Cloud xDB

Last updated Friday, August 10, 2018 in Managed Cloud for Administrator, Developer
Keywords: Cloud, xDB Cloud

Sitecore Managed Cloud xDB provides support for customization by running on the Azure App Service.


Before configuring Sitecore for Managed Cloud xDB, you must ensure that you are running Sitecore 8.2 Update-1 or later. See the Managed Cloud xDB service compatibility tables for the list of versions that are supported by the Managed Cloud xDB service for new xDB customer sets.

This topic describes how to:

Request the Managed Cloud xDB customer set

To request a Managed Cloud xDB customer set, you must register a support ticket through the Sitecore Support portal. To register a support ticket:

  1. Go to Introducing the Sitecore Managed Cloud Service.
  2. Work through the section: Requesting your environment with Sitecore Managed Cloud.

If you do not have a valid Sitecore certification, you must contact your Sitecore Implementation Partner to register the support ticket for you. If this is not possible, contact your Sitecore representative to access the Sitecore Support portal.

Sitecore Support will provide you with:

  • The following MongoDB connection strings: analytics, tracking.livetracking.history,
  • A Search index connection string:
  • The Reporting Service settings, including the address of the service, and the API key.


Save these details because you need them when you configure xDB on your Sitecore instances.

Configure the connection to the Managed Cloud xDB service

When you have installed the CD and CM instances, the next stage is to configure them to communicate with dedicated Azure services of Sitecore Managed Cloud xDB. The steps below apply to both CM and CD instances unless otherwise stated.

To configure the connection to the Managed Cloud xDB service:

  1. Disable the following configuration files by adding the .disabled extension to the file name or by removing them from your local installation.

    File path (relative to the website root)

    Configuration file name























  2. Work through Configure a content management server to use a remote Reporting Service server. Specifically, you must enable and disable your configuration files according to the table in the Configure Path Analyzer section.
  3. In the ConnectionStrings.config file (Website/App_Config), use the connection strings from the response that you received from Sitecore Support to configure the following connection strings for MongoDB, Azure Search, and the Reporting Service Authentication.

    The MongoDB connection strings:

    • analytics
    • (CM or standalone only) tracking.history

    Azure Search connection string:


    Reporting Service authentication key:

    • (CM or standalone only) reporting.apikey
  4. In the ConnectionStrings.config file (Website/App_Config), remove the following connection string:

    <add name="reporting" connectionString="Data Source=…"/>

  5. In the configuration Include folder (Website/App_Config/Include/), enable all of the Azure files, (.*Azure).
  6. In the configuration Include folder (Website/App_Config/Include/), disable all of the Lucene files, (.*Lucene).
  7. (CM or Standalone only) In the Sitecore.Xdb.Remote.Client.config file (Website/App_Config/Include), configure the Reporting Service by using the actual Service URL from the response that you received from Sitecore Support. For example:
        <httpTransportFactory type="Sitecore.Analytics.Commons.ApiKeyHttpTransportFactory, Sitecore.Analytics" singleInstance="true">
    <param desc="serviceUrl">[reporting URL value]</param>
          <param desc="requireHttps" type="System.Boolean" factoryMethod="Parse" arg0="true" />

Deploy marketing definitions

To deploy the marketing definitions:

  1. Enable the following file by removing the .disabled extension.


  2. Go to the Sitecore Launchpad, Control Panel. Under Deploy marketing definitions, select all checkboxes.
  3. Click Deploy.
Send feedback about the documentation to