What Narmi announced
On October 26, 2026, Narmi announced a Copilot Connector server. It links Microsoft 365 Copilot to the company's administrative banking platform. Narmi says staff can use it to:
- Relationship management: review account activity, spot large outflows to other institutions, and look for ways to grow existing customer relationships.
- Lending and liquidity: analyze cash flow, monitor line-of-credit use, and assess loan applications.
- Operations and risk: review transaction histories, flag unusual payments, and support fraud investigations.
- Onboarding: check application status and follow onboarding progress.
Narmi's co-founder Chris Griffin framed the release around access without compromising security or privacy. The release says this builds on Narmi's earlier MCP work with OpenAI and Anthropic, and on its AI Marketplace.
The wording matters here. Staff use the information to support lending decisions and fraud investigations. Nothing in the announcement says Copilot makes credit decisions or investigates fraud on its own.
The security claims
Narmi makes two headline claims:
- Employees see only information they are authorized to view under existing institutional permissions.
- The connector is read-only. It cannot modify accounts or start transactions.
Both are vendor assertions. The announcement gives no technical specification and no independent security assessment. It says nothing about logging, retention or data-processing terms.
The read-only point is a property of this connector, not of Copilot connectors in general. Microsoft's documentation says federated connectors can read data and, where a connector provides the tools, create, update, or delete data with the user's approval. Which tools exist is decided by the connector's own server: the MCP server associated with the federated connector determines tool availability. So Narmi's read-only boundary is a design choice by the vendor. Admins should verify it rather than assume it.
What Microsoft's connector model implies for IT teams
The announcement doesn't say whether Narmi's connector is a Microsoft federated connector. If it is, Microsoft's documentation describes these controls and behaviors:
- Real-time access, no indexing. Federated connectors fetch data in real time and don't index external data into Microsoft 365.
- User identity governs access. They access data using the user's identity and permissions. That fits Narmi's "existing permissions" language.
- Admin governance. They are managed and governed by admins in the Microsoft 365 admin center. Admins can audit activity in Microsoft Purview.
- Visibility conditions. A user sees a connector only if all of these hold: its publisher type is allowed (or an admin turned it on individually), it is enabled, the user is in the User access scope, the user is in any staged rollout, and the user has a Microsoft 365 Copilot license.
Microsoft also offers a custom route. Its docs say a custom federated connector starts with an MCP server that exposes read-only tools. An institution could also build its own connector against a vendor's MCP endpoint. Whether Narmi's is published through Microsoft's gallery or deployed another way isn't stated, so treat that as unconfirmed.
A practical checklist for banks
This is general guidance based on Microsoft's documented controls. It is not a Narmi procedure.
- Confirm the deployment path with Narmi. Ask how the connector is delivered, what licensing it requires, and which Copilot experiences it supports.
- Check the tool list. Microsoft's docs describe reviewing a connector's tools to identify any that can create, update, or delete data. Confirm that none exist for this connector.
- Stage the rollout. Start with a small Entra group before opening the connector to everyone.
- Test permissions. Compare what a front-line user and a lending officer each see against what core-system permissions allow.
- Turn on auditing. Make sure Purview audit coverage meets your regulators' expectations.
- Write usage guidance. Staff should know that Copilot output can be wrong and that important findings need verifying in the source system.
Reasons for caution
The pitch is attractive. Fewer swivel-chair reports and fewer system hops are real benefits in a back office. But the announcement has no measured time savings, accuracy figures, named customers, pricing or availability details. Narmi's earlier AI Marketplace announcement did include a time-saving figure for a different feature, AI DecisionAssist. That figure doesn't carry over to this connector.
An AI assistant summarizing customer financial data also raises model-error and oversight questions. Read-only access limits what can go wrong, but it doesn't make summaries correct. Expect examiners to ask how outputs are reviewed.
Bottom line
Narmi's Copilot connector is a vendor-announced integration. Narmi says it is read-only and inherits institutional permissions. Microsoft's documented model for MCP-based connectors offers real admin controls that could back those claims up. The specifics aren't public yet: deployment method, licensing, supported experiences and independent validation. IT teams at financial institutions should get those answers from Narmi before enabling anything.