Update blobfuse2-commands-secure-decrypt.md

[ShraddhaSSwadi]

I am proposing changes to this file post discussing with SE Sourav Gupta (souravgupta)

[prmerger-automator]

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

[learn-build-service-prod]

Learn Build status updates of commit e2fb1e4:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/storage/blobs/blobfuse2-commands-secure-decrypt.md	✅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

[Court72]

@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

[Court72]

@akashdubey-ms

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

[Court72]

I sent an email to the content owner today.

[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

[ttorble]

Hi @ShraddhaSSwadi

Thanks for reaching out in Teams.

Because this PR was created in the public repo, only the listed author can sign off on updates. You can wait for approval from the author or you can close this PR and make the change in the private repo azure-docs-pr.

Read about authors working in the public repo for more information.

If you need help getting set up to work in the private repo, see Get started contributing to the Microsoft Learn platform.

Important: Contributor guidance has moved to https://learn.microsoft.com/help/
To access the guides, you must log in with your Learn profile. If you don't have a Learn profile, follow the instructions at Manage your Microsoft Learn profile settings | Microsoft Learn to create one.

After you make your changes in the private repo, review the articles on staging, and fix any validation issues, you can add the #sign-off comment to let PR reviewers know that the updates are ready to be merged. 

I've sent a follow-up email to the author asking them to review your PR. I copied you in the email. If you decide to move forward in the private repo, please close this PR.

Thanks

cc @akashdubey-ms

[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

[PMEds28]

@akashdubey-ms

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

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

[PMEds28]

@akashdubey-ms

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

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

[ttorble]

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