-
Designing AKS Autoscaling for Capacity Resilience
How SKU-flexible node provisioning with Node Auto-Provisioning and Karpenter can reduce scale-out risk Technical acknowledgement: A nod to Zach Bugay for his AKS technical review and guidance, which helped sharpen the NAP/Karpenter migration considerations,…
-
Tracking AI Token Usage with APIM and Application Insights
How to replace APIM LLM logging as your primary token-reporting mechanism, emit richer metrics to Application Insights, and finally report on cached tokens. By Scott Ray · Azure API Management · Application Insights ·…
-
PTU Spillover and Token Tracking in Microsoft Foundry
Why spillover matters for cost attribution, chargeback, and observability in provisioned AI deployments In this post, I’ll walk through how PTU spillover works in Microsoft Foundry, why it complicates token tracking, and what you…
-
Token-Level Chargeback for Azure OpenAI Batch API Using APIM, Event Hub, and Durable Functions
Batch APIs are fantastic for high-volume, asynchronous workloads—but they come with a challenge every architect eventually runs into: How do you track and charge back token consumption when thousands of completions are bundled into…
-
Tracking Azure OpenAI Token Usage by an Application’s Client ID in APIM
Because “who’s using my tokens?” is always a fun question—especially at chargeback time. Disclaimer: The views and opinions expressed here are my own and do not necessarily reflect those of my employer or any organization…
-
Implementing Token‑Based Chargeback for Azure OpenAI PTU Deployments Using API Management
Disclaimer: The views and opinions expressed here are my own and do not necessarily reflect those of my employer or any organization with which I am affiliated. Hello, my name is Scott Ray, and…
Architecting in Azure
Explore effective Azure architecture strategies, learn what works and what breaks, and understand the reasons behind success and failure in real-world applications.
Follow Me On Social Media
@ScottRayPhoto
This is how it all started…
After 30 years in IT—working across engineering, architecture, operations, and now serving as a Principal Cloud Solution Architect at Microsoft—I realized it was time to create a place where I can share the ideas, patterns, and practical guidance that continue to shape my work. This blog is the beginning of that journey. I’ll be using it to publish posts that break down real-world architecture decisions, explore emerging cloud capabilities, and highlight the lessons learned from helping customers modernize and innovate at scale. While the primary focus will be on Azure and cloud architecture, I’ll also weave in the occasional personal perspective—because after three decades in this industry, the future isn’t just about the technology I work with, but the experiences I continue to grow from. This space will evolve with the challenges, opportunities, and conversations that lie ahead.
DISCLAIMER
The views and opinions expressed here are my own and do not necessarily reflect those of my employer or any organization with which I am affiliated.
Scott Ray
Principal Cloud Solution Architect