Update and correction, October 13, 2026: Current documentation limits the runtime connector to Business and Enterprise workspaces during its gradual rollout. Read-only access still needs authorization checks.
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.
Publishing, data access and sign-in
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 announced Copilot Managed Runtime integration in public preview. Its current documentation makes the connector available on Business and Enterprise plans through a gradual rollout. Confirm access, support and migration terms before a team depends on a published app.
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. Those plans also include single sign-on, automated account provisioning through SCIM, security scanning and audit logs. SCIM lets IT create and remove workspace accounts from its identity system. Confirm Microsoft feature charges for your plan before starting a pilot.
The risk: an app that can write to company data
A SharePoint list can contain sensitive records even when an app only reads it. Write access adds the ability to change records or send information through Outlook and Teams. An app you generated by prompt can now change real company records with real employees’ permissions.
Have IT inspect the permissions the app uses to write data. Test with an account that lacks access to the target records before using live company data.
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 intended Microsoft accounts can sign in, and a person without access to the underlying list cannot see its data through the app.
- Submit invalid test data and confirm it is rejected. Then make a valid test change and confirm you can trace and reverse it.
Proceed only if the access checks hold, invalid data is rejected, and a valid test change can be traced and reversed. If a check fails, stop the pilot and fix that control before using live company data.
End of article