Build Your First AI Agent: An IT & HR Self-Service Agent with Copilot Studio

Why this is the right first agent

If your organization is just starting with AI, an internal IT and HR self-service agent is the safest, fastest win. The audience is internal, the content already exists (policies, how-to guides, FAQs), and success is easy to measure: fewer tickets, faster answers.

Typical questions it will handle:

• How do I reset my password or set up the VPN?
• How many leave days do I have left, and how do I request leave?
• Where is the expense policy, and what is the travel limit?
• I need a new laptop or software licence — how do I ask?

Architecture at a glance

• Microsoft Copilot Studio hosts the agent, its topics, and generative answers.
• SharePoint Online stores the knowledge (HR handbook, IT guides).
• Power Automate performs actions (create a ticket, check leave balance).
• Microsoft Entra ID provides single sign-on, so answers respect each user's permissions.
• Microsoft Teams is where employees talk to the agent.

Prerequisites

1. A Copilot Studio licence (or pay-as-you-go messages billed to an Azure subscription).
2. A Power Platform environment dedicated to the agent (do not build in the Default environment for production).
3. A SharePoint site containing clean, current IT and HR content.
4. Owners from IT and HR who will review answers before go-live.

Step 1 — Prepare and secure your knowledge

Generative answers are only as good as your documents. Before building anything:

1. Collect the top 50 questions from your ticketing system for the last 6 months.
2. Make sure each question has an up-to-date answer in SharePoint. Delete or archive outdated versions — the agent cannot tell which copy is "the real one".
3. Check permissions. Remove "Everyone except external users" from libraries that contain salary, disciplinary or medical documents.
4. Apply Microsoft Purview sensitivity labels to confidential HR content so it is protected even if permissions drift.

Step 2 — Create the agent

1. Open copilotstudio.microsoft.com and choose the correct environment.
2. Select Create, then New agent. Describe it in plain language, for example: "An internal assistant that answers IT and HR questions for employees of Contoso using our policies."
3. Give it a name (for example "Contoso Help"), an icon, and instructions such as:

You help Contoso employees with IT and HR questions.
Only answer using the connected knowledge sources.
If you are not sure, say so and offer to create a support ticket.
Never give legal, medical or salary advice for a specific person.
Keep answers short and include a link to the source document.

1. Under Knowledge, add your SharePoint site URLs. Copilot Studio uses the signed-in user's identity, so people only get answers from files they can already open.

Step 3 — Configure authentication

1. Go to Settings, Security, Authentication.
2. Choose "Authenticate with Microsoft". This is the simplest option for Teams and enables SharePoint grounding with the user's identity.
3. Require users to sign in. Anonymous access should never be used for an internal HR agent.

Step 4 — Add topics for common, structured requests

Generative answers handle "what is" questions. For "do something" requests, build topics:

1. Create a topic "Request new hardware" with trigger phrases like "I need a new laptop" or "my monitor is broken".
2. Add Question nodes to collect device type, reason, and urgency.
3. Add a Confirm node that summarises the request back to the user.

Step 5 — Connect actions with Power Automate

1. In the topic, add an Action and choose "Create a flow".
2. In Power Automate, add a step that creates a ticket — using the ServiceNow, Jira or SharePoint list connector depending on what you use.
3. Return the ticket number to the agent and display: "Your request has been logged as INC0012345."

A similar flow can call your HR system (for example Dynamics 365 HR or an SAP SuccessFactors connector) to read leave balances.

Step 6 — Escalation to a human

Always give people a way out:

1. Edit the built-in "Escalate" system topic.
2. Post the conversation summary to a Teams channel monitored by the service desk, or hand off to Dynamics 365 Customer Service if you use it.
3. Tell the user how long a human will take to respond.

Step 7 — Test with a pilot group

1. Use the Test pane to ask your top 50 questions. Record the result as correct, partially correct, or wrong.
2. Fix wrong answers by improving the source document, not by adding more instructions.
3. Run a two-week pilot with 30–50 employees from different departments.

Step 8 — Publish to Teams

1. Select Publish, then Channels, Microsoft Teams.
2. Submit the app to your admin. In the Teams admin center, approve the app and use an app setup policy to pin it for your pilot group, then everyone.

Measure success

Use the Analytics tab in Copilot Studio to track:

• Resolution rate (conversations solved without escalation).
• Escalation rate and the top unanswered questions.
• Customer satisfaction scores.

A good target for the first 3 months is 40–60% of common questions resolved without a ticket.

Governance checklist

• Separate development, test and production environments, moved with solutions.
• Data loss prevention (DLP) policies in the Power Platform admin center that block unapproved connectors.
• A named business owner for every knowledge source.
• A monthly review of unanswered questions.

Common mistakes to avoid

• Connecting the entire SharePoint tenant on day one.
• Treating the agent as "done" after launch — content must be maintained.
• Skipping the escalation path, which quickly destroys employee trust.

Learn more

• Microsoft Learn: Copilot Studio overview — https://learn.microsoft.com/microsoft-copilot-studio/fundamentals-what-is-copilot-studio
• Microsoft Learn: Add knowledge to an agent — https://learn.microsoft.com/microsoft-copilot-studio/knowledge-copilot-studio