Skip to main content

Run a weekly Microsoft change review

Use this routine to produce a short, actionable change review each week. The output is a list of relevant changes with a named owner, a next step and a date for checking progress.

Written by Tom Arbuthnot

Use this routine to produce a short, actionable change review each week. The output is a list of relevant changes with a named owner, a next step and a date for checking progress.

Prepare your scope

Agree which services you own and who represents IT operations, adoption and the service desk. Confirm whether Message Center shows standard or connected-tenant data. Views, bookmarks and labels are now account-backed, but actual ownership, deadlines and completion belong in your team work tracker.

Review operational priorities

  1. Open Message Center → New Items and choose the period since your last review.

  2. Filter to your services. Read relevant items rather than relying only on titles.

  3. Check Actionable and High Admin Impact for configuration changes, retirements and preparation work.

  4. Review Upcoming to find changes approaching rollout.

  5. Check My Items → Watching → Recent activity for updates to items already under review.

New Items alone is not a complete change review: an older announcement can acquire a new deadline or revised instructions.

Review user and roadmap impact

Use High User Impact to identify changes that need communications, training or service-desk preparation. Then review Microsoft 365 Roadmap and Azure Updates for upcoming capabilities and date changes relevant to your planning.

Record a decision for each relevant item

A useful review entry contains:

  • The source, item ID and ChangePilot link.

  • What changes and which users or services are affected.

  • The Microsoft rollout window or action deadline, where provided.

  • Your decision: investigate, prepare, communicate, monitor or no action.

  • A named owner, a next step and a review date.

For example: “Teams meeting experience update — adoption lead to review the Microsoft message, update the organiser guide and check the rollout date at next week's review.” This is a process example, not a claim about a specific announcement.

Finish with a short briefing

Share the few items requiring a decision or action. Link to the underlying records so colleagues can inspect the source and latest dates. Add selected items to Watching, save useful filtered-feed URLs, and check any uncertain dates in the Microsoft message before committing to a rollout communication.

Related guides

Did this answer your question?