4.2.2. Knowledge Sources for In-App Help and Guidance
F&O apps are complex — hundreds of forms, thousands of fields, business processes that span multiple modules. In-app help powered by Copilot can surface contextual guidance, but only if the knowledge sources are well-designed.
💡 First Principle: In-app help is a retrieval problem. Copilot's helpfulness is bounded by the quality, relevance, and freshness of its knowledge sources. Connect the wrong sources, and users get generic Microsoft documentation when they need company-specific procedures.
Knowledge Source Hierarchy:
| Source Type | Priority | Content | Example |
|---|---|---|---|
| Organization-specific | Highest | Internal SOPs, business process guides, configuration docs | "How to process intercompany invoices in our D365 Finance setup" |
| Industry guidance | Medium | Regulatory requirements, compliance checklists, industry best practices | "GAAP revenue recognition rules for SaaS contracts" |
| Microsoft documentation | Baseline | Product documentation, feature guides, known issues | "How to configure budget control in D365 Finance" |
Design Decisions:
The architect determines which knowledge sources Copilot can access, how they're prioritized, and how they're maintained. The most common failure is connecting too many sources without prioritization — Copilot returns a Microsoft Docs article about a feature when the user needs their company's specific configuration procedure.
Design knowledge source interoperability so that the F&O agent chat can pull from Copilot Studio knowledge bases, SharePoint document libraries, and custom APIs. This requires configuring the agent chat's data boundaries and ensuring knowledge sources are indexed and refreshable.
Multi-country design: Structure knowledge in layers: a shared global policy base plus a separate regulatory guide per country, so common content is reused while each jurisdiction's rules stay isolated rather than merged into one ambiguous index. Drive retrieval from the user's legal entity context so users never have to state their country in each query. Translating one country's guidance doesn't help, because the countries differ in regulation, not just language; a separate agent per country makes users pick their jurisdiction by hand and copies the shared global content twelve times.
⚠️ Exam Trap: A scenario describes F&O users getting generic help responses instead of organization-specific guidance. A distractor suggests "fine-tuning the Copilot model on company data." The correct answer involves configuring knowledge sources and their priority — Copilot in D365 uses retrieval-augmented generation, not custom model training.
Reflection Question: A multinational company uses D365 Finance across 12 countries, each with different regulatory requirements for financial reporting. How would you design the knowledge source architecture so that in-app Copilot help provides country-specific guidance?
