# Install azurehound with Homebrew, Nix

Azure Data Exporter for BloodHound. Version 3.0.0 via Homebrew; verified 2026-07-26. Also installable with nix: nix profile install nixpkgs#azurehound.

## Install

```sh
sudo av install brew:azurehound
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install azurehound
```

  Evidence: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#azurehound
```

  Evidence: nixpkgs package indexes: pkgs/by-name/az/azurehound/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

## Package facts

- **Package key:** brew:azurehound
- **Package manager:** Homebrew
- **Version:** 3.0.0
- **Source summary:** Azure Data Exporter for BloodHound
- **Homepage:** <https://github.com/SpecterOps/AzureHound>
- **Repository:** <https://github.com/SpecterOps/AzureHound>
- **Last updated:** 2026-07-26T13:19:55+02:00
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- azurehound (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 3.0.0
## Project history and usage

AzureHound is SpecterOps' Microsoft Azure data collector for BloodHound. It gathers Azure and Microsoft Entra ID relationship data so BloodHound users can reason about identity attack paths in cloud and hybrid environments.

### Project history

AzureHound comes from the BloodHound/SpecterOps ecosystem, extending BloodHound collection beyond traditional Active Directory graph data into Azure tenant data. The official README identifies it as the BloodHound data collector for Microsoft Azure and the official tool for collecting Azure data for BloodHound Community Edition and BloodHound Enterprise.

The public repository provides Go source, release binaries, a rolling release tied to the main branch, and command help for listing tenant data or running a collection service.

### Adoption history

Adoption follows BloodHound's security-operator audience rather than general Azure administration. The input package facts list Homebrew and Nix packages, which is typical for offensive-security and assessment tooling that needs reproducible workstation installs.

The README shows Azure CLI token reuse via `az account get-access-token`, making it convenient for operators who already authenticate with Microsoft's Azure CLI and want to export graph data without a separate browser flow.

### How it is used

Common usage is `azurehound list` with username/password, tenant, JWT, or refresh token options, optionally writing JSON output for BloodHound ingestion. `azurehound configure` and `azurehound start` support service-style collection for BloodHound Enterprise.

The command exposes a `--config` flag with a default config path under the user's config directory. Credential material is supplied through flags, tokens, certificates, or config rather than a separately documented universal credentials file.

### Why package nerds care

For package nerds, AzureHound is a compact Go security CLI with release binaries and a rolling-release channel. It is notable less for broad package coverage than for being a high-signal dependency in BloodHound workflows where exact versioning and tenant-data compatibility matter.

It also illustrates a common packaging boundary in security tools: the package can install a binary, but the meaningful output is sensitive tenant graph data that belongs outside package-manager state.

### Timeline

- 2022: The AzureHound repository exposes a rolling release for binaries built from the main branch.
- 2020s: SpecterOps documents AzureHound as the Azure collector for BloodHound Community Edition and Enterprise.
- 2020s: Homebrew and Nix package entries make AzureHound easy to install on assessment workstations.

### Related projects

- BloodHound Community Edition and BloodHound Enterprise consume the data AzureHound collects.
- Azure CLI can provide Microsoft Graph access tokens reused by AzureHound.
- SharpHound is the related BloodHound collector for Active Directory environments.

### Sources

- SpecterOps BloodHound AzureHound docs
- SpecterOps/AzureHound README and releases
- source_facts.package-manager


## Security Notes

narrow executable package without higher-risk signals.

- **Geiger risk:** green / low
- narrow executable package without higher-risk signals


## Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.


## Configuration files

- Unix: ~/.config/azurehound/config.json

## Credential files

- Windows: C:\Users\Administrator.ROOT\.config\azurehound\key.pem, C:\Users\Administrator.ROOT\.config\azurehound\cert.pem
## Other Package-Manager Records

- Nix - azurehound: normalized package name match | nixpkgs package indexes: pkgs/by-name/az/azurehound/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1


## Combined YAML source

View the package source record on GitHub. [combined/azurehound.yml](https://github.com/mxcl/pkgdb/blob/main/combined/azurehound.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph