COMMUNITY
Practitioners answering practitioners
The people who run cloud and AI in production know things no announcement covers. This is where we share it: the limit you hit, the pattern that worked, the decision you are still weighing.
Ways to take part
Propose an article
Write Field Notes, a Deep Dive or an Open Question about what you actually operate.
Report an error
Spotted something inaccurate or out of date? Corrections are made in place, with the source.
Comment on an article
Add what worked, or what did not, in your environment in the comments under any article.
Get new articles by email
Each new article arrives in your inbox when it publishes. Every email has an unsubscribe link.
Community guidelines
How we keep discussions useful, sourced and respectful, and how to report a problem privately.
Your first week here
- Read the articles for the pillar you work in.
- Subscribe to get each new article by email when it publishes.
- Comment on an article with what worked, or what did not, in your environment.
- Propose an article about something you build, run or fix.
Ground rules
- Stay vendor-neutral and assume good faith.
- Source your claims. A link to documentation beats a confident opinion.
- Disclose your employer when discussing its products.
- No sales pitches, recruiting posts or lead generation.
- Never post customer data, credentials, tenant or account IDs, or anything under NDA.
The full Code of Conduct applies in comments and in every azCloudOps community space.
A note from Manoj
I started azCloudOps as my own journal of what I am learning about enterprise AI and cloud operations. It only becomes useful when other people bring what they know. I read every proposal and every correction. If you want to help shape the community as it grows, say so in the proposal form.