Automate·Advanced·55 min·Updated Sep 30, 2026

Build an IP protection agent

Build a Copilot Studio agent that scans for likely trademark or IP infringement and drafts the first step of an enforcement workflow.

Download PDF

Microsoft 365

Works With

Prerequisites

A register of the organization's protected marks/assets and your standard enforcement escalation ladder

Business Outcome

Faster detection and response to infringement, reducing the window where unauthorized use goes unchallenged.

Handle with care

Confidential IP strategy

The protected-asset register and enforcement escalation details are commercially sensitive — a leak could tip off the party being investigated. Restrict the agent's knowledge source (step 1) and the drafted enforcement letters (step 4) to the legal team, not a broader shared location.

Workflow Overview

The apps run in this order.

Word
SharePoint
Copilot Studio

Step 1: Define the protected asset registerSharePoint

Build a SharePoint list or library with one row per registered mark — the exact name/logo, registration number, and the goods/services it covers — and connect that as the agent's knowledge source.

The agent needs an authoritative, structured register to check against, not a general sense of "our brand" pulled from marketing materials.

Step 2: Build the detection and severity-scoring agentCopilot Studio

In Copilot Studio, have the agent evaluate flagged potential matches (from a monitoring feed or a manual submission) against the protected asset register and assign a severity level based on how closely the use matches a registered mark and the context of use (competing product vs. unrelated use).

Prompt idea:

This listing uses a name that closely resembles our registered trademark "Northwind Traders" on a product in an adjacent market. Compare it against our trademark register, assess the infringement severity, and draft a preliminary cease-and-desist letter for legal review.

The agent's drafted letter and severity assessment go to legal counsel for review and sign-off — this is not a workflow to automate past the draft stage given the legal consequences of a wrongly sent enforcement letter.

Step 4: Log every case with its outcomeSharePoint

Add each case to a SharePoint list with columns for the mark involved, assigned severity, and legal's final decision.

A structured list you can filter and sort beats a folder of individual letters, both for spotting patterns in the severity model and for pulling up your enforcement history if a case is ever challenged.

Check the work

  • Verify the trademark register the agent checked against is current — an expired or unregistered mark can't support an infringement claim.
  • Have legal confirm the severity assessment before any letter is sent, especially for borderline or first-time cases.
  • Review a sample of dismissed (low-severity) cases to make sure genuine infringement isn't being under-scored.

Source: Microsoft Copilot Scenario Library — Legal (2026)

Expected Outcome

A reviewed list of potential infringement matches with severity assessment and a drafted first-response letter for legal sign-off.

✓

AI is the right call here

Loading the asset register (step 1) and logging outcomes (step 4) are recordkeeping. Judging how closely a use resembles a mark and whether the context of use actually matters (competing product vs. unrelated) is a real severity call, not a string match.

Related Workflows

WORK WITH LIMINALS

Ready to roll this out beyond one person?

Workflows like this tend to raise real governance and licensing questions once more than one person is using them — that's exactly what we help with.