In Copilot for Service, there’s currently a disconnect between the different knowledge-grounding experiences used in the 'ask a question' and 'draft an email' features:

• When using internal knowledge base articles (from Dynamics 365), these are available in both features.
• When adding a trusted website via the Copilot Service admin center, this is only accessible when drafting emails – not when using 'ask a question'
• Conversely, if I configure a Copilot Studio model with that website as a knowledge source in the Knowledge Hub, then the website becomes accessible in 'ask a question' — but no longer works for generating replies via the email composer.

This creates two separate knowledge source configurations for two different Copilot experiences (although in the same Copilot model) in the same application, which is confusing for end-users and inefficient for administrators.

Please unify the knowledge grounding mechanism between the 'ask a question' and 'draft an email' features so that KB articles and trusted websites can be used across both features. This would drastically improve usability and reduce redundant content maintenance across two tools.