Microsoft Azure PolicyTrackedResourcesClient

Name: PolicyTrackedResourcesClient API
Brand: Azure Policy Tracked Resources
Availability: InStock

★ Only Publicly Available OpenAPI DocumentSecurityComplianceoauth24 EndpointsREST

For Agents

Query the inventory of resources created or modified by deployIfNotExists and modify Azure Policy effects through 4 OData query endpoints under Microsoft.PolicyInsights.

Install Jentic One Beta

Connect the PolicyTrackedResourcesClient to your agent

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

List resources created by deployIfNotExists policy effects within a subscription

Inspect resources modified by modify-effect policies for tag, location, or property changes

Filter tracked resources by the policy assignment that produced them

GET STARTED

Start building with PolicyTrackedResourcesClient API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for PolicyTrackedResourcesClient, keeping it validated and agent-ready. The Azure Policy Insights tracked resources API exposes 4 query endpoints under Microsoft.PolicyInsights for retrieving the inventory of resources that deployIfNotExists and modify policy effects have created or altered. Use it to verify that remediation actions actually ran, list the resources spawned by an initiative, or audit which deployments are owned by policy rather than direct user action — at management group, subscription, resource group, or individual resource scope.

Use Cases

Patterns agents use PolicyTrackedResourcesClient API for, with concrete tasks.

★ Remediation Audit

Verify that deployIfNotExists and modify policy effects ran as expected. Querying tracked resources at the relevant scope returns every resource that policy created or altered, with a back-pointer to the policy assignment that owns it. This closes the loop between policy assignment and remediation outcome — instead of trusting that an effect fired, the agent checks the inventory of what the effect actually produced.

Query tracked resources for the production subscription filtered to policyAssignmentId='/subscriptions/{id}/providers/Microsoft.Authorization/policyAssignments/diagnostics-deploy' and report the resource count

Modify-Effect Tag Drift Audit

When a modify-effect policy auto-applies tags (for example to backfill 'cost-center' or 'environment'), this API lists every resource the policy touched. The result is the audit trail of automated tag changes — useful when a downstream system that depends on tag values needs to reconcile drift, or when a finance team asks which resources had tags applied by automation rather than the original deployer.

Query tracked resources at subscription scope filtered to the modify-tag policy assignment, return the list of resources touched, and group by resource type

Policy-Owned Resource Cleanup

Before deleting a resource group or a workload, identify which contained resources were created by policy rather than by the team that owns the workload. Listing tracked resources at resource group scope surfaces policy-owned items so the cleanup plan can either keep them in place (if the policy will recreate them) or explicitly disable the relevant assignment first. Without this step, manual deletions are silently re-created, leading to confusion.

List tracked resources for resource group 'app-prod', return their IDs and the originating policy assignment, and produce a cleanup plan

AI Agent Remediation Verifier

An AI agent supporting a security or governance team can verify policy remediation through Jentic. The agent searches by intent ('list azure policy tracked resources'), Jentic returns the queryResults operation with its OData filter schema, and the agent executes the call with managed Azure credentials. The same flow handles cross-subscription audit at management group scope.

Search Jentic for 'list Azure policy tracked resources', load the queryResults schema, and execute it for the production subscription with a 7-day filter

Key Endpoints

4 endpoints — jentic publishes the only available openapi specification for policytrackedresourcesclient, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/subscriptions/{subscriptionId}/providers/Microsoft.PolicyInsights/policyTrackedResources/{policyTrackedResourcesResource}/queryResults

Query tracked resources at subscription scope

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.PolicyInsights/policyTrackedResources/{policyTrackedResourcesResource}/queryResults

Query tracked resources at resource group scope

POST

/providers/{managementGroupsNamespace}/managementGroups/{managementGroupName}/providers/Microsoft.PolicyInsights/policyTrackedResources/{policyTrackedResourcesResource}/queryResults

Query tracked resources at management group scope

POST

/{resourceId}/providers/Microsoft.PolicyInsights/policyTrackedResources/{policyTrackedResourcesResource}/queryResults

Query tracked resources for a specific resource

POST

/subscriptions/{subscriptionId}/providers/Microsoft.PolicyInsights/policyTrackedResources/{policyTrackedResourcesResource}/queryResults

Query tracked resources at subscription scope

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.PolicyInsights/policyTrackedResources/{policyTrackedResourcesResource}/queryResults

Query tracked resources at resource group scope

POST

/providers/{managementGroupsNamespace}/managementGroups/{managementGroupName}/providers/Microsoft.PolicyInsights/policyTrackedResources/{policyTrackedResourcesResource}/queryResults

Query tracked resources at management group scope

POST

/{resourceId}/providers/Microsoft.PolicyInsights/policyTrackedResources/{policyTrackedResourcesResource}/queryResults

Query tracked resources for a specific resource

Why Jentic?

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

Credential isolation

Azure service principal credentials are encrypted in the Jentic vault. Agents receive scoped ARM bearer tokens at execution time and never see the underlying client secret.

Intent-based discovery

Agents search by intent ('list azure policy tracked resources') and Jentic returns the matching scope-specific queryResults operation, avoiding the need to pick between the four scope variants manually.

Time to first call

Direct ARM integration: half a day for AAD app registration, MSAL token handling, and OData filter construction. Through Jentic: under 30 minutes.

FAQs

Specific to using PolicyTrackedResourcesClient API through Jentic.

Why is there no official OpenAPI spec for PolicyTrackedResourcesClient?

Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call PolicyTrackedResourcesClient via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Azure Policy Tracked Resources API use?

It uses Azure Active Directory OAuth 2.0 against https://management.azure.com/ with the user_impersonation scope. The caller needs Reader on Microsoft.PolicyInsights at the queried scope. Jentic stores service principal credentials encrypted and issues short-lived bearer tokens at execution time.

Can I see which resources were created by a specific deployIfNotExists assignment?

Yes. POST to /subscriptions/{id}/providers/Microsoft.PolicyInsights/policyTrackedResources/default/queryResults with $filter=policyAssignmentId eq '{assignmentId}' in the OData query. The response lists each resource created or modified by that assignment along with the originating evaluation timestamp.

What are the rate limits for the Policy Tracked Resources API?

Azure Resource Manager applies subscription-level throttling at roughly 1,200 reads per hour. Tracked resource queries can return large result sets; use $top and $skiptoken pagination for environments with hundreds of remediations.

How do I audit policy remediations through Jentic?

Run pip install jentic and search for 'list Azure policy tracked resources'. Jentic returns the queryResults operation; load its schema and execute it at the desired scope with optional $filter on policyAssignmentId or timestamp.

Does this API include resources affected by audit-effect policies?

No. Tracked resources covers deployIfNotExists and modify effects, which create or change resources. Audit, deny, and append effects are not in scope here. For audit-effect compliance state use PolicyStatesClient; for evaluation history use PolicyEventsClient.

Microsoft Azure PolicyTrackedResourcesClient

Connect the PolicyTrackedResourcesClient to your agent

Capabilities

Start building with PolicyTrackedResourcesClient API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs