Microsoft Power Platform (Power Apps, Power Automate, Power BI, Power Pages and Copilot Studio) is the central low-code platform in Microsoft 365 in 2026. Swiss enterprises use it to build business apps, workflow automations and AI agents – fast, without a developer team, and integrated with SharePoint, Teams and Dataverse. Without clear best practices, however, the platform turns into chaos. This guide shows the CNEXT approach for sustainable Power Platform projects.
Power Platform components
| Component | Purpose | Typical use |
|---|---|---|
| Power Apps Canvas | Custom business UIs | Mobile inspection apps, approvals, dashboards |
| Power Apps Model-driven | Data-heavy CRUD apps on Dataverse | Asset management, service desk, pipeline |
| Power Automate Cloud | Workflow automation | Approvals, notifications, integrations |
| Power Automate Desktop | RPA for legacy apps | Automating web/desktop UIs |
| Power BI | Reports and dashboards | Finance and operations reporting |
| Power Pages | External portals | Customer and supplier portals |
| Copilot Studio | AI agents | HR bot, IT helpdesk, contract analysis |
Environment strategy
The most common mistake in Swiss Power Platform projects is the lack of an environment strategy. CNEXT's standard recommendation:
- Default environment – personal productivity only (makers should not build business-critical content here)
- DEV / TEST / PROD environments per business unit
- Sandbox environment for citizen developers / training use cases
- Dataverse for Teams environments auto-created per team – restrict via policy
Data residency: choose Switzerland region for all production environments to ensure FADP compliance.
ALM (Application Lifecycle Management)
Swiss enterprises with productive Power Apps need ALM:
- 1Use solutions – never build in the default environment
- 2Source control – commit unpacked solution ZIPs to Git
- 3Pipelines – Power Platform Pipelines (or Azure DevOps / GitHub Actions) for DEV → TEST → PROD
- 4Connection references and environment variables for environment-specific config
- 5Service principal for CI/CD instead of personal user accounts
Power Apps best practices
Performance
- Respect delegation – filtering and sorting server-side (SharePoint, Dataverse, SQL)
- Use lazy loading instead of loading full lists
- Minimise OnStart code; replace with named formulas
- Optimise images (max 100 KB per asset)
UX
- Use modern controls (Fluent UI 2026)
- Theming via named formulas and global variables
- Responsive layout with container and layout components
- Accessibility (ARIA labels, tab order, contrast)
Security
- Never store secrets in app variables or OnStart
- Sensitive data in Dataverse with field-level security
- SharePoint lists with item-level permissions
- Audit logs via Power Platform Admin Center or Microsoft Purview
Power Automate best practices
- Solutions instead of "my flows"
- Try-catch-finally pattern for error handling
- Service principal connections instead of personal accounts (no single point of failure on leavers)
- Performance: avoid apply-to-each loops, use batch operations
- Telemetry to Application Insights
Citizen development programme
Swiss enterprises benefit from citizen developers (business teams building their own apps) – but only with governance:
- 1Maker training (CNEXT delivers 2-day workshops in DE/EN/FR)
- 2Champions programme (1 champion per department)
- 3Solution catalog – reusable components and templates
- 4Review process before go-live (performance, security, governance)
- 5Center of Excellence (CoE) Toolkit for inventory of all apps and flows
Governance with the CoE Toolkit
Microsoft offers the free Center of Excellence Starter Kit. It provides:
- Inventory of apps, flows and makers
- Compliance and risk reports
- Auto-cleanup for inactive apps
- DLP policy reports
- Adoption dashboards
CNEXT deploys the CoE Toolkit for Swiss customers and runs it as a managed service.
Swiss best practices
- Languages – apps in DE/FR/IT/EN via localisation (resource files)
- Connectors – use Bexio, Abacus and Swisscom connectors instead of custom REST calls
- Data residency – Switzerland region, EU Data Boundary for connectors
- Compliance – Power Platform audit logs in Microsoft Purview
Integration with Copilot Studio
Power Platform is the foundation for Microsoft Copilot Studio agents:
- Agents trigger Power Automate flows
- Agents read from Dataverse / SharePoint
- Agents write to Bexio, Abacus, SAP via connectors
See our Microsoft 365 Copilot rollout guide for the end-user side.
FAQ
Which licence is right for a Swiss SMB? Power Apps is included in M365 (for standard / SharePoint connectors). Premium connectors (SQL, Bexio, Abacus, REST APIs) require Power Apps Premium (~CHF 20 / user / month) or pay-as-you-go.
Do we need Dataverse or is SharePoint enough? For simple lists (<2,000 items, few relations) SharePoint is fine. For relational models, field-level security or large data volumes use Dataverse.
How do we prevent sprawl? With DLP policies, default-environment restrictions, the CoE Toolkit and a pre-go-live review process.
What does a Power Platform setup with CNEXT cost? Discovery + governance setup from CHF 12,000. A first productive app typically CHF 20,000–60,000 depending on complexity.
Conclusion
Power Platform is the most important low-code platform for Swiss enterprises in 2026 – but only with a clear strategy, environment separation, ALM and governance. CNEXT, a Microsoft Solutions Partner, guides Swiss companies from CoE setup to productive solution.