Review the whole NetApp network sibling set before a feature upgrade

Source facts

Changing an existing Azure NetApp Files volume from Basic to Standard network features affects every volume in its network sibling set. Those siblings share the network interface used for client access. During the change, new volumes and application volume groups cannot be created in that set. Microsoft warns that blocking DNS or domain-controller connectivity through routing or security rules can disrupt access. Microsoft Learn.

Applicability

Use this review for an existing-volume upgrade, not a new Basic deployment. Confirm feature registration and the current supported topology, and identify all volumes shown in the sibling-set review.

DSE recommendation

Make the sibling set, rather than the selected volume alone, the change scope. Notify every affected workload owner and coordinate conflicting volume-creation plans. Review routing and security rules against the directory and DNS paths before approval. Define an alternative access or recovery plan without assuming that reverting the feature is immediately available.

Verification

Compare the complete sibling list before and after the operation, then inspect each volume’s network-feature state. Test representative client access and the required directory-dependent operations across affected workloads. Record any unreachable dependency or unexpected sibling before expanding the change. A successful update of the originally selected volume should not close the review for the rest of the shared set.

Official references

Microsoft Learn: Configure network features for an Azure NetApp Files volume.