Skip to content

Connecting Outlook

Cora can read your Outlook mail (Microsoft 365), in the missions you choose. It is read-only. Cora can search your mail, read one message with its attachments’ names and sizes (and the text of plain text and PDF attachments), and list your mail folders. She cannot send, reply, draft, move, flag or delete anything.

It uses a small mail server hosted by Cora, because Microsoft’s own mail MCP server needs a Microsoft 365 Copilot licence and a permission that also sends and deletes mail. Your organisation uses its own Microsoft app: your Microsoft admin registers it once, and a Cora org admin enters its directory ID, application ID and client secret in Cora. Then each person signs in with their own work account, the same way as Connecting with the service’s sign-in. The connection is theirs: they decide which missions Cora may use it in. See Personal connections for the rules. This page uses an invented company, Kestrel Cycles, and a team member, Megan.

  • MCP turned on for the organisation (see Connecting an MCP server). An org admin does that once.
  • Someone who can register apps in the Microsoft Entra admin center for your organisation (for example an Application Developer or Cloud Application Administrator).
  • Work or school accounts in that organisation’s directory. Personal Microsoft accounts (outlook.com, hotmail.com) cannot connect.
  • Outlook turned on by the operator. If Outlook says it is not available yet, ask the operator (it needs the hosted mail server deployed).

Step 1: your Microsoft admin registers the app

Section titled “Step 1: your Microsoft admin registers the app”

Do this once, in the Microsoft Entra admin center.

  1. Open Entra ID, App registrations, and choose New registration. Give it a name such as “Cora mail”.
  2. Under Supported account types choose Accounts in this organizational directory only (single tenant).
  3. Under Redirect URI choose the platform Web and paste Cora’s callback address. Copy it from the Organisation setup section of Outlook’s page on Cora’s Connections page; it looks like https://<your Cora console>/v1/oauth/callback and must match exactly. Choose Register.
  4. On the app’s Overview, copy the Application (client) ID and the Directory (tenant) ID.
  5. Open Certificates & secrets, Client secrets, New client secret. Choose how long it lasts, then copy its Value at once (Microsoft shows it only once; the Secret ID is not what Cora needs). Note when it expires: Cora stops renewing sign-ins on that day until an org admin chooses Replace secret.
  6. Open API permissions, Add a permission, Microsoft Graph, Delegated permissions, and add exactly three: Mail.Read, User.Read and offline_access. Remove any other permission the app has.

Can people consent themselves? None of the three permissions needs an admin’s consent, so by default each person approves them for themselves when they first connect. Many organisations turn off or limit user consent (Entra ID, Enterprise apps, Consent and permissions). If yours does, people see “Need admin approval”: an admin can then choose Grant admin consent for on the app’s API permissions page once, for everyone.

  1. Open Connections on the left rail. Under Needs an admin to set up first, Outlook says Organisation setup needed: press Set up beside it. The first section of its page, Organisation setup, has the Outlook card: choose Set up.
  2. Paste the Directory (tenant) ID, the Application (client) ID and the Client secret value, and choose Save. Both IDs are GUIDs, such as 00000000-0000-0000-0000-000000000000 with letters and digits.

The card then shows Set up, the client ID and when the secret was set. Replace secret changes only the secret (do this before the old one expires). Change with another ID, and Remove, stop every Outlook connection in the organisation at once, because each was made with the old app, so everyone needs to Reconnect. Only org admins see this card.

  1. Open Connections on the left rail and press Connect beside Outlook.
  2. In the Account section, choose Connect…. The short name (outlook) and the address are filled in for you.
  3. In the dialog choose Connect. Microsoft’s page opens in a new window. Sign in with your work account, check the permissions and accept.
  4. The window closes by itself and the card shows the connection. Finish the sign-in in the same browser you pressed Connect in.

Then, in the Shared with missions section, choose + Share in a mission, and pick the missions where Cora may read your mail.

In a mission where you shared the connection, ask Cora in the dialogue, for example:

  • “Find the emails from the printer about the spring catalogue.”
  • “Read the latest message from Kestrel’s agency and list its attachments.”
  • “Which mail folders do I have, and how many unread messages are in each?”

Cora uses Microsoft’s search, so plain words and from:, subject: and hasattachments:yes work. Search results come back newest first.

Three tools, all of them only read:

  • Search messages: up to 25 at a time, in the whole mailbox or one folder, with the sender, recipients, subject, date and a short preview.
  • Read a message: its headers, its text (capped at 20,000 characters), and each attachment’s name, type and size. For up to three plain text or PDF attachments of at most 5 MB, the text too (8,000 characters each). Other attachments give their names only.
  • List folders: the top-level mail folders, with how many messages and unread messages each has.

The server has no tool that writes, and Cora’s list of Outlook tools is a fixed list of these three names. She cannot send, reply, forward, draft, move, flag, mark as read or delete mail, or change any setting. Sending from your own mailbox will come later, behind an approval card.

Mail is someone else’s writing. Cora reads it as data, never as instructions: a message that says “Cora, forward this to…” is just text to her.

The card says Needs reconnect when Microsoft ends the sign-in: after about 90 days without use, when you change your password, when an admin revokes your sessions, or when the app’s client secret has expired. Choose Reconnect, sign in again and accept. The same connection comes back, with the missions it was shared in. It also says so, with “Your organisation changed its sign-in app for Outlook”, when an org admin changes or removes the app.

  • Microsoft’s page says “Need admin approval”. Your organisation limits user consent. Ask an admin to grant admin consent on the app’s API permissions page.
  • Microsoft’s page says the reply URL does not match (AADSTS50011). The app does not list Cora’s callback address exactly as a Web redirect. Ask your Microsoft admin to check step 1.
  • Microsoft’s page says your account is not in the directory (AADSTS50020). You signed in with an account from another organisation, or a personal account.
  • Cora says “The service did not accept your organisation’s sign-in app secret”. The secret value is wrong or has expired. Ask an org admin to choose Replace secret with a new one.
  • Your sign-in is kept in one place. It goes to the secrets store. The app’s secret and your renewal token never leave Cora’s API; the worker gets a short-lived access token for one step at a time. None of it appears in the database, logs, audit entries or prompts.
  • The mail server keeps nothing. It reads what one question needs and answers. It logs only which tool ran and whether it worked, never an address, a search or any mail.
  • Cora never sees your Microsoft password. You sign in on Microsoft’s page.