How articles are researched, written, and maintained.

1. Scope and audience

Articles target practising Microsoft identity administrators, Microsoft 365 engineers, SOC analysts, and cloud security architects. The depth assumes familiarity with Microsoft Entra concepts and aims for the level of detail that helps with real production decisions — not introductory overviews.

2. Topic selection

Topics are chosen on three criteria:

• Operational relevance — does this come up in real tenants, real escalations, or real architecture reviews?
• Gap in available public material — is the existing public coverage thin, outdated, or marketing-flavoured?
• Long-shelf-life value — will the article still be useful in 12 to 24 months, or is it a fast-moving preview that we should defer?

3. Sourcing standards

Articles rely on primary sources wherever possible. Claims about Microsoft product behavior, licensing, deprecation timelines, or support boundaries are linked inline to one or more of the following:

• Microsoft Learn documentation.
• Microsoft Entra and Microsoft 365 official blogs and product release notes.
• Microsoft Tech Community posts authored by Microsoft staff.
• RFCs and other IETF / W3C / FIDO Alliance specifications for protocol material.
• Vendor partner documentation when the article concerns a specific integration.

We do not source from anonymous forums for factual claims. Where community sources or our own testing are the only data point, the article says so explicitly.

4. Original content

Articles are written for this site. We do not republish or paraphrase third-party blog posts. Short quotations from Microsoft Learn or RFCs are used with attribution where they materially help the explanation. We never copy substantial sections of another author's work.

5. AI assistance disclosure

We use large language models as drafting and editing aids — for outline review, prose tightening, and catching grammar issues. Every published article is reviewed and edited by a human editor with relevant Microsoft identity experience before publication. Technical claims are verified against primary sources by a human; we do not publish unverified model output, hallucinated references, or fabricated code samples. Diagrams and screenshots are produced by humans.

6. Fact-checking and verification

Before publication we verify:

• All inline links resolve and reference the documentation cited.
• Cmdlet names, parameter syntax, and KQL queries compile and run.
• Conditional Access, MFA, and Authentication Method references match current Entra portal behaviour.
• Quoted error codes (AADSTS, MS-CV, KRB) are accurate to current Microsoft documentation.

7. Update and corrections process

Microsoft Entra moves quickly. Articles include a publication date and, when materially revised, an updated date. Significant updates are summarised at the top of the article.

If you spot an error, an out-of-date claim, or a broken link, please report it via the contact form or email info@sentinelidentity.ca. We aim to acknowledge corrections within two business days and to publish a correction note when one is warranted.

8. Conflicts of interest

Sentinel Identity is independent. We are not paid by Microsoft, third-party identity vendors, or any MSP to write specific articles, recommend specific products, or shape editorial outcomes. If a future article is sponsored or includes paid placement, it will be clearly labelled as such before any article body content.

9. Advertising standards

The site may display advertising through Google AdSense. Ads are independent of editorial — no advertiser previews, reviews, or influences article content. Ads are placed within standard layout zones (header, between body sections, sidebar) and are subject to the AdSense publisher policies. See our Privacy Policy and Cookie Notice for how advertising data is handled.

10. Reader feedback

Each article includes a feedback control to flag whether it was useful or not. We use that signal — alongside direct messages — to decide what to expand, rewrite, or retire. Feedback is anonymous.

11. Comments and moderation

The site does not currently host on-article comments. Discussion is handled by email so that corrections and edits stay traceable. If comments are added later, this policy will be updated to describe moderation rules.

12. Contact

Editorial questions, corrections, story ideas, or licensing requests: info@sentinelidentity.ca.