> ## Documentation Index > Fetch the complete documentation index at: https://docs.velatir.com/llms.txt > Use this file to discover all available pages before exploring further. # Microsoft 365 > Connect a Microsoft 365 tenant to bring in Microsoft 365 Copilot conversations, Copilot licences, and seat counts. The Microsoft 365 connector reads your organisation's Microsoft 365 Copilot activity straight from Microsoft. It covers every Copilot surface, including Copilot Chat and Copilot in Word, Excel, PowerPoint, Outlook, and Teams, on any device, whether or not Velatir runs on it. You connect once, with an admin approval in Microsoft Entra. There is nothing to install and nothing for your users to do. ## What It Brings In The prompts and responses of everyone with a Microsoft 365 Copilot licence, as sessions in Velatir. Each Copilot product your tenant pays for, with purchased and assigned seats. Optional. Copilot activity from the Microsoft Purview audit log, including Copilot Chat users without a licence. No message text. Conversations from the 30 days before you connected, imported in the background. [What Velatir collects](/connectors/microsoft-365/data) lists exactly what is read and what is kept. ## Before You Start Only an organisation **Administrator** can connect, reconnect, or disconnect. See [Roles & permissions](/platform/roles-and-permissions). Someone with the **Global Administrator** or **Privileged Role Administrator** role in the Microsoft Entra tenant you want to connect. Microsoft requires one of these two roles to approve the kind of permissions Velatir asks for. Application Administrator and Cloud Application Administrator are not enough. Conversations are read for users whose licence includes Microsoft 365 Copilot. A tenant without Copilot licences can connect, but has no seats or licensed conversations to show. The Velatir Administrator and the Microsoft admin do not need to be the same person. Start the connection in Velatir, then let the Microsoft admin sign in when Microsoft asks. Finish in the same browser you started in. Read [Permissions](/connectors/microsoft-365/permissions) before you approve. It explains each permission on Microsoft's consent screen and why Velatir asks for it. ## Connect Microsoft 365 In Velatir, open **Inventory** from the sidebar. If there is no **Microsoft** card, select **Declare service(s)** and declare Microsoft 365 Copilot. The card then shows **Declared · not connected**. Select **Connect** on the **Microsoft** card. The dialog lists what Velatir will pull. Select **Continue to Microsoft**. Sign in with the admin account, in the directory you want to connect. Velatir connects the directory this account belongs to, and no other. Microsoft shows a consent screen for **Velatir Connector** with the list of permissions it asks for. Review them, then select **Accept**. The approval covers your whole organisation. Microsoft returns you to Velatir, which checks that the approval works. When it does, you see *Microsoft connected*, and the card shows **Connected**. The consent is for **Velatir Connector**, an app of its own. It is separate from the app behind **Sign in with Microsoft** and [Microsoft Entra member sync](/platform/microsoft-entra). Connecting does not change how anyone signs in to Velatir, and turning member sync off does not affect the connector. If Microsoft takes a moment to apply a new approval, the connection can show **Action needed** with *Permissions missing* right after you accept. Wait a few minutes, then select **Reconnect**. ## After You Connect | What | When it appears | How often it updates | | - | - | - | | **Licences and seats** | Within minutes | Once a day | | **New conversations** | From the moment you connect | Every 15 minutes | | **Copilot audit records** | Usually an hour or more after the activity, because Microsoft publishes them late | Every few minutes, as Microsoft makes them available | | **The last 30 days** | Over the following hours, most recent day first | Once, in the background | The 30-day import has no progress bar. It runs in the background at a pace that leaves room for your live activity, one day at a time, starting with the most recent. Larger tenants take longer. Imported conversations are dated when they happened, so they fill in Sessions and Insights from the most recent day backwards. ## Seats and Plans The **Microsoft** card lists one plan per Copilot product your tenant holds, with its seats, for example *40 / 50 used*: * **Microsoft 365 Copilot** * **Microsoft 365 Copilot (Education)** * **Microsoft 365 Copilot for Sales** * **Microsoft 365 E7** A licence that includes Copilot but is not one of these, such as Copilot Business, appears under the name Microsoft gives it in its licence list. **Total** is the number of seats your tenant has bought and that are active. **Used** is how many of those are assigned to people. Velatir counts a licence as a Copilot seat when it includes Microsoft 365 Copilot, whichever product it was bought as. Two things the Microsoft card does not show: * **A billing cycle.** Microsoft does not report whether a licence is billed monthly or yearly. * **Usage concentration.** That figure is a share of tokens, and Microsoft does not report token counts for Copilot. ## Managing the Connection When the connection shows **Action needed**, the alert on the card says why and offers **Reconnect**. Reconnecting runs the same Microsoft sign-in and approval again. Your existing access stays in place until the new approval succeeds, and imported data is kept. Select **Disconnect** on the **Microsoft** card and confirm. Velatir deletes its approval for the tenant and stops reading from it straight away. Everything already imported stays in Velatir, and the declared Microsoft services stay in the inventory. Disconnecting in Velatir does not remove the **Velatir Connector** app from your tenant. Remove it in Entra as well if you do not plan to reconnect. You can remove Velatir's access from Microsoft's side at any time. In the Microsoft Entra admin center, open **Enterprise applications**, select **Velatir Connector**, and either delete the app or revoke its permissions. Velatir checks its access every 15 minutes, so the connection shows **Action needed** within that time, with *Access to Microsoft was removed*. Velatir stops reading. Everything already imported stays. One connection reads one Microsoft tenant. To add another, select **Add connection** in the card's **Connections** section and sign in with an admin account from that tenant. *** Every permission on the consent screen, and why Velatir asks for it. What is read from Microsoft, what is kept, and what is left out. What each alert means and how to fix it. How connectors work in general. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.