Manual deployment
Deploy an Azure Data Source Connector manually without the aid of Vectra provided ARM templates.
Vectra highly recommends the Automated deployment method for most customers.
If you have an existing Azure logging setup that you wish to utilize to provide the required logs to Vectra, then the manual deployment method may be desirable. Other customers may have a desire to manually configure the required logging and not use the Vectra provided ARM templates to automate the process.
Please keep in mind the following if you are interested in the manual deployment method:
Requirements
For manual deployment, please ensure the General Requirements specified earlier have been satisfied.
The requirements below are specific to manual deployment and describe what will need to be created in Azure:
Resource Group
A resource group to contain the storage accounts that will be used to temporarily hold the logs prior to Vectra ingesting them.
Storage Accounts
Vectra recommends that customers configure 4-day retention for all storage accounts.
When using Vectra's automated deployment this is set automatically.
One storage account that can be used for all subscription activity logs.
A storage account for each location/region that has supported resources deployed in it.
When writing logs to a storage account, Azure requires that the storage account be in the region that the resource resides in.
Supported resource types are Automation Accounts, Key Vaults, and Storage Accounts.
Vectra AI - CDR for Azure
This enterprise application / service principal is still required in the manual deployment method.
It requires a role assigned to it that allows it to read from the resource group that was created to contain the storage accounts.
See permissions required post deployment for more details on specific role requirements.
Diagnostic Settings
Need to be applied to each subscription and supported resource:
Any subscription you desire to be monitored by this Azure Data Source should have its platform activity logs sent to the same storage account you created for this purpose.
For subscription logs - include all log categories.
Any supported resource you desire to be monitored by this Azure Data Source should have its logs sent to the storage account you setup for the region/location the resource is deployed in.
For Automation Accounts - only the AuditEvent log type is required.
For Key Vaults - include Audit Logs and Azure Policy Evaluation Details.
For Storage Accounts - only the Audit category group is required.
This includes Storage Read, Storage Write, and Storage Delete categories.
Starting Data Source Connector Setup
This will be done in your Vectra UI at Configuration → Data Sources → Microsoft Azure and begins the process of enabling Vectra to pull logs from your Azure tenant.
Navigate in your Vectra UI (Respond UX) to Configuration → Data Sources > Microsoft Azure and click the + Create Azure Connector button in the top right.
You can expand the Resources area below for links and a demo deployment video.
If Microsoft Azure is not listed as an available Data Source to deploy in your UI, please contact your Vectra account team.

Give your connector a name and then click Create and Continue.

After clicking Create and Continue you will be in a Configuring Azure Connector flow that guides you through the remaining steps that are needed to complete the overall Azure Data Source Connector setup.
If you need to complete other work before your deployment is complete, it’s ok to close this window or just open another browser tab for the other work. You can come back and complete deployment later.
Configuring Azure Connector Overview
Grant Vectra Access
This is the same step as in the automated deployment.
After creating the Azure data source connector name, a link will be given to follow a consent process that creates an Enterprise application (Service Principal) in your Microsoft Azure tenant.
When Vectra collects logs from the storage accounts, we assume this Service Principal in order to read any generated logs.
Select Coverage
Choose the coverage for your connector. Azure CDR (Control Plane) is required and included with every connector. Azure Flow + DNS is an optional add-on, currently in private preview.
Deploy to Azure
For Manual Deployment:
Create resource groups and storage accounts.
Create an assign role to the Vectra AI - CDR for Azure enterprise application.
Setup logging.
If pursuing Flow and DNS log coverage, also set up the additional resources described in the Set Up Flow and DNS Logging section below.
Wait 24 Hours
Even though Vectra's automated deployment is not being used when deploying this Azure Data Source manually, if your manual deployment uses Azure policy to set diagnostic resources, the same concepts still apply.
When a new policy is put in place, Azure will initiate an automated compliance scan to determine which resources are not in compliance with the polices that were just put in place.
There is no set amount of time required or easy way to determine if this scan has been completed.
Provide Log Location
The resource group that contains the storage locations for you Azure logs needs to entered in the Data Source Connector setup dialog to complete the initial deployment process.
Vectra then begins to collect log data from the storage accounts.
1. Grant Vectra Access
In this step you will follow a consent process that allows Vectra to ingest Azure platform logs from the storage locations that will be created in the next step. This consent process creates a trust relationship between your Azure tenant and the Vectra AI Platform using Microsoft’s best practices as described in this Microsoft Document. It uses the Microsoft app registration process and creates an Enterprise Application (aka Service Principal) in your Azure tenant.
Permissions required by the user who will perform the consent process:
Global Administrator in Entra ID (Azure AD)
Please see Appendix 1 - Azure configuration notes for full details about:

Click either on Authorize Vectra in Azure or Copy Authorization Link.
Authorize Vectra in Azure - Opens the link in new tab.
Copy Authorization - Copies the link so you can provide it to someone else.
This is useful when you may not have the required privileges to complete this step.
Remember, you need Global Administrator privileges in Entra ID to accomplish this step.
Step though the following pages, choosing an appropriate entity and logging in if required.
2. Select Coverage

As per the configuring Azure connector steps above, choose the coverage for your connector on this screen:
Azure CDR (Control Plane) — Required and included with every connector. Provides deep visibility into control-plane threats using Azure Activity Logs and key Resource logs.
Azure Flow + DNS — Optional add-on, currently in private preview. Provides data-plane visibility for your Azure workloads using flow logs and DNS logs, enabling detection of threats like exfiltration and port scans.
If you select Azure Flow + DNS, you'll also be asked whether you already have flow logs turned on and collecting. Since you're following the manual deployment path, this doesn't change your steps either way — follow the requirements in Set Up Flow and DNS Logging below regardless of your answer.
3. Deploy to Azure
Create Resource Group and Storage Accounts
Use any method you desire (Azure CLI / Cloud Shell, Azure Portal, custom tooling, etc) to create the required resource group and storage accounts that were specified in the manual deployment requirements. Please note the following:
The naming convention you choose for the resource group and storage accounts does not matter to Vectra. Vectra will read all logs from any storage account in the resource group.
The
resourceGroupIdwill be required later to complete the Vectra Data Source Connector setup that you began in step 1. See below for the format to use (this is just an example):/subscriptions/b3fobfus-cate-dfor-securityeb01ff43e/resourceGroups/rg-vectra-cdr
If you require configuration of private access for the storage accounts created, please see Configuring Private Access for Azure Storage Accounts for details.
Create and Assign Role for Vectra Enterprise App
The Vectra AI - CDR for Azure Enterprise application needs a role with specific permissions assigned to it so that it can read from the storage accounts that you created to temporarily hold the logs to be ingested by this Azure Data Source.
Use any method you desire (Azure CLI / Cloud Shell, Azure Portal, custom tooling, etc) to create the required role and assign it to the Vectra AI - CDR for Azure Enterprise application.
The permissions required post deployment are what need to be assigned to the role. If you have permissions issues, full guidance is available in Appendix 1.
Set up Logging
Use any method you desire (Azure CLI / Cloud Shell, Azure Portal, custom tooling, etc) to create the required diagnostic settings for the Azure platform logs you wish Vectra to analyze.
As per the manual deployment requirements all subscription activity logs for any subscription you want Vectra to monitor should go to the same storage account in the resource group.
Also, remember that Azure will require each supported resource to log to a storage account that is in the same location/region that the resource is deployed in.
The log types required for subscriptions and for supported resources is in the table below:
Subscription or Resource Type
Log Categories Required
Example
Subscription
All
Automation Account
AuditEvent
Key Vault
Audit Logs Azure Policy Evaluation Details
Storage Accounts
“audit” category gives Read/Write/Delete (all required) for storage accounts
Set Up Flow and DNS Logging
If you are pursuing Flow and DNS log coverage as part of your manual deployment, configure the following resources using any method you desire (Azure CLI / Cloud Shell, Azure Portal, custom tooling, etc.). You can reuse existing resources that meet these requirements.
The Microsoft.Insights resource provider must be registered in each subscription where you want VNet flow logs collected.
VNet-level flow logs (via Azure Network Watcher) for each VNet you want covered, writing to the same storage accounts used for platform logs (or an equivalent storage account in the same region as the VNet).
It is recommended to disable NSG Flow Logs on the same workloads before enabling VNet Flow Logs, to avoid duplicate traffic recording and additional cost. See Introduction, architecture, and requirements for how VNet Flow Logs differ from NSG Flow Logs.
A DNS Security Policy for each location with VNets you want covered, with each in-scope VNet linked to it (only one DNS Security Policy link is allowed per VNet).
Diagnostic settings on each DNS Security Policy, sending all logs to the same storage accounts used for platform logs.
As with the rest of manual deployment, the Vectra AI – CDR for Azure enterprise application needs a role assigned that lets it read these new resources. See permissions required post deployment for the specific roles needed for Flow and DNS log coverage.
Use Existing VNet Flow Logs
If VNet flow logs are already enabled, you can reuse their existing storage accounts. Choose one of these options to grant Vectra access:
Keep the storage accounts in their existing resource groups (recommended). Assign the following permissions to the
Vectra AI – CDR for Azureservice principal on the resource group containing the storage accounts.Microsoft.Storage/storageAccounts/readMicrosoft.Storage/storageAccounts/blobServices/containers/readMicrosoft.Storage/storageAccounts/blobServices/containers/blobs/read
Move the storage accounts into the Vectra logging resource group. Move the existing flow-log storage accounts into the resource group you created during manual deployment, where Vectra's log-ingestion role is assigned. Storage accounts inherit the role assignment from that resource group.
Moving a storage account changes its Azure resource ID. Follow Microsoft's resource-move guidance, update flow-log configurations and other references to the storage account's new resource ID, and review role assignments after the move. Verify that logs continue to be written and that Vectra can read them. Granting access in place avoids these move-related changes.
With either option, retain the subscription-level Reader access required for source discovery and asset enrichment, and ensure the storage account's network rules allow Vectra access.
You can also use Automated deployment with Flow and DNS log coverage to manage VNets that do not yet have VNet flow logs. The flow-log policy leaves existing configurations and their storage destinations unchanged. Remediation creates flow logs for existing in-scope VNets without a flow-log configuration; new in-scope VNets are covered by the policy automatically. Existing flow-log storage accounts still need one of the access options above.
An existing but disabled VNet flow-log configuration is also left unchanged by the policy. Enable it separately if you want Vectra to ingest its logs.
4. Wait 24 Hours
Even though Vectra's automated deployment is not being used when deploying this Azure Data Source manually, if your manual deployment uses Azure policy to set diagnostic resources, the same concepts could still apply.
When a new policy is put in place, Azure will initiate an automated compliance scan to determine which resources are not in compliance with the polices that were just put in place.
There is no set amount of time required or easy way to determine if this scan has been completed.
Vectra recommends waiting for 24 hours before continuing with this step to ensure that the scan has completed if you will be using remediation policies in your manual deployment to remediate and resources that are not compliant with policy.

Example Reminder Email:

5. Remediate Policies
6. Provide Log Location
To complete the deployment in the Vectra UI, paste the
resourceGroupIdfrom step 3 earlier in the Azure Log Location field and click Save and Complete Setup.

You should see a Setup complete, awaiting first logs message and then a Logs flowing message once Vectra begins processing your logs.
Last updated
Was this helpful?