How to integrate Microsoft Apps with Sally AI
Connect Sally AI with your Microsoft apps, so Planner, Microsoft To Do and OneNote, and create tasks and notes straight from your meetings.
One click puts your follow-ups into your Microsoft workspace, and all your tools show the same state.
Quick navigation
- How to connect Microsoft Apps with Sally AI
- How to create tasks and notes in Microsoft Apps
- Required OAuth scopes
1. How do I connect Microsoft Apps with Sally AI?
Follow these steps to enable the Sally Microsoft Apps integration.
- Open Settings from the bottom-left corner of the sidebar.
- Under Configuration, select Integrations. If no integration is connected yet, click Discover integrations, otherwise click Add integration in the top right corner.
- In the Add integration panel, pick the Project management category on the left and then Microsoft Apps (Planner, To Do, OneNote). Complete the login on the Microsoft side.
- After the login, the integration appears in the list under the Project management category. Disconnect in the top right corner ends the connection whenever you need to.
If your connected Microsoft account is a personal account, only the option to create a task in To Do
is available.
Other actions, such as creating tasks or comments in Planner or saving meeting notes in OneNote, require a work, school, or university account.
When a personal account is used, these buttons will appear grayed out or unavailable.
Microsoft distinguishes between two main account types:
-
Microsoft account (personal):
A personal account you use to access consumer services like Outlook.com, Xbox Live, or Microsoft Store.
These accounts are usually linked to an email ending with @outlook.com, @hotmail.com, or similar. -
Work, school, or university account:
An account provided by your organization (e.g. a company or educational institution) that gives access to Microsoft 365, Planner, To Do (work), Teams, OneNote, and other enterprise tools.
1.1. Which actions may Sally use?
A connected integration has two tabs, Overview and Actions. The Actions tab defines what Sally offers through this integration, in the Sally chat and after the meeting.
Primary actions are what Sally actively writes into Planner and To Do, meaning listing, creating, updating, commenting on, and completing tasks. Each action explains what it does in the line below it.
Use the toggle on the right to take out a single action that Sally should not use for this organization account.
Not every action shows up in the selection at the meeting. Sally uses some of them itself, in the chat or as part of another action. Leave them switched on so the integration works in full, and switch off only what Sally really should not do in this organization account.
Below that sit the helper functions, the read and search functions that support the primary actions, for example finding a plan or a list. They stay locked as long as an active action needs them.
2. How do I create tasks and notes in Microsoft Apps?
Once the integration is connected, you can send meeting insights from Sally to Planner, To Do, or OneNote with a single click.
You can:
- Create a task in Planner
- Add a comment to an existing Planner task
- Create a task in Microsoft To Do
- Create a page in OneNote
- Create task in Planner for a task in the team plan, with a bucket, an owner, and a due date.
- Add comment to Planner task for extra context on an existing task.
- Create task in To Do for a personal task in your own list.
- Create page in OneNote for documentation that should stay around as text.
2.1. Create a task in Planner
Turn a Sally insight into a new task in Planner.
- Open the meeting in Sally.
- In the summary, hover over a block or over a single entry and click the plug icon. In the list, choose Create task in Planner under Microsoft Apps (Planner, To Do, OneNote).
- Fill in the dialog. Plan, Bucket, and Title are required, and the title already comes prefilled from Sally. Assigned to, Priority, and Due date are optional.
- The description holds the details from the summary where the selected entry has any. You can freely adjust them.
- Click Create task to send it to Planner.
Pick the bucket deliberately and set an owner and a due date right away. The more complete the task, the fewer follow-up questions come back later in the plan.
2.2. Add a comment to an existing Planner task
Add meeting context to an existing task, which suits updates, decisions, or extra notes.
- Open the meeting in Sally.
- Click the plug icon on the block or on the entry and choose Add comment to Planner task.
- In the dialog, pick the plan and the task the comment belongs to. The comment field holds the text from the summary. All three fields are required.
- Click Add a comment to send the comment to Planner.
2.3. Create a task in Microsoft To Do
Create a personal task in your own to-do list.
- Open the meeting in Sally.
- Click the plug icon on the block or on the entry and choose Create task in To Do.
- Fill in the dialog. List and Title are required, Due date is optional. Use the description field to add details.
- Click Create task to put the task into your to-do list.
2.4. Create a page in OneNote
Keep a summary or single notes as a page in OneNote.
- Open the meeting in Sally.
- Click the plug icon on the block or on the entry and choose Create page in OneNote.
- In the dialog, pick the notebook, the section, and the title. All three fields are required.
- The content field holds the details from the summary where the selected entry has any. You can edit and format them in the editor.
- Click Create a page to create the page in OneNote.
Use OneNote for structured meeting documentation and reference material, and Planner and To Do for tasks that someone works off.
3. What OAuth scopes does the Microsoft Apps integration require?
For the integration with Microsoft Apps (Planner, ToDo, OneNote), Sally uses OAuth 2.0 for authorization. The following scopes define which areas Sally can access on behalf of the authenticated user.
-
Sally accesses this information solely to technically establish and maintain the connection to the user account.
-
Sally does not make any autonomous changes. Actions are performed exclusively upon the explicit initiative of the user.
-
API endpoints are only called within the scope of an active action initiated by the user within the platform.
Technical overview of required scopes
| Scope | Type | What Microsoft technically allows with this scope | How Sally uses this scope |
|---|---|---|---|
Calendars.ReadWrite.Shared | Delegated | API permission for shared calendars | Part of Microsoft's permission model. Sally does not independently create or modify calendar events. |
Contacts.ReadWrite.Shared | Delegated | API permission for shared contacts | Technically required within the OAuth model. Sally does not modify contact data. |
email | Delegated | Access to the user's email address | Sally reads the email address to uniquely identify the connected account. |
Files.ReadWrite.All | Delegated | API permission for Microsoft 365 files | Part of the integration permission model. Sally does not independently create, modify, or delete files. |
Group.ReadWrite.All | Delegated | API permission for Microsoft 365 groups | Technically defined by Microsoft. Sally does not alter group structures. |
Mail.ReadWrite.Shared | Delegated | API permission for shared mailboxes | Sally does not access mailbox content or modify emails independently. |
Mail.Send | Delegated | API permission to send emails | Part of the Microsoft OAuth model. Sally does not send emails independently outside explicitly user-initiated actions. |
Notes.Create | Delegated | API permission for note objects | Included in the Microsoft permission model. Sally does not independently create notes. |
Notes.ReadWrite | Delegated | API permission for note content | Sally does not modify existing notes without explicit user action. |
Notes.ReadWrite.All | Delegated | Extended API permission for notes | Part of the OAuth model. Sally does not independently access or alter note content. |
offline_access | Delegated | Issuance of long-lived access tokens | Enables a stable connection without repeated login. No Microsoft data is modified. |
openid | Delegated | OpenID Connect authentication | Secure authentication via Microsoft Identity. |
People.Read | Delegated | Read access to contact information | Sally reads basic information for display within the integration. No contact data is modified. |
ShortNotes.ReadWrite | Delegated | API permission for quick notes | Technically defined within Microsoft's model. Sally does not independently modify quick notes. |
Sites.Manage.All | Delegated | API permission for SharePoint sites | Part of the permission model. Sally does not modify SharePoint site structures. |
Sites.ReadWrite.All | Delegated | API permission for SharePoint content | Sally does not independently create or modify SharePoint content. |
Tasks.ReadWrite | Delegated | API permission for task objects | Technically defined within the OAuth model. Sally does not modify tasks without explicit user action. |
Tasks.ReadWrite.Shared | Delegated | API permission for shared tasks | Sally does not independently interfere with team tasks. |
User.Read | Delegated | Read basic user information | Sally reads basic account information for authentication purposes. |
User.ReadBasic.All | Delegated | Read basic information of other users | Sally reads this information solely for display within the integration. |











