Introduction
Purpose and Scope of This Guide
This guide covers the planning, deployment, configuration, migration, and ongoing maintenance of ADAudit Plus across all supported hosting environments.
It is intended for IT administrators, system architects, and infrastructure teams responsible for deploying or evaluating ADAudit Plus in self-hosted or cloud environments.
The guide covers both supported deployment models end to end:
- On-Premises Deployment — installing ADAudit Plus on a VM within your own datacenter or private infrastructure
- Cloud-Hosted Deployment (BYOC) — installing ADAudit Plus on a VM hosted within your own cloud account (AWS, Azure, GCP, OCI, IBM Cloud)
Deployment Types Covered
| Deployment Type | Hosting | Data Collection | Public Endpoint |
|---|---|---|---|
| On-Premises Deployment | Customer datacenter or private infrastructure | Agentless and/or agent-based | Not required |
| Cloud-Hosted Deployment (BYOC) | Customer cloud account (AWS/Azure/GCP/OCI/IBM) | Agent-based only | Required |
Both models deliver identical ADAudit Plus product features. The deployment environment and data collection architecture differ; the product capability does not.
Terminology and Alternate Names
The following terms are used consistently throughout this guide. Alternate names are listed for reference where customers may encounter different terminology.
| Primary Term | Alternate Names |
|---|---|
| On-Premises Deployment | Self-hosted deployment, private datacenter deployment |
| Cloud-Hosted Deployment (BYOC) | Bring Your Own Cloud, private cloud deployment, hybrid cloud deployment, BYOC |
| Public Endpoint | Reverse proxy, load balancer, application gateway, NAT |
| Agent | ADAudit Plus agent, data collection agent |
| Agentless | RPC-based collection, network-based collection |
| BYOL | Bring Your Own License |
Note Cloud-Hosted (BYOC) deployment covers all monitored endpoint scenarios — on-premises endpoints, cloud endpoints, or a hybrid of both. The ADAudit Plus installation and configuration is identical in all cases. Only the location of monitored endpoints differs.