LLMpediaThe first transparent, open encyclopedia generated by LLMs

Power Query

Generated by GPT-5-mini
Note: This article was automatically generated by a large language model (LLM) from purely parametric knowledge (no retrieval). It may contain inaccuracies or hallucinations. This encyclopedia is part of a research project currently under review.
Article Genealogy
Parent: Microsoft Power BI Hop 5
Expansion Funnel Raw 110 → Dedup 0 → NER 0 → Enqueued 0
1. Extracted110
2. After dedup0 (None)
3. After NER0 ()
4. Enqueued0 ()
Power Query
Power Query
Unknown authorUnknown author · CC BY 4.0 · source
NamePower Query
DeveloperMicrosoft
Released2010s
Written inM (Power Query Formula Language), C#
Operating systemMicrosoft Windows, macOS (Excel), web
LicenseProprietary commercial software

Power Query is a data connection and transformation tool developed by Microsoft for extracting, transforming, and loading data from a wide range of sources into analytical and reporting environments. It provides a graphical interface and a functional formula language for data shaping, enabling users across organizations such as Microsoft Corporation, Accenture, Deloitte, PwC, KPMG to prepare data for business intelligence and analytics platforms including Microsoft Excel, Microsoft Power BI, Azure Synapse Analytics, Snowflake, Databricks. Power Query supports connectors to enterprise systems like Salesforce, SAP, Oracle Corporation, IBM, ServiceNow and public data sources hosted by Amazon Web Services, Google Cloud Platform, GitHub.

Overview

Power Query is positioned as an extract, transform, load (ETL) experience embedded in client and cloud products from Microsoft Corporation to reduce reliance on specialist tools such as Informatica, Talend, Alteryx, SSIS. It blends a user interface inspired by spreadsheet paradigms used in Microsoft Excel with a functional language called M, enabling advanced users and developers familiar with technologies like SQL Server, T-SQL, Transact-SQL, LINQ and C# to implement repeatable dataflows. Enterprise IT teams at organizations like Goldman Sachs, JP Morgan Chase, Bank of America, Citigroup use Power Query capabilities through integrations with Microsoft Power Platform, Azure Data Factory, Azure Data Lake Storage, and governance layers in Microsoft Purview.

History and development

Power Query emerged from work inside Microsoft Research and product teams responsible for Microsoft Excel's business intelligence features, evolving in parallel with initiatives like Power Pivot, Power View, and Power BI to address self-service BI demands cited by analysts at Gartner, Forrester Research, and IDC. Early previews targeted Excel users and the developer community at events such as Microsoft Build and Microsoft Ignite, with iterative releases aligned to cloud services like Office 365 and strategic cloud partners such as Amazon Web Services and Google Cloud Platform. Corporate adoption accelerated after integrations with SQL Server Integration Services and the inclusion of Power Query technology in Power BI Desktop and the Power Platform suite. Influential Microsoft engineers and product managers contributed to its maturation alongside community feedback from forums such as Stack Overflow, Microsoft TechCommunity, and user groups affiliated with PASS (Professional Association for SQL Server).

Architecture and components

Power Query architecture combines a client-side mashup engine, a formula language runtime, connector libraries, and cloud-hosted dataflow orchestration. Core components include the M engine (also known as Power Query Formula Language), connector modules for systems like SAP HANA, Oracle Database, Salesforce, and authentication integrations with identity providers such as Azure Active Directory, Okta, Ping Identity. The mashup engine executes query folding against backends including SQL Server, PostgreSQL, Snowflake, BigQuery to delegate transformations when possible. In cloud contexts, integration points tie into Power BI Service dataflows, Azure Synapse Analytics pipelines, and enterprise cataloging in Microsoft Purview; governance often leverages Azure Active Directory roles, Microsoft Entra ID, and Azure Policy.

Query language and functions

The Power Query Formula Language (M) is a strongly typed, declarative functional language influenced by concepts from F#, Haskell, Lisp and query languages like SQL and XQuery. M supports primitives and higher-order functions, record and table types, and extensibility via custom connectors developed with the Power Query SDK and Visual Studio tooling. Typical functions interact with data sources such as CSV, JSON, XML, OData, REST APIs exposed by services like GitHub API, Twitter API, Google Analytics, and enterprise SOAP endpoints. Advanced users combine M with DAX expressions in scenarios within Power BI Desktop and Microsoft Excel to implement complex calculations and time intelligence routines used by analytics teams at firms like Siemens, General Electric, Procter & Gamble.

Integration with Microsoft products

Power Query is embedded in Microsoft Excel (for Microsoft 365 and certain Office versions), Power BI Desktop, Power BI Service, and data integration services like Azure Data Factory and Azure Synapse Analytics. It interoperates with storage and compute platforms such as Azure Blob Storage, Azure Data Lake Storage, SQL Server, Azure SQL Database, and third-party warehouses like Snowflake, Google BigQuery, Amazon Redshift. Authentication, governance, and monitoring integrate with Azure Active Directory, Microsoft Purview, Azure Monitor, and Microsoft Defender where applicable. The product roadmap and feature announcements have historically been communicated at events like Microsoft Ignite, Microsoft Build, and through collaboration with enterprise partners including Accenture, Capgemini, and IBM Consulting.

Use cases and workflows

Common use cases span self-service analytics, data cleansing, data enrichment, and operational reporting for organizations in sectors served by McKinsey & Company, Bain & Company, Boston Consulting Group, and industry-specific platforms such as EPIC Systems in healthcare and SAP ERP in manufacturing. Analysts use Power Query to connect to sources like Salesforce, Workday, ServiceNow, Marketo, perform merge and append operations, pivot and unpivot tables, and create parameterized dataflows for recurring ETL tasks. Workflows typically progress from source connection to transformation steps recorded as an M script, validation with sample data, and output to destinations such as Excel workbooks, Power BI datasets, Azure Data Lake, or SQL Server for downstream reporting by BI teams at enterprises like Walmart, Target Corporation, Costco.

Performance, security, and governance

Performance tuning involves promoting query folding, reducing row scans, and leveraging native connectors and pushdown to backends like SQL Server, Snowflake, BigQuery; monitoring uses tools such as Performance Monitor (Windows), Azure Monitor, and telemetry surfaced in Power BI Service. Security considerations include credential management, OAuth flows with providers like Azure Active Directory, Okta, encryption at rest via Azure Storage Service Encryption, and role-based access controlled through Microsoft Purview or Azure RBAC. Governance patterns combine versioning in GitHub, deployment pipelines in Azure DevOps, and policy enforcement using Azure Policy and organizational controls in Microsoft 365 administration, supporting compliance regimes referenced by regulators such as SEC, GDPR (European Union), HIPAA in healthcare contexts.

Category:Microsoft software