Request the Azure server
When your cloud team creates the servers in your Azure subscription, send them one short request. They create a Linux virtual machine whose managed identity can only read; you install Excubius on it afterwards over SSH, and you do not need the cloud team again. This guide lists what to ask for and gives you the request to copy.
Before you begin
Collect these values. The request uses them as placeholders in angle brackets.
| Placeholder | What it is | Example |
|---|---|---|
<subscription> | The subscription that holds the server and, usually, what you monitor | Production |
<resource-group> | A resource group for the server; a dedicated one is easiest to manage | rg-monitoring |
<monitoring-vm> | The name of the virtual machine | vm-monitoring-01 |
<subnet> | A subnet with a route to the SQL Server virtual machines, the availability group listeners and any private endpoints you will monitor | snet-management |
<monitoring.example.com> | The name users will open | monitoring.example.com |
<my-user> and the SSH key | Your administrator account on the server and your SSH public key | opsadmin, ssh-ed25519 AAAA… |
<my-ip> | The address you connect from over SSH | 203.0.113.10 |
<ninjaone-region> | Only when you use NinjaOne as a source: the region of your NinjaOne instance | app |
Decide one more thing: whether people reach Excubius directly on the server's public address, or through a gateway such as Azure Application Gateway or Front Door that ends TLS in front of it.
What to ask for
The virtual machine
| Item | Value |
|---|---|
| Image | Rocky Linux 9 from the Azure Marketplace: publisher resf, offer rockylinux-x86_64, plan 9-base |
| Size | Standard_B2ms (2 vCPU, 8 GiB) to start. It can be resized later |
| Operating system disk | 64 GiB, Premium SSD |
| Identity | A system-assigned managed identity with the read-only roles below |
| Administrator | <my-user> with sudo, signing in with your SSH public key; password sign-in turned off |
The first Rocky Linux machine in a subscription needs the Marketplace terms accepted once:
az vm image terms accept --publisher resf --offer rockylinux-x86_64 --plan 9-base
Read-only roles for the managed identity
Each role is assigned on the subscription. None of them can change anything; Excubius never writes to what it monitors.
| Role | Role definition ID | Used for |
|---|---|---|
| Reader | acdd72a7-3385-48ef-bd42-f606fba81ae7 | Inventory and configuration of Azure resources through Azure Resource Graph |
| Monitoring Reader | 43d0d8ad-25c7-4714-9337-8ba259a9fe05 | Azure Monitor metrics and alerts |
| Security Reader | 39bc4728-0917-49c7-9d2c-d95423bc2eb4 | Microsoft Defender for Cloud assessments, used by the security modules. Leave it out if you will not use them |
To monitor more subscriptions later, the same roles are assigned to the same identity on each of them. Ask the cloud team for the identity's object (principal) ID so you can request that later without looking it up.
Network security group
| Direction | Port | Source or destination | Purpose |
|---|---|---|---|
| Inbound | 443 | The internet, or your company's address ranges | The web console, sign-in and webhooks |
| Inbound | 80 | The internet | Redirect to HTTPS and Let's Encrypt validation over HTTP |
| Inbound | 22 | <my-ip>/32 | Administration over SSH |
| Outbound | 443 | *.azure.com, *.microsoft.com | Azure APIs and Microsoft sign-in |
| Outbound | 443 | ghcr.io, docker.io | Container images, unless you install with the offline package |
| Outbound | 443 | slack.com | Slack notifications |
| Outbound | 443 | api.newrelic.com, <ninjaone-region>.ninjarmm.com | New Relic and NinjaOne, when you use them as sources |
| Outbound | 443 | endoflife.date, api.msrc.microsoft.com, dataplat.github.io, raw.githubusercontent.com | Public feeds of the updates and advisories module |
| Outbound | 443 | The Let's Encrypt API | Certificates, when you use Let's Encrypt |
Inside the virtual network, the server connects to what it monitors: 1433 for SQL Server (and UDP 1434 for named instances without a fixed port), 5432 for PostgreSQL, 5986 for WinRM over HTTPS and 22 for SSH. Nothing connects to the server's collector.
Public address, name and backup
- A static public IP address with the name
<monitoring.example.com>pointing at it. With a gateway in front, the gateway ends TLS and the server needs only port 80 from the gateway. - The virtual machine in your existing Azure Backup policy. Daily is enough; Excubius also keeps its own database backups on the disk.
Send the request
- Replace the placeholders in the request below with your values. Remove the Security Reader line if you will not use the security modules, and the New Relic or NinjaOne addresses if you will not use those sources.
- Copy the request and send it through your usual channel, for example a ticket to the cloud team.
- When the server exists, check that you can connect with
ssh <my-user>@<monitoring.example.com>and runsudo -v.
Subject: Resources for the monitoring server
Hello,
To install our monitoring platform we need one Linux virtual machine in the
<subscription> subscription. Nothing has to be installed on it; we install
the platform ourselves over SSH.
1. Virtual machine
- Image: Rocky Linux 9, Marketplace publisher resf, offer rockylinux-x86_64,
plan 9-base (accept the terms once: az vm image terms accept
--publisher resf --offer rockylinux-x86_64 --plan 9-base)
- Size: Standard_B2ms (2 vCPU, 8 GiB); we may ask to resize it later
- OS disk: 64 GiB Premium SSD
- Name and resource group: <monitoring-vm> in <resource-group>
- Network: subnet <subnet>, with a route to the SQL Server VMs, the
availability group listeners and the private endpoints to monitor
- Administrator: <my-user> with sudo, SSH public key below,
password sign-in disabled
2. Managed identity (read-only)
System-assigned managed identity with these roles on the subscription:
- Reader acdd72a7-3385-48ef-bd42-f606fba81ae7
- Monitoring Reader 43d0d8ad-25c7-4714-9337-8ba259a9fe05
- Security Reader 39bc4728-0917-49c7-9d2c-d95423bc2eb4
Please send us the identity's object (principal) ID.
3. Network security group
Inbound 443 from the internet (or our ranges) web console and sign-in
Inbound 80 from the internet HTTPS redirect, certificates
Inbound 22 from <my-ip>/32 administration over SSH
Outbound 443 to *.azure.com, *.microsoft.com, ghcr.io, docker.io,
slack.com, api.newrelic.com, <ninjaone-region>.ninjarmm.com,
endoflife.date, api.msrc.microsoft.com, dataplat.github.io,
raw.githubusercontent.com, Let's Encrypt
Inside the VNet: outbound 1433 (SQL Server), UDP 1434 (named instances),
5432 (PostgreSQL), 5986 (WinRM over HTTPS), 22 (SSH).
4. Public IP and DNS
A static public IP and the name <monitoring.example.com> pointing at it.
5. Backup
Please include the VM in the existing Azure Backup policy (daily).
SSH public key:
<ssh-ed25519 AAAA... my-user@workstation>
Thank you.
The cloud team's part ends here. Everything else, including the monitoring logins, the sign-in app registration and Slack, is done by you and does not need them.