Skip to main content
The Microsoft Loop integration makes your team’s shared working notes available in client work. Ask what the Contoso pricing review workspace says about the test stores, pull a Loop table of open questions into a status update, or save a finished summary as a new Loop page. Hebno cites each page and component it reads, and creates a page only after you confirm. Loop uses your existing Microsoft 365 connection. You do not connect a separate account: you grant Loop’s permissions on top of the Microsoft connection you already have.

​
At a glance

​
Before you start

You need:
  • A work or school Microsoft account with Loop turned on for your organisation.
  • Membership of each Loop workspace you want to use, or access to the Loop components shared with you in Teams, Outlook or OneDrive.
  • An allowed integration. An owner or admin sets Microsoft Loop to Allow under Admin → Connectors → Catalogue.
Loop pages and components are stored as .loop files. Workspace pages are stored in SharePoint Embedded containers, and components shared in chats and email are stored in the sender’s OneDrive. Hebno reads them through Microsoft Graph with these delegated permissions. User.Read, email, openid and offline_access come with every Microsoft integration.
Microsoft 365 admins turn Loop on or off with Cloud Policy settings such as Create and view Loop files in Loop and Create and view Loop workspaces in Loop. If either is off for a member’s group, that member’s Loop content is not available in Hebno either. See the Microsoft Entra admin guide for consent.

​
Connect Microsoft Loop

1

Open connections

Open Settings → Connections and find Microsoft Loop under Knowledge. You can also type / in chat and choose Microsoft Loop.
2

Grant access

Select Grant access if your Microsoft account is connected, or Connect if it is not. Sign in to Microsoft and approve read access. The row shows Connected as with your email address.
3

Allow page creation (optional)

Select Allow page creation on the Microsoft Loop row to add Files.ReadWrite.All. The same button appears on a page card if you try to create first.
If your organisation has enabled Loop for everyone, you see no consent screen. See Enable for the organisation. Disconnecting Loop removes the whole Microsoft connection.

​
What Hebno reads

The Loop workspaces your organisation selects are stored in the knowledge index and searched by meaning, with Microsoft permissions checked at search and again at read. Opening a specific page reads it as it is now, with your account. Only the excerpts a reply used are stored with the conversation as its sources. Images and embedded files inside a page appear as links. Hebno reads their names but not their contents, so open them in Loop when you need them.
Excerpts a reply uses become part of the conversation. Anyone you share the conversation with can read them, even if they are not a member of the Loop workspace.

​
What Hebno writes

Every new page appears first as a confirmation card. You can change any field before you select Confirm.
Confirmation card for Microsoft Loop with editable fields

A Microsoft Loop change pending confirmation. Nothing is written until you confirm.

The page is created in the workspace you pick, under your own account, and other workspace members see it straight away. Hebno never edits or deletes existing pages, changes components shared in chats or email, creates workspaces or changes workspace membership. Linking marks which Loop workspaces belong to an engagement, so you can ask about “the team’s notes” without naming the workspace.
  1. Open the project and select Brain.
  2. Under Linked sources, select Link source, then Microsoft Loop.
  3. Search by workspace name, or paste a Loop workspace link, and select Link.
In chats tagged to the project, Hebno searches the linked workspaces first, and page cards default to them. Each person still opens pages with their own Microsoft access. See Linked records.

​
Use Microsoft Loop in chat

  • Attach: open the + menu, choose Sources → Microsoft Loop, and browse workspace and page, or type to filter titles. Or type / and choose Microsoft Loop.
  • Ask: name the workspace, page or component in your request. For example:
    Summarise the Contoso pricing review workspace and list every open question in its tables.
    Which tasks on the workshop actions page are assigned to Priya Nair and still unticked?
    Save this steering committee summary as a new page in the Contoso workspace.
  • Research runs show a Reviewing Microsoft Loop step, with a chip for each page or component Hebno read.
  • Agents can read linked Loop workspaces on a schedule. Pages an agent drafts appear in agent approvals for review.

​
Troubleshooting