About the publication
Editorial standards and corrections
Policy revised October 1, 2026
Sentinel Identity publishes explanations and troubleshooting material for Microsoft identity administrators. The value of an article should come from helping a reader understand a problem, evaluate evidence, or complete a task. An article’s length, publishing date, or confident tone does not establish its accuracy.
Sources and interpretation
Use linked Microsoft documentation, specifications, and product announcements to check product claims. Editorial recommendations should be distinguishable from documented requirements. Links provide a way to inspect a claim; they do not mean Microsoft has reviewed or endorsed this site.
Some older articles need further source and technical review. We do not represent the entire archive as independently verified. Where behaviour depends on licensing, release stage, platform, or tenant configuration, confirm those conditions before using the guidance.
AI assistance
AI tools are used in drafting, editing, coding, and maintaining this site. An article’s byline identifies editorial responsibility; it does not mean every sentence or illustration was created without AI assistance. AI output and generated examples can contain errors.
Our previous policy made blanket claims that every technical statement had been human-verified, every command had been run, and every diagram was human-produced. We have removed those claims because a site-wide statement is not a substitute for evidence attached to the work.
Examples and testing
Treat code, tenant names, sample output, and scenarios as illustrative unless the article explicitly documents a test. A first-hand test report should identify its date, environment, relevant versions, method, observed result, and limitations. Source review and execution in a real environment are different checks.
Do not assume a command is safe for your tenant just because it appears in an article. Review its scope, required permissions, expected result, and rollback before using it. Never paste credentials or sensitive tenant data into public feedback.
Corrections and dates
Publication dates identify when a page was first published. A material correction should retain that date, add an updated date, and explain what changed near the beginning of the article. A recent date does not imply every statement was retested.
The October 2026 review corrected the Permissions Management article, which had recommended a retired product, and the Active Directory site-assignment article. Their correction notes describe the changes.
Send an error report through the contact page. Include the article URL, the disputed statement, and supporting documentation or redacted evidence. Reports help prioritise further review.
Commercial interests
Consulting offers and affiliate links are commercial material. Affiliate articles should disclose that relationship clearly. Payment must not be presented as evidence that a technical recommendation is sound. Read the affiliate disclosure for details.
The free administrator workbench is available without purchase or newsletter registration. Advertising approval is decided by the advertising provider; this policy does not imply approval.
Who is responsible
Articles use the byline MU.A. Sentinel Identity is independent of Microsoft. Editorial questions and corrections can be sent to info@sentinelidentity.ca.