Is there any solution to getting question names yet for a form submission in Power Automate?
It's been about 10 years now. Surely there is a solution to dynamically retrieve question names without needing a janky britttle workaround that may or may not work, not just IDs (get form response etc), without having to rely on a hard coded list of questions with answers inserted in against them.
Have OneDrive or SharePoint files/folders on home screen of iPad without internet connection?
This. I'm on a big iOS project. We have several users who need files on an ipad when traveling, and be able to open them when there is no internet connectivity. These files aren't intended to be edited, just 'read only.' These files do not contain any sensitive corporate data. The content lives in SharePoint online and I'm using OneDrive as a bridge to their sharepoint site. BUT the files can only be viewed on the ipad within the OneDrive app without internet access. These are devices using user affinity enrollment. Initially, the solution for users was to use the 'Mark Offline' feature within the OneDrive iOS app. I used Power Automate to have it fetch new files found in OneDrive and move them to the teams SharePoint site. These shared devices are locked down (an understatement). These will be used by the least computer savy/literate people and so having them dive through OneDrive folder after folder, even offline, is a tall order to ask. I totally get it and don't want them doing that either. So now I have to move onto plan B. How can we put the files that live within OneDrive/Sharepoint onto the home screen without an internet connection when the ipad is 'out in the field.?' This would make it infinitely easier for them. The key here is to not have end users manually moving files around. We don't want them to even have to go into OneDrive and mark folders/files offline, if possible. We don't have the SharePoint app on them. I tried the SP app a while back, and it is a hot mess of garbage. I could revisit it. Whatever I can get to work of course we'll have to modify our Intune polices. Thoughts?
Planner Premium in GCCH
Hi all, We are looking to do more with Planner Premium and are frustrated at the lack of tools given to gov clouds to support the conversion of Planner basic plans to Planner Premium. We don't have the magic button to add the premium views like commercial. I then attempted to build a flow to do this based on a basic plan exported to Excel and we don't have the action within Power Automate to interact with Premium plans. It only allows me to select the basic Planners, the Premium ones don't show up in the drop-down to select. Has any one else figured out a way to do this other then manually recreating your tasks from one plan to another?Modernizing Nonprofit Operations with Power Automate
Nonprofits often rely on manual processes because they feel simpler. But manual workflows create bottlenecks, inconsistencies, and unnecessary administrative burden. Power Automate enables nonprofits to automate routine tasks using low‑code logic, connectors, and triggers. How Power Automate Works Power Automate uses: Triggers (e.g., “When a form is submitted”) → Learn more: Triggers in Power Automate [learn.microsoft.com] Actions (e.g., “Send an email,” “Create a SharePoint item”) → See: Create cloud flows and actions [learn.microsoft.com] Connectors (Microsoft 365, Dynamics, Salesforce, Mailchimp, etc.) → Overview: Power Automate connectors [learn.microsoft.com] Logic (conditions, loops, approvals) → Tutorial: Get started with cloud flows [learn.microsoft.com] This allows nonprofits to build workflows without writing code. Workflows Nonprofits Can Deploy Immediately (With Real Triggers) 1. Automated Donor Thank‑You Emails ✅ Trigger: When a row is added (Excel Online – Business) Actions: Send personalized thank-you email (Outlook) Create item (SharePoint) to log donation Post message (Teams) to notify staff 2. Volunteer Application Routing ✅ Trigger: When a new response is submitted (Microsoft Forms) Actions: Get response details Create item (SharePoint list) Condition: route based on program interest Send confirmation email Notify program manager (Teams) 3. Intake Form → SharePoint Database ✅ Trigger: When a new response is submitted (Microsoft Forms) Actions: Get response details Create structured SharePoint record Condition: check urgency level Create follow-up task (Planner) 4. Social Media Scheduling ✅ Trigger: When a file is created (properties only) (SharePoint) Actions: Retrieve file metadata Post content via connector Notify communications team 5. Event Registration Automation ✅ Trigger: When a new response is submitted (Microsoft Forms) Actions: Send confirmation email Create Outlook calendar event Create SharePoint attendance record 6. Document Approval Workflows ✅ Trigger: When a file is created (properties only) (SharePoint) Actions: Start and wait for approval Update file status Notify stakeholders Technical Best Practices Use environment variables for URLs and credentials Store data in SharePoint lists for scalability Use error handling and retry policies Document workflows for continuity Apply DLP policies to protect sensitive data Final Thought Power Automate gives nonprofits the ability to scale operations without scaling staff. Every workflow starts with a real trigger tied to a business event, ensuring automation runs instantly and reliably. By standardizing processes and reducing manual intervention, organizations can improve data accuracy, accelerate response times, and create more consistent experiences for donors, volunteers, and program participants. Automation also enhances visibility across teams, making it easier to track activities, measure impact, and make informed decisions. Most importantly, Power Automate frees staff from repetitive administrative tasks, allowing them to focus on higher‑value work—building relationships, delivering services, and advancing the organization’s mission. In a resource‑constrained environment, this shift is not just efficient—it is transformative.Microsoft Power Platform community call - June 2026
💡 Power Platform monthly community call focuses on different extensibility options for builders, makers and developers within the Power Platform. Typically demos are from our awesome community members who showcase the art of possible within the Power Platform capabilities. 👏 Looking to catch up on the latest news and updates, including cool community demos, this call is for you! 📅 On 17th of June we'll have following agenda: Power Platform Updates & Events Latest on Power Platform samples Elliot Margot (Witivio) - Process Mining + Copilot Studio: Stop Reading Dashboards, Start Asking Questions Sailaja Mantripragada (Low Code Power) - From Prompt to a Filled-In Word Template: Automating Deep Customer Research with Copilot Studio and Agent Flows John Liu (Rapid Circle) - Using Copilot Cowork with MCP to build Power Automate flows 📅 Download recurrent invite from https://aka.ms/powerplatformcommunitycall 📞 & 📺 Join the Microsoft Teams meeting live at https://aka.ms/PowerPlatformMonthlyCall 💡 Building something cool for Microsoft 365 or Power Platform (Copilot, SharePoint, Power Apps, etc)? We are always looking for presenters - Volunteer for a community call demo at https://aka.ms/community/request/demo 👋 See you in the call! 📖 Resources: Previous community call recordings and demos from the Microsoft 365 & Power Platform community YouTube channel at https://aka.ms/community/videos Microsoft 365 & Power Platform samples from Microsoft and community - https://aka.ms/community/samples Microsoft 365 & Power Platform community details - https://aka.ms/community/homeIs Power Automate Becoming the New Technical Debt in Dynamics 365 Projects?
Power Automate has transformed how organisations build automation within Dynamics 365 and the Power Platform. Teams can automate processes quickly, reduce manual effort, and deliver business value without extensive custom development. At the same time, I have noticed an interesting challenge in some organizations as Power Platform adoption matures. Over time, hundreds of flows can be created by different teams, often with varying levels of governance, documentation, and ownership. Business logic may become distributed across multiple automations, making troubleshooting, maintenance, and long-term support more complex. On the other hand, many organisations have successfully scaled Power Automate by implementing strong governance practices and automation standards. I'm interested in hearing different perspectives from the community. Have you seen Power Automate become difficult to manage at scale, or has it reduced technical debt in your organization? What governance, architecture, or operational practices have worked best for balancing innovation with maintainability?Build an AI Resume Screening Multi-Agent
Hello everyone 👋 I recently built an AI-powered resume screening multi-agent that automates the hiring intake and candidate evaluation process. The solution automatically: Accepts resume uploads Stores resumes in SharePoint Evaluates candidates using AI Matches resumes against job requirements Generates recruiter-ready summaries Sends automated recruiter notifications Technologies Used: • Power Automate • AI Builder • SharePoint • Outlook • GPT-Based Prompting This is Part 1 of my AI Hiring Multi-Agent Series. I’d love to hear feedback from the community and learn how others are approaching AI-powered recruitment workflows. Newsletter: https://www.linkedin.com/pulse/build-ai-resume-screening-multi-agent-sajeda-sultana-k1ege/?trackingId=TQzoIUy0RveiwXLIgEKvSQ%3D%3D If you find it helpful, please share it with others who may benefit from it as well.Stop Writing Promotional Emails. Build an AI Agent That Does It For You.
Hi everyone 👋 A few weeks ago, I started thinking about how much time businesses still spend writing repetitive promotional emails manually every month. The process is usually the same: review customer purchase history check active discounts write personalized emails send them one by one So I decided to build a simple AI-powered workflow that could automate the entire process. For Edition #003 of my newsletter, I created an AI agent that: ✅ reads customer purchase data ✅ matches category-based discounts ✅ generates personalized promotional emails using AI ✅ sends emails automatically What I enjoyed most while building this project was seeing how even small personalization details can completely change the customer experience. Instead of sending generic promotions, the workflow creates emails tailored to each customer’s purchases and interests. In this edition, I shared: the real-world use case the complete workflow approach implementation screenshots sample datasets GitHub project files practical automation tips 📌 View the newsletter If you enjoy building practical AI automations or exploring real-world AI agent ideas, I think you’ll enjoy this edition. I’d genuinely love to hear your thoughts and learn how others are approaching AI-driven automation in their own projects 🙌Feature Request – Read-only and Locked Fields for Pre-filled Microsoft Forms
Microsoft Forms has recently introduced support for pre-filled responses, which is a very valuable addition. However, the lack of read-only fields significantly limits its usability in real-world and enterprise application scenarios. In many workflows, especially those involving bots, kiosks, or guided user interactions, some fields must be pre-populated with system-generated data such as user identity, email, or contextual information. These fields need to remain visible to the user for transparency, but must not be editable in order to guarantee data integrity and prevent tampering. Currently, there is no reliable way to enforce this behavior. Even when using pre-filled URLs, users can still modify the values before submission. This creates a risk of data inconsistency and makes it difficult to maintain a secure and synchronized interaction between the client and backend systems. This is not just a UX limitation, but also a data integrity issue in integrated workflows. As a result, developers are forced to implement server-side validation and ignore user-provided values for critical fields, which defeats the purpose of pre-filling them in the first place. This forces developers to rely entirely on server-side validation, reducing the effectiveness of pre-filled data and introducing unnecessary complexity. While Power Apps can address this limitation, it is often too complex and heavy for simple scenarios where Microsoft Forms would otherwise be perfectly adequate. Suggested improvement: - Allow form fields to be marked as read-only or locked - Optionally support hidden or system fields - Allow pre-filled values to be protected against tampering - Preserve compatibility with pre-filled URLs This feature would enable Microsoft Forms to be used in secure, system-driven workflows without requiring migration to more complex platforms.
