Skip to main content

Azure Quotes - Cores per subscription at Azure Region level

Each Azure Subscription had a default quotas service limits. You can check this quotas on the following Azure page https://azure.microsoft.com/en-gb/documentation/articles/azure-subscription-service-limits/.
This values are set by default and can be increased easily by creating a new support requests.
In the new portal there is even a special support request template for this kind of scenarios.
I was surprised how fast the support team responded to my requests. In under 15 minutes a part of the quotas were changed of I was contacted to confirm the change.

Core Limitation
Let's talk a little about Core limitation. The default value is 20. This means that you can have allocated maximum 20 CPU Cores (VMs, Web Roles, Worker Roles, ...). The maximum public limit is 10.000 cores, but the interesting thing will happen in the moment when you want to change this limit and you do a request for it.
You will need to specify not only the number of cores that you need (let's assume 100), but also the location (West Europe for example).

What does this mean?
It means, that on that subscription you can consume maximum 100 cores in that region and for other regions you have a limit of 20 cores. Don't forget that you can increase this limit for each region separately.
On top of this don't forget that there are two different limits for cores. One is for the classical Core Service and another one for the new ones ('Resource Manager Cores').

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

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

Navigating Cloud Strategy after Azure Central US Region Outage

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