> ## Documentation Index
> Fetch the complete documentation index at: https://docs.blinq.me/llms.txt
> Use this file to discover all available pages before exploring further.

# Connecting Outlook to Blinq

> Authorise Blinq against your Microsoft 365 tenant and choose whether to export your existing contacts.

Connecting Outlook is a single authorisation from your Blinq dashboard, done by someone with administrator access to your Microsoft 365 tenant.

## Connect Outlook in Blinq

<Steps>
  <Step title="Open your integrations">
    In the Blinq [dashboard](https://dash.blinq.me), go to **Settings**, then the **Integrations** tab.
  </Step>

  <Step title="Start the connection">
    Under **Export contacts**, find **Outlook** and select **Connect**.
  </Step>

  <Step title="Sign in to Microsoft">
    Sign in with an account that has administrator access to your Microsoft 365 tenant.
  </Step>

  <Step title="Grant consent">
    Review what Blinq is asking for and approve it for your organisation.
  </Step>

  <Step title="Choose whether to export now">
    Decide whether to export the contacts already in your workspace straight away.
  </Step>

  <Check>
    **Outlook is connected.** It now shows a **Settings** button in your integrations list. Next, [choose when contacts export](/integrations/outlook/configuring-blinq).
  </Check>
</Steps>

<Warning>
  **Being an Exchange administrator often isn't enough.** The consent step covers your whole tenant, and in practice it usually needs a **Global Administrator**. If the sign-in works but consent fails, that's the reason — ask a Global Administrator to complete this step rather than retrying.
</Warning>

## Using a service account

Because the connection belongs to the account that authorised it, it's worth using an account that will outlast any one person. A Microsoft administrator service account added to your Blinq workspace as an admin works well here. It doesn't need a card, and it doesn't change your billing.

## What Blinq asks for

The consent screen covers reading and writing contacts across mailboxes in your tenant, because Microsoft doesn't offer a way to scope the permission to a subset of mailboxes. This comes up in security reviews — if your IT team needs the exact permissions in writing before approving, email [support@blinq.me](mailto:support@blinq.me) and support can supply them.

<Info>
  Don't see Outlook under **Export contacts**? Check your plan first, then contact [support@blinq.me](mailto:support@blinq.me).
</Info>

<hr />

### Need help?

For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me).