How I Built a Chat-Triggered ChatOps Pipeline Using Teams, Logic Apps & AWX

Ram — Tue, 24 Jun 2025 10:37:45 +0000

When I set out to build a chat-triggered automation pipeline, I had one goal: make infrastructure operations as easy as sending a Teams message. I explored licensed tools like Power Automate and Copilot Studio — but due to organizational constraints, I needed to pivot.

What came out of that constraint is now one of the most scalable, cost-efficient patterns I’ve implemented: a GitOps-powered, Teams-triggered automation fabric backed by Logic Apps and AWX. Here’s how I made it happen.

I wanted a solution that would let my team:

Trigger infrastructure jobs (like power cycling a VM)
Use Microsoft Teams as the front door
Avoid manual YAML edits or AWX logins
Maintain a strong audit trail with Git

But...

Power Automate - Required additional licensing
*Copilot Studio *- Locked behind paid tiers

The Architecture I Built
I leaned on services already approved within my organization — Teams, Azure Logic Apps, Azure DevOps, and AWX.

Here’s the flow I designed:

Teams Message → Logic App (API Push) → Git Repo (YAML Update) → Azure DevOps Pipeline → AWX Job Execution

What I Gained
Zero-touch cloud automation triggered by chat
Auditability and traceability using Git commits
Secure, collaborative workflows with no direct infra access needed
No extra cost — all tools approved and within license
Easy extensibility — add new jobs by updating config paths

Final Thoughts
I didn’t build this because I couldn’t get a license — I built it because I wanted more control, traceability, and simplicity. The result? A resilient, Git-native automation framework that feels as modern as it is practical.

If you’re facing tooling constraints or want to avoid adding overhead to your ops stack, know this: Sometimes, building your own solution is the most powerful path forward.

DEV Community: Ram

How I Built a Chat-Triggered ChatOps Pipeline Using Teams, Logic Apps & AWX