
Unifying Multi-Cloud Operations: AWS DevOps Agent with Azure Integration
With multi-cloud becoming mainstream strategy, organizations struggle with fragmented tools and siloed visibility. AWS DevOps Agent drives operational excellence as autonomous AI teammate across AWS and Azure to provide a unified, AI-driven management layer. This step by step guide explains Integration with Azure Resource Graph to elevate AI cloud operation across AWS and Azure.
Navigating the Complexity of Multi-Cloud Operations
As highlighted in a 2025 SANS Institute survey , 76% of organizations are adopting a multi-cloud strategy. AWS and Microsoft Azure are the top two cloud service providers with n early 50% market share . While multi-cloud strategy address concentration and lock-in risks, managing workloads across diverse environments has become a significant operational hurdle. Teams often struggle with fragmented tooling, inconsistent monitoring, siloed incident response, and a lack of unified visibility. These factors poses risks to availability and slow the mean time to resolution (MTTR), resulted in longer downtime from incidents.
AWS DevOps Agent, now generally available with native support for Azure mitigates these pain points by providing a unified, AI-driven operations layer spanning AWS, Azure, on-premises, and hybrid environments. The agent proactively detects and prevents incidents through intelligent anomaly detection while resolving issues faster via automated root-cause investigation. By offloading SRE engineers from non-human friendly tasks such as reading and correlating logs and metrics, the agent eliminates disparate toolchains and empowers teams to operate confidently across any infrastructure.
How Integration With Azure Resources Works
AWS DevOps Agent integrates with Azure Resource Graph , a native Azure service that enables efficient resource exploration. When granted least-privileged permissions, the agent accesses metrics, logs, and configuration data across your Azure subscription.
While Azure Resource Graph is available at no additional cost, it operates under specific quotas . For example, a user is limited to 15 queries every 5 seconds to prevent throttling. AWS DevOps Agent's native integration handles these technical constraints automatically, freeing SRE teams from building custom tools or managing API rate limits manually.
How to Connect to Azure
The AWS DevOps Agent supports two methods for connecting to Azure, both offering identical capabilities.
- Admin Consent:
- Pro: Streamlined consent-based flow with only few clicks.
- Con: Requires privileged administrator to review and grant admin consent within Microsoft Entra ID.
- App Registration:
- Pro: Self-managed with more control over the application configuration.
- Con: Manual configurations of AWS IAM Outbound Identity Federation and Microsoft Entra ID app registration.
In this walkthrough, we will use the Admin Consent method.
Step By Step Walkthrough
Prerequisites
- An AWS account with access to the AWS DevOps Agent.
- An Azure subscription with permissions to create and assign Azure RBAC roles.
- A Privileged Administrator account with permission to grant admin consent in Microsoft Entra ID .
Step 1: Register Azure Capability Provider
a. Select Capability Providers in AWS DevOps Agent console.
b. Register the Azure Cloud capability.

c. Select the Admin Consent registration method, provide a registration name.

d. You will be redirected to the Microsoft Entra to provide admin consent.
e. Sign in with a user work/ school account that has permission to grant admin consent.

f. Review permissions requested and accept consent for the AWS DevOps Agent application.

g. Upon acceptance, you are redirected back to the AWS DevOps Agent console with a success status showing your registered Azure capability provider.
Step 2: Assign Azure RBAC role
Azure provides built-in Reader role that allow user to view resource configuration within assigned scope such as subscription, resource group etc. Complying to security principle of least privilege we will create a custom role with read permissions on selected Azure resources required by AWS DevOps Agent.
a. Login to Azure portal Subscriptions service. Note down your Azure subscription ID.

b. Prepare JSON document for custom Azure permissions.
{ "properties": { "roleName": "AWS DevOps Agent - Azure Reader", "description": "Least-privilege read-only access for AWS DevOps Agent incident investigations.", "assignableScopes": [ "/subscriptions/<your Azure subscription GUID>" ], "permissions": [ { "actions": [ "Microsoft.AlertsManagement/*/read", "Microsoft.Compute/*/read", "Microsoft.ContainerRegistry/*/read", "Microsoft.ContainerService/*/read", "Microsoft.ContainerService/managedClusters/commandResults/read", "Microsoft.DocumentDB/*/read", "Microsoft.Insights/*/read", "Microsoft.KeyVault/vaults/read", "Microsoft.ManagedIdentity/*/read", "Microsoft.Monitor/*/read", "Microsoft.Network/*/read", "Microsoft.OperationalInsights/*/read", "Microsoft.ResourceGraph/resources/read", "Microsoft.ResourceHealth/*/read", "Microsoft.Resources/*/read", "Microsoft.Sql/*/read", "Microsoft.Storage/*/read", "Microsoft.Web/*/read" ], "notActions": [], "dataActions": [], "notDataActions": [] } ] }}c. Go to Access control (IAM), select Add custom role

d. Upload the JSON document. Your custom role will be auto populated.

e. Verify the Permissions and Assignable scopes. Proceed to Review + create.

f. Return to Subscription's Access control (IAM) to assign role for AWS DevOps Agent application registered in Microsoft Entra.

g. Search for the custom role (AWS DevOps Agent - Azure Reader) created earlier.

h. Proceed to Select members by searching for AWS DevOps Agent. Complete the assignment.

Step 3: Create Agent Space and add Azure source
a. In AWS DevOps Agent console, create an Agent Space by providing a name. You can choose to accept default configuration and auto create a new DevOps Agent role.
AWS DevOps Agent responds to the browser locale setting, including translating agent responses enabling interact with AWS DevOps Agent in your preferred language. 你好!

b. After your Agent Space is created, add secondary source for Azure.

c. Add your Azure subscription easily by simply providing Subscription ID.

d. AWS DevOps Agent will automatically initiate topology mapping. Wait until the mapping completed.

Step 4: Investigate Azure with AWS DevOps Agent
a. Navigate to Agent Space Web App through AWS Console. You can explore the Learned Azure resources listed in Topology.

b. Use the SRE Chat interface for conversational AI assistant to perform on-demand tasks.

c. We start by asking AWS DevOps Agent to show all Azure resources in our subscription.

d. We can query the Azure Virtual Machine's peak CPU usage as AWS DevOps Agent can access Azure Monitor metrics.

e. AWS DevOps Agent can query Azure Activity Logs (AWS CloudTrail equivalent) to track the "what, who, and when" of changes which may cause operational incidents.

Operating with Confidence Across Clouds
By following the steps outlined in this walkthrough, you have successfully configured the AWS DevOps Agent to extend its AI-driven operational capabilities covering your Azure environment. With AWS DevOps Agent, Operation/ SRE teams now benefit from unified visibility across AWS and Azure resources. Engineers can strategically focus on higher-value work including designing resilient architectures, optimizing performance, and driving innovation.
Multi-cloud strategy is here to stay. Having a single, intelligent operations layer that seamlessly bridges environments is no longer a luxury but a necessity. The AWS DevOps Agent positions your organization to operate with confidence, agility, and consistency regardless of where your workloads run.
In next article, we will explore Azure DevOps integration in AWS DevOps Agent with Azure Pipelines to track deployments and code changes in Azure environments
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article