Create a delegated subnet for Azure NetApp Files
PDF of this doc site
- AI Converged Infrastructures
Data Pipelines, Data Lakes and Management
- NetApp AI Control Plane
- Distributed training in Azure - Click-Through Rate Prediction
- Conversational AI using NVIDIA
- Anthos with NetApp
- DevOps with NetApp Astra
Red Hat OpenShift with NetApp
- NetApp Storage Integrations Overview
Solution Validation and Use Cases
- Red Hat OpenShift Virtualization with NetApp ONTAP
- VMware Tanzu with NetApp
- Data Migration and Data Protection
- Oracle Database
- SnapCenter for Databases
- Modern Data Analytics
NetApp Hybrid Multicloud with VMware
- VMware for Public Cloud
- NetApp for GCP / GCVE
- NetApp Hybrid Multicloud with Red Hat OpenShift
- VMware vSphere Automation
- Virtual Desktops
- Artificial Intelligence
To create a delegated subnet for Azure NetApp Files, complete the following steps:
Navigate to Virtual Networks within the Azure portal. Find your newly created virtual network. It should have a prefix such as
Click the name of the VNet.
Click Subnets and click +Subnet from the top toolbar.
Provide the subnet with a name such as
ANF.snand, under the Subnet Delegation heading, select
Microsoft.Netapp/volumes. Do not change anything else. Click OK.
Azure NetApp Files volumes are allocated to the application cluster and are consumed as persistent volume claims (PVCs) in Kubernetes. In turn, this process provides you the flexibility to map them to different services, such as Jupyter notebooks, serverless functions, and so on.
Users of services can consume storage from the platform in many ways. As this technical report discusses NFSs, the main benefits of Azure NetApp Files are:
Providing users with the ability to use Snapshot copies.
Enabling users to store large quantities of data on Azure NetApp Files volumes.
Using the performance benefits of Azure NetApp Files volumes when running their models on large sets of files.