AWS Security Hub has added a built‑in Azure connector that pulls Azure resource configurations, Microsoft Defender for Cloud alerts, and Entra ID audit logs into the same exposure‑finding pipeline used for AWS assets. Practitioners can now see cross‑cloud attack paths in one place, making it possible to rank and remediate risks that arise from a single compromised identity moving between clouds.
Why Multicloud Risk Is Hard to Prioritize
In many enterprises, an Entra ID tenant is federated into AWS so that a single identity can assume an AWS role. The compromise of that identity creates a threat vector that lives in both clouds, but the signals appear in separate consoles: Entra ID and Defender for Cloud on the Azure side, and IAM and other AWS security tooling on the AWS side. Each team sees only a fragment—over‑privileged identities, an internet‑exposed host, a federated trust, or exposed data—making each fragment appear low severity in isolation. Only when the fragments are correlated does the true attack path emerge.
How the Azure Connector Extends Exposure Findings
To bring Azure data into Security Hub, you create an Azure connector in the AWS Management Console. The connector authenticates to the Entra ID tenant via an application registration. Once authorized, it records Azure resource configurations and streams two data feeds through an Azure Event Hubs namespace:
- Microsoft Defender for Cloud alerts
- Entra ID audit logs
These streams are ingested by Security Hub’s existing correlation engine, which then produces exposure findings that are ranked alongside AWS findings. Each finding is mapped to the MITRE ATT&CK framework, preserving the same level of detail that practitioners are used to when working solely in AWS.
Architectural and Operational Implications
Integrating Azure data changes the security data flow in several ways:
- Unified correlation layer: The same engine evaluates reachability, blast radius, and misconfigurations across both clouds, reducing the need for separate analysis pipelines.
- Shared identity plane visibility: Exposure findings now surface the impact of a compromised Entra ID identity on AWS resources, highlighting the need for coordinated identity governance.
- Event Hubs dependency: The connector relies on a correctly configured Azure Event Hubs namespace; network permissions and throughput limits become part of the operational checklist.
- Team coordination: Findings are presented in a single queue, but ownership still resides with distinct teams (identity, Azure platform, cloud security). Effective triage now requires cross‑team communication.
Related CloudNinjas coverage: AWS.
What This Means For Practitioners
To take advantage of the new visibility, teams should:
- Enable the Azure connector in Security Hub and verify the application registration has the required permissions to read Defender for Cloud alerts and Entra ID audit logs.
- Confirm the Event Hubs namespace is reachable from the AWS account and that any network security groups allow the required traffic.
- Review exposure findings for cross‑cloud attack paths, paying particular attention to over‑privileged Entra identities, missing MFA, and permissive conditional access policies.
- Coordinate remediation actions across the identity, Azure platform, and cloud security teams, using the ranked findings as a shared priority list.
By consolidating Azure and AWS signals, Security Hub provides a practical way to surface and prioritize the true impact of a federated identity compromise, allowing engineers to focus remediation effort where it reduces the overall attack surface the most.

