Salesforce + Microsoft Power BI Integration — CRM Reporting Automation
Salesforce + Microsoft Power BI Integration connects Salesforce to Microsoft Power BI so sales teams, revenue operations, marketing leaders, and executives can analyze CRM performance without manual Salesforce exports. IT Partner builds on Power BI's built-in Salesforce connectors — Salesforce Objects and Salesforce Reports — authenticating with OAuth against your org's API, models the data on an import-and-scheduled-refresh basis, builds interactive dashboards, and applies row-level security mapped to Microsoft Entra ID groups. Salesforce API limits shape the refresh design and are reviewed during scoping.
What this engagement is
This service connects Salesforce to Microsoft Power BI to automate sales and marketing reporting. Instead of static Salesforce reports or manual exports, teams analyze pipeline health, win rates, customer segmentation, leads, campaigns, opportunities, accounts, and activities in interactive Power BI dashboards. The integration uses the connectors Microsoft ships in Power BI for exactly this purpose: the Salesforce Objects connector for object-level extraction — Leads, Opportunities, Campaigns, Accounts, custom objects — and the Salesforce Reports connector where existing Salesforce reports are the right source. Authentication is OAuth against the org's API, and the reporting model is import with scheduled refresh — the standard, supported pattern for Salesforce data in Power BI; DirectQuery is not the norm for these connectors, and refresh design must respect Salesforce API limits, which vary by edition and licensing. IT Partner models the extracted data with relationships and DAX measures, builds the agreed dashboards with drill-through and cross-filtering, configures row-level security mapped to Microsoft Entra ID groups, sets up scheduled refresh, and validates report totals against Salesforce before handoff. Where genuinely low-latency dashboards are required, alternative architectures — such as push datasets fed by an automation layer — can be designed as a separately scoped option.
Success criteria
What you receive
How the work unfolds
Confirm business objectives, target audiences, Salesforce objects, key fields, dashboard requirements, refresh expectations, licensing, security requirements, and acceptance criteria. Dependency: client provides stakeholder availability, Salesforce reporting context, and access details needed for scoping.
Validate Salesforce API access, the OAuth/connected app approach, Power BI workspace access, required Microsoft Entra ID groups, gateway requirements if applicable, and any network or tenant constraints. Acceptance gate: required access is available and the agreed connection approach is approved.
Connect Power BI to Salesforce with the built-in Salesforce Objects and/or Salesforce Reports connectors using OAuth, and extract the agreed objects and fields.
Shape the extracted data in Power Query, build the semantic model with relationships across the agreed objects, and implement calculated columns and DAX measures.
Build the agreed interactive Power BI reports and dashboards with drill-through and cross-filtering.
Configure scheduled refresh within the org's Salesforce API limits and the client's Power BI licensing, and configure row-level security roles mapped to Microsoft Entra ID groups. Where a separately scoped near-real-time requirement exists, implement the agreed push-dataset architecture.
Validate refresh behavior, sample Salesforce-to-Power BI record alignment, key KPI calculations, dashboard usability, and row-level security behavior with nominated client testers. Acceptance gate: client confirms the scoped dashboards and measures are ready for production use or provides remediation feedback.
Publish the Power BI content in the agreed workspace, confirm ownership and access, provide handoff guidance, and conduct user and admin orientation for the delivered dashboards and refresh process.
Prerequisites
Who does what
IT Partner
- Lead discovery workshops and document the approved dashboard, data, refresh, and security scope.
- Connect Power BI to Salesforce through the built-in Salesforce connectors with OAuth authentication.
- Recommend a conservative connection and refresh design that accounts for Salesforce API limits, Power BI licensing, data volume, and security requirements.
- Extract and model the agreed Salesforce objects: Power Query shaping, relationships, calculated columns, and DAX measures.
- Build the agreed interactive reports and dashboards with drill-through and cross-filtering.
- Configure Power BI row-level security roles and map them to Microsoft Entra ID groups where included in scope.
- Configure scheduled refresh — and any separately scoped near-real-time architecture — within platform and licensing constraints.
- Support validation, issue remediation for scoped deliverables, and production handoff documentation, including user and admin orientation.
Your team
- Provide Salesforce API access, appropriate Salesforce permissions, and approval for OAuth/connected app configuration as required.
- Provide Power BI licensing, workspace access, gateway administrator support if required, and Microsoft Entra ID groups or users for access control.
- Identify business owners for sales, marketing, revenue operations, and executive reporting requirements.
- Provide definitions for KPIs, field meanings, pipeline stages, campaign attribution logic, and any approved reference reports used for validation.
- Confirm which Salesforce standard and custom objects, fields, date ranges, and filters are in scope.
- Provide access to any campaign spend or non-Salesforce data sources if those sources are added to the approved scope.
- Participate in UAT, validate report outputs against Salesforce, provide timely feedback, and approve go-live readiness.
- Own ongoing Salesforce data quality, source-system governance, user access approvals, and post-handoff operational ownership unless a separate managed service is contracted.
What's not included
Limitations & technical notes
Frequently asked questions
What is the Salesforce + Microsoft Power BI Integration service?
IT Partner connects Salesforce to Microsoft Power BI so teams can analyze CRM performance in interactive dashboards without manual exports. The implementation uses Power BI's built-in Salesforce connectors, models the data with relationships and DAX measures, builds the agreed dashboards, applies row-level security, and configures scheduled refresh within your Salesforce API limits.
How does Power BI connect to Salesforce?
Through the connectors Microsoft ships in Power BI for this purpose: the Salesforce Objects connector for object-level data — Leads, Opportunities, Campaigns, Accounts, custom objects — and the Salesforce Reports connector where existing Salesforce reports are the right source. Authentication is OAuth against your org's API; no third-party middleware is required for the standard reporting pattern.
Is the integration real-time?
The standard, supported pattern is import with scheduled refresh — dashboards are as fresh as the last refresh, designed around your Salesforce API limits and Power BI licensing. DirectQuery is not the norm for the Salesforce connectors. Where a genuinely low-latency dashboard is required, a separately scoped architecture — such as push datasets fed by an automation layer — can be designed.
Does Power BI write data back to Salesforce?
No. The integration is read-only: Power BI extracts, models, refreshes, and visualizes Salesforce data. Write-back from Power BI to Salesforce is explicitly not included in this service.
Which Salesforce data can be included?
The agreed standard and custom objects — commonly Leads, Opportunities, Campaigns, Accounts, and activities — with relationships modeled across objects so users analyze connected CRM data rather than isolated extracts. The exact objects, fields, and date ranges are confirmed during scoping.
What about Salesforce API limits?
Salesforce API limits vary by edition and licensing, and they are a real design constraint for refresh frequency and extract size. IT Partner reviews your org's available API capacity during scoping and designs a conservative refresh schedule that stays inside it, validating refresh behavior before handoff.
How is sensitive CRM data secured in Power BI?
The connection authenticates with OAuth against the Salesforce API, and report access is controlled in Power BI: row-level security roles mapped to Microsoft Entra ID users or groups restrict what each audience sees. Note that Power BI security is a separate layer from Salesforce sharing rules — the RLS design is agreed and tested during the engagement.
What Power BI licenses do we need?
Power BI Pro at minimum for shared workspaces and scheduled refresh; Premium capacity or Premium Per User where model size, refresh frequency, or advanced requirements demand it. The right level is validated during scoping based on data volume and requirements.
Can the dashboards cover sales KPIs and marketing alignment?
Yes. Typical scope includes pipeline health, win rates, stage aging, and customer segmentation for sales, and lead and campaign dashboards for marketing-sales alignment. Custom DAX measures — for example customer lifetime value — are built where scoped, and KPI definitions come from your business owners.
How long does the integration take, and how is it priced?
The service is billed hourly at the published rate, with total effort scoped per project. A standard engagement is planned at five days; the final timeline depends on the number of objects, model complexity, dashboard requirements, and security rules.
What is not included?
Write-back to Salesforce, Salesforce configuration or data cleanup, non-Salesforce data source integration, Microsoft Fabric or data warehouse builds, custom AI/ML development, and all licensing costs are excluded unless separately scoped. Ongoing report enhancement and managed analytics support after handoff are available as separate services.
What happens after the implementation is completed?
You receive the published dashboards, the semantic model, refresh configuration, RLS roles, and administrator handoff documentation, plus user and admin orientation. Ongoing dashboard changes, monitoring, and additional data sources are handled as separate engagements or a support agreement.