Skip to main content

Azure Regions products and services availability

Cloud is evolving. Nowadays we can say that cloud infrastructure is mature enough to support most of the business scenarios on the market.

This evolution changed also how we see cloud, where Data Centers (Regions) are available and who is the owner of them. Microsoft is the best example for this. In this moment Microsoft has 3 types of Azure Regions:
  • Hosted and managed by Microsoft - public available for all of us
  • Azure Government Regions - exclusively available only for government (solution providers and customers that work with government)
  • Azure "Private" Regions - special Azure Regions where Azure infrastructure runs, but controlled and owned by a data trustee like China or Germany

New times, new problems.
In this moment in time, Microsoft have 32 Azure Regions and 6 additional already announced (coming soon). Each of Azure Region has his own update and delivery timeline. It means that when a new service is launched it will not be available in all 32 Azure Regions.
For regions managed by Microsoft, the updates and delivery of new services arrives faster, but there are other regions like China or Germany the last updates or new services might not be deliver in the same timelines.
A good example is Azure Search that is available in North Europe and West Europe regions but is not available in Germany or UK regions. This means that we need to be aware of what kind of services we are using and to ensure that they are available in the regions where we need them.

Product available per region
When we design our system we need to know exactly what product (service) is available in each region. Microsoft made a lot of improvements in this area. They created a dashboard that allow us to check what service is available in each location -
Another useful dashboard, that can help you a lot during the presales is All the Azure Regions are marked on the map. Additional to this you can find also regions that will be available in the future.

Wait, one more thing
Even if a product is available in a specific region this doesn't mean that the last version is available. A few months ago I encountered some problems with a solution that was deployed in Azure Regions from Europe, USA and Asia. The client extended his business to China where we realised that the Azure Storage version is not the same. Happily, in our case the problem was solved with some updated in code. Temporary we have a branch of our solution for China.
This problems usually occurs for Regions that are not controlled by Microsoft directly and a partner of government is the owner of the data centers. For regions controlled by Microsoft, you will usually find the last version of the product in a short period of time.  

Keep a eye all the time on what Azure products are available in each Azure Region and take into account that new features might not be available immediately in all regions. 


Popular posts from this blog

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&#…

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 …

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…