Copilot Studio agents, checked against your rules
Your teams build agents in Microsoft Copilot Studio. NEKOD checks what each agent can reach against your own rules and shows the evidence.
When the rules pass, the agent goes to an approver and the decision stays on record. Copilot Studio support is set up with you in the pilot.
Book a DemoWhy Copilot Studio agents need your rules
Copilot Studio lets a domain expert build an agent in an afternoon: point it at a SharePoint site, add a connector, publish it to Teams. No engineering sprint needed.
One knowledge source can expose files meant for a single team. One connector can send data outside the company. NEKOD checks the agent against your rules and names what to fix.
What a Copilot Studio agent touches
Copilot Studio
Agent builder
Power Platform environments
Where agents run
SharePoint / Dataverse
Knowledge sources
Power Automate
Flows and actions
Microsoft Entra ID
Sign-in and access
Teams / Microsoft 365
Channels
Copilot Studio in your company
- What it is
- Microsoft's builder for agents. A maker points an agent at company knowledge and tools, then publishes it to Teams or Microsoft 365.
- Who builds with it
- Teams already working in Microsoft 365, such as HR, finance and the IT service desk.
- What gets built
- Agents that answer questions from SharePoint, start flows and work inside Teams.
- Where it lives
- A Power Platform environment, with knowledge in SharePoint or Dataverse.
Why use Copilot Studio with NEKOD
Copilot Studio gives your teams
- An agent built in an afternoon, with no code
- Access to the company's own knowledge and connectors
- Publishing to the channels people already use
NEKOD gives your company
- Your written rules checked on what each agent can reach
- A look at knowledge sources and connectors before an agent reaches more people
- An owner, a risk level and a recorded approval for each agent
How NEKOD works with Copilot Studio
- 01
Set up with you
Copilot Studio support is set up with you in the pilot. We agree which environments and agents to start with.
- 02
Check against your rules
NEKOD checks what each agent can reach: knowledge sources, connectors and channels.
- 03
Fix with the maker
The maker gets a plain list of what to change, in terms they know, such as a narrower knowledge source.
- 04
Approve with a record
When the rules pass, the app goes to the right approver. The decision and the evidence behind it stay on record.
What We Check
Checks against your rules for each agent
Knowledge & data sources
Which SharePoint sites, files, Dataverse tables and websites the agent answers from, and whether they hold data its users should not see.
Connectors & actions
Power Platform connectors, Power Automate flows and HTTP actions the agent can call, and where they send data.
Authentication & sharing
How the agent signs users in, who it is shared with, and the channels it is published to, such as Teams or a public website.
Owner & lifecycle
A named owner, the environment it runs in, and a record of who approved it before it reached more users.
A check against your rules, and a fix in the tool your team already uses.
Critical · Security
Agent knowledge source shared with all users in the tenant
Fixed · Security
Agent knowledge source shared with all users in the tenant
Prioritized fix list
Every finding comes with its severity, a plain-English explanation and what to fix next. The builder pastes the fix prompt back into Copilot Studio.
Applications
- Approved
Supplier onboarding
Owner: Procurement
- Fixes needed
Expense checker
Owner: Finance
- In review
Shift planner
Owner: Operations
Approved by Risk
Supplier onboarding · all checks passed · evidence attached
Approval on record
Approvers see every application with its owner and status. Each decision is recorded with the evidence behind it.
The line that failed
Agent knowledge source shared with all users in the tenant in HR policy assistant › Settings › Security
Anyone in the company can ask this agent about HR files
The agent answers from a folder meant for HR only. Limit who can use the agent, or point it at a narrower source.
Plain language
Every issue comes with a plain-English title, why it matters, and what to fix, so approvers can follow it too.
Critical · Security
Anyone in the company can ask this agent about HR files
The agent answers from a folder meant for HR only. Limit who can use the agent, or point it at a narrower source.
Report assessment
Each check leaves a record: the findings that matter, and a fix prompt in plain language.
Frequently Asked Questions
No. Your teams keep building agents in Copilot Studio. NEKOD holds your rules, checks what the agent can reach, and keeps the approval on record.
The things your policy cares about: which knowledge sources and connectors the agent uses, who can talk to it, how it signs users in, and where its answers can send data.
We set it up with you in the pilot. Tell us about your Microsoft environment when you book a demo and we confirm what NEKOD reads and how.
No. NEKOD reads in read-only mode by default and does not change an agent when it checks it. The builder makes the fix in Copilot Studio.
No. Your tenant and environment settings stay in place. NEKOD adds a check against your own policy for each agent and records who approved it.
Start with the agents your teams already built
Tell us about your Microsoft environment. In the pilot NEKOD checks each agent against your rules and records the approval.