Skip to main content

What should I do if I suspect that one of Azure Services is not available or there is a quality degradation?

By
This post will be short and I will try to response to the following question:
What should I do if I suspect that one of Azure Services is not available or there is a quality degradation?
Checklist:

1. Check Azure Status (https://azure.microsoft.com/en-us/status) 

You will be able to find in real time information related to interruption and service degradation at world wide level. All the issues and problem are reported on this page. In this way you can know if there are (known) issues on Azure.

2. Check Azure Portal for Alerts
The new portal will notified you about different issues that can appear in the system. For example when you reach a limitation of your service (throughput) you will be notified about it (before reaching it). Don't forget that you can redirect this alerts on your email.


3. Check your service instance status on Azure Portal 
 At this step you want to be sure that your service status is green and the configuration is good. I had situations when somebody reset the access configuration or change a configuration without notify all the teams that are impacted and make a double check.

4. Check Azure Audit Logs
You might be surprised to find out that you can find very useful information about what happen in the system.

5. Check your inbox (operations)
When the services that you are using  are impacted by different operations that are done on Azure, you will be notified in advance. It is simple to miss this kind of information. For example that a major update will be done on specific VMs and you might be impacted (when you have don't have redundancy).

6. Check your inbox (notifications)
It is so easy to miss an email that notifies you that you have problem with the credit card that is connected to your Azure Subscription or situations like this. I remember one time when our credit card expired and we missed the email that notified us that in the last 3m payment was not done.

7. Open a support ticket
You can any time to open a support ticket. But, before doing this you should be 100% sure that the problem is not from your side. I'm happy to say that until now all the time the issues were because of us (when Azure Status was green) and not from Azure.

In this post I didn't talked about what you can do monitor your system. That is a long and complex story that I might write in future.

You should remember to:
  • Check Azure Status
  • Check Azure Portal
  • Check your Email

Labels:

Comments

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

By
After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(
Post a Comment
Read more

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

By
Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see
8 comments
Read more

Navigating Cloud Strategy after Azure Central US Region Outage

By
 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provided a too
Post a Comment
Read more