Plan end-user communications and training
Use Change Readiness and communication tags to turn relevant Microsoft changes into an agreed user communications plan.
Applies to: Dataverse-based ChangePilot Enterprise with Change Readiness available in your installed release.
Who this is for: communications and training leads working with service owners. You need access to the relevant items; editing tags and notes requires the appropriate permissions.
1. Identify relevant upcoming changes
Open Dashboards & Reports > Change Readiness. Set the product-category and user-impact filters, then choose the next 30, 60 or 90 days. The page includes open items with a user impact rating and a Standard Start within the chosen window.
Use impact to prioritise your assessment. Low or medium impact can still merit communication for a particular audience; high impact does not automatically mean every user needs an email.
2. Agree the audience and response
Open the MCID and check the summary, Microsoft source and rollout dates with the service owner. Confirm which users are affected, whether the feature is enabled or relevant to your tenant, and what people need to know or do.
Record a short note covering the audience, proposed channel, message or training need, accountable person and timing. Separate confirmed tenant behaviour from assumptions that still need testing.
3. Flag the item for communications
Add the End User Communication tag to the item. Return to Change Readiness and select Refresh. The tagged item appears in the End User Communication section when it also matches the current category, impact and timeframe filters.
The tag flags the work. Adding it does not by itself send a newsletter, create training or assign an action. Record the work and owner through your organisation’s agreed process.
4. Coordinate the delivery
Agree wording with the service owner before publication. Choose a channel appropriate to the change, such as an intranet update, targeted message, service-desk briefing or short training item.
Bring cross-team decisions to the internal change meeting. If you use your organisation’s own drafting tools, check their output against the Microsoft source, tenant settings and policy before publication.
5. Keep the plan current
During the weekly review, check What’s Changed for moved dates or rewritten posts. Adjust planned communications when those updates affect your audience or instructions.
After delivery, record the outcome and any remaining work. Follow the agreed item status and closure process with the service owner.
Share a readiness summary
Create report on Change Readiness downloads a PDF summary for the current filters, covering counters and breakdowns by product category and Standard Start month. It does not include individual items. Use the underlying item records for action tracking and detailed handover.
If a tagged item does not appear
Check that it is open, has a user impact rating and a Standard Start inside the selected window. Clear category and impact filters, refresh the page and check your access. An item without a start date or outside the window will need separate review in the item list.
See Change Readiness for the full page reference and troubleshooting if the issue remains.
The communications lead can also use the User Impact Report described in Roles and Automated Emails. The email and dashboard have their own scopes and timing.
Documentation reviewed: 12 November 2026.