AI Meets AMS
@import url(‘https://fonts.googleapis.com/css2?family=Big+Shoulders+Display:wght@600;700;800&family=IBM+Plex+Sans:ital,wght@0,400;0,500;0,600;1,400&family=IBM+Plex+Mono:wght@400;500;600&display=swap’); :root{ –bg:#f4f6f8; –surface:#ffffff; –surface-2:#ebeff3; –border:#d7dee5; –text:#131a22; –text-dim:#5b6772; –accent:#c97a12; –accent-ink:#ffffff; –accent-2:#14877a; –accent-3:#3457c7; –shadow: 0 1px 2px rgba(20,30,40,.06); } @media (prefers-color-scheme: dark){ :root:not([data-theme=”light”]){ –bg:#0a0e14; –surface:#121821; –surface-2:#1b232f; –border:#29323d; –text:#e7edf3; –text-dim:#8a97a6; –accent:#f2a93b; –accent-ink:#181104; –accent-2:#4fd1c5; –accent-3:#7c9cf7; –shadow: 0 1px 2px rgba(0,0,0,.4); } } :root[data-theme=”dark”]{ –bg:#0a0e14; –surface:#121821; –surface-2:#1b232f; –border:#29323d; –text:#e7edf3; –text-dim:#8a97a6; –accent:#f2a93b; –accent-ink:#181104; –accent-2:#4fd1c5; –accent-3:#7c9cf7; –shadow: 0 1px 2px rgba(0,0,0,.4); } *{box-sizing:border-box;} html,body{margin:0;padding:0;} body{ background:var(–bg); color:var(–text); font-family:’IBM Plex Sans’,system-ui,sans-serif; line-height:1.6; -webkit-font-smoothing:antialiased; } h1,h2,h3{ font-family:’Big Shoulders Display’,system-ui,sans-serif; text-transform:uppercase; letter-spacing:.01em; text-wrap:balance; color:var(–text); margin:0; } code, .mono, .tag, .stat-value, .console, .kicker{ font-family:’IBM Plex Mono’,’SFMono-Regular’,monospace; } .page{max-width:920px;margin:0 auto;padding:0 24px 96px;} /* ———- MASTHEAD ———- */ .masthead{ padding:64px 0 40px; border-bottom:1px solid var(–border); margin-bottom:56px; } .kicker{ font-size:.72rem; font-weight:500; letter-spacing:.14em; color:var(–accent-2); display:flex; align-items:center; gap:10px; margin-bottom:22px; animation:rise .6s ease both; } .kicker .dot{ width:7px;height:7px;border-radius:50%; background:var(–accent-2); box-shadow:0 0 0 3px color-mix(in srgb, var(–accent-2) 20%, transparent); } h1.title{ font-size:clamp(2.6rem,7vw,4.6rem); font-weight:800; line-height:.95; animation:rise .7s .05s ease both; } .subtitle{ max-width:62ch; font-size:1.15rem; color:var(–text-dim); margin-top:20px; font-weight:400; animation:rise .7s .12s ease both; } .byline{ margin-top:26px; font-size:.85rem; color:var(–text-dim); display:flex; gap:10px; align-items:center; animation:rise .7s .18s ease both; } .byline strong{color:var(–text);font-weight:600;} .byline .sep{color:var(–border);} @keyframes rise{ from{opacity:0;transform:translateY(10px);} to{opacity:1;transform:translateY(0);} } @media (prefers-reduced-motion: reduce){ .kicker,h1.title,.subtitle,.byline,.console{animation:none !important;} .kicker .dot{animation:none !important;} } /* ———- CONSOLE (hero dashboard chrome) ———- */ .console{ margin-top:40px; background:var(–surface); border:1px solid var(–border); border-radius:6px; overflow:hidden; box-shadow:var(–shadow); animation:rise .7s .24s ease both; } .console-bar{ display:flex; align-items:center; justify-content:space-between; padding:10px 16px; background:var(–surface-2); border-bottom:1px solid var(–border); font-size:.7rem; letter-spacing:.1em; color:var(–text-dim); } .console-bar .live{ display:flex;align-items:center;gap:8px; color:var(–accent-2); } .live .pulse{ width:6px;height:6px;border-radius:50%; background:var(–accent-2); animation:pulse 1.8s ease-in-out infinite; } @keyframes pulse{ 0%,100%{opacity:1;box-shadow:0 0 0 0 color-mix(in srgb, var(–accent-2) 45%, transparent);} 50%{opacity:.55;box-shadow:0 0 0 5px color-mix(in srgb, var(–accent-2) 0%, transparent);} } .console-grid{ display:grid; grid-template-columns:repeat(3,1fr); } .console-cell{ padding:20px 22px; border-right:1px solid var(–border); } .console-cell:last-child{border-right:none;} .console-label{ font-size:.68rem; letter-spacing:.08em; color:var(–text-dim); margin-bottom:10px; } .console-value{ font-size:1.7rem; font-weight:600; color:var(–text); display:flex; align-items:baseline; gap:8px; } .console-value .delta{ font-size:.8rem; color:var(–accent-2); font-weight:500; } .console-value .delta.warn{color:var(–accent);} .spark{display:block;margin-top:12px;} .spark path{fill:none;stroke:var(–accent-2);stroke-width:1.6;} .spark .fill{stroke:none;fill:color-mix(in srgb, var(–accent-2) 14%, transparent);} .console-foot{ padding:9px 16px; border-top:1px solid var(–border); font-size:.68rem; color:var(–text-dim); letter-spacing:.03em; } /* ———- ARTICLE ———- */ .article section{ max-width:64ch; margin:0 auto 64px; } .article section:last-of-type{margin-bottom:0;} .tag{ display:inline-block; font-size:.68rem; font-weight:600; letter-spacing:.12em; color:var(–accent); border:1px solid color-mix(in srgb, var(–accent) 40%, transparent); background:color-mix(in srgb, var(–accent) 10%, transparent); padding:3px 8px; border-radius:4px; margin-bottom:16px; } .article h2{ font-size:clamp(1.6rem,4vw,2.15rem); font-weight:700; margin-bottom:20px; } .article p{ font-size:1.05rem; color:var(–text); margin:0 0 18px; } .article p.lede{ font-size:1.2rem; color:var(–text); } .article p:last-child{margin-bottom:0;} .article strong{color:var(–text);font-weight:600;} .article em{color:var(–text-dim);font-style:italic;} blockquote{ margin:32px 0; padding:4px 0 4px 22px; border-left:2px solid var(–accent); font-size:1.25rem; line-height:1.5; color:var(–text); font-family:’IBM Plex Sans’,sans-serif; font-style:italic; } /* ———- CODE BLOCK ———- */ .query{ margin:28px 0; background:var(–surface); border:1px solid var(–border); border-radius:6px; overflow:hidden; box-shadow:var(–shadow); } .query-head{ display:flex; justify-content:space-between; align-items:center; padding:9px 16px; background:var(–surface-2); border-bottom:1px solid var(–border); font-size:.68rem; letter-spacing:.08em; color:var(–text-dim); } .query pre{ margin:0; padding:18px 20px; overflow-x:auto; font-size:.86rem; line-height:1.7; } .query code{color:var(–text-dim);} .query .kw{color:var(–accent-3);} .query .fn{color:var(–accent-2);} .query .str{color:var(–accent);} .query .num{color:var(–accent);} /* ———- RESULT TILES ———- */ .tiles{ display:grid; grid-template-columns:repeat(2,1fr); gap:14px; margin:28px 0 8px; } .tile{ background:var(–surface); border:1px solid var(–border); border-radius:6px; padding:22px 20px; box-shadow:var(–shadow); } .tile-value{ font-family:’IBM Plex Mono’,monospace; font-size:2.4rem; font-weight:600; color:var(–accent-2); font-variant-numeric:tabular-nums; line-height:1; } .tile-label{ margin-top:10px; font-size:.82rem; color:var(–text-dim); } .tile.wide{grid-column:1 / -1;} .tile.qual .tile-value{ font-family:’Big Shoulders Display’,sans-serif; font-size:1.5rem; text-transform:uppercase; color:var(–text); } @media(max-width:640px){ .tiles{grid-template-columns:1fr;} .console-grid{grid-template-columns:1fr;} .console-cell{border-right:none;border-bottom:1px solid var(–border);} .console-cell:last-child{border-bottom:none;} } /* ———- FOOTER ———- */ .colophon{ margin-top:88px; padding-top:28px; border-top:1px solid var(–border); display:flex; justify-content:space-between; gap:20px; flex-wrap:wrap; font-size:.8rem; color:var(–text-dim); } .colophon strong{color:var(–text);}
FIELD NOTES — APPLICATION MANAGED SERVICES
AI Meets AMS
How Azure AI/ML and KQL are reshaping application managed services — and why “keep the lights on” support is becoming a strategic differentiator, not a cost center.
Amarnath
·
August 2026
·
7 min read
INCIDENT CONSOLE
LIVE — 90D WINDOW
MEAN TIME TO RESOLUTION
31
m
▼ 30%
SEV1/2 OPEN BACKLOG
4
▼ steady
TRIAGED W/O ESCALATION
68
%
▲ rising
Representative telemetry pattern, modeled on the Microsoft ACE Support initiative — not a live export.
SIGNAL
The line item nobody renegotiates up
For most of its history, application managed services has been sold on a promise nobody says out loud: keep it running, keep it cheap, keep it quiet. AMS won contracts on discipline, not intelligence — tighter SLAs, cheaper headcount, fewer surprises. It was insurance, not investment, and clients priced it accordingly.
That’s the part of the industry I think is about to be renegotiated. Not because clients suddenly value uptime more, but because the tools underneath AMS have changed enough that the work itself changed. When telemetry lives in a queryable platform and a model can read an incident before a human opens the ticket, “keep the lights on” stops being a cost center you manage down and starts being a capability you can point to.
CONTEXT
What the old model actually cost
Traditional AMS runs on tribal knowledge. Logs live in five different systems, dashboards are built for the last incident rather than the next one, and a Sev1 at 3 a.m. depends on whichever engineer happens to remember where the relevant table lives. Alert fatigue is not a side effect of this model — it’s the default output of it. Escalation paths exist because no single view of the system exists.
None of this is a staffing problem. It’s an information architecture problem, and for a long time there was no economical way to fix it: telemetry volumes were too large to query cheaply, and the people who understood the data were the same people who were supposed to be responding to it.
STACK
Azure Data Explorer, and why KQL changes the math
The first real shift is boring, in the way that good infrastructure usually is: centralize the telemetry, and give people a language fast enough to actually interrogate it. Azure Data Explorer is built for exactly this — billions of log, metric, and trace rows, queried in seconds rather than minutes, with KQL doing the work that used to require a bespoke script and a coffee break.
What that unlocks isn’t just faster dashboards. It’s pattern detection that used to be impossible on a ticket-by-ticket basis — the same latency spike that preceded the last four Sev2s, surfaced automatically instead of remembered by whoever was on call that week.
KQL — incident_ops.kql
Azure Data Explorer
IncidentEvents
| where TimeGenerated > ago(90d)
| where Severity in ("Sev1", "Sev2")
| summarize AvgResolutionMinutes = avg(ResolutionMinutes),
Incidents = count()
by bin(TimeGenerated, 7d)
| order by TimeGenerated asc
| render timechartNothing here is exotic. What matters is that a query like this now returns in the time it takes to read it, over a platform every engineer on the account can already query — not a report someone builds once a quarter.
AUTOMATION
Copilot doesn’t replace the responder — it changes who responds first
Layered on top of that data platform, Copilot-driven automation does the part engineers least want to do at 3 a.m.: read the noise, correlate it against history, and draft a first hypothesis in plain language before a human is even paged. A natural-language query stands in for the KQL one when speed matters more than precision. A draft runbook shows up attached to the ticket instead of living in someone’s head.
The important design choice is where the human stays in the loop. Remediation still needs a person to approve it. But triage, correlation, and root-cause drafting — the work that used to consume the first twenty minutes of every incident — increasingly happens before anyone is woken up. The senior engineer’s job shifts from first responder to reviewer: tuning the model’s judgment rather than being the model.
The scarce skill in AMS is no longer “knows where the logs are.” It’s “knows when to override the model.”
INITIATIVE
What this looked like inside the ACE Support initiative
The clearest version of this shift I’ve watched play out has been inside Microsoft’s ACE Support initiative, where AMS operations were rebuilt around this same combination — telemetry consolidated into Azure Data Explorer, KQL as the shared query layer across the team, and Copilot-driven automation sitting on top of both. It wasn’t a rip-and-replace of the support model; it was the existing team, given a platform that let their judgment scale past the size of the queue.
The result wasn’t fewer incidents. Systems still fail in the same ways they always have. What changed was how quickly the pattern behind a failure got surfaced, and how much of the early diagnostic work happened before a person had to sit down and do it by hand.
RESULTS
What moved
Two numbers made the case better than any architecture diagram did.
−30%
Incident resolution time, driven by automated correlation across telemetry instead of manual log-hopping.
≤−30%
Operating cost, as automation absorbed the triage and diagnostic hours that used to sit on every ticket.
Reactive → proactive
The more durable change: engineering time shifted from firefighting individual tickets to tuning the models and queries that catch the next one earlier.
ARGUMENT
From cost center to differentiator
Here’s the strategic version of the same story. When resolution is faster and the cost to deliver it is lower, AMS stops being the line a client’s procurement team negotiates down every renewal cycle. It becomes the reason they renew at all — a capability a competitor without the same data platform can quote a lower headline rate for, but can’t actually match on outcome.
That’s a moat, and it’s a specific kind of moat: not proprietary technology, but the discipline of centralizing telemetry and building the query and automation layer on top of it before the AI gets credit for the result. Any provider can buy Copilot. Fewer have spent the unglamorous months making sure it has something worth reading.
OUTLOOK
The platform comes before the intelligence
This is still early. The pattern I’d expect over the next few years is AMS providers splitting into two groups — those who treat the data platform as the actual product and the AI layer as a feature of it, and those who bolt a copilot onto the same fragmented logging they’ve always had and wonder why the numbers don’t move.
If there’s one thing worth taking from this, it’s that order of operations. Copilot is only as good as the telemetry underneath it. Get the platform right first, and “keep the lights on” starts paying for itself.
Intelligent Automation & Enterprise AI Governance
Deploying advanced cognitive automation and intelligent algorithmic systems across enterprise operations demands a disciplined equilibrium between automated efficiency and institutional accountability across every departmental touchpoint. Organizations advancing automation maturity must first establish the integrity, security, and traceability of underlying operational data pipelines before deploying autonomous execution engines into mission-critical workflows. Instituting explicit ethical guidelines, human-in-the-loop exception checkpoints, and granular audit logging frameworks ensures automated system outputs remain thoroughly transparent, verifiable, and compliant with evolving international regulatory mandates. Without standardized data engineering foundations, automation initiatives inevitably risk accelerating legacy operational inconsistencies across interconnected business units.
Sustainable automation scale demands a centralized center of excellence that seamlessly integrates systems engineering with frontline business domain expertise throughout project lifecycles. By maintaining continuous visibility into cycle times, operational throughput, and process exception rates, management teams can systematically prioritize high-value business processes for iterative architectural optimization. Concurrently investing in human-centric change enablement and structured workforce upskilling empowers personnel to transition from mechanical administrative routines to high-impact strategic advisory responsibilities. This collaborative operating philosophy ensures enterprise automation delivers sustainable productivity gains, enhanced auditability, and measurable competitive differentiation.
No comment yet, add your voice below!