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.

Evolution
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 - https://azure.microsoft.com/en-us/regions/services/.
Another useful dashboard, that can help you a lot during the presales is https://azure.microsoft.com/en-us/regions/. 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.  

Conclusion
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. 

Comments

Popular posts from this blog

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

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(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP