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.
Showing 50 of 968 matching terms. Narrow the search to reduce the list.
Databases
premium
Flexible server
A flexible server is the Azure Database deployment model for managed PostgreSQL or MySQL servers with configurable compute, storage, availability, maintenance, backup, and networking options. Teams use it to host managed relational databases with more control over maintenance windows, compute tiers, backup retention, high availability, private networking, stop-start behavior, and performance settings. It is not a self-managed VM database, a single-server compatibility promise, a free unlimited database tier, or proof that schema design, indexes, failover, and application connection pooling are correct.
Azure managed databases
intermediate
6 commands
Aliases: Azure Database flexible server, PostgreSQL flexible server, MySQL flexible server, managed flexible database server
Quick peek
Open full term page
Developer Tools
premium
EF Core migration
An EF Core migration records database schema changes from an Entity Framework Core model so teams can generate, review, and apply controlled schema updates.
.NET data access
intermediate
4 commands
Aliases: Entity Framework Core migration, EF migration
Quick peek
Open full term page
Databases
verified
Pending migration
A pending migration means the application already knows about a database schema change, but the database has not received it yet. The code might expect a new table, column, index, or constraint that is missing in production. In Azure, this often appears during App Service, Functions, container, or pipeline deployments connected to Azure SQL, PostgreSQL, or another managed database. It is not just a developer warning; it is a sign that release order, approval, connection strings, and rollback plans need attention.
Database deployment
intermediate
4 commands
Aliases: EF Core pending migration, unapplied migration, database migration pending, schema migration drift, pending model change
Quick peek
Open full term page
Databases
premium
Shared database throughput
Shared database throughput in Azure Cosmos DB means RU/s are provisioned at the database level and shared by containers in that database. Microsoft recommends container-level throughput for most workloads because shared throughput can create unpredictable performance and scale behavior across containers.
Azure Cosmos DB
intermediate
5 commands
Aliases: Cosmos DB shared database throughput, database-level throughput, shared RU/s database, Cosmos DB database throughput, shared throughput database
Quick peek
Open full term page
Management and Governance
premium
What-if deployment
A what-if deployment is a preview of changes Azure Resource Manager predicts from an ARM template or Bicep file before deployment. It shows which resources would be created, modified, ignored, or deleted without applying changes, helping teams review infrastructure impact before execution.
Infrastructure as code
fundamentals
5 commands
Aliases: ARM what-if deployment, Bicep what-if deployment, deployment preview
Quick peek
Open full term page
Management and Governance
learning-path-anchor
Tenant deployment
A tenant deployment is a Resource Manager deployment executed at Microsoft Entra tenant scope.
ARM deployments
intermediate
5 commands
Aliases: Tenant deployment, tenant deployment, Azure Tenant deployment, tenant scope deployment, az deployment tenant, ARM tenant deployment
Quick peek
Open full term page
Databases
premium
Managed instance database
A managed instance database is a database hosted inside Azure SQL Managed Instance with managed platform operations and SQL Server compatibility features. Teams use it when a workload needs managed SQL operations while keeping instance-level features closer to SQL Server. In plain English, it gives operators a named control for database-level ownership, backup evidence, restore planning, and migration clarity within a managed instance instead of leaving the decision hidden in a portal setting, script, or deployment file. Treat it as production-ready only when the owner, dependencies, permission boundary, monitoring signal, and rollback evidence are clear.
Azure SQL Managed Instance
intermediate
3 commands
Aliases: Managed instance database, Azure SQL Managed Instance
Quick peek
Open full term page
Databases
complete
SQL database
Microsoft Learn describes Azure SQL Database as a fully managed relational database service where a single database is created on a logical server and configured with compute, storage, backup, security, and availability settings. It supports portal, PowerShell, Azure CLI, REST, and Transact-SQL operations for deployment and management.
Azure SQL
fundamentals
5 commands
Aliases: Azure SQL database, single SQL database, Azure SQL DB, SQL DB resource
Quick peek
Open full term page
Web
premium
Function deployment slot
Function deployment slot is a separate deployment environment inside a Function App that can host a release before it becomes the production slot. Teams use it to test code, app settings, warmup behavior, and integrations under the same app boundary before swapping traffic to the new version. In daily Azure work, it appears when engineers deploy a queue processor safely, warm an HTTP API, test slot settings, or roll back a bad serverless release without rebuilding the app.
Azure Functions
intermediate
6 commands
Aliases: Azure Functions deployment slot, function app slot, staging slot for Functions
Quick peek
Open full term page
Containers
premium
Kubernetes Deployment
A Kubernetes Deployment is a workload controller that declaratively manages ReplicaSets and pods for stateless applications.
Kubernetes workloads
Intermediate
6 commands
Aliases: No aliases yet
Quick peek
Open full term page
Databases
premium
Azure Database for MySQL Flexible Server
A fully managed Azure database service for MySQL workloads with configurable compute, storage, backups, networking, maintenance, and high availability options.
Managed MySQL
intermediate
5 commands
Aliases: MySQL Flexible Server
Quick peek
Open full term page
Databases
premium
Azure Database for PostgreSQL Flexible Server
A fully managed Azure PostgreSQL service with configurable compute, storage, backups, networking, maintenance, extensions, and high availability options.
Managed PostgreSQL
intermediate
5 commands
Aliases: PostgreSQL Flexible Server
Quick peek
Open full term page
Databases
premium
Azure SQL Database
Azure SQL Database is a fully managed relational database service in Azure that provides SQL Server-compatible engines as single databases, elastic pools, and serverless or provisioned compute choices. Microsoft Learn presents it as platform as a service with built-in availability, backups, patching, scaling, and security integration.
Database
intermediate
5 commands
Aliases: Azure SQL DB, Azure SQL Database, Azure SQL pooled database, Azure SQL single database, SQL Database
Quick peek
Open full term page
Databases
premium
Azure SQL database copy
Azure SQL database copy creates a transactionally consistent copy of an Azure SQL Database using portal, PowerShell, Azure CLI, or Transact-SQL.
Azure SQL Database
fundamentals
5 commands
Aliases: Azure SQL copy, Azure SQL database copy, CREATE DATABASE AS COPY OF, SQL database copy, database copy
Quick peek
Open full term page
Databases
premium
Azure SQL Database DTU model
Azure SQL Database DTU model is a purchasing model that bundles compute, storage, and I/O resources into Database Transaction Units for Basic, Standard, and Premium tiers.
Azure SQL Database
fundamentals
5 commands
Aliases: Azure SQL Database DTU model, DTU model, DTU-based purchasing model, Database Transaction Unit, eDTU
Quick peek
Open full term page
AI and Machine Learning
premium
Batch deployment
A batch deployment in Azure Machine Learning is the deployment configuration behind a batch endpoint, defining the model or pipeline, compute, environment, and execution behavior for asynchronous inference.
Azure Machine Learning
intermediate
5 commands
Aliases: No aliases yet
Quick peek
Open full term page
DevOps
premium
Canary deployment
Canary deployment is a release approach that sends a small portion of real traffic to a new version before rolling it out broadly.
Deployment workflows
intermediate
5 commands
Aliases: No aliases yet
Quick peek
Open full term page
Management and Governance
premium
Deployment scope
Microsoft Learn describes Azure Resource Manager and Bicep deployments as running at a specific scope: resource group, subscription, management group, or tenant. The selected scope determines which resources can be declared directly, where deployment history is recorded, and what permissions the deployment principal needs.
ARM deployments
fundamentals
5 commands
Aliases: ARM deployment scope, Bicep targetScope, deployment boundary
Quick peek
Open full term page
DevOps
premium
Infrastructure deployment script
Infrastructure deployment script controls how deployment teams run imperative setup, validation, or bridge logic inside an otherwise declarative Azure infrastructure deployment. Teams see it in bicep files, arm templates. It is not a local shell script, a DevOps pipeline task, a custom script extension, or normal template declarative resource creation; confusing them can create hung deployments, leaked script output. Use the term when reviewing access, monitoring, cost, recovery, or performance. It keeps architects, operators, security reviewers, and support teams focused on the same setting, resource, or behavior.
Infrastructure as Code
Intermediate
5 commands
Aliases: deployment script, ARM deployment script, Bicep deployment script, deploymentScripts resource, scripted IaC step
Quick peek
Open full term page
Analytics
premium
Kusto database
Kusto database is a logical container inside an Azure Data Explorer cluster that holds tables, functions, policies, permissions, and ingestion/query configuration.
Azure Data Explorer database
Intermediate
5 commands
Aliases: ADX database, Azure Data Explorer database, Kusto DB
Quick peek
Open full term page
Analytics
premium
Kusto follower database
Kusto follower database is a read-only database attached from another Azure Data Explorer cluster so consumers can query leader data without copying it.
Azure Data Explorer data sharing
Advanced
5 commands
Aliases: ADX follower database, Azure Data Explorer follower database, followed database
Quick peek
Open full term page
Web
premium
Local Git deployment
Microsoft Learn describes Local Git deployment for App Service as a method for deploying code from a Git repository on a local computer to an app-hosted Git endpoint. It requires deployment credentials and Source Control Manager basic authentication. Operators should review it with the connected Azure resource settings.
App Service
intermediate
5 commands
Aliases: No aliases yet
Quick peek
Open full term page
Databases
premium
PostgreSQL database
A named PostgreSQL catalog inside a flexible server that holds schemas, tables, extensions, permissions, and application data.
Azure Database for PostgreSQL
fundamentals
5 commands
Aliases: PostgreSQL database, postgresql database, Azure Database for PostgreSQL database, database catalog, schema migration, charset, collation
Quick peek
Open full term page
Web
premium
Serverless API deployment
Serverless API deployment in Azure commonly means publishing HTTP-triggered Azure Functions, often with zip deployment, run-from-package, Static Web Apps APIs, or API Management integration. The deployment packages code, configuration, identity, routing, and monitoring so an API endpoint can scale without dedicated server management.
Azure Functions
intermediate
5 commands
Aliases: serverless API release, Azure Functions API deployment, HTTP trigger deployment, function API deployment
Quick peek
Open full term page
Databases
premium
Serverless SQL database
A serverless SQL database is an Azure SQL Database single database configured with the serverless compute model. It automatically scales compute within configured limits, can auto-pause in supported tiers, resumes on activity, and keeps the managed SQL Database platform features such as backups, patching, monitoring, and security.
Azure SQL Database
fundamentals
5 commands
Aliases: No aliases yet
Quick peek
Open full term page
Management and Governance
premium
Complete deployment mode
Complete mode is the dangerous deployment mode. At resource-group scope, it can delete resources that are not in the template. It is useful only when you truly want the template to define the full state, and it needs careful review before production use.
ARM deployments
intermediate
4 commands
Aliases: No aliases yet
Quick peek
Open full term page
Databases
premium
Cosmos DB database
An Azure Cosmos DB database is a unit of management for one or more containers within an account and acts as a namespace for child resources.
Cosmos DB
fundamentals
4 commands
Aliases: No aliases yet
Quick peek
Open full term page
Databases
premium
Database compatibility level
A SQL database setting that controls engine behaviors and query-processing compatibility so applications can move versions without every feature changing at once.
Azure SQL
fundamentals
4 commands
Aliases: compatibility level, SQL compatibility level, Azure SQL compatibility level
Quick peek
Open full term page
Monitoring and Observability
premium
Database diagnostic settings
Azure Monitor routing rules that export database logs and metrics to Log Analytics, Storage, Event Hubs, or partner destinations for investigation and governance.
Azure Monitor
intermediate
4 commands
Aliases: SQL diagnostic settings, database diagnostics export, Azure Monitor diagnostic settings for databases
Quick peek
Open full term page
Databases
premium
Database server / account
The Azure resource boundary that owns database instances, authentication, networking, regional placement, and service-wide settings for a database workload.
Database platform
intermediate
4 commands
Aliases: database account, database server, database resource account, logical database server
Quick peek
Open full term page
AI and Machine Learning
premium
Deployment capacity
Deployment capacity is the throughput allocation configured for an Azure OpenAI or Foundry model deployment, affecting available request volume, quota use, latency, and cost.
Azure OpenAI
intermediate
4 commands
Aliases: Azure OpenAI deployment capacity, model deployment capacity, deployment throughput capacity, PTU deployment capacity
Quick peek
Open full term page
Web
premium
Deployment Center
Deployment Center is the Azure portal experience for configuring and reviewing App Service deployment sources, such as GitHub, Azure Repos, Bitbucket, local Git, and supported build providers.
Deployment
fundamentals
4 commands
Aliases: App Service Deployment Center, Azure Deployment Center, deployment center in App Service, continuous deployment center
Quick peek
Open full term page
Management and Governance
premium
Deployment correlation ID
A deployment correlation ID is the GUID recorded for an Azure Resource Manager deployment and related control-plane operations so teams can trace events, failures, and support evidence across logs.
ARM deployments
fundamentals
4 commands
Aliases: ARM deployment correlation ID, correlationId for deployment, deployment tracking GUID, Azure deployment correlationId
Quick peek
Open full term page
Management and Governance
premium
Deployment history
Deployment history is the Azure Resource Manager record of template, Bicep, and deployment operations at a scope, used to review past deployments, outputs, errors, and resources affected.
Azure Resource Manager
fundamentals
4 commands
Aliases: ARM deployment history, Azure deployment history, resource group deployment history, template deployment history
Quick peek
Open full term page
Management and Governance
premium
Deployment history record
A deployment history record is one named Azure Resource Manager deployment entry that captures status, parameters, outputs, correlation ID, timestamps, and operations for a specific deployment run.
ARM deployments
fundamentals
4 commands
Aliases: deployment record, ARM deployment record, Azure deployment record, template deployment record
Quick peek
Open full term page
Management and Governance
premium
Deployment name
A deployment name is the label Azure uses for one ARM or Bicep rollout. It is not the resource name. It helps you find the right deployment history, check status, inspect failed operations, and connect automation logs to the change that actually ran.
ARM deployments
fundamentals
4 commands
Aliases: No aliases yet
Quick peek
Open full term page
Management and Governance
premium
Deployment output
A deployment output is what your template hands back after it runs. Instead of hunting for a generated hostname, ID, endpoint, or principal ID, you define an output and let automation read the value directly from the deployment result.
ARM deployments
fundamentals
4 commands
Aliases: No aliases yet
Quick peek
Open full term page
Management and Governance
premium
Deployment parameter
A deployment parameter is a value you pass into a template at run time. It keeps the template reusable by letting dev, test, and production use different names, regions, sizes, or settings without rewriting the infrastructure code.
ARM deployments
fundamentals
4 commands
Aliases: No aliases yet
Quick peek
Open full term page
Management and Governance
premium
Deployment script
A deployment script is a Microsoft.Resources/deploymentScripts resource that runs Azure CLI or Azure PowerShell during an ARM or Bicep deployment to perform controlled custom actions and return outputs.
ARM deployments
intermediate
4 commands
Aliases: ARM deployment script, Microsoft.Resources/deploymentScripts, Bicep deployment script, template deployment script
Quick peek
Open full term page
Management and Governance
premium
Deployment stack
A deployment stack is an Azure Resource Manager resource that manages a group of resources deployed from a Bicep or ARM template, including lifecycle tracking, unmanaged-resource handling, and optional deny settings.
Infrastructure as code
intermediate
4 commands
Aliases: Azure deployment stack, Bicep deployment stack, Microsoft.Resources/deploymentStacks, ARM deployment stack
Quick peek
Open full term page
Management and Governance
premium
Deployment stack action on unmanage
Deployment stack action on unmanage is the setting that defines what Azure does with resources that are no longer managed after a deployment stack is updated or deleted, such as detaching or deleting them.
ARM deployments
intermediate
4 commands
Aliases: actionOnUnmanage, deployment stack unmanage action, stack unmanaged resource action, deployment stack cleanup behavior
Quick peek
Open full term page
Management and Governance
premium
Deployment stack deny settings
Deployment stack deny settings define how stack-managed resources are protected from unauthorized control-plane operations, including deny modes, excluded actions, excluded principals, and child-scope behavior.
ARM deployments
advanced
4 commands
Aliases: deploymentStacks denySettings, stack deny settings, deployment stack deny assignments, deny settings mode
Quick peek
Open full term page
AI and Machine Learning
premium
Deployment type
Deployment type is the Azure AI or Microsoft Foundry model hosting option, such as standard, global, data-zone, regional, batch, serverless, or provisioned deployment, that determines availability, data processing location, capacity model, cost, and operational behavior.
Microsoft Foundry
intermediate
4 commands
Aliases: Microsoft Foundry deployment type, Azure AI deployment type, model deployment type, Foundry Models deployment type
Quick peek
Open full term page
Management and Governance
premium
Deployment variable
A deployment variable is a named value or expression in an ARM template or Bicep file used to simplify resource definitions, construct repeatable names, reuse calculated values, and reduce duplication during deployment.
ARM deployments
fundamentals
4 commands
Aliases: ARM template variable, Bicep variable, template variable, infrastructure variable
Quick peek
Open full term page
Web
premium
FTP deployment
FTP deployment is an Azure App Service deployment method where application files are uploaded to a web app through FTP or FTPS publishing endpoints. Teams use it to support simple or legacy file-based releases when a full CI/CD pipeline, container image, or ZIP deployment flow is not available. In daily Azure work, it shows up when engineers publish static content, migrate an older web app, recover a small site, rotate deployment credentials, or disable basic publishing after modernization. It is not source control, a build pipeline, a secure secret-management strategy, or the preferred deployment method for regulated production systems.
App Service deployment
intermediate
4 commands
Aliases: FTPS deployment, App Service FTP deployment, FTP/S deployment
Quick peek
Open full term page
DevOps
premium
GitHub Actions deployment
GitHub Actions deployment is a repository workflow that publishes application code, containers, or infrastructure changes to Azure after selected GitHub events such as push, pull request, or release. Teams use it to standardize builds, approvals, tests, packaging, and deployment to Azure services without relying on manual portal changes. In daily Azure work, it shows up when engineers configure App Service Deployment Center, deploy to a slot, use azure/login, run Bicep deployments, or troubleshoot a failed workflow run.
Deployment workflows
intermediate
4 commands
Aliases: GitHub Actions deploy, GitHub Actions CI/CD deployment, GitHub workflow deployment
Quick peek
Open full term page
Databases
premium
Hyperscale database
Hyperscale database is an individual Azure SQL Database configured to use the Hyperscale service tier and its scalable storage and compute architecture.
Azure SQL
intermediate
4 commands
Aliases: Azure SQL Hyperscale database, hyperscale database, Hyperscale database, Hyperscale SQL database
Quick peek
Open full term page
Management and Governance
premium
Idempotent deployment
An idempotent deployment should be safe to run again. If the desired state has not changed, rerunning the Bicep or ARM deployment should not create duplicate resources or surprise changes; it should confirm or update Azure toward the same intended configuration.
ARM deployments
fundamentals
4 commands
Aliases: No aliases yet
Quick peek
Open full term page
Management and Governance
premium
Incremental deployment mode
Incremental mode is the normal ARM deployment behavior. It creates or updates what the template declares, but it does not delete unrelated resources just because they are missing from the template. That makes it safer than complete mode for most ongoing deployments.
ARM deployments
fundamentals
4 commands
Aliases: No aliases yet
Quick peek
Open full term page
AI and Machine Learning
premium
Model deployment
Model deployment is the step where a trained or selected model becomes something an application can actually call. The model may have performed well in experiments, but deployment decides how it is hosted, secured, scaled, monitored, and routed.
Generative AI
fundamentals
4 commands
Aliases: No aliases yet
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