How we write and check guides, step by step.

Every guide on LowCodeStacks goes through the same five steps before you see it, and lists the sources it was checked against.

1. Start from real problems

We read public community questions that have an accepted answer, and Microsoft's own troubleshooting pages, to learn what people struggle with right now. We only read them: we never copy anyone's text or name the people who posted.

2. Check every fact against Microsoft Learn

Limits, settings, error codes and dates are checked against Microsoft's official documentation. Each guide lists its sources, and guides checked since launch show the date they were checked. When Microsoft's own pages disagree, the guide says so.

3. Write it in our own words

Guides are original and in plain English. Drafts are written with the help of AI, then fact-checked line by line. When we've tried something ourselves, the guide says "Tested by us".

4. A person reviews it before it's published

Nothing is published automatically. Every guide is reviewed and published by the LowCodeStacks team.

5. Keep it current

When Microsoft changes something, we re-check the guides it affects and update the date. If you spot something that changed, email contact@lowcodestacks.com and we'll check it.

What we never do

• Claim Microsoft endorses, certifies or approves anything. We're independent.
• Copy text from Microsoft, forums or other sites.
• Use Microsoft's product logos.
• Publish a guide without its sources.

Found a mistake? Email contact@lowcodestacks.com and we'll re-check it.