Skip to main content

Connect Microsoft Copilot Studio to Access360

Add Access360Access360 The licensed add-on that connects AI assistants such as Claude, ChatGPT, and Microsoft Copilot Studio to Process Design through the Model Context Protocol (MCP). The assistant acts as the signed-in iGrafx account, with that account's permissions. to a Microsoft Copilot Studio agent as an MCP tool, so the agent can look things up in Process DesignProcess Design The discipline of explicitly modeling business processes to document, analyze, and optimize them. In Process360 Live, process design is the authoring side that complements mining's data-driven view. and, if you allow it, make changes.

Prerequisites​

  • Requires Access360Access360 The licensed add-on that connects AI assistants such as Claude, ChatGPT, and Microsoft Copilot Studio to Process Design through the Model Context Protocol (MCP). The assistant acts as the signed-in iGrafx account, with that account's permissions. to be set up for your platform, and your platform's MCP Server URL. Your iGrafx administrator copies the URL from Admin → Server Settings → AI Settings and gives it to you. See step 6 of Set up Access360.
  • Requires permission to edit the agent in Copilot Studio. Your Power Platform data policies also apply to MCP tools.
  • Decide whose iGrafx account the agent uses (see Individual and shared accounts):
    • Each user signs in — every person who uses the agent needs the Access MCP server permission on their own account.
    • A shared API key — you need one dedicated iGrafx account with Access MCP and an API key for it. Everyone who uses the agent then acts as that account, so any change it makes is recorded under that account rather than the person who asked. For an agent that only looks things up, give the account view-only permissions.

Supported versions​

MCP tools are available in Copilot Studio agents. The menu names below follow Microsoft's article Connect your agent to an existing MCP server; if your screens differ, follow that article for where things are, and use the values on this page.

Configuration​

  1. In Copilot Studio, open your agent and go to Tools.

  2. Click Add a tool, then New tool, and choose Model Context Protocol.

  3. Enter a Server name, such as iGrafx Process Design, and a Server description. The agent reads the description to decide when to use the tool, so say what it's for. For example: "Looks up processes, risks, controls, and other content in our iGrafx process repository."

  4. Paste your platform's MCP Server URL as the Server URL. It has this shape, with your region (com, eu, or jp) and your platform's tenant ID filled in:

    https://process-design-mcp.svc.igrafxcloud.<region>/<tenant-id>

  5. Under Authentication, choose one:

    • For a shared API key, choose API key, set the type to Header, and enter Authorization as the header name.
    • For each user to sign in, choose OAuth 2.0 and keep the Configuration type at Dynamic (with discovery). Copilot Studio registers itself automatically, so you don't need a client ID or secret.

  6. Click Add. Copilot Studio asks you to pick a connection. If you don't have one yet, create one and give it a name. Then:

    • For a shared API key, enter the key as Bearer, a space, and then the key. The connection you create covers everyone who uses the agent, so they don't need a connection of their own.
    • For each user to sign in, the iGrafx authorization page opens. Sign in with your iGrafx account.

  7. Add the tool to the agent.

Verify​

In the agent's test pane, ask: "Which iGrafx user am I connected as?" With a shared API key, the agent answers with the dedicated account's name; with individual sign-in, with yours.

Troubleshooting​

  • The agent reports REST API via API key authentication Disabled — an iGrafx administrator needs to turn on Allow access via API Key. See Set up Access360.
  • The agent reports that MCP connectivity is disabled, or that the account doesn't have permission — compare the message with Messages an assistant reports.
  • Every request fails after the key worked before — the key may have been deleted or regenerated. Ask your iGrafx administrator for the current key and update the connection.