Skip to content

Commit f0fcb78

Browse files
Merge pull request #272689 from TravisCragg-MSFT/patch-118
Update availability.md
2 parents 7a63069 + e2471e0 commit f0fcb78

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

articles/virtual-machines/availability.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,8 @@ This article provides an overview of the availability options for Azure virtual
2121

2222
Each Availability Zone has a distinct power source, network, and cooling. By designing your solutions to use replicated VMs in zones, you can protect your apps and data from the loss of a data center. If one zone is compromised, then replicated apps and data are instantly available in another zone.
2323

24+
> [!NOTE]
25+
> Regional resources may or may not exist in an Availability zone, and there is no insight into what physical or logical zone a regional resource is in. A failure in any of the availability zones in a region has the potential to bring down a regional VM.
2426
2527
## Virtual Machines Scale Sets
2628
[Azure virtual machine scale sets](flexible-virtual-machine-scale-sets.md) let you create and manage a group of load balanced VMs. The number of VM instances can automatically increase or decrease in response to demand or a defined schedule. Scale sets provide high availability to your applications, and allow you to centrally manage, configure, and update many VMs. There is no cost for the scale set itself, you only pay for each VM instance that you create.

0 commit comments

Comments
 (0)