I'm a Cloud Solutions & Automation Engineer at Vinebrook Technology and the founder of OsbornePro LLC.

I work across the boundaries of infrastructure, cloud, security, networking, identity, development, and automation. My career has taken me across the technology stack. From administering and troubleshooting systems to engineering automation and designing solutions that span infrastructure, cloud, networking, identity, security, and software.

That breadth has shaped how I approach engineering today: understand the whole system, automate what should be automated, secure it by design, and build solutions that someone can actually operate and maintain.

A lot of what you'll find here is the result of that philosophy-tools, scripts, security projects, experiments, and solutions built while figuring out how things really work.

My work tends to live where systems, security, automation, and architecture intersect.

🔹 Cloud & Hybrid Infrastructure - Designing, integrating, automating, and troubleshooting infrastructure across cloud and on-premises environments.

🔹 Automation Engineering - Turning repetitive or error-prone operations into reliable tooling, scripts, workflows, and reusable processes.

🔹 Security Engineering - Working with identity, authentication, PKI, encryption, secure protocols, hardening, and security-conscious design.

🔹 Systems & Networking - Troubleshooting across operating systems, applications, networks, identity, and infrastructure rather than stopping at the boundary of a single technology.

🔹 Architecture & Technical Strategy - Evaluating technologies, understanding constraints and tradeoffs, and turning technical and operational requirements into practical solutions.

🔹 Development & Tooling - Building software and utilities when an off-the-shelf solution doesn't solve the problem—or when there's a better way to automate it.

I like solving the problems that don't fit neatly into one technology stack.

Code can show what someone built. I'm equally interested in documenting why it was built that way.

At OsbornePro.com, I publish technical articles and case studies covering the engineering behind real-world solutions.

I focus on the parts that often get left out of technical tutorials: architecture decisions, constraints, security implications, tradeoffs, automation, failure modes, and long-term maintainability.

Problem: Rapid MSP growth created a need to systematically translate client SOW obligations into recurring, verifiable operational work. The platform needed to ensure contractual responsibilities were understood and performed, provide evidence of completion, manage recurring service and access-verification tasks, incorporate new clients into established operational workflows, account for staffing conflicts during maintenance windows, and identify work that fell outside contracted scope.

Approach: Architected a centralized operations and assurance platform that converts client obligations and operational requirements into structured, trackable workflows for the engineering team. A Power Apps interface provides administrators with a centralized work queue, while Power Automate and SharePoint coordinate recurring tasks, onboarding workflows, maintenance activities, access verification, patching obligations, evidence collection, and management escalation.

The platform also incorporates AI-assisted review of out-of-band client project requests submitted through Microsoft Forms, helping determine whether requested work aligns with the client's SOW or requires separate billing and review.

The supporting Azure architecture uses Functions and Storage Queues for backend processing, Key Vault for third-party API secrets, Managed Identities where supported to reduce credential exposure, and Azure Monitor and Log Analytics for application monitoring, alerting, and troubleshooting.

Key areas: Solution Architecture · Operational Governance · Automation · Power Platform · Azure · Security · Identity · Observability

Read the Operations & Assurance Platform Case Study →

Problem: Patch governance across an MSP required administrators to repeatedly perform the same research for each client-reviewing known issues, identifying applicable KBs by operating system, correlating security advisories, and gathering vendor-specific vulnerability information. This duplicated effort across the organization and made consistent patching decisions more difficult.

Approach: Designed a centralized, tool-agnostic patch governance platform using SharePoint and automation to aggregate patching and security intelligence into a single operational resource. The platform collects information from Microsoft Graph, MSRC, Red Hat, Ubuntu, Action1, BleepingComputer, Palo Alto Networks, and other vendor and security feeds. A scheduled automation correlates the latest known issues, security advisories, and patch information and generates an interactive HTML report every Patch Tuesday, which is published to SharePoint for the engineering team.

Administrators can then work from a common intelligence source and filter the information according to each client's environment and requirements, instead of independently repeating the same research for every customer.

Key areas: Solution Architecture · Patch Governance · Security · Automation · Microsoft Graph · SharePoint · API Integration

Read the Patch Governance Platform Case Study →

Problem: Gain visibility into SPF and DKIM authentication failures and provide the insight needed to safely progress toward a p=reject DMARC policy, while minimizing deployment time, operational complexity, and cost. The solution also needed to be repeatable, allowing an MSP to efficiently deploy the platform across multiple client environments.

Approach: Designed an Azure-based DMARC analytics platform and automated its deployment using Bicep and Power Automate. The solution combines report ingestion, storage, SQL-based processing, and Grafana visualization to turn DMARC aggregate reports into actionable authentication data.

Key areas: Solution Architecture · Azure · Infrastructure as Code · Automation · DMARC · DKIM · SPF

Read the DMARC Analytics Platform Case Study →

I build and maintain tooling around infrastructure, automation, administration, and security.

Many of my projects start with a simple question:

"Why am I doing this manually?"

...and occasionally:

"Why doesn't a tool for this already exist?" 😄

A secure secret-delivery system designed to move sensitive values from a mobile device to a desktop without turning the desktop into another long-term secret store.

NovaKey addresses a problem that sits between traditional password managers and everyday workflows: how do you securely deliver a secret to the system where it's needed while minimizing unnecessary handling and exposure?

Rather than functioning as another password manager, NovaKey focuses on the secure delivery and controlled use of secrets between devices. It provides a purpose-built workflow for getting credentials and other sensitive values from a trusted mobile device into desktop workflows when they're needed.

The project explores the kind of security problem I find particularly interesting: designing around trust boundaries, minimizing secret exposure, and making secure behavior practical enough to use every day.

A modern command-line replacement for the traditional whois utility.

As RDAP replaced WHOIS as the standardized protocol for domain and IP registration data, there wasn't a natural command-line successor to the familiar whois workflow. I built RDAP-CLI to fill that gap—providing a practical CLI for querying modern RDAP services while preserving the simplicity administrators and engineers expect from a command-line utility.

This is the kind of project I enjoy building: identify a gap, understand the underlying standards and protocols, and create tooling that makes the technology practical to use.

One of my original security-focused projects, built to make strong file encryption accessible and practical. EncrypIT is still available through SourceForge.

An endpoint security and administration toolkit I developed before modern EDR platforms became commonplace. BTPS-SecPack brought together security tooling and administrative capabilities to help protect and manage Windows environments.

PowerShell has been one of my primary tools for turning systems administration into engineering. I build and publish reusable modules and tooling designed to automate operations, standardize processes, and solve real-world infrastructure problems.

These are some of the technologies I regularly use to build, automate, troubleshoot, and secure systems.

C#	PowerShell	Bash	.NET	Ansible
JavaScript	Git	YAML	VS Code	Automation ⚙️

I also run the OsbornePro YouTube channel, where I break down technologies, security concepts, infrastructure, automation, and secure protocols.

The channel originally started as a way for me to demonstrate hands-on technical knowledge and share what I'd learned as an administrator and engineer. Today, it's another part of the larger OsbornePro technical library.

My goal has always been to go beyond surface-level "click here, run this command" tutorials.

I want someone watching to understand how the technology works, why we're configuring it this way, what can go wrong, and how to build it securely and maintainably.

If detailed walkthroughs and getting into the weeds sounds like your kind of thing, come join the community.

Security has always been an important part of how I approach infrastructure and engineering.

I also spend time breaking things on purpose. 😉

My security work and labs have included offensive and defensive security concepts, Hack The Box challenges, security tooling, protocol analysis, and documenting the techniques I've learned along the way.

Technology changes constantly. Continuing to learn isn't optional in this field.

My certifications and professional credentials are available through Credly:

Because serious engineering and shiny internet trophies don't have to be mutually exclusive. 😎

rosborne@osbornepro.com

"Automate the boring stuff. Understand the complicated stuff. Secure all of it."