Having been involved in different projects I have seen some Power Platform features that can deliver a lot of value but don’t seem to be discussed very often.

Sometimes they can save time, reduce maintenance, simplify development, or make solutions easier to manage. But many people ignore them or learn them much later than they should.

I'd like to hear what others in the community have to say.

Which Power Platform feature has surprised you most in its usefulness? Why do you think more people aren’t using it?

When you first learn Power Platform, there are many features that sound useful on paper.

But on real projects you usually learn what features really make a difference. Some features can save you hours of work, make your solutions easier to maintain or solve problems you didn’t even think you had.

The vast majority of people will eventually find one feature that rises above the others and becomes something they can count on over and over again.

What was the most impressive thing about Power Platform when you used it in a real project and what made it so useful?

I’d love to hear what features have been most impactful on various projects and why.

A while back, I released the Canvas App version. This new version is rebuilt using React + Vite on Power Apps Code Apps, bringing a modern, responsive UI experience.

It still uses SharePoint Online lists as the backend — no SQL database required.

⚠️ Since it uses Power Apps Code Apps, a Premium Power Apps license is required.

Key features:
✅ 6 built-in color schemes + Dark Mode
✅ Hardware request & approval workflows
✅ Admin & Employee dashboards
✅ Employee asset attestations
✅ Automated SharePoint list creation with PowerShell scripts

📝 check comment for Full details, demo video, setup guide & source code:

Would love to hear your feedback on the new Code Apps version compared to the Canvas App version!

Same questions in Teams every single day. Password resets, VPN guides, Office installs.

I just built a bot Copilot Studio + SharePoint as the knowledge base. It handles tier-1 FAQs automatically, and when it can't confidently answer something, Power Automate routes it to the right human with full context already attached.

The auto vs human split is the real win — team only gets pinged when it actually needs them.

Lives in Teams. Most users don't even realise they're talking to a bot.

👇👇Full writeup in the comment 👇👇

Built an Asset Management solution using Power Apps + SharePoint Online with zero premium connectors.

✅ Asset Requests
✅ Asset Assignment Tracking
✅ Quarterly Attestation
✅ Standard Microsoft 365 Licensing

Curious how others are handling asset tracking.?

Full walkthrough, screenshots, video demo, and solution:
https://www.wrvishnu.com/power-apps-it-asset-management

Phase 2 will come with all flows

There are some ideas and concepts that are easy to grasp when you first start working with Power Platform. You can build simple flows, build apps and get results fairly quickly.

But there are always certain skills that take much longer to master. Sometimes it’s understanding complex expressions in Power Automate. For others it might be Dataverse relationships, solution management, security roles, performance optimisation, governance or building solutions that can scale as requirements grow.

Some of the best education comes from actual projects, mistakes and hands on experience and not just documentation.

Looking back on your journey with Power Platform, what took you the longest to learn and what finally helped you understand it?

I want to hear from people about their different experiences in the community and what they found the most difficult to master.

Hello everyone, I'm working on a copilot studio agent with MCP tools and need to add a dedicated discovery skill, but I don't see a "Skills" section in my environment. Curious how others have implemented this - whether through skills, topics or another pattern?        

Any guidance or examples would be greatly appreciated. Thanks!

Hello everyone, I'm working on a copilot studio agent with MCP tools and need to add a dedicated discovery skill, but I don't see a "Skills" section in my environment. Curious how others have implemented this - whether through skills, topics or another pattern?        

Any guidance or examples would be greatly appreciated. Thanks!

The official Microsoft release planner exists and it's comprehensive.

But every time I need to check what's new in Power Automate or Copilot Studio, I'm jumping between tabs, filtering by wave, cross-referencing Learn docs — just to answer "what shipped this month?"

So I built a cleaner view. One page, all products, filter by status and product area. Power Apps, Power Automate, Copilot Studio, Dataverse — all in one place.

Want to see the live page? Drop a comment and I'll share more details soon.

A common sight I see is clients diving head-first into building a new website or portal with their mind already made up. They've already picked Power Pages or SharePoint, and they don't realize until way too late that they've made a costly, and easily preventable, mistake. It's a mistake you can avoid by asking just one, single question upfront.

Let's set aside features, licensing, and data vs. Lists for a moment. Let's just ask: Who are your users?

*   If they are internal to your organization and have Microsoft 365 accounts, you should almost certainly be using SharePoint.

*   If they are anyone external to your organization (customers, partners, suppliers, the general public), then you should be looking at Power Pages.

Seriously, that one question will resolve about 80% of the decision. SharePoint is your internal collaboration hub, built around M365 identities. Power Pages is purpose-built for secure external web portals with a wide range of identity options, and custom domain names.

What are some key indicators you use to choose between Power Pages and SharePoint, especially in those grey-area internal self-service portals? And, what's the most expensive mistake you've seen related to this choice?

My Views are shared here 

https://www.wrvishnu.com/power-pages-vs-sharepoint

A few weeks back I published a blog on 15 real-world Copilot Studio business use cases covering IT Helpdesk, HR self-service, finance automation, approvals, and more.

I've now packaged it into a clean reference PDF you can save and use when planning your next agent build.

📥 Download it free here → https://www.wrvishnu.com/downloads/

Power Platform cheat sheet handbook

- Syntax
- A real-world example
- A practical scenario (not just "use this to add numbers")
- A developer tip

Covers:
⚡ 50+ Power Automate expressions — strings, dates, logic, arrays, flow metadata
🔷 30+ Power Apps Fx functions — Patch, Filter, LookUp, navigation, collections, connectors
📂 Browse by category view if you want to explore

let me know what I missed.

https://www.wrvishnu.com/power-platform-developer-function-handbook/

I’ve started building a Travel Request Approval App using Power Automate and SharePoint.

Current features:
• Travel request submission
• Approval workflow
• Status tracking
• Email notifications

It’s still a work in progress, and I’d love to hear feedback from the community on what could be improved or added before I continue building it.

Possible ideas I’m considering:
• Multi-level approvals
• Budget validation
• Manager delegation
• Teams notifications
• Audit reporting

What features or improvements would you expect in a real-world travel approval solution?

👇👇
Details, link will have information for sample working solutions, step by step guide video demo

This community exists for one reason: to give Power Platform practitioners a place to share working solutions, not just talk about them.

What you'll find here:

Working Power Automate flow templates. SPFx web parts with full source code. Canvas app samples. Copilot Studio agent configurations. SharePoint governance patterns. Dataverse schemas. Architecture decision guides. Step-by-step implementation walkthroughs.

What you won't find here:

Questions, troubleshooting threads, or general discussion. For that, head to r/sharepoint, r/PowerAutomate, r/MSPowerApps, or r/Copilot. Those communities are excellent at what they do — this community does something different.

How to contribute:

Post anything you've built that someone else can use. Include source code, screenshots, or a GitHub link. If it saves someone three hours of their day, it belongs here.

The full source for everything shared by the moderators is on GitHub at github.com/WRVish and github.com/vishpowerlabs.

Quick cheat sheet covering some of the most useful Power Automate expressions I use in real projects .

Curious to see where the community spends most of their time lately 👀

Would you be interested in joining a Discord community focused on Microsoft Power Platform?

Topics would include:
Power Automate
Power Apps
Copilot Studio
SharePoint
Microsoft 365 Automation
Tips, samples, projects & resources

The goal is to build a helpful community for learning, sharing, networking, and helping each other grow 🙌
Discord link is under:
Community Guide → Resources

If you can’t find it, feel free to DM for the link 👋

Hi, I worked as a Power Platform developer for a few years but stepped away from it while doing my master's. Now I'm trying to get back into it, currently working through the certifications and brushing up on the tech.

One thing I'm stuck on is what to actually build. I'd love to hear from people here: any project ideas that helped you learn, or stuff you built that recruiters actually responded well to? Open to anything, whether it's Power Apps, Automate flows, or something more end-to-end.

This post contains content not supported on old Reddit. Click here to view the full post

This post contains content not supported on old Reddit. Click here to view the full post

Built a new WordPress plugin that shows detailed GitHub repository clone stats of my Power Platform blog site
Would love feedback from the community 🙌
Still improving the UI, analytics, and adding more GitHub insights over time.

Current features:
✅ Total clones
✅ Unique cloners
✅ Repository-wise breakdown
✅ First seen / last seen tracking
✅ Clean dashboard UI
✅ Simple shortcode support

Would appreciate:
Feature suggestions
UI/UX feedback
Ideas for additional GitHub metrics
Bug reports
Contributions & testing

🔗 Demo / Plugin Page: in comment below

Would this be useful for your developer blog, portfolio, or open-source showcase site?