canonical: https://jentic.com/apis/azure.com/storsimplemanagementclient

# Microsoft Azure StorSimpleManagementClient

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.

## For AI agents

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

## Scope

Does not manage StorSimple 8000 series physical appliances, public Azure storage accounts, or run iSCSI traffic - use for StorSimple 1200 Virtual Array Azure-side management only.

## Capabilities

- Register and update StorSimple managers and their attached devices
- Configure backup schedule groups and individual backups for a device
- Clone a volume from a backup element to recover specific data
- Manage CHAP iSCSI authentication settings on a device
- List and clear alerts emitted across the StorSimple manager
- Upload and rotate manager certificates used for device communication
- Configure access control records that gate iSCSI initiator access

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

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

## Key endpoints

| 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 |

## Key resources

- **Managers** — Top-level StorSimple manager grouping devices and global resources
- **Devices** — Registered StorSimple appliances under a manager
- **Backup Schedule Groups and Backups** — Backup schedules and historical backups per device, with clone operations
- **Alerts** — List and clear alerts across the manager
- **Certificates** — Manager-level certificates for secure device communication
- **CHAP Settings** — iSCSI CHAP authentication configuration on a device
- **Access Control Records** — Tenant-level iSCSI initiator access controls

## Why Jentic

- **Setup:** Wiring the Microsoft.StorSimple 1200 series surface by hand means registering an Azure AD app, running the OAuth2 token exchange, learning the manager-and-device object model, and tracking backup, clone, and certificate-rotation calls through the manager's job endpoints. Through Jentic you install once, import StorSimple Management from the API Directory, store the Azure AD service principal credential once, and your agent calls it.
- **Permission scoping:** This API puts the subscription, resource group, and manager in the URL path (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.StorSimple/managers/{managerName}/...), so a rule can pin your agent to one manager and its devices, backups, and access control records. You choose the operations it may call, so ones like clearAlerts or cloning a backup element are not included unless you add them.
- **Credential handling:** Your Azure AD service principal credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context, and neither do the CHAP secrets you set on a device.
- **Discovery method:** Agents search Jentic by intent such as 'configure CHAP on a StorSimple device' or 'list StorSimple alerts on a manager', and Jentic returns the matching Microsoft.StorSimple operation with its input schema so the agent calls the right endpoint without reading the ARM reference.

## Related APIs

- **StorSimple8000SeriesManagementClient** — Management API for the 8000 series physical appliances
- **StorageImportExport** — Bulk physical-disk transfer into Azure Storage
- **StorageManagementClient** — Azure Stack admin storage acquisitions endpoint

## FAQ

### 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 with Jentic One, the self-hosted execution layer.

### 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.

### Can I limit what my agent is allowed to do with the Microsoft Azure StorSimple Management API?

Yes. Because you run Jentic One yourself, your own rules decide which StorSimple operations and which Azure AD service principal credential the agent may use. Since this API carries the subscription, resource group, and manager in the URL path, you can pin the agent to a single manager and only its devices, backups, and access control records. You also choose the exact operations it may call, so sensitive ones like clearAlerts or cloning a backup element are excluded unless you explicitly add them.