Skip to content

Commit 40d6b5e

Browse files
committed
Fix build issues.
1 parent c0dc3a5 commit 40d6b5e

File tree

2 files changed

+11
-11
lines changed

2 files changed

+11
-11
lines changed

articles/storage/files/geo-redundant-storage-for-large-file-shares.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -65,17 +65,17 @@ Perform the following steps to configure 100TiB shares and geo-redundancy for ne
6565

6666
Perform the following steps to configure geo-redundancy for a new storage account and Azure file share.
6767

68-
1. [Create a standard storage account](storage-how-to-create-file-share.md?tabs=azure-portal#create-a-storage-account) and select geo-redundant storage (GRS) or geo-zone redundant storage (GZRS) for the **Redundancy** option.
69-
2. [Create an SMB Azure file share](storage-how-to-create-file-share.md?tabs=azure-portal#create-a-file-share). New file shares that are created default to 100 TiB.
68+
1. [Create a standard storage account](storage-how-to-create-file-share.md#create-a-storage-account) and select geo-redundant storage (GRS) or geo-zone redundant storage (GZRS) for the **Redundancy** option.
69+
2. [Create an SMB Azure file share](storage-how-to-create-file-share.md#create-a-file-share). New file shares that are created default to 100 TiB.
7070

7171
#### Existing storage accounts with a redundancy option of LRS or ZRS
7272

7373
1. [Change the redundancy option](../common/redundancy-migration.md?tabs=portal#change-the-redundancy-configuration-using-azure-portal-powershell-or-azure-cli) for your storage account to GRS or GZRS.
74-
2. [Increase the file share quota](storage-how-to-create-file-share.md?tabs=azure-portal#expand-existing-file-shares) up to 100 TiB. [New file shares that are created](storage-how-to-create-file-share.md?tabs=azure-portal#create-a-file-share) default to 100 TiB.
74+
2. [Increase the file share quota](storage-how-to-create-file-share.md#change-the-cost-and-performance-characteristics-of-a-pay-as-you-go-file-share) up to 100 TiB. [New file shares that are created](storage-how-to-create-file-share.md#create-a-file-share) default to 100 TiB.
7575

7676
#### Existing storage accounts with a redundancy option of GRS, GZRS, RA-GRS, or RA-GZRS
7777

78-
1. [Increase the file share quota](storage-how-to-create-file-share.md?tabs=azure-portal#expand-existing-file-shares) up to 100 TiB. [New file shares that are created](storage-how-to-create-file-share.md?tabs=azure-portal#create-a-file-share) default to 100 TiB.
78+
1. [Increase the file share quota](storage-how-to-create-file-share.md#change-the-cost-and-performance-characteristics-of-a-pay-as-you-go-file-share) up to 100 TiB. [New file shares that are created](storage-how-to-create-file-share.md#create-a-file-share) default to 100 TiB.
7979

8080
## Snapshot and sync frequency
8181

articles/storage/files/storage-how-to-create-file-share.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -150,9 +150,9 @@ The **Encryption** tab controls settings related to encryption at rest.
150150

151151
| Field name | Input type | Values | Applicable to Azure Files | Meaning |
152152
|-|-|-|-|-|
153-
| Encryption type | Radio button group | <ul><li>Microsoft-managed keys</li><li>Customer-managed keys</li></ul> | Yes | This setting controls who holds the encryption key for the data placed in this storage account. See [Encryption for data at rest](../common/storage-service-encryption?toc=%2Fazure%2Fstorage%2Ffiles%2Ftoc.json) for more information. |
153+
| Encryption type | Radio button group | <ul><li>Microsoft-managed keys</li><li>Customer-managed keys</li></ul> | Yes | This setting controls who holds the encryption key for the data placed in this storage account. See [Encryption for data at rest](../common/storage-service-encryption.md?toc=%2Fazure%2Fstorage%2Ffiles%2Ftoc.json) for more information. |
154154
| Enable support for customer-managed keys | Radio button group | <ul><li>Blobs and files only</li><li>All service types (blobs, files, tables, and queues)</li></ul> | No | All kind/SKU combinations Azure file shares can exist in can support customer-managed keys regardless of this setting. |
155-
| Enable infrastructure encryption | Checkbox | Checked/unchecked | Yes | Storage accounts can optional use a secondary layer of encryption for data stored in the system to guard against one of the keys being compromised. See [Enable infrastructure encryption](../common/infrastructure-encryption-enable?toc=%2Fazure%2Fstorage%2Ffiles%2Ftoc.json&tabs=portal) for more information. |
155+
| Enable infrastructure encryption | Checkbox | Checked/unchecked | Yes | Storage accounts can optional use a secondary layer of encryption for data stored in the system to guard against one of the keys being compromised. See [Enable infrastructure encryption](../common/infrastructure-encryption-enable.md?toc=%2Fazure%2Fstorage%2Ffiles%2Ftoc.json) for more information. |
156156

157157
### Tags
158158
Tags are name/value pairs that enable you to categorize resources and view consolidated billing by applying the same tag to multiple resources and resource groups. These are optional and can be applied after storage account creation.
@@ -308,7 +308,7 @@ Follow these instructions to create a new Azure file share using the Azure porta
308308

309309
3. Complete the field in the **Basics** tab of the new file share blade:
310310

311-
![A screenshot of the basics tab in the new file share blade.](./media/storage-how-to-create-file-share/create-file-share-provisioned-v2-1.png)
311+
![A screenshot of the basics tab in the new file share blade (provisioned v2).](./media/storage-how-to-create-file-share/create-file-share-provisioned-v2-1.png)
312312

313313
- **Name**: The name of the file share to be created.
314314

@@ -438,7 +438,7 @@ Follow these instructions to create a new Azure file share using the Azure porta
438438

439439
3. Complete the fields in the **Basics** tab of new file share blade:
440440

441-
![A screenshot of the basics tab in the new file share blade.](./media/storage-how-to-create-file-share/create-file-share-provisioned-v1-0.png)
441+
![A screenshot of the basics tab in the new file share blade (provisioned v1).](./media/storage-how-to-create-file-share/create-file-share-provisioned-v1-0.png)
442442

443443
- **Name**: The name of the file share to be created.
444444

@@ -571,7 +571,7 @@ az storage share-rm create \
571571
## Change the cost and performance characteristics of a file share
572572
After you've created your file share, you may need to adjust the provisioning (provisioned models) or access tier (pay-as-you-go model) of the share. The following sections show you how to adjust the relevant properties for your share.
573573

574-
### Provisioned v2 file shares
574+
### Change the cost and performance characteristics of a provisioned v2 file share
575575
After creating your provisioned v2 file share, you can change one or all three of the provisioned quantities of your file share.
576576

577577
# [Portal](#tab/azure-portal)
@@ -721,7 +721,7 @@ az resource patch \
721721

722722
---
723723

724-
### Provisioned v1 file shares
724+
### Change the cost and performance characteristics of a provisioned v1 file share
725725
After creating your provisioned v1 file share, you can change the provisioned storage size of the file share. Changing the provisioned storage of the share will also change the amount of provisioned IOPS and provisioned throughput. For more information, see [provisioned v1 provisioning detail](./understanding-billing.md#provisioned-v1-provisioning-detail).
726726

727727
# [Portal](#tab/azure-portal)
@@ -783,7 +783,7 @@ az storage share-rm update \
783783

784784
---
785785

786-
### Pay-as-you-go file shares
786+
### Change the cost and performance characteristics of a pay-as-you-go file share
787787
After you've created your pay-as-you-go file share, there are two properties you may want to change:
788788

789789
- **Access tier**: The access tier of the file share dictates to the ratio of storage to IOPS/throughput costs (in the form of transactions). There are three access tiers: *transaction optimized*, *hot*, and *cool*. Changing the tier of the Azure file share results in transaction costs for the movement to the new access tier. For more information, see [switching between access tiers](./understanding-billing.md#switching-between-access-tiers).

0 commit comments

Comments
 (0)