Hi, I’m Lloyd —
Systems Support Engineer
I build and operate cloud-native platforms on Azure — from CSP billing tools to containerized web apps — with a bias for automation, clean delivery and cost efficiency.
Lloyd Christian M. Ismael
Cloud engineering, end to end
Systems Support Engineer and Microsoft Cloud Solution Provider (CSP) partner based in Makati City. I design Azure infrastructure, modernize .NET apps, wire CI/CD with Azure DevOps and GitHub, and ship Docker workloads to App Service and VMs — with pragmatic architecture, traceable automation, and honest cloud spend.
I help founders, IT teams and Microsoft partners — in Makati and remotely — stand up Azure platforms, automate delivery, and keep production operations and billing under control.
Tools I work with
Official technology logos across the stack I use daily.
Cloud & Infrastructure
Development
Tooling & Platforms
Selected projects
Production platforms I designed, built and deployed. Click any card to open it live.
Request Hub
A ticketing / request-management portal that centralizes ESG-related submissions, approvals and tracking with role-based access.
One role-based intake for ESG requests instead of scattered email threads.
Azure CSP Calculator
A CSP billing portal that estimates and reconciles Azure consumption, helping partners track customer spend and Azure Credit Offers.
Partners can estimate and reconcile Azure spend and credit offers in one portal.
Learning Development Portal
A learning platform for a Leadership Development Program — course delivery, sign-in and participant progress, deployed on Azure App Service.
Course delivery, sign-in and progress tracking hosted on Azure App Service.
Puto Copy
A self-hosted photo and media management deployment (Immich) running in Docker on an Azure VM with a custom domain and SSL.
Private media library on an Azure VM with a custom domain and SSL.
GitHub activity
Live contribution graph and stats for @lloydismael.
Certifications & education
How I work
A short, repeatable path from first conversation to a running Azure platform.
-
01
Discover
Clarify goals, constraints, the current Azure estate and the outcome that matters.
-
02
Design
Map a pragmatic architecture, CI/CD path and cost envelope before we write code.
-
03
Build
Implement infrastructure, apps and pipelines with traceable automation.
-
04
Operate
Handover runbooks, monitoring and optional ongoing CSP or managed support.
Consulting engagements
Flexible ways to work together — scaled to the depth of support you need.
Advisory
- 1:1 Azure / DevOps consultation
- Architecture & cost review
- Written recommendations
- Email follow-up
Build & Deploy
- Everything in Advisory
- Azure infra + CI/CD setup
- Dockerized app deployment
- Custom domain & SSL
- Handover documentation
Managed Partner
- Everything in Build & Deploy
- CSP subscription management
- Cost optimization & monitoring
- Priority support SLA
- Quarterly roadmap reviews
Questions teams usually ask
Straight answers about Azure consulting, CSP support and how we start.
What Azure and DevOps work do you take on?
Architecture reviews, Azure landing zones and app hosting, CI/CD with Azure DevOps or GitHub, Docker deployments to App Service or VMs, and CSP billing or cost reviews.
Do you work as a Microsoft Cloud Solution Provider?
Yes. I am a Microsoft CSP partner and can help with subscription setup, consumption visibility, Azure Credit Offers and ongoing cost control — not just the first deploy.
Where are you based, and do you work remotely?
I am based in Makati City, Philippines, and work with teams on-site in Metro Manila or remotely across time zones.
How do we start an engagement?
Send a short note via the contact form, SMS or email. Share the workload, timeline and constraints. I typically reply within one business day with next steps.
What stack do you use day to day?
Microsoft Azure, Azure DevOps, GitHub, .NET, C#, Python, PowerShell and Docker, plus Power Platform when it is the faster path for the business.
Start an Azure or DevOps engagement
Tell me about the workload, timeline and constraints. I typically reply within one business day.