Microsoft Azure Dynamics Telemetry

Name: Dynamics Telemetry API
Brand: Dynamics Telemetry
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsMonitoring Observabilityoauth21 Endpoints

Install Jentic One Beta

Connect the Dynamics Telemetry to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Dynamics Telemetry, 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: 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 Dynamics Telemetry API.

Retrieve the catalogue of CSM operations for Microsoft.DynamicsTelemetry

Discover the action strings required to author custom RBAC roles on the provider

Drive role-definition tooling that needs the provider operations list

GET STARTED

Start building with Dynamics Telemetry API

Explore with Jentic

View OpenAPI Document

For Agents

List the operations exposed by the Microsoft.DynamicsTelemetry resource provider so an agent can plan custom RBAC roles or audit role assignments on Dynamics telemetry resources.

Use for: List every operation supported by the Microsoft.DynamicsTelemetry provider, Find the RBAC action string for reading Dynamics telemetry resources, Retrieve the operations catalogue to build a custom Azure role, Check whether the provider exposes a specific telemetry action

Not supported: Does not return telemetry data, manage telemetry resources, or configure Dynamics workloads - use only to enumerate operations exposed by the Microsoft.DynamicsTelemetry provider.

Use Cases

Patterns agents use Dynamics Telemetry API for, with concrete tasks.

★ Custom RBAC for Dynamics Workloads

Defining an Azure role that grants read-only access to Dynamics telemetry without granting compute or networking permissions requires the exact action strings on Microsoft.DynamicsTelemetry. Calling Operations_List returns those strings so a tool can emit a role definition (Bicep, ARM, or Terraform) restricted to the provider - keeping Dynamics observability service principals on a least-privilege footing.

Call Operations_List on Microsoft.DynamicsTelemetry and emit a Bicep custom-role definition granting all read operations and no write or delete operations.

Cross-Provider Operations Audit

Compliance reviews look at whether service principals across an Azure tenant have appropriate, scoped permissions on every resource provider that handles customer data. By calling Operations_List on Microsoft.DynamicsTelemetry alongside other providers, an audit tool can build a tenant-wide map of what actions exist and cross-reference it against actual role assignments to flag wildcard grants.

Pull Operations_List for Microsoft.DynamicsTelemetry and verify that no role assignment in the tenant grants Microsoft.DynamicsTelemetry/* on any subscription.

Provider Feature Detection

Tooling that wraps multiple Dynamics-related Azure APIs needs to detect when new operations land in the Microsoft.DynamicsTelemetry provider. Calling Operations_List at deployment time lets the wrapper feature-flag any operations not yet returned and avoid runtime errors when older API versions are pinned.

Compare the operations list returned by two different api-version values for Microsoft.DynamicsTelemetry and emit a diff of added or removed operation names.

AI Agent Permissions Discovery via Jentic

An IAM agent integrated through Jentic can answer a question like what Azure permissions are needed to read Dynamics telemetry by searching Jentic for list dynamics telemetry operations, calling Operations_List, and returning only the read action strings. This makes least-privilege role design a one-prompt task instead of a documentation hunt.

Through Jentic, search for list dynamics telemetry operations, load Operations_List, execute it, and return only operations whose name ends in /read.

Key Endpoints

1 endpoints — jentic publishes the only available openapi specification for dynamics telemetry, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/providers/Microsoft.DynamicsTelemetry/operations

List CSM operations supported by the Microsoft.DynamicsTelemetry resource provider

GET

/providers/Microsoft.DynamicsTelemetry/operations

List CSM operations supported by the Microsoft.DynamicsTelemetry resource provider

Why Jentic?

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

Credential isolation

Your Azure AD credential is stored once, encrypted, by your own Jentic One instance and injected as a short-lived bearer token at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list dynamics telemetry operations', and Jentic returns the Microsoft.DynamicsTelemetry list-operations call with its empty input schema so the agent runs it directly without crawling ARM docs.

Time to first call

FAQs

Specific to using Dynamics Telemetry API through Jentic.

Why is there no official OpenAPI spec for Dynamics Telemetry?

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

It uses Azure Active Directory OAuth 2.0 (azure_auth) against https://management.azure.com/. The principal needs read access at the appropriate scope. Through Jentic the underlying client secret stays in your Jentic One instance and the agent only sees a scoped bearer token.

What does Operations_List return?

GET /providers/Microsoft.DynamicsTelemetry/operations returns the catalogue of CSM operations the provider supports, each with a name like Microsoft.DynamicsTelemetry/operations/read and a display object describing the operation in natural language. Use it to build custom RBAC roles or audit existing role assignments.

What are the rate limits for the Dynamics Telemetry API?

Standard Azure Resource Manager subscription-scoped read throttling applies (broadly 12,000 reads per hour). Because this API exposes a single read endpoint with a small payload, throttling is rarely the binding constraint.

How do I list provider operations through Jentic?

Run pip install jentic, search for list dynamics telemetry operations, load Operations_List, and execute it with no parameters. The response is the array of operation definitions ready to drop into a role-definition tool.

Does this API let me read or write actual Dynamics telemetry data?

No. This API only exposes provider operations metadata. It does not return telemetry payloads - those flow through Microsoft Dynamics workloads themselves rather than this resource provider operations endpoint.

Can I limit what my agent is allowed to do with the Dynamics Telemetry API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent can use, and this API exposes only one read-only call, Operations_List (GET /providers/Microsoft.DynamicsTelemetry/operations). Grant the agent just that single list operation and it can only enumerate the provider's operation metadata for building or auditing RBAC roles, with no ability to touch resources or write anything. The Azure AD credential stays in your instance and is injected as a short-lived scoped token at execution time.