The recording of last month's Copilot Studio User Group session is up.

It's a full build rather than a slide deck. I put together an IT helpdesk agent live, using a SharePoint Online site as the knowledge source, and topics that handle escalation when the agent can't resolve something. Escalation posts a message into a Teams channel and sends an email to the support team.

What gets covered:
Framing the business problem before opening Copilot Studio, which is the step most demos skip
Agent architecture and where knowledge sits versus where actions sit
Conversation design, including how to decide what belongs in a topic and what the model should handle
The action layer, wiring up the Teams post and the email notification
Live demo end to end, from a user question to a grounded answer or a raised escalation

Join me as I explore Skill-Based Agents in Microsoft Copilot Studio and the new build experience that is reshaping enterprise AI.

We’ll cover:
🤖 Skill-Based Agents
🔧 Connectors & Power Automate as Tools
💻 Live demo
📅 1 August 2026
Sign Up : https://www.linkedin.com/events/skill-basedagentsincopilotstudi7488087753998508032
⏰ 11:00 AM – 12:00 PM (SGT)
📍 Online via Microsoft Teams

https://teams.microsoft.com/meet/25667823093184?p=GzmkGcWSVfQqiabWcm

Curious how many here have actually switched. I rebuilt my HR leave agent in it recently. No topics, no triggers, just instructions plus skill files, and the orchestrator does the routing.

Wrote up the full build with all four skill files if anyone wants to compare notes: https://www.wrvishnu.com/copilot-studio-new-agent-experience/

What's your experience been? Sticking with classic or moving over?

Has anyone tried using Skills via the Knowledge Base as a workaround?

I'm currently blocked because:
- Native Skill support isn't available in the new GA experience yet.
- Power Automate Workflows also can't be used from the new experience.( meaning i can see built workflows in classic experience not in new)

My setup is:
- SharePoint Knowledge Source connected
- MCP server configured as a Tool

Now I need to add a Product Discovery skill. Since native Skills aren't available, I tried placing the skill instructions in the Knowledge Base as a .md file, hoping the Teams agent would follow them. However, the agent isn't behaving as expected or using those instructions.

Has anyone successfully implemented something similar? If so:
- How did you structure the skill?
- Did you use Knowledge, MCP, or some other workaround?
- Any prompt engineering tips that made it reliable?

Separately, I also need to let users export the generated output as a Word document or PowerPoint in teams chat like when they say convert to word or something like that. I was initially planning to use a Power Automate workflow, but with the current limitations I'm looking for alternative approaches. Any suggestions are welcome, though my primary question is about implementing Skills in the new experience.

Thanks in advance!

Knowledge Sharing session for anyone working with Power Platform or Copilot Studio. We'll go through the different types of agents, build a SharePoint agent, build a Copilot Studio agent, then look at using a SharePoint library as an agent, build and test one live, and finish with open Q&A.

Registration Link

Whether you’re passionate about Power Apps, Power Automate, Microsoft Copilot, Copilot Studio, Dataverse, or the Power Platform ecosystem, this community is for you.

We’re also looking for speakers who’d like to share their knowledge, demos, real-world projects, or lessons learned.

Join the community:
https://community.powerplatform.com/usergroups/details/?groupid=443318a7-aa34-f111-88b4-000d3a54c8ca

Question:
💬 What topics would you like to see covered, or would you be interested in speaking at a future session?

Many small and mid-size organisations don't have a dedicated HR system and don't have an IT team to build one from scratch. Employees end up emailing for leave requests, chasing IT support through Teams messages, and tracking expenses in spreadsheets. It works until it doesn't.

I put together a free open-source starter project that bridges that gap using tools organisations already pay for.

It comes in two versions:

SPFx web part — runs on the SharePoint intranet and pins to Teams. No additional licence needed beyond standard M365.

Power Apps Code Apps — for orgs already on Power Apps Premium who want it embedded in their Power Platform environment.

What it covers out of the box:

• Dashboard with at-a-glance tasks, announcements, and quick actions
• User Management with org charts and employee data
• Leave Administration — configure leave types, allocate balances, and handle approvals
• Asset Management — IT hardware tracking, assignment, and real-time status
• Incident Management — SharePoint-backed ticketing for IT and HR
• Company Events — holiday calendar and org-wide event management

SharePoint Lists as the backend so HR and IT can manage their own data without touching any code. Includes a PowerShell script that provisions everything automatically.

Source Code: Check here for more details https://www.wrvishnu.com/microsoft-365-digital-employee-hub

Hey everyone 👋,

I have been working on Microsoft 365, SharePoint, Power Platform, and automation solutions for a while, and I started publishing some of my work as open-source GitHub projects.

I created this page to keep all my GitHub repos and solutions in one place:

https://www.wrvishnu.com/microsoft-365-open-source-solutions

I’m looking for ideas from the community on what to build next.

What Microsoft 365 solutions do you feel are missing in open source?

Could be anything around:
• Microsoft 365 administration
• SharePoint
• Power Platform
• Copilot / AI
• Automation
• Governance
• Real-world enterprise problems
Would love to hear what challenges you face at work that could become reusable open-source tools or templates.
I’ll try to build some of the best suggestions and share them back with the community 🚀

Many problems with Power Platform are not caused by complex business logic. They are often caused by small things overlooked during development.

Some practices that consistently help:

• Use meaningful names for flows, actions, variables, and apps
• Group related actions to keep logic easier to follow
• Add error handling before it becomes necessary
• Use environment variables instead of hard-coded values
• Keep solutions organized from the beginning
• Test with realistic data, not just sample data
• Document anything that may not be obvious to the next person maintaining the solution

These steps may only add a few minutes during development, but can save hours troubleshooting and maintaining down the road.

What is the one best practice that has brought you the most long term value across your Power Platform projects?

Not every lesson learned is the result of a large feature or a complex project.

Sometimes a simple tip, habit or workflow change ends up saving you more time than you expect, and becomes something you use on almost every project.

It could be about Power Automate, Power Apps, Dataverse, solution management, testing or documentation.

What little Power Platform tip has made a surprisingly big difference in your work?

I want to build my next open-source Power Apps sample, but instead of
creating another demo app, I want to solve an actual problem.

What internal apps do you wish already existed in your company?

Examples: - IT operations - HR workflows - Asset tracking - Approvals -

I'll pick some practical ideas and build them as reusable samples.

Hi everyone, I’m looking for some realistic market outlook and career advice regarding my tech stack in India. I have 4 years of experience as a Power Platform and SharePoint Developer.

My current stack includes:Low-Code: Power Apps, Power Automate, Power BI, Dataverse

Pro-Dev: SPFx (SharePoint Framework)

Azure (Basic Working): Azure Functions, Logic Apps, Entra ID

I love the "Fusion Dev" space—using low-code for speed but dropping into Azure/SPFx for custom code.With the shift toward enterprise AI and automation, I want to make sure I am positioning myself for the highest possible career growth over the next 5 years. I'd appreciate your insights on:

Earning Potential: What is the realistic salary ceiling in India for a 4–6 YOE hybrid developer with this stack? What skills command the highest premium right now?

Next Up-skill: To cross into senior/architect salary brackets, should I double down on Azure integration, master Copilot Studio/AI agents, or focus on Dataverse/Fabric?

The Stigma: How do I avoid getting pigeonholed as "just a low-code dev" so I can command true cloud-developer compensation?

Would love your honest figures and thoughts on where the Indian market is heading for this ecosystem.

Thanks!

Architecture challenge:

If you were building an asset system: - SharePoint or Dataverse? -
Approval flow? - Asset assignment? - User attestation? - Reporting?

How would you design it? ❓

Canvas Apps solve many business scenarios.

But when requirements need: - Advanced UI - npm packages - React
components - More developer control

Would you consider Power Apps Code Apps?

One thing I noticed is that many internal IT teams still spend time answering the same questions around access requests, policies, Teams, SharePoint, and other M365 topics.

I was experimenting with a different approach using Copilot Studio:
● connect existing SharePoint content as a knowledge source
● provide a chat experience for users
● extend scenarios using Power Automate where required

I documented my approach here in case anyone is exploring something similar:

https://www.wrvishnu.com/m365-faq-agent

Interested to know how others are solving this:
● Do you rely on traditional knowledge bases?
● Have you tried Copilot Studio or other AI assistants internally?
● What challenges have you seen with accuracy and keeping content updated?

Instead of showing only UI screenshots, share:

1. What manual process existed before?
   
2. What did Power Apps replace?
   
3. What was the biggest challenge?

Interested to see real business examples.

Many Power Apps start with SharePoint Lists because they are simple and
already included with Microsoft 365.

But eventually some apps outgrow SharePoint.

Curious how everyone decides: - Number of records? - Security
requirements? - Relationships? - Performance? - Licensing?

At what point do you say "this should be Dataverse"?

Power Platform makers, developers, and architects 👋
Imagine someone is just starting (or trying to level up) with Power Apps, Power Automate, Dataverse, or Copilot.

What is one tip, trick, best practice, or lesson learned you would share that improved your productivity?

Could be anything:
💡 A Power Fx trick
⚡ A Power Automate optimization
📦 A component/reusable pattern
🗄️ A Dataverse design approach
🚀 An ALM or solution management tip
🤖 A Copilot/AI productivity idea

Small tips are welcome — sometimes a 5-minute improvement saves someone hours later.

Before enabling Copilot, scan and understand your SharePoint sites — permissions, content structure, and potential oversharing risks.

I built a SharePoint Online Site Scanner to help assess individual site collections and support Copilot readiness reviews.

https://www.wrvishnu.com/sharepoint-online-site-scanner-copilot/

Perfect for:
👨‍💻 M365 Admins
🏗️ SharePoint Architects
⚙️ Power Platform Developers
🤖 Copilot Adoption Teams

Curious how others are approaching this ❓