// SYS.ONLINE — 2501.AI COMMAND INTERFACE
[STATUS: ACTIVE]
2501/Agent specialties/Azure Central/Azure VM unreachable

SOLUTION //

Azure Central

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.

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

ServiceNow or another ITSM

Your rules, confirmation and blacklists

Investigate only, with a person, or on its own

On-prem, cloud or hybrid

SOLUTION_BRIEFING

// HOW 2501 HANDLES IT

When an Azure VM stops answering, a restart or a redeploy is the reflex, but neither helps if a security rule is blocking the way in, and a redeploy also wipes the VM's temporary disk. 2501 finds where the connection fails before it changes anything, then makes the fix that matches the cause, all within limits you set.

Nobody can connect to the VM, or the application on it has gone quiet. The cause can sit in the network rules around it, in the VM or in the system running inside it, and each needs a different fix.

What 2501 does

The Azure Central specialty takes the ticket from your ticketing system and works out which layer is at fault before it acts: the virtual network and its security rules, the VM, or the system inside it. When a ticket could mean more than one VM, it asks a person which one. Where you allow it, it applies the fix the cause calls for, such as a restart or a redeploy, checks that the VM answers again, and reports what it found, what it changed and why.

How 2501 handles an unreachable Azure VM: signal, find whether the network rules, the VM or the system inside it is at fault, apply the fix the cause calls for within your rules, check the VM answers and report what changed and why

You stay in control

  • You choose the level: investigate only, act after a person confirms, or act on its own within your rules. The level is set per specialty, not per ticket.
  • Destructive actions are the exception: nothing is deleted unless a confirmed incident explicitly requires it, and role assignments and identities are not changed without strong cause.
  • It stays in its subscription: other subscriptions and tenants are outside its scope.
  • Your rules apply: which VMs may be restarted or redeployed unattended and which need a person first, and blacklisted commands stay out of reach, whatever a ticket asks for.

Frequently asked

Does a redeploy lose data? The VM keeps its disks and settings, but its temporary disk is wiped and its dynamic addresses can change, so a redeploy is a fix to choose, not a reflex.

Can it find the cause without changing anything? Yes. In investigate-only mode it reports which layer is at fault and the fix it recommends, and changes nothing.

Related

> READY_TO_DEPLOY

SEE IT ON YOUR OWN INFRASTRUCTURE

Book a technical demo and walk through your own environment with the 2501 team.

REQUEST DEMO

CONTACT SALES