Urgent.News

What's breaking now, across thousands of outlets.

AI

Every Cloud Sells the Same AI Stack. Each One Anchors It Somewhere Else.

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,…

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.

The 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.

Each 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.

When 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.

The 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.

In 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.

Employee 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."

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in AI

The Anthropic IPO

In general I am bullish on the commercial prospects of AI companies, including Anthropic (do note I am on the Advisory Board, though with zero governance role and zero access to internal information).

How 5 Companies Use AI Coding Agents and Assistants Across the SDLC

An agent-generated pull request has a green build and a full set of tests. A reviewer compares it with the ticket and discovers that the agent guessed how duplicate requests should behave.

  • AI coding agents assist at each SDLC stage from requirements to merge
  • Agents prepare tasks, engineers verify implementations, reviewers ensure test coverage
  • Approved plan guides process; engineers decide on failures and merge owner

More from Thursday 19 November →