Skip to content

Commit 0158beb

Browse files
v-ccolinv-ccolin
authored
Merge pull request #221149 from bharathim/meds-reliability
Initial draft for Az documentation
2 parents 2d500f5 + c626263 commit 0158beb

File tree

2 files changed

+90
-0
lines changed

2 files changed

+90
-0
lines changed

‎articles/energy-data-services/toc.yml

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -43,6 +43,11 @@
4343
href: concepts-ddms.md
4444
- name: Entitlements
4545
href: concepts-entitlements.md
46+
- name: Reliability
47+
items:
48+
- name: Reliability overview
49+
href: ../reliability/reliability-energy-data-services.md?toc=/azure/energy-data-services/toc.yml
50+
displayName: availability zones, high-availability, zone redundancy
4651
- name: How-to guides
4752
items:
4853
- name: Administration

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

Lines changed: 85 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,85 @@
1+
---
2+
title: Resiliency in Microsoft Energy Data Services #Required; Must be "Resiliency in *your official service name*"
3+
description: Find out about reliability in Microsoft Energy Data Services #Required;
4+
author: bharathim #Required; your GitHub user alias, with correct capitalization.
5+
ms.author: bselvaraj #Required; Microsoft alias of author; optional team alias.
6+
ms.topic: overview
7+
ms.custom: subject-reliability
8+
ms.prod: non-product-specific
9+
ms.date: 12/05/2022 #Required; mm/dd/yyyy format.
10+
---
11+
12+
<!--#Customer intent: As a customer, I want to understand reliability support for Microsoft Energy Data Services so that I can respond to and/or avoid failures in order to minimize downtime and data loss. -->
13+
14+
<!--
15+
16+
Template for the main reliability article for Azure services.
17+
Keep the required sections and add/modify any content for any information specific to your service.
18+
This article should live in the reliability content area of azure-docs-pr.
19+
This article should be linked to in your TOC. Under a Reliability node or similar. The name of this page should be *reliability-Microsoft Energy Data Services.md* and the TOC title should be "Reliability in Microsoft Energy Data Services".
20+
Keep the headings in this order.
21+
22+
This template uses comment pseudo code to indicate where you must choose between two options or more.
23+
24+
Conditions are used in this document in the following manner and can be easily searched for:
25+
-->
26+
27+
<!-- IF (AZ SUPPORTED) -->
28+
<!-- some text -->
29+
<!-- END IF (AZ SUPPORTED)-->
30+
31+
<!-- BEGIN IF (SLA INCREASE) -->
32+
<!-- some text -->
33+
<!-- END IF (SLA INCREASE) -->
34+
35+
<!-- IF (SERVICE IS ZONAL) -->
36+
<!-- some text -->
37+
<!-- END IF (SERVICE IS ZONAL) -->
38+
39+
<!-- IF (SERVICE IS ZONE REDUNDANT) -->
40+
<!-- some text -->
41+
<!-- END IF (SERVICE IS ZONAL) -->
42+
43+
<!--
44+
45+
IMPORTANT:
46+
- Do a search and replace of TODO-service-name with the name of your service. That will make the template easier to read.
47+
- ALL sections are required unless noted otherwise.
48+
- MAKE SURE YOU REMOVE ALL COMMENTS BEFORE PUBLISH!!!!!!!!
49+
50+
-->
51+
52+
<!-- 1. H1 -----------------------------------------------------------------------------
53+
Required: Uses the format "What is reliability in X?"
54+
The "X" part should identify the product or service.
55+
-->
56+
57+
# What is reliability in Microsoft Energy Data Services?
58+
59+
<!-- 2. Introductory paragraph ---------------------------------------------------------
60+
Required: Provide an introduction. Use the following placeholder as a suggestion, but elaborate.
61+
-->
62+
63+
This article describes reliability support in Microsoft Energy Data Services, and covers intra-regional resiliency with [availability zones](#availability-zone-support). For a more detailed overview of reliability in Azure, see [Azure reliability](../reliability/overview.md).
64+
65+
## Availability zone support
66+
<!-- IF (AZ SUPPORTED) -->
67+
Azure availability zones are at least three physically separate groups of datacenters within each Azure region. Datacenters within each zone are equipped with independent power, cooling, and networking infrastructure. If there's a local zone failure, availability zones are designed so that if the one zone is affected, regional services, capacity, and high availability are supported by the remaining two zones. Failures can range from software and hardware failures to events such as earthquakes, floods, and fires. Tolerance to failures is achieved with redundancy and logical isolation of Azure services. For more detailed information on availability zones in Azure, see [Regions and availability zones](/azure/availability-zones/az-overview.md).
68+
69+
Microsoft Energy Data Services Preview supports zone-redundant instance by default and there's no setup required by the Customer.
70+
71+
### Prerequisites
72+
73+
The Microsoft Energy Data Services Preview supports availability zones in the following regions:
74+
75+
| Americas | Europe | Middle East | Africa | Asia Pacific |
76+
|------------------|----------------------|---------------|--------------------|----------------|
77+
| South Central US | North Europe | | | |
78+
| East US | West Europe | | | |
79+
80+
### Zone down experience
81+
During a zone-wide outage, no action is required during zone recovery. Customer may however experience brief degradation of performance, until the service self-heals and rebalances underlying capacity to adjust to healthy zones. Customers experiencing failures with Microsoft Energy Data Services APIs may need to be retried for 5XX errors.
82+
83+
## Next steps
84+
> [!div class="nextstepaction"]
85+
> [Resiliency in Azure](/azure/availability-zones/overview.md)

0 commit comments

Comments
 (0)