/
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
Handles
Browse by social media handle
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

Rackspace partners with Microsoft, extends support from private to public and hybrid Azure clouds

Toby Wolpe / ZDNet :

ZDNet Toby Wolpe

Context & Ripple Effects

In mid-2015, Rackspace — a hosting company whose brand was built on running customers' workloads in its own data centers — agrees to put its support operation on top of Microsoft's infrastructure instead, extending its managed-services push from private clouds out into Azure's public and hybrid offerings. For Microsoft, this is distribution: enterprise buyers get a familiar services wrapper around Azure without Microsoft staffing it.

The move kicked off a pattern Microsoft repeated across the ecosystem within months. Hewlett Packard Enterprise signed on to sell Azure as its preferred cloud alternative, Red Hat brought Linux to the platform, and by mid-2016 Microsoft had recruited HPE, Dell, and Lenovo to ship Azure Stack on their own hardware. Rackspace was the first services player to sign that template.

First-order effects

  • Rackspace's engineers now manage customer workloads running in Microsoft's data centers as well as its own — revenue shifts toward service fees while utilization of Rackspace-owned capacity becomes less central to the business.
  • Microsoft gains an enterprise-facing support channel for Azure at essentially no headcount cost, using Rackspace's existing customer relationships as an entry point.

Second-order effects

  • Hardware vendors are forced to pick sides: HPE responds by making Azure its preferred cloud and joining the Azure Stack program with Dell and Lenovo, turning former server-and-hosting rivals into Azure resellers.
  • AWS faces the same playbook turned against it — Rackspace's later plan to offer managed services for both clouds signals that third-party support layers will span hyperscalers, pressuring every platform to court such partners.

Third-order effects

  • If the pattern holds, cloud competition reorganizes around a small set of hyperscale platforms with everyone else — hosts, OEMs, software vendors like Red Hat, which later brought jointly managed OpenShift to Azure — competing on service, hardware, and tooling layered on top rather than on infrastructure itself.
  • Independent hosting economics erode: when the biggest former competitor becomes your landlord's partner, owning data centers stops being the moat and managing across platforms becomes the product.

The trend: Hyperscalers are converting former hosting competitors into managed-services channels for their platforms, shifting the industry's value from owning infrastructure to operating it on someone else's.