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 / Cloud Infrastructure / Azure / MaintenanceManagementClient
MaintenanceManagementClient logo

Microsoft Azure MaintenanceManagementClient

Browse all Azure APIs
50
AI ReadinessFoundational (D+)50/100
See full scorecard
Agent-ready OpenAPI document · curated by JenticCloud InfrastructureComputeoauth218 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Define Azure maintenance windows, assign them to resources, and apply or track platform updates through Azure Resource Manager. Use for maintenance configuration and update tracking, not for OS patching or guest software updates.

Use for: Create a maintenance configuration with a weekly Sunday window, Assign the 'weekly-sunday' configuration to a list of production VMs, Apply pending platform updates to the VM 'app-vm-01' immediately, List all available platform updates for resource 'app-vm-01'

Not supported: Does not patch guest operating systems, install application updates, or schedule VM reboots outside Azure's platform fabric - use only for Microsoft.Maintenance configurations and platform-update orchestration.

Jentic publishes the only available OpenAPI specification for MaintenanceManagementClient, keeping it validated and agent-ready. MaintenanceManagementClient is the Azure Resource Manager surface for the Microsoft.Maintenance provider - Azure Maintenance Configurations. It defines maintenance windows, assigns those configurations to virtual machines and other resources, and tracks the status of pending or applied platform updates. It does not patch operating systems or install application updates.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the MaintenanceManagementClient to your agent

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

Create and manage maintenance configuration resources defining recurring windows

Assign maintenance configurations to virtual machines and other supported resources via ConfigurationAssignments

Apply pending platform updates to a resource on demand using ApplyUpdates

Track the status of platform updates per resource through the Updates and ApplyUpdates resources

List available platform updates for a target resource before triggering apply

Patch a maintenance configuration to change cadence, scope, or window timing

Use Cases

Patterns agents use MaintenanceManagementClient API for, with concrete tasks.

★ Scheduled Platform Maintenance Windows

Operations teams running production virtual machines need predictable platform-update windows so unplanned reboots do not disrupt customer traffic. MaintenanceManagementClient creates a MaintenanceConfiguration resource with a recurring schedule (for example, every Sunday 02:00-06:00 UTC), and ConfigurationAssignments bind that window to specific VMs. Azure platform updates are then deferred to the configured window rather than the default reboot policy.

PUT a MaintenanceConfiguration named 'sunday-02-utc' with maintenanceScope 'Host' and a weekly Sunday 02:00 UTC window, then create ConfigurationAssignments binding it to each VM in the 'app-prod' availability set.

On-Demand Update Apply

When a critical platform update is announced, operators apply pending updates to specific VMs without waiting for the next scheduled window. ApplyUpdates POST against /providers/Microsoft.Maintenance/applyUpdates/default triggers the update immediately, and the response includes a status the agent can poll until the update completes. The Updates list endpoint surfaces what is pending before the trigger.

List Updates for VM 'app-vm-01', then if any update has impactType=Restart and is approved, call applyUpdates/default and poll the resulting ApplyUpdates resource until status=Completed.

Subscription-Wide Maintenance Audit

Compliance teams confirm every VM in scope has a maintenance configuration assigned. MaintenanceConfigurations_List returns every defined window in the subscription, and ConfigurationAssignments_List per resource returns the bindings. An agent can join these and flag VMs without an assignment for follow-up.

List MaintenanceConfigurations in the subscription, list ConfigurationAssignments for each VM in the 'prod' resource group, and produce a CSV of VM names without an assigned configuration.

AI Agent Patch Orchestration

SRE agents handling patch coordination use Jentic to discover the right Microsoft.Maintenance operation. Searching for 'apply azure platform updates' returns the schema; the agent loads it and executes against management.azure.com using a token retrieved from your Jentic One instance, so no ARM SDK install is needed.

Use Jentic to search 'apply azure platform updates to a virtual machine', load the ApplyUpdates schema, and POST against the target VM's applyUpdates/default sub-resource.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

PUT

/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.Maintenance/maintenanceConfigurations/{resourceName}

Create or update a maintenance configuration

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Maintenance/maintenanceConfigurations

List maintenance configurations in a subscription

DELETE

/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.Maintenance/maintenanceConfigurations/{resourceName}

Delete a maintenance configuration

PUT

/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/{providerName}/{resourceParentType}/{resourceParentName}/{resourceType}/{resourceName}/providers/Microsoft.Maintenance/applyUpdates/default

Apply pending platform updates to a resource

GET

/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/{providerName}/{resourceParentType}/{resourceParentName}/{resourceType}/{resourceName}/providers/Microsoft.Maintenance/applyUpdates/{applyUpdateName}

Track an apply-updates operation

PUT

/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.Maintenance/maintenanceConfigurations/{resourceName}

Create or update a maintenance configuration

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Maintenance/maintenanceConfigurations

List maintenance configurations in a subscription

DELETE

/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.Maintenance/maintenanceConfigurations/{resourceName}

Delete a maintenance configuration

PUT

/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/{providerName}/{resourceParentType}/{resourceParentName}/{resourceType}/{resourceName}/providers/Microsoft.Maintenance/applyUpdates/default

Apply pending platform updates to a resource

GET

/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/{providerName}/{resourceParentType}/{resourceParentName}/{resourceType}/{resourceName}/providers/Microsoft.Maintenance/applyUpdates/{applyUpdateName}

Track an apply-updates operation

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

MaintenanceManagementClient

- Foundational (D+)
50/100
66
Foundational Compliance
57
Developer Experience & Jentic Compatibility
30
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
66

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: BSignals: 4
90%

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

75%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

57

Developer Experience & Jentic Compatibility

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

Grade: CSignals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

33%

Response Coverage

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

93%

Tooling Readiness

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

30

AI-Readiness & Agent Experience

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

Grade: FSignals: 4
64%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

0%

OperationId Quality

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

58%

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 the Azure Maintenance management API by hand means registering an Azure AD app, negotiating OAuth 2.0 tokens for management.azure.com, and threading subscription and resource-group scope through every maintenance-configuration call. Through Jentic you install once, import MaintenanceManagementClient from the API Directory, store the Azure AD credential once, and your agent calls it.

Permission scoping

This API puts the maintenance configuration in the URL path (/providers/Microsoft.Maintenance/maintenanceConfigurations/{resourceName}), so a rule can pin your agent to reading configurations and their apply-update records: it can list configurations and read apply-update state. You choose the operations it may call, so creating, deleting, or applying an update is not included unless you add it.

Credential isolation

Your Azure AD credential for the Maintenance control plane 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 Azure maintenance configurations' or 'read a maintenance apply-update record', and Jentic returns the matching Maintenance operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

MonitorManagementClient

→

Configure alerts on platform-update events emitted by maintenance operations.

Use when wiring up alerting on update completion or failure events.

Complementary

PolicyClient

→

Enforce that all production VMs must have a maintenance configuration assigned.

Use when enforcing maintenance assignment as a compliance policy.

Complementary

AdvisorManagementClient

→

Surface Advisor recommendations including missing maintenance configurations.

Use to discover VMs that should have a maintenance configuration but do not.

FAQs

Specific to using MaintenanceManagementClient API through Jentic.

Why is there no official OpenAPI spec for MaintenanceManagementClient?

Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call MaintenanceManagementClient 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 MaintenanceManagementClient use?

AAD OAuth 2.0 bearer tokens scoped to https://management.azure.com/. With Jentic, AAD client credentials are stored encrypted in the vault and a short-lived bearer token is injected into the Authorization header at call time.

Does this API patch the operating system inside a VM?

No. This API schedules and applies Azure platform updates (host fabric, image, and extension level). For guest OS patching use Azure Update Management (Microsoft.OperationalInsights/Automation) or VM extensions; this client controls when the platform is allowed to disrupt the resource.

What are the rate limits for the MaintenanceManagementClient?

Standard Azure Resource Manager throttling - roughly 12,000 reads and 1,200 writes per hour per subscription per region. ApplyUpdates calls are asynchronous and the resulting ApplyUpdates resource exposes its progress.

How do I assign a maintenance window to a VM through Jentic?

Run pip install jentic, then search Jentic for 'assign azure maintenance configuration to a vm'. Jentic returns the ConfigurationAssignments_CreateOrUpdate operation; load it, supply the VM resource path and the maintenance configuration ID, and PUT the assignment.

What scope values does a maintenance configuration accept?

Common values include Host (Azure host fabric updates), OSImage (image-level updates for VMs in a scale set), and Extension (VM extension updates). The exact set is enumerated in the maintenanceScope property of the MaintenanceConfiguration body schema.

Can I limit what my agent is allowed to do with the Azure Maintenance API?

Yes. Because you run Jentic One yourself, your own rules decide which Maintenance operations and which Azure AD credential the agent may use. Since the maintenance configuration sits in the URL path, you can pin the agent to read-only work, such as listing maintenance configurations and reading apply-update records, while withholding create, delete, and apply-update calls. Those write operations run only if you explicitly add them to the agent's allowed set.

GET STARTED

Start building with MaintenanceManagementClient API

Explore with Jentic One
View OpenAPI Document