Explanation:
suggested prompts
In Microsoft 365 Copilot, suggested prompts are designed to help users get started quickly and interact with an agent effectively. Microsoft guidance for Copilot agents emphasizes that many users struggle most at the beginning-knowing what to ask, how to phrase requests, and how to take advantage of an agent's purpose.
Suggested prompts address this by providing ready-to-use examples that demonstrate the best ways to engage the agent for its intended scenarios.
Suggested prompts also act as lightweight "guardrails" for good prompting. They show users the expected input patterns, the types of tasks the agent can perform, and the kinds of outputs they can request. This accelerates adoption and improves the quality of results by steering users toward well-structured requests and appropriate context.
By contrast, capabilities describe what an agent can do (tools/features), instructions define how the agent should behave, and agent settings control configuration. None of those are primarily meant to help users begin conversations through example starters.
Therefore, the correct completion is suggested prompts .

Explanation:

Prompt scheduling in Microsoft 365 Copilot enables users to automate recurring AI-driven tasks such as generating reports, summaries, or updates. However, there are defined operational limits to ensure system performance, responsible AI usage, and governance compliance.
First, the most frequent interval at which a prompt can be scheduled is once per day . Scheduling more frequently, such as hourly, is not supported. This limitation prevents excessive automated execution that could strain system resources or generate unnecessary redundant outputs.
Second, a scheduled prompt has a maximum execution limit of 15 times . After reaching this threshold, the schedule must be recreated if further automation is required. This control ensures users periodically review and validate automated prompts for relevance, accuracy, and business alignment.
These constraints reflect Microsoft's enterprise AI governance strategy: balancing productivity automation with performance optimization, cost control, compliance oversight, and responsible AI lifecycle management within Microsoft 365 Copilot environments.

Explanation:
Statements:
You can add a Microsoft Teams chat as a knowledge source to a Microsoft 365 Copilot agent.
The answer: Yes
You can add a Microsoft 365 Copilot conversation as a knowledge source to a Copilot agent.
The answer: No
You can use an image file, such as a JPG file, as a knowledge source for a Microsoft 365 Copilot agent.
The answer: NO
Microsoft 365 Copilot Agent Builder supports grounding agents in approved knowledge sources so responses are accurate and permission-trimmed. Teams chats can be used as a knowledge source: Microsoft Learn confirms you can ground an agent in Teams data, including chat messages (and optionally scope to specific chats), enabling the agent to reference collaboration context when answering questions.
A Copilot conversation itself is not a supported "knowledge source" option; knowledge sources are configured from items like SharePoint content, Teams, email, websites, uploaded files, and connectors-not prior chat transcripts.
Finally, JPG images are not supported as knowledge-source file types . Microsoft's supported file types for agent knowledge include documents like .doc/.docx, .pdf, .ppt/.pptx, .txt, and Excel formats (.xls/.xlsx), but not image formats. Therefore, you cannot use a JPG as a knowledge source for a Copilot agent.

Effective prompting in Microsoft 365 Copilot requires two critical components: clear instructions and grounding in authoritative content. Microsoft guidance emphasizes that prompts should explicitly state the desired output format, tone, length, and purpose. In this case, specifying "a bulleted list of three to five concise, simply worded key points" represents concise instructions, making option B essential.
Additionally, grounding the response in a specific knowledge source-such as attaching or referencing the proposal document-ensures factual accuracy and reduces hallucination. Option D ensures Copilot uses the actual proposal content rather than relying on generalized model knowledge.
Profiles and stakeholder contact details are unrelated to summarization requirements. Therefore, the correct selections are B and D.