Microsoft 365 context
Email and Teams context retrieval, calendar reasoning, file discovery, SharePoint knowledge, and Planner operations.
CASE STUDY / 03MICROSOFT 365 / MCP / BUSINESS SYSTEMS
One context. Across your work.
Cross-System Work Action Assistant
An assistant that connects workplace context to business systems through constrained tools and explicit approval.
PROJECT STATUSArchitecture & integration
The challenge.
Work is distributed across messages, meetings, tasks, files, and business records. An isolated chatbot cannot reliably reason over that environment or safely turn its conclusions into changes.
THE OBJECTIVE
Connect Microsoft 365 context with Business Central and Dataverse capabilities, using the sequence read, understand, reason, propose, approve, then write.
Follow the system.
Select a stage to explore its role in the architecture.
SYSTEM FLOW / SELECT A STAGE01 OF 05
STAGE 01
Read context
Retrieve scoped information from Outlook, Teams, Calendar, Planner, SharePoint, OneDrive, and Microsoft 365 search.
STAGE 02
Understand & reason
Resolve cross-source context, calendar constraints, task information, and relevant business records.
STAGE 03
Propose
Prepare a concrete action or structured artifact such as a quotation comparison.
STAGE 04
Human approval
Present consequential changes for explicit approval before they are applied.
STAGE 05
Constrained write
Execute permitted operations through restricted MCP tools and capability allowlists.
What I built.
Business-system integration
Business Central integration through constrained MCP read/create/update capabilities, with destructive operations disabled.
Restricted Dataverse tools
A capability allowlist for safe Dataverse integration and cross-application reasoning.
The choices that matter.
Start from actual work context
Retrieve the relevant evidence across applications before generating a proposed change.
Constrain the tool surface
An agent should have the capabilities its task needs. Business Central destructive operations remain disabled.
Keep the person in control
Separate preparing an action from applying it, and require explicit approval for consequential writes.
Controls, by design.
- User-scoped access, permission trimming, and restricted MCP capabilities for Business Central and Dataverse.
- Destructive Business Central operations disabled.
- Explicit approval for consequential changes across connected systems.
Where the work stands.
I designed and integrated an assistant architecture for cross-system reasoning, structured artifacts, and controlled actions. User-scoped context, restricted tools, and approval gates define how the assistant can interact with connected systems.
Architecture is generalized. Client and operational details remain private.