This guide walks you through creating a Microsoft Entra application, assigning Azure RBAC roles for Network Watcher flow logs, and gathering the configuration needed to create an Azure Network Security integration with Synqly.
This provider currently supports flow logs written to Azure Blob Storage. Log Analytics destinations are not supported.
Prefer virtual network (VNet) flow logs for new setups. Network security group (NSG) flow logs are still readable when already configured, but Azure blocked creating new NSG flow logs as of June 30, 2025, and plans to retire them on September 30, 2027; migrate to VNet flow logs when possible. See Migrate from NSG flow logs to VNet flow logs.
Before you begin, ensure that you have:
- Access to the Microsoft Entra admin center with the Application Developer role (or other permissions that allow creating an app registration)
- Access to an Azure subscription with a Network Watcher and flow logs publishing to an Azure Storage account
- Permission to assign Azure RBAC roles to a service principal
| Permission | Purpose |
|---|---|
Microsoft.Network/networkWatchers/flowLogs/read | Discover Network Watcher flow log configurations |
| Storage Blob Data Reader | List and download flow log blobs from the destination storage account |
Assign Reader (or a custom role that includes Microsoft.Network/networkWatchers/flowLogs/read) on the Network Watcher resource, resource group, or subscription, and assign Storage Blob Data Reader on the storage account or container that receives flow log data. Control-plane Reader on the storage account alone is not sufficient to download blobs.
- Sign in to the Microsoft Entra admin center with an account that can create app registrations.
- Go to Entra ID → App registrations, then select New registration.
- Enter a Name for the application.
- For Supported account types, choose Accounts in this organizational directory only (single tenant) unless you need a multi-tenant app. If you are unsure, choose the single-tenant option. For more information, see Tenancy in Microsoft Entra ID.
- Select Register.
- On the Overview page, copy the Application (client) ID and Directory (tenant) ID and store them in a safe location.
For more details, see Register an application with the Microsoft identity platform.
- In the app registration, go to Certificates & secrets → Client secrets.
- Select New client secret, enter a description and expiration, then select Add.
- Copy the secret Value immediately and store it with the client ID and tenant ID. You will not be able to view the value again after you leave the page.
Assign the roles from Required Permissions to the application's service principal.
Assign Reader on the Network Watcher scope:
- In the Azure portal, navigate to the Network Watcher resource (or the resource group or subscription that contains it).
- Go to Access control (IAM) → + Add → Add role assignment.
- Search for Reader, select it, and click Next.
- Click + Select members, add the application from step 1, and click Select.
- Click Review + assign.
Assign Storage Blob Data Reader on the flow log storage account:
- In the Azure portal, navigate to the storage account (or container) that receives Network Watcher flow logs.
- Go to Access control (IAM) → + Add → Add role assignment.
- Search for Storage Blob Data Reader, select it, and click Next.
- Click + Select members, add the application from step 1, and click Select.
- Click Review + assign.
For more details, see Assign Azure roles using the Azure portal.
- In the Azure portal, navigate to your Network Watcher resource.
- On the Overview page, note the following values:
- Subscription ID
- Resource group
- Name (Network Watcher name)
Create your integration by supplying the following values.
| Integration Parameter | Description |
|---|---|
| Client ID | The Application (client) ID from the Entra app registration Overview page |
| Client Secret | The client secret Value from Certificates & secrets |
| Tenant ID | The Directory (tenant) ID from the Entra app registration Overview page |
| Subscription ID | The Azure subscription ID that contains the Network Watcher |
| Resource Group | The Azure resource group name that contains the Network Watcher |
| Network Watcher Name | The name of the Network Watcher resource |
| Azure Cloud (optional) | Microsoft cloud environment. public (default) or government |
| Traffic Log Configuration IDs (optional) | Flow log short names or full ARM IDs ending in .../flowLogs/{name}. When omitted, all configurations discoverable by the Network Watcher are used |