Copilot help pane: in-app answers about product capabilities

What it does

A side pane inside Customer Insights - Data that answers questions about how the product works, in natural language, from Microsoft's own documentation, troubleshooting guides and team blogs. It answers questions about the application, not about your customer data — that's the other Copilot.

Key facts

Preview. Same caveat as the rest of the Copilot capabilities here: not meant for production use, may have restricted functionality.
Available on every page of Customer Insights - Data except the segment create and edit pages, where the dedicated segment creation Copilot takes over instead.
Answers come from Microsoft documentation, troubleshooting content and Microsoft team blogs about Customer Insights setup. It is not reading your tenant, your data, or your configuration.
Each answer carries numbered references back to the source pages, so you can check where a claim came from.
Conversation history persists while the pane stays open and is cleared when you close the app. There's no saved history to go back to.
The Reload button in the pane header clears the conversation on demand.
Documented availability is the United States and Switzerland, with language and region coverage tracked in the Copilot International Availability report.
Gated by the same admin consent as everything else — Enable Copilot features powered by Azure OpenAI in Settings > System > Consent, default On, Customer Insights - Data admin role required to change it.
Turning that consent off removes this pane along with every other Copilot capability. There's no way to keep the help pane and disable the data-facing ones.
It has a responsible AI FAQ of its own alongside dialog with data and segment creation, which is the set of three documented AI capabilities in this app.

When to use / skip

This is the least glamorous Copilot capability in the product and quietly the most useful one during a delivery. A consultant three weeks into a build who wants to know why a data source refresh is behaving oddly gets a referenced answer without leaving the app. The numbered citations are what make it worth anything — you follow the link, read the actual page, and treat the summary as navigation rather than truth.

Where it genuinely helps is client enablement. Handing a client's admin team a product they'll use monthly means they forget everything between sessions, and an in-app answer with a link to the right doc page beats a Teams message to you at 4pm on a Friday.

Skip it as a support strategy. It answers documentation questions, so it cannot tell anyone why their ingestion failed, why their match rules produced the profile count they did, or what their configuration should be. Clients who assume otherwise will be disappointed in a specific and repeatable way. It's also preview, so it doesn't belong in a support model you're contractually committing to.

Configuration decisions

Whether the tenant leaves the global Copilot consent on. That single decision covers this pane too — you can't scope consent to the harmless capability.
Whether client-side documentation and runbooks reference the help pane as a first-line self-service route, given it only knows Microsoft's public content and nothing about the client's build.
What you tell users about the distinction between this pane and dialog with data, because in the UI they're both "ask Copilot a question".
Whether the client's own build documentation needs to live somewhere the help pane can't reach, and how you signpost that instead.
For non-US/Switzerland environments, the same cross-geography consent question as every other Copilot capability, for a feature that never touches customer data at all.

Gotchas

People assume it can see their environment. It can't. The first time someone asks "why did my refresh fail" and gets a generic troubleshooting summary, expectations reset — do that reset in training instead.
Its absence on segment create and edit pages looks like a bug. It isn't; the segment Copilot replaces it there, and if segment Copilot is also unavailable you get nothing on those pages.
Conversation history disappearing when the app closes surprises people who were mid-investigation. Tell them to copy anything they want to keep.
It answers from public Microsoft content, which lags the product. In a preview-heavy area like this, an answer can describe behaviour that has already changed.
The consent gate is all-or-nothing. A security team that wants Copilot off for data-facing reasons also removes an in-app help feature that touches no customer data, and nobody thinks to mention that at the time.
Region restriction applies even though the pane is only reading documentation, so clients outside the supported geographies lose it for reasons that are hard to explain convincingly.

Consultant notes

Show it during admin handover, not during the sales demo. It's an enablement tool and it's wasted on a sponsor audience.
Teach people to click the numbered references. An unchecked summary of preview documentation is exactly the sort of thing that ends up quoted back at you in a design review.
Set the boundary explicitly in training: this pane knows the product, dialog with data knows your customers, and neither knows your project. Say it once, clearly, and repeat it in the handover pack.
Push back gently if a client wants this counted as a reduction in support hours. It shortens some lookups; it doesn't replace anyone.
Before go-live, check the pane actually appears in the client's environment. If the region or consent state has removed it, you want to know before it's in the training deck.

Worth another look if Microsoft opens this pane up to tenant-specific configuration or environment context.