Document control
Legal & about
We write runbooks for a living, so this page is shaped like one. Everything a reader might reasonably want to audit about this site — who writes it, how it's funded, how facts get checked, what we collect — stated in sections, with the uncomfortable parts included rather than buried.
| Item | Status |
|---|---|
| Publisher | RolloutDesk, an independent site. Not affiliated with, endorsed by, or operated by any vendor named on it. |
| Authorship | A small team, writing under a team byline |
| Funding | Affiliate commission on some outbound links, labeled inline |
| Vendor editorial input | None. No vendor sees drafts or reviews copy. |
| Sponsored placements | None accepted |
| Fact verification | Against vendor documentation, with the date printed on the page |
1. Who writes this
A small team with backgrounds on the shipping side of IT — packaging installers, arguing with change advisory boards, and watching well-chosen software die because nobody planned the deployment. We publish under a team byline rather than inventing individual authors with photographs and fabricated credentials, which is a thing that happens on sites like this one and which we would rather not do.
What that costs you: you can't evaluate an individual author's track record. What it buys you: nobody on this site is a fictional person, and no claim here is propped up by an expertise we made up. If a page states something as fact, it's because vendor documentation says so and we've dated the check.
2. How the site makes money
Affiliate commission. If your organization clicks through to a vendor from here and subsequently buys, we may be paid a commission by that vendor. It costs you nothing and it does not change the price you pay.
The rules we hold ourselves to, which are the only part of this section that actually matters:
- Every commercial link is labeled where it appears, inline, in plain language — not once at the bottom of the page in grey text.
- Commercial links carry
rel="sponsored nofollow"and route through a/go/path so they are trivially identifiable. - We recommend things that pay us nothing, prominently and first. The built-in Microsoft and Zoom administrative levers are free, already licensed, and get the opening section of the main playbook because they should. There is no affiliate relationship between this site and Microsoft or Zoom.
- We tell you when not to buy. The seat-math page argues for fewer seats than most vendors would like and names the tier gap that turns a sticker price into a sales call. That is deliberate and it stays.
- No sponsored posts, no paid reviews, no vendor-supplied copy. Nothing on this site has been written, edited, or approved by a vendor.
3. How facts get verified
Prices, plan tiers, policy parameter names and installer behaviour are checked against the vendor's own current documentation before publication, and the date of that check is printed on the page — usually in the byline, and always next to the specific claim when the claim is fragile.
Vendor documentation drifts. Policy panes get reorganised; installer parameters move between releases; pricing pages change without announcement. A dated page is our way of telling you how much trust the specifics deserve. Before you make a change that depends on an exact parameter name or price, re-verify it against the vendor's documentation. That's not us disclaiming responsibility — it's the same advice we'd give about any third-party documentation, including our own.
We publish no performance benchmarks. Any claim about how a tool performs on a fleet would have to be measured on that fleet, which is why every page that touches the question sends you to measure it yourself in ring 0 rather than quoting a number we could not honestly produce.
4. Corrections
If something here is wrong — a parameter that changed, a price that moved, a claim that was never right — we want to fix it rather than defend it. Corrections are made in place, and where a correction changes the substance of a recommendation we note it on the page rather than quietly editing.
5. Privacy
This is a static site. There are no accounts, no comment system, no newsletter, and no forms — so there is nothing here for you to submit and nothing for us to store about you directly.
- Analytics. Page-view counts from our CDN, Cloudflare, show which runbooks get used. They set no analytics cookies. It is aggregate traffic measurement, not an attempt to identify you.
- Affiliate tracking. Clicking a labeled commercial link hands you off to the vendor, who may set a cookie to attribute a later purchase. That happens on the vendor's side, under the vendor's policy.
- Hosting logs. Standard server logs, as every website on the internet has.
- What we don't do: sell data, build advertising profiles, run third-party ad networks, or embed social trackers. No fonts or scripts are loaded from third-party domains — the typefaces this site uses are served from our own server for exactly that reason.
6. Trademarks
Krisp, Microsoft, Microsoft Teams, Intune, Zoom, Apple, macOS, Jamf and every other product or company named on this site are trademarks of their respective owners. They are used here descriptively, to identify the software being discussed. No affiliation, sponsorship or endorsement is claimed or implied by any of them.
7. No warranty, and what that means practically
This site is published for information. It is not consulting, and it is not a substitute for your own testing in your own environment. Commands, registry paths, policy parameters and packaging steps are given as they are documented by their vendors at the date shown — but your estate has details we don't know about.
So: test in a lab, stage in rings, keep the rollback warm. That is the advice of every page here and it applies to the pages themselves. To the fullest extent permitted by law, we accept no liability for loss or damage arising from actions taken on the basis of this site's content. You own your change window.
8. Contact
Corrections, factual disputes and “this parameter moved in the latest release” notes are the correspondence we most want. Vendor pitches, guest-post offers, link-insertion requests and sponsored-content proposals are declined automatically and without reply — stating that here saves everyone the exchange.
Back to the front page, the company-wide playbook, or The Change Window.