Microsoft Azure StorSimpleManagementClient

★ Only Publicly Available OpenAPI DocumentStorageBackup Recoveryoauth294 EndpointsREST

For Agents

Manage StorSimple hybrid appliance estates: managers, devices, backup schedules, backups, alerts, certificates, and CHAP settings.

Install Jentic One Beta

Connect the StorSimpleManagementClient to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the StorSimpleManagementClient, 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 StorSimpleManagementClient API.

Configure backup schedule groups and individual backups for a device

Clone a volume from a backup element to recover specific data

GET STARTED

Start building with StorSimpleManagementClient API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for StorSimpleManagementClient, keeping it validated and agent-ready. The StorSimple management API drives the Azure-side configuration of StorSimple hybrid storage, exposing managers, devices, backup schedule groups, backups, CHAP settings, certificates, and access control records. It supports the full lifecycle of a hybrid storage estate — from registering a manager and devices, through scheduling backups and configuring CHAP authentication, to clearing alerts and managing certificates. Use it to automate StorSimple operations from outside the Azure portal.

Use Cases

Patterns agents use StorSimpleManagementClient API for, with concrete tasks.

★ Hybrid Backup Scheduling

StorSimple devices back up volume data to Azure on a schedule defined by backup schedule groups. StorSimpleManagementClient creates and updates these groups, lists historical backups under a device, and supports cloning a backup element to recover a specific dataset. Operators script this so a new tenant onboarding triggers the right backup cadence automatically.

Create a daily backup schedule group 'nightly-2am' on device 'sts-london-01' under manager 'finance-stsmgr' and list the most recent five backups.

iSCSI Access Hardening

StorSimple exposes volumes over iSCSI; locking down which initiators can connect and under what CHAP credentials is operationally essential. The API supports access control records (ACRs) at the manager level and CHAP settings at the device level, including create, update, list, and delete. A security team can audit the full access posture of a StorSimple estate via this API alone.

Add a CHAP user 'app-server-01' with the supplied secret on device 'sts-london-01' and list the access control records on manager 'finance-stsmgr'.

Alert and Certificate Hygiene

StorSimple managers raise alerts for hardware, capacity, and connectivity issues, and rely on certificates for secure device-to-cloud communication. The API lists alerts with filters, clears alerts in bulk via /clearAlerts, and exposes manager certificate operations for rotation. This combination supports a single hygiene job that triages alerts and ensures certificates are current.

List all alerts on manager 'finance-stsmgr' newer than 7 days, then call /clearAlerts to acknowledge alerts older than 30 days.

Agent-Driven StorSimple Operations via Jentic

An AI agent supporting a hybrid-cloud operations team can run StorSimple lifecycle tasks through Jentic without learning the ARM URL hierarchy. The agent searches by intent, loads the operation schema for the required action, and submits it with the correct manager and device identifiers. Jentic isolates the Azure AD credentials.

Use Jentic to load the StorSimpleManagementClient list-alerts operation, then call it for manager 'finance-stsmgr' filtered to severity 'Critical'.

Key Endpoints

94 endpoints — jentic publishes the only available openapi specification for storsimplemanagementclient, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/providers/Microsoft.StorSimple/operations

List operations exposed by the resource provider

GET

/subscriptions/{subscriptionId}/providers/Microsoft.StorSimple/managers

List StorSimple managers in a subscription

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.StorSimple/managers/{managerName}

Create or update a manager

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.StorSimple/managers/{managerName}/devices

List devices under a manager

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.StorSimple/managers/{managerName}/alerts

List alerts under a manager

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.StorSimple/managers/{managerName}/clearAlerts

Clear acknowledged alerts in bulk

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.StorSimple/managers/{managerName}/devices/{deviceName}/backups/{backupName}/elements/{elementName}/clone

Clone a backup element to a new volume

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.StorSimple/managers/{managerName}/accessControlRecords

List access control records

GET

/providers/Microsoft.StorSimple/operations

List operations exposed by the resource provider

GET

/subscriptions/{subscriptionId}/providers/Microsoft.StorSimple/managers

List StorSimple managers in a subscription

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.StorSimple/managers/{managerName}

Create or update a manager

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.StorSimple/managers/{managerName}/devices

List devices under a manager

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.StorSimple/managers/{managerName}/alerts

List alerts under a manager

Why Jentic?

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

Credential isolation

Azure AD OAuth tokens are stored encrypted in the Jentic vault (MAXsystem). Agents calling StorSimpleManagementClient receive scoped, short-lived bearer tokens at execution time — refresh tokens and tenant secrets never enter the agent's context.

Intent-based discovery

Agents search Jentic by intent (e.g., 'configure chap on a storsimple device') and Jentic returns the matching operation with its full input schema, so the agent can call the right endpoint without reading ARM docs.

Time to first call

Direct integration with Azure Resource Manager and the StorSimple object model — manager scopes, schedule groups, async job polling — typically takes 2-3 days. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using StorSimpleManagementClient API through Jentic.

Why is there no official OpenAPI spec for StorSimpleManagementClient?

Microsoft Azure publishes Swagger fragments for the Microsoft.StorSimple resource provider but does not publish a consolidated, validated OpenAPI 3 spec. Jentic generates and maintains this spec so that AI agents and operators can call StorSimpleManagementClient via structured tooling. It is validated against the live Azure Resource Manager API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the StorSimpleManagementClient use?

All endpoints require Azure Active Directory OAuth 2.0, declared as the azure_auth security scheme with the user_impersonation scope against https://login.microsoftonline.com. Through Jentic, Azure tokens are held in the vault and injected at call time so the agent never sees the raw bearer token.

Can I clone a volume from a StorSimple backup?

Yes. POST /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.StorSimple/managers/{managerName}/devices/{deviceName}/backups/{backupName}/elements/{elementName}/clone clones a backup element back into a usable volume. The clone is a long-running operation that returns 202; track it via the manager's job endpoints.

What are the rate limits for the StorSimpleManagementClient?

Calls go through Azure Resource Manager, which throttles writes per subscription (typically 1,200 writes per hour) and reads more generously. Backup, clone, and certificate-rotation calls are long-running — track via job endpoints rather than retrying.

How do I configure CHAP on a StorSimple device through Jentic?

Run pip install jentic, search Jentic for 'configure chap on a storsimple device', load the StorSimpleManagementClient chapSettings create-or-update operation, and execute it with subscriptionId, resourceGroupName, managerName, deviceName, and the CHAP user payload. Jentic handles the Azure AD token exchange.

Does this API manage StorSimple 8000 series appliances?

No. This spec covers the StorSimple 1200 series (Virtual Array) management surface. For the 8000 series physical appliance, use StorSimple8000SeriesManagementClient — the resource model and endpoint shapes differ.