Recommendations for Azure
CloudZero analyzes your Azure environment and generates recommendations that identify specific resources where you can reduce costs through reservation purchases. Each recommendation includes the affected resources, the estimated savings, and guidance on how to address it.
For details on how to work with recommendations in the CloudZero UI (search, filter, group, take action), see Recommendations.
Overview of Azure Recommendations
Databases
| Recommendation | What CloudZero identifies |
|---|---|
| Purchase Azure MySQL Database Reservations | Pay-as-you-go spend for Azure Database for MySQL that could be covered by a reservation |
| Purchase Azure PostgreSQL Database Reservations | Pay-as-you-go spend for Azure Database for PostgreSQL that could be covered by a reservation |
| Purchase Azure Redis Cache Reservations | Pay-as-you-go spend for Azure Cache for Redis that could be covered by a reservation |
| Purchase Azure SQL Database Reservations | Pay-as-you-go spend for Azure SQL Database or SQL Managed Instance that could be covered by a reservation |
Storage
| Recommendation | What CloudZero identifies |
|---|---|
| Purchase Azure Premium Disk Reservations | Pay-as-you-go spend for Azure Premium Disk Storage that could be covered by a reservation |
Databases
Purchase Azure MySQL Database Reservations
This recommendation is created when there is pay-as-you-go spend for Azure Database for MySQL Single Server or Azure Database for MySQL Flexible Server, or both, that could be covered by a reservation for compute resources.
Threshold: This recommendation is created if using a reservation on pay-as-you-go spend for Azure Database for MySQL Single Server and Azure Database for MySQL Flexible Server, or both, will save at least $500 based on a 25% savings rate. When pay-as-you-go spend results in savings of less than $500, the recommendation is automatically closed.
How reservations work
- A reservation is a commitment for Azure Database for MySQL Single Server, Azure Database for MySQL Flexible Server use, or both, for a period of one or three years to get a significant discount on the compute costs.
- Existing deployments that are already running, or ones that are newly deployed automatically, that match the criteria set for the reservation will get the benefit. You do not need to assign the reservation to a specific database or managed instance.
How to address this
When you are purchasing a reservation in Azure, you must specify the following:
| Parameter | Description |
|---|---|
| Scope | The vCore reservation's scope can cover one subscription, multiple subscriptions (shared scope), a single resource group, or a management group |
| Region | The Azure region covered by the capacity reservation |
| Deployment Type | The Azure Database for MySQL Flexible Server resource type that you want to buy the reservation for |
| Performance Tier | The service tier for the Azure Database for MySQL Flexible Server instances |
| Term | 1 or 3 years |
| Quantity | The number of vCores to reserve in the selected Azure region and Performance Tier |
Learn more about buying a reservation in the Microsoft documentation.
The size of reservation should be based on the total amount of compute used by the existing or soon-to-be-deployed database or managed instance within a specific region and using the same performance tier and hardware generation. Learn more about how to determine the correct reservation size in the Microsoft documentation.
Additional details
- Single Server Retirement: Azure Database for MySQL Single Server is being retired. Azure strongly recommends upgrading to Azure Database for MySQL Flexible Server. For more information, see the Microsoft documentation.
- Single Server Reservation Availability: New reservations will not be available for Azure Database for MySQL Single Server. Your existing single server reservations remain valid, and you can still purchase reservations for Azure Database for MySQL Flexible Server.
- Upfront Payment: Reservations are charged upfront through the subscription specified.
- Reservation Flexibility: You can cancel, exchange, or refund reservations with certain limitations. Learn more in the Microsoft documentation.
- Role Requirements: To buy a reservation, you must have the Owner role or Reservation Purchaser role on an Azure subscription.
- Reservation Coverage: A reservation applies to both primary and billable secondary compute replicas, but does not cover software, networking, or storage charges associated with the service.
- Infrastructure Changes: Purchasing a reservation for an existing resource does not modify its infrastructure or trigger a failover or downtime.
- Savings Calculation: The savings multiplier used to calculate the cost impact for this recommendation represents the savings achieved in applying a reservation to a non-Enterprise Account resource cost.
The 90-day cost graph shows the daily total spend for all Databases for MySQL and highlights the top five resources with the highest spend to consider optimizing.
Purchase Azure PostgreSQL Database Reservations
This recommendation is created when there is pay-as-you-go spend for Azure Database for PostgreSQL Single Server or Azure Database for PostgreSQL Flexible Server that could be covered by a reservation for compute resources.
Threshold: This recommendation is created if using a reservation on pay-as-you-go Databases for PostgreSQL will save at least $500 based on a 25% savings rate. When pay-as-you-go spend results in savings of less than $500, the recommendation is automatically closed.
How reservations work
- A reservation is a commitment for PostgreSQL Single Server or Azure Database for PostgreSQL Flexible Server use for a period of one or three years to get a significant discount on the compute costs.
- Existing deployments that are already running, or ones that are newly deployed automatically, that match the criteria set for the reservation will get the benefit. You do not need to assign the reservation to a specific database or managed instance.
How to address this
When you are purchasing a reservation in Azure, you must specify the following:
| Parameter | Description |
|---|---|
| Scope | The vCore reservation's scope can cover one subscription, multiple subscriptions (shared scope), a single resource group, or a management group |
| Region | The Azure region covered by the capacity reservation |
| Deployment Type | The Azure Database for the PostgreSQL Flexible Server resource type that you want to buy the reservation for |
| Performance Tier | The service tier for the PostgreSQL Flexible Server instances |
| Term | 1 or 3 years |
| Quantity | The number of vCores to reserve in the selected Azure region and Performance Tier |
Learn more about buying a reservation in the Microsoft documentation.
The size of reservation should be based on the total amount of compute used by the existing or soon-to-be-deployed database or managed instance within a specific region and using the same performance tier and hardware generation. Learn more about how to determine the correct reservation size in the Microsoft documentation.
Additional details
- PostgreSQL Single Server Retirement: Azure Database for PostgreSQL Single Server is being retired. Azure strongly recommends upgrading to Azure Database for PostgreSQL Flexible Server. New reservations will not be available for Single Server. Your existing reservations remain valid. For more information, see the Microsoft documentation.
- Reservation Flexibility: You can cancel, exchange, or refund reservations with certain limitations. Learn more in the Microsoft documentation.
- Role Requirements: To buy a reservation, you must have the Owner role or Reservation Purchaser role on an Azure subscription.
- Reservation Coverage: A reservation applies to both primary and billable secondary compute replicas, but does not cover software, networking, or storage charges associated with the service.
- No Impact on Existing Infrastructure: Purchasing a reservation for an existing resource does not modify its infrastructure or trigger a failover or downtime.
- Savings Calculation: The savings multiplier used to calculate the cost impact for this recommendation represents the savings achieved in applying a reservation to a non-Enterprise Account resource cost.
The 90-day cost graph shows the daily total spend for all Databases for PostgreSQL and highlights the top five resources with the highest spend to consider optimizing.
Purchase Azure Redis Cache Reservations
This recommendation is created when there is pay-as-you-go spend for Azure Cache for Redis that could be covered by a reservation for compute resources. Learn more about these reservations in the Microsoft documentation.
Threshold: This recommendation is created if using a reservation on pay-as-you-go Redis Cache will save at least $500 based on a 25% savings rate. When pay-as-you-go spend results in savings of less than $500, the recommendation is automatically closed.
How reservations work
- The size of the reservation should be based on the total amount of memory used by the existing or soon-to-be-deployed cache within a specific region, and using the same service tier.
- Premium and Enterprise Caches have two nodes by default, while Enterprise Flash has three nodes.
- Reservations are sold in increments of nodes. Use the Azure Pricing Calculator to calculate the number of nodes needed based on the number of hours to cover with a reservation.
How to address this
When you are purchasing a reservation in Azure, you must specify the following:
| Parameter | Description |
|---|---|
| Subscription | Subscription used to pay for the Azure Cache for Redis reservation |
| Scope | The reservation's scope can cover one subscription, multiple subscriptions (shared scope), a single resource group, or a management group |
| Region | The Azure region covered by the capacity reservation |
| Pricing Tier | The service tier for the instances |
| Term | 1 or 3 years |
| Quantity | The number of nodes to reserve in the selected Azure region and Pricing Tier |
Learn more about buying a reservation in the Microsoft documentation.
Analyze your usage information to help determine which reservations you should purchase. Learn more about how to determine the correct reservation size in the Microsoft documentation.
Additional details
- Applicable Tiers: Reservations are only available for Premium, Enterprise, and Enterprise Flash Redis Cache tiers.
- Reservation Flexibility: You can cancel, exchange, or refund reservations with certain limitations. Learn more in the Microsoft documentation.
- Role Requirements: To buy a reservation, you must have the Owner role or Reservation Purchaser role on an Azure subscription.
- Savings Calculation: The savings multiplier used to calculate the cost impact for this recommendation represents the savings achieved in applying a reservation to a non-Enterprise Account resource cost.
The 90-day cost graph shows the daily total spend for all instances with a Premium, Enterprise, or Enterprise Flash Redis Cache tier and highlights the top five resources with the highest spend to consider optimizing.
Purchase Azure SQL Database Reservations
This recommendation is created when there is pay-as-you-go spend for Azure SQL Database or SQL Managed Instance, or both, that could be covered by a reservation for compute resources.
Threshold: This recommendation is created if using a reservation on a pay-as-you-go SQL Database will save at least $500 based on a 25% savings rate. When pay-as-you-go spend results in savings of less than $500, the recommendation is automatically closed.
How reservations work
- A reservation is a commitment for SQL Database, a SQL Managed Instance use, or both, for a period of one or three years to get a significant discount on the compute costs.
- Existing deployments that are already running, or ones that are newly deployed automatically, that match the criteria set for the reservation will get the benefit. You do not need to assign the reservation to a specific database or managed instance.
How to address this
When you are purchasing a reservation in Azure, you must specify the following:
| Parameter | Description |
|---|---|
| Scope | The vCore reservation's scope can cover one subscription, multiple subscriptions (shared scope), a single resource group, or a management group |
| Region | The Azure region covered by the capacity reservation |
| Deployment Type | The SQL resource type that you want to buy the reservation for |
| Performance Tier | The service tier for the databases or managed instances |
| Term | 1 or 3 years |
| Quantity | The number of vCores to reserve in the selected Azure region and Performance Tier |
Learn more about buying a reservation in the Microsoft documentation.
Reservations are best for workloads that have consistent resource usage across a similar deployment type.
The size of the reservation should be based on the total amount of compute used by the existing or soon-to-be-deployed database or managed instance within a specific region and using the same performance tier and hardware configuration. Learn more about how to determine the correct reservation size in the Microsoft documentation.
Additional details
- Reservation Limitations: Not all configurations support reservations. Learn about limitations in the Microsoft documentation.
- Reservation Coverage: A reservation applies to both primary and billable secondary compute replicas, but does not cover software, networking, or storage charges associated with the service.
- Infrastructure Changes: Purchasing a reservation for an existing resource does not modify its infrastructure or trigger a failover or downtime.
- Upfront Payment: Reservations are charged upfront through the subscription specified.
- Reservation Flexibility: You can cancel, exchange, or refund reservations with certain limitations. Learn more in the Microsoft documentation.
- Role Requirements: To buy a reservation, you must have the Owner role or Reservation Purchaser role on an Azure subscription.
- Savings Calculation: The savings multiplier used to calculate the cost impact for this recommendation represents the savings achieved in applying a reservation to a non-Enterprise Account resource cost.
The 90-day cost graph shows the daily total spend for all SQL Databases and highlights the top five resources with the highest spend to consider optimizing.
Storage
Purchase Azure Premium Disk Reservations
This recommendation is created when there is pay-as-you-go spend for Azure Premium Disk Storage that could be covered by a reservation for storage resources. Learn more about these reservations in the Microsoft documentation.
Threshold: This recommendation is created if using a reservation on pay-as-you-go Premium Disk Storage will save at least $500 based on a 5% savings rate. When pay-as-you-go spend results in savings of less than $500, the recommendation is automatically closed.
How reservations work
- The SKU of a premium SSD determines the disk's size and performance.
- When determining your storage needs for a reservation, think of the total number of disks per SKU needed across your desired scope.
- A disk reservation is made per disk SKU. As a result, the reservation consumption is based on the unit of the disk SKUs instead of the provided size.
How to address this
When purchasing a reservation in Azure, you must specify the following:
| Parameter | Description |
|---|---|
| Billing Subscription | Subscription used to pay for the Azure Disk Storage reservation |
| Scope | The reservation's scope can cover one subscription, multiple subscriptions (shared scope), a single resource group, or a management group |
| Disks | The SKU you want to create |
| Region | The Azure region covered by the capacity reservation |
| Billing Frequency | Upfront or monthly |
Learn more about buying a reservation in the Microsoft documentation.
Analyze your usage information to help determine which reservations you should purchase. Make sure to track the usage in disk SKUs instead of provisioned or used disk capacity. Learn more about determining the correct reservation size in the Microsoft documentation.
Additional details
- Disk and VM Reservations: Examine your disk reservation along with your VM reservation. Azure highly recommends making reservations for both VM usage and disk usage for maximum savings.
- Applicable Disks: Reservations apply only to premium SSDs above size P30.
- Reservation Flexibility: You can cancel, exchange, or refund reservations with certain limitations. Learn more in the Microsoft documentation.
- Purchase Restrictions: Azure Disk Storage reservation discounts don't apply to unmanaged disks, ultra disks, or page blob consumption. Learn more about purchase restrictions in the Microsoft documentation.
- Savings Calculation: The savings multiplier used to calculate the cost impact for this recommendation represents the savings achieved when applying a reservation to a non-Enterprise Account resource cost.
The 90-day cost graph shows the daily total spend for all P30, P40, P50, P60, P70, and P80 Premium Disks Storage and highlights the top five resources with the highest spend to consider optimizing.
Have questions or feedback? Reach out to your account manager.
Updated 18 days ago