Purview Radar
Purview changes fast.
The hard part is knowing what actually changes in practice.
I track Microsoft's roadmap, documentation, releases and licensing and identify the changes that may affect an architecture, a production policy or a recommendation made to a customer.
Free. I publish when there is a change worth paying attention to.
What makes it into the Radar
This is not a copy of the roadmap.
Change
What changed?
A feature, documentation, availability, requirement or licensing change.
Impact
What does it affect?
Architecture, implementation, existing policies or a project decision.
Next step
Do I need to do anything?
Sometimes yes. Sometimes the right action is simply to monitor it. The goal is to distinguish one from the other.
How I analyze changes
How a change becomes a decision
I verify the change at the source, assess where it affects the environment and determine what needs to be reviewed. The recommendation depends on the conditions that apply and the evidence available.
-
01
Change
What changed, where it was documented and how certain the information is.
-
02
Decision
What the change may require you to review.
-
03
Application
Where the condition actually applies in the environment.
-
04
Evidence
What allows you to verify the behavior and expected outcome.
-
05
Adjustment
What needs to change when the evidence does not support the current design.