Dev extensions remain installed on sandboxes
Dev extensions remain installed on sandboxes
Dev extensions are treated more like PTEs and are not uninstalled during environment updates or other lifecycle operations unless incompatible. This reduces unexpected uninstalls and republishing.
Area: Developer tools. Status: GA. Developer relevance: high. Airtime: 1 min across 1 video.
Status evidence
- Nothing said about status; launch event convention: generally available unless stated otherwise.
Where they talk about it
- What's new: Manage PTEs in the Admin Center: 13:28 to 14:24 (called "Dev extensions remain installed on sandbox environments" there)
Quotes
- 14:00 "they will not get uninstalled uh during environment updates or other life cycle operations" - Changes how dev extensions behave on sandboxes, which developers will notice.
Caveats mentioned
- Still uninstalled if incompatible with the environment change, for example an update
Prerequisites mentioned
- Sandbox environment
Documented features match
- No documented item matched. Not documented
- Product documentation (partial, the article describes the broader feature or mentions this in passing): Maintain Marketplace apps and Per-Tenant extensions in Business Central online, checked 2026-10-02. If an incompatible Marketplace app, PTE, or Dev Extension is preventing the deployment of a critical security update, it might be uninstalled. Note: Only mentions Dev Extension alongside PTEs. The FAQ for developing in AL still says VS Code published extensions are removed on sandbox update, which contradicts the new behavior.
Docs checked on 2026-10-02: the match is against Microsoft's what's new pages for the wave as they were on that date. Microsoft keeps filling the documentation, so "no documented item" can go stale.
Tags: al, sandbox, extensions, developer
Generated by pipeline step 06. Source: YouTube auto-captions of the launch event videos, see the deep links. Not official.