> For the complete documentation index, see [llms.txt](https://docs.finout.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.finout.io/user-guide/optimize/my-commitments.md). # My Commitments The My Commitments feature in Finout provides you with an in-depth view of your cloud commitments across providers. You can monitor coverage and utilization at a high level, then drill into individual Reserved Instances, Reservations, and Savings Plans to refine your commitment strategy. My Commitments currently supports **AWS** and **Azure**. ### Why Use My Commitments? As cloud services continue to grow and diversify, you are frequently navigating numerous commitments, each with its own distinct terms. Given this increasing complexity, there's a significant demand for a straightforward, efficient tool that lets you manage these commitments while optimizing costs and usage. **Main insights you can gain using My Commitments** * **Increase utilization**: Identify commitment plans with low usage and implement strategies to increase their utilization. * **Renewal**: Review expiring commitment plans and consider renewal options based on current and projected usage. * **Reallocation**: Strategically adjust workloads to better align with the specifications of your commitment plans, maximizing their value and benefits. **Key Features**: 1. Monitor all the plans you've opted for from your cloud providers in one place. Finout supports AWS and Azure. 2. Gain a high-level view of your coverage % and your utilization % across all your plans by type or any filter in the [MegaBill](https://claude.ai/user-guide/inform/megabill). 3. Dig deeper and examine coverage and utilization for each specific plan, refining your cloud management strategy. ### Switching Between Cloud Providers A cloud provider switcher appears in the top-right corner of the My Commitments page. Use it to choose which provider's commitments you want to view. * **AWS** — displays the four AWS views: [Executive Summary](#aws-executive-summary), [Reserved Instances Commitments](#aws-reserved-instances-commitments), [Saving Plans Commitments](#aws-saving-plans-commitments), and [RI Explorer.](#aws-ri-explorer) * **Azure** — displays the three Azure views: [Executive Summary](#azure-executive-summary), [Reservations Commitments](#azure-reservations-commitments), and [Saving Plans Commitments](#azure-saving-plans-commitments).
*** ## AWS Commitments Select **AWS** in the cloud provider switcher to view your AWS commitments. AWS support includes four views: the Executive Summary, Reserved Instances Commitments, Saving Plans Commitments, and the RI Explorer. ### AWS Executive Summary The Executive summary provides a concise overview of your AWS commitments, equipping you with key metrics to manage your cloud commitments expenditure optimally. {% hint style="info" %} This tab displays metrics for EC2 instances only. The coverage metric is an exception - it includes instances from additional services, as detailed below. {% endhint %} * **Filters and time frame settings**: Filter the executive summary using specific AWS cost data or [Virtual Tags](https://claude.ai/user-guide/inform/virtual-tags). Additionally, select a relevant timeframe for the overview. * **Coverage**: Represents the percentage of eligible spend covered by Reserved Instances or Savings Plans, rather than paid at on-demand rates. This metric includes the following services: * EC2 - Compute * RDS - Compute * RDS - Other * ElastiCache * Redshift * AmazonDynamoDB * DynamoDB - On Demand Read * DynamoDB - On Demand Write * DynamoDB - Provisioned Write * DynamoDB - Provisioned Read * SageMaker * Amazon Elastic MapReduce * AmazonES * Lambda * EC2 Container Service - Fargate Memory * EC2 Container Service - Fargate Compute. * **Utilization**: The percentage of your commitment capacity actively used during the selected period. For example, 80% utilization means 20% of your commitments went unused. Applies to EC2 Reserved Instances (RIs) only. * **Savings**: The total amount saved during the selected period by leveraging your commitments instead of on-demand pricing. Applies to EC2 Reserved Instances (RIs) only. * **Waste**: The cost of unused commitment capacity during the selected period. To minimize waste, consider using Finout's automated commitment management — [CostGuard](https://claude.ai/user-guide/optimize/costguard). This applies to EC2 Reserved Instances (RIs) only. #### Executive Summary Graphs
1. **Coverage**: Your daily coverage status is based on the selected filters and timeframe. Use the Group By feature to further break down the coverage status by specific groups and values. 2. **Reserved Instance Utilization**: Showcases the utilization rate of reserved instances, helping identify underutilized commitments. 3. **Hourly Usage by Purchase Options**: Your hourly commitment usage versus the on-demand usage, illustrates the frequency at which your commitments are utilized. 4. **On-Demand Cost by Family Type**: The on-demand costs are broken down by instance family, helping identify potential areas for improved coverage and savings. ### AWS Reserved Instances Commitments The Reserved Instances Commitments view provides detailed insights into your active Reserved Instances, allowing you to monitor and manage them effectively. This view supports EC2 instances only.
This view provides the following details: * **Plan ID**: A unique identifier for each Reserved Instance. * **Instance type**: The specific type of Reserved Instance (e.g., m5.large, t3.nano). * **Expiration**: Date when the Reserved Instance term ends. * **Utilization**: A visual and percentage representation of how much of the reserved capacity usage. * **Net savings**: The savings gained by choosing a Reserved Instance over on-demand pricing. Additionally, AWS presents savings per plan coverage at a **yearly level**, whereas Finout provides these calculations at a **daily level**. * **Underutilized waste**: Costs for any unused reserved capacity. * **Region**: The AWS region of the Reserved Instance. * **Operating system**: The operating system associated with the Reserved Instance. * **Reservation term**: The duration of the reservation, typically one or three years. * **Offering class**: Type of Reserved Instance purchased, such as 'Standard' or 'Convertible'. * **Payment option**: The chosen payment method, such as 'no upfront', 'partial upfront', or 'all upfront'. * **Units**: Number of Reserved Instances in the commitment. ### AWS Saving Plans Commitments The Savings Plans Commitments view provides detailed insights into your active Savings Plans, allowing you to monitor and manage them effectively. Unlike AWS, which calculates savings and coverage annually, Finout provides these calculations daily. **This tab supports all Savings Plan types:** * Compute Savings Plans * EC2 Instance Savings Plans * SageMaker Savings Plans * Database Savings Plans
You can filter Savings Plans by type, instance family, term (1 or 3 years), and purchase option (partial upfront, all upfront). This view provides the following details: * **Plan ID**: A unique identifier for the savings plan. * **Savings plan type**: Displays the type of savings plan (e.g., Compute). * **Instance type family**: Shows the category of instances or services covered in the savings plan (if applicable). * **Expiration**: Indicates when the savings plan will end. * **Utilization**: Represents the percentage of the committed usage that has been consumed. * **Net savings**: Reflects the total cost savings achieved through the plan. Additionally, AWS presents savings per plan coverage at a **yearly level**, whereas Finout provides these calculations at a **daily level**. * **Underutilized waste**: The amount of financial waste due to underutilization of the committed plan. * **Region**: The geographical region where the savings plan is applicable. * **Term**: The duration for which the savings plan is active, typically noted in years or months. * **Payment option**: The payment method chosen for the savings plan, such as 'no upfront', 'partial upfront', or 'all upfront'. * **Hourly commitment**: The committed hourly cost as per the savings plan. * **Total commitment**: The total cost commitment over the term of the savings plan. ### AWS RI Explorer Organizations that manually purchase and manage commitments often struggle to align Reserved Instances (RIs) with fluctuating usage patterns, such as nightly spikes. They require hourly insights to compare on-demand usage and rates against RI cost and usage, enabling more accurate commitment management. This includes examining on-demand hourly patterns to identify opportunities for purchasing additional commitments and analyzing RI utilization for optimization of existing commitments.
With RI Explorer, you can track and compare hourly data on instances that are eligible for RIs using purchase groups. Additionally, AWS presents savings per plan coverage at a **yearly level**, whereas Finout provides these calculations at a **daily level**. {% hint style="info" %} Purchase groups are collections of resources sharing the same instance family, region, and OS. These groups encompass all possible combinations within an AWS account based on utilized resources, regardless of their billing type (on-demand, RI, SP, etc.) {% endhint %} This granular data empowers organizations to manage manually purchased commitments more effectively and precisely, optimizing both usage and costs while also aiding in the purchase of new commitments. 1. Graph and metrics that display the cost or usage of RIs per different purchase groups based on the chosen filters. These groups encompass all possible combinations within an AWS account based on utilized resources, regardless of their billing type (on-demand, RI, SP, etc.). 2. Total Cost (per purchase group): This summarizes the cost for each group, regardless of billing type, within the selected period. 3. Total On-Demand Cost (per purchase group): This represents the total on-demand cost for each group during the filtered period. 4. Coverage Rate (per purchase group): Calculates the percentage of costs covered by commitments, excluding on-demand costs, for each group within the selected period. 5. RI Utilization Rate (per purchase group): Measures the percentage of Reserved Instance (RI) usage for each group within the selected period. Utilization indicates how effectively the purchased RIs are being used, helping you identify opportunities for optimization and ensuring commitments are fully leveraged. 6. On-Demand Baseline (per purchase group): Displays the greatest common denominator for on-demand cost and usage, providing a clear reference point for comparison. This can be used to purchase new commitments or expand existing ones. 7. Filters by choosing specific MegaBill keys. The chosen keys will affect the presented purchase groups 8. Time Frame:\ The default is the last 30 days. You can either select one of the predefined options or switch to custom. 9. Choose to display the hourly data by your Cost or Usage. 10. Sort the groups by: Total Cost, Total On-Demand, Coverage Rate, RI Utilization, and On-Demand Baseline. 11. Redirects you to MegaBill with the selected prepopulated filters. *** ## Azure Commitments (Beta) {% hint style="info" %} Azure Commitments are currently in Beta. To enable it for your account, contact your Finout customer success manager or email . {% endhint %} Select **Azure** in the cloud provider switcher to view your Azure commitments. Azure support includes three views: the Executive Summary, Reservations Commitments, and Saving Plans Commitments. Azure commitments cover **Azure Reservations** and **Azure Savings Plans for compute**. To bring this data into Finout, you must grant two additional read-only roles to your Finout service principal during onboarding. See Connect Azure Commitments to Finout for the setup steps. ### Azure Executive Summary The Executive Summary provides a high-level snapshot of your Azure commitment health — coverage, utilization, cost distribution across pricing models, and upcoming expirations — in a single consolidated view.
* **Filters and time frame settings**: Filter the Executive Summary using any [MegaBill](https://claude.ai/user-guide/inform/megabill) dimension or [Virtual Tags](https://claude.ai/user-guide/inform/virtual-tags). The default time range is the last 30 days, adjustable through the date picker. #### Top-line metrics Three KPI tiles are displayed at the top of the page, calculated based on the applied filters: * **Current Total Coverage**: The percentage of committable cost that is not billed at on-demand pricing — in other words, the share of eligible spend covered by Reservations or Savings Plans. See [How Azure coverage is calculated](https://claude.ai/chat/a44d14e6-b28b-4bda-b934-25d8d79b64e1#h_azure-coverage-calc) below. * **Reservations Utilization**: The percentage of your Azure Reservation capacity that is being used during the selected period. * **Saving Plans Utilization**: The percentage of your Azure Savings Plan commitment that is being used during the selected period. {% hint style="info" %} The utilization metrics include only plans with Provisioning State = Succeeded {% endhint %} {% hint style="info" %} The Azure Executive Summary does not display the dollar Savings, Underutilized Waste, or Discount Rate tiles shown for AWS. Azure does not expose a monetary commitment value for Reservations, so these dollar-based metrics cannot be calculated for Azure Reservations. {% endhint %} #### Azure Executive Summary graphs All charts respect the active filters and selected time range. 1. **Coverage**: Your daily coverage status across the selected period. Use the Group By control to break coverage down by specific dimensions and values. 2. **Reservations Utilization**: The daily utilization rate of your Azure Reservations, helping you identify underused reservations. 3. **Saving Plans Utilization**: The daily utilization rate of your Azure Savings Plans. 4. **VM Cost per Pricing Model**: Your virtual machine spend split across pricing models (On-Demand, Reservation, Savings Plan, and Spot) over time, so you can see how much of your VM cost is covered by each commitment type. 5. **Database Cost per Pricing Model**: Your database spend split across pricing models over time, covering Azure database services such as SQL Managed Instance, SQL Database, Azure Database for MySQL, and Azure Database for PostgreSQL.
#### Upcoming Commitments Expirations A single table combining both Reservations and Savings Plans that are nearing expiration. The table is calculated from today's date and is independent of the selected time-range filter. The table includes the following columns: * **ID**: The Azure resource ID of the commitment. * **Commitment Type**: Either Reservations or Saving Plan. * **Name**: The commitment's display name as ingested from Azure. * **Expiration Date**: The date the commitment term ends. Sorted ascending by default. ### Azure Reservations Commitments The Reservations Commitments view provides detailed insights into your active Azure Reservations, allowing you to monitor and manage them effectively. Azure Reservations apply to a range of services, including virtual machines, SQL databases, and app services. You can filter Reservations by **Status**, **Instance Type**, **Region**, and **Reservation Term**. The count of active plans is shown above the table, and you can export the list or adjust visible columns using the controls in the top-right of the table.
This view provides the following details: * **Reservation ID**: A unique identifier for each reservation. * **Name**: The reservation's display name as ingested from Azure. * **Instance Type**: The resource SKU covered by the reservation (e.g., Standard\_B4ms, Standard\_D4as\_v4). * **Reserved Resource Type**: The category of resource the reservation covers (e.g., VirtualMachines, SqlDatabases, AppService). * **Region**: The Azure region the reservation applies to (e.g., southcentralus, centralus). * **Quantity**: The number of reserved units in the commitment. * **Term**: The duration of the reservation, shown in ISO 8601 duration format (P1Y for one year, P3Y for three years). * **Start Date**: The date the reservation term began. * **Expiration**: The date the reservation term ends. * **Utilization**: A visual and percentage representation of how much of the reserved capacity is being used. * **Provisioning State**: Indicating whether a plan was successfully provisioned. Filtered to show "Succeeded" plans by default. * **Utilization Trend**: The direction of the utilization trend over the selected period (UP, DOWN, or SAME). {% hint style="info" %} Azure does not expose a monetary commitment value or a payment-option field for Reservations. As a result, the Azure Reservations view does not include net savings, underutilized waste (in dollars), or payment-option columns. Utilization is reported as a percentage and as a trend. {% endhint %} ### Azure Saving Plans Commitments The Saving Plans Commitments view provides detailed insights into your active Azure Savings Plans. Azure offers a single Savings Plan product — Savings Plan for compute — that applies across eligible compute services and is not region-scoped. You can filter Savings Plans by **Status**, **Scope Type**, and **Reservation Term**. The count of active plans is shown above the table, and you can export the list or adjust visible columns using the controls in the top-right of the table.
This view provides the following details: * **Plan ID**: A unique identifier for the savings plan. * **Name**: The savings plan's display name as ingested from Azure. * **Savings Plan Type**: The type of savings plan. Azure currently offers a single type — Compute. * **Term**: The duration of the savings plan, shown in ISO 8601 duration format (P1Y for one year, P3Y for three years). * **Commitment Amount**: The hourly dollar commitment for the savings plan. * **Start Date**: The date the savings plan term began. * **Expiration**: The date the savings plan term ends. * **Utilization**: A visual and percentage representation of how much of the committed spend is being used. * **Provisioning State**: Indicating whether a plan was successfully provisioned. Filtered to show "Succeeded" plans by default. * **Utilization Trend**: The direction of the utilization trend over the selected period (UP, DOWN, or SAME). * **Scope Type**: The scope at which the savings plan benefit applies — Shared (across subscriptions in the billing account) or Single (restricted to a specific subscription). * **Subscription Name**: The subscription associated with the savings plan, where applicable. ### How Azure coverage is calculated Coverage represents the percentage of your committable Azure spend that is billed through a commitment rather than at on-demand pricing. ``` Coverage (%) = Committed Spend / Committable Spend ``` Where: * **Committable Spend** is the total spend on Azure services that support Reservations or Savings Plans, excluding Spot-priced usage. * **Committed Spend** is the subset of committable spend that is billed through a Reservation or Savings Plan. The calculation works as follows. Finout filters Azure billing data to committable services only, then excludes any Spot-priced usage, since Spot cannot be covered by a commitment. The remaining spend is the committable spend (the denominator). Within that same set, Finout sums the spend billed as Reservation or Savings Plan to get the committed spend (the numerator), then divides the two. *** ### FAQs **Why is the Executive Summary Coverage rate in Finout different from AWS?** For AWS, Finout focuses on fewer resources and calculates coverage rates using only Reserved Instances (RIs), while AWS includes both RIs and Savings Plans (SPs) across a broader range of resources. **How do Finout's savings per plan calculations differ from AWS?** AWS calculates savings per commitment yearly, whereas Finout provides savings per commitment calculations on a daily level. This allows for more granular tracking and optimization of cloud costs in Finout. **What are the required permissions for AWS?** * `assumeRole` * `ce:GetReservationUtilization` * `ce:GetSavingsPlansUtilizationDetails` {% hint style="info" %} You need to grant Finout permissions for each AWS payer account for which you want to have commitments in Finout. {% endhint %} **What are the required permissions for Azure?** To ingest Azure commitments, assign two read-only roles to your Finout service principal: * **Savings plan Reader** at the `Microsoft.BillingBenefits` scope (tenant-wide), for Savings Plan inventory and metadata. * **Reservations Reader** at the `Microsoft.Capacity` scope (tenant-wide), for Reservation inventory and metadata. Azure Reservations and Savings Plans are tenant-level resources and do not inherit permissions from subscriptions, so these roles are assigned separately from your existing Azure billing permissions. For the full setup steps, see [Connect Azure Commitments to Finout](https://claude.ai/billing-integrations/cloud-providers/connect-to-azure#h_connect-azure-commitments). **Why don't I see net savings or waste for my Azure Reservations?** Azure does not expose a monetary commitment value for Reservations through its APIs — only the reserved quantity. Because of this, Finout cannot calculate dollar-based savings or underutilized waste for Azure Reservations. Utilization is still available as a percentage and as a trend. **How do I proceed if I don't have permissions?** * A Missing Permissions icon appears at the top of the page. Hover on it to see all the missing permissions. * For AWS using CloudFormation during onboarding, [run the update function](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-direct.html). * For AWS manual onboarding, modify the JSON based on the [onboarding process](https://claude.ai/billing-integrations/cloud-providers/connect-to-aws#h_cb44a06282). * For Azure, assign the roles described in [Connect Azure Commitments to Finout](https://claude.ai/billing-integrations/cloud-providers/connect-to-azure#h_connect-azure-commitments), then return to My Commitments after the next data refresh. **Why do I see RI and SP data under my commitments but no data in the commitments log?** There are two possible reasons for this: 1. The commitments log requires different permissions than the My Commitments page. If you don't have the necessary access, you won't see the log. 2. Commitment logs only appear when an RI or SP plan is purchased while the account is already onboarded to Finout. If the plan was purchased before onboarding, logs will not appear. Additionally, logs are only retained for 30 days — if no action was taken on the plan within that timeframe, the logs won't be available. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.finout.io/user-guide/optimize/my-commitments.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.