Lovable says it now works with Microsoft so that apps built in Lovable can run inside a company’s own Microsoft environment. In Lovable’s announcement, the company says the aim is to remove a familiar gap: a tool built on a SharePoint list works for one team, but putting it in front of the whole company becomes a separate project.
A “tenant” is your company’s private slice of Microsoft’s cloud, where employee accounts, permissions, and approved apps live. Apps inside it use the same sign-in and rules as everything else IT manages.
What Lovable actually shipped
Lovable describes three connections.
Publish into your tenant. Once an app is built, you connect Copilot Managed Runtime and publish. Lovable packages the app with Microsoft’s Copilot Managed Runtime SDK and deploys it into your Microsoft Entra tenant. Entra is Microsoft’s employee account system. People open the app with their work login, and it appears in the company’s app inventory.
Build on Microsoft 365 and Fabric data. You can connect Outlook, Teams, Excel, SharePoint, OneDrive, Word, PowerPoint, or OneNote. Lovable says the app builds on that data and writes back to it. Connecting Microsoft Fabric lets the app read your lakehouses and warehouses, which are Microsoft’s data storage products for analytics. Lovable says nothing is exported or copied. Apps can also read and write Dataverse and SQL, which matters if your company runs on Dynamics.
Sign in with Microsoft. Apps can use Entra ID for login, so access follows who is in the company directory.
The availability details matter
Lovable says Copilot Managed Runtime is in public preview. That is the piece that puts the app inside the tenant, so the headline feature is the least settled one. Preview features can change or behave unevenly, and Lovable’s post does not describe what happens to a published app if that changes.
The Microsoft 365 connectors, Fabric integration, and Microsoft sign-in are listed as available across all plans. Workspace sign-in with Entra ID is included on Business and Enterprise. Lovable lists SSO, SCIM, security scanning, and audit logs on those plans too. Lovable does not publish separate pricing for the Microsoft features in this announcement.
The risk: an app that can write to company data
Reading a SharePoint list is low stakes. Writing back to it, or to Outlook and Teams, is not. An app you generated by prompt can now change real company records with real employees’ permissions.
Lovable’s post does not say how much of an employee’s access the app inherits when it writes. Treat that as unanswered until you test it.
What builders should do next
If you build internal tools for a company on Microsoft, run a small pilot before anyone depends on it.
- Pick one low-stakes app, such as a request tracker on a test SharePoint list, not a live one.
- Publish it through Copilot Managed Runtime following Lovable’s documentation.
- Ask IT to confirm three things: the app appears in the app inventory, only directory members can sign in, and a person without access to the underlying list cannot see its data through the app.
- Try to write a bad record on purpose, then confirm you can see and undo it.
Pass means all three access checks hold and you can trace and reverse the write. If any fail, keep the app on the read-only connectors until Lovable documents more.
The bigger picture
Lovable’s own framing is that getting an app in front of a whole company is a separate project from building it. This release is its attempt to shrink that project. Whether the preview holds up for a whole company is the open question.
End of article