Merge pull request #224337 from bandersmsft/sp-update-01182023

MCM - Savings plan doc updates

Author: American-Dipper

articles/cost-management-billing/savings-plan/buy-savings-plan.md

@@ -8,105 +8,86 @@ ms.service: cost-management-billing
 ms.subservice: savings-plan
 ms.custom: ignite-2022
 ms.topic: how-to
-ms.date: 01/30/2023
+ms.date: 02/03/2023
 ms.author: banders
 ---
 
 # Buy an Azure savings plan
 
-Azure savings plans help you save money by committing to an hourly spend for one-year or three-years plans for Azure compute resources. Saving plans discounts apply to usage from virtual machines, Dedicated Hosts, Container Instances, App Services and Azure Premium Functions. The hourly commitment is priced in USD for Microsoft Customer Agreement customers and local currency for Enterprise customers.
-
-Before you enter a commitment to buy a savings plan, review the following sections to prepare for your purchase.
+Azure savings plans help you save money by committing to an hourly spend for one-year or three-year plans for Azure compute resources. Before you enter a commitment to buy a savings plan, review the following sections to prepare for your purchase.
 
 ## Who can buy a savings plan
 
-You can buy a savings plan for an Azure subscription that's of type Enterprise Agreement (EA) offer code MS-AZR-0017P or MS-AZR-0148P, Microsoft Customer Agreement (MCA), or Microsoft Partner Agreement (MPA). If don't know what subscription type you have, see [check your billing type](../manage/view-all-accounts.md#check-the-type-of-your-account).
+Savings plan discounts only apply to resources associated with subscriptions purchased through an Enterprise Agreement (EA), Microsoft Customer Agreement (MCA), or Microsoft Partner Agreement (MPA). You can buy a savings plan for an Azure subscription that's of type EA (MS-AZR-0017P or MS-AZR-0148P), MCA or MPA. To determine if you're eligible to buy a plan, [check your billing type](../manage/view-all-accounts.md#check-the-type-of-your-account).
 
-## Change agreement type to one supported by savings plan
+### Enterprise Agreement customers
 
-If your current agreement type isn't supported by a savings plan, you might be able to transfer or migrate it to one that's supported. For more information, see the following articles.
+- EA admins with write permissions can directly purchase savings plans from **Cost Management + Billing** > **Savings plan**. No subscription-specific permissions are needed.
+- Subscription owners for one of the subscriptions in the enrollment account can purchase savings plans from **Home** > **Savings plan**.
 
-- [Transfer Azure products between different billing agreements](../manage/subscription-transfer.md)
-- [Product transfer support](../manage/subscription-transfer.md#product-transfer-support)
-- [From MOSA to the Microsoft Customer Agreement](https://www.microsoft.com/licensing/news/from-mosa-to-microsoft-customer-agreement)
+Enterprise Agreement (EA) customers can limit purchases to only EA admins by disabling the Add Savings Plan option in the [Azure portal](https://portal.azure.com/#blade/Microsoft_Azure_GTM/ModernBillingMenuBlade/BillingAccounts). Navigate to the **Policies** menu to change settings.
 
-## Required permission and how to buy
+### Microsoft Customer Agreement (MCA) customers
 
-You can buy a savings plan using the Azure portal or with the [Savings Plan Order Alias - Create](/rest/api/billingbenefits/savings-plan-order-alias/create) REST API.
+- Customers with billing profile contributor permissions or higher can purchase savings plans from **Cost Management + Billing** > **Savings plan** experience. No subscription-specific permissions are needed.
+- Subscription owners for one of the subscriptions in the billing profile can purchase savings plans from **Home** > **Savings plan**.
 
-### Purchase in the Azure portal
+To disallow savings plan purchases on a billing profile, billing profile contributors can navigate to the **Policies** menu under the billing profile and adjust the Azure Savings Plan option.
 
-Required permission and the steps to buy vary, depending on your agreement type.
+### Microsoft Partner Agreement partners
 
-#### Enterprise Agreement customers
+- Partners can use **Home** > **Savings plan** in the [Azure portal](https://portal.azure.com/) to purchase savings plans on behalf of their customers.
 
--	EA admins with write permissions can directly purchase savings plans from **Cost Management + Billing** > **Savings plan**. No specific permission for a subscription is needed.
--	Subscription owners for one of the subscriptions in the EA enrollment can purchase savings plans from **Home** > **Savings plan**.
--	Enterprise Agreement (EA) customers can limit purchases to EA admins only by disabling the **Add Savings Plan** option in the [Azure portal](https://portal.azure.com/#blade/Microsoft_Azure_GTM/ModernBillingMenuBlade/BillingAccounts). Navigate to the **Policies** menu to change settings. 
+## Change agreement type to one supported by savings plan
+
+If your current agreement type isn't supported by a savings plan, you might be able to transfer or migrate it to one that's supported. For more information, see the following articles.
 
-#### Microsoft Customer Agreement (MCA) customers
+- [Transfer Azure products between different billing agreements](../manage/subscription-transfer.md)
+- [Product transfer support](../manage/subscription-transfer.md#product-transfer-support)
+- [From MOSA to the Microsoft Customer Agreement](https://www.microsoft.com/licensing/news/from-mosa-to-microsoft-customer-agreement)
 
--	Customers with billing profile contributor permissions and above can purchase savings plans from **Cost Management + Billing** > **Savings plan** experience. No specific permissions on a subscription needed.
--	Subscription owners for one of the subscriptions in the billing profile can purchase savings plans from **Home** > **Savings plan**.
--	To disallow savings plan purchases on a billing profile, billing profile contributors can navigate to the Policies menu under the billing profile and adjust **Azure Savings Plan** option.
+## Purchase savings plan
 
-#### Microsoft Partner Agreement partners
+You can purchase a savings plan using the [Azure portal](https://portal.azure.com/) or with the [Savings Plan Order Alias - Create](/rest/api/billingbenefits/savings-plan-order-alias/create) REST API.
 
--	Partners can use **Home** > **Savings plan** in the Azure portal to purchase savings plans for their customers.
+### Buy a savings plan in the Azure portal
+
+1. Sign in to the Azure portal.
+2. Select **All services** > **Savings plans**.
+3. Select **Add** to purchase a new savings plan.
+4. Complete all required fields:
+    - **Name** – Friendly name for the new savings plan.
+    - **Billing subscription** - Subscription used to pay for the savings plan. For more information about permissions and roles required to purchase a savings plan, see [Who can buy a savings plan](#who-can-buy-a-savings-plan).
+    - **Apply to any eligible resource** – scope of resources that are eligible for savings plan benefits. For more information, see [Savings plan scopes](scope-savings-plan.md).
+    - **Term length** - One year or three years.
+    - **Hourly commitment** – Amount available through the savings plan each hour. In the Azure portal, up to 10 recommendations may be presented. Recommendations are scope-specific. Azure doesn't currently provide recommendations for management groups. Each recommendation includes:
+        - An hourly commitment.
+        - The potential savings percentage compared to on-demand costs for the commitment.
+        - The percentage of the selected scopes compute usage that would be covered by new savings plan. It includes the commitment amount plus any other previously purchased savings plan or reservation.
+    - **Billing frequency** – **All upfront** or **Monthly**. The total cost of the savings plan will be the same regardless of the selected frequency.
 
 ### Purchase with the Savings Plan Order Alias - Create API
 
-Buy savings plans by using RBAC permissions or with permissions on your billing scope. When using the [Savings Plan Order Alias - Create](/rest/api/billingbenefits/savings-plan-order-alias/create) REST API, the format of the `billingScopeId` in the request body is used to control the permissions that are checked. 
+Buy savings plans by using Azure RBAC permissions or with permissions on your billing scope. When using the [Savings Plan Order Alias - Create](/rest/api/billingbenefits/savings-plan-order-alias/create) REST API, the format of the `billingScopeId` in the request body is used to control the permissions that are checked.
 
-To purchase using RBAC permissions:
+#### To purchase using Azure RBAC permissions
 
-- You must be an Owner of the subscription which you plan to use, specified as `billingScopeId`.
+- You must be an Owner of the subscription that you plan to use, specified as `billingScopeId`.
 - The `billingScopeId` property in the request body must use the `/subscriptions/10000000-0000-0000-0000-000000000000` format.
 
-To purchase using billing permissions:
+#### To purchase using billing permissions
 
 Permission needed to purchase varies by the type of account that you have.
 
 - For Enterprise agreement customers, you must be an EA admin with write permissions.
-- For Microsoft Customer Agreement (MCA) customers, you must be a billing profile contributor or above.
-- For Microsoft Partner Agreement partners, only RBAC permissions are currently supported
+- For Microsoft Customer Agreement (MCA) customers, you must be a billing profile contributor or higher.
+- For Microsoft Partner Agreement partners, only Azure RBAC permissions are currently supported
 
 The `billingScopeId` property in the request body must use the `/providers/Microsoft.Billing/billingAccounts/{accountId}/billingSubscriptions/10000000-0000-0000-0000-000000000000` format.
 
-## Scope savings plans
-
-You can scope a savings plan to a shared scope, management group, subscription, or resource group scopes. Setting the scope for a savings plan selects where the savings plan savings apply. When you scope the savings plan to a resource group, savings plan discounts apply only to the resource group—not the entire subscription.
-
-### Savings plan scoping options
-
-You have the following options to scope a savings plan, depending on your needs:
-
-- **Shared scope** - Applies the savings plan discounts to matching resources in eligible subscriptions that are in the billing scope. If a subscription was moved to a different billing scope, the benefit no longer applies to the subscription. It does continue to apply to other subscriptions in the billing scope.
-  - For Enterprise Agreement customers, the billing scope is the enrollment. The savings plan shared scope would include multiple Active Directory tenants in an enrollment.
-  - For Microsoft Customer Agreement customers, the billing scope is the billing profile.
-  - For Microsoft Partner Agreement, the billing scope is a customer.
-- **Single subscription scope** - Applies the savings plan discounts to the matching resources in the selected subscription.
-- **Management group** - Applies the savings plan discounts to the matching resource in the list of subscriptions that are a part of both the management group and billing scope. To scope a savings plan to a management group, you must have at least read permission on the management group.
-- **Single resource group scope** - Applies the savings plan discounts to the matching resources in the selected resource group only.
-
-When savings plan discounts are applied to your usage, Azure processes the savings plan in the following order:
-
-1. Savings plans with a single resource group scope
-2. Savings plans with a single subscription scope
-3. Savings plans scoped to a management group
-4. Savings plans with a shared scope (multiple subscriptions), described previously
-
-You can always update the scope after you buy a savings plan. To do so, go to the savings plan, select **Configuration**, and rescope the savings plan. Rescoping a savings plan isn't a commercial transaction. Your savings plan term isn't changed. For more information about updating the scope, see [Update the scope after you purchase a savings plan](manage-savings-plan.md#change-the-savings-plan-scope).
-
-:::image type="content" source="./media/buy-savings-plan/scope-savings-plan.png" alt-text="Screenshot showing saving plan scope options." lightbox="./media/buy-savings-plan/scope-savings-plan.png" :::
-
-## Discounted subscription and offer types
-
-Savings plan discounts apply to the following eligible subscriptions and offer types.
+## Cancel, exchange, or refund savings plans
 
-- Enterprise agreement (offer numbers: MS-AZR-0017P or MS-AZR-0148P)
-- Microsoft Customer Agreement subscriptions.
-- Microsoft Partner Agreement subscriptions.
+You can't cancel, exchange, or refund savings plans.
 
 ### Buy savings plans with monthly payments
 
@@ -159,5 +140,10 @@ If you have Azure savings plan for compute questions, contact your  account team
 
 ## Next steps
 
-- [Permissions to view and manage Azure savings plans](permission-view-manage.md)
-- [Manage Azure savings plans](manage-savings-plan.md)
+- To learn how to manage a savings plan, see [Manage Azure savings plans](manage-savings-plan.md).
+- To learn more about Azure Savings plans, see the following articles:
+    - [What are Azure Savings plans?](savings-plan-compute-overview.md)
+    - [Manage Azure savings plans](manage-savings-plan.md)
+    - [How saving plan discount is applied](discount-application.md)
+    - [Understand savings plan costs and usage](utilization-cost-reports.md)
+    - [Software costs not included with Azure savings plans](software-costs-not-included.md)

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

@@ -8,40 +8,40 @@ ms.service: cost-management-billing
 ms.subservice: savings-plan
 ms.custom: ignite-2022
 ms.topic: how-to
-ms.date: 12/19/2022
+ms.date: 02/03/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 next. Usage exceeding the savings plan commitment is charged using more expensive pay-as-you-go rates.
+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.
 
 ## 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 calculates 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 calculation is performed for every quantity that you used during the time frame. The commitment amount that maximizes your savings is recommended.
+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).
 
-For example, you might use 500 VMs most of the time, but sometimes usage spikes to 700 VMs. In this example, Azure calculates your savings for both the 500 and 700 VM quantities. Since the 700 VM usage is sporadic, the recommendation calculation determines that savings are maximized for a savings plan commitment that is sufficient to cover 500 VMs and the recommendation is provided for that commitment.
+For example, you might incur about $500 in hourly pay-as-you-go compute charges most of the time, but sometimes usage spikes to $700. Azure determines your total costs (hourly savings plan commitment plus pay-as-you-go charges) if you had either a $500/hour or a $700/hour savings plan. Since the $700 usage is sporadic, the recommendation calculation is likely to determine that a $500 hourly commitment provides greater total savings. As a result, the $500/hour plan would be the recommended commitment.
 
-:::image type="content" source="./media/choose-commitment-amount/savings-plan-usage-spikes.png" alt-text="Diagram showing usage spikes exceeding savings plan recommendations that would get payed for at PAYG pricing." lightbox="./media/choose-commitment-amount/savings-plan-usage-spikes.png" :::
+:::image type="content" source="./media/choose-commitment-amount/savings-plan-usage-spikes.png" alt-text="Diagram showing usage spikes exceeding savings plan recommendations that would get paid for at PAYG pricing." lightbox="./media/choose-commitment-amount/savings-plan-usage-spikes.png" :::
 
 Note the following points:
 
-- Savings plan recommendations are calculated using the on-demand usage rates that apply to you.
-- Recommendations are calculated using individual sizes, not for the instance size family.
-- The recommended commitment for a scope is reduced on the same day that you purchase a commitment for the scope.
-  - However, an update for the commitment amount recommendation across scopes can take up to 25 days. For example, if you purchase based on shared scope recommendations, the single subscription scope recommendations can take up to 25 days to adjust down.
+- Savings plan recommendations are calculated using the pay-as-you-go rates that apply to you.
+- Recommendations are calculated using individual VM sizes, not for the instance size family.
+- The recommended commitment for a scope is updated on the same day that you purchase a savings plan for the scope.
+    - However, an update for the commitment amount recommendation across scopes can take up to three days. For example, if you purchase based on shared scope recommendations, the single subscription scope recommendations can take up to three days to adjust down.
 - Currently, Azure doesn't generate recommendations for the management group scope.
 
 ## 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 shown in the savings plan purchase experience 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).
 
-## Need help? Contact us.
+## 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 will only provide Azure savings plan for compute expert support requests in English.
 
 ## Next steps
 
 - [Manage Azure savings plans](manage-savings-plan.md)
 - [View Azure savings plan cost and usage details](utilization-cost-reports.md)
-- [Software costs not included in saving plan](software-costs-not-included.md)
+- [Software costs not included in saving plan](software-costs-not-included.md)