Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Storage / Azure / Microsoft NetApp
Microsoft NetApp logo

Microsoft Azure Microsoft NetApp

Browse all Azure APIs
55
AI ReadinessFoundational (C)55/100
See full scorecard
Agent-ready OpenAPI document · curated by JenticStorageObject Storageoauth224 EndpointsREST

Know of an official OpenAPI document? Contribute it →

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.

Jentic publishes the only available OpenAPI specification for Microsoft NetApp, keeping it validated and agent-ready. The Azure NetApp Files management API provisions and operates the high-performance file storage tier built on NetApp ONTAP, organised as accounts containing capacity pools, capacity pools containing volumes, and volumes optionally backed by snapshots and mount targets. Use it to create accounts, allocate capacity pools, expose NFS or SMB volumes, snapshot data, and check name and file path availability before provisioning. Authentication is via Azure Active Directory OAuth 2.0 on Azure Resource Manager.

Jentic One on GithubView OpenAPI Document

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.

1

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Fazure-microsoft-netapp" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Fazure-microsoft-netapp" | 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

Take, list, and restore snapshots of NetApp volumes for point-in-time recovery

Discover the mount targets needed to mount a NetApp volume from a workload

Check whether a candidate file path is available within a capacity pool before creation

Validate a NetApp resource name in a region before provisioning

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

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

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

M

Microsoft NetApp

- Foundational (C)
55/100
49
Foundational Compliance
66
Developer Experience & Jentic Compatibility
42
AI-Readiness & Agent Experience
94
Agent Usability
35
Security
100
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
49

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: D+Signals: 4
83%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

0%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

14%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

66

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: BSignals: 4
12%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

42

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D-Signals: 4
92%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

8%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

67%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

35

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1
35%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1
100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Microsoft NetApp by hand means implementing Azure AD OAuth 2.0, minting an ARM-scoped bearer token for management.azure.com, walking the three-level account, pool, and volume hierarchy, polling asynchronous operation URLs, and plumbing the delegated subnet yourself. Through Jentic you install once, import Microsoft NetApp from the API Directory, store the Azure AD credential once, and your agent calls it.

Permission scoping

The API puts the subscription, resource group, account, pool, and volume names in the URL path, so a rule can pin your agent to one NetApp account: it can create pools, volumes, and snapshots under that account and nothing else. You choose the operations it may call, so destructive ones like deleting a volume or a snapshot are not included unless you add them.

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.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Storage Management Client

→

Provision general-purpose Azure Storage accounts (blob, file, queue) instead of NetApp's high-performance tier.

Pick Storage Management for blob and standard file shares; pick NetApp for high-throughput NFS or SMB workloads.

Complementary

Compute Management Client

→

Provision the Azure VMs that mount NetApp volumes.

Use Compute Management to create VMs in the same VNet as the NetApp delegated subnet.

Complementary

Network Management Client

→

Configure the delegated subnet that NetApp volumes attach to.

Use Network Management first to create the delegated subnet for Microsoft.Netapp/volumes before provisioning volumes.

Complementary

Recovery Services Backup Client

→

Add Azure Backup coverage on top of NetApp's snapshot-based recovery.

Use Recovery Services Backup when policy demands an external backup vault on top of in-place NetApp snapshots.

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.

GET STARTED

Start building with Microsoft NetApp API

Explore with Jentic One
View OpenAPI Document