Update the Az readiness draft

Author: bharathim

articles/energy-data-services/reliability-energy-data-services.md

@@ -60,10 +60,7 @@ The "X" part should identify the product or service.
 Required: Provide an introduction. Use the following placeholder as a suggestion, but elaborate.
 -->
 
-This article describes reliability support in Microsoft Energy Data Services, and covers regional resiliency with [availability zones](../reliability/reliability-functions?toc=%2Fazure%2Fazure-functions%2FTOC.json&tabs=azure-portal#availability-zone-support). For a more detailed overview of reliability in Azure, see [Azure reliability](https://docs.microsoft.com/azure/architecture/framework/resiliency/overview.md).
-
-[Introduction]
-TODO: Add your introduction
+This article describes reliability support in Microsoft Energy Data Services, and covers regional resiliency with [availability zones](#availability-zone-support). For a more detailed overview of reliability in Azure, see [Azure reliability](https://docs.microsoft.com/azure/architecture/framework/resiliency/overview.md).
 
 ## Availability zone support
 <!-- IF (AZ SUPPORTED) -->
@@ -95,14 +92,20 @@ N/A
 <!-- END IF (SERVICE IS ZONAL) -->
 
 ### Fault tolerance
-N/A
+To prepare for availability zone failure, Microsoft Energy Data Services will over-provision capacity of service to ensure that the solution can tolerate ⅓ loss of capacity and continue to function without degraded performance during zone-wide outages.
 
 <!-- 3E. Fault tolerance ---------------------------------------------------------------
 To prepare for availability zone failure, customers should over-provision capacity of service to ensure that the solution can tolerate ⅓ loss of capacity and continue to function without degraded performance during zone-wide outages. Provide any information as to how customers should achieve this.
 -->
 
 ### Zone down experience
-In a zone-wide outage scenario, users should experience no impact on provisioned resources in a zone-redundant deployment. During a zone-wide outage , customers should be prepared to experience brief interruption for communication to provisioned resources; typically, this is manifested by client receiving 409 error code; this prompts re-try logic with appropriate intervals. New requests will be directed to healthy nodes with zero impact on user. During zone-wide outages, users will be able to create new offering resources and successfully scale existing ones. 
+- During a zone-wide outage, no action is required during zone recovery, Offering will self-heal and re-balance itself to take advantage of the healthy zone automatically. 
+    
+- During a zone-wide outage, the customer should expect brief degradation of performance, until the service self-healing re-balances underlying capacity to adjust to healthy zones. This is not dependent on zone restoration; it is expected that the Microsoft-managed service self-healing state will compensate for a lost zone, leveraging capacity from other zones. 
+  
+- In a zone-wide outage scenario, users should experience no impact on provisioned resources in a zone-redundant deployment. During a zone-wide outage , customers should be prepared to experience brief interruption for communication to provisioned resources; this prompts re-try logic with appropriate intervals. New requests will be directed to healthy nodes with zero impact on user. During zone-wide outages, users will be able to create new offering resources; however, there could be capacity constraints, due to which the underlying resources will be scaled on a best-effort basis.
+
+- All Microsoft Energy Data Services APIs may need to be retried for 5XX errors.
 
 <!-- IF (SERVICE IS ZONE REDUNDANT) -->
 
@@ -136,7 +139,7 @@ List the following:
 <!-- END IF (SERVICE IS ZONE REDUNDANT) -->
 
 #### Zone outage preparation and recovery
-TODO: Add your zone outage preparation and recovery
+<!-- TODO: Add your zone outage preparation and recovery -->
 
 <!-- 3G. Zone outage preparation and recovery ------------------------------------------
 The table below lists alerts that can trigger an action to compensate for a loss of capacity or a state for your resources. It also provides information regarding actions for recovery, as well as how to prepare for such alerts prior to the outage.
@@ -146,7 +149,7 @@ The table below lists alerts that can trigger an action to compensate for a loss
 -->
 
 ### Low-latency design
-TODO: Add your low-latency design
+Microsoft guarantees communication between zones of < 2ms and all underlying Microsoft Energy Data Services resources supports it.
 
 <!-- 3H. Low-latency design ------------------------------------------------------------
 -->
@@ -161,30 +164,29 @@ TODO: Add your low-latency design
 
 <!-- END IF (SERVICE IS ZONE REDUNDANT AND ZONAL) -->
 
->[!IMPORTANT]
->By opting out of zone-aware deployment, you forego protection from isolation of underlying faults. Use of SKUs that don't support availability zones or opting out from availability zone configuration forces reliance on resources that don't obey zone placement and separation (including underlying dependencies of these resources). These resources shouldn't be expected to survive zone-down scenarios. Solutions that leverage such resources should define a disaster recovery strategy and configure a recovery of the solution in another region.
 
-### Safe deployment techniques
-TODO: Add your safe deployment techniques
+<!-- ### Safe deployment techniques -->
+<!-- TODO: Add your safe deployment techniques -->
 
 <!-- 3I. Safe deployment techniques ----------------------------------------------------
 If application safe deployment is not relevant for this resource type, explain why and how the service manages availability zones for the customer behind the scenes.
 -->
 
-When you opt for availability zones isolation, you should utilize safe deployment techniques for application code, as well as application upgrades. Describe techniques that the customer should use to target one-zone-at-a-time for deployment and upgrades (for example, virtual machine scale sets). If something is strictly recommended, call it out below.
+<!-- When you opt for availability zones isolation, you should utilize safe deployment techniques for application code, as well as application upgrades. Describe techniques that the customer should use to target one-zone-at-a-time for deployment and upgrades (for example, virtual machine scale sets). If something is strictly recommended, call it out below. -->
 
 <!-- List health signals that the customer should monitor, before proceeding with upgrading next set of nodes in another zone, to contain a potential impact of an unhealthy deployment. -->
-[Health signals]
-TODO: Add your health signals
+<!-- [Health signals] -->
+<!-- TODO: Add your health signals -->
 
-### Availability zone redeployment and migration
-TODO: Add your availability zone redeployment and migration
+<!-- ### Availability zone redeployment and migration -->
+<!-- TODO: Add your availability zone redeployment and migration -->
 
 <!-- 3J. Availability zone redeployment and migration ----------------------------------------------------
 Link to a document that provides step-by-step procedures, using Portal, ARM, CLI, for migrating existing resources to a zone redundant configuration. If such a document doesn't exist, please start the process of creating that document. The template for AZ migration is:
 
 ` [!INCLUDE [AZ migration template](az-migration-template.md)] `
 -->
+
 <!-- END IF (AZ SUPPORTED)-->
 
 ## Next steps