Skip to main content

Azure Status - Real time information about Azure Services Health Status

Last week I had the opportunity to talk with some people that started to take into consideration cloud and Microsoft Azure.
Even if the services and SLA’s were very clear for them, there was a thing that was not clear from them:
How can I know when a service offered by Azure is down? How can I know if the SLA is respected or not (99.9X %)?
They thought that Microsoft is the same as 10 years ago and they don’t share with customers this kind of information.
For them it was a surprise to discover the Current Health Azure Dashboard aka Azure Status and how easy you can see the status of all the services around the globe. In real time you can see the status of each services from all datacenter that are available.
On top of this, on this dashboard you have a History section that can be used to see what services had issues and what was the cause. In this way, all the clients around the world can know exactly what happen when a specific service was down.
Hint: There is a RSS feed for each service. You can use it to integrate this status on your own system/aggregator.
Additional to this portal, customer should know that if an issue of one of Azure services is affecting their services, they are usually notify by support team as soon as possible via email.
If you want to know exactly what is the SLA for different Azure services you should check the following page On this page there are listed all the SLA for all available services. Even if you are a small customer, you will have the same SLA like the big ones. In this moment there are 2 services available that has 4 nines (99.99%) – Traffic Manager and Storage.
Another sources of Azure Status (that are not provided by Microsoft, but aggregates information from Azure services) are:

Unfortunately, in this moment you will not be able to find a portal that can gives you the uptime history for different Azure services. For example in the last 12 month the uptime for Y service was 99.999%.


Popular posts from this blog

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

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 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.51EF 6.0.2VS2013
It seems that there …

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

Fundamental Books of a Software Engineer (version 2018)

More then six years ago I wrote a blog post about fundamental books that any software engineer (developer) should read. Now it is an excellent time to update this list with new entries.

There are 5 different categories of books, that represent the recommended path. For example, you start with Coding books, after that, you read books about Programming, Design and so on.
There are some books about C++ that I recommend not because you shall know C++, only because the concepts that you can learn from it.


Writing solid codeCode completeProgramming Pearls, more programming pearls(recommended)[NEW] Introduction to Algorithms


Refactoring (M. Fowler)Pragmatic ProgrammerClean code[NEW] Software Engineering: A Practitioner's Approach[NEW] The Mythical Man-Month[NEW] The Art of Computer Programming


Applying UML and Patterns (GRASP patterns)C++ coding standards (Sutter, Alexandrescu)The C++ programming language (Stroustrup, Part IV)Object-oriented programming (Peter Coad)P…