Corrections Policy

At OurCloudNetwork, I strive for absolute accuracy in every technical guide, script, and news update published. However, the Microsoft cloud ecosystem moves incredibly fast, and despite testing, mistakes can happen. Interfaces change, PowerShell modules get deprecated, and occasionally, I might just get something wrong.

When errors occur, my priority is to fix them quickly and transparently so you can continue to rely on the information this site provides for managing your environments.

How to Report an Error

If you spot an inaccuracy, a broken script, or outdated information in any article, please let me know. The community is one of the best safety nets for catching things that slip through the cracks.

You can report an error by:

  • Reaching out on Social Media: Send me a direct message or tag me on LinkedIn or Twitter (I am highly active on both).

  • Leaving a Comment: If the article has an active comments section, leave a detailed note explaining what isn’t working.

  • Email: Reach out directly via [email protected].

When reporting an issue, please include the URL of the article and a brief explanation of what you believe is incorrect or outdated.

How Corrections Are Reviewed

Because this is an independent publication run by just me (Daniel Bradley), every correction report is reviewed personally by me.

Once an error is reported, I will:

  1. Verify the claim: I will cross-reference the report against official Microsoft documentation (such as Microsoft Learn or the Message Center).

  2. Test the issue: If the report involves a script or a configuration setting, I will jump into my test tenant to replicate the issue and validate the proposed fix.

  3. Implement the change: Once verified, I will update the article with the correct information as quickly as possible.