canonical: https://jentic.com/apis/windows.net

# Azure (windows.net) APIs

The windows.net domain hosts Microsoft Azure service endpoints. This vendor groups two Azure REST APIs: the Azure Batch service (BatchService on batch.core.windows.net) for running large-scale compute jobs, and the Azure Active Directory Graph RBAC service (GraphRbacManagementClient on graph.windows.net) for managing directory applications, groups, and role assignments. Together they let an agent provision and run batch compute workloads and manage the identities and applications that access them.

## For AI agents

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.

## Scope

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

## APIs

| API | Category | Endpoints | Description |
| --- | --- | --- | --- |
| BatchService | developer-tools | 70 | Programmatically lists all of the applications available in the specified account., gets information about the specified application.. |
| GraphRbacManagementClient | hr-recruiting | 56 | Programmatically applications_create, applications_list. |

## Which API to use

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

## Cross-API use cases

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

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

Example prompt: Call GET /{tenantID}/applications on graphrbac and GET /applications and GET /certificates on batch-BatchService, then compile the results

## Why Jentic

- **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 handling:** Each API's credential, the Batch access and the Azure AD OAuth client, is stored encrypted by your own self-hosted Jentic One instance and injected at execution time, so raw secrets never enter the agent's prompt, logs, or context.
- **Discovery method:** An agent searches the Jentic directory by intent, such as submitting a batch job or listing applications in a tenant, and Jentic returns the matching BatchService or GraphRbac operation with its input schema so the agent calls the right endpoint across both APIs.

## Related vendors

- **Microsoft** — Microsoft Graph and Azure Resource Manager cover newer identity and resource-provisioning APIs adjacent to these Azure services.
- **Google Cloud** — Google Cloud offers comparable batch compute and IAM identity management APIs as an alternative provider.
- **Amazon Web Services** — AWS Batch and IAM provide equivalent compute-job scheduling and identity administration.

## FAQ

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

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