Microsoft Azure Microsoft NetApp

Name: Microsoft NetApp API
Brand: Microsoft NetApp
Availability: InStock

★ Only Publicly Available OpenAPI DocumentStorageObject Storageoauth224 EndpointsREST

Install Jentic One Beta

Connect the Microsoft NetApp to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Microsoft NetApp, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Microsoft NetApp API.

Create or update an Azure NetApp account that scopes capacity pools and volumes

Allocate a capacity pool with a chosen service level and provisioned size in TiB

Expose NFS or SMB volumes from a capacity pool with quota and protocol settings

GET STARTED

Start building with Microsoft NetApp API

Explore with Jentic

View OpenAPI Document

For Agents

Provision and operate Azure NetApp Files: create NetApp accounts, allocate capacity pools, expose NFS or SMB volumes, and snapshot data. Useful for high-performance file storage automation.

Use for: I need to provision a NetApp Files capacity pool for an HPC workload, Create an NFS volume on Azure NetApp Files, Take a snapshot of a NetApp volume before a deployment, List all volumes under a NetApp capacity pool

Not supported: Does not handle blob storage, queue storage, or backup vault management - use for control-plane Azure NetApp Files account, pool, volume, and snapshot operations only.

Use Cases

Patterns agents use Microsoft NetApp API for, with concrete tasks.

★ Provision file storage for an HPC workload

HPC and SAP HANA teams use the API to provision Azure NetApp Files at scale: a NetApp account anchored in a region, one or more capacity pools at a chosen service level (Standard, Premium, or Ultra), and NFS volumes sized to the workload. Each PUT call is asynchronous, so the agent polls the operation URL until provisioning succeeds before mounting the volume from compute.

PUT /.../netAppAccounts/{accountName}, then PUT capacityPools/{poolName} with serviceLevel and size, then PUT volumes/{volumeName} with usageThreshold and protocol set to NFSv3 or NFSv4.1.

Snapshot and restore production data

Operations teams take frequent snapshots of NetApp volumes before deployments or risky migrations. Snapshots are space-efficient point-in-time copies that can be listed, restored, or deleted through dedicated endpoints, providing a fast roll-back path that does not require restoring from a full backup.

PUT /.../volumes/{volumeName}/snapshots/{snapshotName} to capture the snapshot, then if needed call the snapshot revert API on the volume to roll back.

Right-size capacity pools as workloads grow

As workloads grow, teams expand the capacity pool that backs a set of volumes rather than recreating the storage tier. The PATCH endpoint on a capacity pool updates its size in TiB while leaving the volumes inside untouched. Combine with GET on the pool to read the current size, and with the volumes list to confirm utilisation before resizing.

GET the capacity pool to read current size, then PATCH /.../capacityPools/{poolName} with the new size in bytes (TiB multiplied by 2^40).

Agent-driven NetApp lifecycle

Through Jentic, an AI agent can read a workload spec and provision a complete NetApp environment: account, capacity pool, NFS volume, and a daily snapshot policy. The agent searches Jentic for 'create azure netapp volume', loads the operations in turn, and chains the calls. Jentic injects the Azure AD bearer token at execution time so the agent never sees raw credentials.

Use Jentic search 'create azure netapp volume', execute Accounts_CreateOrUpdate then Pools_CreateOrUpdate then Volumes_CreateOrUpdate, polling the async operation URL between steps.

Key Endpoints

24 endpoints — jentic publishes the only available openapi specification for microsoft netapp, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.NetApp/netAppAccounts/{accountName}

Create or update a NetApp account

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.NetApp/netAppAccounts/{accountName}/capacityPools/{poolName}

Create or update a capacity pool

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.NetApp/netAppAccounts/{accountName}/capacityPools/{poolName}/volumes/{volumeName}

Create or update a volume

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.NetApp/netAppAccounts/{accountName}/capacityPools/{poolName}/volumes/{volumeName}/snapshots/{snapshotName}

Create a volume snapshot

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.NetApp/netAppAccounts/{accountName}/capacityPools/{poolName}/volumes/{volumeName}/mountTargets

List volume mount targets

POST

/subscriptions/{subscriptionId}/providers/Microsoft.NetApp/locations/{location}/checkFilePathAvailability

Check file path availability

POST

/subscriptions/{subscriptionId}/providers/Microsoft.NetApp/locations/{location}/checkNameAvailability

Check resource name availability

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.NetApp/netAppAccounts/{accountName}

Create or update a NetApp account

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.NetApp/netAppAccounts/{accountName}/capacityPools/{poolName}

Create or update a capacity pool

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.NetApp/netAppAccounts/{accountName}/capacityPools/{poolName}/volumes/{volumeName}

Create or update a volume

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.NetApp/netAppAccounts/{accountName}/capacityPools/{poolName}/volumes/{volumeName}/snapshots/{snapshotName}

Create a volume snapshot

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Azure AD credential is stored once, encrypted, by your own Jentic One instance and exchanged for a short-lived ARM-scoped bearer token at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create an Azure NetApp Files volume' or 'snapshot an Azure NetApp volume', and Jentic returns the matching operation with its input schema, including the service level and protocol enums, so the agent executes with the right fields.

Time to first call

FAQs

Specific to using Microsoft NetApp API through Jentic.

Why is there no official OpenAPI spec for Microsoft NetApp?

Microsoft Azure does not publish a standalone OpenAPI specification for the NetApp Files resource provider. Jentic generates and maintains this spec so that AI agents and developers can call Microsoft NetApp via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the NetApp Files API use?

The API uses Azure Active Directory OAuth 2.0 via the azure_auth scheme on https://management.azure.com/. Through Jentic, your Azure AD application credentials are stored encrypted in your Jentic One instance and exchanged for a short-lived bearer token at execution time.

Can I create an NFS volume with this API?

Yes. After provisioning a NetApp account and capacity pool, call PUT /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.NetApp/netAppAccounts/{accountName}/capacityPools/{poolName}/volumes/{volumeName} with protocolTypes set to NFSv3 or NFSv4.1 and usageThreshold sized for your workload.

What are the rate limits for the NetApp Files API?

The endpoints inherit standard Azure Resource Manager throttle quotas, surfaced through x-ms-ratelimit-remaining-* response headers. Long-running operations such as Volumes_CreateOrUpdate return 202 with an Azure-AsyncOperation URL the agent should poll rather than retry.

How do I take a snapshot through Jentic?

Search Jentic for 'create azure netapp snapshot', load Snapshots_Create, supply the account, pool, volume, and snapshot name, and execute. The response includes the snapshot's resource ID, which the agent can store for later restore or delete operations.

What service levels does NetApp Files support?

Capacity pools are created with one of three service levels: Standard, Premium, or Ultra. The level is set on the pool's serviceLevel property and determines the throughput per TiB the volumes inside the pool can sustain. Volumes inherit the service level from their parent pool.

Can I check name availability before creating resources?

Yes. POST /subscriptions/{subscriptionId}/providers/Microsoft.NetApp/locations/{location}/checkNameAvailability validates resource names, and POST /subscriptions/{subscriptionId}/providers/Microsoft.NetApp/locations/{location}/checkFilePathAvailability validates volume file paths against the chosen subnet to avoid conflicts.

Can I limit what my agent is allowed to do with the Microsoft Azure NetApp Files API?

Yes. Because you self-host Jentic One, your own rules decide which operations and credentials the agent may use, and those rules pin it to a single NetApp account so it can create pools, volumes, and snapshots under that account and nothing else. You pick the exact operations it can call, so destructive ones like deleting a volume or a snapshot are excluded unless you add them. Your Azure AD credential stays encrypted in your own instance and is exchanged for a short-lived ARM-scoped bearer token at execution time, so the agent never sees the raw secret.