based on user reports and queries over the last 24 hours
Microsoft Azure outage statistics
- Azure Support at portal.azure.com (New Support Request);
- Azure documentation at learn.microsoft.com/azure;
- Community forums at learn.microsoft.com/answers;
- Stack Overflow with azure tag;
- Twitter support at https://x.com/AzureSupport;
- Azure status page at status.azure.com;
- Premier/Unified support for enterprise customers.
- X (Twitter) - https://x.com/Azure;
- X (Azure Support) - https://x.com/AzureSupport;
- LinkedIn - https://www.linkedin.com/showcase/microsoft-azure;
- YouTube - https://www.youtube.com/c/MicrosoftAzure;
- Official Blog - https://azure.microsoft.com/blog;
- Official Website - https://azure.microsoft.com;
- Status Page - https://status.azure.com;
- Documentation - https://learn.microsoft.com/azure.
When Azure experiences an outage, users may encounter service unavailability, deployment failures, or connectivity issues across regions.
- Check Azure status at status.azure.com/status;
- Visit Azure Service Health in portal.azure.com;
- Check specific service status by region;
- Review Azure status history page;
- Subscribe to RSS feeds for outage notifications;
- Check if specific service or region affected;
- Wait during confirmed outages and monitor updates.
VM issues include startup failures, poor performance, connection errors, or unexpected reboots.
- Check VM status in Azure portal;
- Review boot diagnostics logs;
- Verify sufficient quota available;
- Check if VM deallocated or stopped;
- Restart VM from Azure portal;
- Resize VM if performance inadequate;
- Review metrics for CPU, memory, disk usage;
- Check network security group rules.
Network problems include connection timeouts, DNS resolution failures, or VNet peering issues.
- Verify network security group (NSG) rules;
- Check firewall settings and IP whitelisting;
- Test connectivity using Network Watcher;
- Verify VNet peering configured correctly;
- Check route tables and user-defined routes;
- Test DNS resolution with nslookup;
- Review Application Gateway or Load Balancer logs;
- Verify ExpressRoute or VPN Gateway status.
Authentication problems include login failures, RBAC errors, or subscription access issues.
- Verify Azure AD credentials are correct;
- Check if Multi-Factor Authentication required;
- Review RBAC role assignments in portal;
- Confirm subscription is active and not expired;
- Clear browser cache and cookies;
- Try signing in through incognito mode;
- Check if Conditional Access policies blocking;
- Verify service principal credentials valid.
Deployment issues include template validation errors, quota limits, or resource creation failures.
- Review deployment error messages in portal;
- Check resource quota limits in subscription;
- Validate ARM template syntax with tools;
- Verify resource names meet naming requirements;
- Check if service available in target region;
- Review activity logs for detailed errors;
- Use incremental deployment mode;
- Test deployment in different subscription.
Storage issues include access denied errors, slow performance, or data retrieval failures.
- Verify storage account access keys valid;
- Check SAS token not expired;
- Review storage firewall and virtual network settings;
- Test access using Azure Storage Explorer;
- Check if storage account throttled;
- Verify correct storage tier selected;
- Monitor storage metrics for bottlenecks;
- Check CORS settings for web access.
Database problems include connection timeouts, query performance issues, or failover errors.
- Check database connection string is correct;
- Verify firewall rules allow client IP;
- Review database DTU or vCore usage;
- Enable query performance insights;
- Check if database in read-only mode;
- Test connection from Azure portal query editor;
- Review long-running queries and blocking;
- Configure auto-failover groups if needed.
App Service issues include application errors, slow response times, or deployment failures.
- Check application logs in Azure portal;
- Verify App Service plan not overloaded;
- Review application insights for errors;
- Restart App Service from portal;
- Check deployment slots configured correctly;
- Verify application settings and connection strings;
- Scale up or out if resource constrained;
- Review KUDU console for diagnostics.
Billing issues include unexpected costs, budget overruns, or invoice discrepancies.
- Review cost analysis in Azure portal;
- Check cost management and billing section;
- Set up budget alerts and spending limits;
- Identify top cost resources using cost analysis;
- Review resource usage and rightsizing recommendations;
- Check for orphaned resources consuming costs;
- Delete unused resources and disks;
- Contact billing support for charge disputes.
Monitoring problems include missing metrics, alerts not triggering, or Log Analytics issues.
- Verify diagnostic settings configured properly;
- Check alert rules conditions and thresholds;
- Review action groups configured correctly;
- Wait for metric aggregation period;
- Check Log Analytics workspace retention;
- Verify Azure Monitor agent installed;
- Test alert rules manually;
- Review activity log for alert history.
Microsoft Azure
Your message will be published in about
5 minutes
Service administration will see your message