Glossary
Search Azure terms
Open a clear definition, then continue into exam context, architecture, commands, operational examples, common mistakes, and related concepts.
Search all
Commands
Learning guides
Concept graph
Compare
Search-first Azure knowledge base
Term results
Search for a term or click a category. Results render only after you ask for them, so the glossary does not dump every available term on first load. Each result includes Quick peek and Open full term page actions.
Start with a search or a category.
Try managed identity , resource group , az group , private endpoint , or click Databases to load all database-related terms.
Management and Governance
premium
Policy effect
A policy effect is the action Azure Policy takes after a rule matches a resource. The rule asks a question, such as whether a storage account allows public access, and the effect decides the response. Some effects only record a finding, some block the request, some add or change properties, and some deploy supporting settings later. For a learner or operator, the effect is the difference between a policy that warns, a policy that prevents drift, and a policy that actively repairs configuration.
Azure Policy
intermediate
5 commands
Aliases: Policy effect, policy-effect
Quick peek
Open full term page
Management and Governance
premium
Policy event
A policy event is a record or notification that something changed in Azure Policy evaluation. It can tell you that a resource became compliant, became non-compliant, or had a policy state created or removed. Instead of waiting for someone to refresh a portal report, teams can query policy events or route state-change events through Event Grid. For operators, this makes policy activity visible close to the time it happens, so compliance changes can trigger alerts, tickets, evidence capture, or remediation workflows.
Azure Policy
intermediate
5 commands
Aliases: Policy event, policy-event
Quick peek
Open full term page
Management and Governance
premium
Policy exemption
A policy exemption is an approved exception to an Azure Policy assignment. It says that a resource, resource group, subscription, or management group should not be evaluated by a specific policy or initiative for a documented reason. The resource still appears in compliance reporting, but the exemption explains why it is not treated like ordinary non-compliance. Exemptions are useful when a migration, vendor dependency, outage response, or compensating control makes immediate compliance unrealistic. They should be owned, time-bound, and reviewed.
Azure Policy
intermediate
5 commands
Aliases: Policy exemption, policy-exemption
Quick peek
Open full term page
Management and Governance
premium
Policy initiative
A policy initiative is a bundle of related Azure Policy definitions. Instead of assigning ten separate policies for tags, allowed regions, diagnostics, encryption, and public access, a team can group them into one initiative and assign that package to a scope. It makes a governance baseline easier to deploy, review, and explain. For learners, think of an initiative as a control set: the individual policies still do the checking, but the initiative provides the organized package, shared parameters, and management structure.
Azure Policy
intermediate
5 commands
Aliases: Policy initiative, Policy set definition, policy-initiative
Quick peek
Open full term page
Management and Governance
premium
Policy Insights
Policy Insights is where Azure Policy compliance evidence becomes queryable. Azure Policy definitions and assignments describe what should happen, but Policy Insights shows what Azure observed after evaluation. It stores state records that show current compliance and event records that show recent evaluation activity. Operators use it to answer questions such as which resources are non-compliant, which assignment is responsible, when the state changed, and whether remediation improved results. It turns policy from a static rule set into operational telemetry.
Azure Policy
intermediate
5 commands
Aliases: Policy Insights, policy-insights
Quick peek
Open full term page
Management and Governance
premium
Policy notScope
Policy notScope is the list of places where an Azure Policy assignment should not apply. Think of it as a surgical exclusion inside a larger assignment. A governance team might assign a location policy to an entire management group, then exclude a disaster recovery resource group or migration subscription that needs temporary freedom. The assignment still exists at the parent scope, but Azure Policy skips the excluded child scope during evaluation, so those resources do not appear as non-compliant for that assignment.
Azure Policy
intermediate
5 commands
Aliases: notScopes, Policy notScope, policy-not-scope
Quick peek
Open full term page
Management and Governance
premium
Policy parameter
A policy parameter is a safe input box for Azure Policy. Instead of writing separate policies for each allowed region, tag name, diagnostic workspace, or enforcement effect, you define the rule once and pass different values when assigning it. That makes policies easier to reuse across management groups, subscriptions, and environments. Parameters can include defaults, allowed values, friendly display names, and metadata, so platform teams can offer controlled choices without asking every application team to understand the full policy JSON.
Azure Policy
intermediate
5 commands
Aliases: Policy parameter, policy-parameter
Quick peek
Open full term page
Management and Governance
premium
Policy remediation
Policy remediation is Azure Policy’s controlled repair job for resources that already exist. A deny policy can stop a bad new deployment, but it cannot automatically fix old resources. Remediation is for policies with modify or deployIfNotExists effects, such as adding required tags or deploying missing diagnostic settings. You create a remediation task, Azure finds the affected resources, and the assignment’s managed identity performs the configured change. It is governance automation, but it still needs careful scope, permission, and result review.
Azure Policy
intermediate
5 commands
Aliases: Policy remediation, policy-remediation
Quick peek
Open full term page
Management and Governance
premium
Policy state
Policy state is the evidence record behind an Azure Policy compliance result. It answers practical questions such as which resource was evaluated, which policy assignment applied, whether the resource was compliant, and when Azure last knew that result. The portal summarizes these states, but operators often query them directly through Azure CLI, REST, or Resource Graph when they need proof. Policy state is especially useful when a dashboard says “non-compliant” and the team needs to locate the exact resource, policy, scope, and reason.
Azure Policy
intermediate
5 commands
Aliases: Policy state, policy-state
Quick peek
Open full term page
No glossary terms matched that search.
Try a service name, acronym, command group, or category such as RBAC , az group , App Service , Application Insights , Databases , or Azure AI Search .
Clear filters and show matches
Reset search
