What is out of scope for this vendor?

The grouped APIs handle Batch compute and Azure AD directory objects only. They do not cover payments, customer messaging, crm, blob storage, or general Azure Resource Manager provisioning.

How does an agent find the right operation?

An agent searches the Jentic directory by intent, such as submitting a batch job or listing directory applications, and Jentic returns the matching operation with its input schema so the agent calls the correct endpoint without reading the reference docs.

Azure (windows.net) APIs for AI Agents

Developer ToolsSource ControlRecruiting AtsMixed ProvenanceNo authOAuth 2.0Agent Ready

azure.microsoft.com

Azure (windows.net) API Catalog

2 APIs across 2 product groups.

Developer Tools1

BatchServiceProgrammatically lists all of the applications available in the specified account., gets information about the specified application..~70 endpoints

HR recruiting1

GraphRbacManagementClientProgrammatically applications_create, applications_list.~56 endpoints

Which Azure (windows.net) API should I use?

I want to...	Use	Why
Run and manage large-scale compute jobs, tasks, and certificates	BatchService	BatchService covers applications, jobs, job schedules, and certificates on the Azure Batch account.
Manage directory applications, groups, domains, and owners in a tenant	GraphRbacManagementClient	GraphRbacManagementClient handles Azure AD application, group, and directory object operations.

Install Jentic One Beta

Connect the Azure (windows.net) APIs to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Azure (windows.net) APIs, 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fwindows.net" | sh

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%2Fwindows.net" | 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.

Once connected, ask your agent something like: “run an Azure Batch job and manage the Azure AD application that authorizes it”.

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Instead of wiring the Azure Batch endpoint on batch.core.windows.net and the Azure AD OAuth flow on graph.windows.net by hand, you install Jentic One once and add both APIs from the Jentic directory to your workspace. Once Jentic One is installed, you or your agent can find and add any API from the Jentic directory to your workspace.

Permission scoping

Both APIs put resource ids in the URL path, such as an application id on Batch and a tenant and application object id on GraphRbac, so your own rules can pin an agent to reading one application or one tenant. You choose which operations the agent may call, so destructive ones like deleting a certificate or removing an application owner are excluded unless you add them.

Credential isolation

FAQs

Specific to using Azure (windows.net) APIs through Jentic.

What does the windows.net vendor cover on Jentic?

It groups two Microsoft Azure REST APIs reached through the windows.net domain: Azure Batch (BatchService) for running compute jobs, tasks, and certificates, and Azure Active Directory Graph RBAC (GraphRbacManagementClient) for managing directory applications, groups, and domains.

Do the two APIs share one credential?

No. BatchService uses no authentication in its current spec, while GraphRbacManagementClient authenticates with OAuth 2.0 against Azure Active Directory. Each API is configured with its own credential in your Jentic One instance.

Can an agent use both APIs together?

Yes. An agent can register or read an Azure AD application through GraphRbacManagementClient and then submit or inspect the corresponding compute work through BatchService, combining identity management with batch job orchestration.

Is this an official Microsoft product?

windows.net is a Microsoft-owned domain used by Azure services. These are Azure service APIs; Jentic groups them here by their shared domain and does not represent an official Microsoft integration.

BOOK A DEMO

Start Connecting APIs to Your AI Agents

Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.

Book a Demo

For Agents

APIs2 in catalogue

Endpoints126 indexed

AuthNo auth / OAuth 2.0

ProvenanceMixed provenance

An agent can submit and manage Azure Batch jobs, job schedules, application packages, and certificates, and separately create, read, update, and remove Azure AD applications, groups, domains, and their owners across a tenant.

These are Microsoft Azure service APIs reached through the windows.net domain, pairing Azure Batch compute-job orchestration with Azure Active Directory Graph identity and application management, so an agent can run compute work and govern the directory objects that authorize it from one vendor.

Use for: Orchestrating Azure Batch compute jobs, tasks, and certificates and managing Azure Active Directory applications, groups, and directory objects through the windows.net endpoints

Not supported: payment processing, customer messaging, crm records, Azure Resource Manager provisioning, blob storage

Credentials: No, the two APIs authenticate differently: BatchService uses no auth in this spec while GraphRbacManagementClient uses OAuth 2.0 against Azure Active Directory, so each needs its own credential.

What AI Agents Can Do with Azure (windows.net)

Each workflow spans multiple Azure (windows.net) APIs. Jentic routes each operation to the right API automatically.

Provision an app identity and run a batch job under it

Register an Azure AD application to represent a workload, then submit a job to an Azure Batch account so the compute work runs under a governed identity.

Example prompt:

Call POST /{tenantID}/applications on graphrbac to register the application, then POST /jobs on batch-BatchService to add the job to the account

APIs used

GraphRbacManagementClient + BatchService

Audit directory apps and batch account contents

List Azure AD applications and their owners in a tenant and list the applications and certificates present on a Batch account to build a combined inventory.