NVIDIA Software / SaaS Global

Microsoft

Document Processing

Microsoft needed to deliver accurate live captions and real-time meeting transcripts in many languages for Teams while keeping inference latency low and compute costs under control at massive user scale.

28 languages
nearly 250 million active monthly users

Reported impact

Business outcome

Microsoft delivers cost-efficient, accurate live captioning and transcription across 28 languages for Teams, using Triton to improve throughput and reduce the computational resources needed for real-time speech services.

  • Cost Reduction
  • Customer Experience
  • Scalability

Solution

Microsoft built Teams live captioning and transcription on Azure speech infrastructure that combines Azure Cognitive Services, NVIDIA GPUs on Azure, and NVIDIA Triton Inference Server. Meeting audio is sent from the Teams client to speech models tuned to recognize names, jargon, and meeting context across 28 languages. Triton manages low-latency inference and keeps GPU resources saturated, while Azure packages the service into production-ready captioning and transcript features for massive hybrid-work traffic. The architecture lets Microsoft serve real-time subtitles and transcripts at global scale without overprovisioning compute, so accessibility features remain responsive for daily meetings while keeping throughput high and infrastructure use efficient.

Data flow

Teams sends meeting audio into Azure Cognitive Services, speech models run on NVIDIA GPUs with Triton managing inference, and the resulting captions and transcripts are returned to meeting participants in real time.

Solution architecture

3 components · 2 layers
  1. Compute
    • NVIDIA GPUs on Azure Provide the accelerated compute used to run Microsoft speech models in real time.
  2. Serving
    • Microsoft Azure Cognitive Services Hosts the speech models and application services that power Teams captioning and transcription.
    • NVIDIA Triton Inference Server Serves speech-recognition inference with low latency while maximizing GPU utilization.

Architecture clues

  • Speech models recognize jargon, names, and meeting context
  • Triton ensures models use GPUs to their full potential inside Azure Cognitive Services

Evidence from the source

Microsoft Teams is a collaboration app with nearly 250 million active monthly users.
This enables them to leverage advanced language models that recognize jargon, names, and other meeting context, to deliver highly accurate, personalized speech-to-text results-in real time-with very low latency.
This reduces the cost to customers by delivering higher throughput using fewer computational resources.
Using Triton Inference Server in Azure Cognitive Services seamlessly enables live transcription and captions with state of the art speech models in 28 languages.
Transparency Evidence & methodology 90/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 value90/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 impact15/25
    1 metric 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
    4 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. NVIDIA

    Microsoft customer story

    First-party
    https://www.nvidia.com/en-us/case-studies/live-captions-and-transcription-services-for-microsoft-teams/
    Source type
    Vendor-published customer story
    Published
    Aug 25, 2025
    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 Aug 25, 2025 · NVIDIA · 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.