Azure Central: incidents and maintenance on Azure VMs

Azure Central investigates and fixes problems on Azure VMs, virtual networks, security rules and managed disks, under the Azure role you assign. On-prem, cloud or hybrid.

REQUEST DEMO

READ THE DOCS

2501's Azure Central specialty investigates and fixes problems on Azure VMs and the services around them, under the Azure role you assign. One agent covers a whole subscription, and it acts only as far as you allow.

A VM stops answering, a managed disk fills up, an operation is refused for lack of a role. Before any fix, someone has to work out whether the network, the disk or the VM is at fault.

What 2501 does

The Azure Central specialty takes these requests from your ticketing system and handles maintenance, incident investigation and remediation across Azure VMs and associated services: virtual networks, network security rules, managed disks, VM add-ons and diagnostics, and Azure Monitor. It works out why a VM cannot be reached, why a service stopped responding, why access is denied or where configuration has drifted. Where you allow it, it restarts, resizes or redeploys a VM, or grows a disk that has filled. It works from one central VM in your Azure network and stays within its subscription, and when a ticket could mean more than one resource, it asks a person which one. What it changed, and why, is always reported.

Scope map of 2501's Azure Central: within the role you assign, it restarts, resizes or redeploys Azure VMs, grows full managed disks and reads virtual networks, network security rules, VM add-ons, diagnostics and Azure Monitor to find why access is denied or configuration drifted; a person says which resource an unclear ticket means, and other subscriptions are never touched.

You stay in control

You choose the level, per specialty: investigate only, act after a person confirms, or act on its own within your rules.
The Azure role is the hard limit: an agent whose role only lets it read cannot resize or delete a VM, whatever a ticket says.
Your rules decide which resources are in scope, and destructive commands can be blacklisted outright.
On-prem, cloud or hybrid: 2501 runs wherever you do. On-prem, no data leaves your network.

Frequently asked

Do we register every Azure VM with 2501? No. One agent handles the subscription from a central VM.

Is this the same as running 2501 on Azure OpenAI? No. Azure Central operates your infrastructure. The model the agents run on is a separate choice, and it can be your own Azure OpenAI deployment.

Problems it handles

Each page is one kind of ticket, and how this specialty handles it within the limits you set.

An Azure VM that stops answering answers again after 2501 finds whether the network rules, the VM or the system inside it is at fault and applies the fix that matches the cause

Problem

Azure VM unreachable

An Azure VM stops answering and a restart is the reflex. How 2501 finds whether the network, the VM or the system inside it is at fault, and fixes it within your limits.

See how it is handled

Azure Central: incidents and maintenance on Azure VMs

What 2501 does

You stay in control

Frequently asked

Related

Problems it handles

SEE IT ON YOUR OWN INFRASTRUCTURE