Included Microsoft connectors
Pick the connector that matches what you are building. You can add more than one connection if you need different Microsoft accounts or environments.
How Microsoft connections work
- OAuth 2.0: You authorize a Microsoft account for that product. Permissions depend on the scopes requested for that connector (some connectors expose optional Advanced settings for scopes—grant only what your app needs).
- Microsoft Graph: Requests go to
https://graph.microsoft.com/v1.0/via Lovable’s connector gateway. See Gateway-based connectors for secure token handling and per-project request limits. - Same flow everywhere: Add connection → sign in with Microsoft → approve consent → link the connection to projects. Only the connector name and API surface change between Outlook, Teams, OneDrive, etc.
Microsoft 365 licensing, tenant policies, and Graph throttling are controlled by Microsoft and your organization—not Lovable.
How to connect (any Microsoft product)
Workspace admins and owners can create Microsoft connections.- Open Connectors → App connectors.
- Choose the Microsoft connector you need—for example Microsoft Outlook or Microsoft Teams (each product has its own tile).
- Click Add connection, enter a Display name, and complete Connect / Sign in with Microsoft.
- Accept the permissions shown for that product.
- Link the connection to a project, by prompting the Lovable agent in the project to connect.
Managing and removing connections
Steps match other app connectors; only the product you select in Settings changes.Unlink projects from a connection
Editors and above can unlink projects without deleting the connection.- Open Connectors → App connectors and select the same Microsoft connector you used (for example Microsoft OneDrive).
- Open the connection → Linked projects → choose projects → Unlink projects.
Delete a connection
Workspace admins and owners can delete a connection.- Connectors → App connectors → pick the Microsoft product (for example Microsoft Excel).
- Open the connection → review Linked projects → Delete under delete options → confirm.
Limitations
- Each connection is tied to one authorized Microsoft identity (and that identity’s mail, files, teams, etc., per scopes)—not each visitor’s account unless you build a separate auth story.
- Tenant and admin policies (consent, MFA, blocked apps) can block or limit sign-in; resolve those in Microsoft 365 / Entra ID.
- Gateway limits apply as in Gateway-based connectors.
Need each end user to sign in with their own Microsoft account and act on their own mail, files, and data? Use the Microsoft app user connector instead.