Update blobfuse2-what-is.md

[sanuskaria123]

According to the https://github.com/Azure/azure-storage-fuse/issues/564 , the product group has confirmed that the chown operation is not supported for Data Lake Storage accounts. The current documentation incorrectly mentions both chown and chmod as supported, leading to confusion among users.

[prmerger-automator[bot]]

@sanuskaria123 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

[learn-build-service-prod[bot]]

Learn Build status updates of commit 53f7ace:

:white_check_mark: Validation status: passed

File	Status	Preview URL	Details
articles/storage/blobs/blobfuse2-what-is.md	:white_check_mark:Succeeded

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[Jak-MS]

@akashdubey-ms Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged" @MicrosoftDocs/public-repo-pr-review-team

[v-dirichards]

@akashdubey-ms Can you review this old PR and determine whether it needs to be closed or merged?

@MicrosoftDocs/public-repo-pr-review-team

[v-ccolin]

I sent an email to the content owner today.

@MicrosoftDocs/public-repo-pr-review-team

[ttorble]

I sent a Teams message to the content owner today.

@MicrosoftDocs/public-repo-pr-review-team

[v-ccolin]

I sent an email to the content owner today.

@MicrosoftDocs/public-repo-pr-review-team

[ttorble]

I assigned @tjvishnu per email from the contributor and replied to the email today.

[v-dirichards]

@tjvishnu

Can you review this old PR and determine whether it needs to be closed or merged?

@MicrosoftDocs/public-repo-pr-review-team

[v-dirichards]

@p15nishatr

Can you review this old PR and determine whether it needs to be closed or merged?

The merge conflict will need to be addressed before we can merge.

IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge. If the changes no longer apply, add an explanation and a #please-close comment to close the PR.

@MicrosoftDocs/public-repo-pr-review-team #assign: @p15nishatr

[sanuskaria123]

We can commit them

On Tue, Sep 9, 2025 at 8:34 AM Diana Richards @.***> wrote:

@.**** commented on this pull request.

In articles/storage/blobs/blobfuse2-what-is.md https://github.com/MicrosoftDocs/azure-docs/pull/124904#discussion_r2334033862 :

@@ -137,7 +137,7 @@ 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, 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 chmod operation is supported for Data Lake Storage, whereas the chown operation is not. For FNS block blobs, neither operation is supported. While running a chmod command on a mounted FNS block blob container may return a success message, the operation does not actually take effect.

@sanuskaria123 https://github.com/sanuskaria123 Can you respond to the requested changes or let us know if you would like us to commit them?

@p15nishatr https://github.com/p15nishatr - When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged" @MicrosoftDocs/public-repo-pr-review-team https://github.com/orgs/MicrosoftDocs/teams/public-repo-pr-review-team

— Reply to this email directly, view it on GitHub https://github.com/MicrosoftDocs/azure-docs/pull/124904#discussion_r2334033862, or unsubscribe https://github.com/notifications/unsubscribe-auth/BLE73QHXYR42MFM3GWHIGQT3R3XQXAVCNFSM6AAAAABSFKZQGWVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZTEMBSGE4TAMJZHA . You are receiving this because you were mentioned.Message ID: @.***>