> For the complete documentation index, see [llms.txt](https://docs.hivel.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hivel.ai/self-managed-hivel-deployment/virtual-private-cloud/azure/hivel-on-premises-deployment-guide-azure/verification-and-access.md).

# Verification and Access

On-Prem Deployment Guide (Azure)

**Your deployment is complete when every item below is true:**

* All VM containers show Up/healthy in docker ps.
* Every endpoint in Test Service Endpoints below returns a healthy response.
* The application is reachable at the address you configured in Access Hivel Application below.
* At least one integration (Jira/GitHub/GitLab) has been connected and shows data in the UI.

### Validation Checklist

<table data-header-hidden data-search="false"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>Check</strong></td><td><strong>How to verify</strong></td></tr><tr><td>Database connectivity</td><td>psql "host=$DB_HOST port=5432 dbname=insightly user= sslmode=require" connects from VM</td></tr><tr><td>Cache/queue (Redis)</td><td>docker exec -it insightly-redis redis-cli ping returns PONG on VM</td></tr><tr><td>API readiness</td><td>curl <code>http://localhost:80/health</code> returns healthy on VM</td></tr><tr><td>UI access</td><td>UI loads at http://&#x3C;vm-public-ip>:3000 with no console errors</td></tr><tr><td>Integration connectivity</td><td>Connected Jira/GitHub/GitLab shows "connected" status in the UI</td></tr><tr><td>First-data confirmation</td><td>Open the relevant dashboard in the Hivel UI for the integration you just connected (e.g. Jira/GitHub/GitLab) - records/metrics appearing there confirm data is flowing. This is the primary supported signal for on-prem/VPC deployments</td></tr></tbody></table>

### Step 1: Verify Services Are Running

**On VM:**

```
# Check all containers
docker ps
 
# Check service health
./deploy.sh --health
 
# Check specific service
./deploy.sh --health auth-svc
```

### Step 2: Test Service Endpoints

**On VM:**

```
# Test API Gateway
curl http://localhost:80/health
 
# Test Auth Service
curl http://localhost:8095/health
 
# Test Insightly Service
curl http://localhost:8082/hivelapi/health
 
# Test UI
curl http://localhost:3000
```

### Step 3: Access Hivel Application

Once all services are healthy, access Hivel using one of these methods:

**Option A: Quick test / pilot - Direct VM Public IP**

Choose this only for quick testing or pilots - not recommended for production (no load balancing, and no HTTPS unless you add the Caddy option in DNS Setup).

* Web UI: `http://\<vm-public-ip>:3000`
* API Gateway: `http://\<vm-public-ip>`

\
**Option B: Azure Load Balancer**

Choose this when you need a stable, health-checked entry point but don't require a custom domain yet.

1. Create a Standard Load Balancer in the Azure Portal
2. Configure a backend pool pointing to VM (ports 80, 3000)
3. Configure health probes and load balancing rules
4. Access via the Load Balancer's public IP or DNS name

\
**Option C: Recommended for production - Azure DNS + Load Balancer**

Choose this for customer-facing production deployments. If you'd rather not stand up a full Load Balancer or Application Gateway, the lighter-weight Caddy option in DNS Setup achieves the same HTTPS outcome for smaller deployments.

1\. Create a Load Balancer (as above) or Application Gateway

2\. Create an Azure DNS zone for your domain

3\. Create an A record pointing to the Load Balancer's public IP

4\. Configure an SSL/TLS certificate (Application Gateway or Key Vault-managed certificate) for HTTPS

5\. Access via custom domain: ***<https://your-domain.com>***

**Next step:** [Troubleshooting](/self-managed-hivel-deployment/virtual-private-cloud/azure/hivel-on-premises-deployment-guide-azure/troubleshooting.md) - if anything above fails.

Otherwise create your first admin account and connect your integrations - see [Application Setup Guide](/self-managed-hivel-deployment/virtual-private-cloud/aws/hivel-on-premises-deployment-guide-aws/application-setup-guide-user-sign-up-and-integration.md): User Sign-up and Integration&#x20;

then review&#x20;

[Backup and Restore](/self-managed-hivel-deployment/virtual-private-cloud/azure/hivel-on-premises-deployment-guide-azure/backup-and-restore.md),

[Upgrade and Rollback](/self-managed-hivel-deployment/virtual-private-cloud/azure/hivel-on-premises-deployment-guide-azure/upgrade-and-rollback.md),&#x20;

[Uninstall and Cleanup](/self-managed-hivel-deployment/virtual-private-cloud/azure/hivel-on-premises-deployment-guide-azure/uninstall-and-cleanup.md) and

&#x20;[Security and Secrets](/self-managed-hivel-deployment/virtual-private-cloud/azure/hivel-on-premises-deployment-guide-azure/security-and-secrets.md) to prepare for ongoing operations.

{% columns %}
{% column %} <a href="/self-managed-hivel-deployment/virtual-private-cloud/azure/hivel-on-premises-deployment-guide-azure/log-rotation-setup.md" class="button primary" data-icon="backward">Log Rotation Setup</a>
{% endcolumn %}

{% column %}

{% endcolumn %}

{% column %} <a href="/self-managed-hivel-deployment/virtual-private-cloud/azure/hivel-on-premises-deployment-guide-azure/application-setup-guide-user-sign-up-and-integration.md" class="button primary" data-icon="forward">Application Setup Guide</a>
{% endcolumn %}
{% endcolumns %}