Follow the customer pull
The partnership began with customer behavior, not a co-marketing brief. Enterprise teams were already building on Azure and using Datadog to understand those environments, so the question was how to make the joint experience feel native. Distribution, billing, telemetry, integrations, and enterprise support had to work as one path—not as separate partner motions.
Make “better together” operational
Datadog became an Azure Native ISV Service, embedded in the Azure portal and sold through Azure Marketplace. Joint engineering expanded monitoring across Azure services and brought integrations including Azure Arc to market. My role was to translate the architecture into the outcomes enterprise teams cared about: lower migration risk, simpler procurement, hybrid visibility, faster onboarding, and the confidence to retire an on-premises service once the new environment was ready.
Prove the partnership in the field
At Microsoft Build, joint launches and customer conversations tested whether the story held up outside a launch plan. The lesson was straightforward: “better together” only becomes credible when product, engineering, field teams, support, and customer demand point in the same direction. Partnership language comes last; shared customer evidence comes first.
Public artifacts
Datadog transforms cloud-scale monitoring with Azure - Microsoft's customer story on native distribution, joint engineering, and enterprise-scale observability.
Replicate apps on Azure - Microsoft's software-company guidance, featuring Datadog as a customer-led path into Azure.
Shared customer evidence - the Azure Observability Summit, bringing the joint product story into operating conversations with enterprise customers.
Microsoft Build launch record - the Datadog team's public record of new Azure capabilities launched with Microsoft.