Skip to content

Commit 8f6297f

Browse files
committed
incorporated review feedback
1 parent 819317b commit 8f6297f

File tree

1 file changed

+39
-10
lines changed

1 file changed

+39
-10
lines changed

articles/lab-services/reliability-in-azure-lab-services.md

Lines changed: 39 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -3,42 +3,42 @@ title: Reliability in Azure Lab Services
33
description: Learn about reliability in Azure Lab Services
44
ms.topic: overview
55
ms.custom: subject-resiliency
6-
ms.date: 08/11/2022
6+
ms.date: 08/16/2022
77
---
88

99
# What is reliability in Azure Lab Services?
1010

11-
Reliability is a system’s ability to recover from failures and continue to function. It’s not only about avoiding failures but also involves responding to failures in a way that minimizes downtime or data loss. Because failures can occur at various levels, it’s important to have protection for all types based on service reliability requirements. Reliability in Azure supports and advances capabilities that respond to outages in real time to ensure continuous service and data protection assurance for mission-critical applications that require near-zero downtime and high customer confidence.
12-
1311
This article describes reliability support in Azure Lab Services, and covers regional resiliency with availability zones. For a more detailed overview of reliability in Azure, see [Azure resiliency](/azure/availability-zones/overview.md).
1412

1513
## Availability zone support
1614

17-
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. In the case of 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).
15+
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. In the case of a local zone failure, availability zones allow the services to failover to the other availability zones to provide continuity in service with minimal interruption. 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).
1816

1917
Azure availability zones-enabled services are designed to provide the right level of resiliency and flexibility. They can be configured in two ways. They can be either zone redundant, with automatic replication across zones, or zonal, with instances pinned to a specific zone. You can also combine these approaches. For more information on zonal vs. zone-redundant architecture, see [Build solutions with availability zones](/azure/architecture/high-availability/building-solutions-for-high-availability).
2018

21-
Azure Lab Services provide zone redundancy for service infrastructure for specific regions. Zone redundancy is provided automatically by Microsoft.
19+
Azure Lab Services provide availability zone redundancy automatically in all regions listed in this article. While the service infrastructure is zone redundant, customer labs and VMs are not zone redundant.
2220

2321
Currently, the service is not zonal. That is, you can’t configure a lab or the VMs in the lab to align to a specific zone. A lab and VMs may be distributed across zones in a region.
2422

2523
### SLA improvements
2624

27-
There are no increased SLAs for Azure Lab Services. For more information on the Azure Lab Services SLAs, see [SLA for Azure Lab Services](https://azure.microsoft.com/support/legal/sla/lab-services/v1_0/).
25+
There are no increased SLAs available for uptime in Azure Lab Services. For the monthly uptime SLAs for Azure Lab Services, see [SLA for Azure Lab Services](https://azure.microsoft.com/support/legal/sla/lab-services/v1_0/).
26+
27+
The Azure Lab Services infrastructure uses Cosmos DB storage. The Cosmos DB storage region is the same as the region where the lab plan is located. All the regional Cosmos DB accounts are single region. In the five regions listed in this article, the Cosmos DB accounts are single region with Availability Zones. In the other regions, the accounts are single region without Availability Zones. For high availability capabilities for these account types, see [SLAs for Cosmos DB](/azure/cosmos-db/high-availability#slas).
2828

2929
### Zone down experience
3030

3131
#### Azure Lab Services infrastructure
3232

33-
Azure Lab Services infrastructure is zone-redundant. The Azure Lab Services infrastructure uses Cosmos DB storage, which has redundancy enabled for the following regions:
33+
Azure Lab Services infrastructure is zone-redundant in the following regions:
3434

3535
- Australia East
3636
- Canada Central
3737
- France Central
3838
- Korea Central
3939
- East Asia
4040

41-
Resources apart from the Lab resources and virtual machines are zone redundant in these regions. The storage region is the same as the region where the lab plan is located.
41+
Resources apart from the Lab resources and virtual machines are zone redundant in these regions.
4242

4343
In the event of a zone outage in these regions, you can still perform the following tasks:
4444

@@ -50,7 +50,10 @@ In the event of a zone outage in these regions, you can still perform the follow
5050

5151
Data loss may occur only with an unrecoverable disaster in the Cosmos DB region. For more information, see [Region Outages](/azure/cosmos-db/high-availability#region-outages).
5252

53-
For regions not listed, access to the Azure Lab Services infrastructure is not guaranteed when there is an outage in the region. You may not be able to access the Azure Lab Services website or perform any of the tasks listed previously.
53+
For regions not listed, access to the Azure Lab Services infrastructure is not guaranteed when there is an outage in the region containing the lab plan. You will only be able to perform the following tasks:
54+
55+
- Access the Azure Lab Services website
56+
- Create new labs and VMs in regions unaffected by the zone outage
5457

5558
> [!NOTE]
5659
> Existing labs and VMs in regions unaffected by the zone outage aren't affected by a loss of infrastructure in the lab plan region. Existing labs and VMs in unaffected regions can still run and operate as normal.
@@ -76,9 +79,35 @@ Lab and VM services will be restored as soon as the zone availability is restore
7679

7780
If infrastructure is impacted, it will be restored when the zone availability is resolved.
7881

82+
### Region down experience
83+
84+
#### Azure Lab Services infrastructure
85+
86+
In a regional outage, the experience of using the Azure Lab Services infrastructure is the same as in a zone outage. For lab plans in zone-redundant regions, you can access the Azure Lab Services website and perform the same tasks described in the [Zone down experience](#zone-down-experience) section for Azure Lab Services infrastructure.
87+
88+
For regions not listed as zone-redundant, the experience of using the Azure Lab Services infrastructure is the same as in a zone outage.
89+
90+
#### Labs and VMs
91+
92+
In a regional outage, you will be unable to manage or use any labs or VMs in the region.
93+
94+
Existing labs and VMs in regions unaffected by the zone outage aren't affected by a loss of infrastructure in the lab plan region. Existing labs and VMs in unaffected regions can still run and operate as normal.
95+
96+
#### Regional outage preparation and recovery
97+
98+
Access to infrastructure, Lab and VM services will be restored as soon as the regional outage is resolved.
99+
100+
If infrastructure is impacted, it will be restored when the regional outage is resolved.
101+
79102
### Fault tolerance
80103

81-
If you want to preserve access to Azure Lab Services infrastructure during a zone outage, create the lab plan in one of the zone-redundant regions listed above.
104+
If you want to preserve access to Azure Lab Services infrastructure during a zone outage, create the lab plan in one of the zone-redundant regions listed.
105+
106+
- Australia East
107+
- Canada Central
108+
- France Central
109+
- Korea Central
110+
- East Asia
82111

83112
## Next steps
84113

0 commit comments

Comments
 (0)