/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

← → days · ↑ ↓ browse · Enter similar · o open

How Microsoft is making the machine learning capabilities behind Cortana accessible to any app with Project Oxford

Sean Gallagher / Ars Technica :

Ars Technica Sean Gallagher

Context & Ripple Effects

In 2015, Microsoft began treating Cortana not just as a consumer assistant but as a source of sellable capability: Project Oxford exposed the speech and vision machine learning behind the assistant as APIs any developer could call. Two months later the company packaged the broader stack — Power BI, Azure Machine Learning and more — into the subscription-priced Cortana Analytics Suite, making clear the play was Azure consumption, not just developer goodwill.

That arc kept extending: Oxford added Speaker Recognition and Video API previews by year-end, and by 2017 the Cortana Skills Kit plus Microsoft Graph data sharing for third-party apps turned the assistant itself into a developer platform. The endpoint of this strategy arrived in 2023, when Nadella committed to integrating OpenAI's tools across all Microsoft products and opening them to other businesses to build on.

First-order effects

  • Developers gain direct API access to the same speech, vision, and language models that power Cortana, without building ML expertise in-house — with usage routed through Microsoft's cloud.
  • Microsoft converts an internal assistant feature into a billable product line, giving Azure a differentiated ML offering against rivals' own cognitive services.

Second-order effects

  • Success of the initial APIs forces a rapid widening of the catalog — speaker recognition, video analysis, then a full analytics suite on monthly subscription — pulling more workloads onto Azure.
  • Third-party apps built on these APIs become dependent on Microsoft's model roadmap, shifting bargaining power over voice and vision features toward the platform provider.

Third-order effects

  • The pattern — internal AI opened as a platform, then a skills ecosystem, then graph-level data sharing — establishes the template Microsoft later applied at much larger scale with OpenAI tooling across its entire product line.
  • If assistants keep evolving from features into distribution layers for third-party capabilities, the durable position belongs to whoever controls both the models and the app surface they run on.

The trend: Microsoft has spent nearly a decade converting assistant-era machine learning into rentable cloud platforms, a strategy that culminated in wiring OpenAI's models into every product it sells.