Question 44 — AB-650 Practice Exam 2
A company has a proprietary knowledge repository for which no ready-to-use connector exists. The company wants the repository's content searchable through Copilot's normal Microsoft Graph grounding and requires the source permissions to remain associated with indexed items. What should the company implement? (Select one answer)
A custom synced connector built with the Microsoft Graph connectors API
A federated connector built as a custom Model Context Protocol implementation
A Microsoft-published federated connector with per-user OAuth 2.0 authentication
A federated connector that stores a copy of each retrieved record in Microsoft Graph
Correct answers
A custom synced connector built with the Microsoft Graph connectors API
Explanations
Correct:
A custom synced connector built with the Microsoft Graph connectors API
Synced connectors can be developed for organization-specific sources through the Microsoft Graph connectors API. They index external content into Microsoft Graph and carry source permissions with the indexed information, making this model suitable for a proprietary repository that needs standard Copilot grounding.
Wrong:
A federated connector built as a custom Model Context Protocol implementation
Federated connectors currently do not support custom connectors. The available federated model uses Microsoft-published connectors.
A Microsoft-published federated connector with per-user OAuth 2.0 authentication
Federated connectors retrieve information live rather than indexing it into Microsoft Graph, so this model does not satisfy the requirement for indexed Copilot grounding.
A federated connector that stores a copy of each retrieved record in Microsoft Graph
Federated connectors do not copy or persist source content in Microsoft 365. Their purpose is to retrieve information live while leaving it in the system of record.