Editorial policy
How guides on this site are written, dated, corrected, and kept current — and what the site will and won't do for money.
What a guide is
Every guide states a position and gives a recommendation. It is not Microsoft documentation, and it doesn’t try to be exhaustive the way Microsoft Learn is — it exists to answer “which of these options applies to my situation, and why”, which official documentation is deliberately neutral about. Where a Further reading block points to Microsoft Learn or the product documentation, that’s the authoritative source for the exact, current mechanics; the guide is one consultant’s reading of how to apply them.
Dates and what they mean
Every guide carries a publication date and, when it has been revisited since, a review date shown as “Reviewed <date>” next to the publish date. A review means the guide was read again against the current state of the product and adjusted if anything had changed — a new licensing tier, a renamed feature, a retired capability. A guide with no review date hasn’t needed one yet, not that it’s been forgotten; Microsoft 365 changes at very different speeds across its surface area, and a guide to something structurally stable (what a distribution list is) ages slower than one to something Microsoft actively ships features into every quarter (Copilot, for instance).
Corrections vs routine updates
Not every change to a guide is a correction. Most updates are routine refreshes — a new feature added to an existing explanation, a section expanded, a link fixed. A correction is specifically a case where something the guide said was factually wrong and has been fixed. Corrections are tracked separately in the changelog via a corrections:entry on the guide itself, distinct from the ordinary review-date bump — so a reader can tell the difference between “this was kept current” and “this was wrong and is now fixed”.
Sources
Where a guide makes a specific, checkable factual claim — a licensing limit, a default value, a retirement date — the goal is for that claim to trace back to a primary source, surfaced in a Sourcesblock on the guide itself when one is attached. Sources are being added guide by guide rather than all at once; their absence on an older guide doesn’t mean the claim is unverified, only that the explicit citation hasn’t been added yet.
What doesn’t happen here
- No sponsored guides, and no paid placement in comparisons or recommendations.
- No affiliate links that would change which product a guide recommends.
- No content generated purely to target a keyword with nothing new to say — every guide exists because a real question needed a direct answer.
Reporting an error
If something here is wrong, out of date, or missing, the contact form reaches the author directly, and corrections get priority over everything else in the queue.