Common Integrations (SQL, SharePoint, Gmail, etc.)
Common Integrations in Microsoft Power Platform
Microsoft Power Platform is powerful because it can connect with many different data sources, applications, cloud services, databases, email systems, and APIs. These connections are done through connectors. Common integrations include services such as SQL Server, SharePoint, Gmail, Outlook, Microsoft Teams, Excel Online, OneDrive, Dataverse, and custom APIs.
Microsoft documentation explains that Power Apps has connectors for many popular services and on-premises data sources, including SharePoint, SQL Server, Office 365, Salesforce, and Twitter. It also explains that some connectors provide tables of data, some provide actions, and some provide both. [1](https://learn.microsoft.com/en-us/power-apps/maker/canvas-apps/connections-list)
In simple words, Common Integrations means connecting Power Apps or Power Automate with frequently used business systems so that data can be read, created, updated, deleted, synchronized, or used in workflows.
1. What are Common Integrations?
Common integrations are frequently used connections between Power Platform and other systems. For example, a Power App may connect to SharePoint to store request data, SQL Server to read product information, Gmail to send emails, Teams to post notifications, and Dataverse to store structured business records.
Microsoft describes connectors as a way to connect Microsoft data and automate routine tasks and processes in apps like Excel, Outlook, and SharePoint with Power Automate cloud flow connectors. Microsoft also states that connectors can pull in data from multiple sources to create individual solutions. [2](https://www.microsoft.com/en-us/power-platform/connectors)
| Integration | Purpose | Example |
|---|---|---|
| SQL Server Integration | Connect Power Platform with relational database data. | Read product inventory from SQL Server. |
| SharePoint Integration | Work with lists, libraries, documents, and list items. | Store request records in a SharePoint list. |
| Gmail Integration | Send, receive, or trigger flows from Gmail messages. | Send confirmation email using Gmail connector. |
| Outlook Integration | Automate email and calendar-related work. | Send approval notification through Outlook. |
| Teams Integration | Post messages and collaborate with teams. | Post support ticket alert in Teams channel. |
| Dataverse Integration | Store and manage structured business data. | Create customer record in Dataverse. |
2. Why Common Integrations are Important
Business processes often use multiple systems. For example, customer data may be stored in Dataverse, documents may be stored in SharePoint, notifications may go through Teams, emails may be sent through Outlook or Gmail, and transactional data may live in SQL Server. Integrations allow these systems to work together.
Microsoft states that connectors can take formerly siloed data, on-premises or in the cloud, and combine it to build more robust solutions. Microsoft also states that connectors can consolidate information, revamp legacy functions, and generate new processes by using data from multiple sources with Power Platform products. [2](https://www.microsoft.com/en-us/power-platform/connectors)
| Importance | Explanation | Example |
|---|---|---|
| Reduces Manual Work | Data can move automatically between apps and services. | Form submission creates a SharePoint item and sends email automatically. |
| Improves Accuracy | Automation reduces copy-paste mistakes. | SQL inventory data updates directly in a flow. |
| Connects Systems | Multiple business systems can work together. | Dataverse customer record links with SharePoint documents. |
| Supports Automation | Data changes can trigger workflows. | New Gmail message starts a Power Automate flow. |
| Improves Collaboration | Teams and email integrations keep users informed. | Post alert to Teams when a high-priority ticket is created. |
3. SQL Server Integration
SQL Server is a relational database management system developed by Microsoft. Microsoft documentation states that the SQL Server connector lets users connect to SQL Server to manage data and perform actions such as create, update, get, and delete rows in a table. [3](https://learn.microsoft.com/en-us/connectors/sql/)
Microsoft documentation also shows that the SQL Server connector is available in Power Apps and Power Automate as a Premium connector, while in Logic Apps it is listed as Standard. [3](https://learn.microsoft.com/en-us/connectors/sql/)
| SQL Integration Use Case | Description | Example |
|---|---|---|
| Read SQL Data | Power Apps or flows can retrieve rows from SQL tables. | Show product list from SQL database. |
| Create SQL Row | A flow can insert new data into SQL Server. | Create new order row after form submission. |
| Update SQL Row | A flow can update existing database rows. | Update stock quantity after purchase. |
| Delete SQL Row | A flow can delete database rows if permitted. | Remove temporary staging record. |
SQL Server Integration Example
| Business Scenario | Power Platform Design |
|---|---|
| Inventory data is stored in SQL Server, but users need a Power App to view stock levels. | Use SQL Server connector in Power Apps to display product and inventory rows from SQL Server. |
| When a new order is approved, stock quantity must be reduced. | Use Power Automate with SQL Server action to update inventory quantity. |
4. SharePoint Integration
SharePoint helps organizations share and collaborate with colleagues, partners, and customers. Microsoft documentation states that the SharePoint connector can connect to SharePoint Online or to an on-premises SharePoint 2016 or 2019 farm using the On-Premises Data Gateway to manage documents and list items. [4](https://learn.microsoft.com/en-us/connectors/sharepointonline/)
Microsoft documentation shows that the SharePoint connector is available as a Standard connector in Copilot Studio, Logic Apps, Power Apps, and Power Automate. [4](https://learn.microsoft.com/en-us/connectors/sharepointonline/)
| SharePoint Integration Use Case | Description | Example |
|---|---|---|
| List Data Storage | Use SharePoint lists as a simple data source. | Store employee requests in a SharePoint list. |
| Document Management | Store and manage files in SharePoint libraries. | Upload invoice PDFs to a document library. |
| Approval Automation | Start flows when list items are created or updated. | Start approval when a new request item is created. |
| File Processing | Flows can work with SharePoint files and metadata. | Move document to archive library after approval. |
SharePoint Integration Example
| Business Scenario | Power Platform Design |
|---|---|
| A team needs a simple issue tracking app. | Use Power Apps with SharePoint list as the data source. |
| Users upload supporting documents for each request. | Use SharePoint document library to store uploaded files. |
5. Gmail Integration
Gmail is a web-based email service from Google. Microsoft documentation states that with the Gmail connector, users can perform actions such as send or receive email messages and trigger flows on new emails. [5](https://learn.microsoft.com/en-us/connectors/gmail/)
Microsoft documentation shows that the Gmail connector is available as a Standard connector in Copilot Studio, Logic Apps, Power Apps, and Power Automate, with some listed regional exceptions. [5](https://learn.microsoft.com/en-us/connectors/gmail/)
| Gmail Integration Use Case | Description | Example |
|---|---|---|
| Send Email | Use Gmail connector to send messages. | Send confirmation email after request submission. |
| Receive Email | Use Gmail connector to work with received emails. | Read incoming support emails. |
| Trigger Flow on New Email | Start automation when a new Gmail message arrives. | Create support ticket when customer sends an email. |
| Email-Based Notification | Send automated updates to users. | Notify user when approval is completed. |
Gmail Integration Example
| Business Scenario | Power Platform Design |
|---|---|
| Customer sends issue details to a Gmail mailbox. | Use Gmail trigger to start a flow when a new email arrives. |
| Support ticket should be created from email. | Flow reads Gmail message and creates a ticket record in Dataverse or SharePoint. |
6. Outlook Integration
Outlook integration is commonly used in Power Automate and Power Apps for email notifications, approval messages, calendar actions, and business communication. Microsoft’s Power Platform connector page states that cloud flow connectors can automate routine tasks and processes in apps like Excel, Outlook, and SharePoint. [2](https://www.microsoft.com/en-us/power-platform/connectors)
| Outlook Integration Use Case | Description | Example |
|---|---|---|
| Email Notification | Send email automatically from a flow. | Send leave approval result to employee. |
| Email Trigger | Start flow from incoming email. | Save attachments from incoming invoice emails. |
| Calendar Automation | Use calendar-related automation where connector supports it. | Create meeting after booking approval. |
7. Microsoft Teams Integration
Teams integration is commonly used for collaboration and notifications. Power Platform connector documentation includes Microsoft Teams as one of the connectors available for Power Platform products, and Teams connector documentation describes Teams as enabling users to get content, tools, and conversations in a team workspace with Microsoft 365. [6](https://learn.microsoft.com/en-us/connectors/teams/)
| Teams Integration Use Case | Description | Example |
|---|---|---|
| Post Message | Send automated message to a chat or channel. | Post ticket alert in support channel. |
| Approval Notification | Notify approvers or teams about pending work. | Notify manager when approval is waiting. |
| Team Collaboration | Keep teams updated about business process changes. | Post update when project status changes. |
8. Excel Online Integration
Excel Online integration is commonly used for lightweight data entry, simple tracking, and reporting scenarios. Microsoft’s Power Platform connector page states that connectors can automate routine tasks and processes in apps like Excel, Outlook, and SharePoint. [2](https://www.microsoft.com/en-us/power-platform/connectors)
| Excel Integration Use Case | Description | Example |
|---|---|---|
| Read Table Data | Use Excel table data in apps or flows. | Read training participant list. |
| Update Rows | Write data back to Excel files. | Update attendance tracker. |
| Simple Reporting | Generate or update simple spreadsheet-based reports. | Export daily request summary. |
9. Dataverse Integration
Dataverse is often used as the structured business data platform for Power Apps and Power Automate. Microsoft’s Power Platform connector page states that the Microsoft Dataverse connector can connect to existing data in virtual tables and create custom Dataverse solutions. [2](https://www.microsoft.com/en-us/power-platform/connectors)
| Dataverse Integration Use Case | Description | Example |
|---|---|---|
| Business Data Storage | Store structured business data in Dataverse tables. | Customer, Employee, Case, Leave Request tables. |
| Power Apps Data Source | Build apps using Dataverse tables. | Employee Management App. |
| Flow Automation | Start flows when Dataverse rows change. | Start approval when request row is created. |
| Virtual Tables | Use external data through Dataverse virtual tables. | Show external ERP data in model-driven app. |
10. OneDrive Integration
OneDrive integration is commonly used for file storage and document automation in personal or business contexts. Microsoft’s connector page states that connectors can connect Microsoft data and automate routine tasks in Microsoft services. [2](https://www.microsoft.com/en-us/power-platform/connectors)
| OneDrive Integration Use Case | Description | Example |
|---|---|---|
| Save Files | Store files generated or uploaded by apps and flows. | Save generated PDF to OneDrive. |
| Read Files | Flows can retrieve file content. | Read uploaded Excel file for processing. |
| File Automation | Automate file movement or organization. | Move completed document to archive folder. |
11. API and Custom System Integration
Sometimes a required system is not available as a ready-made connector. In such cases, custom connectors or API-based integration may be used. Microsoft’s connector page states that users can create custom connectors to communicate with more APIs, services, and systems. [2](https://www.microsoft.com/en-us/power-platform/connectors)
| API Integration Use Case | Description | Example |
|---|---|---|
| Internal API | Connect to a company-specific service. | Connect to HR payroll API. |
| Third-Party API | Connect to services not available as prebuilt connectors. | Courier tracking API. |
| Legacy System | Connect Power Platform to older business systems. | Legacy ERP integration. |
12. Common Integration Architecture
A typical integration architecture includes Power Apps for user input, Power Automate for workflow automation, connectors for communication, and external systems for data storage or processing. Microsoft states that connectors help pull in data from multiple sources and combine formerly siloed data to build more robust solutions. [2](https://www.microsoft.com/en-us/power-platform/connectors)
| Architecture Layer | Tool / Service | Purpose |
|---|---|---|
| User Interface | Power Apps | User enters or views business data. |
| Automation | Power Automate | Runs business process and data movement. |
| Connector Layer | SQL, SharePoint, Gmail, Teams, Dataverse connectors | Connects Power Platform with services and data sources. |
| Data Source | SQL Server, SharePoint, Dataverse, Gmail, files | Stores or provides data for the solution. |
| Notification Layer | Outlook, Gmail, Teams | Sends email or chat notifications. |
13. Integration Pattern Examples
| Pattern | Connectors Used | Example Scenario |
|---|---|---|
| Form Submission to Email | Power Apps, SharePoint, Outlook/Gmail | User submits form, record is saved, confirmation email is sent. |
| Email to Ticket | Gmail/Outlook, Dataverse/SharePoint | Incoming email creates support ticket. |
| Database to Notification | SQL Server, Teams | Low stock in SQL triggers Teams alert. |
| Document Approval | SharePoint, Power Automate, Outlook/Teams | New document starts approval workflow. |
| Structured Business App | Dataverse, Power Apps, Power Automate | Employee onboarding app with automated tasks. |
14. Choosing the Right Integration
| Requirement | Recommended Integration | Reason |
|---|---|---|
| Simple list-based tracking | SharePoint | Good for lightweight list and document scenarios. |
| Structured relational business data | Dataverse | Good for tables, relationships, security, and app integration. |
| Existing enterprise database | SQL Server | Good when business data already exists in SQL. |
| Email-based automation | Gmail or Outlook | Good for sending, receiving, or triggering from emails. |
| Team notifications | Microsoft Teams | Good for collaboration and alerts. |
| External custom service | Custom Connector / API | Good when no prebuilt connector exists. |
15. Licensing and Connector Type Considerations
Before selecting an integration, makers should check connector licensing and availability. Microsoft documentation shows that SQL Server is Premium for Power Apps and Power Automate, while SharePoint and Gmail are Standard for Power Apps and Power Automate. [3](https://learn.microsoft.com/en-us/connectors/sql/)[5](https://learn.microsoft.com/en-us/connectors/gmail/)[4](https://learn.microsoft.com/en-us/connectors/sharepointonline/)
| Connector | Power Apps / Power Automate Class in Microsoft Docs | Planning Note |
|---|---|---|
| SQL Server | Premium for Power Apps and Power Automate. | Review premium licensing before using in production. [3](https://learn.microsoft.com/en-us/connectors/sql/) |
| SharePoint | Standard for Power Apps and Power Automate. | Suitable for many Microsoft 365 list and document scenarios. [4](https://learn.microsoft.com/en-us/connectors/sharepointonline/) |
| Gmail | Standard for Power Apps and Power Automate. | Useful for Gmail-based email automation. [5](https://learn.microsoft.com/en-us/connectors/gmail/) |
16. Security Considerations
Integrations should be designed securely because connectors can access business data, emails, documents, and databases. Microsoft states that Power Platform connectors can consolidate data from multiple sources with Power Automate cloud flow connectors backed by Microsoft Entra ID security. [2](https://www.microsoft.com/en-us/power-platform/connectors)
| Security Area | Explanation | Example |
|---|---|---|
| Authentication | Users or service accounts must authenticate to use connectors. | Sign in to Gmail or SQL Server connection. |
| Least Privilege | Connections should only have required access. | Flow account should not have unnecessary delete permission. |
| DLP Policies | Control which connectors can be used together. | Block business data from going to unapproved connectors. |
| Credential Management | Avoid unmanaged personal connections for critical processes. | Use approved connection strategy for production flows. |
17. Best Practices for Common Integrations
| Best Practice | Explanation | Example |
|---|---|---|
| Choose the right data source | Use the integration that matches business complexity. | Use Dataverse for relational business apps, SharePoint for simple lists. |
| Check connector classification | Some connectors are Standard, some are Premium. | SQL Server is Premium for Power Apps and Power Automate. [3](https://learn.microsoft.com/en-us/connectors/sql/) |
| Use proper authentication | Ensure secure and reliable connector access. | Use approved Gmail or SQL connection. |
| Document integrations | Keep records of which connectors are used and why. | Support App uses Gmail, Dataverse, and Teams. |
| Monitor failures | Connector actions may fail due to permission or service issues. | Check failed flow runs and update connections if needed. |
| Apply DLP governance | Protect business data movement between services. | Separate business and non-business connectors. |
18. Common Mistakes in Integrations
| Mistake | Problem | Better Approach |
|---|---|---|
| Using SQL without licensing review | SQL Server is Premium for Power Apps and Power Automate. | Review licensing before design. [3](https://learn.microsoft.com/en-us/connectors/sql/) |
| Using SharePoint for complex relational data | Complex relationships and security may become difficult. | Consider Dataverse for structured business apps. |
| Using personal email connections in critical flows | Flow may fail if user account changes or loses access. | Use approved production connection strategy. |
| No error handling | Failed integration may stop business process. | Add failure handling, logging, and notifications. |
| No documentation | Future maintenance becomes difficult. | Document connectors, data sources, owners, and purpose. |
| Ignoring connector limitations | Apps or flows may behave unexpectedly. | Read connector-specific documentation before production use. |
19. Real-Life Example: Customer Support System
A customer support system may use multiple common integrations together.
| Requirement | Connector | Purpose |
|---|---|---|
| Receive customer email | Gmail or Outlook | Trigger flow when customer email arrives. |
| Create support ticket | Dataverse or SharePoint | Store support ticket record. |
| Attach screenshots | SharePoint or OneDrive | Store uploaded files. |
| Notify support team | Microsoft Teams | Post ticket alert to channel. |
| Check customer data | SQL Server or Dataverse | Retrieve customer account information. |
20. Real-Life Example: Inventory Management System
| Requirement | Connector | Purpose |
|---|---|---|
| Read inventory records | SQL Server | Get product quantity from database. [3](https://learn.microsoft.com/en-us/connectors/sql/) |
| Update stock after order | SQL Server | Update row in inventory table. [3](https://learn.microsoft.com/en-us/connectors/sql/) |
| Send low stock alert | Teams or Outlook | Notify warehouse team. |
| Store stock adjustment files | SharePoint | Manage documents and list items. [4](https://learn.microsoft.com/en-us/connectors/sharepointonline/) |
21. Mini Project: Multi-Connector Request Management System
Project Objective
Create a simple request management system using multiple common connectors.
| Feature | Connector | Purpose |
|---|---|---|
| Request submission form | Power Apps + SharePoint or Dataverse | User submits a new request. |
| Email confirmation | Outlook or Gmail | Send confirmation email to requester. |
| Manager notification | Microsoft Teams | Post request notification in Teams. |
| Document upload | SharePoint or OneDrive | Store supporting documents. |
| Reference data lookup | SQL Server or Dataverse | Retrieve department or product information. |
Learning Outcome
- Students understand how multiple connectors can work together in one business solution.
- Students learn when to use SQL Server, SharePoint, Gmail, Outlook, Teams, and Dataverse.
- Students understand that connector choice affects architecture, licensing, security, and maintainability.
22. Interview Questions and Answers
Q1. What are common integrations in Power Platform?
Common integrations are frequent connections between Power Platform and services such as SQL Server, SharePoint, Gmail, Outlook, Teams, Dataverse, Excel, OneDrive, and APIs. Microsoft documentation states that Power Apps has connectors for popular services and on-premises data sources including SharePoint, SQL Server, Office 365, Salesforce, and Twitter. [1](https://learn.microsoft.com/en-us/power-apps/maker/canvas-apps/connections-list)
Q2. What is SQL Server integration used for?
SQL Server integration is used to connect with relational database data. Microsoft documentation states that the SQL Server connector can manage data and perform actions such as create, update, get, and delete rows in a table. [3](https://learn.microsoft.com/en-us/connectors/sql/)
Q3. What is SharePoint integration used for?
SharePoint integration is used to manage documents and list items. Microsoft documentation states that the SharePoint connector can connect to SharePoint Online or on-premises SharePoint 2016 or 2019 using the On-Premises Data Gateway to manage documents and list items. [4](https://learn.microsoft.com/en-us/connectors/sharepointonline/)
Q4. What is Gmail integration used for?
Gmail integration is used for email automation. Microsoft documentation states that the Gmail connector can perform actions such as send or receive email messages and trigger flows on new emails. [5](https://learn.microsoft.com/en-us/connectors/gmail/)
Q5. Is SQL Server a Standard or Premium connector?
Microsoft documentation lists SQL Server as Premium for Power Apps and Power Automate and Standard for Logic Apps. [3](https://learn.microsoft.com/en-us/connectors/sql/)
Q6. Is SharePoint a Standard or Premium connector?
Microsoft documentation lists SharePoint as Standard for Power Apps and Power Automate. [4](https://learn.microsoft.com/en-us/connectors/sharepointonline/)
Q7. Is Gmail a Standard or Premium connector?
Microsoft documentation lists Gmail as Standard for Power Apps and Power Automate. [5](https://learn.microsoft.com/en-us/connectors/gmail/)
Q8. When should we use SharePoint instead of SQL Server?
As a practical design suggestion, SharePoint is usually suitable for simple list and document scenarios, while SQL Server is more suitable when the solution needs relational database data or existing SQL-based enterprise data. This recommendation is a design guideline, not a direct Microsoft licensing statement.
Q9. Why is security important in integrations?
Security is important because connectors can access business data, emails, documents, and databases. Microsoft states that Power Platform cloud flow connectors can consolidate data from multiple sources backed by Microsoft Entra ID security. [2](https://www.microsoft.com/en-us/power-platform/connectors)
Q10. What is a multi-connector solution?
A multi-connector solution uses more than one connector in the same app or flow. For example, a request system may use SharePoint for storage, Outlook or Gmail for email, Teams for notification, and SQL Server for reference data.
23. Student-Friendly Summary
| Connector | Easy Meaning | Example Use |
|---|---|---|
| SQL Server | Database integration connector. | Read or update inventory rows. [3](https://learn.microsoft.com/en-us/connectors/sql/) |
| SharePoint | List and document integration connector. | Store request list and documents. [4](https://learn.microsoft.com/en-us/connectors/sharepointonline/) |
| Gmail | Email integration connector. | Send or receive emails and trigger flows on new emails. [5](https://learn.microsoft.com/en-us/connectors/gmail/) |
| Outlook | Microsoft email and calendar-related integration. | Send approval emails. |
| Teams | Collaboration and notification connector. | Post alert to a Teams channel. |
| Dataverse | Structured business data platform connector. | Create and manage business records. |
24. Quick Revision Points
- Common integrations connect Power Platform with frequently used services such as SQL Server, SharePoint, Gmail, Outlook, Teams, Dataverse, Excel, OneDrive, and APIs.
- Power Apps has connectors for many popular services and on-premises data sources including SharePoint, SQL Server, Office 365, Salesforce, and Twitter. [1](https://learn.microsoft.com/en-us/power-apps/maker/canvas-apps/connections-list)
- SQL Server connector can perform actions such as create, update, get, and delete rows in a table. [3](https://learn.microsoft.com/en-us/connectors/sql/)
- SharePoint connector can manage documents and list items. [4](https://learn.microsoft.com/en-us/connectors/sharepointonline/)
- Gmail connector can send or receive email messages and trigger flows on new emails. [5](https://learn.microsoft.com/en-us/connectors/gmail/)
- SQL Server is listed as Premium for Power Apps and Power Automate. [3](https://learn.microsoft.com/en-us/connectors/sql/)
- SharePoint and Gmail are listed as Standard for Power Apps and Power Automate. [5](https://learn.microsoft.com/en-us/connectors/gmail/)[4](https://learn.microsoft.com/en-us/connectors/sharepointonline/)
- Connector selection should consider business requirement, licensing, security, performance, governance, and maintainability.
Conclusion
Common integrations are essential for building real-world Microsoft Power Platform solutions. Power Apps and Power Automate can connect with SQL Server, SharePoint, Gmail, Outlook, Teams, Dataverse, Excel, OneDrive, and APIs to create powerful business applications and automated workflows.
SQL Server integration is useful for relational database scenarios and can perform row operations such as create, update, get, and delete. SharePoint integration is useful for document and list item management. Gmail integration is useful for email automation, including sending and receiving email messages and triggering flows on new emails. [3](https://learn.microsoft.com/en-us/connectors/sql/)[5](https://learn.microsoft.com/en-us/connectors/gmail/)[4](https://learn.microsoft.com/en-us/connectors/sharepointonline/)
A good integration design should choose the right connector for the right requirement. SharePoint may be suitable for simple list and document scenarios. Dataverse is useful for structured business applications. SQL Server is useful when the data already exists in relational databases. Gmail and Outlook are useful for email automation. Teams is useful for collaboration and alerts. Custom APIs are useful when no ready-made connector exists.
Before building a production solution, always review connector type, licensing, authentication, security, DLP policies, error handling, monitoring, and documentation. A well-planned integration makes Power Platform solutions more reliable, secure, scalable, and professional.