Microsoft 365 permissions

This page is for the person asked to approve Daslab in a Microsoft 365 tenant. It lists every permission Daslab requests, the ones it does not, and who can use an account once someone has connected it.

One app covers every Microsoft integration

Teams, Outlook, OneDrive, Excel, SharePoint, Power BI and Business Central run through one Microsoft Entra application, and so does Sign in with Microsoft. One admin consent covers all of them, and connecting another integration later does not ask for a second grant.

Admin consent authorizes the application for the tenant. It connects nobody's account and moves no data on its own: each person still connects their own.

What each integration asks for

Every permission is delegated. It acts as the person who connected, and reaches only what that person can already open. "All" in a Microsoft permission name means all the ones this user can open, not everything in the organization.

IntegrationPermissionsIn plain language
Sign in with Microsoftopenid, email, profileWho you are, to sign you in to Daslab. No Graph permission and no refresh token
TeamsTeam.ReadBasic.All, Channel.ReadBasic.All, ChannelMessage.Read.All, ChannelMessage.SendRead the teams and channels this user belongs to and the messages in them, post messages
OutlookMail.Read, Mail.Send, Calendars.ReadWrite, Contacts.ReadRead this user's mail, send as them, read and write their calendar, read their contacts
OneDrive and ExcelFiles.ReadWrite.AllRead and write files and workbooks this user can already reach. Excel uses the OneDrive connection and asks for nothing more
SharePointSites.Read.All, Files.Read.AllRead sites, document libraries and files this user can already reach
Power BIWorkspace.Read.All, Dataset.Read.All, Report.Read.All, Dashboard.Read.All (Power BI Service)List the workspaces, reports and dashboards this user can see, and run read-only DAX queries against their semantic models
Business CentralFinancials.ReadWrite.All (Dynamics 365 Business Central)Read and write Business Central data within this user's own permission sets. It is the only data permission Business Central offers; Daslab's Business Central tools only read

Every integration also requests openid, profile and offline_access: sign-in, the connecting user's name, and a refresh token so the connection lasts past an hour. All of them except SharePoint add email. Teams, Outlook, OneDrive and SharePoint add User.Read, to read the connecting user's profile.

What Daslab does not ask for

Tenant.Read.All for Power BI. That permission reads every workspace in the organization. Daslab does not request it, so Power BI access ends at the connecting user's own workspace memberships.

Any Chat permission in Teams. Teams keeps conversations in two places: channels, inside a team, and chats, the 1:1, group and meeting conversations in the Chat pane. Daslab requests channel permissions only, so it cannot read chats, from a tool or from search: message search runs under the same permissions and returns channel messages only. An agent that should take part in a conversation needs it in a channel.

Private channels follow the same rule. If the connecting user is a member, Daslab reads it like any other channel. If they are not, it is not listed and its messages are not reachable.

A connected account is shared with the workspace unless its owner keeps it

When someone connects a Microsoft account, Daslab asks who can use it: Just me, or Everyone. Outlook starts on Just me: only that person's own jobs can use the mailbox and calendar, and nobody else can, admins included. Teams, OneDrive, Excel, SharePoint, Power BI and Business Central start on Everyone, because they are usually the team's files and channels.

An account shared with everyone can be used by a job any member of the workspace runs, in any scene of the workspace. If someone moves their Outlook to Everyone, a teammate's job can read that mailbox and, once a member approves, send mail from it. Microsoft sees each of those calls as the person who connected the account. The choice can be changed later in the account's settings.

A viewer's job never reads a mailbox, whichever audience the account has.

Writes wait for approval unless a scene or a rule lets them run

These permissions can change something: posting or replying in a Teams channel, sending or replying to mail, creating, changing or cancelling calendar events and answering invitations, uploading files and creating folders in OneDrive, and writing to an Excel workbook. Each of those waits for a member to approve it, with the exact content shown. Reads run without asking.

Two settings change that default:

  • A scene with Ask before actions run switched off, or a job set to auto-approve, runs OneDrive and Excel writes without asking.
  • Mail, Teams posts and calendar events reach people outside the workspace, so neither setting covers them. They run without asking only when they match a rule someone added to the scene's or the job's Always allowed list.

Every write records what let it run: a person's approval, the scene or job setting, or the rule and who added it.

SharePoint and Power BI are read-only in both directions: Daslab requests no write permission for them and ships no write tool.

Granting it

A Global Administrator, Application Administrator or Cloud Application Administrator can consent for the whole tenant:

https://login.microsoftonline.com/{your-tenant-id}/adminconsent?client_id=17f50414-705b-4b6e-ad04-f9d7a5db236f

Alternatively, the first user to connect sees a "Consent on behalf of your organization" checkbox if they hold one of those roles.

17f50414-705b-4b6e-ad04-f9d7a5db236f is the application ID. Check that it matches what your consent screen shows, and that the permissions the screen lists match the table above.

Revoking it

The whole tenant: Microsoft Entra admin center → Enterprise applications → Daslab → Delete. No connection can refresh its token after that, so every one stops, for every user, once its current access token expires, within about 90 minutes. This works whether or not Daslab cooperates.

One account: remove the account in Daslab, which deletes its stored tokens, or have the user revoke Daslab at myapps.microsoft.com.

Removing a person from the workspace does not disconnect accounts they connected. A shared account keeps serving the workspace until someone removes it or revokes it at Microsoft.

What's next

Updated 2026-11-14