Before you start
Capture the current state, preserve recoverable data and record recent changes before remediation. Use production-impacting commands only within an approved maintenance or change window.
Confirm Azure VM state
Check VM power state, instance view and provisioning state. Record when the Agent became unavailable and correlate with recent changes.
Check the guest Agent service
On Windows, verify the Azure VM Agent service is running. Review service events and Agent logs if it repeatedly stops.
Do not repeatedly restart the service without collecting evidence.
Test DNS and outbound access
Test DNS from the VM and validate custom DNS, proxy, NSG, firewall and routing configuration.
RDP can work while Azure management communication fails because outbound management traffic is filtered.
Inspect extensions
Review extension provisioning state and identify whether one extension or all extensions fail. Inspect guest extension logs before reinstalling anything.
Repair and validate
Fix the underlying guest or network problem, then restart the Agent service if required. Use supported Azure repair procedures if the installation is damaged.
Recheck Agent readiness and rerun the failed management operation.
Agent services
Get-Service -Name RdAgent,WindowsAzureGuestAgent -ErrorAction SilentlyContinue | Format-Table Name,Status,StartTypeDNS
Resolve-DnsName management.azure.comConnectivity
Test-NetConnection management.azure.com -Port 443Troubleshooting validation
- Confirm the original symptom is resolved.
- Verify dependent services and application health.
- Review logs or command output for secondary errors.
- Document the root cause and corrective action.
- Retain rollback evidence until the change is accepted.
Frequently Asked Questions
What should I check first?
Capture the current state, exact error, affected scope and recent changes before making changes. Then test the failing layer from the lowest dependency upward.
How do I validate the fix?
Repeat the original failing operation, check dependent services and confirm the issue remains resolved after any required restart or service recovery.
Can this troubleshooting be automated?
Automate read-only diagnostics first. Add remediation only after commands, permissions, logging and rollback behavior have been validated.