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

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

Can User Technical Profile Influence AI Architecture Decisions?

In the last few days, I ran a small experiment on Devin/Windsurf/Cascade, BMAD, and LLM-based architecture decisions. The initial concern was simple: if an AI coding assistant knows something about the user, for example, that the user is a Java developer or a .NET developer, can this information influence the architecture and technology stack that the AI will propose? This question is important because many companies are starting to use AI tools not only for coding but also for product discovery, architecture, documentation, and technical decision-making. If the AI is influenced by the developer's personal profile, the result may not be fully neutral. It may look like a business or architecture decision, but in reality, it may be partially shaped by the context of the person using the tool. The test was done using BMAD with Devin/Windsurf/Cascade. The scenario was a unified field service operations platform. The task was to let BMAD refine the product, define the architecture and s...

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