We work on Azure, Microsoft 365, and Windows Server — mostly the parts that are not glamorous. Identity, security, migration, disaster recovery. The things that need to keep working always.
The engineers who design your system are the engineers who deploy it, and the engineers you call six months later when something breaks. There is no second tier behind us. There is no first tier in front of us. It is just us.
We use Microsoft's own playbooks — the Cloud Adoption Framework, the Well-Architected Framework, the Zero Trust deployment plan. They are not perfect, but they are well thought out, and rewriting them rarely turns out better.
We move slowly on purpose. Most cloud problems we see started as a faster decision somewhere upstream. We would rather take an extra two weeks at the start than spend six months later untangling what was rushed.
A selection of project-based engagements. We also do custom work that doesn't fit a template. If what you need isn't listed, write to us.
Most customers don't stop at the project. When the work is in production, they stay with us for ongoing operations — monitoring, incident response, change management, regular Microsoft Cloud reviews. Same engineers who built the system, same standards, just at a different pace.
We use HaloPSA for tickets, change records, and reporting. Every customer gets their own client portal — visible at the top of this page. Existing customers know where to find us. New customers can ask about how managed services would look for their environment.
We write about the work, occasionally. Notes from real engagements — what worked, what didn't, what we'd do differently. It lives at medium.com/inthecloud.
If you are an experienced Microsoft engineer and the way we describe the work sounds like the way you want to work — write to us at careers@inthecloud.co.th.
If you are a customer thinking about an engagement, the contact details are below. We usually reply the same day.