Skip to content

Commit d9690d4

Browse files
khdowniewmgries
authored andcommitted
Tweak language of availability.
1 parent 251f4ce commit d9690d4

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

includes/storage-files-tiers-overview.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,9 +11,9 @@
1111
---
1212
Azure Files offers two different media tiers of storage, SSD and HDD, which allow you to tailor your shares to the performance and price requirements of your scenario:
1313

14-
- **SSD (Premium)**: Premium file shares use by solid-state drives (SSDs) and provide consistent high performance and low latency, within single-digit milliseconds for most IO operations, for IO-intensive workloads. Premium file shares are suitable for a wide variety of workloads like databases, web site hosting, and development environments. Premium file shares can be used with both Server Message Block (SMB) and Network File System (NFS) protocols. Premium file shares are deployed in the **FileStorage storage account** kind and are only available in a provisioned billing model. For more information on the provisioned billing model for premium file shares, see [Understanding provisioning for premium file shares](../articles/storage/files/understanding-billing.md#provisioned-model). Premium file shares support a [99.99% SLA](https://www.microsoft.com/licensing/docs/view/Service-Level-Agreements-SLA-for-Online-Services) (see "Azure Files Premium Tier").
14+
- **SSD (Premium)**: Premium file shares use by solid-state drives (SSDs) and provide consistent high performance and low latency, within single-digit milliseconds for most IO operations, for IO-intensive workloads. Premium file shares are suitable for a wide variety of workloads like databases, web site hosting, and development environments. Premium file shares can be used with both Server Message Block (SMB) and Network File System (NFS) protocols. Premium file shares are deployed in the **FileStorage storage account** kind and are only available in a provisioned billing model. For more information on the provisioned billing model for premium file shares, see [Understanding provisioning for premium file shares](../articles/storage/files/understanding-billing.md#provisioned-model). Premium file shares offer [99.99% availability](https://www.microsoft.com/licensing/docs/view/Service-Level-Agreements-SLA-for-Online-Services) (see "Azure Files Premium Tier").
1515

16-
- **HDD (Standard)**: Standard file shares use hard disk drives (HDDs) and provide a cost-effective storage option for general purpose file shares. Standard file shares are deployed in the **general purpose version 2 (GPv2) storage account** kind. Standard file shares support a [99.9% SLA](https://www.microsoft.com/licensing/docs/view/Service-Level-Agreements-SLA-for-Online-Services) (see "Storage Accounts"). Standard file shares use a pay-as-you-go model that provides usage-based pricing. You can further tailor the ratio between storage and IOPS cost through *access tiers*:
16+
- **HDD (Standard)**: Standard file shares use hard disk drives (HDDs) and provide a cost-effective storage option for general purpose file shares. Standard file shares are deployed in the **general purpose version 2 (GPv2) storage account** kind. Standard file shares offer [99.9% availability](https://www.microsoft.com/licensing/docs/view/Service-Level-Agreements-SLA-for-Online-Services) (see "Storage Accounts"). Standard file shares use a pay-as-you-go model that provides usage-based pricing. You can further tailor the ratio between storage and IOPS cost through *access tiers*:
1717
- **Transaction optimized**: Transaction optimized file shares enable transaction heavy workloads that don't need the latency offered by premium file shares.
1818
- **Hot**: Hot file shares offer storage optimized for general purpose file sharing scenarios such as team shares.
1919
- **Cool**: Cool file shares offer cost-efficient storage optimized for online archive storage scenarios.

0 commit comments

Comments
 (0)