Lovable apps can now run inside a company's own Microsoft tenant

Lovable is working with Microsoft so that apps built on its platform can be published into a company's own Microsoft tenant, using the same sign-in and IT controls as other apps there. According to Lovable, more than 70 million projects have been created with the platform, and many of them within companies run on Microsoft.
- Lovable apps can be published into a company's Microsoft Entra tenant using Microsoft's Copilot Managed Runtime SDK.
- Employees use their work login, and IT manages the apps like other Microsoft apps, including in the app inventory.
- Lovable connects to Microsoft 365 apps, Fabric, Dataverse and SQL, with write-back to the source data.
- Copilot Managed Runtime is in public preview; Microsoft 365 connectors, Fabric and Microsoft sign-in are on every Lovable plan.
- Entra workspace sign-in is included on Business and Enterprise plans.
Publishing into the Microsoft tenant
Lovable says apps built by individual teams often work for those teams, but getting them in front of the whole company is a separate project. The new integration is meant to shorten that step.
According to Lovable, a user describes the app and Lovable builds it. When it is ready, the user connects Copilot Managed Runtime and publishes. Lovable packages the app with Microsoft's Copilot Managed Runtime SDK and deploys it into the company's Microsoft Entra tenant. Employees open it with their work login, IT manages it like any other Microsoft app, and it appears in the company's app inventory.
Lovable also says people can sign in to the apps they build with Microsoft Entra ID, and the builder decides who gets access. Anyone in the company directory can use the app.
Building on Microsoft 365 and Fabric data
Lovable can connect to Outlook, Teams, Excel, SharePoint, OneDrive, Word, PowerPoint and OneNote. It builds on that data and writes back to it. With Microsoft Fabric connected, apps read a company's lakehouses and warehouses. Lovable states that nothing gets exported or copied. Apps can also read and write Dataverse and SQL, which puts Dynamics data within reach.
Lovable gives an example: a finance team builds an app that reads supplier statements from the Outlook inbox, checks them against ERP data and flags unpaid invoices. After publishing it to the tenant, the accounts payable team opens it with their work login, and IT sees it next to other Microsoft apps under existing policies.
Other uses named by the company include:
- Construction crews tracking tasks and costs on their phones from OneDrive documents
- Operations teams turning years-old Excel sheets into live tools that write every change back
- Data teams building reports on live Fabric data without writing SQL
Controls for IT and availability
For IT, Lovable says the app lives in the company's tenant, sign-in runs through Entra, and the code is real code that engineers can work with. Business and Enterprise plans include SSO, SCIM, security scanning and audit logs.
Lovable also appears in other parts of the Microsoft ecosystem. The Lovable MCP server is listed in the MCP Center, so users can build, iterate and deploy Lovable apps from their AI workflows without opening the editor. The Lovable desktop app runs on Windows. Lovable is listed on Microsoft Marketplace, and companies that buy through Microsoft can ask about a private offer.
Copilot Managed Runtime is rolling out in public preview. Microsoft 365 connectors, Microsoft Fabric and Microsoft sign-in for built apps are available on every Lovable plan today. Workspace sign-in with Microsoft Entra ID is included on Business and Enterprise.
What it means for companies
The pitch is that a tool built by a single team no longer needs a separate rollout to reach the wider company. Lovable argues that because an app arrives in the tenant the same way other Microsoft apps do, the builder spends less time asking permission and more of what people build reaches production. The company says that "enterprises shouldn't have to choose between speed and governance."
Because the publishing feature relies on Copilot Managed Runtime, which is still in public preview, the full publishing path is not yet generally available.


