Dev GuideAPI Reference
Dev GuideAPI ReferenceUser GuideGitHubNuGetDev CommunitySubmit a ticketLog In
GitHubNuGetDev CommunitySubmit a ticket

Set up Microsoft Azure

This topic describes how to store product images and documents associated with products on Microsoft Azure in Optimizely Configured Commerce.

Optimizely Configured Commerce can use Microsoft Azure to store product images and related documents. This section provides an overview of the components necessary to set Configured Commerce to use Microsoft Azure.

Visually, the Admin Console will not change, and the process for adding content like images is the same as when using a local file system.



  • An active Microsoft Azure Account
  • Your Microsoft Azure Account Name
  • Your Microsoft Azure Account Key

As of the December 2016 Service Pack, Configured Commerce now supports SQL Azure databases; it is no longer necessary to host the SQL Server on an Azure VM.

The following Settings must be set in order to use Azure as your file store location.

[4.6]The following Settings must be set in order to use Azure as your file store location. These settings display if your storage provider is not set in the appSetting file of your project. If your storage provider is set in the appSetting file, these settings will appear grayed out and some data may appear blank or masked by field based on its sensitivity.[4.6]

Setting NameDescription
Storage ProviderAzure
Once Azure is selected for the Storage Provide, the Settings below will display.
Account KeyRequired value for the Azure Account Key
Account NameRequired value for the Azure Account Name
Default End Points ProtocolRequired value for the Azure EndPoint Protocol. This defaults to https.
Container NameRequired value for the Azure container name. This defaults to userfiles.
Public Host NameOptional value that defaults to " ". This is an override for the Azure Storage Container public hostname. When setting this, do not include https.



The December 2016 SP included changes in integration processing to stop using global temp tables (which is not supported in SQL Azure). It also removed the usage of the SQL Server SignalR backplane because SQL Azure does not support being a SignalR backplane.