Monitor Microsoft M365 service changes

[schrolla]

💡 Summary

Determine where and how Microsoft disseminates both service and API level changes to M365 services. Collect and find a way to detect announcements of upcoming changes quickly to feed into a change evaluation process.

Motivation and context

ScubaGear is only useful if it accurately assesses M365 services. As cloud services and their feature evolve rapidly and APIs change, ScubaGear will need to be updated to keep pace. Therefore, monitoring upcoming service changes through announcements is important to be able to anticipate and evaluate changes before they happen.

Implementation notes

Developing a monitoring solution for changes includes:

• Research and discuss current mechanisms for staying abreast of service changes
• Determine how to monitor service and feature level changes
• Determine best way to monitor API level changes
• Automate, to the extent possible, notification of new changes to project tech leads

Acceptance criteria

How do we know when this work is done?

• [ ] Project staff are made aware of upcoming changes in a timely manner

[schrolla]

Retain and potentially split into smaller chunks for iterative refinement torwards automated process.