A university will ship a Dynamics 365 sales copilot change this week and a service copilot change next week, and the two contradict on the same student status. What should the release plan do?
Select an answer to reveal the explanation.
Short Explanation
Two edits to the same sign, posted a week apart, leave the hallway arguing with itself. You release the sales copilot change and the service copilot change together so the student status does not flip halfway through the week. Staggering them asks staff to pick a winner.
Full Explanation
When two copilot changes describe the same student status and contradict, shipping them a week apart creates a stretch where sales and service disagree. The release plan should send the sales copilot change and the service copilot change out together so staff see one consistent status. A week of disagreement is long enough for one student to be told two statuses, and staff will not know which copilot to trust while both are live. Shipping them a week apart and letting staff choose which status to trust leaves the contradiction in production on purpose. Removing the service copilot avoids the clash by deleting a copilot the university still needs, rather than aligning the two changes. Holding both for a month while the contradictory pair remains live extends the bad week into a bad month and still does not decide which status is right. Exam caveat: unrelated sales and service changes can keep their own cadence; these two cannot, because they state the same fact in opposite ways. Operational check: compare the status wording in both changes on one student record in a test environment, and ship only when that record reads the same in both copilots.