fixes

Author: bandersmsft

articles/cost-management-billing/reservations/azure-openai.md

@@ -20,7 +20,7 @@ To purchase an Azure OpenAI reservation, you choose an Azure region, quantity, a
 When you purchase a reservation, the Azure OpenAI provisioned throughput usage that matches the reservation attributes is no longer charged at the hourly rates. 
 
 >[!NOTE]
->Reservations for Global, Managed Area (Data Zone), and Regional deployments aren't interchangeable. You need to purchase a separate reservation for each deployment type. For more information about transitioning provisioned deployments, see [Transition Azure OpenAI provisioned deployments](azure-openai-provisioned-deployments.md).
+>Reservations for Global, Managed Area (Data Zone), and Regional deployments aren't interchangeable. You need to purchase a separate reservation for each deployment type. For more information about transitioning provisioned deployments, see [Transition Azure OpenAI provisioned deployments](transition-azure-openai-provisoned-deployments.md).
 
 For pricing information, see the [Azure OpenAI Service pricing](https://azure.microsoft.com/pricing/details/cognitive-services/openai-service/) page.
 

articles/cost-management-billing/reservations/transition-azure-openai-provisioned-deployments.md

@@ -44,26 +44,26 @@ If you use existing Azure OpenAI Regional Provisioned deployments, there are two
 
 ### Option 2 – Has downtime
 
-1. Ensure all Azure OpenAI API requests are stopped on the Azure OpenAI Regional Provisioned deployment
-2. Delete the existing Regional Provisioned deployment
+1. Ensure all Azure OpenAI API requests are stopped on the Azure OpenAI Regional Provisioned deployment.
+2. Delete the existing Regional Provisioned deployment.
 3. Create a new deployment using the Azure OpenAI Global Provisioned or Managed Area (Data Zone) Provisioned deployment type in the desired Azure OpenAI resource.
 
 ## Transition Azure OpenAI provisioned reservations from Regional to Global or Data Zone
 
 - First, you must decide how many PTUs you want to retain on the Provisioned Regional deployment. Then decide how many PTUs to move to the provisioned Global or Managed Area (Data Zone) deployments.
 - Of these deployments, you need to decide how many need to get covered by reservations to get the discounted price.
-- Reservations for Global, Managed Area (Data Zone), and Regional deployments aren't inter-changeable. You need to purchase a separate reservation for each deployment type.  
+- Reservations for Global, Managed Area (Data Zone), and Regional deployments aren't inter-changeable. You need to purchase a separate reservation for each deployment type.
 - When you have existing Regional provisioned deployments and want to transition to Global or Managed Area (Data Zone) provisioned deployments, both types of deployments might need to exist for a brief time period to migrate your applications. It results in you right-sizing your Regional provisioned deployments.
 - Based on your desired end state (deployments across Regional, Managed Area (Data Zone), and Global), you need to cancel your existing reservations and purchase new reservations that cover your deployments.
 - It could result in one of two scenarios:
-  - Overlap of existing and newly purchased reservations, resulting in getting charged for both
-  - Time period between cancellation of existing reservations and purchasing new reservations, resulting in deployments being charged at the hourly rate (instead of a reservation price, because there wouldn’t be any reservations covering those deployments)
+  - Overlap of existing and newly purchased reservations, resulting in getting charged for both.
+  - Time period between cancellation of existing reservations and purchasing new reservations, resulting in deployments being charged at the hourly rate (instead of a reservation price, because there wouldn’t be any reservations covering those deployments).
   - In either case, it isn't considered double billing but essential to transition from one deployment to another.
 - Careful planning for transitioning deployments and transitioning reservations minimize charges.
   - When you transition deployments, ensure that the reservation administrator understands the desired end state. Then you can cancel and purchase the right number of reservation units for the respective deployment types.
-  - Avoid hourly charges for deployments by ensuring that all deployments have a matching reservation
-  - Avoid purchasing reservations ahead of time to prevent charges for deployments that aren’t active yet
-  - Cancel reservations that don’t cover any deployments
+  - Avoid hourly charges for deployments by ensuring that all deployments have a matching reservation.
+  - Avoid purchasing reservations ahead of time to prevent charges for deployments that aren’t active yet.
+  - Cancel reservations that don’t cover any deployments.
 - Existing Provisioned Regional reservation cancellation is approved when you buy new Global or Managed Area (Data Zone) reservations to replace or exchange your existing reservations.  
     >[!NOTE]
     >Cancellations are supported for a limited time. You should stop auto renewals for your Provisioned Regional Reservations if want to transition to Global or Managed Area (Data Zone) reservations.
@@ -73,7 +73,8 @@ If you use existing Azure OpenAI Regional Provisioned deployments, there are two
 
 1. Cancel your existing Provisioned Regional reservations for the number of PTUs that you want to transition to Global or Managed Area (Data Zone).
 2. To cover the deployments that you want to transition, purchase corresponding Global or Managed Area (Data Zone) reservations.  
-  For example, assume you have 300 PTUs on the Regional deployment. You decide to transition 200 PTUs to Managed Area (Data Zone) deployment and keep the remaining 100 on Regional deployment. Also, assume that you have one or more reservations to cover all of the 300 existing Regional deployments.
+
+    For example, assume you have 300 PTUs on the Regional deployment. You decide to transition 200 PTUs to Managed Area (Data Zone) deployment and keep the remaining 100 on Regional deployment. Also, assume that you have one or more reservations to cover all of the 300 existing Regional deployments.
     1. To consolidate and realign reservations, your need to cancel your existing reservations for 300 PTUs.
     2. To cover the 200 Managed Area (Data Zone) deployments, purchase a Managed Area (Data Zone) reservation.
     3. Purchase a Regional reservation to cover the 100 Regional deployments.
@@ -87,10 +88,11 @@ In this scenario, you have two options:
 
 1. Let your current monthly reservations expire on their own. For example, stop auto renewal of your existing reservations.
 2. To consolidate and realign reservations, purchase corresponding Global, Managed Area (Data Zone), or Regional reservations. They cover the deployments that you want to transition to.  
-    For example, assume you have 300 PTUs on the Regional deployment. You decide to transition 200 PTUs to Managed Area (Data Zone) deployment and keep the remaining 100 on Regional deployment. Also, assume that you have a single reservation to cover all of the 300 existing Regional deployments.
-      1. To realign reservations, you need to stop auto renewal of the existing reservation that covers the 300 PTUs.
-      2. On the same or following day that a reservation expires, buy a Managed Area (Data Zone) reservation to cover the 200 Managed Area (Data Zone) deployments. Purchase a Regional reservation to cover the 100 Regional deployments.
-      3. Timing the new purchases correctly helps avoid overlap in reservations or being charged at the hourly pay-as-you-go rates.
+
+    For example, assume you have 300 PTUs on the Regional deployment. You decide to transition 200 PTUs to Managed Area (Data Zone) deployment and keep the remaining 100 on Regional deployment. Also, assume that you have a single reservation to cover all of the 300 existing Regional deployments.  
+    1. To realign reservations, you need to stop auto renewal of the existing reservation that covers the 300 PTUs.
+    2. On the same or following day that a reservation expires, buy a Managed Area (Data Zone) reservation to cover the 200 Managed Area (Data Zone) deployments. Purchase a Regional reservation to cover the 100 Regional deployments.
+    3. Timing the new purchases correctly helps avoid overlap in reservations or being charged at the hourly pay-as-you-go rates.
 3. If you think there’s an error or a credit due, you can [create a support request](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest).
 
 **Option 2** - Recommended for multiple monthly reservations
@@ -99,7 +101,7 @@ In this scenario, you have two options:
 
 ## Important information
 
-[!WARNING]
+>[!WARNING]
 >If you cancel your current PTU reservations but don't purchase the new Global or Managed Area (Data Zone) PTU reservations, then all of your PTU deployments get charged at the hourly price.
 
 You can cancel reservations yourself if the amount is less than or equal to $50,000. Otherwise, you must contact Azure support to request cancellation. To contact support for cancellations, see [create a support request](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest).