Choosing an AI agent integration without exposing extra data
Choose between Work IQ, Dataverse MCP and direct APIs using a reusable data-boundary checklist, a hypothetical failure case and clear release conditions.
Stanic & Co.
Perspectives for business leaders
Choose an AI agent integration by defining which records it needs, whose permissions it will use and whether it must retrieve information or take action. For Microsoft business applications, consider Dataverse MCP for environment-specific tools and Work IQ MCP when broader Microsoft 365 and supported business-app context is genuinely needed. Neither choice replaces permission checks. If the task needs predictable retrieval, assess a source API instead.
The decision is not which connector offers the most context. It is which connection can complete a defined task without making unrelated sensitive records available. This article provides a reusable selection and release record for that decision, based on the supplied primary-source evidence for a research date of 18 November 2026. The procedures below are proposed business controls, not vendor-prescribed rules.
Choose an AI agent integration by its data boundary
Start with a task statement that names the records needed and excludes everything else. For example: “Help service staff explain the status of an existing customer case using approved case fields; do not retrieve payroll, recruitment records or unrelated customer accounts.” Then identify where those records live. A request for “CRM context” is too vague to establish whether an integration is appropriately restricted.
Microsoft distinguishes several connection options. Work IQ MCP provides Microsoft 365 and supported business-application context through one MCP server. Dataverse MCP provides direct, environment-specific Dataverse tools or business skills without the broader Work IQ context layer. Application code can also use the Dataverse Ask API for a response grounded in a selected semantic model. These are vendor-specific capabilities, not interchangeable descriptions of all AI connectors. See Microsoft’s Business Applications in Work IQ documentation.
A narrower connection is a useful starting point, but its name is not proof of isolation. Microsoft says environment, app and data permissions still determine accessible business context through Work IQ MCP. It also says existing Dataverse permissions and application controls continue to apply. Therefore, enabling Work IQ does not itself mean every organisational record becomes accessible; equally, choosing Dataverse MCP does not establish that the selected environment contains only appropriate records.
Keep this decision separate from choosing an AI feature or workflow product. The earlier Work IQ or AI Builder comparison addresses that broader fit question. Here, the narrower decision is whether a proposed connection exposes only the context and actions required for one approved task.
Write the access boundary before selecting the connector
Use a short boundary statement as the first procurement or implementation artefact. Record the intended users, business purpose, permitted environments, apps, record groups and fields. Separately list prohibited data and prohibited actions. “Internal use” is not a sufficient access condition: a sales representative, payroll officer and external support contractor can all have legitimate but different information needs.
Next, ask the implementer to identify the effective access arrangement. Does the integration operate through the individual employee’s authorised access, a shared connection or another configured identity? What can that identity retrieve and change? Require evidence from the proposed configuration rather than assuming that the permissions visible in a staff member’s normal application necessarily describe every part of the integration.
Microsoft assigns different configuration responsibilities across these options: administrators control Work IQ MCP availability, while environment, app and data permissions determine accessible business context. Dataverse MCP must be configured and authorised for each environment the client uses. That distinction makes the documented connection scopes useful for selection, but it does not replace checking the actual deployment.
As a proposed procedure, ask the business data owner to approve the boundary and the system administrator to demonstrate how it is enforced. Escalate unclear identity behaviour or mixed sensitive data before connecting real records. Microsoft’s AI modernisation guidance recommends layered security, including access controls, least privilege, threat modelling and monitoring. Treat the connector as one part of those layers, not the security boundary by itself.
Reusable integration selection and release record
The following selection matrix and release conditions are illustrative procedures to adapt to your business. Copy them into an approval ticket. Start with: Task; user role; permitted data; prohibited data; permitted actions; proposed access identity; candidate integration; evidence location; business approver; technical owner; suspension method. Do not leave the prohibited-data or access-identity fields blank.
Selection matrix — Broad Microsoft 365 plus supported business-app context is necessary: assess Work IQ MCP. Only direct tools or skills in a specific Dataverse environment are necessary: assess Dataverse MCP. Application code needs an answer grounded in a selected Dataverse semantic model: assess Dataverse Ask API. Predictable retrieval of specified records is necessary: assess the source API or another targeted integration. Microsoft explicitly notes that Work IQ MCP does not currently offer a retrieval-only parameter that bypasses response generation; see its connection guidance.
Example entry — Role: sales representative. Task: inspect authorised CRM opportunity records. Data scope: one nominated Dataverse environment, with approved record and field restrictions. Actions: read only for this pilot. Prohibited: payroll, unrelated customer accounts and record updates. Candidate: Dataverse MCP, subject to confirming available tools, effective permissions and the client configuration. “CRM only” selects a candidate; it does not earn approval.
Pass conditions — The business owner has approved the boundary; the administrator has demonstrated the effective identity and permissions; permitted retrieval works; prohibited-record tests produce no disclosure; disallowed actions are rejected; relevant activity is observable; and the team has demonstrated suspension. Record the test evidence and configuration version. These conditions are an internal release proposal, not a claim that passing proves complete security.
Stop conditions — Sensitive records remain accessible outside the approved task; the team cannot explain which identity authorises access; a required action cannot be restricted; monitoring cannot support investigation; or suspension has not been demonstrated. Mark the decision “hold”, name the unresolved issue and assign an owner. Do not average these failures into an overall score that permits a serious access gap to pass.
Test permitted and prohibited access separately
A useful demonstration must show more than the agent answering an authorised question. As an illustrative protocol, create synthetic records representing permitted customer cases, another team’s cases and explicitly prohibited personnel information. Use recognisable test markers rather than real salaries or customer secrets. Confirm that the test environment represents the permission relationships intended for production, and document any differences.
Run the same task under each relevant user role and connection arrangement. Test a normal permitted request, a direct request for prohibited information and a request mixing permitted and prohibited records. Test applicable tools as well as the final answer. A polite refusal in the chat is not sufficient evidence if the underlying integration has already retrieved information outside the approved boundary.
Include action tests where tools can change business records. Ask the technical owner to demonstrate that an unauthorised update is rejected by the application or authorisation layer, rather than relying only on an instruction telling the agent not to update anything. Keep the initial scope read-only where that meets the task, and avoid enabling unused tools merely because the connector offers them.
Human review has limits here. A reviewer can check an answer against visible source material, but cannot establish from the answer alone which other records were available to the integration. Nor does a successful test cover every later configuration or access change. The NCSC’s secure AI development guidelines treat security as a lifecycle requirement, including deployment, logging, monitoring and update management. Repeat boundary checks after relevant changes rather than treating approval as permanent.
Hypothetical failure: a service assistant reaches personnel records
Consider a hypothetical business building an assistant for customer-service staff. Its approved task is to summarise open service cases. The implementer chooses Work IQ MCP because a later phase might need wider organisational context. During setup, the team also permits access to an app containing synthetic personnel records through an over-broadly authorised configuration. Nobody compares the effective access with the original service-only requirement.
In a release rehearsal, a tester asks the assistant to combine a customer complaint with information about the employee handling it. The assistant returns a synthetic salary marker from the personnel records. The failure is not that Work IQ automatically exposes HR information. It is that this hypothetical configuration, its participating data and its effective permissions allowed information outside the approved task boundary to be retrieved.
The decision record should make the response straightforward: stop the pilot, suspend the affected connection or access route, preserve relevant investigation evidence and have the technical owner establish what was accessible. The business owner should assess the consequences with the appropriate security and privacy advisers if real information was involved. Removing a sentence from the answer would not correct the underlying access problem.
For recovery, reassess whether broader context is necessary at all. If the task remains environment-specific, evaluate Dataverse MCP in the nominated service environment, with the required permissions and tools verified. If Work IQ MCP is retained, correct the relevant access and participation settings and retest. In either case, demonstrate that authorised service-case retrieval still works and the personnel marker cannot be retrieved through the tested routes before considering release.
When a report or targeted API is the better choice
Do not deploy an agent connection merely to answer a recurring question with an already-defined result. If staff need a list of overdue cases, a standard read-only report may meet the requirement without AI. If software needs exact record values for a known identifier, assess targeted source-API retrieval. Keep the process deterministic where interpretation adds no business value.
A practical fallback is an approved report that employees use directly. Where summarisation genuinely helps, a separate, controlled step could provide only necessary, sanitised report content to an approved AI environment. That is not a wholly non-AI workflow, and it creates another disclosure decision. A “closed” chat or sandbox label alone is not evidence that the information is appropriate to upload.
Manual selection can reduce the integration scope, but it transfers work to employees: they must choose the correct report, remove unnecessary details and check that the information remains current. Sanitisation also needs a defined method; simply deleting names may leave identifying context. Where personal information is involved, ask the privacy lead or qualified adviser what information may be used and what handling conditions apply rather than treating manual copying as an exemption.
Compare the operating burden, not just the connector setup. The proposed agent needs permission maintenance, testing, monitoring and incident response. The report workflow needs staff time, access controls and version discipline. Prefer the simpler route when volumes are low, the boundary cannot be enforced confidently, the source system lacks a suitable restricted interface, or the business cannot resource ongoing oversight. Neither approach should be approved on a promise of guaranteed savings.
Assign ownership and make the decision reversible
The business process owner should decide whether the additional context is necessary and accept the operational trade-off. The data owner should approve permitted records and uses. The technical owner should document identities, permissions, tools and configuration evidence. The security lead should agree monitoring and incident handling. These are proposed responsibilities; a small business may combine roles, but should still name the accountable people.
Before release, write down how to suspend access, who has authority to do it and how staff will continue the task without the agent. Keep a record of enabled integrations and participating environments so the team knows what to inspect. For a fuller handover structure, use the complementary guide on who owns AI pilot security after deployment.
Do not describe suspension as complete reversal. It can stop further use through the affected route, but the team must separately investigate information already returned or copied into other locations. Define what evidence will be retained, how exposed information will be assessed and who authorises restoration. The NCSC’s lifecycle guidance supports planning for secure operation and incident management, rather than relying solely on pre-launch design.
The decision-ready outcome is a short approval, not a broad endorsement of an AI platform: “Use this connection, for this task, under these identities, with these data and action limits, subject to this evidence.” Choose broader Work IQ context only when the task justifies it. Choose an environment-specific or targeted connection when that is sufficient. If the boundary cannot be demonstrated, retain the report or manual process until it can.
Sources
General information only; verify sources before making business decisions.