App Service Builder · Private Preview

From code to a running app.

Describe your app, build a version, and deploy it. Build and manage web apps through the Portal, Builder CLI, or Azure Resource Manager.

Portal quickstartCLI quickstartGet samplesOpen portal

Development and test only

Do not deploy production workloads on App Service Builder Private Preview. Preview has no financially backed SLA; features and availability may change or be discontinued. Review the preview guidance and Azure Preview terms before use. Use the access details supplied by your preview contact.

Check feature availability and preview plans before choosing a workflow.

What Builder does

App Service Builder builds your application from GitHub source or an uploaded ZIP and hosts its static files or HTTP process at a service-provided URL. You describe the app in builder.yaml; Builder produces a version, and a successful deployment makes that version serve traffic.

• Build from source: connect a GitHub repository or upload a ZIP containing your code and builder.yaml.
• Host your app: publish static browser assets or run a supported HTTP application.
• Keep versions: capture source and configuration in each build, then deploy eligible retained versions again.
• Configure and diagnose: manage application variables and inspect build/deployment logs.
• Choose your client: use Portal, Builder CLI, or ARM API; ARM and Bicep infrastructure templates can provision the resource.

GitHub or managed Microsoft Entra work-account sign-in, autoscaling on CPU or memory utilization, and managed identity for Azure access are available for development/test apps. Sign-in requires a configured provider application. HTTP scaling and scale to zero are per-component opt-ins. Feature status separates those boundaries from current capabilities. Start with Portal or Builder CLI for a complete first-app journey using the same recommended sample. Language tutorials explain runtime-specific build and startup choices when you need them. Use your own GitHub repository or start from a Portal template. If you already forked a sample, select Use my repository to keep working with it.

What you can build

• Static websites. Publish HTML, CSS, and browser assets directly, or build a frontend with a supported toolchain.
• Web applications. Run an HTTP application built with Node.js, Python, .NET, or PHP.
• HTTP APIs. Serve request-driven endpoints with runtime startup, a listening port, and a health check.
• Frontend plus backend. Combine a generic static frontend and HTTP backend in one app. Next.js is not ready as a complete framework workflow.
• Sign-in protected tools. Protect visitors with GitHub or managed Microsoft Entra work-account sign-in and configure who can access the app.
• Azure-connected apps. Call Azure and external services from your app.

Anatomy of a Builder app

Choose how to manage your app. Your source and manifest define what is built; a deployment makes that version active.

Manage the same app with

• Portal

  Connect and deploy visually.

• Builder CLI

  Work from your terminal.

• ARM/API

  Manage the Azure resource.

• GitHub Copilot app canvas

  Prepare and manage your app alongside Copilot chat.

One Builder app

1. 01 / DescribeApplication source

   Your code and builder.yaml define the app.

2. 02 / BuildAvailable version

   A build captures your code and configuration in a version.

   • Static assets · optional
   • Web process · optional
3. 03 / DeployActive deployment

   A successful deployment makes that version serve traffic.

4. 04 / ServePublic app URL

   Visitors reach the active app. Verify the expected HTTP response.

Host static files, an HTTP application, or both — at most one of each. Wait for deployment success, then check your app URL.

Building blocks

• GitHub source. An authorized repository, reference, and source root provide the code for your app.
• App manifest. builder.yaml describes component builds, outputs, public paths, startup, and health checks.
• Built versions. Retained, available versions can be deployed again without rebuilding the same version.
• Deployments. Track a request through activation and completion, independently of build readiness.
• Variables. App configuration is captured per version for build and web-process use.
• App authentication. Protect visitors with managed Microsoft Entra sign-in; review provider-specific limitations.
• Managed identity. Assign system-assigned or user-assigned identities so your app can call Azure services without stored credentials.
• Scaling policy. Scale using CPU, memory, or HTTP demand. Opt into scale to zero for suitable apps.
• Supported scope. Check app limits, quotas, and preview limitations before choosing a design.
• Networking. Understand public routes, outbound connections, and private-network boundaries.
• Diagnostics. Find build and deployment logs and plan application-owned monitoring.
• External services. Connect to Azure and external services with explicit permissions and reachable endpoints.

Choose your next step

• Start with PortalDeploy the recommended HTTP sample visually, or keep another sample you have chosen.
• Start with Builder CLIDeploy the same sample from your terminal, verify it, and clean up.
• Explore language tutorialsUnderstand Node.js, Python, .NET, PHP, or static-site build and startup settings.
• Prepare for previewUnderstand access, management sign-in, and source authorization.
• Manage deploymentsDeploy new source, track completion, or activate an eligible earlier version.
• Provision with ARM or BicepUse infrastructure templates to create the resource, then deploy your code.
• Find a sampleChoose an app shape and language, then fork its Azure-Samples repository.
• Agent skillsInstall the Builder plugin in Copilot CLI for agent-assisted preparation and deployment. Preview access and Builder CLI are separate prerequisites.
• Describe your appSet up builder.yaml for static content, a web process, or both.
• Protect visitor accessSet up managed Microsoft Entra work-account sign-in and test your access rules.
• Compare Azure platformsUnderstand when to choose Builder, App Service, Container Apps, or another service.
• GitHub Copilot app canvasPrepare and deploy an app alongside Copilot chat.
• Host an MCP serverDeploy your own stateless HTTP tool endpoint as an app, with a sample and target-verification checklist.
• Host an AI agent APIExplore a bounded agent-backed HTTP app that calls a separately configured model service.