Study guide
13.4 Connecting AWS and GCP Environments to Microsoft Defender for Cloud
Microsoft Azure Security Technologies AZ-500
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Overview & Azure Security Architecture Foundation
1.1 Azure Security Engineer Role & Exam Logistics 1.2 Microsoft Cybersecurity Reference Architecture & Zero Trust Principles
2 Chapter 2: Secure Identity and Access - Authentication, MFA & PIM
2.1 Microsoft Entra ID Security, Users, and Groups 2.2 Authentication Methods, MFA, and Conditional Access Policy Design 2.3 Microsoft Entra Privileged Identity Management (PIM)
3 Chapter 3: Secure Identity and Access - RBAC & Workload Identity
3.1 Azure RBAC, Custom Roles, and Governance 3.2 Workload Identities and Managed Identities 3.3 External Identities and Cross-Tenant Collaboration
4 Chapter 4: Microsoft Entra Application Access & Consent Governance
4.1 Enterprise Applications, OAuth Permission Grants & Consent Governance 4.2 App Registrations, Permission Scopes & Service Principal Credentials
5 Chapter 5: Secure Azure Networking - Boundary & Perimeter Protection
5.1 Virtual Network Security & Micro-segmentation 5.2 Azure Firewall and Firewall Manager 5.3 Web Application Firewall (WAF) & Azure Front Door
6 Chapter 6: Secure Azure Networking - Private Access & Monitoring
6.1 Private Connectivity with Private Endpoints & Private Link 6.2 Azure Bastion & Remote Management Security 6.3 Network Perimeter Protection & Flow Monitoring
7 Chapter 7: Network Architecture, Routing & Hybrid Connectivity
7.1 Azure Virtual Network Manager, Network Groups & User-Defined Routes 7.2 VPN Gateway, ExpressRoute Encryption & Virtual WAN Secured Hub 7.3 Network Integration for App Service, Functions, App Service Environment & SQL Managed Instance
8 Chapter 8: Public and Edge Access Protection
8.1 Azure Application Gateway Security, TLS Policy & Mutual Authentication 8.2 Azure Front Door, CDN Caching & TLS for App Service and API Management
9 Chapter 9: Compute, Container & Registry Security
9.1 Azure Virtual Machine Hardening & Host Security 9.2 Azure Key Vault Deep Dive & Secrets Lifecycle 9.3 Container & Azure Kubernetes Service (AKS) Security 9.4 Azure Container Instances, Container Apps & Registry Access Control
10 Chapter 10: Storage Security, Access Methods & Data Protection
10.1 Storage Account Security & Access Controls 10.2 Selecting and Configuring Access to Azure Files 10.3 Selecting and Configuring Access to Azure Blob Storage 10.4 Storage Data Protection: Soft Delete, Versioning, Point-in-Time Restore & Backup
11 Chapter 11: Data Platform & Database Security
11.1 Azure SQL Database Security & Always Encrypted 11.2 Database Auditing & Vulnerability Assessment 11.3 Data Discovery, Classification, & Microsoft Purview Integration
12 Chapter 12: Cloud Governance, Key Lifecycle & Asset Protection
12.1 Azure Policy for Security Governance: Definitions, Initiatives, Effects & Remediation 12.2 Key Vault Backup, Recovery & Automated Key Rotation 12.3 Implementing Security Controls to Protect Backups 12.4 Security Controls for Asset Management: Locks, Tags, Resource Graph & Azure Arc
13 Chapter 13: Microsoft Defender for Cloud - Posture & Workload Protection
13.1 Microsoft Defender for Cloud & Secure Score 13.2 Defender Cloud Workload Protection (CWP) Plans 13.3 Defender for Cloud Inventory, Compliance Standards & Custom Standards 13.4 Connecting AWS and GCP Environments to Microsoft Defender for Cloud
14 Chapter 14: External Attack Surface & Vulnerability Management
14.1 Microsoft Defender External Attack Surface Management (EASM) 14.2 Agentless Scanning & Microsoft Defender Vulnerability Management for Azure VMs 14.3 Defender for Cloud DevOps Security: GitHub, Azure DevOps & GitLab
15 Chapter 15: Security Monitoring, Microsoft Sentinel & Automation
15.1 Azure Monitor Data Collection Rules & Network Security Event Monitoring 15.2 Microsoft Sentinel Data Connectors, Content Hub & Normalization 15.3 Microsoft Sentinel Workspace & KQL Threat Hunting 15.4 Sentinel Incident Management & SOAR Automation
13.4 Connecting AWS and GCP Environments to Microsoft Defender for Cloud
Key Takeaways Explain This Topic AI
AWS connectors authenticate through an IAM role assumed via OpenID Connect federation with Microsoft Entra ID, deployed with a CloudFormation template.
GCP connectors use workload identity federation with a dedicated service account, deployed with a provided gcloud or Terraform script.
Connecting at the AWS management account or GCP organization level auto-onboards member accounts and projects as they are created.
Defender for Servers on AWS and GCP machines depends on Azure Arc onboarding or agentless scanning provided by the connector.
Multicloud recommendations are mapped to the Microsoft Cloud Security Benchmark, and CIS AWS and CIS GCP standards can be assigned per connector.
Last updated: August 2026
Why Multicloud Appears on an Azure Security Exam
The AZ-500 audience profile explicitly says the Azure security engineer implements and monitors security "for resources in Azure, multi-cloud, and hybrid environments". Defender for Cloud is the product that delivers that, so connecting AWS and GCP is a named objective. The pattern to internalize: Defender for Cloud reads the other cloud's configuration through a federated identity, evaluates it against the Microsoft Cloud Security Benchmark, and optionally deploys workload protection onto the machines.
Connecting an AWS Account
Authentication model. Defender for Cloud does not store AWS access keys. Instead:
You create an AWS connector in Defender for Cloud (Environment settings → Add environment → Amazon Web Services), naming the account and selecting plans.
Defender for Cloud generates a CloudFormation template (Terraform is also supported).
Running it in AWS creates IAM roles with a trust policy that allows assumption by Microsoft's application through OpenID Connect (OIDC) federation with Microsoft Entra ID .
Defender for Cloud assumes those roles to read configuration and, where enabled, to perform agentless scanning.
The security property: there is no long-lived AWS secret anywhere in the integration — the same workload identity federation idea used for GitHub Actions, applied to a cloud connector.
Onboarding scope:
- Scope Behaviour
- Single AWS account One account only; repeat per account
AWS management account (organization) Auto-provisions member accounts, including accounts created later, via StackSets
Choose the management account when the scenario mentions many accounts or future growth — manually connecting accounts one by one is the wrong answer at scale.
Plans available on the AWS connector:
Defender CSPM — agentless posture, attack path analysis, cloud security graph, and agentless VM scanning of EC2 instances.
Defender for Servers — Microsoft Defender for Endpoint on EC2 instances. Requires the machines to become Azure Arc–enabled servers (the connector can auto-provision Arc), or to be covered agentlessly.
Defender for Containers — EKS cluster discovery, audit log collection, and runtime protection with the Defender sensor.
Defender for Databases — protection for supported managed database instances.
Connecting a GCP Project or Organization
Authentication model. GCP uses workload identity federation :
Create a GCP connector in Defender for Cloud, naming the project (or organization) and selecting plans.
Run the supplied gcloud CLI script or Terraform configuration in GCP.
It creates a workload identity pool and provider plus a service account that Microsoft's identity can impersonate — again, no downloaded service account key file.
Onboarding scope: connect a single project or the GCP organization , where the organization scope auto-onboards existing and future projects.
Plans available on the GCP connector mirror AWS: Defender CSPM (including agentless VM scanning), Defender for Servers (via Arc onboarding), Defender for Containers (GKE), and Defender for Databases.
What You Get After Connecting
- Capability Result across clouds
- Unified inventory AWS and GCP resources appear in Inventory alongside Azure resources
Recommendations Multicloud recommendations mapped to MCSB, with cloud-native detail (for example, S3 bucket public access, GCS uniform bucket-level access)
Secure Score Multicloud resources contribute through their MCSB-mapped recommendations
Compliance standards CIS AWS Foundations Benchmark , CIS GCP Foundations Benchmark , PCI DSS, and custom standards assignable per connector
Custom recommendations Authored as KQL over the cloud security graph (Defender CSPM required) rather than as Azure Policy
Attack paths Cross-cloud attack path analysis in Defender CSPM
Alerts and export AWS/GCP alerts flow into the same alert pipeline, exportable to Sentinel through continuous export or the Defender for Cloud connector
Common Design Decisions
Agent or agentless? Agentless scanning through Defender CSPM gives broad, low-friction coverage of EC2 and GCE disks with no software installed. Defender for Servers with the Defender for Endpoint sensor adds real-time behavioural detection and response. Regulated workloads usually need both; a first-pass posture assessment needs only the connector.
Arc or not? Full Defender for Servers features on non-Azure machines require Arc onboarding, which the connector can automate. If a scenario says "endpoint detection and response on EC2 instances", expect Arc plus Defender for Endpoint in the answer.
Permissions. Onboarding requires administrative rights in the target cloud (to run CloudFormation or the gcloud script) and Owner or Security Admin on the Azure subscription hosting the connector. A frequent failure mode is having one but not the other.
Legacy connectors. The older classic cloud connectors have been superseded by the native connectors described here; new work should always use the native connector experience.