AI Agents -Copilot

Creating and Deploying Copilot Agents

Complete guide to building agents in Microsoft 365 Copilot, configuring knowledge sources, automating workflows, and deploying to Teams and SharePoint

Published May 2026 | Microsoft 365 Guide

---

Copilot Agents in Microsoft 365 are intelligent digital assistants designed to automate tasks, provide insights, and streamline workflows directly within your Microsoft 365 ecosystem. Unlike generic chatbots, Copilot Agents can be tailored to your organization's specific data, processes, and business rules.

This guide covers the complete journey: from creating lightweight agents using Agent Builder, to building autonomous agents triggered by events, configuring knowledge sources, and deploying to Teams and SharePoint.

🎯 Key Insight

Copilot Agents operate in two modes: lightweight conversational agents (built via Agent Builder for business users) and autonomous agents (via Copilot Studio with Power Automate triggers for complex, event-driven automation). Choose based on your use case complexity.

---

Part 1: Creating a Basic Agent (Agent Builder)

1Access the Agent Builder

The Agent Builder provides a fast, natural-language interface designed for business users to create lightweight agents without technical expertise.

Getting Started

• Open Copilot Chat in your Microsoft 365 environment
• Look for "Create an agent" in the right pane
• Click to launch the Agent Builder wizard

💡 Pro Tip

Agent Builder is optimized for business users without coding experience. If you need complex automation with event triggers and AI decision-making, use Copilot Studio (Part 2) instead.

2Describe Your Agent

You'll be placed in the "Describe" menu. Simply type a description of what you want your agent to do.

Example Descriptions

"Create an agent that helps my project team figure out next steps and track deliverables" "Build an agent that summarizes customer feedback from Teams channels and emails" "I need an agent that extracts key dates and values from contracts"

Copilot will automatically generate:

• Agent name: Auto-generated based on your description
• Icon: A unique visual identifier for your agent
• Description: Refined prompt that becomes the agent's core instruction

3Add Knowledge Sources

Knowledge sources are the foundation of a useful agent. They define what information your agent can access and reference when responding to users.

Supported Knowledge Sources

• SharePoint sites: Entire sites or specific document libraries
• Microsoft Teams: Specific chats, channels, or channel conversations
• Emails: Specific mailbox folders or email threads
• Uploaded files: PDFs, Word documents, Excel spreadsheets, or images

Critical Best Practice

In the Configure tab, toggle "Only use specified sources" to restrict your agent from using general internet knowledge. This is the single most important step for:

• Reducing AI hallucinations (false or fabricated information)
• Keeping responses focused on your company data only
• Ensuring accuracy and compliance with corporate policies

⚠️ Critical Setting: Always enable "Only use specified sources" for production agents. Without this setting, agents will make up information when they don't find relevant data in your sources.

4Customize Capabilities and Instructions

In the Configure tab, you can fine-tune every aspect of your agent's behavior, capabilities, and user experience.

Key Customizations

• Step-by-step instructions: Edit the exact behavior guidelines your agent follows
• Tone and style: Set whether the agent is formal, conversational, technical, etc.
• Behavioral guidelines: Define what the agent should never do (e.g., "never share salary information")
• Capabilities toggle: Enable features like code generation, image creation, or document generation

Enabling Advanced Capabilities

Flip switches to unlock additional agent powers:

• Code generation: Agent can write Python, JavaScript, SQL, or other code
• Image generation: Create images based on user descriptions
• Document generation: Create PowerPoint presentations, Word documents, or Excel files on the fly

Suggested Prompts

Define 3-5 Suggested Prompts to guide users on how to interact with your agent:

"Summarize the Q3 budget from our finance docs" "Create a one-page summary of project status" "List all open risks and mitigation plans"

5Publish and Share

Once configured, publish your agent to make it available to users.

Publishing Steps

1. Click "Create" to finalize your agent
2. Click "Share" to set access permissions
3. Choose who can access:
   • Specific users: By individual email address
   • Security groups: By Microsoft Entra group
   • Organization-wide: Available to anyone in your tenant
4. Copy the agent link and send directly in Teams chats for quick access

🔐 Security Tip

Start by sharing with a small pilot group (5-10 users) to test behavior. Once you validate it performs correctly, expand access to broader teams.

---

Part 2: Creating Autonomous Agents (Copilot Studio + Power Automate)

If you need your agent to operate independently, perform complex multi-step tasks, or run automatically based on schedules or events, you must use the full Copilot Studio platform. This is where you combine Copilot Studio agent logic + Power Automate triggers to create truly autonomous agents.

6Enable Generative Orchestration

Generative Orchestration is the AI engine that allows agents to make autonomous decisions about how to respond and sequence their actions.

Configuration

• In Copilot Studio, create your agent
• Locate the "Generative AI Orchestration" setting
• Toggle ON to enable autonomous decision-making

When enabled, your agent can:

• Determine the best action to take based on the current situation
• Sequence multiple actions in the right order
• Handle edge cases and exceptions intelligently
• Recover from errors automatically

🤖 Autonomous Behavior

With Generative Orchestration enabled, you don't need to define every possible path. Instead, you tell the AI what tools/actions are available, and it figures out how to use them to solve the user's request.

7Set Up Event Triggers (Power Automate)

Event triggers tell your agent when to automatically wake up and perform tasks. Triggers are configured via Power Automate.

Common Trigger Examples

• Email trigger: "When a new email arrives (V3)" from Outlook - agent processes incoming contracts automatically
• Schedule trigger: "Recurrence" (daily at 2 AM) - agent runs daily reports or checks
• Form submission: When a SharePoint form is submitted, agent extracts data and updates records
• Teams message trigger: When specific keywords appear in Teams, agent responds or escalates

Setting Up Email Trigger Example

Trigger: When a new email arrives (V3) From: contracts@company.com Subject Contains: "Contract for review" → Agent extracts contract value, dates, and signatory → Agent saves to SharePoint list → Agent posts summary to Teams channel

⚡ Trigger Strategy

Use email or form triggers for inbound data processing (contracts, requests, feedback). Use scheduled triggers for daily/weekly reports or compliance checks. Use Teams triggers for real-time conversational automation.

8Define Agent Actions

Actions are what your agent actually does when triggered. They can update systems, query databases, process documents, or post results to Teams.

Supported Action Types

• Power Automate flows: Update Dynamics 365, query APIs, send notifications
• AI Builder models: Document processing (extract contract fields), sentiment analysis
• Teams integration: Post Adaptive Cards with formatted results
• SharePoint/Dataverse: Create/update items in lists or tables

Example: Contract Processing Workflow

TRIGGER: New email arrives with contract ↓ ACTION 1 (AI Builder): Extract contract value, dates, parties ↓ ACTION 2 (SharePoint): Save extracted data to Contracts list ↓ ACTION 3 (Teams): Post summary as Adaptive Card to Legal channel ↓ ACTION 4 (Power Automate): Send reminder email to CFO if value > $100K

Best Practice: Chain multiple actions together. For instance: Document Processing → Data Extraction → Database Update → Notification → Escalation. This creates end-to-end automation without human intervention.

---

Part 3: Deploying Agents to Teams and SharePoint

9Deploy to Microsoft Teams

Once your agent is built and published in Copilot Studio, deploy it to Teams so users can access it directly in their workspace.

Deployment Steps

1. In Copilot Studio, ensure your agent is published
2. Click "Add channel" and select Microsoft Teams
3. Choose availability:
   • "Show to my teammates and shared users": Deploy to specific security group
   • "Organization-wide": Submit for organization-wide availability
4. If org-wide, obtain approval from Teams Administrator in Teams Admin Center
5. Once approved, agent appears as a pinned app in Teams sidebar for all users

🚀 Approval Process

Organization-wide deployment requires Teams Admin approval. This review ensures the agent complies with data governance and security policies. Allow 1-3 business days for approval.

10Deploy to SharePoint

Make your agent available directly within a SharePoint site so team members can interact with it while viewing documents and lists.

Deployment Steps

1. In Copilot Studio, click "Channels"
2. Select SharePoint
3. Provide the target SharePoint site URL:
   • Example: https://company.sharepoint.com/sites/ProjectAlpha
4. Click "Deploy"
5. Wait 30 minutes for the Copilot agent icon to render on your SharePoint site

Rendering Timeline

After deployment:

• Immediately: Agent appears in Copilot Studio as deployed
• 5-15 minutes: Agent starts processing requests in SharePoint
• 20-30 minutes: Copilot icon fully renders in SharePoint UI
• After 30 minutes: Agent is fully operational and visible to all site members

Note: Do not navigate away from SharePoint immediately after deployment. Give it 5 minutes for the integration to activate. If the icon doesn't appear after 30 minutes, refresh your browser or clear cache.

---

Key Takeaways

Agent Builder

Fast, natural-language interface for business users. Perfect for lightweight conversational agents with knowledge sources.

Knowledge Sources

Connect agents to SharePoint, Teams, emails, files. CRITICAL: Enable "Only use specified sources" to prevent hallucinations.

Capabilities

Enable code generation, image creation, or document generation. Define suggested prompts to guide user interactions.

Autonomous Agents

Use Copilot Studio + Power Automate for event-driven automation. Enable Generative Orchestration for autonomous decision-making.

Event Triggers

Configure Power Automate triggers (email, schedule, form submit) to automatically wake up agents and process tasks.

Deployment

Deploy to Teams (group or org-wide with approval) or SharePoint. Allow 30 minutes for full rendering and functionality.

🎯 FazDane Perspective: The Future of Work

Copilot Agents represent a fundamental shift in how work gets done. While Agent Builder is for lightweight tasks, the real power emerges when you combine Copilot Studio + Power Automate + knowledge sources. Contract processing, expense reporting, customer escalation, compliance checks - all become autonomous. The teams that master agent deployment in 2026 will have 2x throughput with 50% fewer manual steps. The key is ruthlessness in setup: precise knowledge sources, clear behavioral boundaries, and event-driven triggers. Vague agents cause chaos; precise agents multiply capability.

This guide was produced by FazDane Analytics based on Microsoft 365 Copilot documentation and best practices. Specific features, UI elements, and availability may vary by region and subscription plan. For current information, refer to official Microsoft 365 documentation. Deployment timelines and approval processes may vary by organization. Always test agents with pilot groups before organization-wide deployment.

FazDane Analytics - Microsoft 365 Enterprise Documentation - Copyright 2026