Always Free A1 stuck STARTING; one conditional diagnostic reboot rejected with HTTP 409 Conflict
in Arm Compute
Hello,
An existing Always Free VM.Standard.A1.Flex instance (1 OCPU, 4 GB RAM) in
Ashburn has remained STARTING for several days. Fresh official CLI checks on
October 27, 2026 still returned STARTING. We have not established whether the
underlying cause is guest configuration, a blocked operation or infrastructure.
Before another recovery step, we isolated only this instance's dedicated subnet
using a new admin-SSH-only route table and security list. The verified route
permits only the administrator's single address through the existing gateway;
the sole stateful ingress rule permits SSH from that address, with no outbound
initiation rules. Shared route contents and the separate working scheduler's
Tagged:
0