A consultant is preparing to roll out a new generative AI feature in Dynamics 365 Sales to a 400-seat sales organization. Before enabling the feature tenant-wide, the consultant needs to confirm the organization will not hit avoidable rollout problems in week one. (Select TWO.)
Select all correct answers, then click Submit.
Short Explanation
Before flipping the switch on a new AI feature for a few hundred people at once, there are really only two things that will actually break on day one if you skip them: can the tool see the data it needs, and does the organization have enough fuel in the tank to run it at that scale. If sellers' permissions don't extend to the records the feature reads from, it'll come back empty or broken for a chunk of the team. And if the licensed capacity wasn't sized for four hundred people using it simultaneously, the feature will start failing or throttling within days as usage burns through the allotment. Everything else people worry about before a rollout, like formal certification training or having every customer-facing language covered, might be nice-to-haves for a polished experience, but neither one will actually cause the feature to stop working in week one. The two that matter are data access and capacity, because those are the two things the feature is technically dependent on to function at all.
Full Explanation
The correct answers are A and D. A generative AI feature can only return complete, accurate results if the sellers using it hold security roles with access to the Dataverse tables and fields the feature reads from, so confirming that access before go-live prevents silent failures or incomplete answers in week one. Separately, generative AI features consume message or credit-based capacity, and a 400-seat rollout can exhaust an underprovisioned capacity allotment almost immediately, so confirming licensing capacity matches the planned seat count prevents the feature from failing or throttling for sellers shortly after launch. Option B is incorrect because there is no requirement for sellers to complete a multi-day certification course before using the feature; light onboarding may help adoption, but it is not a technical or licensing prerequisite that would cause week-one failures if skipped. Option C is incorrect because localizing the feature into every customer-facing language is not required for the feature to function correctly for internal sellers, and skipping it would not cause the kind of rollout failure the consultant is trying to avoid. The two real prerequisites here are data access and capacity, both of which directly determine whether the feature works at all once turned on.