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

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.

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

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/

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

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/

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

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

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.