Dynamics 365 finance and supply chain — AI features and knowledge

The finance and supply chain side of Dynamics, and a section on knowledge sources
that carries a governance point worth more than the product detail around it.

Orchestrating the AI features

Start from the process. Which decisions are slow, or made on stale
information? Which steps are pure data assembly? AI features are configured into
a process rather than bolted onto one.

Prefer what ships. Enable and configure the built-in capability first. It is
maintained, supported and upgrade-safe. Custom is the exception you justify, not
the default you reach for.

Cross-app reality. Finance and supply chain questions often touch
customer-facing data too, so design for the process rather than the module
boundary. The boundary is an artefact of how the software is packaged, not of how
the work happens.

In-app help, guidance and extra knowledge sources

The requirement. The finance and operations agent chat should answer from
your material, not only from Microsoft's product documentation. Otherwise it
can explain the software beautifully and tell you nothing about how your
organisation actually runs it.

The process to recommend, and this is the part to remember in order:

Identify the authoritative internal content, and its owner. Add it as a
knowledge source to in-app help and guidance. Apply the five grounding dimensions
from card 5 before you connect it. And put it under change control, because
knowledge changes behaviour with no deployment.

Interoperability. The agent chat should reach additional knowledge sources
rather than only product help — and the same permission rules apply, because
grounding inherits the user's entitlement. It shows people what they could already
reach, faster.

Exam trap. Adding a knowledge source is a governed change, not a
configuration tweak. It alters what the agent says immediately, with no
deployment and no release note — which is exactly why the correct answers pair
it with ownership, review and versioning.

The one line to carry: knowledge changes behaviour without a deployment, so it
needs the same discipline as code and rarely gets it.

Goes with: card 38 for the named agents, including Finance's Account
Reconciliation Agent and Supply Chain's Supplier Communications Agent.