I launched more than 12 products at Microsoft Azure. Most of them underperformed at launch. Here's what that taught me about enterprise GTM.
Seven years at Microsoft Azure — one of the most successful enterprise software companies in history — reveals a paradox: large company success creates the conditions for launch failure. The essay covers the 'big company PMM trap' (internal alignment as the real GTM problem), why most Microsoft product launches underperformed at launch even when the products were excellent, and the specific patterns that separated the launches that worked from the ones that didn't. Also: what the author misses about Microsoft and what they escaped.
I joined Microsoft in 2014. When I left in 2020, I had worked on more than twelve product launches across Azure's analytics and AI portfolio. I had been part of launches that drove hundreds of millions of dollars in pipeline. I had also been part of launches that, six months after the announcement, had barely moved the needle despite genuine product excellence and genuine customer need.
The gap between those outcomes taught me more about enterprise GTM than any framework I've read.
The single biggest problem in enterprise product marketing at large organisations is not competitive positioning. It is not messaging quality. It is not channel strategy. It is internal alignment — the challenge of getting a large, distributed, incentive-diverse organisation to execute a coherent go-to-market motion.
At Microsoft, the sales organisation is enormous and specialised. There are Azure-focused sellers, solution-area specialists, industry-focused teams, channel partners, and inside sales motions. Each of these groups has quotas. Each of those quotas creates incentives. Those incentives do not always point in the direction of your product launch.
The launches that worked had one thing in common that had nothing to do with the product or the messaging: they had a clear, specific answer to "why should this sales team prioritise this product in this quarter?" Not "it's important to our cloud strategy" — every product in a company the size of Microsoft is important to the cloud strategy. A specific answer: this product gives you a land motion in accounts that are currently buying from Snowflake. This product gives you an upsell path in every account using our data warehouse. Here is why selling this product now is the right thing for your number.
The launches that underperformed almost always had excellent external messaging and unclear internal alignment. The product was positioned well for customers. It was not positioned at all for the field organisation that was supposed to sell it.
Azure SQL Data Warehouse — now Azure Synapse Analytics — was a genuinely strong product. It had performance advantages over major competitors. It had a cost model that worked for enterprise customers. It had Micrsooft's sales infrastructure behind it. And in its initial launch form, it underperformed.
The reason was category confusion. We had launched it into a market where buyers had a well-established mental model of what a cloud data warehouse was, and we had positioned SQL DW as an upgrade to that model rather than a distinct alternative with a different architectural approach. Buyers compared us to Redshift and Snowflake on the metrics those products had established as important, and we looked like a late entrant trying to catch up.
The relaunch — which I led — was almost entirely a positioning exercise rather than a product change. We stopped positioning against competitors' architectures and started positioning against buyers' business outcomes. The same product, positioned differently, generated a 400% year-over-year increase in digital impressions and 15% month-over-month revenue growth in the twelve months following the relaunch.
The product hadn't changed. The buyer's perception of what they were being asked to consider had changed.
Microsoft has a real culture of accountability. This is not a corporate talking point — it manifests in specific ways that were formative for how I think about professional standards.
At Microsoft, product reviews are substantive. You bring data. You are expected to know your numbers: pipeline, revenue, competitive win rates, customer satisfaction. "We're gaining momentum" is not an acceptable answer to "how is this product performing?" You need to know the actual number and be prepared to defend it.
This culture produces something valuable: a very high bar for what counts as evidence. I came out of Microsoft with a deep distrust of vague performance language — "strong progress," "encouraging signals," "building towards." These phrases mean something failed but nobody wants to say it clearly. At Microsoft, the culture was to name the gap directly and explain the plan to close it.
I've brought this to every role since. When someone tells me a launch is "going well," I ask what the pipeline number is. When someone describes messaging as "resonating," I ask what the close rate on deals where that messaging was used. The answers to those questions are usually more informative than any amount of qualitative optimism.
I miss the resources. Seven years of working with world-class engineering, research, and design talent leaves you with a calibration for quality that's genuinely hard to replicate elsewhere. The products I worked on had real engineering depth, and the collaboration between product, engineering, and marketing was more substantive than anything I've experienced at companies a tenth of the size.
What I escaped was the pace. Large organisations move slowly not because of individual incompetence but because of collective coordination cost. Every decision involves stakeholders, reviews, sign-offs, and process. For product launches, this means the time between "we know what the positioning should be" and "the field is executing that positioning" is measured in months, not weeks.
Smaller organisations move faster and break things more. But when the thing you're trying to move fast at is a go-to-market motion in a competitive market, the ability to iterate and correct quickly is worth more than the scale you sacrifice. I learned that by spending seven years inside the scale.
"The launches that worked weren't the ones with the best messaging. They were the ones where the internal organisation understood exactly why selling this product was the right thing for their number."
Microsoft gave me a foundation I still build on. The accountability culture. The evidence standard. The understanding of how large-organisation GTM actually works versus how it's supposed to work. I wouldn't have the vantage point I have at UiPath without the seven years that preceded it.
But it also taught me that scale is a tool, not an outcome. And the most interesting work in enterprise software happens at the edges of what large organisations can do — which is why I left when I did.
Kuber Sharma leads platform product marketing at UiPath. He writes Positioned, a newsletter on AI-era product marketing strategy for enterprise PMMs.