Deployment
Deployment of Business Central embed apps: how to build deployment packages (BACPACs, branding, manifest.json, database requirements) and how ISV partners use Lifecycle Services (LCS) to upload, deploy to rings, and onboard customers. Answers questions about package structure and the LCS deployment workflow.
Path: Get started > Develop > Embed apps > Deployment · tier official · system none · narrative reviewed (checked by Opus)
Overview
This section covers the two steps of getting an embed app to customers. First, you build a deployment package. Second, you use the Lifecycle Services (LCS) portal to deploy it and onboard customers.
The package page explains the structure of the package: the database BACPACs, branding elements, and the manifest.json configuration. It also gives requirements for the application database and the tenant template database. The LCS page describes the ISV partner workflow in the portal: creating a project, uploading the package, deploying to rings, monitoring logs, and provisioning tenants.
Start with the deployment package page, since the LCS steps depend on a valid package. Then move to the LCS page for deployment and for customer onboarding through self-service sign-up or the CSP program.
Key points
- Deployment packages include database BACPACs, branding elements, and a manifest.json.
- Separate requirements apply to the application database and the tenant template database.
- ISV partners manage embed app deployment in the LCS portal.
- LCS workflow: create a project, upload the deployment package, deploy to rings, and monitor logs.
- Tenant provisioning is handled through LCS.
- Customers can be onboarded through self-service sign-up or CSP channels.
Learn pages
- Embed app deployment packages: Learn about how to deploy a Business Central Embed app to the Online service
- Lifecycle Services for Embed App: Provides an overview of Lifecycle Services for Embed App in Business Central
Source: Microsoft Learn (CC BY 4.0). Descriptions are Learn’s own.