{"title":"Extension types and scope","url":"https://jonas-paprotka.de/docs/dev-itpro/developer/devenv-extension-types-and-scope/","by":"JOP-AL","license":"Copyright (c) Microsoft Corporation. CC BY 4.0, https://creativecommons.org/licenses/by/4.0/; code samples MIT. From https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-extension-types-and-scope, MicrosoftDocs/dynamics365smb-devitpro-pb at 828b6ee (2026-11-19). Changed: includes filled in, links to this site, and for agents shortened without dropping a fact.","credit":"Microsoft Corporation, CC BY 4.0","origin":"https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-extension-types-and-scope","source":{"name":"Business Central developer and IT pro docs","repo":"https://github.com/MicrosoftDocs/dynamics365smb-devitpro-pb","commit":"828b6ee72fcd75755627cd6011f3d20899217ab2","date":"2026-11-19"},"checked":"2026-11-19","description":"Extension types for Business Central explained: global apps, per-tenant extensions, and DEV extensions. Learn how scope and environment affect each type.","date":"2026-08-10","meta":{"topic":"concept-article"},"outline":[{"level":2,"title":"Global apps","slug":"global-apps","at":229,"chars":2637},{"level":3,"title":"Environment types","slug":"environment-types","at":987,"chars":907},{"level":4,"title":"How to install","slug":"how-to-install","at":1152,"chars":742},{"level":3,"title":"Behavior on environment upgrade","slug":"behavior-on-environment-upgrade","at":1894,"chars":972},{"level":4,"title":"Marketplace apps","slug":"marketplace-apps","at":2005,"chars":571},{"level":4,"title":"Microsoft apps","slug":"microsoft-apps","at":2576,"chars":189},{"level":4,"title":"Embed apps","slug":"embed-apps","at":2765,"chars":101},{"level":2,"title":"Per-tenant extensions (PTEs)","slug":"per-tenant-extensions-ptes","at":2866,"chars":2101},{"level":3,"title":"Environment types","slug":"environment-types-1","at":3492,"chars":155},{"level":3,"title":"How to install","slug":"how-to-install-1","at":3647,"chars":705},{"level":3,"title":"Behavior on upgrade","slug":"behavior-on-upgrade","at":4352,"chars":615},{"level":2,"title":"DEV extensions","slug":"dev-extensions","at":4967,"chars":1557},{"level":3,"title":"Environment types","slug":"environment-types-2","at":5809,"chars":155},{"level":3,"title":"How to install","slug":"how-to-install-2","at":5964,"chars":209},{"level":3,"title":"Behavior on upgrade","slug":"behavior-on-upgrade-1","at":6173,"chars":351},{"level":2,"title":"Constraints on extension types","slug":"constraints-on-extension-types","at":6524,"chars":1061},{"level":2,"title":"Related information","slug":"related-information","at":7585,"chars":105}],"text":"This article provides an overview of the different extension types and their scope.\nAn extension can move from one scope to another under certain circumstances. See Moving Between Extension Scopes<devenv-extension-moving-scope>.\n## Global apps\nA global app is an app that meets one or more of the following criteria:\n Microsoft publishes it.\n You install it from the Marketplace.\n Embed ISVs provide it if your environment uses a code-customized base application. See Publishing a code-customized Base Application<devenv-publish-code-customization>.\nGlobal apps are uniquely defined by their id and version.\nYou can't deploy a global app with the same id and version, but different content to multiple environments.\nYou can choose to install, uninstall, or upgrade global apps, but you don't control when they're published or unpublished, because other environments in the service might use them. You also can't force sync a global app.\nGlobal apps can only depend on other global apps.\n### Environment types\nGlobal apps can exist in production and in sandbox environments. See Production and sandbox environments<../administration/environment-types>.\n#### How to install\nFor Marketplace and Microsoft apps:\n From the Marketplace, choose Contact Me, Free Trial, or Get It Now and follow the steps.\n From the Extension Management page in Business Central, you can navigate to the Marketplace embed view, locate the app, and install it. See Installing and uninstalling extensions in Business Central</ui-extensions-install-uninstall>.\n> NOTE\n> The Marketplace offer listing contains the list of supported countries and regions. You must verify that the app is available for the country or region of your environment. If the app isn't available for the country or region of your environment, the installation fails.\nFor apps provided by Embed ISVs, the Embed ISV partner handles the installation.\n### Behavior on environment upgrade\nUpgrades preserve global apps in both production and sandbox environments.\n#### Marketplace apps\n Upgrades never uninstall marketplace apps unless the apps prevent the tenant from upgrading during the Enforced Update Period<../administration/update-rollout-timeline>. See Maintain Marketplace apps and per-tenant extensions<app-maintain>.\n Upgrades update marketplace apps to the latest version during upgrades to a new Business Central major version (for example, 19.5 to 20.0), but preserve them during minor version upgrades (for example, 19.0 to 19.1) - unless the extension publisher marks the app as incompatible through a support request.\n#### Microsoft apps\n Upgrades always update Microsoft apps to the latest compatible version for the corresponding major and minor version during upgrades to a new Business Central version.\n#### Embed apps\n The partner deploying the apps controls embed apps behavior on environment upgrade.\n## Per-tenant extensions (PTEs)\nThese apps are unique per environment. Per-tenant extensions are uniquely defined by their app id, version, and the environment where you deploy them.\n You can deploy multiple PTEs with the same id and version, but different content to multiple environments. This deployment might, however, cause extra overhead when managing these environments.\n You control when to publish, install, upgrade, uninstall, or unpublish the app because it's specific to your environment. You might also choose to force sync a PTE.\n A PTE can have dependencies on global apps, on other PTEs, or on DEV extensions.\n### Environment types\nPTEs can exist in Production and sandbox environments. See Production and sandbox environments<../administration/environment-types>.\n### How to install\nUpload the .app file from the Manage Apps page in the Business Central Admin Center or the Extension Management page in the environment. See Installing and uninstalling extensions in Business Central</ui-extensions-install-uninstall>.\n> IMPORTANT\n> The recommended way to upload, install, and manage per-tenant extensions is now the Business Central Admin Center<../administration/tenant-admin-center-manage-apps> and its ../administration/administration-center-api_app_management. The in-product Extension Management upload flow and the Automation API extensionUpload endpoint are deprecated and planned for removal in 2027 release wave 1. See ../upgrade/deprecated-features-platform.\n### Behavior on upgrade\nThe upgrade process never uninstalls PTEs from a production environment, unless they're preventing the environment from upgrading during the Enforced Update Period<../administration/update-rollout-timeline>. See Maintain Marketplace apps and per-tenant extensions<app-maintain>. The upgrade process uninstalls PTEs when the sandbox environment is relocated if they depend on DEV extensions, but the upgrade process doesn't remove the data. The upgrade process can update PTEs to a newer version during an environment update if a newer version is staged for the target version of the update.\n## DEV extensions\nUse DEV extensions for development purposes. This usage includes extensions published from Visual Studio Code or created by using devenv-inclient-designer in Business Central.\nYou can deploy a DEV extension with the same id and version, but different content, to multiple sandbox environments. You control when to publish, install, upgrade, uninstall, or unpublish the app because it's specific to your environment. You can also force sync the app. See devenv-json-launch-file and Retaining table data after publishing<devenv-retaining-data-after-publishing>.\n> NOTE\n> The resourceExposurePolicy applies differently to DEV extensions. See Resource exposure policy setting<devenv-security-settings-and-ip-protection>.\nDEV extensions can have dependencies on Global apps, on per-tenant extensions, or on other DEV extensions.\n### Environment types\nDEV extensions can only exist in sandbox environments. See Production and sandbox environments<../administration/environment-types>.\n### How to install\nFor information on how to install, see Use Designer<devenv-inclient-designer> and Building your first sample extension that uses new objects and extension objects<devenv-extension-example>.\n### Behavior on upgrade\nWhen you upgrade or relocate a sandbox environment within the service, the process uninstalls DEV extensions. However, the upgrade process doesn't remove the data of an app. To make the app available again, you just need to republish and install it. The upgrade process also uninstalls any PTE that depends on a DEV extension.\n## Constraints on extension types\nIn general, the id uniquely defines extensions. The id and version define a specific version of an app. For per-tenant extensions, add environment to the definition.\n You can't deploy a Global app and a PTE with the same id. During the upload of a PTE, the system validates that there's no Global app with the same id. Currently, the Marketplace validation process doesn't detect all identity conflicts with PTEs. If you upload an app with the same ID as an existing PTE to Marketplace, you can't update the PTE anymore. See devenv-checklist-submission#technical-validation-checklist.\n You can't deploy a Global app and a DEV extension with the same id and version. When you deploy the DEV version of a Global app from Visual Studio Code to a sandbox environment, for example, for development or troubleshooting, make sure your DEV extension has a different version than what is published to Marketplace. Similarly, after you're done developing or testing your extension, increase the version before submitting to Marketplace.\n## Related information\nDeveloping extensions<devenv-dev-overview>\nGet started with AL<devenv-get-started>"}