Microsoft Azure StorSimple8000SeriesManagementClient
Browse all Azure APIsAgent-ready OpenAPI document · curated by JenticStorageBackup Recoveryoauth292 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Manage StorSimple 8000 hybrid storage appliances on Azure: devices, volume containers, volumes, backup policies, and alerts.
Use for: I want to provision a new volume on a StorSimple 8000 device, List all StorSimple managers in my subscription, Set up a backup schedule for a volume container, Trigger a manual backup of a StorSimple volume immediately
Not supported: Does not manage StorSimple 1200 Virtual Array appliances, public Azure storage accounts, or run iSCSI traffic - use for StorSimple 8000 series Azure-side management only.
Jentic publishes the only available OpenAPI specification for StorSimple8000SeriesManagementClient, keeping it validated and agent-ready. The StorSimple 8000 Series management API drives Azure-side configuration of StorSimple 8000 hybrid storage appliances, including managers, devices, volume containers, volumes, backup policies, and alerts. It exposes the full lifecycle of an appliance fleet - registration, configuration, backup scheduling, failover, and decommissioning - along with diagnostic operations like alerts and metrics. Use it for organisations still operating StorSimple 8000 series appliances against Azure.
Install Jentic One Beta
Connect the StorSimple8000SeriesManagementClient to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the StorSimple8000SeriesManagementClient, 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%2Fstorsimple8000seriesmanagementclient" | sh2
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%2Fstorsimple8000seriesmanagementclient" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 StorSimple8000SeriesManagementClient API.
Register and configure StorSimple 8000 appliances under a manager resource
Create volume containers and provision iSCSI volumes on a device
Schedule and trigger backups against a backup policy
Clone volumes from a backup or trigger a device failover to another appliance
Configure bandwidth settings and access control records for tenants
List and acknowledge alerts emitted by appliances and managers
Update device firmware and inspect job history for long-running operations
Use Cases
Patterns agents use StorSimple8000SeriesManagementClient API for, with concrete tasks.
★ Hybrid Storage Lifecycle Management
StorSimple 8000 appliances tier hot data on-prem and cold data into Azure. Operators use StorSimple8000SeriesManagementClient to register the appliance under a StorSimple manager, create volume containers backed by an Azure storage account, then carve iSCSI volumes for application servers. The same API handles ongoing changes - resizing volumes, updating bandwidth limits, and rolling new firmware to devices.
Create a 1 TB volume named 'erp-data' inside volume container 'finance-vc' on device 'sts8000-london-01' under manager 'finance-stsmgr'.
Backup and Disaster Recovery
StorSimple 8000 backup is policy-driven: a backup policy attaches to one or more volumes and runs on a schedule, with snapshots stored in Azure. The API exposes create-or-update on backup policies and schedules, manual backup triggers, and clone-from-backup operations for recovery. Failover endpoints relocate workloads to a replacement appliance when hardware fails.
Create a backup policy 'nightly' on manager 'finance-stsmgr' that backs up volume id /subscriptions/.../volumes/erp-data daily at 02:00 UTC.
Fleet-Wide Alert Triage
StorSimple managers raise alerts for capacity thresholds, hardware failures, and connectivity issues. The API lists alerts across a manager and supports clearing acknowledged alerts in bulk. A monitoring job pulls the alert list every few minutes, opens incidents for severity High and above in the operations queue, and clears stale alerts.
List all alerts on manager 'finance-stsmgr' with severity 'Critical', then call the clearAlerts endpoint for any alert older than 30 days.
Agent-Driven Backup Operations via Jentic
An AI operator agent receives an instruction like 'back up the ERP volume now' and needs to translate it to the right StorSimple API call. Through Jentic, the agent searches by intent, loads the manual-backup operation schema, and executes it with the correct device and volume identifiers. Azure AD tokens stay in your Jentic One instance.
Use Jentic to load the StorSimple8000SeriesManagementClient backup-now operation, then trigger a manual backup of volume 'erp-data' on device 'sts8000-london-01'.
Key Endpoints
92 endpoints — jentic publishes the only available openapi specification for storsimple8000seriesmanagementclient, 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
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.StorSimple/managers/{managerName}/bandwidthSettings
List bandwidth settings
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
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.StorSimple/managers/{managerName}/clearAlerts
Clear acknowledged alerts in bulk
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.StorSimple/managers/{managerName}/bandwidthSettings
List bandwidth settings
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.StorSimple/managers/{managerName}/accessControlRecords
List access control records
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Microsoft.StorSimple 8000 series surface by hand means registering an Azure AD app, running the OAuth2 token exchange, learning the manager-device-volume-container hierarchy, and tracking backup, failover, and clone operations through the manager's jobs endpoint. Through Jentic you install once, import StorSimple 8000 Series 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, volumes, and alerts. You choose the operations it may call, so ones like clearAlerts or a device failover are not included unless you add them.
Credential isolation
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.
Intent-based discovery
Agents search Jentic by intent such as 'list StorSimple alerts on a manager' or 'create a StorSimple volume', 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
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using StorSimple8000SeriesManagementClient API through Jentic.
Why is there no official OpenAPI spec for StorSimple8000SeriesManagementClient?
Microsoft Azure publishes Swagger fragments for the Microsoft.StorSimple resource provider but does not publish a consolidated, validated OpenAPI 3 spec for the 8000 series management surface. Jentic generates and maintains this spec so that AI agents and operators can call StorSimple8000SeriesManagementClient 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 StorSimple8000SeriesManagementClient 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 trigger a manual StorSimple backup with this API?
Yes. The API exposes a backup-now operation under the device and volume-container scope (POST under /managers/{managerName}/devices/{deviceName}/.../backup) that triggers an immediate backup using the supplied policy. Long-running operations return 202; poll the returned job endpoint for completion.
What are the rate limits for the StorSimple8000SeriesManagementClient?
Calls go through Azure Resource Manager, which throttles writes per subscription (typically 1,200 writes per hour) and reads more generously. Backup, failover, and clone are long-running - track them through the manager's jobs endpoint rather than retrying.
How do I list StorSimple alerts through Jentic?
Run pip install jentic, search Jentic for 'list storsimple alerts', load the StorSimple8000SeriesManagementClient alerts list operation, and execute it with subscriptionId, resourceGroupName, and managerName. Jentic returns the alert payload directly without you handling the Azure AD token.
Does this API support StorSimple Virtual Array appliances?
No. This spec covers only the 8000 series physical appliances. StorSimple Virtual Array (1200 series) management lives under a different resource provider; use StorSimpleManagementClient for that surface.
Can I limit what my agent is allowed to do with the Azure StorSimple 8000 Series Management Client?
Yes. Because you run Jentic One yourself, your own rules decide which StorSimple operations and credentials the agent may use. This API carries the subscription, resource group, and manager in the URL path, so a rule can pin the agent to a single manager and only its devices, volumes, and alerts. You also choose the exact operations it may call, so destructive ones like clearAlerts or a device failover stay off limits unless you add them.
GET STARTED