Skip to main content

​
Set up for yourself

Works on all plans. Your own connection works in Ask Jamie, Sidekick, briefings, and your own workflows. You choose what Jamie can reach: files, Outlook, Teams, and Planner. For each one, you choose read only, or read and write.

In Microsoft 365

Nothing to prepare in most cases. You sign in with your own Microsoft login.Some organizations let only an admin approve apps. Then a Microsoft admin approves Jamie once for everyone. See Microsoft’s guide to granting admin consent

In Jamie

  1. Open Settings → Agent → Connectors
  2. Find Microsoft 365 and click Connect. The Microsoft 365 permissions dialog opens, with one card per permission
  3. On a card you want, click Connect read or Connect read and write
  4. In the popup, sign in to Microsoft and approve access. If you connected your Outlook calendar to Jamie, use the same Microsoft account
  5. Repeat the last two steps for every card you want. Each card is a separate approval
  6. If Microsoft says that your organization needs an admin to approve Jamie:
    • On the card, click Needs admin approval?
    • Click copy read link or copy read and write link
    • Send the link to your Microsoft admin
    • After your Microsoft admin approves Jamie, connect again
Within the permissions you approve, Jamie sees what your Microsoft account can see. Every email, message, event, and file that Jamie creates shows as yours. Jamie drafts email by default. It sends email only when you ask. If you don’t say where to save a file, Jamie saves it in your OneDrive, in a folder called “Jamie Meeting Notes”. Later, you can connect more permissions, or change a card from read to read and write. Open Microsoft 365 and use the cards under Permissions. If you’re a workspace admin, these cards are under Permissions (personal).

​
Set up for the workspace (admins only)

Needs the Team or Enterprise plan. Only workspace workflows use this connection. It covers SharePoint and OneDrive files only. Mail, calendar, Teams, and Planner stay personal. Jamie signs in as a service account: a Microsoft work account that your team creates only for Jamie, not a person’s own login.

In Microsoft 365

  1. Create a work account for Jamie, such as jamie@yourcompany.com, with a SharePoint license. See Microsoft’s guide to adding users
  2. Add the service account to the SharePoint sites that your workflows should use. Share each site with it as you would with a colleague. See Microsoft’s guide to sharing a site
  3. If your organization lets only an admin approve apps, a Microsoft admin approves Jamie. A Cloud Application Administrator can do this

In Jamie

  1. Open Settings → Agent → Connectors and select Microsoft 365 to open its details. The Connect button on the row connects your own permissions, not the workspace connection
  2. Under Permissions (workspace), click Connect read or Connect read and write on the SharePoint and OneDrive card
  3. In the popup, sign in to Microsoft as the service account, not as yourself, and approve access
  4. If Microsoft says the app needs approval:
    • Click Needs admin approval?
    • Copy the link
    • Send the link to a Microsoft admin, such as a Cloud Application Administrator
    • After the Microsoft admin approves it, connect again
Workspace workflows see only what the service account can open. They act as the service account, not as the person whose meeting it is. Files that workspace workflows create or change show the service account as their author. So Jamie puts the meeting owner’s name in what it writes. Name the SharePoint library in the workflow. Then Jamie saves files there, not in the service account’s own OneDrive.

​
Permissions and scopes

Jamie uses delegated permissions for Microsoft 365. It acts on behalf of the connected Microsoft account and can access only resources that account can access. This also applies to workspace connections: Jamie acts as the service account. A scope ending in .All does not give Jamie access beyond that account’s permissions. See Microsoft’s explanation of delegated permissions. Each permission card requests the Microsoft Graph scopes below. The Read and write column lists the complete set for that choice, rather than additional scopes to add to the Read column. Every request also includes openid, profile, email, User.Read, and offline_access. These let Jamie sign you in, identify the connected account, and maintain access without asking you to sign in each time. Workspace connections offer only SharePoint and OneDrive, with the same scopes listed above. Teams read access covers chat messages and team and channel names and descriptions; it does not include reading channel messages. The separate Outlook calendar integration requests only Calendars.Read plus the five sign-in and access scopes above. It does not request mail access. For admin approval, use the link from the relevant permission card in Jamie. It requests that card’s scopes plus the shared sign-in and access scopes. The full permissions list in Microsoft Entra can also include scopes for other Jamie integrations.

​
What Jamie can do

What Jamie can do depends on the permissions you approve. Jamie can:
  • Search and read Word, Excel, PowerPoint, and PDF files in OneDrive and SharePoint, and save meeting notes there
  • Read your Outlook mail and calendar, draft email, and create events, including Teams meetings
  • Post to Teams channels and chats, and reply in threads
Jamie can do more than this list. It can’t delete anything in Microsoft 365. Try asking: “Draft a follow-up email to everyone who was in this meeting”

​
Disconnect

  • Your own connection. Open Microsoft 365 in Settings → Agent → Connectors and click Disconnect. Your Outlook calendar in Jamie stays connected.
  • The workspace connection. Under Permissions (workspace), click Disconnect on the SharePoint and OneDrive card. This removes Jamie’s sign-in for the service account. Workspace workflows that use Microsoft 365 pause. They start again when a workspace admin connects Microsoft 365 again. To also block access on the Microsoft side, remove the service account from the SharePoint sites, or disable the account.
Last modified on October 30, 2026