Access Builder apps through private inbound endpoints
Plan private inbound access to Builder apps through customer private endpoints and a Private Link experience.
Start typing to find articles and roadmap items.
Arrow keys select a result. Enter opens it. Escape dismisses results.
Explore the direction of App Service Builder. Open a feature to discuss what would help your team.
Availability is independent of work status: Not yet availablePrivate previewPublic previewGA
Plan private inbound access to Builder apps through customer private endpoints and a Private Link experience.
Broaden Builder resource-management audit coverage beyond current sampled Azure Activity Log events.
Plan an Application Insights integration to help customers investigate application behavior and failures.
Plan outbound VNet integration so a Builder app can reach dependencies in a customer-owned virtual network.
Plan one portal experience to create a supported external resource and connect a Builder app.
Plan custom pages for agreed app error conditions.
Investigate whether Builder should provide a first-party integration with Azure Key Vault for application secrets.
Organize separate, isolated persistent Builder apps under a common app or repository view with clear environment labels and configuration.
Plan multi-region resilience for Builder apps.
Address reported accessibility barriers in selected Builder UI journeys.
Plan supported security posture and protection integration for Builder apps through Microsoft Defender for Cloud.
Plan a native application storage solution intended to retain data beyond an individual running app process.
Plan a Builder stack-management experience.
Migrate Builder integration into native built-in Azure CLI commands as a later step after the initial extension.
Plan tooling to assess an existing Azure Static Web Apps app and help move supported app code and configuration to Builder.
Use runtime and HTTP request metrics to understand how your app is operating, rather than relying only on log messages.
Plan hosted functions associated with a Builder app, similar in customer experience to managed functions in Azure Static Web Apps.
Plan Builder app support for cloud environments isolated from public networks.
Plan Builder app support in sovereign cloud environments.
Connect and deploy repositories using GitHub accounts managed by your organization.
Plan resilience across availability zones for Builder apps.
Give your app an address on a domain you own instead of using only its Builder-generated hostname.
No items in this column.
Plan named nonsecret settings for existing Azure Blob Storage, Foundry, and PostgreSQL services in Builder configuration.
Simplify app setup with a planned PostgreSQL database primitive in Builder configuration.
Study how Builder usage should be billed, then use the outcome to guide billing implementation.
Establish how apps receive sensitive settings, such as service credentials, separately from ordinary environment variables.
Build and deploy your app through a first-class GitHub Actions workflow as an alternative to installing the Builder GitHub App.
Qualify a supported Next.js App Router standalone workflow; bounded hosted routes, assets, and retained-version operations work, but Server Actions remain unresolved.
Try proposed app changes in a temporary environment for a pull request targeting an existing Builder app's tracked branch.
Qualify additional Azure regions for Builder app deployment.
Qualify Azure Policy integration beyond current generic required-tag resource enforcement.
Establish a supported integration between Builder-hosted apps and RayFin.
Provision and update Builder app resource configuration with ARM JSON or JSON emitted by Bicep.
Add Builder-specific Azure PowerShell commands for app management and automation.
Give coding agents read-only search and reading access to public Builder documentation through the Model Context Protocol.
Simplify first deployment by helping configure an app without requiring you to write its Builder configuration file from scratch.
Build an inventory of built-in Azure Policy definitions that organizations can select and assign for Builder app governance.
Manage Builder apps through an Azure CLI extension as the initial Azure CLI delivery.
Develop a Visual Studio Code extension for working with Builder apps from the editor.
No items in this column.
Use a dedicated Builder command-line tool to manage apps from a terminal or script.
Completed
Use the Copilot app canvas for assisted setup, configuration review, deployment monitoring, and failure recovery.
Completed
Restore a previous app version and keep the last working version serving when an update fails.
Completed
Explicitly opt an image-backed app into sleeping when idle and waking on the next HTTP request.
Completed
Let visitors authenticate to your deployed app with Microsoft Entra ID through built-in application authentication.
Completed
Let visitors authenticate to your deployed app with GitHub through built-in application authentication.
Completed
Scale a web app with HTTP traffic while keeping a positive minimum of instances running.
Completed
Use an Azure-managed identity for app access to supported Azure services instead of distributing service credentials.
Completed
Start from a sample in the Portal and fork its repository inline during app creation.
Completed
Send an app's stdout and stderr to customer-owned Azure monitoring resources through ARM configuration.
Completed
Upload and deploy local application source without connecting a GitHub repository.
Completed
Host HTTP endpoints that a frontend or another application calls to read data or perform an action.
Completed
Read build output and follow deployment progress to see where a release succeeds or fails.
Completed
Use a browser to connect a repository, configure access, deploy an app, inspect its status, change configuration, and delete it.
Completed
Adjust app capacity automatically in response to CPU and memory utilization.
Completed
See your app's previous deployments and their outcomes when investigating a change or failure.
Completed
Deploy a website and its backend API as components of one Builder application, with requests routed to each component.
Completed
Connect a GitHub repository so Builder can fetch your source code, build it, and deploy your app.
Completed
Build and host a website made of HTML, CSS, JavaScript, and other files, such as a blog or documentation site.
Completed
Run an application server that handles incoming requests and generates responses, such as a Node.js web app.
Completed
Customize the visitor-facing stopped-app experience in Public preview.
Use supported Azure managed connectors through Builder Connections with separately configured connection resources and identity access.
Inspect runtime-log snapshots or follow a selected replica in the CLI, and stream app logs in the Portal, separately from Log Analytics export.
No items in this column.
Roadmap #24
Use an Azure-managed identity for app access to supported Azure services instead of distributing service credentials.
Assign a system-assigned identity, user-assigned identities, or both during the Portal Access step at app creation, on the Identity page, or through ARM. The Portal can create a user-assigned identity during identity setup. User-assigned-only app identity is supported; a system-assigned companion is not required for app code to authenticate. Portal Save and deploy applies the assignment to the running app when deployment succeeds. An identity-only update can redeploy retained build output without rebuilding source; without usable retained output a first deployment is still required. Select a user-assigned identity for Azure SDK credentials with AZURE_CLIENT_ID; Builder sets that variable only when you select it. Changing app variables requests a new source build rather than an identity-only redeployment. Customers must grant the destination's roles or data permissions and meet its firewall and network requirements. This is separate from visitor sign-in and does not qualify every runtime, credential path, service, or tenant combination; verify app-code access. Runtime log export selects its ingestion identity separately.
System-assigned, user-assigned, combined, and user-assigned-only app identity scope, creation setup, retained-output redeployment, and private-preview availability reconfirmed during the roadmap review on November 4, 2026. The completion date retains the October 31 confirmation of the initial supported implementation, not its original release date or general availability. This does not establish universal runtime-identity qualification. Preview access is for development and test workloads, not production.
Completed .
Public documentation and access information
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Roadmap #47
Plan private inbound access to Builder apps through customer private endpoints and a Private Link experience.
This planned feature aims to let customers reach a Builder app privately through a customer private endpoint and Private Link experience. Endpoint placement, connection approval, DNS, public-access controls, regional availability, and limits remain undefined. This is inbound access to the app, not outbound VNet integration or private access to Builder management endpoints. It does not promise automatic outbound integration or destination connectivity. No SKU, pricing, or support guarantee has been selected; private inbound endpoints for Builder apps are not available today.
Customer-facing private inbound endpoint goal, backlog status, and not-yet-available access confirmed during the roadmap review on November 4, 2026. Work has not started; delivery requires a supported customer private-access capability, not investigation alone. No public delivery date or release commitment is approved.
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #17
Let visitors authenticate to your deployed app with GitHub through built-in application authentication.
Supported apps can use Builder's managed GitHub provider or your own GitHub OAuth application. Configure visitor authentication in the Portal Access step before the first deployment, or later on the Authentication page. Creation access setup can be skipped and configured later; this does not assert required sign-in by default for every new app. The Authentication page brings provider setup, optional or required sign-in, access rules, Save, and Test sign-in together. A customer-owned provider requires its callback URL, client ID, and client secret. An empty access-rule list allows every account accepted by that provider application. This concerns app visitors, not your login to the Builder Portal or GitHub source authorization, and does not qualify every account or app combination.
The supported GitHub provider scope in shared built-in application authentication and private-preview availability reconfirmed during the roadmap review on November 4, 2026. The completion date retains the October 31 confirmation of the initial supported implementation, not its original release date or general availability. Preview access is for development and test workloads, not production.
Completed .
Public documentation and access information
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #18
Let visitors authenticate to your deployed app with Microsoft Entra ID through built-in application authentication.
Supported apps can use Builder's managed Microsoft Entra provider or your own app registration. The Portal Access step offers a Microsoft tenant sign-in preset before the first deployment; review the selected tenant and identity rules before applying it. Creation access setup can be skipped and configured later; this does not assert required sign-in by default for every new app. The Authentication page brings provider setup, optional or required sign-in, access rules, Save, and Test sign-in together. Your own registration requires an attached user-assigned managed identity in the same organizational tenant, a redirect URI, and a federated credential. An empty access-rule list allows every account accepted by that provider application. This concerns app visitors, not Builder Portal login or source authorization, and does not qualify every tenant, account type, or app combination.
The supported Microsoft Entra provider scope in shared built-in application authentication and private-preview availability reconfirmed during the roadmap review on November 4, 2026. The completion date retains the October 31 confirmation of the initial supported implementation, not its original release date or general availability. Preview access is for development and test workloads, not production.
Completed .
Public documentation and access information
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #35
Broaden Builder resource-management audit coverage beyond current sampled Azure Activity Log events.
Azure Activity Log already records sampled Builder ARM resource create, update, delete, and policy-denial events. Inspect operation names and statuses at the app resource or subscription scope, allowing for delayed arrival, and verify the events you need before relying on them as an audit control. These control-plane changes are separate from application stdout/stderr, runtime log export, and live Portal log streaming. Management events do not prove a healthy deployment or serving endpoint and are not a complete history of source builds, internal activation steps, or application requests. Comprehensive audit and lifecycle coverage remain under definition and qualification; the broader audit experience is not yet available.
Broader audit goal, backlog status, and not-yet-available comprehensive coverage reconfirmed during the roadmap review on November 4, 2026. Current sampled management events are a limited documented capability, not completion of the broader audit and lifecycle experience. No public delivery date or release commitment is approved.
Public documentation and access information
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #19
Adjust app capacity automatically in response to CPU and memory utilization.
Autoscaling adjusts the capacity running your app as resource usage changes, rather than requiring a manual adjustment each time. This item covers CPU and memory utilization as the scaling signals. Scaling limits and policies still need qualification. It does not include request-based burst scaling, and reducing capacity all the way to zero is covered separately.
Scope, completion, and private-preview availability confirmed during the roadmap review on October 12, 2026. The date records that confirmation, not the original release date.
Completed .
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #29
Scale a web app with HTTP traffic while keeping a positive minimum of instances running.
Enable HTTP traffic as a scaling signal in Portal Scaling or a compatible Builder CLI, with a positive minimum and a maximum greater than that minimum. HTTP-demand scaling works independently of CPU and memory targets and does not require scale-to-zero or sleeping; the signals can also be combined. The service manages the HTTP target, currently defaulting to 100 requests/sec, with no customer request-rate setting. That target is not a traffic quota or capacity guarantee. App and subscription limits can constrain scale-out. Use the separate zero-minimum policy only if the app is suitable for idle sleeping and request-triggered waking.
Supported positive-minimum HTTP autoscaling and private-preview availability confirmed during the roadmap review on October 31, 2026. The date records confirmation of the initial supported implementation, not its original release date or a capacity commitment. Preview access is for development and test workloads, not production.
Completed .
Public documentation and access information
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #22
Plan named nonsecret settings for existing Azure Blob Storage, Foundry, and PostgreSQL services in Builder configuration.
The intended scope is named nonsecret connection settings for Azure Blob Storage, Foundry, and PostgreSQL, captured in versioned configuration and mapped to app environment variables, with optional managed-identity selection. This is planned work under qualification, not an available customer workflow. Portal wizard and CLI experiences, automatic permission grants, and secure credential handling are not delivered by this item. Customers still own the destination service, permissions, and network reachability. This does not mean Builder provisions or operates a built-in database, cache, or storage service, or supplies credentials through a managed secret store.
Intended named, nonsecret connection scope, in-progress status, and not-yet-available access reconfirmed during the roadmap review on November 4, 2026. Work remains under qualification without verified customer availability; configuration mapping and optional identity selection do not establish a shipped wizard, CLI workflow, automatic grants, or secure credential service. No public delivery date or release commitment is approved.
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #38
Plan an Application Insights integration to help customers investigate application behavior and failures.
This planned work aims to connect supported Builder app telemetry and diagnostics to Azure Application Insights. Configuration, supported application stacks, collected data, identity requirements, and charges remain to be defined. It is separate from runtime log export, live Portal log streaming, and app resource metrics. No automatic instrumentation or shipped customer integration is implied; this integration is not available today.
Customer-facing telemetry and diagnostics integration scope, backlog status, and not-yet-available access confirmed during the roadmap review on November 1, 2026. Work has not started; no public delivery date or release commitment is approved.
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #46
Plan outbound VNet integration so a Builder app can reach dependencies in a customer-owned virtual network.
This planned feature aims to connect a Builder app outbound to dependencies in a customer-owned virtual network. Subnet selection, the integration model, DNS, routes, egress permissions, regional availability, and limits remain undefined. Networking inside the Builder service does not establish a customer-configurable VNet integration. This is separate from private inbound access to the app and does not promise that private endpoints, private DNS, or destination permissions are configured automatically. No SKU, pricing, or support guarantee has been selected; outbound VNet integration is not available today.
Customer-facing outbound VNet integration goal, backlog status, and not-yet-available access confirmed during the roadmap review on November 4, 2026. Work has not started; delivery requires a supported customer connectivity capability, not investigation alone. No public delivery date or release commitment is approved.
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #59
Plan one portal experience to create a supported external resource and connect a Builder app.
This planned work aims to let customers create a supported external resource and connect a Builder app in one portal experience. It is separate from connection settings for resources customers already own and from Azure managed-connector integration. The initial service catalog, permissions, provisioning behavior, and cleanup policy remain undecided. No particular service or automatic permission grant is promised. This experience is not available today.
Customer-facing create-and-connect scope and current backlog status reviewed on November 16, 2026. Service coverage and lifecycle behavior require qualification. No public delivery date or release commitment is approved.
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #8
Use a browser to connect a repository, configure access, deploy an app, inspect its status, change configuration, and delete it.
The Builder portal supports repository selection, app creation and deployment, diagnostics, configuration, and deletion. During creation, the Access step lets you configure managed identity and visitor authentication before the first deployment, including an opt-in Microsoft tenant sign-in preset. Leave both access choices off to skip and configure them later on the Identity and Authentication pages. Review the selected rules; sign-in is not asserted as required by default for every new app. GitHub connection recovery and source-selection preservation are covered by the GitHub source item. This is the Builder portal, not a separate integration into the Azure portal.
Creation access, app-management scope, and private-preview availability reconfirmed during the roadmap review on November 4, 2026. The completion date retains the October 12 confirmation of the initial implementation, not the original release date. Preview access is for development and test workloads, not production.
Completed .
Public documentation and access information
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #61
Customize the visitor-facing stopped-app experience in Public preview.
Builder supports customizing the visitor-facing experience when an app is stopped in Public preview, separately from error-page customization. This bounded capability does not establish customization for every error category. It does not promise automatic resume or change app scaling or stop behavior. Public preview is for development and test workloads, not production.
Owner-confirmed completion and Public preview availability for bounded visitor-facing stopped-app customization reviewed on November 17, 2026. Completion date not recorded; this review date is not a completion or release date. This confirmation does not establish other error-page coverage, automatic wake, changed stop/start or scale-to-zero behavior, or independent implementation validation. No broader support or future delivery commitment is implied.
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #60
Plan custom pages for agreed app error conditions.
This planned work considers customizing visitor-facing pages for agreed error conditions in Builder apps. It concerns app visitors, not errors in the Builder portal. Supported conditions, configuration, and fallback behavior remain to be defined and qualified. It does not promise customization for every HTTP status code or resolve underlying runtime failures. Custom error pages are not available today.
Customer-facing error-page customization scope and current backlog status reviewed on November 16, 2026. No supported condition, public delivery date, or release commitment is approved.
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #34
Simplify app setup with a planned PostgreSQL database primitive in Builder configuration.
This work aims to add a PostgreSQL database primitive for app setup, rather than requiring every app to arrange an existing database connection independently. Provisioning, lifecycle, connection configuration, supported plans, and operational ownership still need qualification. It is distinct from app code connecting to a customer-owned PostgreSQL database and from the separate first-class service-connections work. Builder does not currently provide a shipped managed-database capability; this item is not ready for use.
Planned database-primitive scope, in-progress status, and not-yet-available access confirmed during the roadmap review on October 31, 2026. Implementation and qualification continue; no public delivery date, managed-database availability, or release commitment is approved.
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #40
Study how Builder usage should be billed, then use the outcome to guide billing implementation.
This work covers defining and implementing Builder billing based on the billing-model study currently underway. The billing model, usage meters, pricing, and transition experience remain undecided. The study does not mean charging has started; the existing preview offer remains unchanged. This item does not promise future free or paid terms, and the planned billing implementation is not available today.
Customer-facing billing implementation goal, in-progress study, and not-yet-available billing implementation confirmed during the roadmap review on November 1, 2026. In progress records the active billing-model study, not live charging or a completed billing implementation. No public delivery date, pricing, or release commitment is approved.
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #23
Establish how apps receive sensitive settings, such as service credentials, separately from ordinary environment variables.
This work defines the configuration and handling of sensitive values that an app needs to access other services. The current design direction is inline/read-only secrets, but how values are supplied, accessed, and updated still needs definition and qualification. Ordinary environment variables are not a qualified secret store. This item does not promise built-in encrypted storage or secret rotation; whether Builder needs an Azure Key Vault integration is a separate evaluation.
Reviewed status alignment on 2026-11-09: In progress / Not yet available. This supersedes earlier workflow and availability statements below; it does not broaden the documented capability scope. No new release, general availability, production-workload support, or future delivery commitment is implied. Earlier review context: Scope, inline/read-only design direction, backlog status, and not-yet-available access confirmed during the roadmap review on October 12, 2026. Feature implementation has not started; completed design work does not establish delivery or security qualification.
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #4
Deploy a website and its backend API as components of one Builder application, with requests routed to each component.
Define the frontend and backend in one Builder application configuration rather than setting up two unrelated deployments. For example, this blog serves its static frontend at / and routes /api requests to a Node.js backend. This item covers deploying those components together and routing requests between their paths; it does not mean Builder also creates a database or other external services.
Completion and private-preview availability confirmed during the roadmap review on October 12, 2026. The date records that confirmation, not the original release date.
Completed .
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #9
Use a dedicated Builder command-line tool to manage apps from a terminal or script.
A command-line interface, or CLI, lets you manage an app by running commands instead of using the portal. This work covers a customer-facing Builder CLI for the supported app lifecycle, including deployment and management. The intended release excludes developer-only commands. It is not an Azure CLI extension; the final command set and installation instructions still need confirmation.
Reviewed status alignment on 2026-11-09: Done / Private preview. This supersedes earlier workflow and availability statements below; it does not broaden the documented capability scope. The completion date records this review confirmation, not the original release date. No new release, general availability, production-workload support, or future delivery commitment is implied. Earlier review context: Scope, in-progress status, and private-preview availability confirmed during the roadmap review on October 12, 2026. The CLI is available in private preview while work on the complete customer-facing experience continues.
Completed .
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #10
Use the Copilot app canvas for assisted setup, configuration review, deployment monitoring, and failure recovery.
This work connects the supported GitHub Copilot app canvas to the Builder app lifecycle. The intended journey lets an agent help set up an app, review its configuration, deploy it, follow deployment progress, and recover from failures. It is specifically the app canvas integration, not a promise that every Copilot client or editor has Builder deployment support.
Reviewed status alignment on 2026-11-09: Done / Private preview. This supersedes earlier workflow and availability statements below; it does not broaden the documented capability scope. The completion date records this review confirmation, not the original release date. No new release, general availability, production-workload support, or future delivery commitment is implied. Earlier review context: Scope, in-progress status, and private-preview availability confirmed during the roadmap review on October 12, 2026. The app canvas integration is available in private preview while work on the complete supported journey continues.
Completed .
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #3
Host HTTP endpoints that a frontend or another application calls to read data or perform an action.
Deploy a backend service that accepts HTTP requests and returns responses, such as JSON data rather than a complete web page. For example, this blog's API handles requests for article view counts and feature votes. An API runs as a server-side component; this item highlights that backend use case rather than a separate kind of hosting.
Completion and private-preview availability confirmed during the roadmap review on October 12, 2026. The date records that confirmation, not the original release date.
Completed .
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #5
Connect a GitHub repository so Builder can fetch your source code, build it, and deploy your app.
Connect the GitHub repository containing your application so Builder can build and deploy its source. GitHub account authorization and GitHub App access to the selected repository are separate requirements. The Portal can restore your saved GitHub connection after a reload and provides an explicit Change account option. Repository selection waits for the full inventory to load; refreshing installation access preserves the selected repository and branch. Changing the creation region preserves GitHub source and template selections. Connecting source does not enable automatic deployment on every push; use explicit deployment in this preview. A first-class GitHub Actions workflow is tracked separately.
Source-selection scope and private-preview availability reconfirmed during the roadmap review on November 4, 2026. The completion date retains the October 12 confirmation, not the original release date. Preview access is for development and test workloads, not production.
Completed .
Public documentation and access information
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #6
Build and deploy your app through a first-class GitHub Actions workflow as an alternative to installing the Builder GitHub App.
GitHub Actions runs automated steps defined in a YAML workflow in your repository. This work adds a supported first-class workflow deployment path, so customers can test and deploy without installing the Builder GitHub App. ZIP source deployment through a compatible Builder CLI or API is available separately, but that does not complete this GitHub Actions integration. The Portal's Use GitHub Actions option remains Coming soon. Supported workflow steps and packaging requirements still need qualification; this item does not cover Azure DevOps pipelines.
Scope, in-progress status, and not-yet-available first-class integration confirmed during the roadmap review on October 31, 2026. ZIP source deployment does not establish delivery of this workflow. No delivery date is committed.
Public documentation and access information
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #28
Upload and deploy local application source without connecting a GitHub repository.
Use a compatible Builder CLI or the API to upload source packaged as a ZIP, with a valid builder.yaml at the archive root. Builder builds and deploys that source; the archive is not a ready-to-run application package. Use a CLI compatible with your preview access and exclude credentials and other sensitive files. Portal ZIP deployment is not available. This capability does not deliver a first-class GitHub Actions integration or automatic deployment on a GitHub push.
ZIP source deployment through the compatible Builder CLI and API confirmed during the roadmap review on October 31, 2026, consistent with the published October 26-28 release note. The date records confirmation, not the original release date. Availability is private preview for development and test workloads, not production.
Completed .
Public documentation and access information
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #48
Qualify a supported Next.js App Router standalone workflow; bounded hosted routes, assets, and retained-version operations work, but Server Actions remain unresolved.
This work targets Next.js App Router apps running as Node.js standalone output, separate from generic static-plus-HTTP hosting and generated-configuration onboarding. The canonical sample now includes the merged standalone asset-packaging correction and uses Next.js 16.4.4 with React and React DOM 19.3.1. A separate bounded authenticated ARM ZIP experiment in westus2 used build Node.js 24.20.0 and serving Node.js 24.22.1. It demonstrated activation, request-time SSR, dynamic App Router routes, GET handlers, hydration and client navigation, JS/CSS and public PNG assets, decoded optimized PNG/WebP images, redirects, not-found responses, and one proxy matcher. Code update, captured build/runtime configuration, retained-artifact redeployment, and rollback to the original retained version also passed within that experiment. Real authenticated Server Action POSTs still returned HTTP 500 in every phase. This newer evidence is separate from the earlier sample trial; it does not qualify unrestricted lifecycle or framework behavior. An earlier diagnostic observed a public-origin/backend-forwarded-host mismatch, but request headers and cause were not newly captured; the responsible hop, serving ring, and image remain unverified. No origin-check exception or platform fix is included. ARM ZIP deployment does not validate GitHub source acquisition or push workflows. Runtime and ingress ownership, an exact version/feature/region support contract, a Server Actions fix or explicitly approved scope exclusion, dependency-advisory triage, and a maintained requalification gate remain outstanding. Restart/crash recovery, Pages Router, static export, ISR/revalidation, streaming/cache guarantees, Edge Runtime, custom servers, general proxy behavior, other regions and versions, and production workloads remain unqualified. Local CI alone does not establish cloud support; the standalone path is implemented and partially qualified, not official support or a change to the current not-ready guidance.
Dedicated App Router standalone scope, in-progress qualification, and not-yet-available access reconfirmed during the roadmap review on November 5, 2026. The canonical asset correction is merged and bounded hosted route, asset, configuration, and retained-version checks passed; hosted Server Actions remain unresolved and broader qualification is pending. These results do not establish broad customer availability or override current support guidance. No public delivery date or release commitment is approved.
Public documentation and access information
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #2
Run an application server that handles incoming requests and generates responses, such as a Node.js web app.
Builder builds your application and runs its configured server process. Unlike a static website, the application executes code when it receives a request, such as generating a page or processing submitted data. This item covers hosting that server process. API deployment covers servers used for backend endpoints; full-stack deployment combines a server with a separate frontend.
Completion and private-preview availability confirmed during the roadmap review on October 12, 2026. The date records that confirmation, not the original release date.
Completed .
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #1
Build and host a website made of HTML, CSS, JavaScript, and other files, such as a blog or documentation site.
Builder runs your site's build command and hosts the generated files. Visitors receive those files without an application server generating each page. For example, this blog's Astro frontend builds into static pages served by a static component. This item covers the website itself; deploying a backend alongside it is covered by full-stack deployment.
Completion and private-preview availability confirmed during the roadmap review on October 12, 2026. The date records that confirmation, not the original release date.
Completed .
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #25
Try proposed app changes in a temporary environment for a pull request targeting an existing Builder app's tracked branch.
This work aims to create temporary preview subresources for GitHub pull requests targeting an existing Builder app's tracked branch, without replacing the main app deployment. It covers creating, updating, and cleaning up previews with the pull-request lifecycle, with an intended stable URL for each preview. The broader creation, access, configuration, and cleanup contract remains under definition and qualification. This does not include arbitrary branch environments or persistent staging/production grouping, which is tracked separately. Ephemeral previews are not available today.
Scope, in-progress status, and not-yet-available access confirmed during the roadmap review on October 12, 2026. Work has started; the earlier planning-source status is superseded by this confirmation. Ephemeral scope and priority ahead of persistent-environment grouping clarified on November 2, 2026. No preview release date is committed.
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #27
Investigate whether Builder should provide a first-party integration with Azure Key Vault for application secrets.
Azure Key Vault stores secrets in an Azure resource. This evaluation asks whether Builder should integrate directly with it so apps can use customer-managed secrets, and how that would fit the platform's broader secret-handling model. No integration approach has been selected. Secret references, access permissions, updates, and the boundary between Builder and Key Vault would need to be defined before implementation. This is an evaluation, not a commitment to deliver a Key Vault integration.
Reviewed status alignment on 2026-11-09: Backlog / Not yet available. This supersedes earlier workflow and availability statements below; it does not broaden the documented capability scope. No new release, general availability, production-workload support, or future delivery commitment is implied. Earlier review context: Evaluation scope, in-progress status, and not-yet-available access confirmed during the roadmap review on October 12, 2026. The evaluation is actively underway. Key Vault is not the mandatory preview secret-management path or an approved implementation; no integration delivery is committed.
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #49
Qualify additional Azure regions for Builder app deployment.
This work aims to expand the Azure regions where customers can deploy Builder apps. The next regions, supported capabilities, access requirements, and rollout sequence remain to be confirmed. Work on regional expansion does not establish availability in any additional region today or change the current preview workload limits. No region list, launch date, or production-workload support is promised.
Customer-facing regional expansion scope, in-progress status, and not-yet-available additional-region access confirmed during the roadmap review on November 10, 2026. Specific regions and rollout timing remain unannounced. No public delivery date or release commitment is approved.
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #30
Send an app's stdout and stderr to customer-owned Azure monitoring resources through ARM configuration.
Where the preview environment enables runtime log export, configure stdout/stderr export through ARM to your own Log Analytics workspace, custom table, Data Collection Endpoint (DCE), and Data Collection Rule (DCR). Customers provision and configure the destination, grant the selected identity Monitoring Metrics Publisher ingestion permission on the DCR, meet destination network requirements, and verify that new log records arrive. Selecting an attached user-assigned identity with identityResourceId supports user-assigned-only export; a system-assigned companion is not required. Without identityResourceId, a system-assigned app identity is required. Setup is ARM-only, with no Portal form or Builder CLI command. This is not live Portal log streaming, runtime metrics, Azure control-plane Activity Logs, or automatic provisioning of monitoring resources. Destination costs, retention, and access are customer-owned; an accepted configuration update does not prove ingestion.
Environment-enabled ARM export, documented identity-selection behavior, and private-preview availability reconfirmed during the roadmap review on November 4, 2026. This contract refresh does not establish a new end-to-end export qualification. The completion date retains the October 31 confirmation of the initial supported implementation, not its original release date or general availability. Preview access is for development and test workloads, not production.
Completed .
Public documentation and access information
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #14
Read build output and follow deployment progress to see where a release succeeds or fails.
Build logs show output from preparing your app, such as installing dependencies and running its build command. Deployment progress shows what happens as Builder publishes the app. This covers access to that output during deployment so failures can be investigated as they happen. Logs produced by the app after it starts are covered separately by runtime application logs.
Scope, completion, and private-preview availability confirmed during the roadmap review on October 12, 2026. The date records that confirmation, not the original release date.
Completed .
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #31
Start from a sample in the Portal and fork its repository inline during app creation.
Choose Start from a template in the Portal, select a sample, and use Fork and continue to create a GitHub fork in your account or an authorized organization before continuing app creation. If you already prepared a fork, choose Use my repository instead. Normal GitHub source permissions still apply. Templates include builder.yaml; this is not no-YAML manifest generation or a guarantee that every template runtime is supported in your location. Review any sample-specific credentials or service configuration before deployment.
Inline GitHub template forking during Portal app creation confirmed during the roadmap review on October 31, 2026, consistent with the published October 26-28 release note. The date records confirmation, not the original release date. Availability is private preview for development and test workloads, not production.
Completed .
Public documentation and access information
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #36
Qualify Azure Policy integration beyond current generic required-tag resource enforcement.
Azure Policy's built-in Require a tag on resources policy can deny a Builder app resource update when its required tag is missing. This limited resource-metadata enforcement is documented and has been observed; verify denied and compliant writes on your own development/test app. Broader service-specific policy coverage remains under qualification. This does not establish broad compliance assurance or a shipped Builder-specific policy pack. Supported service-specific policies, resource aliases, policy effects, and configuration still need definition and qualification; required tags do not establish application-authentication policies or build approval gates. The built-in policy inventory is a distinct customer scope within this shared governance plan, linked as roadmap #41. The broader integration is not yet available.
Shared governance planning and distinct integration/catalog scopes confirmed during the roadmap review on November 10, 2026. Both scopes are In progress / Not yet available; shared tracking does not establish catalog delivery or retire the broader integration. Existing IDs and discussion threads remain unchanged. Earlier review context: Customer-facing governance scope, in-progress qualification, and not-yet-available broader integration reconfirmed during the roadmap review on November 4, 2026. In progress records qualification beyond current narrow generic required-tag enforcement, not delivery of broader policy integration or a Builder-specific policy catalog. No public delivery date or release commitment is approved.
Public documentation and access information
View the related roadmap scope. These scopes share planning, but retain their own discussion threads.
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #45
Organize separate, isolated persistent Builder apps under a common app or repository view with clear environment labels and configuration.
This planned work aims to group separate, isolated persistent Builder apps under a common app or repository view, using labels such as staging and production to make each app's configuration and purpose clear. It is separate from temporary pull-request previews. The exact UI and resource model remain undecided; a repository view may be sufficient, and no new Azure Resource Manager resource abstraction is committed. This grouping does not promise deployment slots, platform-managed traffic splitting, automatic promotion, A/B routing, or shared state between apps. Environment labels do not establish production-workload qualification. Persistent-environment grouping is not available today.
Customer-facing persistent-environment grouping goal, backlog status, and not-yet-available access confirmed during the roadmap review on November 2, 2026. Work has not started; the grouping and configuration-management experience still need definition and qualification. Ephemeral pull-request previews are prioritized first. No public delivery date or release commitment is approved.
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #57
Plan multi-region resilience for Builder apps.
This planned work considers resilience for Builder apps across Azure regions. Supported scenarios, regional coverage, recovery behavior, and customer configuration remain to be defined and qualified. It is separate from making Builder available in additional regions; regional expansion alone does not provide multi-region resilience for an app. This item does not promise active-active operation, automatic failover, data replication, recovery targets, or an availability SLA. Multi-region resilience is not available today.
Customer-facing multi-region resilience scope, backlog status, and not-yet-available access confirmed during the roadmap review on November 11, 2026. No architecture, regional coverage, resilience guarantee, public delivery date, or release commitment is approved.
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #63
Address reported accessibility barriers in selected Builder UI journeys.
This planned work addresses bounded reported keyboard and assistive-technology barriers in selected Builder UI journeys. The specific journeys, fixes, and validation coverage remain to be qualified. This item does not claim that every product surface conforms to an accessibility standard or that a certification has been achieved. The remediation tracked here is not available today.
Customer-facing accessibility remediation scope and current backlog status reviewed on November 16, 2026. No all-product conformance, certification, public delivery date, or release commitment is approved.
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #15
Inspect runtime-log snapshots or follow a selected replica in the CLI, and stream app logs in the Portal, separately from Log Analytics export.
Runtime logs contain app startup and request-handling messages. The accepted Public preview baseline supports bounded CLI snapshots and following output from a selected replica, plus Portal runtime-log streaming. Snapshots can select one or all replicas. Follow supports one replica, not all replicas or JSON, for up to ten minutes and may end sooner. The Portal streams up to five instances. Choose the replica you need to inspect; following or reconnecting may miss or repeat lines and is not a lossless, complete log history or durable log store. This baseline does not establish distinct stdout/stderr attribution, complete process-output capture, or qualification of a particular deployed build. ARM-configured export to a customer-owned Log Analytics workspace remains a separate available roadmap item with its own setup requirements. On-demand inspection does not provide runtime metrics or an interactive shell into the app. Public preview is for development and test workloads, not production.
Owner acceptance of the bounded replica-aware runtime-log baseline and Done / Public preview status reviewed on November 17, 2026. Completion date not recorded; this review date is not a completion or release date. Acceptance does not establish structured stream identity, complete process-output capture, or exact-build qualification; further qualification remains open. This is acceptance of the baseline, not a new independent hosted test. This supersedes earlier planned/unavailable statements without broadening the accepted scope. Earlier review context: On-demand diagnostic scope, in-progress status, and not-yet-available access reconfirmed during the roadmap review on November 4, 2026. Planned replica-aware CLI snapshots are bounded reads, not continuous streaming or a newly distributed CLI capability. Runtime log export remains separate; no customer release or delivery date is committed.
Public documentation and access information
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #37
Plan supported security posture and protection integration for Builder apps through Microsoft Defender for Cloud.
This planned work aims to help customers understand and address supported security posture and protection needs for Builder apps through Microsoft Defender for Cloud. The recommendations, assessments, protection capabilities, configuration, and licensing surface have not been decided. This does not imply that every Defender plan or capability will apply to Builder apps, or that this integration is available today.
Customer-facing posture and protection integration scope, backlog status, and not-yet-available access confirmed during the roadmap review on November 1, 2026. Work has not started; no public delivery date or release commitment is approved.
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #65
Establish a supported integration between Builder-hosted apps and RayFin.
This work aims to establish a supported Builder-hosted app integration with RayFin. The supported workflow and app-host and authentication contract remain to be agreed. Server-side integration depends on an explicitly supported audience and authorization contract. The integration is not available today; no delivery date, supported operation, or automatic access is promised.
Customer-facing RayFin integration scope, in-progress workflow, and not-yet-available customer access reviewed on November 16, 2026. Supported workflow and app-host/authentication contract remain to be agreed. No completion date or public delivery commitment is recorded.
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #39
Plan a native application storage solution intended to retain data beyond an individual running app process.
This planned work aims to give Builder apps a native persistent application storage solution. The storage design, durability, sharing behavior, and resource model have not been selected. App-owned external stores, best-effort replica snapshots, and existing blob-backed static hosting do not establish delivery of this feature. It does not promise arbitrary filesystem mounts or a persistence guarantee for current apps; a native persistent application storage solution is not available today.
Customer-facing persistent application storage scope, backlog status, and not-yet-available access confirmed during the roadmap review on November 1, 2026. Work has not started; no public delivery date or release commitment is approved.
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #55
Plan a Builder stack-management experience.
This planned work covers a stack-management experience for Builder apps. What constitutes a managed stack, the supported operations, and lifecycle behavior remain to be defined and qualified. This item does not promise a particular resource model, orchestration system, or automatic management of existing apps. Stack management is not available today.
Customer-facing stack-management scope, backlog status, and not-yet-available access confirmed during the roadmap review on November 11, 2026. No architecture, supported operation, public delivery date, or release commitment is approved.
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #11
Provision and update Builder app resource configuration with ARM JSON or JSON emitted by Bicep.
Azure Resource Manager, or ARM, manages Builder app resources and access controls. ARM JSON and JSON emitted by Bicep have been validated for resource provisioning and configuration updates. Resource provisioning is separate from source authorization, building a version, and activating a deployment. Bicep can report BCP081 when resource property types are unavailable; emitted JSON does not establish strong typing or property-schema validation. ARM what-if can report changes for computed or omitted fields, so review intended writable settings and resource readback rather than treating every Modify as a meaningful change. This does not qualify every infrastructure tool or promise a Builder experience inside the Azure portal.
Reviewed status alignment on 2026-11-10: In progress / Not yet available. This supersedes earlier workflow and availability statements below; it does not broaden the documented capability scope. This alignment is not a new release announcement or a promise of support beyond the documented scope and reviewed availability. No future delivery commitment is implied. Earlier review context: Reviewed status alignment on 2026-11-09: Done / Private preview. This supersedes earlier workflow and availability statements below; it does not broaden the documented capability scope. The completion date records this review confirmation, not the original release date. No new release, general availability, production-workload support, or future delivery commitment is implied. Earlier review context: ARM resource-configuration scope, in-progress status, and private-preview availability reconfirmed during the roadmap review on November 4, 2026. Template provisioning and updates are validated within the documented type and change-planning limitations, not full infrastructure-tool qualification. Work on the complete resource-management experience continues; access remains for development and test workloads, not production.
Public documentation and access information
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #33
Add Builder-specific Azure PowerShell commands for app management and automation.
This planned work adds a first-class Builder integration to Azure PowerShell. It is distinct from running Builder CLI commands in a PowerShell shell or using generic ARM requests. The cmdlets, module distribution, authentication experience, and supported app operations still need definition and qualification. Builder-specific Azure PowerShell support is not available today.
Reviewed status alignment on 2026-11-16: In progress / Not yet available. This supersedes earlier workflow and availability statements below; it does not broaden the documented capability scope. This alignment is not a new release announcement or a promise of support beyond the documented scope and reviewed availability. No future delivery commitment is implied. Earlier review context: Customer-facing scope, backlog status, and not-yet-available access confirmed during the roadmap review on October 31, 2026. Work has not started; no public delivery date or release commitment is approved.
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #42
Migrate Builder integration into native built-in Azure CLI commands as a later step after the initial extension.
This planned later work migrates Builder app management into native built-in Azure CLI commands. It follows the initial Azure CLI extension, which is tracked separately; shipping that extension does not complete this native-command capability. It is distinct from the dedicated Builder CLI and generic ARM requests. Command names, supported operations, authentication, and the migration experience still need definition and qualification. Native built-in Builder commands are not available today.
Separate customer-facing native-command scope, backlog status, and not-yet-available access confirmed during the roadmap review on November 1, 2026. This is the later step after the initial extension, not an engineering start or delivery commitment. Work has not started; no public delivery date or release commitment is approved.
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #43
Plan tooling to assess an existing Azure Static Web Apps app and help move supported app code and configuration to Builder.
This planned tooling aims to assess an existing Azure Static Web Apps app, help move supported app code and configuration to Builder, identify compatibility gaps and manual steps, and validate the destination app. The tool surface, supported app shapes, transfer scope, cutover, and rollback behavior remain undecided. This does not promise full feature parity, automatic transfer of authentication, custom domains, DNS, databases, or Functions, zero downtime, or destructive changes to the source app. A Static Web Apps intake marked Coming soon does not establish available migration tooling or a shipped canvas migration path. Migration tooling is not available today.
Customer-facing Static Web Apps migration-tooling goal, backlog status, and not-yet-available access confirmed during the roadmap review on November 2, 2026. Work has not started; the supported migration scope and experience still need definition and qualification. No public delivery date or release commitment is approved.
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #16
Use runtime and HTTP request metrics to understand how your app is operating, rather than relying only on log messages.
Metrics summarize app behavior over time, while logs describe individual events. This work covers customer-visible runtime and HTTP request metrics for diagnosing resource usage and request behavior. The exact measurements, how you access them, and any dashboard or retention behavior remain to be defined. These metrics are separate from the CPU and memory signals used for autoscaling.
Both runtime and HTTP metric scope, backlog status, and not-yet-available access confirmed during the roadmap review on October 12, 2026. Work has not started; metric coverage and the access experience remain to be defined.
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #58
Give coding agents read-only search and reading access to public Builder documentation through the Model Context Protocol.
This work aims to let coding agents search and read already-public Builder documentation through the Model Context Protocol (MCP), with intended anonymous, read-only access. The scope is a standalone development and test pilot for documentation access, not Builder-managed MCP hosting, app administration, or access to private documentation. This planning item does not announce a public endpoint, supported routing, or an official launch. The Builder documentation MCP server is not available today.
Customer-facing documentation MCP scope, in-progress pilot work, and not-yet-available access confirmed during the roadmap review on November 11, 2026. Work on a pilot does not establish an available service or official launch approval. No endpoint, routing, public delivery date, or release commitment is approved.
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #12
See your app's previous deployments and their outcomes when investigating a change or failure.
Deployment history records the app's deployment attempts so you can review what happened before the current version. It helps you trace a change or compare a failed deployment with earlier attempts. This item covers reviewing that history; restoring a previous version is covered by rollback and failed-update recovery. History retention and the exact details shown remain to be confirmed.
Scope, completion, and private-preview availability confirmed during the roadmap review on October 12, 2026. The date records that confirmation, not the original release date.
Completed .
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #13
Restore a previous app version and keep the last working version serving when an update fails.
This work covers two recovery paths: deliberately returning to an earlier deployment, and rejecting an unsuccessful update without replacing the working app. The intended update flow checks the new deployment's health before replacing the previous version. Retention of older versions, recovery when their artifacts are missing, and recovery timing still need qualification; no guaranteed rebuild or recovery time is promised.
Reviewed status alignment on 2026-11-09: Done / Private preview. This supersedes earlier workflow and availability statements below; it does not broaden the documented capability scope. The completion date records this review confirmation, not the original release date. No new release, general availability, production-workload support, or future delivery commitment is implied. Earlier review context: Both recovery paths, in-progress status, and private-preview availability confirmed during the roadmap review on October 12, 2026. Recovery capabilities are available in private preview while work and qualification continue.
Completed .
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #44
Plan hosted functions associated with a Builder app, similar in customer experience to managed functions in Azure Static Web Apps.
This planned capability aims to provide hosted functions associated with a Builder app, similar in customer experience to Azure Static Web Apps managed functions. It is distinct from deploying backend APIs or full-stack HTTP server components and from manually provisioning external Azure Functions resources. The runtime, hosting and resource model, supported languages, triggers, bindings, routing, scaling, limits, costs, and lifecycle remain unselected. This does not promise exact Static Web Apps parity, automatic migration of Static Web Apps functions, support for background triggers, or a shipped Azure Functions integration. Hosted functions are not available today.
Customer-facing hosted-functions goal, backlog status, and not-yet-available access confirmed during the roadmap review on November 2, 2026. Work has not started; the supported scope and implementation model still need definition and qualification. No public delivery date or release commitment is approved.
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #20
Explicitly opt an image-backed app into sleeping when idle and waking on the next HTTP request.
For an image-backed app version, set the minimum replica count to zero in Portal Scaling or a compatible Builder CLI. This opt-in automatically enables the required HTTP activity rule. After roughly five to six minutes without new HTTP requests, the app can sleep; the next request waits for it to start again. The inactivity window is provider-owned and not configurable. Active requests, streams, and background work can be interrupted and do not reliably prevent sleep. Each wake starts a fresh process, with no in-memory state preservation or shared-storage or persistence guarantee. Keep durable data outside the app and use a positive minimum for work that must stay running. Existing defaults remain warm unless you opt in; positive-minimum HTTP autoscaling is separate and does not require sleeping.
Completion reconfirmed on November 17, 2026: Done / Public preview. This supersedes the earlier Backlog alignment without broadening the documented scope. The existing November 9 completion-confirmation date is retained; no new release date or production-workload support is implied. Earlier review context: Reviewed status alignment on 2026-11-10: Backlog / Private preview. This supersedes earlier workflow and availability statements below; it does not broaden the documented capability scope. This alignment is not a new release announcement or a promise of support beyond the documented scope and reviewed availability. No future delivery commitment is implied. Earlier review context: Reviewed status alignment on 2026-11-09: Done / Private preview. This supersedes earlier workflow and availability statements below; it does not broaden the documented capability scope. The completion date records this review confirmation, not the original release date. No new release, general availability, production-workload support, or future delivery commitment is implied. Earlier review context: The documented image-backed opt-in, automatic HTTP rule, and idle/wake behavior confirmed during the roadmap review on October 31, 2026. The capability is available for development and test workloads in private preview while qualification continues; this is not production-workload support or an availability guarantee.
Completed .
Public documentation and access information
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #7
Simplify first deployment by helping configure an app without requiring you to write its Builder configuration file from scratch.
builder.yaml describes how Builder builds and runs your app. Public preview users can generate and persist configuration from detected layouts in supported GitHub repositories without builder.yaml, then review it in Settings. Explicit manifests remain authoritative; ambiguous repository shapes fail rather than guessing a configuration. Planned review and commit of the exact generated builder.yaml includes safeguards for repository ownership, source revision, and an existing file; those safeguards and end-to-end shared-preview qualification remain unfinished. This availability confirmation is not a new hosted qualification result or completion of the broader onboarding journey. Current templates and quickstarts still include builder.yaml. Forking a Portal template is a separate available capability, not no-YAML setup or a supported Next.js workflow; this item does not promise that every app can deploy without configuration.
Availability reviewed on November 17, 2026: In progress / Public preview for bounded detected-layout configuration generation, persistence, and Settings review. This supersedes earlier unavailable-channel statements below, not the unfinished review/commit safeguards or end-to-end qualification. Preview access is for development and test workloads, not production. No completion or release date was supplied; the review date is not a completion or release date. No universal no-configuration support or future delivery date is committed. Earlier review context: Scope, in-progress status, and not-yet-available access reconfirmed during the roadmap review on November 4, 2026. Generated-manifest review and commit remain under qualification, not a released customer workflow. Public guidance still marks broader manifest-generation onboarding as not ready for use; no delivery date or blanket no-configuration support is committed.
Public documentation and access information
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #51
Plan Builder app support for cloud environments isolated from public networks.
This planned work considers running Builder apps in air-gapped cloud environments, where network isolation changes how applications and services are accessed. Supported environments, deployment and update workflows, network requirements, and feature coverage remain to be defined and qualified. This is separate from private endpoints or outbound virtual-network integration for an app; those features do not deliver an air-gapped Builder service. Air-gapped-cloud support is not available today.
Customer-facing air-gapped-cloud scope, backlog status, and not-yet-available access confirmed during the roadmap review on November 10, 2026. No environment, connectivity model, public delivery date, or release commitment is approved.
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #50
Plan Builder app support in sovereign cloud environments.
This planned work considers Builder app support in sovereign cloud environments. The clouds, regions, supported capabilities, access requirements, and operating model remain to be defined and qualified. Availability in the current preview does not establish support in a sovereign cloud, and this item does not promise a compliance certification or a particular cloud deployment. Sovereign-cloud support is not available today.
Customer-facing sovereign-cloud scope, backlog status, and not-yet-available access confirmed during the roadmap review on November 10, 2026. No cloud, region, certification, public delivery date, or release commitment is approved.
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #26
Connect and deploy repositories using GitHub accounts managed by your organization.
GitHub Enterprise Managed Users are accounts whose lifecycle is controlled by an organization through its identity provider, rather than personal GitHub accounts. This work covers supporting those accounts in Builder's GitHub repository connection and deployment workflows. It is not GitHub sign-in for visitors to your deployed app. Supported account and repository configurations still need confirmation.
Reviewed status alignment on 2026-11-09: Backlog / Not yet available. This supersedes earlier workflow and availability statements below; it does not broaden the documented capability scope. No new release, general availability, production-workload support, or future delivery commitment is implied. Earlier review context: Scope, in-progress status, and not-yet-available access confirmed during the roadmap review on October 12, 2026. Work on managed-account compatibility is underway; supported configurations still need qualification.
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #56
Plan resilience across availability zones for Builder apps.
This planned work considers zone redundancy for Builder apps. Eligible regions, supported app capabilities, configuration, and failure behavior remain to be defined and qualified. Existing app deployment does not establish zone-redundant operation. This item does not promise automatic failover, a particular architecture, or an availability SLA. Zone redundancy is not available today.
Customer-facing zone-redundancy scope, backlog status, and not-yet-available access confirmed during the roadmap review on November 11, 2026. No region, resilience guarantee, public delivery date, or release commitment is approved.
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #41
Build an inventory of built-in Azure Policy definitions that organizations can select and assign for Builder app governance.
This planned work covers delivering an inventory and catalog of built-in Azure Policy definitions for Builder apps, like the policy catalogs available for other Azure services. The built-in definitions, supported scenarios, effects, aliases, assignability, and documentation still need selection, delivery, and qualification. Validation of an existing generic required-tag policy for a Builder App scenario does not deliver this catalog or a shipped Builder-specific policy pack. The catalog is a distinct sub-scope of the broader Azure Policy integration in roadmap #36; both now share governance planning. This catalog is not available today.
Reviewed status alignment on 2026-11-10: In progress / Not yet available. This supersedes earlier workflow and availability statements below; it does not broaden the documented capability scope. This alignment is not a new release announcement or a promise of support beyond the documented scope and reviewed availability. No future delivery commitment is implied. Earlier review context: Shared governance planning and the catalog sub-scope confirmed during the roadmap review on November 10, 2026. The catalog retains its existing public ID and discussion thread; it is not a second independent integration. This supersedes the earlier separate-tracking interpretation, not the documented limits of generic required-tag enforcement. Earlier review context: Customer-facing built-in policy inventory scope, backlog status, and not-yet-available catalog confirmed during the roadmap review on November 1, 2026. Work has not started; generic policy-integration testing does not establish catalog delivery. No public delivery date or release commitment is approved.
View the related roadmap scope. These scopes share planning, but retain their own discussion threads.
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #32
Manage Builder apps through an Azure CLI extension as the initial Azure CLI delivery.
Initial delivery is planned as an Azure CLI extension for Builder-specific app lifecycle operations. Native built-in Azure CLI commands are a later capability tracked separately; completing the extension does not complete that native-command work. The extension is distinct from the dedicated Builder CLI already available in private preview and from making generic ARM requests with az rest. Extension packaging, the command set, authentication experience, and supported operations still need definition and qualification. The Azure CLI extension is not available today.
Reviewed status alignment on 2026-11-16: In progress / Not yet available. This supersedes earlier workflow and availability statements below; it does not broaden the documented capability scope. This alignment is not a new release announcement or a promise of support beyond the documented scope and reviewed availability. No future delivery commitment is implied. Earlier review context: Customer-facing scope, backlog status, and not-yet-available access confirmed during the roadmap review on October 31, 2026. Initial extension delivery was clarified and separated from later native built-in commands on November 1, 2026. This describes the planned implementation approach, not an engineering start. Work has not started; no public delivery date or release commitment is approved.
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #52
Use supported Azure managed connectors through Builder Connections with separately configured connection resources and identity access.
Builder Connections integrates supported Azure managed connectors with a Builder app. Set up the Connector Namespace, connection, identity policies, and owner consent separately before using the connection in your app. This is actual managed-connector integration, distinct from named nonsecret settings for direct service connections. It does not create external services or connections automatically, grant permissions or owner consent, provide a managed secret store, or promise every connector or operation. Supported setup and client prerequisites still apply; this capability does not guarantee availability of particular CLI commands or turnkey provisioning.
Supported managed-connector integration and current Done / Private preview status confirmed during the roadmap review on November 16, 2026. Public preview availability is staged for the coordinated announcement, without expanding the bounded setup or supported connector scope. Completion date not recorded; this review date is not a completion or release date. Preview access is for development and test workloads, not production.
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #21
Give your app an address on a domain you own instead of using only its Builder-generated hostname.
A custom domain lets visitors use an address such as app.example.com for your Builder app. This work covers mapping that customer-owned domain to the app. Domain verification, certificate handling, and preview access or packaging still need confirmation. The domain feature does not, by itself, include customer-managed certificates or Azure Key Vault certificate integration.
Scope, backlog status, and not-yet-available access confirmed during the roadmap review on October 12, 2026. Work has not started; domain verification, certificate handling, and preview packaging remain to be defined.
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Roadmap #54
Develop a Visual Studio Code extension for working with Builder apps from the editor.
This work aims to provide a Builder extension in Visual Studio Code. The supported app operations, authentication flow, distribution, and editor experience remain to be defined and qualified. It is separate from the dedicated Builder CLI and the GitHub Copilot app canvas; availability of those tools does not establish a released VS Code extension. No extension listing, installation path, or support for every editor client is promised. The extension is not available today.
Customer-facing Visual Studio Code extension scope, in-progress status, and not-yet-available access confirmed during the roadmap review on November 10, 2026. No public distribution, delivery date, or release commitment is approved.
Share your use case, what you need, and what would make this useful for your team. Comments and reactions are public feedback; they do not change the official roadmap status.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.
Join the discussion.
Anyone can read the comments. Sign in with GitHub to comment or react. Replies are public; please keep secrets and personal information out of them.