#9 Deploy and manage apps from the command line
Use a dedicated Builder command-line tool to manage apps from a terminal or script.
Start typing to find articles and roadmap items.
Arrow keys select a result. Enter opens it. Escape dismisses results.
Completed roadmap items, newest recorded completion first; undated items follow. Availability is shown separately for each feature.
Use a dedicated Builder command-line tool to manage apps from a terminal or script.
Use the Copilot app canvas for assisted setup, configuration review, deployment monitoring, and failure recovery.
Restore a previous app version and keep the last working version serving when an update fails.
Explicitly opt an image-backed app into sleeping when idle and waking on the next HTTP request.
Let visitors authenticate to your deployed app with Microsoft Entra ID through built-in application authentication.
Let visitors authenticate to your deployed app with GitHub through built-in application authentication.
Scale a web app with HTTP traffic while keeping a positive minimum of instances running.
Use an Azure-managed identity for app access to supported Azure services instead of distributing service credentials.
Start from a sample in the Portal and fork its repository inline during app creation.
Send an app's stdout and stderr to customer-owned Azure monitoring resources through ARM configuration.
Upload and deploy local application source without connecting a GitHub repository.
Host HTTP endpoints that a frontend or another application calls to read data or perform an action.
Read build output and follow deployment progress to see where a release succeeds or fails.
Use a browser to connect a repository, configure access, deploy an app, inspect its status, change configuration, and delete it.
Adjust app capacity automatically in response to CPU and memory utilization.
See your app's previous deployments and their outcomes when investigating a change or failure.
Deploy a website and its backend API as components of one Builder application, with requests routed to each component.
Connect a GitHub repository so Builder can fetch your source code, build it, and deploy your app.
Build and host a website made of HTML, CSS, JavaScript, and other files, such as a blog or documentation site.
Run an application server that handles incoming requests and generates responses, such as a Node.js web app.
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 completed items yet. We will add work here once completion is confirmed.
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.
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 #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 #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 #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 #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 #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 #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.
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 #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 #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 #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 #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 #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 #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 #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 #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 #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 #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 #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 #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 #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 #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.
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.