Editorial policy

Who writes this

Every guide is written by Emil Björk, Microsoft business apps consultant, Gothenburg. There is no editorial team, no freelance pool, and no ghost-written content — one person is accountable for every page. See the About page for background.

What "written from hands-on work" means

Guides are drafted from direct experience with the product being described, then checked against Microsoft's own documentation, release notes, and (for licensing and pricing pages) published price lists. Where a guide states a fact that could change — a price, a limit, a feature's availability — the goal is to state it plainly and date it, not to hedge it into uselessness. Confidence in the writing is not a claim that nothing on the page will ever need updating; it is a commitment to say what is true as of the stated date as clearly as possible.

What a guide's dates mean

Every guide carries a first-publish date and, once it has been substantively revised, an updated date — both shown on the page via the freshness badge. A guide's revision history (where the build environment has git history available) lists the real dates the underlying file was actually edited, separate from that frontmatter narrative.

How sources are cited

Where a guide links to Microsoft Learn or Microsoft Docs, that link is to the specific page or a stable section root the writer actually consulted — never a plausible-looking URL nobody checked. A weekly automated check re-verifies every such link and flags anything that now 404s; a citation that hasn't yet passed that check does not carry the "Microsoft Learn" badge on the page.

Comparisons and competitors

Comparison guides name real competitor products and try to say plainly where the other product wins, not just where Dynamics 365 wins. Nothing on this site is sponsored, and no vendor has paid for or reviewed a comparison before publication.

The republish cadence

Twice a year, around the spring and autumn Dynamics 365 release waves, the product overviews, licensing guides, and comparison pages most likely to be affected are re-read in full and their updated date bumped only when something in the text actually changed — not on a schedule for its own sake.

Corrections

Mistakes happen on a single-author site faster than they get caught. See the corrections page for how to report one and what happens next.