12 Jan 2025

Connecting Wiz to your Microsoft Azure Tenant

azure and wiz logo on a blue background

In today’s rapidly evolving cloud landscape, ensuring the security of your resources is paramount. Wiz is a powerful cloud security solution that provides deep visibility into your cloud environment, helping you identify and mitigate risks effectively. Integrating Microsoft Azure with Wiz allows you to leverage these capabilities and maintain a robust security posture. This guide walks you through the steps to seamlessly connect Azure with Wiz.

Step 1: Prerequisites

Before starting the integration process, ensure you have the following:

  • Wiz Account: Access to a Wiz account with sufficient permissions to configure integrations.
  • Azure Subscription: An active Microsoft Azure subscription where you have the necessary administrative rights.

Step 2: Deploying the Wiz Azure Connector

1) In Wiz, navigate to the Settings > Deployments page.

Wiz sidebar navigation with the Settings menu open, showing the Deployments option highlighted

2) Click Add Deployment.

Wiz software interface showing the Deployments page with the Add Deployment button highlighted

3) Select Microsoft Azure.

Wiz "Connect to Wiz" screen listing cloud service providers, including AWS, Microsoft Azure, Google Cloud and Oracle Cloud Infrastructure

4) For Installation Type, leave Wiz Azure App selected.

Installation type selector showing Wiz Azure App (Recommended) selected over Outpost Azure App

5) For Deployment Method, leave Bash selected.

Deployment method selector with Bash selected, alongside Terraform and Manual options

6) For Azure Tenant ID, enter your Azure Tenant ID (refer to this post by Microsoft to find your Tenant ID)

Form field labelled "Azure Tenant ID" asking for the tenant's GUID, with an empty text input

7) For Connector Scope, in this example we will be selecting Subscription.

Connector Scope settings with Subscription selected over Management Group and Azure Active Directory Only options

Wiz allows for the following Connector Scopes:

  • Management Group: Automatically scans all subscriptions within the group, with optional integration to Microsoft Entra ID (AAD) for enhanced capabilities - this would be your typical selection
  • Subscription: Scans only the selected subscription, with optional integration to Microsoft Entra ID (AAD).
  • Microsoft Entra ID (AAD) Only: Scans only Microsoft Entra ID, focusing on principals without scanning any Management Group or Subscription resources.

8) For Subscription ID, enter your Subscription ID (refer to this post by Microsoft to find your Subscription ID)

Empty form field labelled "Subscription ID", with help text stating it is where the Connector roles will be created

9) (Optional) You can choose to grant additional permissions to the connector for the following additional capabilities - serverless and DSPM are typically recommended unless you have specific reasons to exclude them.

Settings panel showing three additional capability checkboxes: Serverless and DSPM permissions ticked, Azure OpenAI permissions unticked

10) Copy the Bash command from the Wiz portal. (Leave the tab open; you'll come back to it soon)

Bash code snippet showing a curl command to download and run the Wiz Azure subscription deployment script

11) In a new browser tab, log in to your Azure portal. Open Cloud Shell with Bash selected.

Microsoft Azure Cloud Shell terminal showing a session starting, with a yellow warning that the session is ephemeral

12) Run the Bash command copied from step 9. If prompted with, Is it okay to proceed?, enter y.

Terminal output of an Azure CLI script prompting to create custom roles for Wiz and assign them to an app, asking "Is it okay to proceed?

13) Once the script finishes successfully, return to the Wiz browser tab.

Terminal screenshot showing a deployment script's comments advising to copy client IDs and secrets before continuing setup in the Wiz portal

14) Below the Bash script, check Deployment script completed, ready to complete connector setup. And click Continue.

Screenshot of a checked confirmation reading "Deployment completed, ready to complete Connector setup" with Cancel and Continue buttons

15) On the New Connector Details page, for Name, enter a display name that will be used for this Connector across the portal. Note that if you're connecting multiple Azure tenancies or subscriptions, you'll want to use a name that easily identifies the target tenant/subscription.

Screenshot of a form field labelled Name containing the value wiz-azure-connector

16) Click Finish. Your first scan will be initiated automatically. Wait until the status change to

Wiz Azure connector deployment row showing status Initializing with no sources yet

Active (Note: It will take a few minutes for your resources to appear in Wiz due to the fetching and enrichment processes).

Step 3: Validate the Integration

  • Once the Cloud connector is deployed, Wiz begins to scan the environment using its agentless read-only APIs approach.
  • You will be able to navigate through the scan findings and details, as well as analyse and address issues identified by the workload scanner
Wiz dashboard for an Azure subscription listing compute instance groups and containers with their status and cloud platform

By integrating Microsoft Azure with Wiz, you gain comprehensive visibility and security insights into your cloud environment. This connection ensures continuous monitoring, enabling you to proactively address vulnerabilities and compliance risks. Follow these steps, and you’ll be on your way to enhancing the security posture of your Azure infrastructure.

In upcoming posts, we will share how to use Wiz to further improve security in your Azure tenant. Stay tuned!

Share