Azure offers a wide range of SKUs to cater to different workloads and requirements. There are over 30 SKUs available, each with its unique characteristics and pricing models.
To choose the right Azure SKU, consider the type of workload you're running. If you're using a small to medium-sized business application, a General Purpose v2 SKU might be a good fit.
Each SKU has its own set of features and limitations. For example, the Basic SKU is designed for small workloads and offers a lower price point, but it also has limited storage and memory.
Understanding the different SKUs and their pricing models is crucial to making an informed decision. Be sure to review the pricing calculator to get an accurate estimate of the costs involved.
Azure SKU Features
Azure SKU Features are designed to provide a clear understanding of the capabilities and limitations of each SKU.
ResourceSkuCapabilities describe the SKU capabilities object, which includes the scale type applicable to the sku.
Capabilities
Capabilities play a crucial role in determining the functionality of an Azure SKU. There are two types of capabilities to consider: scale type and zonal capabilities.
The scale type applicable to the sku is described by the ResourceSkuCapabilities object. This object outlines the scale type available for the SKU.
A SKU's zonal capabilities are detailed in the ResourceSkuZoneDetails object. This object provides a list of capabilities available for the SKU in specified zones.
Here are the types of capabilities available for a SKU in a zonal setup:
In a zonal setup, a list of capabilities is available for each zone. This list is described by the capabilities property, which is an array of ResourceSkuCapabilities objects.
Result
The result of listing Resource Skus is a crucial part of the Azure SKU features.
The List Resource Skus operation response is stored in the ResourceSkusResult object.
The response contains a URI to fetch the next page of Resource Skus, which can be used to call ListNext().
The list of skus available for the subscription is also included in the response, stored in a ResourceSku[] array called value.
Here are the details of the ResourceSkusResult object:
Azure SKU Planning
Azure SKU Planning is a crucial step in setting up your Azure App Service. The Basic service plan is designed for low-traffic workloads, with pricing based on instance size and number.
The Basic plan offers three instances: B1, B2, and B3, each with varying core and RAM configurations. The B1 instance has 1 core and 1.75 GB of RAM, while the B3 instance has 4 cores and 7 GB of RAM.
If you need more advanced features, consider the Isolated v2 Service Plan, which offers higher core and RAM configurations. This plan is designed for high-scale workloads and provides fine-grained control over network traffic.
Restrictions
Restrictions play a significant role in Azure SKU planning. You can reference one SKU, never both, when using a standalone virtual machine resource, availability set resource, or virtual machine scale set resource.
Moving resources can also be tricky. Move operations have specific requirements, but the article doesn't provide further details on this topic.
ResourceSkuRestrictions is a crucial concept to understand. It includes a reasonCode, restrictionInfo, type, and values. The reasonCode describes the reason for the restriction, while the restrictionInfo provides information about the restriction where the SKU cannot be used.
The type of restrictions is also important. It can be one of several types, but the article doesn't specify what those types are. The values field contains a list of strings, which can include different locations where the SKU is restricted.
You can further explore the restriction info by looking at the ResourceSkuRestrictionInfo. This includes locations and zones where the SKU is restricted. Locations are simply a list of strings, while zones are a list of availability zones.
Extended locations are also worth considering. ResourceSkuLocationInfo describes an available Compute SKU Location Information. This includes extended locations, location, type, zone details, and zones. Extended locations are a list of strings, while location is a single string. Type is an ExtendedLocationType, which is not specified in the article. Zone details are a list of ResourceSkuZoneDetails, and zones are a list of strings.
Capacity
Capacity is a crucial aspect of Azure SKU planning. It determines the maximum amount of resources that can be allocated to an instance.
The default capacity is the starting point for any SKU, and it's an integer value. You can think of it as the minimum amount of resources that will be allocated to an instance.
Maximum capacity, on the other hand, is the highest amount of resources that can be set for a SKU. This is also an integer value, and it represents the upper limit of resources that can be allocated.
Minimum capacity is another important value, representing the lowest amount of resources that can be allocated to an instance.
Here's a summary of the different capacity values:
The scale type applicable to a SKU is determined by the ResourceSkuCapacityScaleType. This value helps you understand how the capacity can be scaled.
Build, Deploy, and Scale Web Apps Globally
Building and deploying web apps globally is a breeze with Azure App Service. It's a fully managed platform-as-a-service optimized for web and API applications.
You can choose from a range of plans, including Free, Basic, Premium, and Isolated Environment, making it a cost-effective option. The Free plan is a great starting point for small projects or proof-of-concepts.
Azure App Service is available in multiple locations around the world, allowing you to deploy your apps close to your users and improve their experience. This is especially important for large-scale applications that need to be highly available.
With App Service, you can rapidly migrate, modernize, and build web and API apps in the cloud. This means you can quickly adapt to changing business needs and stay competitive.
To learn more about App Service features and capabilities, you can visit the dedicated page for more information.
Frequently Asked Questions
What does SKU mean in Load Balancer?
In Azure Load Balancer, a SKU (Stock-Keeping Unit) refers to a specific version or tier of the service, each with its own set of features and pricing. Understanding the different SKUs can help you choose the right Load Balancer for your application's needs.
What is VM SKUs in Azure?
In Azure, VM SKUs (Stock Keeping Units) define the characteristics, capabilities, and pricing of virtual machines, including performance levels and features. Each SKU represents a specific version or offering of a virtual machine, helping you choose the right one for your needs.
How do I check my Azure VM SKU?
To check your Azure VM SKU, sign in to the Azure portal and navigate to your bastion host's Configuration page, where you can view and compare available Tier options. Here, you can see how the SKU affects the features available for your bastion host.
What is the SKU capacity of VMSS?
The SKU capacity of VMSS refers to the maximum number of instances allowed, which can be upgraded using the command $vmss.sku.capacity = 5. Upgrading SKU capacity does not increase the number of running instances, but rather sets the maximum allowed instances.
What is basic and standard SKU in Azure?
In Azure, Basic SKU refers to a public IP address without availability zones, while Standard SKU allows association with virtual machines or load balancer front ends. Understanding the difference between Basic and Standard SKU is crucial for optimizing your Azure public IP address setup.
Sources
- https://learn.microsoft.com/en-us/azure/load-balancer/skus
- https://learn.microsoft.com/en-us/rest/api/compute/resource-skus/list
- https://www.sqlshack.com/how-to-identify-suitable-skus-for-azure-sql-database-managed-instance-mi-or-sql-server-on-azure-vm/
- https://azure.microsoft.com/en-us/pricing
- https://azure.microsoft.com/en-us/pricing/details/app-service/windows/
Featured Images: pexels.com