Merge pull request #230144 from bandersmsft/pub-contrib-fix-03092023

MCM - Updates for Saira Shaik

Author: v-regandowner

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

@@ -34,31 +34,34 @@ Note the following points:
 
 ## Recommendations in the Azure portal
 
-Savings plan purchases are calculated by the recommendations engine for the selected term and scope, based on last 30 days of usage. Recommendations are provided through [Azure Advisor](https://portal.azure.com/#view/Microsoft_Azure_Expert/AdvisorMenuBlade/~/Cost), the savings plan purchase experience in [Azure portal](https://portal.azure.com/), and through the [savings plan benefit recommendations API](/rest/api/cost-management/benefit-recommendations/list).
-
-## Savings plan purchase recommendations for customers using Management groups
-Currently Azure portal doesn't provide Savings plan recommendations for Management groups, but customers can calculate their own per-hour commitment for Management groups by using the following steps until Azure portal provides Management group-level recommendations.
-1. Download Usage Detail report from EA portal or Azure portal to get the accurate usage and cost.
-    - From EA portal - By logging into ea.azure.com, navigating to Reports section, and downloading Usage Details report for the current month and the past 2 months.
-    - From Azure portal - By logging into Azure portal and searching for cost management and billing. Under Billing, click on Usage + charges and click on download against the month to download current and past 2 months.
-1. Open the downloaded file in Excel. If the file size is huge open it in Power BI.
-1. Create cost column by multiplying PayG Price * Quantity (i.e. calculated cost).
-1. Filter Charge Type = "Usage".
-1. Filter Meter Category = "Virtual Machines", "App Service", "Functions", "Container Instance" - As the SP is applied on only these services.
-1. Filter ProductOrderName = Blank 
-1. Filter Quantity >= 23 to consider only items which ran 24 hours as SP is per hour commitment, and we have the granularity of per day and not per hour. This will avoid any sparse compute.
-1. Filter Months for current and previous 2 months. 
-1. If you are doing this in Power BI export the data to .csv file and copy into Excel. 
-1. Now copy the subscription names that belong to the management group on which you want to apply Savings plan on in Excel sheet.
-1. Do a Vlookup against the internal subscriptions against the filter data. 
-1. Divide calculated cost with 24 hours to get per hour cost.
-1. Create pivot to group the data by subscription by month and day, and copy this pivot data into new sheet.
-1. Multiply per hour cost with .4. Reason for this is you will get a discount on the usage. For example, you have committed 100 rupees you will be charged based on 1 or 3 year Savings plan discount applicable for SKU hence your cost per hour will be less than 100 hours and hence you will be needing more cost of compute to get the value of 100. 40% is the safe limit. 
-1. Now see the range of cost per hour per day and per month to get view of the sage commitment you can make.
+The recommendations engine calculates savings plan purchases for the selected term and scope, based on last 30 days of usage. Recommendations are provided through [Azure Advisor](https://portal.azure.com/#view/Microsoft_Azure_Expert/AdvisorMenuBlade/~/Cost), the savings plan purchase experience in [Azure portal](https://portal.azure.com/), and through the [savings plan benefit recommendations API](/rest/api/cost-management/benefit-recommendations/list).
+
+## Recommendations for management groups
+
+Currently, the Azure portal doesn't provide savings plan recommendations for management groups. However, you can manually calculate your own per-hour commitment for management groups using the following steps.
+
+1. Download the Usage Detail report from the EA portal or Azure portal to get your usage and cost.
+    - EA portal - Sign in to ea.azure.com, navigate to the Reports section, and then download the Usage Details report for the current and previous two months.
+    - Azure portal - Sign in to the Azure portal and navigate to Cost Management + Billing. Under Billing, select **Usage + charges** and then download for the current and previous two months.
+1. Open the downloaded file in Excel. Or, if the file size is too large to open in Excel, you can use Power BI Desktop.
+1. Create the `cost` column by multiplying `PayG Price` * `Quantity` to create `CalculatedCost`.
+1. Filter `Charge Type` = `Usage`.
+1. Filter `Meter Category` = `Virtual Machines`, `App Service`, `Functions`, `Container Instance` because the savings plan applies to only those services.
+1. Filter `ProductOrderName` = `Blank`.
+1. Filter `Quantity` >= `23` to consider only items used for 24 hours because a savings plan is per hour commitment, and we have the granularity of per day, not per hour. This step avoids sparse compute records.
+1. Filter `Months` for the current and previous two months.
+1. If you're using Power BI, export the data to a CSV file and open it in Excel.
+1. Copy the subscription names that belong to the management group where you want to apply a savings plan to an Excel sheet.
+1. In Excel, use the `Vlookup` function for the subscriptions against the filtered data.
+1. Divide `CalculatedCost` by `24` hours to get `PerHour` cost.
+1. Create a PivotTable to group the data by subscription and by month and day, and then copy the PivotTable data to a new sheet.
+1. Multiply the `PerHour` cost by `0.4`.  
+    This step determines the discount for the usage. For example, you committed $100.00 USD and you are charged based on a one or three-year savings plan discount. The discount applies per SKU, so your cost per hour is less than 100 hours. You need more compute cost to get the $100.00 US value. So, 40% is a safe limit.
+1. View the range of cost per hour, per day, and per month to determine a safe commitment to make.
 
 ## Need help? Contact us
 
-If you have Azure savings plan for compute questions, contact your account team, or [create a support request](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest). Temporarily, Microsoft will only provide Azure savings plan for compute expert support requests in English.
+If you have Azure savings plan for compute questions, contact your account team, or [create a support request](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest). Temporarily, Microsoft only provides Azure savings plan for compute expert support requests in English.
 
 ## Next steps
 

articles/cost-management-billing/savings-plan/utilization-cost-reports.md

@@ -126,13 +126,15 @@ Get the Amortized costs data and filter the data for a `PricingModel` = `Savings
 2. Get the savings plan costs. Sum the `Cost` values to get the monetary value of what you paid for the savings plan. It includes the used and unused costs of the savings plan.
 3. Subtract estimated pay-as-you-go costs from savings plan costs to get the estimated savings.
 
-- To know the Savings made out of public list price:
-   - Get public or list price cost.  Multiply the `PayGPrice` value with `Quantity` values to get public-list-price costs.
-   - Get Savings made out of savings plan against public list price. Subtract estimated public-list-price costs from `Cost`.
+To determine the savings from the pay-as-you-go list price:
 
-+ To know the % savings made out of discounted price for customer:
-   + Get Savings made out of savings plan against discounts given to customer. Subtract estimated pay-as-you-go from `Cost`.
-   + Get % discount applied on each line item. Divide `Cost` with public-list-price and then divide by 100.
+1. To get the pay-as-you-go list price cost (`PayGPriceCost`), multiply the `PayGPrice` value with the `Quantity` value.
+1. Subtract `PayGPriceCost` from `Cost` to determine the savings from the savings plan.
+
+To determine the savings percentage from the discounted price:
+
+1. Subtract `PayGPrice` from `Cost` to get the savings from the savings plan against discounts.
+1. Divide `Cost` by `PayGPrice` and then divide by 100 to get the discount percentage applied, per line item.
 
 Keep in mind that if you have an underutilized savings plan, the `UnusedBenefit` entry for `ChargeType` becomes a factor to consider. When you have a fully utilized savings plan, you receive the maximum savings possible. Any `UnusedBenefit` quantity reduces savings.