The Complete Guide to Microsoft Copilot in Power BI: Setup, Licensing, and First Queries (2026)

Microsoft Copilot in Power BI is an AI assistant built into the Power BI platform that enables natural language queries, automated report generation, narrative summaries, and DAX formula suggestions. It transforms how analysts interact with data by allowing them to describe what they want in plain language rather than building complex queries manually. However, getting Copilot working in Power BI requires specific licensing, admin configuration, and data model preparation that Microsoft’s documentation scatters across dozens of pages.

This guide consolidates everything you need to know to get Copilot running in Power BI — from licensing requirements through your first production queries.

Licensing Requirements: What You Actually Need

The single most common question about Copilot in Power BI is licensing. The answer depends on whether you are using Power BI Desktop or the Power BI Service, and whether your organization has Fabric or Premium capacity.

Minimum Requirements

For Copilot in Power BI Service (reports and dashboards):

• Microsoft Fabric F2 capacity or higher, OR Power BI Premium P1 capacity or higher
• Power BI Pro or Premium Per User (PPU) license for each user
• Copilot enabled by the Power BI admin at the tenant level
• Workspace hosted on Fabric or Premium capacity

For Copilot in Power BI Desktop:

• Same capacity requirements as the Service — the dataset must be published to a Fabric/Premium workspace
• Power BI Desktop must be connected to the Power BI Service for Copilot features to activate
• Some Copilot features in Desktop work with local models during development, but full functionality requires Service connectivity

Cost Analysis

Fabric F2: Approximately $260/month. This is the entry-level capacity that enables Copilot. Suitable for small to mid-size BI teams (up to 50 concurrent users). Provides 2 Capacity Units (CUs) which determine the computational resources available for Copilot and other Fabric workloads.

Power BI Premium P1: Approximately $4,995/month. Provides dedicated capacity with more computational resources. Suitable for larger deployments with heavy Copilot usage. Includes additional enterprise features beyond Copilot.

Premium Per User (PPU): Approximately $20/user/month on top of E5 licensing. Provides Premium features for individual users without organization-wide Premium capacity. Can enable Copilot for a limited pilot group at lower cost than full capacity licensing.

For organizations testing Copilot, the most cost-effective path is Fabric F2 ($260/month) combined with existing Pro licenses. This enables Copilot for all users whose workspaces are hosted on the Fabric capacity.

Admin Configuration: Enabling Copilot Step by Step

Step 1: Verify Capacity

Confirm that your organization has Fabric F2+ or Premium P1+ capacity provisioned. Check the Power BI Admin Portal → Capacity settings. If no eligible capacity exists, the Copilot tenant setting will not appear.

Step 2: Enable Copilot at the Tenant Level

1. Navigate to the Power BI Admin Portal (admin.powerbi.com)
2. Select Tenant settings from the left navigation
3. Search for “Copilot” in the settings search bar
4. Locate “Users can use Copilot and other features powered by Azure OpenAI”
5. Enable the setting for the entire organization, or restrict to specific security groups for a phased rollout

Step 3: Configure Workspace Settings

Each workspace where Copilot should be available must be assigned to a Fabric or Premium capacity. In the workspace settings, verify that the license mode is set to “Fabric” or “Premium” rather than “Pro” or “Shared.”

Step 4: Data Residency and Compliance Settings

Review the tenant setting “Data sent to Azure OpenAI can be processed outside of your tenant’s geographic region.” For organizations with data residency requirements, disable this setting to ensure Copilot processing stays within your tenant’s geographic boundary. Note that disabling cross-region processing may limit some Copilot capabilities in certain regions.

Step 5: Verify Activation

Open a report in a Fabric/Premium workspace. The Copilot button should appear in the report toolbar. If it does not appear, verify that the user has a Pro or PPU license, the workspace is on eligible capacity, and the tenant setting is enabled for the user’s security group.

Preparing Your Data Model for Copilot

Copilot’s output quality is directly determined by your data model quality. A well-structured model produces accurate, useful Copilot responses. A poorly structured model produces garbage — and unlike a human analyst, Copilot will not warn you that its output is unreliable because the model is messy.

Star Schema Structure

Copilot works best with star schema models — a central fact table surrounded by dimension tables connected by single-column relationships. Flat tables (all data in one wide table) produce significantly worse Copilot results because the AI struggles to understand the relationships between different data elements.

Clear Table and Column Names

Copilot reads table and column names literally. A column named “Amt” will confuse Copilot, while “Sales Amount” will produce accurate results. A table named “DimDate” is less useful than “Date” or “Calendar.” Invest time in renaming tables and columns to use plain, descriptive language.

Measure Descriptions

This is the single most impactful data model improvement for Copilot quality. Add descriptions to your DAX measures that explain what they calculate in natural language. When a measure has a description, Copilot uses it to understand the measure’s purpose and select the right measure for user queries.

Example: Instead of a measure named “YTD Revenue” with no description, add: “Year-to-date total revenue calculated from the Sales fact table, filtered to the current calendar year. Includes all product categories and regions.”

Proper Data Types

Ensure dates are Date type, currencies are Currency type, and percentages are Decimal Number type with appropriate formatting. Copilot uses data types to determine how to format and aggregate values in its responses.

Your First Copilot Queries

Once Copilot is enabled and your data model is prepared, start with these query patterns to test functionality:

Narrative summary: “Summarize the key trends in this report.” Copilot will analyze the visuals on the current report page and generate a written narrative highlighting trends, outliers, and patterns.

Simple aggregation: “What was total revenue last quarter?” Tests whether Copilot correctly identifies the revenue measure, applies the date filter, and returns an accurate number.

Comparison: “Compare sales by region for 2025 vs 2026.” Tests Copilot’s ability to create comparison visuals and apply multiple filters.

DAX suggestion: “Create a measure that calculates the year-over-year growth rate for revenue.” Tests Copilot’s DAX generation capability.

Report page creation: “Create a report page showing monthly revenue trends with a breakdown by product category.” Tests Copilot’s ability to generate complete report layouts with appropriate visualizations.

What Copilot Can and Cannot Do in Power BI

What Copilot Does Well

• Generating narrative summaries of report pages
• Creating simple to moderate complexity report pages from natural language descriptions
• Writing basic DAX measures (aggregations, time intelligence, CALCULATE with straightforward filters)
• Answering questions about the data when the data model is well-structured
• Suggesting visual types appropriate for specific data patterns

Where Copilot Struggles

• Complex DAX involving iterator functions (SUMX with nested conditions), advanced time intelligence, or many-to-many relationships
• Data models without clear naming, star schema structure, or measure descriptions
• Queries requiring context that is not in the data model (business rules, external factors)
• Creating pixel-perfect formatted reports — Copilot creates functional layouts, not production-ready designs
• Working with very large models where grounding requires processing millions of rows

Common Setup Failures and Fixes

Copilot button does not appear: Verify the workspace is on Fabric/Premium capacity, the tenant setting is enabled for the user’s security group, and the user has a Pro or PPU license. Clear browser cache and try again.

Copilot returns generic or inaccurate responses: The data model likely lacks measure descriptions, uses ambiguous column names, or is not in star schema format. Add descriptions to key measures and rename columns to use plain language.

Copilot is slow or times out: The Fabric capacity may be undersized for the model complexity. Monitor capacity utilization in the Fabric admin portal. Consider upgrading from F2 to F4 or F8 for large models.

“Feature not available” error: Check the data residency setting. If cross-region processing is disabled and your region does not yet have local Copilot processing, some features may be unavailable.

Frequently Asked Questions