Connect your app to Microsoft 365

Microsoft 365 includes services like Outlook, Teams, OneDrive, SharePoint, Word, Excel, PowerPoint, and OneNote. Lovable offers a separate connector for each of these products, and they all work the same way: you sign in with your Microsoft account, Lovable stores the tokens securely, and your app calls Microsoft Graph through Lovable’s connector gateway with automatic token refresh.

Use	If you want to
App + chat connector (this page)	Work with a shared Microsoft connection in the chat and in your published apps
App user connector	Let each user of your published app connect their own Microsoft account and work with their own data

Included Microsoft connectors

Each Microsoft product has its own connector in the catalog:

Connector in Lovable	What it’s for
Microsoft Outlook	Email and calendar: read, send, and manage mail, and read and manage calendar events in the signed-in account.
Microsoft Teams	Teams and channels: send messages, list teams and channels, and work with conversations.
Microsoft OneDrive	Files: upload, download, and work with files in the connected account’s OneDrive.
Microsoft SharePoint	Sites, lists, and document libraries: browse sites, read and write list items, and work with files stored in SharePoint.
Microsoft Word	Documents: read and write Word files stored in OneDrive or SharePoint.
Microsoft Excel	Spreadsheets: read and write Excel workbooks.
Microsoft PowerPoint	Presentations: read and write PowerPoint files.
Microsoft OneNote	Notes: notebooks, sections, and pages in OneNote.

Pick the connector that matches what you are building. You can create multiple connections per product if you need different Microsoft accounts or environments.

Common use cases and example apps

These examples show what you can build with a single Microsoft product. You can also combine several Microsoft connectors in the same project for multi-product workflows.

Example app	Example prompt	Description
Inbox triage dashboard	Use Microsoft Outlook and build a dashboard that shows my unread email by sender and lets me send replies.	Manage email from a focused interface. The app reads mail from the connected mailbox, groups it for review, and sends replies through the same account.
Team booking page	Use Microsoft Outlook and build a booking page that checks my calendar availability and creates events when someone books.	Let people schedule time based on real calendar availability. The app reads free and busy times, shows open slots, and creates calendar events when a booking is confirmed.
Teams notifier	Use Microsoft Teams and build a form that posts a summary message to our project channel on every submission.	Send automated updates to a Teams channel. The app formats submission details and posts them as channel messages so the team sees new activity without leaving Teams.
Drive-based file hub	Use Microsoft OneDrive and build an internal tool that lists my folders and lets me upload and organize files.	Create a structured file management experience on top of OneDrive. The app lists folders and files, supports uploads, and keeps documents organized in one interface.
SharePoint list manager	Use Microsoft SharePoint and build an app that reads and updates items in our project tracker list.	Work with SharePoint lists from a custom interface. The app reads list items, displays them in a tailored view, and writes updates back to the SharePoint site.
Expense tracker	Use Microsoft Excel and build an expense tracker that logs each entry as a row in my workbook.	Use an Excel workbook as a lightweight backend. The app appends structured rows to a workbook and reads them back for reporting.
Proposal generator	Use Microsoft Word and build a form that generates a proposal document and saves it to OneDrive.	Automate document creation from structured input. The app generates a formatted Word document from form data and saves it for sharing or review.

How Microsoft connections work

All eight connectors follow the same pattern:

OAuth 2.0: You authorize a Microsoft account (work, school, or personal) for the product you are connecting. Permissions depend on the scopes requested for that connector, and every Microsoft connector lets you review them under Advanced settings. Grant only what your app needs.
Microsoft Graph: Requests go to https://graph.microsoft.com/v1.0/ through Lovable’s connector gateway. See Gateway-based connectors for secure token handling and the per-project usage limit.
Same flow everywhere: Add a connection, sign in with Microsoft, approve the requested permissions, and link the connection to projects. Only the product and its API surface change between Outlook, Teams, OneDrive, and the rest.

Microsoft 365 licensing, tenant policies, and Graph throttling are controlled by Microsoft and your organization, not Lovable.

How to connect a Microsoft product

Who can create Microsoft connections depends on your plan and workspace settings. App + chat connectors are available by default on Free, Pro, and Business plans. On Enterprise plans they are effectively disabled at first: Who can create connections and clients defaults to No one until an admin changes it. You can create multiple connections per product using different Microsoft accounts, which is useful for separating environments or working with several mailboxes, drives, or teams. When the connection is created, you can link it to the projects where you want to use it. Anyone building in a project can ask Lovable in chat to link their project to it.

Prerequisites

Before connecting a Microsoft product, make sure you have:

A Microsoft account with access to the product you want to connect
Permission to create connections in your Lovable workspace (see Who can create connections and clients)

Set up your Microsoft connection

The steps are the same for every Microsoft product:

Open the Microsoft product in Connectors

Open Connectors and select the Microsoft product you want to connect, for example Microsoft Outlook or Microsoft Teams. Each product has its own tile. For the other places to open the catalog from, see Where to find connectors.

Add a connection

Click Add connection.

Name the connection

In Display name, name the connection (for example, Outlook Prod). This name is only used inside Lovable to identify the connection.

Review scopes (optional)

Expand Advanced settings to review the Microsoft Graph permissions your app will request. Each product requests its own set of scopes, and defaults are pre-selected for common use cases.For full scope documentation, see the Microsoft Graph permissions reference.

Choose who can use this connection

Under Who can use this connection, decide who in your workspace can use the connection. You start as the only person with access:

Only you (default): leave the access list as is; only you can use the connection and its associated data.
Invite specific people: add workspace members by email; only you and the people you add can use the connection and its associated data.
Invite entire workspace: click Invite entire workspace to make the connection available to everyone in your Lovable workspace.

See Who can use connections and clients for more information.

Connect to Microsoft and authorize

Click Connect. The Microsoft sign-in window opens, so make sure your browser doesn’t block pop-ups. If it does, Lovable redirects you instead.Sign in with the Microsoft account you want to use, review the requested permissions, and click Accept.You’ll be redirected back to Lovable with a confirmation.

When connected, anyone building in a project can ask Lovable in chat to link their project to the connection (based on configured connection-level access). Your Lovable apps can then start working with that Microsoft product. If your organization uses conditional access or requires admin consent, sign-in can fail until a Microsoft 365 administrator approves Lovable for the tenant. For API details for a specific product, see the Microsoft Graph REST API reference.

Limitations

The Microsoft connectors cannot:

Act on behalf of each visitor to your app. Each connection is tied to one authorized Microsoft account, and everything the connection does uses that account’s mail, files, and teams. If you need each user of your app to sign in with their own Microsoft account, use the Microsoft app user connectors.
Bypass tenant and admin policies. Conditional access, MFA requirements, and blocked apps can prevent sign-in or limit what the connection can do. Resolve those in Microsoft 365 or Microsoft Entra ID.
Exceed the per-project usage limit that applies to gateway-based connectors.

If Microsoft authorization is revoked from the Microsoft side, you’ll need to reconnect the integration in Lovable before API calls can succeed again.

Manage your connection

Connections are managed from Connectors: select , then open the connection.

Unlink projects to remove access from specific projects while keeping the connection available for others. See Unlink projects from a connection for the steps.
Delete the connection to remove it from the workspace entirely. Deleting is permanent. It removes the credentials from all linked projects, and app features that use stop working until a new connection is added. See Delete a connection for the steps and who can delete.

Getting started

Build

Connect

Collaborate

Deploy & host

Grow & optimize

Workspace & account

Plans & billing

Guides & reference

Included Microsoft connectors

Common use cases and example apps

How Microsoft connections work

How to connect a Microsoft product

Prerequisites

Set up your Microsoft connection

Limitations

Manage your connection

​Included Microsoft connectors

​Common use cases and example apps

​How Microsoft connections work

​How to connect a Microsoft product

​Prerequisites

​Set up your Microsoft connection

​Limitations

​Manage your connection

Included Microsoft connectors

Common use cases and example apps

How Microsoft connections work

How to connect a Microsoft product

Prerequisites

Set up your Microsoft connection

Limitations

Manage your connection