Skip to content

Conversation

@p15nishatr
Copy link
Contributor

Add AZNFS 3.0 public preview note to BlobNFS documentation

Added a note about AZNFS 3.0 Public Preview and its features.
Add AZNFS 3.0 Public Preview note to documentation
@prmerger-automator
Copy link
Contributor

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

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit f039b2f:

✅ Validation status: passed

File Status Preview URL Details
articles/storage/blobs/network-file-system-protocol-support-how-to.md ✅Succeeded

For more details, please refer to the build report.

@v-dirichards v-dirichards requested a review from Copilot November 13, 2025 21:37
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR adds a public preview announcement for AZNFS 3.0 to the BlobNFS documentation, informing users about the new release and its improvements.

  • Adds a NOTE block announcing AZNFS 3.0 public preview with key feature highlights

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@v-dirichards
Copy link
Contributor

@normesta

Can you review the proposed changes?

Due to the upcoming Ignite conference, all merging and publishing is on hold until the morning of Tuesday, November 19.

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

@prmerger-automator prmerger-automator bot added the aq-pr-triaged tracking label for the PR review team label Nov 13, 2025
@normesta
Copy link
Contributor

Looks ok. @p15nishatr - if you use the internal repo (azure-docs-pr), you can sign off on these without blocking on the content team. Either way is fine, but it might be easier for you in future. BTW - not necessarily a strict guideline, but typically, we avoid things like exclamation marks. They can sound like shouting and/or too marketing and "salesy" in tone. Cheers!

#sign-off

Updated note to a tip and improved wording for clarity.
@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit b29587d:

✅ Validation status: passed

File Status Preview URL Details
articles/storage/blobs/network-file-system-protocol-support-how-to.md ✅Succeeded

For more details, please refer to the build report.

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit 626f258:

✅ Validation status: passed

File Status Preview URL Details
articles/storage/blobs/network-file-system-protocol-support-how-to.md ✅Succeeded

For more details, please refer to the build report.

@ktoliver
Copy link
Contributor

#sign-off

@prmerger-automator
Copy link
Contributor

Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @normesta

@ktoliver
Copy link
Contributor

Due to the upcoming conference, all merging and publishing is on hold until the morning of November 18, 2025.

This PR is ready for merge on November 18, 2025.

#label: "event-triaged-to-10AM"
#label: "missed-content-complete"
#label: "ready-to-merge"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants