Create Your First Power Apps Code App with PAC CLI
A practical first-app walkthrough for Power Apps Code: create the Vite React starter, authenticate PAC CLI, initialize the code app, run it locally, build it, and publish it to Power Apps.
This archive collects nextM365 articles about the Power Platform ecosystem, including Power Apps, Power Automate, Copilot Studio, connectors, governance, and low-code or pro-code solution design. It is an article collection, not a replacement for the focused learning hubs.
Open the Power Platform learning hubUse this page when you want to browse Power Platform content across product boundaries. For deeper learning, follow the dedicated Power Automate, Power Apps Code, and Copilot Studio hub pages linked from related articles.
This article archive collects the concepts, setup steps, design choices, and common implementation patterns behind Power Platform. Use them as practical references while planning, building, testing, and improving Microsoft 365 solutions.
109 articles in “Power Platform”
A practical first-app walkthrough for Power Apps Code: create the Vite React starter, authenticate PAC CLI, initialize the code app, run it locally, build it, and publish it to Power Apps.
Day 12 of the 365 Days of Microsoft Copilot Studio series explains variables and entities: what they are, how they work together, common examples, a real-world HR leave request scenario, best practices, and key takeaways.
A hands-on guide to connecting a Power Apps Code app to Microsoft Dataverse with the PAC CLI: prerequisites, authenticating your environment, adding a Dataverse table as a data source, the auto-generated service and model files, and full create, read, update, and delete examples.
Day 11 of the 365 Days of Microsoft Copilot Studio series explains knowledge sources: what they are, the supported sources, how knowledge works, choosing the right source, best practices, common mistakes, a real-world HR example, and key takeaways.
A folder-by-folder, file-by-file tour of a Power Apps Code (React + Vite + TypeScript) project scaffolded by the PAC CLI. What .power, node_modules, public, src and generated are for, what App.tsx, main.tsx, package.json and power.config.json do, and which files to leave alone.
A plain-English introduction to Microsoft Power Fx — the Excel-like, low-code language behind Power Apps and the wider Power Platform. What it is, why it "thinks spreadsheet", how declarative formulas auto-recalculate, the no-code to pro-code spectrum, its design principles, and where you use it.
Day 10 of the 365 Days of Microsoft Copilot Studio series explains what topics are, why they matter, how they process a conversation, system and custom topics, common node types, best practices, and mistakes to avoid.
Week 2 of the 365 Days series: meet the core components that power every Copilot Studio agent — Topics, Knowledge, Generative AI, Actions, Variables and Entities — plus the production-ready areas like Instructions, Tools, Evaluation, Analytics, Channels and Test Canvas.
A complete developer guide to connecting Power Apps Code apps to any data source: Dataverse, Azure SQL, SharePoint, Copilot Studio agents, table metadata and REST APIs. See how to add each data source with PAC CLI, what each supports, how to choose the right one, and Microsoft best practices.
It groups articles that discuss Power Apps, Power Automate, Copilot Studio, connectors, and governance across the Power Platform.
No. This is an article archive. Use the product pillar pages for structured learning paths.