AzureHound Enterprise System Requirements and Deployment Process

AzureHound Enterprise is a critical element in your deployment that collects and uploads data about your Microsoft Entra ID and Azure environments to your BloodHound Enterprise tenant for processing and analysis.

AzureHound Enterprise supports Windows, Docker, and Kubernetes deployments. Many organizations deploy one AzureHound Enterprise instance per Entra ID tenant. If you deploy AzureHound Enterprise on Windows, it typically runs as a Windows service. You need at least one AzureHound deployment for the tenants in scope and one Entra ID Enterprise Application service instance for each tenant.

Running multiple AzureHound collector instances on a single server requires the collectors to be installed as Scheduled Tasks instead of Windows Services. Installation instructions for such a configuration can be found at: Setting up multiple AzureHound collectors on the same server with scheduled tasks.

While it is possible to run both AzureHound and SharpHound on the same machine, the hardware recommendations for each application persist.

Deployment Process Overview

To deploy a new AzureHound collector:

1. Configure Entra ID and Azure: AzureHound Enterprise Azure Configuration
2. Create your AzureHound configuration: Create an AzureHound Configuration
3. Deploy and maintain AzureHound: Run and Upgrade AzureHound (Windows, Docker, or Kubernetes)

Server Requirements

Hardware

Resource	Minimum	Recommended	Large enterprise
Processor Cores	2 physical cores	4 physical cores	6 physical cores
Memory	4GB RAM	16GB RAM	32GB RAM
Hard disk space	1GB for logging	5GB for logging	20GB for logging

These recommendations should be considered a baseline and may need to be increased depending on the size and complexity of your environments.

Minimums apply to test or development deployments. Where multiple collectors are deployed on a single host, scaling will be necessary to maintain performance.

Software

AzureHound Enterprise supports several deployment options:

• Windows Server 2019+
• .NET 4.7.2+

OR

• Docker

OR

• Kubernetes

Network

• TLS on 443/TCP to your BloodHound Enterprise tenant URL (provided by your account team)
• TLS on 443/TCP to your Azure environment. Required domains are:
  • login.microsoftonline.com
    • Required for authentication to Entra ID and Azure.
  • msidentity.com (CNAME of login.microsoftonline.com)
    • Required for authentication to Entra ID and Azure.
  • graph.microsoft.com
    • Required for collection of attack path data from Microsoft Entra ID.
  • management.azure.com
    • Required for collection of attack path data from Microsoft Azure Resource Manager.

Service Principal Requirements

The AzureHound Enterprise service runs as an Entra ID registered application with a corresponding service principal (Enterprise application).

The application and service principal need permissions to collect data from your tenant as detailed in AzureHound Data Collection and Permissions.