What Microsoft announced
Microsoft's Apps on Azure blog describes the connectors as built-in AWS and Google Cloud connectors. The post is titled "What's new in Azure SRE Agent at Microsoft Ignite 2026." Two points from the post matter most:
- Investigations can continue beyond Azure. The agent no longer has to stop where Azure resources end.
- Federation starts from an Azure managed identity. In Microsoft's words, there are no access keys to manage, and each cloud's own IAM decides what the agent can access.
The Ignite post lists "AWS and GCP connectors" as public preview. The same post lists Teams integration, Entra Agent ID, agent collaboration over A2A, Azure CLI, Grafana and Connector Triggers as separate public previews. It lists Slack as a private preview.
Why the identity model matters
Static cloud keys are the usual weak point in cross-cloud tooling. They get created, pasted into a config, and forgotten. Federating from a managed identity avoids that pattern. Because the destination cloud's IAM sets the limits, the agent's reach in AWS or Google Cloud is bounded by roles you define on that side.
Microsoft's announcement does not say the following, so treat them as open questions:
- The exact federation protocol and trust configuration.
- Which AWS or Google Cloud roles are required.
- Which services and resource types are supported.
- Whether cross-cloud actions are read-only.
- How approval controls apply to actions in the external clouds.
- How activity in those clouds is logged.
Least-privilege IAM roles and a non-production trial are sensible general security practice. Microsoft did not prescribe them for this feature.
How this fits Azure SRE Agent's existing design
Microsoft Learn describes the agent as connecting Azure resources, observability tools, incident platforms and source repositories. It uses them to gather signals, identify probable causes, and suggest or execute mitigations. The AWS MCP route required IAM permissions such as aws-mcp:InvokeMcp and aws-mcp:CallReadOnlyTool. That shows how the earlier AWS integration was bounded by IAM policy. Whether the native connectors use a similar permission model is not documented in the material I could see.
Microsoft Learn also says run modes control whether the agent applies actions itself or waits for approval. In Review mode an administrator approves write actions that need approval. In Autonomous mode the agent applies them without waiting. Those are product-level controls. Microsoft has not confirmed how they behave for AWS or Google Cloud actions.
Preview caveats
Azure's update definitions describe "In preview" as available for non-production use and testing, so don't put this in front of production incident response yet. The announcement gives no regional, licensing or onboarding prerequisites for the connectors. Microsoft Learn says pricing is usage-based, metered in Azure Agent Units.
The competitive picture
Vendors are converging on cross-cloud incident agents. AWS DevOps Agent now extends beyond AWS to investigate incidents in Azure workloads. Dynatrace's Cloud SRE Agents app orchestrates AWS, Azure and Google AI agents for incidents across multicloud environments. A third-party comparison published before this announcement said Azure SRE Agent reached non-Azure resources mainly through MCP. That gap is what these connectors address, though no source I found tests the preview's depth.
What admins should do
- Inventory which incidents in your estate span Azure and AWS or Google Cloud.
- Create narrowly scoped IAM roles in the external cloud for any trial.
- Test only against non-production workloads.
- Check audit logs on both sides to confirm what the agent did.
- Wait for the dedicated connector documentation before planning production use.
The practical takeaway is that the announcement is real but thin on detail. The keyless federation model is the part worth watching. Whether the connectors are as controllable as Microsoft's Azure-side governance will only become clear once the setup documentation and logging details are public.
References
- (In preview) Public Preview: Native AWS and Google Cloud support in Azure SRE Agent Azure Updates · 2026-11-17T20:00:32Z
- Announcing AWS with Azure SRE Agent: Cross-Cloud Investigation using the brand new AWS DevOps Agent techcommunity.microsoft.com
- What’s new in Azure SRE Agent at Microsoft Ignite 2026 techcommunity.microsoft.com