Deploy a new e-Commerce tenant

Important

Dynamics 365 Retail is now Dynamics 365 Commerce - offering comprehensive omnichannel commerce across e-Commerce, in-store, and call center. For more information about these changes, see Microsoft Dynamics 365 Commerce.

This topic describes how to deploy a new e-Commerce site by using Microsoft Dynamics Lifecycle Services (LCS).

Overview

Microsoft Dynamics Lifecycle Services (LCS) is a cloud-based collaborative workspace that partners and customers can use to manage their projects and environments, view the latest information about Microsoft Dynamics products and features, and create, track, and browse support incidents. E-Commerce management features are integrated into LCS.

To learn more about LCS, see the Lifecycle Services User Guide.

Get started

Before you can initialize e-Commerce, you must initialize a project, an environment, and a Retail Cloud Scale Unit (RCSU). To do the initialization in LCS, you must have permissions for either the Project Owner or Environment manager role. The production and sandbox environment topologies are supported.

For more information about environments, see Environment planning. For more information about RCSU, see Initialize Retail Cloud Scale Unit.

Initialize e-Commerce

Use this procedure to initialize the e-Commerce feature in an existing environment.

Before you begin, make sure that you have the following required information:

  • The RCSU that will be used.
  • The Microsoft Azure Active Directory security group that will be used for e-Commerce system admins.
  • The Microsoft Azure Active Directory security group that will be used for ratings and reviews moderators.
  • The domains that will be associated with the environment.

In addition, you can collect the following optional information:

  • Azure AD business-to-consumer (B2C) information:

    • Tenant Name.
    • Client ID.
    • Login Custom Domain.
    • Reply URL.
    • SignUp SignIn Policy ID.
    • Reset password Policy ID.
    • Edit Profile Policy ID.

[!NOTE] This information can be added later, through a service request.

After you've collected the required information, follow these steps to initialize e-Commerce.

  1. Sign in to LCS.
  2. Open the project that contains the environment where you want to initialize e-Commerce.
  3. In the Environments section, select the environment.
  4. Under Environment features, select the Retail manage link.
  5. On the e-Commerce tab, select Setup. A dialog box appears, where you must enter the information that is required for provisioning.
  6. Fill in the required information, and then go to the next page.
  7. On the next page, fill in the required information, and then submit the form. You're returned to the e-Commerce tab, where you should see that initialization has been started.
  8. To view the initialization status, either Refresh or return to the e-Commerce tab later.

When e-Commerce is initialized from LCS, the system provisions several components that are required for e-Commerce and associates them with the environment. After provisioning is complete, the e-Commerce tab on the Retail management page is updated to reflect the provisioning. The page shows the latest customization deployments and the status of any other ongoing deployments. It also includes links to the e-Commerce site and the e-Commerce site builder where sites are authored.

Access site builder

To access site builder, go to the e-Commerce tab on the Retail management page in LCS and select the e-Commerce site management tool link. The site builder landing page displays a tenant-level view. From this page, you can:

  • Modify tenant-level settings.
  • Navigate to any site you have created, and have permission to view.
  • Access Reviews features such as moderation and reporting.
  • Create a new site. For more information about how to create a new site, see Create an e-Commerce site .

Additional resources

Configure your domain name

Create an e-Commerce site

Associate an online site with a channel

Manage robots.txt files

Set up custom pages for user logins

Add support for a content delivery network (CDN)

Enable location-based store detection