Teaching an ERP to
document itself.

Data everyone has. Context no one can find.

MSA's Dynamics 365 ERP had evolved faster than its documentation. The result: analysts wasting time on trial-and-error queries, business logic locked in a few people's heads, and a data dictionary nobody trusted.

Five tools. One seamless pipeline.

Built entirely within MSA's existing Microsoft 365 ecosystem — no new vendors, no new platforms, no additional training overhead.

Four components. One living data dictionary.

• 1
  Automated ETL pipelines in Microsoft Fabric

  Designed Lakehouse-to-Warehouse pipelines that continuously extract SQL metadata from Dynamics 365. Custom stored procedures query INFORMATION_SCHEMA views and upsert into staging tables — preserving business definitions while refreshing technical fields on every run.
• 2
  Stored procedure management via Fabric Copilot agents

  Automated the continuous maintenance of stored procedures so documentation evolves in sync with the schema. Columns added, renamed, or dropped — the pipeline adapts without manual rework.
• 3
  Conversational Copilot Studio agent

  A prompt-engineered agent that lets data users query definitions in natural language and knowledge owners validate or update them through conversation — no forms, no spreadsheets. Deployable in Teams, Outlook, or any Microsoft tool with a single click.
• 4
  Power Automate orchestration layer

  Two flows merge Fabric-sourced technical metadata and agent-submitted business definitions into a unified SharePoint list — a single, always-current source of truth for enterprise data knowledge.

Documentation that feels like a conversation.

The agent was designed around one rule: meet users where they already work, and make contributing feel effortless. Here's a real interaction from the prototype.

Tested across three dimensions.