An admin managing Dynamics 365 Sales for an 800-seat organization notices that Copilot-powered features begin failing intermittently for sellers near the end of each month. Investigation shows the tenant's allotted AI message or credit capacity is being exhausted before the monthly reset. A consultant is asked to prevent this from recurring.
Select an answer to reveal the explanation.
Short Explanation
When an AI feature starts failing right before the calendar flips to a new month, that pattern is a big clue, it smells like something running out of a monthly allotment, not a random glitch. Here that's exactly what's happening, the pool of AI capacity the tenant is licensed for is getting used up before the reset comes around, so the fix has to be sizing that pool to match how much the eight hundred sellers actually use. Cutting off sellers' access to the CRM entirely is a wildly disproportionate move that solves nothing about capacity and just breaks their ability to do their job. Running nightly database maintenance tunes how fast queries run, which has nothing to do with how much AI usage capacity is available. And switching people from a browser to a mobile app changes where they click, not how much AI capacity their usage draws down. The failure pattern points straight at a licensing and provisioning gap, so that's the only fix that actually touches the cause.
Full Explanation
The correct answer is A. The root cause identified in the investigation is that AI message or credit capacity is running out before the monthly reset, so the direct fix is tracking actual consumption trends and scaling the provisioned Copilot capacity licensing to match real usage at 800 seats, which prevents the shortfall from recurring. Option B is incorrect because removing Dynamics 365 Sales access from sellers takes away their ability to use the core CRM system entirely, a disproportionate and disruptive step that does not address the underlying capacity shortfall and breaks unrelated functionality. Option C is incorrect because nightly database maintenance and index optimization improve Dataverse query performance, not AI message or credit capacity, so it would not touch the actual bottleneck causing the failures. Option D is incorrect because the client sellers use, web or mobile, has no bearing on how much AI capacity their Copilot usage consumes; switching clients would not reduce consumption or prevent the monthly exhaustion. Diagnosing this correctly requires recognizing that intermittent end-of-month AI failures tied to capacity exhaustion are a licensing and provisioning issue, not a performance, access, or client issue.