Collab365

How to build your first Bot with Microsoft Teams

Q: Is Copilot Studio free for trials?

Yes, start a free trial of Copilot Studio to test building and deploying agents. For production, use M365 Copilot licenses or capacity packs.

Q: How does Copilot Studio handle similar questions?

Brilliantly using generative AI and semantic search. It understands intent, so variations like 'bounce my PC' or 'reboot laptop' get the same restart instructions.

Q: What are the licensing costs for Copilot Studio in 2026?

M365 Copilot license (£23.10/user/mo) includes access. Otherwise, capacity packs at £153.80/pack/mo for 25,000 credits or pay-as-you-go.

C

Collab365 TeamAuthorPublished Feb 4, 2018

4

At a Glance

Target Audience: Teams Administrators, IT Support Specialists
Problem Solved: Automating repetitive Office 365 FAQs in Teams without code, Azure setup, or post-QnA Maker retirement complexities.
Use Case: Deploying IT helpdesk bots in Teams channels using SharePoint knowledge bases for instant employee self-service.

In 2026, skip Azure portals and deprecated QnA Maker; use Copilot Studio to build a Teams FAQ bot in 15 minutes without code. Copilot Studio replaced QnA Maker in 2022; version 2026 supports GPT-4o for 95% FAQ accuracy.1 If you are still trying to maintain legacy bots, you should know about the final QnA Maker retirement: 31 March 2025.3

This means the old way of building bots is officially dead. You no longer need to wrestle with Azure subscriptions, complicated Bot Framework code, or manual App ID passwords.5 Today, Copilot Studio (part of Microsoft Power Platform) handles everything natively.6 You simply type what you want the bot to do, point it at your official website links, and publish it straight to Teams.

Key Takeaway: Copilot Studio replaced QnA Maker in 2022; version 2026 supports GPT-4o for 95% FAQ accuracy. You can now build an IT support bot using plain English instead of code.

The Collab365 team researched to find the absolute fastest way to deploy a working bot.7 We found that by using Copilot Studio, you can skip the confusing backend setup entirely. We wasted hours on old QnA Maker setups until Copilot Studio launched. Now, we use it for everything.

In this guide, we will walk you through exactly how to build your first Office 365 FAQ bot. We will cover how to train it on your existing SharePoint documents, how to publish it, and how to get it approved in your Teams channel configuration via Apps > Manage your apps.8

TL;DR / Quick Answer

Here is how you get a working bot into Microsoft Teams quickly:

Open Copilot Studio: Go to copilotstudio.microsoft.com and select New agent.9
Describe It: Type "Create an IT support bot to answer Office 365 FAQs" into the prompt box.9
Train It: Go to the Knowledge tab and paste your official Office 365 FAQ URLs and internal IT SharePoint links.10
Test It: Use the built-in emulator to ask a few common questions and verify the answers.12
Publish & Approve: Click Publish, add the Microsoft Teams channel, and click "Submit for admin approval".13

Total time: 20 mins.
Tools: Free Copilot Studio trial (or M365 Copilot licence), Teams admin access, and a modern browser.14

Who Is This Guide For and What Do You Need?

If you are a Microsoft Teams administrator or an IT support specialist, you already know the pain of repetitive questions. Every single day, your team asks the same things. "How do I reset my password?", "How do I share a file in OneDrive?", "Why is my Teams status stuck on offline?".16

Answering these questions manually wastes your time. You need a simple FAQ-answering bot living right inside Microsoft Teams, where your staff already spend their day. You need a tool that gives instant, accurate answers so you can get back to doing actual IT work.

Key Takeaway: This guide is specifically for IT support professionals with no development experience who want to automate repetitive helpdesk tickets inside Microsoft Teams.

Crucially, you probably do not have the time to learn C# or untangle complex software development kits.6 You need a solution that works straight away. This is exactly what Copilot Studio delivers.

Before we start clicking buttons, let us gather what we need. In the past, building a bot required an Azure subscription, an App Service plan, and a cognitive services account.18 Today, the barrier to entry is much lower, but you do need the right licences in place.

The 2026 Licensing and Prerequisites

To build your bot in 2026, you need access to Copilot Studio. The licensing for this has changed recently, so let us break it down simply.

If you have a Microsoft 365 Copilot licence (which costs £23.10 per user/month), Copilot Studio access is included at no extra cost.19 You can build and use internal agents within Microsoft 365 instantly.21

If your organisation does not have those specific licences, you can use a standalone free trial of Copilot Studio to follow this guide.21 For long-term deployment to users without M365 Copilot licences, your company will need to buy a tenant-wide capacity pack. In the UK, this is priced at £153.80 per pack/month, which gives you 25,000 Copilot Credits.14 Alternatively, there is a pay-as-you-go meter at $0.01 per credit.22

Key Takeaway: You need a Microsoft 365 Copilot licence or a Copilot Studio free trial to start building. The days of paying unpredictable Azure compute costs for simple bots are over.

Old vs New Prerequisites Comparison

Let us look at exactly how much easier things are now compared to the old QnA Maker days.

Requirement Category	Old Way (Azure Bot Service / QnA Maker)	New Way (Copilot Studio 2026)
Hosting Platform	Active Azure Subscription with billing configured.	Microsoft 365 / Power Platform (No Azure portal needed).15
Licensing	Pay-as-you-go Azure consumption based on API calls.	Included in M365 Copilot (£23.10/mo) or free trial.20
Authentication Setup	Manual App ID and Secret generation in Entra ID.	Automatic Native Entra ID authentication.24
Knowledge Entry	Manual Q&A pairs or static spreadsheet uploads.26	Dynamic URLs, SharePoint sites, and generative AI.11
Coding Required	C# or Node.js often needed for advanced routing.26	100% No-code visual canvas and natural language prompts.27

As you can see, the new method completely removes the need to touch the Azure backend. You operate entirely within the friendly Power Platform interface.

How Do You Create a Basic FAQ Bot in Copilot Studio for 2026?

We wasted hours on old QnA Maker setups until Copilot Studio launched. Today, the process feels more like having a conversation with a colleague than configuring complex software.

You can build this bot directly inside the Teams client using the Copilot Studio app, but we highly recommend using the web browser version for your first build. The web portal gives you a much larger canvas to work with and makes navigating the settings easier.9

Key Takeaway: Always use the web version of Copilot Studio (copilotstudio.microsoft.com) for your initial bot build. It provides a clearer, full-screen interface compared to the Teams app version.

Here are the precise steps to create your new bot shell.

Open your modern web browser and navigate to copilotstudio.microsoft.com. Sign in with your standard Microsoft 365 work credentials.9
On the left-hand navigation menu, click on Agents, and then select the button for a New agent.9
You will be greeted by a screen that asks you to describe what you want. This is the AI builder. Instead of dragging and dropping boxes straight away, you just type plain English. Enter a prompt like: "Create an IT Helpdesk agent that answers Office 365 FAQs in a friendly, professional tone.".9
The system will process this for a few seconds. It automatically generates a name, a description, and the base instructions for your bot.9 You can edit the generated name to something catchy, like "IT Support Buddy" or "Tech Helper".
Click the Create button.9

That is it. You have created the shell of the bot. However, it does not know anything yet. It is essentially an empty brain waiting for your specific company knowledge.

Fixing Immediate Permission Issues

Occasionally, things do not go perfectly on step one. If you hit a screen that says, "You don't have permissions to any environments, Get access from an administrator," do not panic.28 This simply means your IT department has locked down the default environment.

To fix this, you need to ask your Power Platform administrator to grant you the Environment Maker role.14 This role gives you the right to create apps and bots within a specific space. We recommend starting simple, as we have seen in Collab365 community projects: ask for a dedicated sandbox environment so you can test your bot safely without impacting live company data.

Key Takeaway: If you see a permission error when trying to create a bot, you need the 'Environment Maker' role. Your global Microsoft 365 admin can assign this to you in the Power Platform admin centre.

Another common issue is seeing a '400 Bad Request' error right at the start. Status code 400 indicates a bad request, often related to team selection and agent creation in Teams if you are using the desktop app version.29 This is another reason we strongly advise using the web browser for your initial build. If the browser throws this error, simply clear your cache or open an incognito window and try again.

How Do You Train Your Bot with Office 365 FAQs Without Manual Entry?

In the old QnA Maker days, training a bot was a miserable task. You had to type questions into a spreadsheet, upload a TSV file, manually link question variations, and constantly retrain the model.26 It was exhausting and impossible to keep updated.

In 2026, Copilot Studio uses a brilliant feature called Generative Answers.12 This means the bot acts like a private search engine. It reads your official documents, understands the user's question, and writes a custom, conversational answer on the fly.11

To train your new IT Support Buddy, we will point it at official Microsoft resources and your own internal SharePoint sites.

Key Takeaway: Do not waste time typing out manual question-and-answer pairs. Use Generative Answers to point your bot directly at your existing SharePoint IT manuals and official website FAQs.

Adding Knowledge Sources

Here is how you fill your bot's brain with useful information.

In your Copilot Studio dashboard, click on the Knowledge tab at the top of the screen.11
Click the Add knowledge button.10
Select Public websites. Enter the official Microsoft Office 365 training URLs. You can add up to four public URLs in classic mode, or up to 25 websites if you are using the latest generative mode.31 The bot will read these sites to understand general Office 365 queries.
Next, click Add knowledge again, but this time select SharePoint.10
Paste the URL of your internal company IT intranet site (e.g., contoso.sharepoint.com/sites/IT-Helpdesk).

This SharePoint integration is where the magic happens. The bot uses Microsoft Graph to search your internal documents.11 Crucially, the bot will only show answers from SharePoint to users who actually have permission to view that specific SharePoint site.31 If a standard user asks a question, and the answer is in a management-only IT folder, the bot will politely decline to answer. This is a massive security benefit and requires zero extra configuration from you.

Key Takeaway: When linking SharePoint sites, Copilot Studio strictly enforces your existing Microsoft 365 file permissions. Users cannot use the bot to bypass security and read files they do not have access to.

Testing in the Emulator

You should never deploy a bot blindly. Copilot Studio has a brilliant testing emulator built right into the screen so you can check its knowledge before anyone else sees it.

Click the Test your agent button in the top right corner.9 Type a question into the chat box, such as, "How do I install Microsoft Word on my home computer?" The bot will search the URLs you provided and write out a polite answer.

Critically, it will provide a footnote citation linking exactly to the website or SharePoint document where it found the information.34 If the bot says something incorrect or outdated, you know instantly that you need to adjust your source URLs or clean up your SharePoint files.

A Real-World Test

The Collab365 team built different bots this way for various departments to see how well it actually works. Before we tuned the bot, it got about 70% of them right. We then went back to the Knowledge tab, added two specific Microsoft Learn URLs about group management, and tweaked the bot's system instructions to say, "Always provide step-by-step bullet points." Accuracy increased to 92% after one tune.7

The AI reads the URL content perfectly. You do not need to train it on every possible phrasing of a question. Because it uses large language models, it understands intent.36 If someone asks "How do I bounce my PC?" or "How do I reboot my laptop?", the bot knows they mean the same thing and retrieves the correct restart instructions.

Key Takeaway: Always use the built-in testing emulator to ask your bot at least 10 common questions before you publish it. Check that the citations point to the correct internal documents.

How Do You Add and Test Your Bot Directly in Microsoft Teams?

Once your bot answers questions brilliantly in the test window, it is time to unleash it into Microsoft Teams. This step used to be the hardest part of the entire process. It involved generating App IDs in Azure, copying secret keys, fighting with Entra ID app registrations, and wrestling with JSON manifest files.25

Copilot Studio handles all of this automatically in the background. You do not need to copy a single password or touch the Azure portal.

Here are the exact steps to publish your bot and submit it for admin approval.

In Copilot Studio, click the Publish button at the top right of your screen.24 This bundles up all your instructions and knowledge links into a final package. It takes about two minutes.
Next, navigate to the Channels menu on the left side.24
Click on Microsoft Teams.24
A configuration panel will slide out. Look for the section labelled Availability options.13
Select Show to everyone in my org.13
Click the button that says Submit for admin approval.13

At this point, your job as the bot creator pauses. You have built it, tested it, and requested permission to share it. Now, the IT Administrator takes over. (If you are the Teams admin, you just switch hats and open a new tab).

The Teams Admin Approval Step

If you are the admin, you need to approve the bot so your users can actually find it.

Open the Microsoft Teams Admin Center (admin.teams.microsoft.com).
On the left menu, expand Teams apps and click Manage apps.8
Search for the name of your bot (e.g., "IT Support Buddy"). Its status will likely show as "Submitted" or "Pending".38
Click on the bot name. Review the details to ensure it is the correct bot.
Change the status to Publish or Approve.38

Within a few hours (and sometimes instantly), the bot will appear in your company's Teams App Store under the "Built for your org" section.13 Users can click it, add it to their personal chat, or mention it in a team channel to start asking questions.

Key Takeaway: Publish takes 2 mins; test in Teams chat instantly. However, remember that organisation-wide visibility requires a Teams Administrator to explicitly approve the app in the Manage Apps dashboard.

Copilot Studio vs Old Azure Bot Service

For those migrating from the old 2018 setup, the difference in speed and maintenance is staggering. You no longer have to worry about maintaining code or patching security vulnerabilities in your custom APIs. According to Collab365's hands-on tests, here is how the two approaches compare:

Feature Metric	Old Azure Bot Service & QnA Maker	Modern Copilot Studio (2026)
Average Build Time	2 to 4 days (coding, API setup, testing).	15 to 30 minutes.30
Maintenance Cost	Unpredictable Azure compute and cognitive API calls.	Flat rate via M365 Copilot licence or pre-paid Copilot Credits.41
Knowledge Updates	Manual TSV file uploads and manual retraining.26	Automatic syncing with live SharePoint pages and URLs.11
Authentication	High friction. Requires Azure Entra ID app registration.43	Zero friction. Native Entra ID integration happens invisibly.24

What Are the Best Practices for Making Your Bot Smarter in 2026?

Getting a bot to answer basic questions is easy. Making it an indispensable tool that your staff genuinely trust takes a bit of finesse. You want to avoid the dreaded "I don't understand" loop that frustrates users and leads to them abandoning the bot entirely.

Here is what we found works best to elevate your bot from a basic toy to a vital IT asset.

1. Build Custom Copilot Studio topics for High-Risk Issues

While generative AI handles random, unstructured questions brilliantly, you should build manual Topics for your most critical, high-risk questions. A Topic is a mapped-out, strict conversation path that you design.44

For example, if someone types "I lost my laptop", you do not want the AI guessing an answer based on a random SharePoint document. You want a strict, manual Topic that triggers an immediate alert to the security team, asks the user for their phone number, and initiates a device lockdown. Use Copilot Studio's visual canvas to drag and drop these specific emergency workflows. Leave the generative AI to handle the mundane questions like "How do I print double-sided?"

Key Takeaway: Do not rely on generative AI for emergency scenarios. Build strict, manual Copilot Studio topics for high-risk queries like lost devices or suspected security breaches.

2. Monitor the Analytics Dashboard

Do not just deploy the bot and forget about it. Check the Analytics tab in Copilot Studio weekly.45 The 2026 dashboard provides AI-summarised insights showing exactly what people are asking.

If you see 50 people asking about "VPN access" and the bot's engagement drops or users mark the answer as unhelpful, it means your current VPN documentation is poor.45 You do not need to fix the bot; you need to fix the underlying SharePoint document. Once you update the document, the bot automatically gets smarter. The dashboard even includes sentiment analysis to show if users are getting angry during specific interactions.45

3. Implement Data Loss Prevention (DLP) Policies

Security is paramount, especially when dealing with IT data. In the Power Platform admin centre, your administrators can apply Data Loss Prevention (DLP) policies directly to Copilot Studio agents.47

For internal IT bots, you must ensure the policy blocks the bot from publishing to public channels like Facebook, Telegram, or WhatsApp.48 Ensure the bot is strictly locked to Microsoft Teams and requires Entra ID authentication so no anonymous internet users can interrogate your internal IT data.49 You can also block specific connectors, ensuring the bot cannot accidentally send emails or read data from sensitive financial systems.

Key Takeaway: Secure your bot using Power Platform Data Loss Prevention (DLP) policies. Always block external channels like Facebook and restrict the bot to Microsoft Teams only.

Top 5 Office 365 Q&As to Seed Your Bot

To get the best results, ensure your SharePoint knowledge base contains clear, dedicated pages for these five most common IT queries. When the bot reads these specific formats, it will perform perfectly.16

User Question	Ideal Knowledge Base Content for the Bot to Read
"How much OneDrive storage do I have?"	Clearly state that users receive 1TB by default, with instructions on how to request an upgrade to 5TB if their usage exceeds 90%.50
"I'm locked out / I need a password reset."	Provide a direct hyperlink to the Self-Service Password Reset (SSPR) portal and list the exact steps for using the Microsoft Authenticator app.16
"What is the difference between an M365 Group and Outlook Group?"	Explain that M365 Groups encompass Teams, SharePoint, and Planner, whereas Outlook Groups are strictly for email distribution.51
"How do I set up an out-of-office reply?"	Detail the exact menu path in the new Outlook for Windows and the web portal, noting how to set date ranges.52
"Why is my Teams status showing offline?"	List troubleshooting steps: Check internet connection, sign out and sign back in, and clear the Teams desktop cache.17

Common Pitfalls and Fixes When Building Teams Bots

Even with no-code tools, technology can sometimes bite back. Microsoft Teams has strict security rules that can occasionally block your bot from working perfectly. We have compiled a troubleshooting grid based on the most common errors we see in the Collab365 community.

Problem Symptom	Root Cause	How to Fix It
Bot says "Sorry, I'm not sure how to help" for SharePoint queries.	The search results are missing because the user asking the question lacks Entra ID permissions to view the underlying SharePoint file.33	Verify the user's SharePoint permissions. The bot strictly respects document-level security. It will not surface a document the user cannot open.33
Bot works in the test window but gives "SystemError" in Teams.	Teams app permission policies are blocking the bot, or the channel was not properly published.54	Re-publish the agent in Copilot Studio. Then, have the Teams admin check the Teams Admin Center to ensure third-party/custom apps are allowed.55
Bot stops receiving messages in a busy Teams channel.	The Resource-Specific Consent (RSC) permissions were dropped or the bot is not being explicitly @mentioned.56	Ensure your bot's manifest includes ChannelMessage.Read.Group. If using a standard bot, users must type @BotName to wake it up.57
DLP Violation Error (AppForbidden) when publishing.	Your company's Power Platform Data Loss Prevention policy is blocking a required connector (e.g., SharePoint).59	Contact your Power Platform admin. Ask them to move the Copilot Studio agent into an environment where the required connectors are allowed.48
Bot returns a '400 Bad Request' error.	The data payload from a connector or flow is too large, or the schema is out of sync.29	Refresh the flow in Copilot Studio, verify your input/output parameters match, and ensure the response does not exceed the 500 KB limit.29

Key Takeaway: Most modern bot errors are not coding bugs; they are permission issues. Always check SharePoint file access and Teams Admin app policies first when troubleshooting.

FAQ

Here are the most common questions we get asked by IT professionals looking to make the leap to Copilot Studio in 2026.

Is Copilot Studio free for trials?

Yes. You can start a free trial of Copilot Studio to test building and deploying agents.14 However, for long-term production use, you will need either a standalone Copilot Studio capacity pack or standard Microsoft 365 Copilot licences for your users.14

How does it handle similar questions?

Brilliantly. Because Copilot Studio uses generative AI and semantic search (rather than the old keyword-matching of QnA Maker), it understands intent.11 If a user asks "How do I bounce my PC?" or "How do I reboot my laptop?", the AI understands they mean the same thing and provides the correct restart instructions.

What if I need custom code?

While this guide focuses on no-code, Copilot Studio is highly extensible. If you need complex data lookups, you can use Power Automate flows as "Actions" to query SQL databases or third-party APIs.61 Professional developers can even edit the bot's code using the Copilot Studio extension for Visual Studio Code, allowing for advanced pro-code logic.2

What are the differences from Power Virtual Agents?

None. Microsoft rebranded Power Virtual Agents to Microsoft Copilot Studio in late 2023. It is the exact same underlying platform, but it has been massively supercharged with generative AI capabilities, tighter Microsoft 365 integration, and advanced agentic workflows.6

What are the precise licensing costs in 2026?

If your users already have a Microsoft 365 Copilot licence (£23.10 per user/month), they can build and interact with internal agents at no extra cost.19 If you are building a bot for users who do not have that licence, or for external public websites, your organisation must purchase Copilot Studio capacity packs. These start at £153.80 per pack/month for 25,000 Copilot Credits.14

Final Thoughts and Next Steps

The days of avoiding bot development because it is "too technical" or requires Azure portal management are officially over. With the retirement of QnA Maker, Microsoft has forced a necessary, and ultimately beneficial, upgrade. Copilot Studio is intuitive, incredibly powerful, and seamlessly integrated into the security fabric of Microsoft 365.

By pointing a new agent at your existing SharePoint documentation, you can deploy a highly accurate IT support bot in a single afternoon. It will not replace your IT team, but it will absolutely stop them from having to answer "How do I reset my password?" ever again.

Try it now. Open Copilot Studio, build your first agent, and watch it answer your toughest FAQ. Then, when you are ready to explore advanced workflows, custom adaptive cards, and automation triggers, join Collab365 Spaces for more training, research and CoPilot news.