A professional reviews a grantmaking dashboard showing funding data, donor insights, and secure role-based access.
akoyaGO, a Minnesota vendor of foundation-management software built on Dynamics 365, has announced "Copilot in akoyaGO," pitched as practical AI that works alongside the information staff already use. The press release is promotional. The more useful detail sits in akoyaGO's own Product AI Policy and in Microsoft's documentation. Together they show what is being deployed, what it can touch, and what administrators need to check.

A professional reviews a grantmaking dashboard showing funding data, donor insights, and secure role-based access. What akoyaGO announced​

The announcement, issued November 18, 2026, makes a modest pitch. It says AI should not replace the judgment that grantmaking requires. It should make the surrounding information easier to reach.

The release names four kinds of assistance:

  • Summarizing lengthy histories.
  • Turning everyday questions into filters.
  • Visualizing data.
  • Helping with repetitive data entry.

The release says Copilot can organize information, identify trends, suggest values, interpret natural-language requests and help visualize data. The person using akoyaGO still reviews the output and decides what to do with it.

The release gives no pricing, launch date beyond the announcement date, customer examples, adoption figures or time-savings numbers. The efficiency claims are intentions, not measured results.

What "Copilot in akoyaGO" actually is​

The headline mentions Copilot Studio, while the body of the release says only "Copilot." akoyaGO's Product AI Policy, effective 10/15/2026 (version 1.0), clears this up. It describes two separate AI capabilities in the Dynamics 365 solution, and both are optional.

1. akoyaGO Foundation Advisor. The policy says this is an AI agent built by akoyaGO in Microsoft Copilot Studio and delivered as part of the Dynamics 365 solution. It answers questions and surfaces insights grounded in the client's CRM, fund, grant and donor data. The policy states these boundaries:

  • Its only knowledge source is the client's own Dataverse.
  • It has no external connectors or actions.
  • It honors each user's Dataverse security roles, so a user gets answers only from records they can already see.
  • Its output is advisory. It does not create, modify or delete records, award grants, release payments or send communications.
  • The client's administrator controls whether it is enabled.
  • Client information is never used to train the underlying models.

2. Microsoft Copilot for Dynamics 365. This is a separate platform feature that the client's tenant administrator turns on or off. The policy says akoyaGO does not control, configure or require it, and that the solution works fully without it.

The policy also says the portals (GOapply, GOfund, GOdonate and GOmanager) contain no AI features.

This distinction matters. "Copilot in akoyaGO" is a marketing umbrella. In practice, a custom Copilot Studio agent and Microsoft's own Dynamics 365 Copilot have different owners, different settings and different data-handling paths.

What Microsoft's documentation adds​

akoyaGO's policy leans on Microsoft's published data-protection commitments. Microsoft's Dynamics 365 and Power Platform Copilot FAQ says:

  • Prompts and responses are not available to other customers.
  • They are not used to train or improve third-party products such as OpenAI models.
  • They are not used to train or improve Microsoft AI models unless the tenant admin opts in to data sharing.
  • Copilot adheres to existing data permissions and bases its responses only on data the individual user can access.
  • Copilot is built on Azure OpenAI Service and runs within Azure. Microsoft says it does not share customer data with OpenAI.

The same FAQ carries caveats that the press release skips:

  • The trust boundary has exceptions. Customer data is stored within the Microsoft Cloud trust boundary, but Microsoft says that features powered by Bing and third-party copilot plug-ins may send customer data outside it. akoyaGO's policy says it installs and requires no such plug-ins and that Foundation Advisor uses none.
  • Geography matters. Copilot features are not available in every Azure geography and language. Depending on where the environment is hosted, administrators may have to allow data movement across geographies. akoyaGO's policy calls this an opt-in tenant setting.
  • Accuracy is not guaranteed. Microsoft says Copilot responses are not 100% factual and tells users to review output before sharing it.
  • Permissions cut both ways. If a user can access encrypted data and supplies it to Copilot, Copilot can use it. The agent respects access. It does not add protection beyond what the user's own permissions provide.

Why this matters for Dynamics 365 administrators​

Foundations hold sensitive material: donor records, applicant details, fund balances and community relationships. The architecture here is sensible. A single-source, no-connector, read-only agent that inherits Dataverse roles is a conservative design. The weak point is usually not the agent. It is the permission model underneath it.

If Dataverse security roles are broader than they should be, a natural-language assistant can make that over-permissioning much easier to exploit. Staff who never found a sensitive record through menus might find it by asking a question. This is analysis based on how role-based access generally works, not a finding from akoyaGO or Microsoft.

Administrators evaluating this should check:

  1. Which AI capability is being enabled. Foundation Advisor and Microsoft Copilot for Dynamics 365 are controlled separately.
  2. Which security roles apply. Review role scope before turning anything on, since the agent only mirrors it.
  3. Tenant data-sharing settings. Confirm whether optional AI data sharing is opted in.
  4. Cross-geography movement. Confirm whether the environment's hosting region requires it, and whether the tenant allows it.
  5. Bing-backed features and plug-ins. Verify that none are connected, since those are the documented route out of the trust boundary.
  6. Review workflow. Decide how staff should check AI summaries before relying on them for decisions about grants or payments.

The release also mentions sensitivity labels, retention policies and auditing. It says Copilot "can inherit" them. That wording is conditional, so check what applies in your own tenant.

A fair read of the claims​

The "people decide" framing is backed by the policy. Because the agent cannot write records or take actions, the advisory-only claim is structural, not just a promise. That is a real design choice.

The wider claims are less solid. Nothing published shows the tool saves time, reduces errors or improves grant outcomes. The privacy assurances are vendor policy statements plus Microsoft's documentation, not an independent audit. The Microsoft Learn pages the packet draws on carry "last updated" dates of October 2024 and May 2025. Administrators should confirm current behavior in their own tenants.

An independent review of akoyaGO from earlier in 2026 noted that Dynamics 365 gives access to Microsoft's general-purpose AI tooling, as opposed to grantmaking-specific features. A custom Copilot Studio agent grounded in foundation data narrows that gap, though how well it does so in practice is untested publicly.

Bottom line​

This is a modest, vendor-driven product announcement. Its value for Microsoft-platform readers is the pattern it shows: a specialized Dynamics 365 application ships a scoped Copilot Studio agent, grounded in Dataverse, read-only, role-aware and admin-gated. Anyone running a similar line-of-business app on Dataverse can use the same checklist: scope, roles, data movement and plug-ins.

 

References

  1. Microsoft Copilot Studio Brings Practical AI to Foundation Work in akoyaGO EIN Presswire 2026-11-18T15:59:30+00:00
  2. FAQ for Copilot data security and privacy - Dynamics 365 | Microsoft Learn learn.microsoft.com
  3. FAQ for Copilot data security and privacy for Dynamics 365 and Power Platform - Power Platform | Microsoft Learn learn.microsoft.com