Connecting Noibu to Microsoft 365 Copilot Cowork
Last updated: August 13, 2026
This guide walks you through the setup for Noibu in Microsoft Copilot Cowork. By the end, Noibu will be set up and collecting data, the plugin will be installed in Copilot Cowork, and your ecommerce data will be connected and ready to query.
Important: This guide covers Microsoft Copilot Cowork, the agentic surface within Microsoft 365 Copilot. It does not apply to GitHub Cowork or GitHub Copilot, which are separate products with their own setup. After the first mention, this guide shortens Microsoft 365 Copilot Cowork to Cowork.
Note: It is also possible to use Noibu with Copilot Chat if Cowork is unavailable. Those instructions are at the bottom of this article.
Prerequisites
Before continuing, you will need to have completed these prerequisite steps:
Set up your account with Noibu
After Noibu sets up your company and domain, you will receive a welcome email with a link to finish setting up your account with Noibu. Each person who will use Noibu in Cowork needs their own account — email and password, or Google single sign-on (SSO).
Deploy Noibu to your ecommerce website
You will need to deploy Noibu's script on your website to start collecting session and page visit data from your store. Install it as early as possible so Noibu has data to work with by the time you start using the plugin in Cowork. For full details, see this article.
Assign Microsoft 365 Copilot licences
Each Noibu user needs a paid Microsoft 365 Copilot licence. A Global administrator or Billing administrator assigns these at admin.microsoft.com → Users → Active users → Licences. Free Copilot Chat does not run Cowork plugins.
Enable usage-based billing
Cowork runs on Copilot Credits, which must be turned on at the tenant level before any plugin will run. This gates access to Cowork itself, separately from the Noibu plugin. As a Global administrator or Billing administrator, go to admin.microsoft.com → Copilot → Cost Management → Get Started, then:
1. Set the Billing method. This is an Azure subscription; the admin centre can create one for you.
2. Set a monthly spending limit, or choose not to limit it. You can also set a per-user limit.
3. Set up alerts — who is emailed, and at what usage threshold.
4. Select Activate, then Manage Configuration and confirm that Cowork appears as an available service.
Note: An AI administrator or License administrator can create and edit spending policies, but cannot set the billing method itself.
Enable custom-app upload
This allows your users to install the Noibu package without going through an admin each time. Go to admin.teams.microsoft.com/policies/app-setup → Teams apps → Setup policies → Global, or your own policy, and set Upload custom apps to On. This change can take up to 24 hours to take effect.
Download the Noibu plugin for Copilot Cowork
The latest version of the plugin is available for download here.
Setting up Noibu plugin for Copilot Cowork
Step 1 — Install the Noibu plugin in Cowork
One person in your organization uploads the Noibu package and shares it with the rest of the team. That person is the plugin owner. Everyone else installs the shared package.
➡ If you are the plugin owner:
1. Go to m365.cloud.microsoft/agents/cowork and click Customize.
2. Ensure Plugins is highlighted, then click Add plugin.
3. Upload the Noibu .zip package you downloaded.
4. Select Specific users in your organization, and add the email addresses of everyone who needs access to Noibu.
5. Wait approximately 10 minutes before continuing. Cowork needs time to detect and synchronize the newly installed skills.
➡ If the plugin has been shared with you:
1. Go to m365.cloud.microsoft/agents/cowork and click Customize.
2. Ensure Plugins is highlighted, then find Noibu under Shared with me.
3. Click into Noibu and click Install.
Step 2 — Connect your Noibu account
Each person connects their own Noibu account, so you see only the domains your Noibu permissions already allow.
1. Start a new task. Do not reuse an existing chat — it can hold state from before the plugin was installed.
2. Run /setup-noibu. The skill is ready when you can see it detected in the chat dropdown.
3. When the skill prompts you to authenticate, go to Customize → Plugins → Noibu.
4. Refresh the page.
5. Click Connect and sign in with your Noibu credentials.
Step 3 — Begin analysis with Noibu and Copilot
Start a new task to ask questions about your store in plain language, or run one of Noibu's skills. Always include the domain in your question; Copilot uses it to resolve the right store before it runs anything else.
Examples:
/store-pulse
www.example.com/checkout-analysis
www.example.comHow many sessions did
www.example.comhave in the last 7 days?What's the conversion rate for
www.example.comthis week?Which pages have the slowest Largest Contentful Paint (LCP) on
www.example.com?What are the top page journeys, recent releases, or top priority errors for
www.example.com?
Note that Cowork does not render Noibu's interactive visualizations inline, but instead returns its underlying data with links to the Noibu console where applicable.
Updating the plugin
As we continue to iterate and improve on our Copilot Cowork plugin, new and updated skills may become available. To update your plugin, the plugin owner repeats the steps for installing the Noibu plugin, uploading the latest plugin file in place of the previous one.
Cowork needs approximately 10 minutes to detect and synchronize the updated skills. After that, start a new task — an existing chat can still be holding skills from the previous version — and run /setup-noibu to reconnect your Noibu account. Skills and Noibu tools work normally from there.
Setting up Noibu in Copilot when Cowork is unavailable
Note: It is preferable to use Noibu with Copilot Cowork because the pre-built skills are available there. These instructions are for use in Copilot only, if Cowork is unavailable. In this case, you are able to query your store data but not run skills.
Noibu ships as a separate agent package for Copilot Chat and Teams. You invoke it with @Noibu and ask questions directly, rather than triggering a skill.
Prerequisites
Assign Microsoft 365 Copilot seats
Each Noibu user needs a paid Microsoft 365 Copilot seat (Copilot Business or full Copilot); Free Copilot Chat will not run the agent. A Global administrator assigns these at https://admin.microsoft.com → Users → Active users → Licences.
Enable custom-app upload
Go to https://admin.teams.microsoft.com/policies/app-setup → Teams apps → Setup policies → Global, or your own policy, and set Upload custom apps to On. This change can take up to 24 hours to take effect.
Download the Noibu agent for Copilot
The latest version of the agent package is available for download here. Unlike the Cowork plugin, each user installs this themselves.
Step 1 — Install the Noibu agent
1. Open Teams at https://teams.cloud.microsoft.
2. Go to Apps → Manage your apps → Upload an app → Upload a custom app.
3. Select the Noibu .zip package you downloaded.
Step 2 — Connect your Noibu account
1. Open Copilot at https://m365.cloud.microsoft/chat or stay in Teams.
2. Type @Noibu and ask a question.
3. On first use, sign in with your Noibu credentials when prompted. You are returned to Copilot or Teams and the agent answers.
Each person signs in individually, so you see only the domains your Noibu permissions already allow.
Step 3 — Begin analysis with Noibu and Copilot
Ask questions in plain language, always including the domain you want to look at.
How many sessions did
www.example.comhave in the last 7 days?What's the conversion rate for
www.example.comthis week?Show mobile versus desktop sessions for
www.example.comover the last 30 days.Which pages have the slowest Largest Contentful Paint (LCP) on
www.example.com?What are the top pages by visits on
www.example.comin the last 7 days?What's the daily session trend for
www.example.comover the last 7 days?What are the top page journeys, recent releases, or top priority errors for
www.example.com?Show me a replay of a session from the last 7 days on
www.example.com.
The agent covers Noibu's analytics and error tools: domain lookup, session search and trends, page visits, page journeys, releases, session lookup, priority errors, error search, error detail, error diagnosis, and error trends.
Visualizations behave as they do in Cowork: session replay returns a summary and a console link, and page visit visualizations are not available.
Troubleshooting
The skills do not appear in Cowork after installing. Cowork needs roughly 10 minutes to detect and synchronize skills after a package is installed or updated. Wait, then start a new task — an existing chat holds the state it had when it was created.
/setup-noibu is not offered in the chat dropdown in Cowork. The plugin has not finished synchronizing, or you are working in a chat that was open before the install. Start a new task and try again.
Cowork is not available in my tenant. Cowork requires tenant-level usage-based billing. Ask your Microsoft 365 admin to confirm that Copilot Credits are activated and that Cowork appears under Manage Configuration in Copilot → Cost Management.
I cannot upload the plugin package to Cowork. Custom-app upload is not enabled, or the policy change has not propagated yet. Ask your admin to confirm that Upload custom apps is set to On in the Teams admin centre, and allow up to 24 hours.
Copilot asks for a domain I already gave it. Start a new task — a pending prompt can block the rest of the conversation from routing correctly. Include the full domain in the question itself rather than referring back to one mentioned earlier.
@Noibu does not appear in Copilot or Teams. Teams and Copilot cache installed apps aggressively. Allow up to 30 minutes after installing, then sign out and back in.
I cannot upload the agent package to Copilot. Custom-app upload is not enabled in your tenant, or the policy change has not propagated. Ask your admin to confirm that Upload custom apps is set to On in the Teams admin centre.
I am blocked by a licensing error. Your Microsoft 365 Copilot licence has been purchased but not yet assigned to your user, or has not finished provisioning. Confirm the assignment under Users → Active users in the admin centre, sign out and back in, and allow up to an hour after assignment before retrying.