Merge pull request #278056 from normesta/gen2

adding a link to more information about the sticky bit

Author: prmerger-automator[bot]

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

@@ -6,7 +6,7 @@ author: normesta
 
 ms.service: azure-data-lake-storage
 ms.topic: conceptual
-ms.date: 04/24/2024
+ms.date: 04/12/2024
 ms.author: normesta
 ms.reviewer: jamesbak
 ms.devlang: python
@@ -247,7 +247,7 @@ The mask may be specified on a per-call basis. This allows different consuming s
 
 The sticky bit is a more advanced feature of a POSIX container. In the context of Data Lake Storage Gen2, it is unlikely that the sticky bit will be needed. In summary, if the sticky bit is enabled on a directory,  a child item can only be deleted or renamed by the child item's owning user, the directory's owner, or the Superuser ($superuser).
 
-The sticky bit isn't shown in the Azure portal.
+The sticky bit isn't shown in the Azure portal. To learn more about the sticky bit and how to set it, see [What is the sticky bit Data Lake Storage Gen2?](/troubleshoot/azure/azure-storage/blobs/authentication/adls-gen2-sticky-bit-403-access-denied#what-is-the-sticky-bit-in-adls-gen2).
 
 ## Default permissions on new files and directories