Every service team has that one veteran who knows how to fix everything — and every service team rediscovers, usually the week that person goes on vacation, that their knowledge lives entirely in their head. The knowledge base in Dynamics 365 is the platform’s answer to that problem, and it is far more capable than the “FAQ page” most teams treat it as. Articles have an authoring lifecycle, versioning, keywords that drive search, and a search pane that sits right next to the agent while they work a case.
Here is the full loop: author an article, move it through its lifecycle, publish it, and put it in front of agents where they actually need it.
Authoring an article
In Customer Service Hub, the Knowledge section of the sitemap has Knowledge Articles. Click New and you get a form that is really a small CMS.
Three things on this form earn their keep. The business process flow across the top — Author, Review, Publish — is the article’s editorial pipeline, and it means an article’s maturity is a first-class fact, not a naming convention like “DRAFT – do not use”. The Keywords field feeds relevance search — put the words customers actually say in there (“can’t log in”), not just internal jargon. And the content editor has Designer, HTML and Preview tabs, so you can write visually, drop to markup when the designer fights you, and check how the article renders before anyone sees it.
The lifecycle: more than draft and published
Save the article and open the command bar’s overflow menu. This is where the knowledge lifecycle lives.
The verbs that matter: Approve marks the article as reviewed; Publish makes it visible to consumers of the knowledge base; Create major/minor version lets you revise a published article without editing it live — the published version keeps serving agents while you work on the next one; Translate spins up language variants tied to the original; Archive retires an article without deleting history; and Mark Internal flags content for agents’ eyes only, which matters once a portal exposes your public articles. This is the difference between a knowledge base and a folder of documents: the lifecycle is enforced by the platform, not by discipline.
Publishing
Choosing Publish opens a small panel with more control than you would expect.
You can publish now or schedule it, set an expiration date so time-limited content (a workaround for a bug that will be fixed next release, say) retires itself, and push approved translations out together with the original. Expiration is the underrated one — stale articles are how knowledge bases lose the team’s trust, and an expiry date is the cheapest insurance against that.
Getting articles in front of agents
The payoff is on the case form. Agents search the knowledge base from the Knowledge Search control — in Customer Service Hub it sits in the reference panel beside the case — and search covers title, body and those keywords you filled in. From the results an agent can open the article, email a link to the customer directly, and the system tracks how often each article is viewed and linked to cases. Those counters (on the article’s Analytics tab) quietly tell you which articles earn their place and which ones nobody ever uses.
Two settings notes for admins: knowledge management has to be enabled per entity (cases have it on by default), and if you want articles surfaced automatically as suggestions, that is configurable on the form. Start simpler than that — just get the ten questions your team answers every single week written up, keyworded, and published. That vacation problem takes care of itself.
