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 / Identity Auth / Azure / azureactivedirectory
azureactivedirectory logo

Microsoft Azure azureactivedirectory

Browse all Azure APIs
46
AI ReadinessFoundational (D)46/100
See full scorecard
Agent-ready OpenAPI document · curated by JenticIdentity AuthDirectory Servicesoauth26 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Configure where Azure AD sign-in and audit logs are routed by managing diagnostic settings on the aadiam tenant resource.

Use for: I need to send Azure AD sign-in logs to Log Analytics, Stream Azure AD audit logs to an Event Hub, List diagnostic settings on the AAD tenant, Get the named diagnostic setting on microsoft.aadiam

Not supported: Does not manage users, groups, applications, or conditional access - use for tenant-level Azure AD diagnostic settings only.

Jentic publishes the only available OpenAPI specification for Azure Active Directory diagnostic settings, keeping it validated and agent-ready. The API manages diagnostic settings on the microsoft.aadiam tenant resource, letting agents list and configure where Azure AD audit and sign-in logs are sent - Log Analytics workspace, storage account, or Event Hub. It exposes the diagnosticSettings, diagnosticSettingsCategories, and operations resources under the microsoft.aadiam provider on Azure Resource Manager.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the azureactivedirectory to your agent

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

List diagnostic settings on the Azure AD tenant resource

Retrieve a specific diagnostic setting by name

Create or update a diagnostic setting routing AAD logs to Log Analytics

Send Azure AD audit and sign-in logs to a storage account

Stream AAD logs to an Event Hub via diagnostic settings

List the categories of logs available for diagnostic export

Use Cases

Patterns agents use azureactivedirectory API for, with concrete tasks.

★ Stream Azure AD logs to Log Analytics

Configure a diagnostic setting that pushes Azure AD AuditLogs and SignInLogs into a Log Analytics workspace for KQL-based investigation. The PUT /providers/microsoft.aadiam/diagnosticSettings/{name} call attaches the workspaceId and selects log categories. The canonical configuration for Sentinel-based AAD monitoring.

PUT /providers/microsoft.aadiam/diagnosticSettings/aad-to-sentinel with workspaceId and logs[].category in (AuditLogs, SignInLogs) enabled, then verify the GET returns enabled=true

Long-term log archival to storage

Send Azure AD logs to a storage account for long-term retention beyond the default Azure AD log window. The same diagnosticSettings PUT accepts a storageAccountId and per-category retention days. Used by compliance teams who need year-scale retention of identity events.

PUT a diagnosticSetting named aad-archive with storageAccountId and per-category retentionPolicy.days set to 365

Event-driven SIEM integration

Stream Azure AD logs into an Event Hub so a non-Microsoft SIEM can subscribe and consume identity events in near real time. The diagnosticSettings PUT supports eventHubAuthorizationRuleId and eventHubName. This is the standard handoff point for Splunk, QRadar, and similar tools.

PUT diagnosticSetting with eventHubAuthorizationRuleId and confirm AuditLogs and SignInLogs categories are enabled

Agent-driven AAD log routing

Allow an AI agent to wire up an Azure AD log sink during environment bring-up without an operator hand-coding the long microsoft.aadiam resource path. Through Jentic the agent searches by intent, loads the diagnostic setting schema, and executes the PUT. Removes a class of typos when constructing the diagnostic settings request body.

Search Jentic for 'configure azure ad diagnostic setting', load the workspaceId and logs[] schema, and execute the PUT against microsoft.aadiam

Key Endpoints

6 endpoints — jentic publishes the only available openapi specification for azure active directory diagnostic settings, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/providers/microsoft.aadiam/diagnosticSettings

List diagnostic settings on the tenant

GET

/providers/microsoft.aadiam/diagnosticSettings/{name}

Get a specific diagnostic setting

PUT

/providers/microsoft.aadiam/diagnosticSettings/{name}

Create or update a diagnostic setting

DELETE

/providers/microsoft.aadiam/diagnosticSettings/{name}

Delete a diagnostic setting

GET

/providers/microsoft.aadiam/diagnosticSettingsCategories

List available log categories

GET

/providers/microsoft.aadiam/operations

List operations on microsoft.aadiam

GET

/providers/microsoft.aadiam/diagnosticSettings

List diagnostic settings on the tenant

GET

/providers/microsoft.aadiam/diagnosticSettings/{name}

Get a specific diagnostic setting

PUT

/providers/microsoft.aadiam/diagnosticSettings/{name}

Create or update a diagnostic setting

DELETE

/providers/microsoft.aadiam/diagnosticSettings/{name}

Delete a diagnostic setting

GET

/providers/microsoft.aadiam/diagnosticSettingsCategories

List available log categories

GET

/providers/microsoft.aadiam/operations

List operations on microsoft.aadiam

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.

A

azureactivedirectory

- Foundational (D)
46/100
100
Foundational Compliance
63
Developer Experience & Jentic Compatibility
23
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
100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4
99%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

63

Developer Experience & Jentic Compatibility

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

Grade: B-Signals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

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

100%

Tooling Readiness

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

23

AI-Readiness & Agent Experience

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

Grade: FSignals: 4
91%

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.

0%

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 AD diagnostic settings API by hand means registering an Azure AD app for OAuth2 bearer auth against management.azure.com, granting the microsoft.aadiam write role, and hand-building the diagnostic setting body with workspace, storage, or Event Hub sinks. Through Jentic you install once, import Azure Active Directory diagnostic settings from the API Directory, store the Azure AD credential once, and your agent calls it.

Permission scoping

The setting name sits in the URL path (/providers/microsoft.aadiam/diagnosticSettings/{name}), so a rule can pin your agent to a named diagnostic setting. You choose the operations it may call, so the DELETE that removes a log sink is not included unless you add it, leaving an agent that can only list, read, and create or update settings.

Credential isolation

Your Azure AD credential 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 'configure azure ad diagnostic setting to log analytics' or 'stream sign-in logs to an event hub', and Jentic returns the matching microsoft.aadiam diagnosticSettings operation with its full request body schema so the agent wires the sink without hand-coding the resource path.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Azure Log Analytics

→

Provisions the Log Analytics workspace this API routes AAD logs into

Use Log Analytics to create the workspace, then use this API to wire AAD logs into it

Complementary

Azure Monitor private link scopes

→

Restricts the network paths over which AAD logs flow into Azure Monitor

Pair when AAD log routing must traverse private link only

Complementary

Authorization management client

→

Manages the role assignments needed to write microsoft.aadiam diagnostic settings

Use authorization to grant the writer role before configuring diagnostic settings

FAQs

Specific to using azureactivedirectory API through Jentic.

Why is there no official OpenAPI spec for the Azure Active Directory diagnostic settings API?

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

The API uses Azure AD OAuth 2.0 with the implicit flow, scoped to user_impersonation against management.azure.com. The caller needs a role with Microsoft.aadiam/diagnosticSettings/write on the tenant. Through Jentic, the bearer token is held in your Jentic One instance and exchanged for a scoped access token at execution time.

Can I send Azure AD logs to multiple destinations at once?

Yes. A single diagnostic setting can specify any combination of workspaceId, storageAccountId, and eventHubAuthorizationRuleId. To send to multiple workspaces, create separate named settings via PUT /diagnosticSettings/{name}.

What are the rate limits for this API?

Azure Resource Manager applies tenant-level throttling - typically 12,000 reads and 1,200 writes per hour per subscription. Diagnostic setting writes are synchronous and return 200 with the resulting resource.

How do I configure AAD log routing through Jentic?

Run pip install jentic, then search for 'configure azure ad diagnostic setting'. Jentic returns the PUT /providers/microsoft.aadiam/diagnosticSettings/{name} operation, loads the workspaceId and logs schema, and executes the call.

Does this API manage users, groups, or sign-in policies?

No. This API only manages tenant-level diagnostic settings under microsoft.aadiam. User and group management lives in Microsoft Graph; sign-in policies are managed via Conditional Access APIs.

Can I limit what my agent is allowed to do with the Azure Active Directory diagnostic settings API?

Yes. Because Jentic One is self-hosted, your own rules decide which of the microsoft.aadiam operations the agent may call and which credential it uses, so you can grant it list, get, and create-or-update on diagnosticSettings while withholding the DELETE that removes a log sink. Since the setting name sits in the URL path at /providers/microsoft.aadiam/diagnosticSettings/{name}, a rule can also pin the agent to one named diagnostic setting rather than every setting on the tenant. The Azure AD credential is injected at execution time by your instance and never enters the agent's prompt or context.

GET STARTED

Start building with azureactivedirectory API

Explore with Jentic One
View OpenAPI Document