ScrutnLearn considers expert contributions that add a specific, reproducible lesson to its Business Central learning path. Acceptance is based on first-hand subject knowledge and reader value, not article length or promotional reach.
Topics We Accept
- Microsoft Dynamics 365 Business Central & AL development
- Dynamics NAV/Navision migration and extension-model lessons
- Business Central finance, sales, purchasing, inventory, projects, service, or manufacturing workflows
- Azure, SQL, .NET, APIs, Power Platform, and DevOps only when the article solves a clear Business Central integration or delivery problem
- Role-specific certification or interview preparation grounded in verifiable product behavior
Submission Guidelines
- Submit original, unpublished work in your own voice. Do not copy or closely rewrite Microsoft Learn, another tutorial, or generated text.
- State the Business Central deployment type, relevant version or runtime, prerequisites, problem, steps, expected result, and important limitations.
- Explain code and configuration choices. A large unexplained code block or a list of definitions is not a tutorial.
- Use a sandbox or test company for evidence. Remove tenant names, customer data, access tokens, license details, certificate numbers, and other private identifiers from examples and screenshots.
- Link product claims to the most relevant Microsoft Learn page. Sources support a claim; they must not be copied.
- Provide a short, accurate author bio and disclose employment, sponsorship, affiliate relationships, products, or clients connected to the topic. Do not send paid-link placements.
- Disclose material use of an AI assistant for outlining, language editing, or code assistance. The named author remains responsible for originality, testing, and accuracy.
Review and Corrections
We screen a proposal for overlap with existing tutorials before requesting a draft. An accepted draft is checked for a distinct search intent, clear authorship, readable steps, source quality, code reasoning, version boundaries, private data, promotional links, and a result that a reader can inspect. We may ask for revisions, edit for clarity and site style, add internal links, or decline material that cannot be verified.
Publication is not an endorsement of an employer or product. Substantial corrections are made on the page; a contributor must tell us if a later product change makes the guidance unsafe or materially inaccurate. ScrutnLearn may update or remove a contribution when it can no longer be responsibly maintained.
How to Submit
Email a topic pitch to [email protected] with the subject line “Guest Post Submission.” Include the problem, intended reader, environment used to verify it, proposed outcome, and links to any relevant work. Do not attach confidential project files. A submission does not guarantee publication or a particular response time.