Deploy a trusted security partner (preview)
Azure Firewall Manager is currently a managed public preview.
Trusted security partners in Azure Firewall Manager allows you to use your familiar, best-in-breed third-party security-as-a-service (SECaaS) offerings to protect Internet access for your users.
To learn more about supported scenarios and best practice guidelines, see What are trusted security partners (preview)?.
The supported security partners are ZScaler and iboss for this preview. Supported regions are WestCentralUS, NorthCentralUS, WestUS, WestUS2, and EastUS.
Azure Firewall Manager Preview must be explicitly enabled using the
Register-AzProviderFeature PowerShell command.
From a PowerShell command prompt, run the following commands:
connect-azaccount Register-AzProviderFeature -FeatureName AllowCortexSecurity -ProviderNamespace Microsoft.Network
It takes up to 30 minutes for the feature registration to complete. Run the following command to check your registration status:
Get-AzProviderFeature -FeatureName AllowCortexSecurity -ProviderNamespace Microsoft.Network
Deploy a third-party security provider in a new hub
- Sign in to the Azure portal at https://portal.azure.com.
- In Search, type Firewall Manager and select it under Services.
- Navigate to Getting Started. Select Create a Secured Virtual Hub.
- Enter you subscription and resource group, select a supported region, and add your hub and virtual WAN information.
- Deploy VPN gateway is enabled by default. A VPN Gateway is required to deploy a Trusted security partner in the hub.
- Select Next: Azure Firewall
Trusted security partners connect to your hub using VPN Gateway tunnels. If you delete the VPN Gateway, the connections to your Trusted security partners are lost.
- If you want to deploy Azure Firewall to filter private traffic along with third-party service provider to filter Internet traffic, select a policy for Azure Firewall. See the supported scenarios.
- If you want to only deploy a third-party security provider in the hub, select Azure Firewall: Enabled/Disabled to set it to Disabled.
- Select Next: Trusted Security Partners.
- Select Trusted Security Partner to set it to Enabled. Select a partner.
- Select Next.
- Review the content and then select Create.
The VPN gateway deployment can take more than 30 minutes.
To verify that the hub has been created, navigate to Azure Firewall Manager->Secured Hubs. Select the hub->Overview page to show the partner name and the status as Security Connection Pending.
Once the hub is created and the security partner is set up, continue on to connect the security provider to the hub.
Deploy a third-party security provider in an existing hub
You can also select an existing hub in a Virtual WAN and convert that to a secured virtual hub.
- In Getting Started, select Convert Existing Hubs.
- Select a subscription and an existing hub. Follow rest of the steps to deploy a third-party provider in a new hub.
Remember that a VPN gateway must be deployed to convert an existing hub to secured hub with third-party providers.
Configure third-party security providers to connect to a secured hub
To set up tunnels to your virtual hub’s VPN Gateway, third-party providers need access rights to your hub. To do this, associate a service principal with your subscription or resource group, and grant access rights. You then must give these credentials to the third-party using their portal.
Create Azure Active Directory (AD) service principal: You can skip the redirect URL.
Add access rights and scope for the service principal. How to: Use the portal to create an Azure AD application and service principal that can access resources
You can limit access to only your resource group for more granular control.
Follow the ZScaler: Configuring a Microsoft Azure Virtual WAN Integration instructions to:
- Sign in to the partner portal and add your credentials to give the trusted partner access to your secured hub.
- Sync the virtual hubs in the partner portal, and set up the tunnel to the virtual hub. You can do so once your Azure AD authentication credentials are validated.
You can look at the tunnel creation status on the Azure Virtual WAN portal in Azure. Once the tunnels show connected on both Azure and the partner portal, continue with the next steps to set up routes to select which branches and VNets should send Internet traffic to the partner.
Configure route settings
Browse to the Azure Firewall Manager -> Secured Hubs.
Select a hub. The Hub status should now show Provisioned instead of Security Connection Pending.
Ensure the third-party provider can connect to the hub. The tunnels on the VPN gateway should be in a Connected state. This state is more reflective of the connection health between the hub and the third-party partner, compared to previous status.
Select the hub, and navigate to Route Settings.
When you deploy a third-party provider into the hub, it converts the hub into a secured virtual hub. This ensures that the third-party provider is advertising a 0.0.0.0/0 (default) route to the hub. However, VNet connections and sites connected to the hub don’t get this route unless you opt-in on which connections should get this default route.
Under Internet traffic, select VNet-to-Internet or Branch-to-Internet or both so routes are configured send via the third party.
This only indicates which type of traffic should be routed to the hub, but it doesn’t affect the routes on VNets or branches yet. These routes are not propagated to all VNets/branches attached to the hub by default.
You must select secure connections and select the connections on which these routes should be set. This indicates which VNets/branches can start sending Internet traffic to the third-party provider.
From Route settings, select Secure connections under Internet traffic, then select the VNet or branches (sites in Virtual WAN) to be secured. Select Secure Internet traffic.
Navigate back to the hubs page. The hub’s Trusted security partner status should now be Secured.
Branch or VNet Internet traffic via third-party service
Next, you can check if VNet virtual machines or the branch site can access the Internet and validate that the traffic is flowing to the third-party service.
After finishing the route setting steps, the VNet virtual machines as well as the branch sites are sent a 0/0 to third party service route. You can't RDP or SSH into these virtual machines. To sign in, you can deploy the Azure Bastion service in a peered VNet.