Deployment in Microsoft Azure
Each customer has a dedicated RealmHelm deployment in Microsoft Azure. Use NetPrecedent hosting or deploy in your own Azure subscription.
Hosting options
Responsibilities
| Responsibility | Hosted by NetPrecedent | Your Azure subscription |
|---|---|---|
| Azure subscription | NetPrecedent | You |
| Data location | NetPrecedent's Azure subscription | Your subscription, in the region you choose |
| Deployment | NetPrecedent | You, through the Marketplace offer, with our help |
| Update management | NetPrecedent | Your administrator, or automatic updates |
| Platform monitoring | NetPrecedent | Your team, with alerts to your recipients |
| Database backups | Azure automated backups, managed by NetPrecedent | Azure automated backups in your subscription, with the retention you set |
| Support access | The access needed to operate the platform | Read only. Additional access is time limited and approved by your staff |
| Site agents | You provide a VM or physical machine per site, and we help install | You provide a VM or physical machine per site, and we help install |
| Device credentials | You enter them | You enter them |
Deployment architecture
Site agents connect to local equipment and make outbound HTTPS connections to the appliance.
Security
- Change approval
- A person must approve the exact device changes in the browser.
- Credential storage
- Device credentials are kept in Azure Key Vault and stay hidden once saved. Passwords and keys in backed-up configurations are masked.
- Change history
- Each change records who wrote, approved and ran it, and the output from each device.