Search Azure terms

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

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

DevOps premium Blue-green deployment Blue-green deployment is a release strategy that runs two production-capable environments, routes users to the current version, validates the new version, then shifts traffic with minimal downtime. Deployment workflows intermediate 3 commands Aliases: No aliases yet Quick peek Open full term page

DevOps premium Container image build the build step that turns source, Dockerfile instructions, dependencies, and metadata into a container image stored in a registry Deployment workflows intermediate 5 commands Aliases: No aliases yet Quick peek Open full term page

DevOps premium Image promotion Image promotion is the controlled process of moving an approved VM or container image version from build or test use into wider production use. Deployment workflows intermediate 5 commands Aliases: Image promotion, image promotion, image-promotion Quick peek Open full term page

DevOps template-specs-upgraded Rolling upgrade AKS node-pool upgrade pattern that drains and replaces nodes in controlled batches to protect workload availability. Deployment workflows intermediate 6 commands Aliases: AKS rolling upgrade, node pool rolling upgrade, rolling node upgrade, AKS node pool upgrade, Kubernetes rolling upgrade 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

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

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

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

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

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

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 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

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

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

Management and Governance premium Deployment error A deployment error is Azure telling you that an infrastructure change did not validate or did not complete. It can happen before resources are created, while a provider is processing a request, or after a nested operation fails. Microsoft Learn anchors this term in Troubleshoot common Azure deployment errors, but this field-manual definition is intentionally wider than an older short glossary entry because the page must teach what to inspect, what can break, who owns the decision, and which evidence proves the Azure environment is behaving as intended. In field. ARM deployments fundamentals 3 commands Aliases: No aliases yet Quick peek Open full term page

AI and Machine Learning verified Online deployment An online deployment is the Azure Machine Learning serving configuration behind an online endpoint. It defines the model, scoring code, environment, instance type, instance count, and request settings used for real-time inference, while the endpoint controls authentication, scoring URI, traffic routing, and invocation. Azure Machine Learning intermediate 6 commands Aliases: Azure ML online deployment, managed online deployment, blue deployment, green deployment, online deployment, model-serving deployment Quick peek Open full term page

AI and Machine Learning verified OpenAI deployment name An OpenAI deployment name is the customer-chosen name assigned to an Azure OpenAI or Foundry model deployment. Applications use that name, not necessarily the base model name, to route inference requests to the deployed model, quota, version, and deployment type. Azure OpenAI intermediate 6 commands Aliases: Azure OpenAI deployment name, model deployment name, deployment_name, Azure OpenAI model parameter, OpenAI deployment name, deploymentName, deployments route Quick peek Open full term page

AI and Machine Learning field-manual-complete Azure OpenAI deployment An Azure OpenAI deployment is the practical handle your application uses when it calls a model. The resource may offer several models, but code usually sends requests to a deployment name such as summarizer-prod or support-gpt4o. That deployment records which model and. Azure OpenAI fundamentals 5 commands Aliases: No aliases yet Quick peek Open full term page

Web field-manual-complete Deployment slot Microsoft Learn describes App Service deployment slots as live apps with their own host names. You can deploy a web app, API app, mobile backend, or Linux web app to a nonproduction slot, validate it, then swap content and configuration with production. App Service intermediate 5 commands Aliases: App Service deployment slot, Azure App Service slot, Deployment slot, always-on, app-service, app-service-app-setting, app-service-logs, app-service-plan, container-apps-revision, deployment slot, deployment-slot, deployment-slot-swap, github-actions-deployment, production-slot, slot-setting, staging slot, staging-slot, web app slot Quick peek Open full term page

Web field-manual-complete Deployment slot swap A deployment slot swap is the App Service release move that trades the roles of two slots, usually staging and production. Instead of deploying directly over the live app, teams deploy to a staging slot, test it, warm it up, and then swap it into production. The old production version remains in the other slot. App Service intermediate 5 commands Aliases: App Service slot swap, swap deployment slots, staging to production swap, Azure slot promotion Quick peek Open full term page

Management and Governance verified Resource group deployment A resource group deployment runs an ARM template or Bicep file at one resource group scope so the resources in that workload boundary are created or updated together. ARM deployments intermediate 5 commands Aliases: ARM resource group deployment, deployment group, az deployment group, Bicep resource group deployment, resource group scope deployment Quick peek Open full term page

Management and Governance field-manual-complete Subscription deployment A subscription deployment is an ARM or Bicep deployment that targets an Azure subscription instead of one resource group. It is useful when the thing you are creating or assigning lives at subscription scope, such as resource groups, policy assignments, role assignments, budgets, deployment stacks, or shared governance settings. The deployment still stores metadata in a region, but the resources it affects can organize the entire subscription. It is a common building block for landing zones, subscription vending, and consistent environment setup. It is a platform move, not a workload-only deployment. ARM deployments intermediate 5 commands Aliases: ARM subscription deployment, Bicep subscription scope, subscription-scope deployment, az deployment sub Quick peek Open full term page

Web complete Static Web Apps deployment token A secret used by deployment tooling to publish content to an Azure Static Web Apps resource. Static Web Apps intermediate 5 commands Aliases: static-web-apps-deployment-token, Static Web Apps deployment token, SWA deployment token, Static Web App deployment secret, staticwebapp api key, SWA_CLI_DEPLOYMENT_TOKEN Quick peek Open full term page

Management and Governance top-250-pre130-priority-upgraded Deployment operation A deployment operation is the step-by-step evidence inside a deployment. When a template fails, the deployment name tells you which rollout to inspect, and the operations show which resource action succeeded, failed, or returned the error you need to fix. ARM deployments intermediate 4 commands Aliases: No aliases yet Quick peek Open full term page

AI and Machine Learning premium field-manual Managed online deployment A managed online deployment is a named deployment behind a managed online endpoint that hosts a model or scoring application for real-time inference. Teams use it when an ML team needs controlled model rollout, traffic shifting, and observable inference behavior. In plain English, it gives operators a named control for safe model release, version isolation, traffic control, and measurable serving health 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 Machine Learning intermediate 4 commands Aliases: Managed online deployment, Azure Machine Learning, managed online endpoint, batch endpoint, model deployment, online deployment, Azure ML managed deployment, Azure Machine Learning managed online endpoints Quick peek Open full term page

Management and Governance premium field-manual Management group deployment A management group deployment is an ARM or Bicep deployment executed at management-group scope instead of subscription or resource-group scope. Teams use it when platform teams need to deploy governance resources across a management group hierarchy. In plain English, it gives operators a named control for repeatable policy, role, and subscription-level governance from the correct Azure scope 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. ARM deployments intermediate 4 commands Aliases: Management group deployment, Azure Resource Manager, ARM deployments, ARM and Bicep governance deployments, subscription deployment, resource group deployment, tenant deployment, Azure Resource Manager and Bicep, ARM management group deployment, Bicep management group deployment Quick peek Open full term page

AI and Machine Learning field-manual-ready ML managed online deployment An ML managed online deployment hosts one model version, scoring runtime, and compute configuration behind an Azure Machine Learning online endpoint. Azure Machine Learning intermediate 4 commands Aliases: AML managed online deployment, managed inference deployment, online deployment Quick peek Open full term page

AI and Machine Learning field-manual-ready Model deployment type Model deployment type describes the hosting, traffic, region, and billing pattern used when a model is made available for inference. AI platform and search intermediate 4 commands Aliases: No aliases yet Quick peek Open full term page

AI and Machine Learning learning-path-anchor Text to speech Text to speech in Azure AI Speech converts written text or SSML into synthesized audio using neural voices, custom voice options, language support, and APIs. Teams use it to add spoken responses to apps, contact centers, accessibility tools, devices, and media workflows while governing region, keys, networking, and quota. Azure AI services fundamentals 4 commands Aliases: Text to speech, text to speech, Azure Text to speech, Microsoft Learn Text to speech, TTS, speech synthesis, Azure AI Speech synthesis, neural voices, SSML speech Quick peek Open full term page

AI and Machine Learning premium Computer Vision the Azure AI capability that helps applications understand images, read text, detect visual features, and return structured insights from pictures or screenshots Azure AI services fundamentals 12 commands Aliases: No aliases yet Quick peek Open full term page