Merge pull request #247007 from bandersmsft/choose-commit-amount

MCM - Minor update to choose-commit-amount for sotware not covered

Author: prmerger-automator[bot]

articles/cost-management-billing/savings-plan/choose-commitment-amount.md

@@ -8,14 +8,16 @@ ms.service: cost-management-billing
 ms.subservice: savings-plan
 ms.custom: ignite-2022
 ms.topic: how-to
-ms.date: 02/03/2023
+ms.date: 08/01/2023
 ms.author: banders
 ---
 
 # Choose an Azure saving plan commitment amount
 
 You should purchase savings plans based on consistent base usage. Committing to a greater spend than your historical usage could result in an underutilized commitment, which should be avoided when possible. Unused commitment doesn't carry over from one hour to the next. Usage exceeding the savings plan commitment is charged using more expensive pay-as-you-go rates.
 
+Software costs aren't covered by savings plans. For more information, see [Software costs not included in saving plans](software-costs-not-included.md).
+
 ## Savings plan purchase recommendations
 
 Savings plan purchase recommendations are calculated by analyzing your hourly usage data over the last 7, 30, and 60 days. Azure simulates what your costs would have been if you had a savings plan and compares it with your actual pay-as-you-go costs incurred over the time duration. The commitment amount that maximizes your savings is recommended. To learn more about how recommendations are generated, see [How hourly commitment recommendations are generated](purchase-recommendations.md#how-hourly-commitment-recommendations-are-generated).