Customer Lockbox

Name: Customer Lockbox API
Brand: Customer Lockbox
Availability: InStock

★ Only Publicly Available OpenAPI DocumentSecurityComplianceoauth24 EndpointsREST

For Agents

Review and approve or deny Microsoft engineer data-access requests on Azure subscriptions through 4 operations on the Customer Lockbox resource provider, supporting compliance and audit-trail automation.

Connect the Customer Lockbox to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Customer Lockbox, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

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

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 Customer Lockbox API.

List all pending and historical Customer Lockbox requests on a subscription

Retrieve full details of a specific Lockbox request including service, support ticket, and justification

Approve or deny a specific Lockbox request with a status update call

Enumerate available Microsoft.CustomerLockbox operations for permission and audit review

GET STARTED

Start building with Customer Lockbox API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Customer Lockbox, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Customer Lockbox, keeping it validated and agent-ready. The Azure Customer Lockbox API exposes 4 operations across 4 paths to review and respond to Microsoft engineer access requests against your subscription's data. When a Microsoft support engineer requires data-plane access during a support case, a Lockbox request is generated and must be approved or denied by an authorised customer. This API lets agents and automation systems list pending requests, fetch a specific request, and update its approval status without manual portal use.

Use Cases

Patterns agents use Customer Lockbox API for, with concrete tasks.

★ Automated Compliance Review of Microsoft Support Access

Surface every pending Customer Lockbox request to a security operations queue so designated approvers respond within the SLA window. Listing the requests on a subscription returns the requested service, support case number, justification, and expiry, which the operator combines with the open ticket record to make an informed decision. Approval or denial is a single UpdateApproval call. This replaces manual portal monitoring for regulated workloads.

List all Customer Lockbox requests on /subscriptions/{id}, filter for requests with status 'Pending', and post a notification to the security team channel for each one

Audit Trail of Microsoft Engineer Access

Build an audit log of every Microsoft engineer access request and its outcome by polling the requests list endpoint and storing the results. This gives compliance teams a defensible record of who reviewed and approved each request, with the underlying support case and justification, even if the in-portal history is not retained long-term.

Pull all Lockbox requests with status 'Approved' or 'Denied' from the last 90 days and write each record to the compliance log store

Time-Boxed Automatic Denial

Implement a policy where any Lockbox request that has not been reviewed within a defined window is automatically denied. The agent polls the requests list, identifies any pending entry older than the threshold, and calls UpdateApproval with status 'Denied'. This prevents accidental approvals from idle queues while keeping a clear audit trail.

Find all Lockbox requests on /subscriptions/{id} with status 'Pending' and createdDateTime older than 4 hours, then call UpdateApproval with status 'Denied' for each

AI Agent Compliance Assistant

An AI agent acting on behalf of a compliance officer can fetch Lockbox requests through Jentic by intent ('list customer lockbox requests'), summarise them in natural language, and execute UpdateApproval based on a verified human decision. Jentic handles the AAD bearer token so the agent never holds an Azure secret directly.

Search Jentic for 'list customer lockbox requests', execute Requests_List on /subscriptions/{id}, summarise each pending request, and on confirmation call Requests_UpdateStatus with the decided approval status

Key Endpoints

4 endpoints — jentic publishes the only available openapi specification for customer lockbox, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/subscriptions/{subscriptionId}/providers/Microsoft.CustomerLockbox/requests

List Customer Lockbox requests on a subscription

GET

/subscriptions/{subscriptionId}/providers/Microsoft.CustomerLockbox/requests/{requestId}

Get a specific Lockbox request

POST

/subscriptions/{subscriptionId}/providers/Microsoft.CustomerLockbox/requests/{requestId}/UpdateApproval

Approve or deny a Lockbox request

GET

/providers/Microsoft.CustomerLockbox/operations

List available Microsoft.CustomerLockbox operations

GET

/subscriptions/{subscriptionId}/providers/Microsoft.CustomerLockbox/requests

List Customer Lockbox requests on a subscription

GET

/subscriptions/{subscriptionId}/providers/Microsoft.CustomerLockbox/requests/{requestId}

Get a specific Lockbox request

POST

/subscriptions/{subscriptionId}/providers/Microsoft.CustomerLockbox/requests/{requestId}/UpdateApproval

Approve or deny a Lockbox request

GET

/providers/Microsoft.CustomerLockbox/operations

List available Microsoft.CustomerLockbox operations

Why though Jentic?

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

Credential isolation

Azure service principal credentials are encrypted in the Jentic vault. Agents only see scoped ARM bearer tokens at execution time; the client secret never enters agent context. The Customer Lockbox Approver role is enforced on the underlying identity.

Intent-based discovery

Agents search by intent ('approve customer lockbox request' or 'list lockbox requests') and Jentic returns the four Customer Lockbox operations directly, removing the need to learn the URL shape for the resource provider.

Time to first call

Direct ARM integration: half a day for AAD app registration, MSAL token handling, and request-handling code. Through Jentic: under 15 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Authorization Management

Manage RBAC role assignments that determine who can approve Lockbox requests.

Use when an agent needs to grant or revoke the Customer Lockbox Approver role before processing requests.

Complementary

Policy Client

Define Azure Policy rules that complement Lockbox approvals for full data-access governance.

Use alongside Lockbox to express tenant-wide data-access policies that apply to all subscriptions.

Alternative

Key Vault Management

Control secret-level access via Key Vault access policies rather than Lockbox subscription-wide approvals.

Choose Key Vault for fine-grained secret access control; choose Lockbox for subscription-level Microsoft engineer access review.

FAQs

Specific to using Customer Lockbox API through Jentic.

Why is there no official OpenAPI spec for Customer Lockbox?

Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Customer Lockbox via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Customer Lockbox API use?

It uses Azure Active Directory OAuth 2.0 against https://management.azure.com/ with the user_impersonation scope. The caller must hold an RBAC role with Microsoft.CustomerLockbox/requests/* permissions on the subscription, typically Owner or Customer Lockbox Approver. Jentic stores the service principal in its encrypted vault and issues short-lived bearer tokens to agents.

Can I approve or deny a Lockbox request through this API?

Yes. POST to /subscriptions/{id}/providers/Microsoft.CustomerLockbox/requests/{requestId}/UpdateApproval with a body containing status ('Approved' or 'Denied') and a reason. The API returns the updated request record.

What are the rate limits for the Customer Lockbox API?

Azure Resource Manager applies subscription-level read and write throttling (around 1,200 requests per hour for reads and writes). Lockbox requests are low-volume by design, so practical throttling is rare in normal compliance workflows.

How do I auto-approve Lockbox requests through Jentic?

Run pip install jentic and search for 'approve customer lockbox request'. Jentic returns the Requests_UpdateStatus operation; load its schema and execute it with the subscriptionId, requestId, and a body of { status: 'Approved', reason: '...' }. Pair with Requests_List to identify pending requests first.

Does this API let me create or trigger a Lockbox request?

No. Lockbox requests are initiated by Microsoft support engineers during an active support case. This API only lets you list, inspect, and respond to those requests — it does not create them.