You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/virtual-machines/dedicated-hosts.md
+7-4Lines changed: 7 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,6 +41,7 @@ Reserving the entire host provides several benefits beyond those of a standard s
41
41
42
42

43
43
44
+
44
45
A **host group** is a resource that represents a collection of dedicated hosts. You create a host group in a region and an availability zone, and add hosts to it.
45
46
46
47
A **host** is a resource, mapped to a physical server in an Azure data center. The physical server is allocated when the host is created. A host is created within a host group. A host has a SKU describing which VM sizes can be created. Each host can host multiple VMs, of different sizes, as long as they are from the same size series.
@@ -159,6 +160,7 @@ Provisioning a dedicated host will consume both dedicated host vCPU and the VM f
159
160
160
161

161
162
163
+
162
164
For more information, see [Virtual machine vCPU quotas](./windows/quotas.md).
163
165
164
166
Free trial and MSDN subscriptions don't have quota for Azure Dedicated Hosts.
@@ -184,7 +186,7 @@ The *type* is the hardware generation. Different hardware types for the same VM
184
186
The sizes and hardware types vary by region. Refer to the host [pricing page](https://aka.ms/ADHPricing) to learn more.
185
187
186
188
> [!NOTE]
187
-
> Once a Dedicated host is provisoned, you can't change the size or type. If you need a different size of type, you will need to create a new host.
189
+
> Once a Dedicated host is provisioned, you can't change the size or type. If you need a different size of type, you will need to create a new host.
188
190
189
191
## Host life cycle
190
192
@@ -194,10 +196,9 @@ Azure monitors and manages the health status of your hosts. The following states
194
196
| Health State | Description |
195
197
|----------|----------------|
196
198
| Host Available | There are no known issues with your host. |
197
-
| Host Under Investigation| We’re having some issues with the host that we’re looking into. This transitional state is required for Azure to try to identify the scope and root cause for the issue identified. Virtual machines running on the host may be impacted. |
199
+
| Host Under Investigation| We’re having some issues with the host that we’re looking into. This transitional state is required for Azure to try to identify the scope and root cause for the issue identified. Virtual machines running on the host may be impacted. |
198
200
| Host Pending Deallocate | Azure can’t restore the host back to a healthy state and ask you to redeploy your virtual machines out of this host. If `autoReplaceOnFailure` is enabled, your virtual machines are *service healed* to healthy hardware. Otherwise, your virtual machine may be running on a host that is about to fail.|
199
-
| Host deallocated | All virtual machines have been removed from the host. You're no longer being charged for this host since the hardware was taken out of rotation. |
200
-
201
+
| Host Deallocated| All virtual machines have been removed from the host. You're no longer being charged for this host since the hardware was taken out of rotation. |
201
202
202
203
## Next steps
203
204
@@ -206,3 +207,5 @@ Azure monitors and manages the health status of your hosts. The following states
206
207
- There's a [sample template](https://github.com/Azure/azure-quickstart-templates/blob/master/quickstarts/microsoft.compute/vm-dedicated-hosts/README.md) that uses both zones and fault domains for maximum resiliency in a region.
207
208
208
209
- You can also save on costs with a [Reserved Instance of Azure Dedicated Hosts](prepay-dedicated-hosts-reserved-instances.md).
0 commit comments