Deploying Microsoft Azure internally at Microsoft
How Microsoft keeps its Microsoft Azure costs down as the company’s ‘customer zero’
Microsoft kept its Microsoft Azure costs flat while its workload footprint grew by 20 percent.
Here at Microsoft, we’re a customer of Microsoft Azure, and just like our external customers, we’re trying to keep our cloud costs down.
“When I talk to customers, they're always a little bit surprised to hear that we pay the same rates for Azure that they do,” says Heather Pfluger, the general manager of Infrastructure and Engineering Services in Microsoft Digital Employee Experience, Microsoft’s internal IT organization. “We operate with the same licensing, the same pricing (as they do).
We call it being Microsoft’s ‘customer zero.’
What does that mean?
For Pfluger and her team, it means sharing the experiences they have trying to use Azure as efficiently as possible back to the product team, which they use to improve the product.
Heather Pfluger, general manager, Infrastructure and Engineering Services, Microsoft Digital Employee Experience
“We have a bit of a dual responsibility,” says Pete Apple, a principal program manager for Microsoft Azure Engineering in MDEE. “As Microsoft’s customer zero, we are acting as the company’s internal customer. We pay Azure’s going rates, we pay Microsoft 365’s going rates.”
And as Microsoft’s IT organization, we operate at a scale that’s useful for the product group to learn from—during our own migration to the cloud, we moved more than 600 services and solutions comprised of approximately 1,400 components to Azure.
“We are the biggest internal customer for Azure,” Apple says. “We make sure that we are having the same sort of experience with a technical account manager, opening cases with our support organization, making sure that we are living the same life that any other enterprise would have to live so that we are giving good feedback about what is working well and what isn't working well.”
To learn more about our migration to Microsoft Azure and how we’ve optimized our workloads once we got there, read our new Doing more with less internally at Microsoft with Microsoft Azure report. Once you get there, also watch a video where Pluger and Apple share our lessons learned optimizing our internal use of Azure.
Published on:
Learn moreRelated posts
Fabric Mirroring for Azure Cosmos DB: Public Preview Refresh Now Live with New Features
We’re thrilled to announce the latest refresh of Fabric Mirroring for Azure Cosmos DB, now available with several powerful new features that e...
Power Platform – Use Azure Key Vault secrets with environment variables
We are announcing the ability to use Azure Key Vault secrets with environment variables in Power Platform. This feature will reach general ava...
Validating Azure Key Vault Access Securely in Fabric Notebooks
Working with sensitive data in Microsoft Fabric requires careful handling of secrets, especially when collaborating externally. In a recent cu...
Azure Developer CLI (azd) – May 2025
This post announces the May release of the Azure Developer CLI (`azd`). The post Azure Developer CLI (azd) – May 2025 appeared first on ...
Azure Cosmos DB with DiskANN Part 4: Stable Vector Search Recall with Streaming Data
Vector Search with Azure Cosmos DB In Part 1 and Part 2 of this series, we explored vector search with Azure Cosmos DB and best practices for...