{
  "id": 20714011,
  "title": "Every Cloud Sells the Same AI Stack. Each One Anchors It Somewhere Else.",
  "url": "https://urgent.news/2026/11/19/every-cloud-sells-the-same-ai-stack-each-one-anchors-it-somewhere-else",
  "topic": "ai",
  "section": "AI",
  "published": "2026-11-19T06:42:47.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/amitrix/every-cloud-sells-the-same-ai-stack-each-one-anchors-it-somewhere-else-25bf"
  },
  "original_language": "en",
  "account": "AWS, Microsoft Azure, and Google Cloud all sell the same AI stack for their agent services, but each one deploys it in a different environment. The conversion from foreign data sources to the vendor's own system occurs at the point where each identity provider, cloud data, remote employees, and external models are integrated. No two providers use the same method for this conversion.\n\nThe three major clouds each have specific components for agent platforms, identity, models, and marketplaces. The map of these components was last updated on November 18, 2026, and includes preview rows.\n\nEach vendor's service caters to different capabilities. For employee AI assistants, AWS offers Quick, Microsoft provides Microsoft 365 Copilot, and Google has Gemini Enterprise Research. These agents are designed to work with the vendor's own ecosystem of tools and services.\n\nWhen it comes to agent runtimes, AWS uses Amazon Bedrock, Microsoft uses Foundry Agent Service, and Google uses Gemini Enterprise Agent Platform. All three support compatible external models, with Claude Opus, Sonnet, and Haiku running on all three clouds, and xAI's Grok 4.7 available on all platforms as well.\n\nThe identity management differs across providers. AWS automatically creates an agent identity within the account's directory, Microsoft uses an Entra Agent ID, and Google uses a SPIFFE ID tied to the runtime hosting resource.\n\nIn terms of data access, each cloud has a different approach. AWS uses Amazon Redshift for a structured knowledge base, Microsoft uses Fabric data agents over OneLake, and Google uses BigQuery grounded by Knowledge Catalog. All three can access data on other clouds, with AWS using Athena and Google using BigQuery with Knowledge Catalog.\n\nEmployee access to the agent also varies. AWS offers Quick with integrations for Teams, Outlook, and Slack, Microsoft uses Foundry agents publishing to Teams and Microsoft 365 Copilot, and Google offers Gemini Enterprise, which it refers to as \"the new front.\"",
  "summary": "AWS, Microsoft Azure, and Google Cloud now sell matching parts for every layer of an agent. They separate at the point where each one converts anything foreign into one of its own systems. Foreign means a login from another identity provider, data stored on another cloud, employees who work in another vendor's apps, or a model from another lab. All three clouds convert those into a home system,…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}