Skip to content

Commit a9e35fb

Browse files
Merge pull request #211881 from jimmart-dev/jammart-encypt-scope-hns
mark encrypt scopes as preview in feature support doc
2 parents 32d7306 + 3b7d4f2 commit a9e35fb

File tree

2 files changed

+9
-4
lines changed

2 files changed

+9
-4
lines changed

articles/storage/blobs/encryption-scope-overview.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: storage
55
author: tamram
66

77
ms.service: storage
8-
ms.date: 07/13/2022
8+
ms.date: 09/20/2022
99
ms.topic: conceptual
1010
ms.author: tamram
1111
ms.reviewer: ozgun
@@ -18,6 +18,11 @@ Encryption scopes enable you to manage encryption with a key that is scoped to a
1818

1919
For more information about working with encryption scopes, see [Create and manage encryption scopes](encryption-scope-manage.md).
2020

21+
> [!IMPORTANT]
22+
> Encryption scopes are in preview for storage accounts with a hierarchical namespace enabled. The preview supports REST, HDFS, NFSv3 and SFTP protocols.
23+
> The preview is provided without a service level agreement, and is not recommended for production workloads. Certain features might not be supported or might have constrained capabilities.
24+
> For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
25+
2126
## How encryption scopes work
2227

2328
By default, a storage account is encrypted with a key that is scoped to the entire storage account. When you define an encryption scope, you specify a key that may be scoped to a container or an individual blob. When the encryption scope is applied to a blob, the blob is encrypted with that key. When the encryption scope is applied to a container, it serves as the default scope for blobs in that container, so that all blobs that are uploaded to that container may be encrypted with the same key. The container can be configured to enforce the default encryption scope for all blobs in the container, or to permit an individual blob to be uploaded to the container with an encryption scope other than the default.

articles/storage/blobs/storage-feature-support-in-storage-accounts.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: normesta
55
ms.subservice: blobs
66
ms.service: storage
77
ms.topic: conceptual
8-
ms.date: 09/19/2022
8+
ms.date: 09/20/2022
99
ms.author: normesta
1010
---
1111

@@ -63,7 +63,7 @@ The following table describes whether a feature is supported in a standard gener
6363
| [Customer-managed keys in a multi-tenant scenario (encryption)](../common/customer-managed-keys-overview.md?toc=/azure/storage/blobs/toc.json) | 🟦 | 🟦 |  ⬤ |  ⬤ |
6464
| [Customer-provided keys (encryption)](encryption-customer-provided-keys.md) | ✅ |  ⬤ |  ⬤ |  ⬤ |
6565
| [Data redundancy options](../common/storage-redundancy.md?toc=/azure/storage/blobs/toc.json) | &#x2705; | &#x2705; | &#x2705;<sup>2</sup> | &#x2705; |
66-
| [Encryption scopes](encryption-scope-overview.md) | &#x2705; | &nbsp;&#x2B24; | &nbsp;&#x2B24; | &nbsp;&#x2B24; |
66+
| [Encryption scopes](encryption-scope-overview.md) | &#x2705; | &#x1F7E6; | &#x1F7E6; | &#x1F7E6; |
6767
| [Immutable storage](immutable-storage-overview.md) | &#x2705; | &#x2705; | &nbsp;&#x2B24; | &nbsp;&#x2B24; |
6868
| [Last access time tracking for lifecycle management](lifecycle-management-overview.md#move-data-based-on-last-accessed-time) | &#x2705; | &#x2705; | &nbsp;&#x2B24; | &#x2705; |
6969
| [Lifecycle management policies (delete blob)](./lifecycle-management-overview.md) | &#x2705; | &#x2705; | &#x2705; | &#x2705; |
@@ -112,7 +112,7 @@ The following table describes whether a feature is supported in a premium block
112112
| [Customer-managed keys in a multi-tenant scenario (encryption)](../common/customer-managed-keys-overview.md?toc=/azure/storage/blobs/toc.json) | &#x1F7E6; | &#x1F7E6; | &nbsp;&#x2B24; | &nbsp;&#x2B24; |
113113
| [Customer-provided keys (encryption)](encryption-customer-provided-keys.md) | &#x2705; | &nbsp;&#x2B24; | &nbsp;&#x2B24; | &nbsp;&#x2B24; |
114114
| [Data redundancy options](../common/storage-redundancy.md?toc=/azure/storage/blobs/toc.json) | &#x2705; | &#x2705; | &#x2705;<sup>2</sup> | &#x2705; |
115-
| [Encryption scopes](encryption-scope-overview.md) | &#x2705; | &nbsp;&#x2B24; | &nbsp;&#x2B24; | &nbsp;&#x2B24; |
115+
| [Encryption scopes](encryption-scope-overview.md) | &#x2705; | &#x1F7E6; | &#x1F7E6; | &#x1F7E6; |
116116
| [Immutable storage](immutable-storage-overview.md) | &#x2705; | &#x2705; | &nbsp;&#x2B24; | &nbsp;&#x2B24; |
117117
| [Last access time tracking for lifecycle management](lifecycle-management-overview.md#move-data-based-on-last-accessed-time) | &#x2705; | &#x2705; | &nbsp;&#x2B24; | &#x2705; |
118118
| [Lifecycle management policies (delete blob)](./lifecycle-management-overview.md) | &#x2705; | &#x2705; | &#x2705; | &#x2705; |

0 commit comments

Comments
 (0)