Skip to content

Power Apps

Can Power Apps connect to SQL Server?

By Suresh Girinathuni

Quick answer

Yes. Power Apps connects to SQL Server — on-premises via the on-premises data gateway or Azure SQL directly — for galleries, forms, and Patch against tables and views, plus stored-procedure execution. It suits apps modernizing an existing relational backend without migrating data. Because the SQL connector carries premium-licensing implications and gateway ownership burdens, verify current licensing and assign a gateway owner before committing an enterprise app to it.

Key takeaways

  • SQL connector covers tables, views, and stored procedures.
  • On-prem needs a gateway with an assigned owner.
  • Verify premium licensing; keep heavy logic in the database.

Detailed Explanation

Yes. Power Apps connects to SQL Server — on-premises via the on-premises data gateway or Azure SQL directly — for galleries, forms, and Patch against tables and views, plus stored-procedure execution. It suits apps modernizing an existing relational backend without migrating data. Because the SQL connector carries premium-licensing implications and gateway ownership burdens, verify current licensing and assign a gateway owner before committing an enterprise app to it.

How it works

Install and register the gateway on an always-on machine for on-prem sources, create the connection under a service identity with least-privilege database rights, and bind controls to tables. Delegation to SQL is stronger than to SharePoint but still verify large-query behavior.

Limitations and considerations

Gateway downtime kills on-prem apps; credentials and database permissions need lifecycle ownership. Heavy transactional logic belongs in procedures or APIs, not gallery formulas.

This Q&A page is the short-answer layer for “Can Power Apps connect to SQL Server?” Use the related guides below when you need implementation steps, architecture trade-offs, or troubleshooting detail.

For broader context, visit the Power Apps Code Hub. It connects this topic to surrounding Microsoft 365, Power Platform, SharePoint, Copilot Studio, Dataverse, migration, and Dynamics 365 guidance.

When to use it

Choose SQL when the system of record already lives in SQL Server and must stay there; choose Dataverse when building new governed business data.

Practical example

An order-lookup app reads the existing ERP SQL views through a gateway while new approval metadata lives in Dataverse — no data migration, clear ownership split.

Related Questions

Can Power Apps connect to SharePoint?Yes — SharePoint lists and libraries are first-class Power Apps data sources via the SharePoint connector, ideal for departmental apps. Plan for delegation limits on large lists and graduate to Dataverse when relational needs grow.What is Power Apps?Power Apps is Microsoft’s low-code app platform with three paths: canvas apps for pixel-perfect task screens, model-driven apps generated from Dataverse data models, and Power Apps Code for pro-code React development.Is Dataverse a database?Partly: Dataverse stores data like a database, but it is a business application platform — tables ship with security roles, business logic, APIs, auditing, and Power Platform ALM attached.When should I use Dataverse instead of SharePoint for Power Apps?Choose Dataverse when the app needs table relationships, row-level security, auditing, solution ALM, or Dynamics 365 integration. Stay on SharePoint for simple team tools with flat data and list-level permissions.

Related nextM365 Guides

Power AppsConnect Power Apps Code Apps to Azure SQLLearn how to connect Power Apps Code apps to Azure SQL Database with PAC CLI, secure authentication, queries, stored procedures, and scalable enterprise data patterns.

Sources