Microsoft Commercial and Professional Services United Kingdom

Dentsu

Enterprise Knowledge Search · Real-time Analytics

Dentsu needed to turn slow, specialist-driven media analytics into faster self-service insights because complex metrics, multiple systems, and weeks-long turnaround times were putting campaign speed and client satisfaction at risk.

10,000+ employees
80%
90%
minutes

Reported impact

Business outcome

Dentsu moved from weeks-long analysis cycles to a conversational copilot that cuts analysis time by 80 percent, reduces overall time to insight by 90 percent, lowers analysis costs, and helps planners and clients optimize media plans faster with more confidence and broader self-service access.

  • Cost Reduction
  • Productivity Improvement
  • Revenue Growth
  • Speed to Market

Solution

Dentsu built a predictive analytics copilot on the Microsoft Azure AI platform to turn complex media-planning analysis into a conversational, self-service workflow. The application sits inside Dentsu's existing business suite as a loosely coupled microservice and uses multiple autonomous generative AI agents that collaborate through API-based integration and GraphQL. Media metrics, modeled client data, best practices, and forecasting logic flow through Azure AI Foundry, Azure OpenAI Service, and Azure Machine Learning, while Azure Kubernetes Service (AKS) runs the front end and connects it to an Azure AI hub that hosts prompt flow as the app's third tier. The team assembled agent logic as Python-based DAG flows and used Azure API Management for generative AI logging and monitoring. The result is a governed GenAIOps-ready architecture that preserves Dentsu's shared governance model while moving from proof of concept to production in under 12 weeks.

Data flow

User questions from Dentsu's business applications enter the AKS-hosted front end, flow through Azure AI Foundry prompt flows and collaborating agents, draw on media metrics, modeled client data, and best practices through Azure OpenAI Service and Azure Machine Learning, and return governed insights with Azure API Management capturing logging and monitoring.

Solution architecture

5 components · 4 layers
  1. Compute
    • Azure OpenAI Service Drives the chat capability that turns natural-language questions into media-planning insights.
    • Azure Machine Learning Supports the predictive analytics and model operations needed for the copilot's forecasting and optimization logic.
  2. Serving
    • Azure Kubernetes Service (AKS) Runs the front-end application tier and connects it to the Azure AI hub and prompt flow services.
  3. Orchestration
    • Azure AI Foundry Orchestrates the copilot's prompt flows, agent workflows, and Azure AI hub integration for media-planning analysis.
  4. Governance
    • Azure API Management Provides logging and monitoring for generative AI requests to help enforce responsible AI operations.

Architecture clues

  • Agents collaborate using API-based integration and the GraphQL protocol.
  • Azure API Management supports generative AI logging and monitoring, and the rollout used a blue/green deployment model with zero downtime.
  • Prompt flow runs as a third tier in front of Dentsu's existing application architecture with Python-based DAG flows.
  • The application uses loosely coupled microservices and multiple autonomous generative AI agents.

Evidence from the source

A custom implementation of Azure API Management supports generative AI logging and monitoring to help ensure responsible AI.
After assessing its options for an AI platform, Dentsu chose the Microsoft Azure AI platform, including Azure OpenAI Service and Azure Machine Learning.
It slashes analysis time by 80% and overall time to insight by 90%, reducing analysis costs.
The application architecture consists of loosely coupled microservices and multiple generative AI agents that act autonomously but can collaborate using API-based integration and the GraphQL protocol.
We had our existing app architecture in front of prompt flow, and we ran everything on Azure Kubernetes Service (AKS) at the front end and connected that with our Azure AI hub in AI Foundry to provide prompt flow as a third tier for the app.
With that support, the Dentsu team developed the copilot in under 12 weeks.
Transparency Evidence & methodology 100/100 reference value · 89% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value100/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    3 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence89%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    6 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. Microsoft

    Dentsu customer story

    First-party
    https://www.microsoft.com/en/customers/story/19582-dentsu-azure-kubernetes-service
    Source type
    Vendor-published customer story
    Published
    Nov 19, 2024
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

  • Published on source page Nov 19, 2024 · Microsoft · First-party
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.