Dynamics 365 Knowledge Management: Articles, Copilot and Agents (2026)

Abstract illustration of stacked translucent teal glass panels like pages in a library, with one panel glowing orange at the center, representing a trusted knowledge article

Last updated: November 17, 2026

By ZapAI Team

Copilot in Dynamics 365 Customer Service answers from your knowledge base, so every answer is only as good as the articles behind it. Our Dynamics 365 Customer Service consultants build that knowledge layer for mid-market US support teams. This guide covers the article lifecycle, search providers, Copilot knowledge sources, the Customer Knowledge Management Agent, self-service, licensing, metrics, governance and our decision rules, checked against Microsoft Learn on November 17, 2026.

Dynamics 365 knowledge management is the built-in system for writing, reviewing, publishing and searching knowledge articles in Customer Service. The same published articles feed the representative search pane, Copilot’s Ask a question feature, Power Pages portals and Copilot Studio agents, so one governed knowledge base serves every channel.

Picture a hypothetical support team. Copilot goes live on a Monday. By Wednesday, a representative reads a confident answer to a customer about a return policy that changed last spring. Nobody touched the article in a year. Copilot did exactly what it was built to do. The article failed.

Our Dynamics 365 Customer Service guide gives the broad product overview, covering licensing, agents and channels, and it mentions knowledge only in passing, which is why this post goes deep on a single question instead. How do you build a knowledge base that representatives, customers and Copilot can actually trust?

What Is Dynamics 365 Knowledge Management?

It’s a set of features for authoring, categorizing, delivering, analyzing and sharing articles. Microsoft’s knowledge management overview, updated September 30, 2026, splits the work by role. Authors write. Admins configure. Representatives search and rate. Supervisors read the analytics.

ComponentWhat it doesWho owns it
Knowledge articlesRich text articles with versions, translations, categories and productsKnowledge authors and managers
Article templatesPrefilled fields and sections for consistent structureKnowledge manager
Business process flowMoves articles through author, review, publish stagesKnowledge manager
Knowledge search controlSearch pane on case and conversation forms, plus smart assist suggestionsCRM admin
Search providersBring SharePoint, other orgs, Graph connectors or sitemap websites into searchCRM admin
Copilot knowledge sourcesGround Ask a question and email drafts in published articlesCRM admin
Customer Knowledge Management AgentDrafts articles from resolved cases and conversationsKnowledge manager with admin
Knowledge analyticsArticle insights and search term insights dashboardsSupport supervisor

Two defaults matter on day one. Knowledge management is turned on for the Case and Conversation record types out of the box. And Microsoft’s configuration guide says the security boundary for the KnowledgeArticle table is the environment, not the individual user. Don’t put secrets, credentials or regulated personal data in draft or internal articles. Microsoft says so plainly.

How Does the Knowledge Article Lifecycle Work?

Draft, review, publish, expire. Each step has a setting that teams skip and later regret.

Authoring and templates

Start with templates. A template prefills fields such as language, title, keywords and subject, and it keeps branding, tone and structure consistent across every author, whether that author is a senior engineer or a new hire in week two. Set a default authoring language for the org too, and decide whether users can override it. Copilot form fill can suggest keywords and descriptions, which saves time on the fields authors tend to leave blank.

One gap surprises people. Duplicate detection rules don’t work on the Knowledge Article table. Your template and your review step are the only guards against two articles answering the same question differently.

Review, approval and publishing

Articles move through a business process flow. An author submits, a reviewer approves, and a publisher schedules. Per Microsoft’s publishing guide, publishing needs the Publish and Update permissions on the Knowledge Article record type, which ship by default with the knowledge manager, customer service manager, customer service representative and system administrator roles.

Read that role list twice. Representatives can publish by default. That’s rarely intended. If you want a real approval gate, trim the Publish privilege from the representative role and test with a non-admin account.

Five choices appear in the publish dialog.

  • Publish now or on a scheduled date.
  • The status after publishing.
  • An expiration date.
  • The status the article falls into once it expires.
  • Whether approved translations publish along with it.

Versions, translations and expiration

Use minor versions for wording fixes and major versions for real product changes. Microsoft’s versioning page is clear that only one version of an article can be published at a time, and that deleting a version can’t be undone. Keep backups. Once a version is live, only users holding the Publish privilege can update it.

Expiration is the most underused field in the product. Expired articles leave search. That’s exactly what you want for seasonal offers, old firmware and retired policies. Set it on every article that describes something with an end date, and give everything else a review date instead, so an owner gets a nudge to confirm the content before it quietly goes stale.

A loop of small teal glass tiles forming a circle with one orange tile at the top, representing the knowledge article lifecycle from draft to expiration

How Do Representatives Search Knowledge?

Two ways. Smart assist suggests related articles on the case, and the Knowledge search pane lets representatives search on their own. Both sit in Copilot Service workspace. Both need tuning.

Search settings worth changing

Default search mode is any. A search for two words returns articles that match either word. Microsoft lets you switch to all, which returns only articles matching both, and you’ll need Dataverse search turned on for it. We switch it for most mid-market teams because representatives type short, specific queries. Precision wins.

  • Suggest as you type, which matches against article titles.
  • Recently viewed articles for cases, from one to eight.
  • Search filters, with personal saved filters if you allow them.
  • Feedback, so representatives can rate articles.
  • A portal URL format that turns an article number into a shareable public link.

Integrated and external search providers

Your articles won’t live in one place. Few teams do. Microsoft gives you two ways to pull outside content into the same search.

External search providers federate search at query time. Per the external search providers page, you can point at another Dynamics 365 org, a SharePoint site in the same Microsoft tenant, or a Microsoft Graph connector if your company already indexes outside content through Microsoft Search. Representatives only see results they already have access to. Watch one side effect. Once you add even one provider, the configured result count stops applying and each provider shows three articles, with a Show more option.

Integrated search providers work differently. They ingest content from static websites built on the sitemap protocol into Dataverse on a refresh schedule you pick, so a vendor’s public help site or your own product documentation site can show up next to native articles in the same search pane. Test small. The integrated search providers guide lists the rules. Each article URL in the sitemap needs a lastmod tag. Sites that load content with scripts aren’t supported. A trial ingestion caps at 1,000 articles, so check the crawl failures column before you activate anything.

Both options apply to Customer Service and the standalone Contact Center. Ingested content lands in Dataverse, so budget for it. Our Dataverse storage capacity guide explains how database and file capacity are counted.

How Does Copilot in Customer Service Use Knowledge?

Through the Copilot help pane. Representatives use Ask a question to chat with Copilot about a case, and Copilot drafts emails and chat replies. Grounding starts off.

Microsoft’s Copilot help pane configuration page, updated September 10, 2026, says you first select the option to include a knowledge base and then choose your organization’s knowledge base as the source, because nothing is grounded by default. Copilot then reads only the content field of the article. Nothing else. It uses articles tagged with the same language as the user interface. And it only uses the latest version, in the Published state.

Copilot featureDynamics 365 knowledge baseExternal web resourcesCopilot Studio knowledge sources
Ask a questionYesNoYes
Write an emailYesYesNo

Three settings shape answer quality more than any other. Start there.

  • Custom instructions of up to 5,000 characters, which apply only when your Dynamics 365 knowledge base is the selected source.
  • Filters. Preset filters run silently, representative filters appear in the pane, and automated filters follow the record. You get up to five per category.
  • Extend with Copilot Studio, which lets you add tools and other knowledge sources such as SharePoint.

Be careful with trusted webpages. You can add up to five domains for email drafting, but Microsoft’s own caution box says this option relies on the Bing Search API, which is deprecated, so results might not work as expected. Skip it for now. We’d keep policy answers inside your own articles instead.

Pointing Copilot at SharePoint also inherits every permission mistake in that SharePoint. Check first. Our post on Microsoft 365 Copilot oversharing covers how to find overshared sites before an AI does.

What Does the Customer Knowledge Management Agent Do?

It turns resolved cases and closed conversations into draft articles. It drafts. People decide. Microsoft’s 2025 release wave 2 plan lists public preview on March 31, 2025 and general availability on October 31, 2025. That release plan page is now archived, and a few features inside the agent are still labeled preview.

Per the agent admin guide, updated July 29, 2026, it works in two modes.

  • Real-time creation runs when a representative resolves a case or closes a conversation. The agent compares the content with existing articles and creates one only if it decides a new article is needed. Rules can limit which cases qualify.
  • Historical creation scans past cases and conversations that match your rules. It can process up to 100,000 records, can’t be stopped once started, and Microsoft recommends running it in batches.

Settings that decide whether you can trust it

Set the default compliance state to Pending. That’s the gate. Reviewers then mark articles compliant before anything publishes, and articles marked Noncompliant can’t be published at all. Auto publishing is optional and can target internal audiences only, or internal and external audiences, which includes portals.

Defaults are worth knowing. Articles come out in a three-part format covering the issue, its cause and how it was fixed, unless you assign a custom template per historical rule. Automatic minor updates to existing articles are a production-ready preview. Up to five custom record types can feed the agent, also in preview. Microsoft also notes that the agent removes personal data before drafting but might not catch every instance of sensitive information. Keep a human reviewer.

Prerequisites trip teams up. You need knowledge management configured, Copilot access to the knowledge base turned on, pay-as-you-go billing set up, and connection references for the agent’s flows in the Copilot Service admin center. Microsoft also recommends turning on track changes for mapped tables before historical runs.

Copilot knowledge drafts from cases

There’s a lighter option for teams not ready for an agent. Representatives tick a box on the Resolve Case dialog and Copilot drafts an article in a chosen template and language, which suits teams that want each representative to own the article for the problem they just fixed. They can revise it with instructions up to five times before saving it as a proposal. Microsoft’s documentation still labels this a preview feature. Pilot it in a sandbox.

Several scattered teal glass fragments flowing into one solid orange glass block, representing resolved cases turned into a knowledge article

How Do Power Pages and Copilot Studio Reuse the Same Knowledge?

Same articles, different audience. The Internal field decides who sees what.

On a Power Pages site, knowledge articles are searchable only when they’re Published and the Internal field is set to No, and Microsoft’s Power Pages search documentation says that rule can’t be changed. Search runs on Dataverse search. Customers can filter by rating and product, and attachment content can be indexed through a site setting. Our Power Pages customer portal guide covers licensing and when a portal is worth building.

Copilot Studio agents reach the same content through a Search Dynamics 365 knowledge articles action. Per Microsoft’s integration guide, the default filter returns only published external articles, and Dataverse search must be on. Agents can also use SharePoint, uploaded documents, public websites and Dataverse tables as knowledge sources, according to the Copilot Studio knowledge sources summary.

Turn off Allow ungrounded responses for any customer-facing agent. With it off, the agent blocks answers in turns where it didn’t use a knowledge source or tool. Test before launch with our Copilot Studio agent evaluation approach, and price the run cost with our Copilot Studio pricing guide. Our Copilot Studio services team builds these agents when you’d rather not.

Which Licenses Do You Need in November 2026?

Every tier includes knowledge authoring. Copilot and the agent are where tiers split. These rows come from Microsoft’s Customer Service pricing page, read November 17, 2026.

CapabilityProfessional ($50)Enterprise ($105)Premium ($195)
Knowledge management including authoringIncludedIncludedIncluded
Copilot in Dynamics 365 Customer ServiceNot includedIncludedIncluded
Customer Knowledge Management AgentRequires Copilot CreditsRequires Copilot CreditsIncluded capacity
PortalsNot includedIncludedIncluded
Self-service chatbots and IVRNot includedNot includedIncluded

Prices are US list per user per month, paid yearly. Read the footnotes. Premium includes base Copilot Credit capacity, per a footnote on that page, but Microsoft doesn’t publish a per-article credit cost for the agent that we could find in any source we checked this month. Check your agreement, and see our Dynamics 365 overview for where Customer Service sits next to the other apps.

Which Metrics Show the Knowledge Base Is Working?

Start with what Microsoft already measures. The knowledge analytics dashboards come in two parts, plus a third report for the agent.

DashboardMetrics worth a weekly lookWhat it tells you
Article insightsViews, visitors, average feedback rating, linked cases, sharesWhich articles representatives actually use
Search term insightsRate of no-result searches, engagement rate, top terms with no resultsWhere the knowledge gaps are
Agent overall performanceArticles by status, average quality score, articles to revise, usage by CopilotWhether agent-drafted articles hold up

Know the limits. Search term insights covers internal searches only and says nothing about customer behavior on your portal. The agent’s overall performance report flags articles to revise when their quality score is two or lower, and that view is still marked preview on Microsoft’s analytics page.

Deflection isn’t built in. In our practice, we estimate it by comparing portal and agent sessions that ended without a case against total self-service sessions, then trend that ratio month over month rather than chasing a single number. We won’t quote benchmarks. Your own baseline is the only one that counts.

How Should You Govern Knowledge Content?

Give every article an owner. Not a team, a person. Owners fix things. Owner is already a field on the article insights dashboard, so use it.

Here’s the cadence we use with clients, and it’s our practice opinion rather than Microsoft guidance.

  • Weekly, review the top no-result search terms and write or fix the missing articles.
  • Monthly, review every article with low ratings or a quality score of two or lower.
  • Quarterly, have owners confirm or retire their articles, starting with the most linked.
  • On every product or policy change, open a minor or major version the same day.

Stale content is the real risk with Copilot. A wrong answer used to sit quietly in one article that a few representatives might open, but now Copilot repeats it in every chat where someone asks the same question. Our AI governance framework puts knowledge ownership alongside the other controls an AI rollout needs.

A grid of teal glass cubes with a few dimmed cubes and one bright orange cube, representing owned, reviewed and stale knowledge content

Dynamics 365 Knowledge Base vs SharePoint vs a Third-Party KB

Most teams mix them. Here’s how the three sources compare inside Customer Service.

FactorDynamics 365 knowledge baseSharePoint as a knowledge sourceThird-party knowledge base
Lifecycle controlsTemplates, approval flow, versions, translations, expirationDocument library versioning and SharePoint permissionsWhatever the vendor provides
Copilot Ask a questionNative sourceThrough Copilot Studio extensionThrough Copilot Studio connectors
Representative searchNativeExternal search providerIntegrated provider for sitemap sites, or a Graph connector
Customer self-servicePower Pages with Internal set to NoNot built for public portalsThe vendor’s own portal
AnalyticsArticle and search term insightsOutside Customer ServiceOutside Customer Service
Best forCustomer-facing answers and policyInternal procedures and long documentsContent you can’t migrate yet

Our take on storage choices is close to the one in our Dataverse vs SharePoint lists post. Put structured, governed, customer-facing answers in Dataverse. Leave long internal documents in SharePoint.

Knowledge Base Readiness Checklist

Run through this before you switch on Copilot grounding or the agent. Be honest.

  • Every published article has a named owner and a review or expiration date.
  • Templates exist for your top three article types.
  • The Publish privilege sits only with roles that should publish.
  • Internal and external articles are flagged correctly.
  • Dataverse search is on, and search mode is set deliberately.
  • Duplicate articles on the top 20 case reasons are merged.
  • Article language tags match the UI languages representatives use.
  • Knowledge analytics and search term insights are enabled.
  • Copilot knowledge source, filters and custom instructions are configured and tested.
  • For the agent, pay-as-you-go, connection references and a Pending compliance default are in place.

ZapAI Decision Rules for Knowledge Management

These are our practice opinions, drawn from projects rather than Microsoft guidance. Treat them as defaults, then adjust.

SituationOur rule
Published articles with no named ownerAssign owners and clean up before turning on Copilot grounding
Representatives can publish by defaultRemove the Publish privilege and route through a reviewer
First run of the Customer Knowledge Management AgentReal-time creation only, Pending compliance, no auto publish
Years of historical casesRun historical creation in small batches by product or subject
Policy content lives in SharePointMove customer-facing policy into articles and keep SharePoint for internal procedures
Self-service portal plannedFix internal search and no-result terms first, then publish external articles
Customer-facing Copilot Studio agentUngrounded responses off and an evaluation set built from real case questions

Above all, never let an AI publish to customers before a person has owned that topic for at least one review cycle, because the first wrong answer a customer reads is the one they remember and repeat to everyone else.

Wrapping Up

Knowledge comes first, Copilot second. Get owners, templates, the approval gate and expiration dates in place. Then turn on search term insights, ground Copilot in published articles, pilot the agent with a Pending default, and reuse the same articles on Power Pages and in Copilot Studio. Routing and channels matter too, and our sister guides on Dynamics 365 unified routing and the Dynamics 365 Contact Center cover them.

ZapAI is a Microsoft Dynamics 365, Power Platform, Fabric and AI consulting firm in Irving, Texas, working with businesses across Dallas-Fort Worth and nationwide. Our Customer Service team sets up knowledge management, Copilot grounding and the knowledge agent for mid-market support teams. Curious where your articles stand? Ask for a knowledge base readiness review, and we’ll look at ownership, search gaps and Copilot settings with you.

Questions Support Leaders Ask About Dynamics 365 Knowledge Management

Is knowledge management included in Customer Service Professional?

Yes. Microsoft’s pricing page lists knowledge management, including authoring, in Professional, Enterprise and Premium. Copilot in Customer Service isn’t included in Professional, and portals aren’t either.

Does Copilot use draft or expired articles?

No. Copilot uses the latest version of articles in the Published state, tagged with the same language as the user interface. Expired articles also drop out of search.

Is the Customer Knowledge Management Agent generally available?

Microsoft’s release plan lists general availability on October 31, 2025. Automatic article updates and custom record types are still preview, and Professional and Enterprise need Copilot Credits to run it.

Can Copilot answer from SharePoint?

Yes, by two routes. For representative search, add SharePoint as an external search provider. For Ask a question, extend Copilot with Copilot Studio and add SharePoint there. Either way, users only see content they can already access.

How do we stop internal articles showing on our portal?

Keep the Internal field set to Yes. Power Pages only shows published articles where Internal is No, and Microsoft says that rule can’t be changed.

What metric shows knowledge gaps fastest?

Top search terms with no results, from the search term insights dashboard. It covers representative searches only, so pair it with portal search logs for customers.

Should the agent auto publish articles?

Not at first. That’s our practice opinion. Start with a Pending compliance default and human review, then allow internal auto publishing once quality scores hold steady.

Leave a Reply

Your email address will not be published. Required fields are marked *

Book a free consultation