Update write-back considerations in cache requirements

[Dean Miller (deanpmiller)]

Clarified requirements for enabling write-back on external origin volume, including ONTAP version and system specifications.

[prmerger-automator]

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

[prmerger-automator]

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

[learn-build-service-prod]

Learn Build status updates of commit 6e29b0a:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/azure-netapp-files/cache-requirements.md	✅Succeeded

For more details, please refer to the build report.

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Updates the cache requirements documentation by clarifying prerequisites for enabling write-back on an external origin volume, specifically by removing an ONTAP version requirement.

Changes:

• Removed the stated minimum ONTAP version requirement for write-back on an external origin volume.

Suppressed comments (1)

articles/azure-netapp-files/cache-requirements.md:1

• Removing the ONTAP minimum version requirement without adding an alternative compatibility statement leaves the prerequisites incomplete/ambiguous for readers (it’s unclear which ONTAP versions support write-back, or whether support is conditional). Consider adding back a clear compatibility requirement (minimum supported ONTAP version/patch) or explicitly stating where the authoritative support matrix lives (for example, a link to validated ONTAP versions for write-back) so customers can reliably determine eligibility.

---

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Diana Richards (v-dirichards)]

Manish Chabbria (@netapp-manishc)

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