What we publish

Format	Length	What makes it work
Field Notes	800 to 1,500 words	Something you built, migrated or fixed, with what you would do differently
Deep Dive	1,500 to 3,000 words	One topic, primary sources, a diagram, an action checklist
Open Question	600 to 1,000 words	A position on where things are heading, argued with evidence and open for discussion in the comments
Glossary entry	150 to 300 words	A precise, sourced definition of one term

How it works

1. Propose. Use the form below. A title, a three-bullet outline and your sources are enough.
2. Triage. The editor reviews each proposal and replies with one of three outcomes: accepted, accepted with changes, or not a fit this time, with the reason.
3. Draft. Accepted writers get a contributor account on this site. You write in the editor and press Submit for Review when ready.
4. Review. We check every product claim against its source, add verification flags, and suggest edits. You approve the final version.
5. Publish. Articles go live with your name and bio, open for comments, and are sent to email subscribers.

Writer guide

• Open with the point. The first two sentences say what changed and why it matters to an operator.
• Link the primary source for every product claim, and note the date you checked it.
• Mark preview features as preview, and label anything forward-looking as analysis.
• End with an action section: what a team should do this quarter.
• Strip anything confidential: customer names, tenant or account IDs, internal hostnames, credentials.
• Disclose your employer if you write about its products. Vendor employees are welcome; vendor marketing is not.
• Your work stays yours. You grant azCloudOps.org the right to publish and keep it online, and you can republish it anywhere with a link back.

Propose an article

A working title, a three-bullet outline and your primary sources are enough to start. Required fields are marked.

Privacy: what you send is used only to review your proposal and reply to you. Submissions go to the editor, are not published, and are screened for spam.

Report an error or suggest a topic

Found something inaccurate or out of date, or want a topic covered? Tell the editor here. Corrections are made in place and the article’s last-verified date is updated.

Privacy: leave your email only if you want a reply. Submissions go to the editor, are not published, and are screened for spam.