Set up Q.wiki Assistant in Microsoft Copilot

Modell Aachen provides a pre-configured Q.wiki Copilot agent as a ZIP file. You import it, connect it to your Q.wiki instance, and share it with your users. The agent is pre-configured according to our best practice – everything can be adjusted after import.

Prerequisites

A Global Admin handles the entire setup – end users do not need their own license. Usage is billed via existing Microsoft 365 Copilot licenses or Copilot Credits.

Download

Download the pre-configured agent and import it in step 1.

Step 1: Import the solution

The ZIP is a ready-made Power Platform solution – the Q.wiki Assistant is already included as an agent component. You do not need to create a new solution; simply import the ZIP via the Solution Explorer.

1. Sign in to copilotstudio.microsoft.com (external) and select the environment in the top-right corner where you want to deploy the agent.
2. In the left navigation, click Solutions. If the icon is not immediately visible, expand it via the "…" (More) menu at the bottom of the sidebar.
   

3. Click Import solution in the toolbar at the top.
   

4. In the import dialog: click Browse → select the ZIP → click through the wizard with Next until you reach Import. If the wizard asks for Connection References or Environment Variables, leave them blank – the Q.wiki MCP connection is set up separately in step 3.
5. Monitor the status via the bell icon in the top right – the import runs in the background for 1–5 minutes. Wait for the "Successful" banner.

Step 2: Open and verify the agent

1. In the Solution Explorer, click the solution you just imported.
2. In the Objects panel on the left, click Agents.
3. Click "Q.wiki Assistant" – it opens in Copilot Studio.

Step 3: Add the Q.wiki MCP tool

The MCP connection is tenant-specific and is therefore intentionally not included in the ZIP. You create it once in your tenant. In the agent, open the Tools tab and select Add a tool → New tool → Model Context Protocol.

In the "Add Model Context Protocol server" dialog, enter the following values:

Click Create. The "Add tool" dialog opens with two steps:

1. Connection: Select "Create a new connection" → sign in with your Q.wiki account in the OAuth pop-up (no password required with Entra SSO).
2. Add to agent: confirm after successful login.

The tool appears in the tab with status "Connected".

For more details on the MCP onboarding wizard in Microsoft: Connect your agent to an existing MCP server (external).

Step 4: Test the agent

Click Test in the top right to open the test panel. Ask a question whose answer you can verify in your Q.wiki – for example about a process, a role, or a work instruction. The following three criteria should be met:

• The Q.wiki tool is visibly called in the activity log.
• At the end of the response, a "Sources from Q.wiki:" block appears with links to the pages used.
• The content of the answer matches the actual content in your Q.wiki.

Step 5: Publish the agent

1. Click Publish in the top right of the agent.
2. Click Publish again in the confirmation dialog.
3. Status changes to "Published by …".

Step 6: Add the "Microsoft 365 and Microsoft Teams" channel

To make the agent available in Microsoft 365 Copilot and Teams, add the combined channel.

1. In the agent, switch to the Channels tab at the top.
2. Click the "Microsoft 365 and Microsoft Teams" tile.
3. In the side panel under "Turn on Microsoft 365", the checkbox "Make agent available in Microsoft 365 Copilot" is active by default – leave it as is.
4. Click Add channel in the bottom right.
5. Wait for the confirmation status message.
   

Step 7: Submit for approval

After adding the channel, the "Availability options" button appears in the side panel. Use it to request that the agent be published in Microsoft 365 Copilot and your organization's Teams app store.

1. Click Availability options in the same side panel.
2. The "Show in Teams app store for org"panel opens. Work through the following sections:
   • Microsoft Teams + admin status: shows version and approval status – switches to "Waiting for approval" once you have submitted.
   • Set your agent reach: confirms that the agent will be made available in all supported channels – no selection needed.
   • Before submitting, make sure you've …: pre-submit checklist – agent recently published (step 5 ✓), authentication configured (already set in the ZIP ✓).
   • Teams Authentication SSO Configuration: shows the App ID of your agent. Copy it using the copy icon – the admin uses it in step 8 to uniquely identify the agent.
3. Click Submit to org catalog in the bottom right.
4. Status changes to "Your agent is submitted and waiting for approval from your Teams admin".
   

Step 8: Approve in the Admin Center & set the audience

The approval request is waiting in the Microsoft 365 Admin Center (external). Here you decide who can install the agent and who receives it automatically.

1. Open admin.microsoft.com (external).
2. Sidebar: Agents → All agents → tab Requests.
3. Click Q.wiki Assistant in the list – the detail panel opens on the right. (If there are multiple pending agents, use the App ID copied in step 7 to identify the correct one.)
4. Click Publish to store in the top right.
   

The "Publish agent to selected users" wizard opens:

1. Select users– two selection areas:
   • Select users or groups who can install the agent: All users for the entire tenant or Specific users/groups for a pilot group.
   • Select users or groups who will have the agent pre-installed (optional): All users = automatic pinning in Teams; None = users install it themselves.
2. Apply template – select a security and privacy policy template.
3. Accept permissions – confirm admin consent for the API permissions required by the agent.
4. Review and finish – review the summary and complete with Finish.
   

Step 9: For end users – finding and using the agent

After approval (allow up to 24 hours – see Troubleshooting), your users can open the agent in two places.

In Microsoft 365 Copilot

1. Open Microsoft 365 Copilot – via m365.cloud.microsoft/chat (external), the Microsoft 365 Copilot app, or Copilot in Teams.
2. In the sidebar under Agents, click the Q.wiki agent. If it is not yet listed there, click More agents – in the Agents store it appears under "Built by your organization".
   

In Microsoft Teams

1. In Teams, click Apps on the left, search for "Q.wiki Assistant" (section "Built for your org"), and select Add. If you chose Pre-installed: All users in step 8, this step is not needed – the agent is already pinned in the Teams sidebar.
2. The agent appears in the chat area and can be messaged like a contact.

First use: connecting to Q.wiki

On the first question, the agent prompts the user to sign in. Each user signs in once with their own Q.wiki account (no password required with Entra SSO). After that, they can start asking questions straight away – the included conversation starters are a good entry point.

Troubleshooting

Related articles

• Q.wiki MCP Server – Overview & Endpoint