Power BI connects to Dynamics 365, Salesforce, SAP, Workday, and other external systems using certified connectors or REST APIs. This page covers authentication, refresh modes, schema management, and enterprise security patterns.
Key Facts
- Power BI has certified connectors for Dynamics 365, Salesforce, SAP HANA, SAP BW, Workday, and ServiceNow.
- On-premises data sources (SAP on-premises, Oracle, SQL Server on-premises) require a gateway.
- REST API connections use the Web connector or a custom connector built with Power Query M.
- Model external data in a star schema — avoid pulling full source entity schemas into Power BI.
- Incremental refresh reduces API call volume for high-volume external source integrations.
Power BI Integration With External Data Sources Dynamics 365 CRM ERP HRMS
Power BI Integration: Dynamics 365, CRM, ERP, and HRMS
Power BI connects to Dynamics 365, Salesforce, SAP, Workday, and other external systems using certified connectors or REST APIs. This page covers authentication, refresh modes, schema management, and enterprise security patterns.
Key facts
- Power BI has certified connectors for Dynamics 365, Salesforce, SAP HANA, SAP BW, Workday, and ServiceNow.
- On-premises data sources (SAP on-premises, Oracle, SQL Server on-premises) require a gateway.
- REST API connections use the Web connector or a custom connector built with Power Query M.
- Model external data in a star schema — avoid pulling full source entity schemas into Power BI.
- Incremental refresh reduces API call volume for high-volume external source integrations.
Dynamics 365 Integration
Power BI has a certified Dynamics 365 connector. It exposes all standard and custom D365 entities as tables. Both Import and DirectQuery modes are supported.
For Finance and Operations (D365 F&O), use the OData connector or Azure Data Lake export for large data volumes — the native D365 connector can be slow for tables over 1 million rows.
CRM Integration (Salesforce and Others)
- Salesforce — certified connector in Power BI Desktop. Import mode only.
- HubSpot — REST API via the Web connector. Use a custom connector for large volumes.
- Microsoft Dynamics 365 Sales — use the Dynamics 365 connector (same as above).
- Zoho CRM — REST API or certified connector from AppSource.
ERP Integration (SAP, Oracle, Infor)
- SAP HANA — certified connector. DirectQuery supported for real-time analytics.
- SAP Business Warehouse — certified connector. BEx queries as data source.
- Oracle Database — certified connector. Requires Oracle ODP.NET driver and gateway.
- Infor — REST API via the Web connector or third-party connector.
- Workday — REST API connector. Use incremental refresh for large HR data sets.
Data Modeling for External Sources
When blending CRM, ERP, and HRMS data in one Power BI model, design a star schema explicitly. Avoid using Power Query merges for large tables — define relationships in the model instead.
- Create one fact table per subject area (Sales, Finance, HR).
- Share common dimension tables (Date, Employee, Customer) across fact tables.
- Use incremental refresh to limit data pull from high-volume sources.
- Apply row-level security at the semantic model level — do not rely on source-system permissions.
Frequently Asked Questions
How does Power BI connect to Dynamics 365?
Use the Dynamics 365 certified connector in Power BI Desktop. Authenticate with your Azure AD account. The connector exposes Dynamics 365 entities as tables. Both Import and DirectQuery modes are supported.
Can Power BI connect to SAP?
Yes. Power BI supports SAP HANA, SAP Business Warehouse, and SAP Business Objects via certified connectors. Most SAP connections require an on-premises gateway and SAP driver installation.
How do I connect Power BI to a REST API?
Use the Web connector or OData connector in Power BI Desktop. For authenticated APIs, configure credentials in Power Query. For complex APIs, use a custom connector or Azure Function as a middleware layer.
What is the best way to connect CRM data to Power BI?
Use the certified Dynamics 365 or Salesforce connector for native CRM platforms. For other CRMs, use OData or REST API connectors. Always model CRM data in a star schema — avoid pulling the full entity schema.
How do I handle API rate limits in Power BI?
Schedule refresh during off-peak hours to reduce API call frequency. Use incremental refresh to limit the data range queried per cycle. Cache frequently accessed API data in Azure SQL or Dataverse to avoid hitting rate limits.
Get Expert Help
EPC Group architects have completed 1,500+ Power BI deployments. Call (888) 381-9725 or request a 30-minute discovery call.
Related Resources
Continue exploring power bi insights and services
Why Organizations Choose EPC Group
EPC Group is a Houston-based Microsoft consulting firm with 29 years of enterprise implementation experience and over 10,000 successful deployments across Power BI, Microsoft Fabric, SharePoint, Azure, Microsoft 365, and Copilot. We serve organizations across all industries including Fortune 500, federal agencies, healthcare, financial services, government, manufacturing, energy, education, retail, technology, and global enterprises.
What sets EPC Group apart is our governance-first approach. Every engagement begins with a security and compliance assessment. Our team of senior architects brings hands-on delivery experience across HIPAA, SOC 2, FedRAMP, and CMMC environments. We own outcomes, not hours.
- Fixed-fee accelerators with predictable pricing and defined deliverables
- Senior architect engagement on every project, not rotating juniors
- Compliance-native delivery for regulated industries
- End-to-end coverage from strategy through 24/7 managed services
- 11,000+ enterprise engagements refined into repeatable, risk-controlled patterns
Call (888) 381-9725 or email contact@epcgroup.net for a free assessment.
Power BI Strategy: 2026 Considerations for Power BI Integration With External Data Sources Dynamics 365 CRM ERP Hrms
Direct Lake mode has changed the economics of enterprise Power BI in 2026: instead of importing data into Vertipaq, semantic models now query OneLake-resident Parquet files at near-Import-mode performance without the refresh-window cost. For a Fortune 500 finance organization migrating from a 30-minute Import-mode refresh, the equivalent Direct Lake model typically queries fact data in under 800 ms while removing the entire refresh-orchestration job from Azure Data Factory.
Row-level security (RLS) and object-level security (OLS) in Power BI Premium and Fabric F-SKU capacities are the single most-overlooked compliance control in HIPAA, SOC 2, and FINRA-regulated environments. RLS scoped via service principal authentication (rather than embedded UPN passes) is the only pattern that survives a SOC 2 Type II auditor privilege-walk test. EPC Group includes service-principal RLS as a default in every regulated-industry Power BI engagement.
Decision factors EPC Group evaluates
- Direct Lake mode adoption for Fabric-resident semantic models
- License optimization audit (Pro vs Premium Per User vs F-SKU)
- Row-level security via service principal authentication
- Capacity sizing decision (F2/F4/F64+) tied to peak concurrent users and refresh window
- Copilot grounding quality assessment of semantic-model metadata
For a tailored read on this topic in your specific tenant, contact EPC Group at contact@epcgroup.net or +1 (888) 381-9725. Engagement options at /pricing.