Daslab next to Microsoft 365
The tenant grants one application. Teams, Outlook, OneDrive, Excel, SharePoint, Power BI, Business Central and Sign in with Microsoft run through a single Microsoft Entra app, so an administrator consents once and each person then connects their own account. Every scope is delegated, so a job reaches nothing the connecting person could not already open. It is the reference architecture with the Microsoft side named.
What the drawing leaves out on purpose
Chats. Daslab requests channel permissions only, so 1:1, group and meeting chats are unreachable, from a tool or from search. An agent that should be part of a conversation gets put in a channel.
The whole tenant. Power BI runs without Tenant.Read.All, so a report outside the connecting person's workspaces does not exist for the agent.
Writes wait for approval by default
A Teams post, a sent mail, a calendar event, an upload and an Excel range each stop at the approval gate with the exact content. A scene or a job set to approve on its own lets uploads and workbook writes through; mail, Teams posts and calendar events get through without a person only by matching a rule someone added. SharePoint and Power BI ship no write tool, and the Business Central tools only read.
A connected account serves the whole workspace unless its owner keeps it
The person connecting chooses Just me or Everyone. Outlook starts on Just me; the other Microsoft integrations start on Everyone. An account shared with everyone reaches every scene in the workspace, so a mailbox moved to Everyone can be read by a teammate's job and, once approved, sent from, as the person who connected it.
The full list of scopes, who can use an account, the admin-consent link and how to revoke the app are on Microsoft 365 permissions.
What stays the same
Everything else on the reference architecture holds: the scene is the unit you govern, reads go through an account someone connected, and every step lands in a history that cannot be quietly edited.
Updated 2026-11-14