windows.net
windows.net is used by Microsoft Azure service endpoints, including Azure Batch and the legacy Azure AD Graph RBAC API. These endpoints support cloud workload scheduling/management and directory object management for Azure tenants.
windows.net exposes two documented HTTP API surfaces: the Azure Batch Service REST API and the Azure AD Graph RBAC REST API; both require authentication, with Batch accepting either Shared Key or Microsoft Entra bearer tokens and Graph RBAC using Microsoft Entra OAuth.
- Azure Batch Service REST APIdiscovered
- Azure AD Graph RBAC REST APIdiscovered
In the Azure portal, open your Batch account and retrieve one of the account access keys from the account settings described in Manage Batch accounts. The Batch REST auth doc states the Batch service supports authentication via Shared Key; use your Batch account name together with one of its access keys to sign requests.
Register an application in Microsoft Entra ID from the Azure portal as described in Authenticate Azure Batch services with Microsoft Entra ID and standard Azure app registration flows. Then acquire an OAuth access token for the target resource/audience required by the API: Batch uses https://batch.core.windows.net/, and Azure AD Graph / Graph RBAC uses a token for https://graph.windows.net/.
conventions · 0/8 published
- integrations.json✗
/.well-known/integrations.json - llms.txt✗
/llms.txt - API catalog✗
/.well-known/api-catalog - OpenAPI document✗
/api/schema/, /openapi.json, /swagger.json, /api/openapi.json, or /v1/openapi.json - MCP server card✗
/.well-known/mcp/server-card.json - OAuth protected resource✗
/.well-known/oauth-protected-resource - Agent card✗
/.well-known/agent-card.json - Agent skills✗
/.well-known/agent-skills/index.json
Publish these signals → /publishing