Skip to content

Commit fb401aa

Browse files
authored
Clarifying documentation for the deprecation of isolated sizes
Clarifying documentation for the deprecation of isolated sizes
1 parent 54355b8 commit fb401aa

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

includes/virtual-machines-common-isolation.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@
1010
ms.custom: include file
1111
---
1212

13-
Azure Compute offers virtual machine sizes that are Isolated to a specific hardware type and dedicated to a single customer. The Isolated sizes live and operate on specific hardware generation and will be deprecated when the hardware generation is retired.
13+
Azure Compute offers virtual machine sizes that are Isolated to a specific hardware type and dedicated to a single customer. The Isolated sizes live and operate on specific hardware generation and will be deprecated when the hardware generation is retired or new hardware generation is available.
1414

1515
Isolated virtual machine sizes are best suited for workloads that require a high degree of isolation from other customers’ workloads for reasons that include meeting compliance and regulatory requirements. Utilizing an isolated size guarantees that your virtual machine will be the only one running on that specific server instance.
1616

@@ -37,7 +37,7 @@ The current Isolated virtual machine offerings include:
3737
3838
## Deprecation of Isolated VM Sizes
3939

40-
Isolated VM sizes have a hardware limited lifespan. Azure will issue reminders 12 months in advance of the official deprecation date of the sizes and will provide an updated isolated offering for your consideration.
40+
Isolated VM sizes have a hardware limited lifespan. Azure will issue reminders 12 months in advance of the official deprecation date of the sizes and will provide an updated isolated offering for your consideration. The following sizes have retirement announced.
4141

4242
| Size | Isolation Retirement Date |
4343
| --- | --- |
@@ -51,11 +51,11 @@ Isolated VM sizes have a hardware limited lifespan. Azure will issue reminders 1
5151

5252
## FAQ
5353
### Q: Is the size going to get retired or only its "isolation" feature?
54-
**A**: Currently, only the isolation feature of the VM sizes is being retired. The deprecated isolated sizes will continue to exist in non-isolated state. If isolation is not needed, there is no action to be taken and the VM will continue to work as expected.
54+
**A**: Any size that is published as isolated but have no "i" in the name, the isolation feature of the VM sizes is being retired unless communicated differently. Sizes with "i" in the name will be deprecated.
5555

5656
### Q: Is there a downtime when my vm lands on a non-isolated hardware?
57-
**A**: If there is no need of isolation, no action is needed and there will be no downtime.
58-
On contrary if isolation is required, our announcement will include the recommended replacement size. Selecting the replacement size will require our customers to resize their VMs.
57+
**A**: For VM sizes, where only isolation is deprecating but not the size, no action is needed and there will be no downtime.
58+
On contrary if isolation is required, announcement will include the recommended replacement size. Selecting the replacement size will require customers to resize their VMs.
5959

6060
### Q: Is there any cost delta for moving to a non-isolated virtual machine?
6161
**A**: No

0 commit comments

Comments
 (0)