Merge pull request #285769 from normesta/gen2

Gen2 removal from names

Author: Jill Grant

articles/storage/blobs/authorize-access-azure-active-directory.md

@@ -107,7 +107,7 @@ For more information about scope for Azure RBAC role assignments, see [Understan
 
 Azure RBAC provides several built-in roles for authorizing access to blob data using Microsoft Entra ID and OAuth. Some examples of roles that provide permissions to data resources in Azure Storage include:
 
-- [Storage Blob Data Owner](../../role-based-access-control/built-in-roles.md#storage-blob-data-owner): Use to set ownership and manage POSIX access control for Azure Data Lake Storage Gen2. For more information, see [Access control in Azure Data Lake Storage Gen2](../../storage/blobs/data-lake-storage-access-control.md).
+- [Storage Blob Data Owner](../../role-based-access-control/built-in-roles.md#storage-blob-data-owner): Use to set ownership and manage POSIX access control for Azure Data Lake Storage. For more information, see [Access control in Azure Data Lake Storage](../../storage/blobs/data-lake-storage-access-control.md).
 - [Storage Blob Data Contributor](../../role-based-access-control/built-in-roles.md#storage-blob-data-contributor): Use to grant read/write/delete permissions to Blob storage resources.
 - [Storage Blob Data Reader](../../role-based-access-control/built-in-roles.md#storage-blob-data-reader): Use to grant read-only permissions to Blob storage resources.
 - [Storage Blob Delegator](../../role-based-access-control/built-in-roles.md#storage-blob-delegator): Get a user delegation key to use to create a shared access signature that is signed with Microsoft Entra credentials for a container or blob.

articles/storage/blobs/blob-inventory.md

@@ -172,9 +172,9 @@ View the JSON for inventory rules by selecting the **Code view** tab in the **Bl
 ### Custom schema fields supported for blob inventory
 
 > [!NOTE]
-> The **Data Lake Storage Gen2** column shows support in accounts that have the hierarchical namespace feature enabled.
+> The **Data Lake Storage** column shows support in accounts that have the hierarchical namespace feature enabled.
 
-| Field | Blob Storage (default support) | Data Lake Storage Gen2 |
+| Field | Blob Storage (default support) | Data Lake Storage |
 |---------------|-------------------|---|
 | Name (Required)  | ![Yes](../media/icons/yes-icon.png) | ![Yes](../media/icons/yes-icon.png) |
 | Creation-Time  | ![Yes](../media/icons/yes-icon.png) | ![Yes](../media/icons/yes-icon.png) |
@@ -232,9 +232,9 @@ View the JSON for inventory rules by selecting the **Code view** tab in the **Bl
 ### Custom schema fields supported for container inventory
 
 > [!NOTE]
-> The **Data Lake Storage Gen2** column shows support in accounts that have the hierarchical namespace feature enabled.
+> The **Data Lake Storage** column shows support in accounts that have the hierarchical namespace feature enabled.
 
-| Field | Blob Storage (default support) | Data Lake Storage Gen2 |
+| Field | Blob Storage (default support) | Data Lake Storage |
 |---------------|-------------------|---|
 | Name (Required)  | ![Yes](../media/icons/yes-icon.png) | ![Yes](../media/icons/yes-icon.png) |
 | Last-Modified  | ![Yes](../media/icons/yes-icon.png) | ![Yes](../media/icons/yes-icon.png) |

articles/storage/blobs/blobfuse2-how-to-deploy.md

@@ -287,12 +287,12 @@ However, you should be aware of some key [differences in functionality](blobfuse
 
 This table shows how this feature is supported in your account and the effect on support when you enable certain capabilities:
 
-| Storage account type | Blob Storage (default support) | Data Lake Storage Gen2 <sup>1</sup> | NFS 3.0 <sup>1</sup> | SFTP <sup>1</sup> |
+| Storage account type | Blob Storage (default support) | Data Lake Storage  <sup>1</sup> | NFS 3.0 <sup>1</sup> | SFTP <sup>1</sup> |
 |--|--|--|--|--|
 | Standard general-purpose v2 | ![Yes](../media/icons/yes-icon.png) |![Yes](../media/icons/yes-icon.png)              | ![Yes](../media/icons/yes-icon.png) | ![Yes](../media/icons/yes-icon.png) |
 | Premium block blobs          | ![Yes](../media/icons/yes-icon.png)|![Yes](../media/icons/yes-icon.png) | ![Yes](../media/icons/yes-icon.png) | ![Yes](../media/icons/yes-icon.png) |
 
-<sup>1</sup> Azure Data Lake Storage Gen2, Network File System (NFS) 3.0 protocol, and SSH File Transfer Protocol (SFTP) support all require a storage account with a hierarchical namespace enabled.
+<sup>1</sup> Azure Data Lake Storage, Network File System (NFS) 3.0 protocol, and SSH File Transfer Protocol (SFTP) support all require a storage account with a hierarchical namespace enabled.
 
 ## See also
 

articles/storage/blobs/blobfuse2-what-is.md

@@ -33,7 +33,7 @@ The BlobFuse2 project is [licensed under the MIT license](https://github.com/Azu
 
 A full list of BlobFuse2 features is in the [BlobFuse2 README](https://github.com/Azure/azure-storage-fuse/blob/main/README.md#features). These are some of the key tasks you can perform by using BlobFuse2:
 
-- Mount an Azure Blob Storage container or Azure Data Lake Storage Gen2 file system on Linux.  (BlobFuse2 supports storage accounts with either flat namespaces or hierarchical namespace configured.)
+- Mount an Azure Blob Storage container or Azure Data Lake Storage file system on Linux.  (BlobFuse2 supports storage accounts with either flat namespaces or hierarchical namespace configured.)
 - Use basic file system operations like `mkdir`, `opendir`, `readdir`, `rmdir`, `open`, `read`, `create`, `write`, `close`, `unlink`, `truncate`, `stat`, and `rename`.
 - Use local file caching to improve subsequent access times.
 - Gain insights into mount activities and resource usage by using BlobFuse2 Health Monitor.
@@ -103,7 +103,7 @@ BlobFuse2 is different from the Linux file system in some key ways:
 
 - **chown and chmod**:
 
-  Data Lake Storage Gen2 storage accounts support per object permissions and ACLs, but flat namespace (FNS) block blobs don't. As a result, BlobFuse2 doesn't support the `chown` and `chmod` operations for mounted block blob containers. The operations are supported for Data Lake Storage Gen2.
+  Data Lake Storage storage accounts support per object permissions and ACLs, but flat namespace (FNS) block blobs don't. As a result, BlobFuse2 doesn't support the `chown` and `chmod` operations for mounted block blob containers. The operations are supported for Data Lake Storage.
 
 - **Device files or pipes**:
 
@@ -137,18 +137,18 @@ Reading the same blob from multiple simultaneous threads is supported. However,
 
 When a container is mounted with the default options, all files get 770 permissions and are accessible only by the user who does the mounting. To allow any user to access the BlobFuse2 mount, mount BlobFuse2 by using the `--allow-other` option. You also can configure this option in the YAML config file.
 
-As stated earlier, the `chown` and `chmod` operations are supported for Data Lake Storage Gen2, but not for FNS block blobs. Running a `chmod` operation against a mounted FNS block blob container returns a success message, but the operation doesn't actually succeed.
+As stated earlier, the `chown` and `chmod` operations are supported for Data Lake Storage, but not for FNS block blobs. Running a `chmod` operation against a mounted FNS block blob container returns a success message, but the operation doesn't actually succeed.
 
 ## Feature support
 
 This table shows how this feature is supported in your account and the effect on support when you enable certain capabilities.
 
-| Storage account type | Blob Storage (default support) | Data Lake Storage Gen2 <sup>1</sup> | Network File System (NFS) 3.0 <sup>1</sup> | SSH File Transfer Protocol (SFTP) <sup>1</sup> |
+| Storage account type | Blob Storage (default support) | Data Lake Storage <sup>1</sup> | Network File System (NFS) 3.0 <sup>1</sup> | SSH File Transfer Protocol (SFTP) <sup>1</sup> |
 |--|--|--|--|--|
 | Standard general-purpose v2 | ![Yes](../media/icons/yes-icon.png) |![Yes](../media/icons/yes-icon.png)              | ![Yes](../media/icons/yes-icon.png) | ![Yes](../media/icons/yes-icon.png) |
 | Premium block blobs          | ![Yes](../media/icons/yes-icon.png)|![Yes](../media/icons/yes-icon.png) | ![Yes](../media/icons/yes-icon.png) | ![Yes](../media/icons/yes-icon.png) |
 
-<sup>1</sup> Data Lake Storage Gen2, the NFS 3.0 protocol, and SFTP support all require a storage account that has a hierarchical namespace enabled.
+<sup>1</sup> Data Lake Storage, the NFS 3.0 protocol, and SFTP support all require a storage account that has a hierarchical namespace enabled.
 
 ## See also
 

articles/storage/blobs/create-data-lake-storage-account.md

@@ -1,7 +1,7 @@
 ---
-title: Create a storage account for Azure Data Lake Storage Gen2
+title: Create a storage account for Azure Data Lake Storage
 titleSuffix: Azure Storage
-description: Learn how to create a storage account for use with Azure Data Lake Storage Gen2.
+description: Learn how to create a storage account for use with Azure Data Lake Storage.
 author: normesta
 
 ms.topic: how-to
@@ -10,9 +10,9 @@ ms.date: 03/09/2023
 ms.service: azure-data-lake-storage
 ---
 
-# Create a storage account to use with Azure Data Lake Storage Gen2
+# Create a storage account to use with Azure Data Lake Storage
 
-To use Data Lake Storage Gen2 capabilities, create a storage account that has a hierarchical namespace.
+To use Data Lake Storage capabilities, create a storage account that has a hierarchical namespace.
 
 For step-by-step guidance, see [Create a storage account](../common/storage-account-create.md?toc=/azure/storage/blobs/toc.json).
 
@@ -45,10 +45,10 @@ The following image shows this setting in the **Create storage account** page.
 > [!div class="mx-imgBorder"]
 > ![Hierarchical namespace setting](./media/create-data-lake-storage-account/hierarchical-namespace-feature.png)
 
-To enable Data Lake Storage capabilities on an existing account, see [Upgrade Azure Blob Storage with Azure Data Lake Storage Gen2 capabilities](upgrade-to-data-lake-storage-gen2-how-to.md).
+To enable Data Lake Storage capabilities on an existing account, see [Upgrade Azure Blob Storage with Azure Data Lake Storage capabilities](upgrade-to-data-lake-storage-gen2-how-to.md).
 
 ## Next steps
 
 - [Storage account overview](../common/storage-account-overview.md)
-- [Upgrade Azure Blob Storage with Azure Data Lake Storage Gen2 capabilities](upgrade-to-data-lake-storage-gen2-how-to.md)
-- [Access control in Azure Data Lake Storage Gen2](data-lake-storage-access-control.md)
+- [Upgrade Azure Blob Storage with Azure Data Lake Storage capabilities](upgrade-to-data-lake-storage-gen2-how-to.md)
+- [Access control in Azure Data Lake Storage](data-lake-storage-access-control.md)

articles/storage/blobs/data-lake-storage-abfs-driver.md

@@ -1,7 +1,7 @@
 ---
-title: The Azure Blob Filesystem driver for Azure Data Lake Storage Gen2
+title: The Azure Blob Filesystem driver for Azure Data Lake Storage
 titleSuffix: Azure Storage
-description: Learn about the Azure Blob Filesystem driver (ABFS), a dedicated Azure Storage driver for Hadoop. Access data in Azure Data Lake Storage Gen2 using this driver.
+description: Learn about the Azure Blob Filesystem driver (ABFS), a dedicated Azure Storage driver for Hadoop. Access data in Azure Data Lake Storage using this driver.
 author: normesta
 
 ms.topic: conceptual
@@ -13,7 +13,7 @@ ms.service: azure-data-lake-storage
 
 # The Azure Blob Filesystem driver (ABFS): A dedicated Azure Storage driver for Hadoop
 
-One of the primary access methods for data in Azure Data Lake Storage Gen2 is via the [Hadoop FileSystem](https://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-common/filesystem/index.html). Data Lake Storage Gen2 allows users of Azure Blob Storage access to a new driver, the Azure Blob File System driver or `ABFS`. ABFS is part of Apache Hadoop and is included in many of the commercial distributions of Hadoop. By the ABFS driver, many applications and frameworks can access data in Azure Blob Storage without any code explicitly referencing Data Lake Storage Gen2.
+One of the primary access methods for data in Azure Data Lake Storage is via the [Hadoop FileSystem](https://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-common/filesystem/index.html). Data Lake Storage allows users of Azure Blob Storage access to a new driver, the Azure Blob File System driver or `ABFS`. ABFS is part of Apache Hadoop and is included in many of the commercial distributions of Hadoop. By the ABFS driver, many applications and frameworks can access data in Azure Blob Storage without any code explicitly referencing Data Lake Storage.
 
 ## Prior capability: The Windows Azure Storage Blob driver
 
@@ -27,7 +27,7 @@ However, there are some functions that the driver must still perform:
 
 ### URI scheme to reference data
 
-Consistent with other file system implementations within Hadoop, the ABFS driver defines its own URI scheme so that resources (directories and files) may be distinctly addressed. The URI scheme is documented in [Use the Azure Data Lake Storage Gen2 URI](./data-lake-storage-introduction-abfs-uri.md). The structure of the URI is: `abfs[s]://file_system@account_name.dfs.core.windows.net/<path>/<path>/<file_name>`
+Consistent with other file system implementations within Hadoop, the ABFS driver defines its own URI scheme so that resources (directories and files) may be distinctly addressed. The URI scheme is documented in [Use the Azure Data Lake Storage URI](./data-lake-storage-introduction-abfs-uri.md). The structure of the URI is: `abfs[s]://file_system@account_name.dfs.core.windows.net/<path>/<path>/<file_name>`
 
 By using this URI format, standard Hadoop tools and frameworks can be used to reference these resources:
 
@@ -40,14 +40,14 @@ Internally, the ABFS driver translates the resource(s) specified in the URI to f
 
 ### Authentication
 
-The ABFS driver supports two forms of authentication so that the Hadoop application may securely access resources contained within a Data Lake Storage Gen2 capable account. Full details of the available authentication schemes are provided in the [Azure Storage security guide](security-recommendations.md). They are:
+The ABFS driver supports two forms of authentication so that the Hadoop application may securely access resources contained within a Data Lake Storage capable account. Full details of the available authentication schemes are provided in the [Azure Storage security guide](security-recommendations.md). They are:
 
 - **Shared Key:** This permits users access to ALL resources in the account. The key is encrypted and stored in Hadoop configuration.
 
 - **Microsoft Entra ID OAuth Bearer Token:** Microsoft Entra bearer tokens are acquired and refreshed by the driver using either the identity of the end user or a configured Service Principal. Using this authentication model, all access is authorized on a per-call basis using the identity associated with the supplied token and evaluated against the assigned POSIX Access Control List (ACL).
 
    > [!NOTE]
-   > Azure Data Lake Storage Gen2 supports only Azure AD v1.0 endpoints.
+   > Azure Data Lake Storage supports only Azure AD v1.0 endpoints.
 
 ### Configuration
 
@@ -62,4 +62,4 @@ The ABFS driver is fully documented in the [Official Hadoop documentation](https
 ## Next steps
 
 - [Create an Azure Databricks Cluster](./data-lake-storage-use-databricks-spark.md)
-- [Use the Azure Data Lake Storage Gen2 URI](./data-lake-storage-introduction-abfs-uri.md)
+- [Use the Azure Data Lake Storage URI](./data-lake-storage-introduction-abfs-uri.md)

articles/storage/blobs/data-lake-storage-access-control-model.md

@@ -1,5 +1,5 @@
 ---
-title: Access control model for Azure Data Lake Storage Gen2
+title: Access control model for Azure Data Lake Storage
 titleSuffix: Azure Storage
 description: Learn how to configure container, directory, and file-level access in accounts that have a hierarchical namespace.
 author: normesta
@@ -11,9 +11,9 @@ ms.author: normesta
 ms.custom: engagement-fy23
 ---
 
-# Access control model in Azure Data Lake Storage Gen2
+# Access control model in Azure Data Lake Storage
 
-Data Lake Storage Gen2 supports the following authorization mechanisms:
+Data Lake Storage supports the following authorization mechanisms:
 
 - Shared Key authorization
 - Shared access signature (SAS) authorization
@@ -51,7 +51,7 @@ For more information on using Azure ABAC to control access to Azure Storage, see
 
 ## Access control lists (ACLs)
 
-ACLs give you the ability to apply "finer grain" level of access to directories and files. An *ACL* is a permission construct that contains a series of *ACL entries*. Each ACL entry associates security principal with an access level. To learn more, see [Access control lists (ACLs) in Azure Data Lake Storage Gen2](data-lake-storage-access-control.md).
+ACLs give you the ability to apply "finer grain" level of access to directories and files. An *ACL* is a permission construct that contains a series of *ACL entries*. Each ACL entry associates security principal with an access level. To learn more, see [Access control lists (ACLs) in Azure Data Lake Storage](data-lake-storage-access-control.md).
 
 ## How permissions are evaluated
 
@@ -131,12 +131,12 @@ By using groups, you're less likely to exceed the maximum number of role assignm
 
 ## Shared Key and Shared Access Signature (SAS) authorization
 
-Azure Data Lake Storage Gen2 also supports [Shared Key](/rest/api/storageservices/authorize-with-shared-key) and [SAS](../common/storage-sas-overview.md?toc=/azure/storage/blobs/toc.json) methods for authentication. A characteristic of these authentication methods is that no identity is associated with the caller and therefore security principal permission-based authorization cannot be performed.
+Azure Data Lake Storage also supports [Shared Key](/rest/api/storageservices/authorize-with-shared-key) and [SAS](../common/storage-sas-overview.md?toc=/azure/storage/blobs/toc.json) methods for authentication. A characteristic of these authentication methods is that no identity is associated with the caller and therefore security principal permission-based authorization cannot be performed.
 
 In the case of Shared Key, the caller effectively gains 'super-user' access, meaning full access to all operations on all resources including data, setting owner, and changing ACLs.
 
 SAS tokens include allowed permissions as part of the token. The permissions included in the SAS token are effectively applied to all authorization decisions, but no additional ACL checks are performed.
 
 ## Next steps
 
-To learn more about access control lists, see [Access control lists (ACLs) in Azure Data Lake Storage Gen2](data-lake-storage-access-control.md).
+To learn more about access control lists, see [Access control lists (ACLs) in Azure Data Lake Storage](data-lake-storage-access-control.md).