Skip to main content
resource · azure

Azure AI Foundry Resource

schedulable
no
category
ai-ml-services

Does ZopNight manage Azure AI Foundry Resource?

Azure AI Foundry resources are Cognitive Services accounts of kind AIServices, and the account is where token and PTU meters actually bill. ZopNight expands each account into its projects, model deployments, and connections, then attributes Cost Management spend to the account, with the hierarchy beneath it showing which models and projects exist.

Rules that fire on Azure AI Foundry Resource

no live rules

No active rule family targets Azure AI Foundry Resource today. Rules that used to are retired, and retired rules publish no pages and fire no findings. Scheduling and permissions coverage are unaffected.

Browse every live recommendation for this platform →

At a glance

Azure AI Foundry Resource coverage facts.
Field Value
Scheduling notesdiscovery and topology only.

Azure AI Foundry is Microsoft’s unified platform for building generative AI applications, exposing models, agents, and evaluation tooling. Foundry resources anchor the deployments and compute where AI spend concentrates.

Where Foundry spend actually accrues

A Foundry resource is a Cognitive Services account of kind AIServices, and the account is the billing anchor. Token consumption from pay-as-you-go model calls and the reserved capacity of provisioned deployments both land on the account’s meters; the child deployment rows themselves carry no charge of their own. In practice that means the invoice tells you which account spent, while the expanded hierarchy underneath shows which models, projects and connections exist inside it; ZopNight does not split the account’s spend across them.

Expanding the account into its children

Discovered via the AI enricher with child projects, deployments, and connections expanded beneath it. Cost Management billing attributes spend to the account; the projects and deployments beneath it carry no cost of their own. ZopNight inserts synthetic grouping nodes (Model Deployments, Agents, Content Filter Policies) between the account and each cluster of children, and keeps the account as the grandparent, so each child stays tied to the right account even when an estate runs many Foundry accounts side by side.

Sprawl signals on Foundry accounts

The recurring failure mode is one account per experiment: a hackathon or proof of concept creates a fresh Foundry resource, deploys a model or two, and moves on. Each abandoned account may still hold provisioned deployments billing reserved capacity, connections into production data services, and agents nobody remembers configuring. A second pattern is the untracked account outside the platform team’s subscription, invisible until its meters show up in a monthly review. Inventorying every account and its children is what makes both patterns reviewable.

Reaching the account in the Azure portal

Azure portal → Azure AI Foundry lists the accounts, or filter Cognitive Services accounts to the AIServices kind. Day-to-day management of projects, deployments, and agents happens in the separate AI Foundry portal, which scopes its view to one account and project at a time; the Azure portal remains the place to see every account a subscription actually contains.

See it fire on your bill.

Connect an account read-only. The first findings land in minutes.

472 rule families across 353 resource types on 22 platforms. Every threshold, metric, and IAM action is documented on these pages before you grant anything.

472 rule families documented
353 resource types covered
read-only default access level
Multi-cloud automation· Production-ready in 30 min· SOC 2 · ISO 27001· 20–60% off the bill, first month· 4 platforms · 1 console· Multi-cloud automation· Production-ready in 30 min· SOC 2 · ISO 27001· 20–60% off the bill, first month· 4 platforms · 1 console·