Deploying Dynamics 365 Sales Hub in Power Platform Sandbox
Short answer
CD Assign a Dynamics 365 Sales enterprise license to the administrator and add Dataverse while enabling Dynamics 365 apps in the sandbox environment.
Question
An administrator creates a Power Platform environment with the following configuration:
The environment does not have a database.
The environment is a sandbox environment.
Access to the environment is restricted to a security group.
The administrator has the System Administrator role.
You need to ensure that the administrator can deploy Dynamics 365 Sales.
Which two actions should you perform? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.
Key Takeaways
Deployment requires both technical provisioning (Dataverse + Apps) and user entitlements (Sales License); missing either prevents successful installation.
Learn how to deploy Dynamics 365 Sales Hub by assigning licenses and configuring Dataverse in a Power Platform sandbox environment.
Common mistake: Enabling server-side synchronization (E) is often mistaken as a deployment requirement, but it is only needed for email integration, not for installing the core Sales Hub app.
Expert Analysis
To deploy Dynamics 365 Sales Hub, the underlying infrastructure must support both data storage and the application layer. First, Dataverse is mandatory; a Power Platform environment without a database cannot host Dynamics 365 apps. Therefore, adding Dataverse and enabling Dynamics 365 apps is a required step.
Second, licensing is strictly enforced at the user level. Even with the System Administrator role, a user cannot activate or use Dynamics 365 Sales features without a valid Dynamics 365 Sales Enterprise license. Assigning this license ensures the administrator has the entitlement to provision and access the app.
The most attractive but wrong answer often involves removing security restrictions (Option A) or enabling server-side synchronization (Option E). Removing the security group restriction is incorrect because sandbox environments are designed for isolation; restricting access via security groups is a best practice and not a blocker for deployment. Server-side synchronization (Option E) is related to email integration, which is optional and not required for the initial deployment of the Sales Hub app itself.
Community comments correctly identify C and D as the necessary steps. They emphasize that licensing (C) provides the entitlement, while enabling Dataverse with apps (D) provides the technical foundation. Options A and B are distractors: creating a new environment (B) is unnecessary if you can configure the existing one, and removing security (A) violates governance principles.
Exam Strategy
When asked about deploying or enabling a specific Dynamics 365 app, always check two layers: the platform configuration (e.g., Dataverse presence and app enablement flags) and the user licensing model. Do not confuse feature-specific configurations like email sync with core deployment prerequisites. Review the official prerequisites for each app to distinguish between 'required for install' and 'optional for functionality'.
Frequently Asked Questions
Can I deploy Dynamics 365 Sales without a Dataverse database?
Does the System Administrator role include Dynamics 365 Sales access?
Discussion 1 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 1
-
Evincible 👍 1Explanation C. Assign a Dynamics 365 Sales Enterprise license - A valid Dynamics 365 license entitlement is required to enable Dynamics 365 apps during database provisioning. D. Add Dataverse and enable Dynamics 365 apps - Dynamics 365 Sales requires a Dataverse database. When provisioning the database, select Enable Dynamics 365 apps = Yes. Why the other options are incorrect - A. Remove security group restriction: Not necessary. Dynamics 365 Sales supports environments restricted to security groups. - B. Create a new environment: Not necessary because Dataverse can be added to the existing sandbox environment. - E. Enable server-side synchronization: Used for email integration, not Sales deployment.
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All AB-210 Questions
Access 100 questions with complete answers and detailed explanations.
View Full AB-210 Practice Test →