Server Migration: Tableau Server to Power BI Service¶

A comprehensive guide for migrating Tableau Server (or Tableau Cloud) infrastructure — sites, projects, workbooks, permissions, schedules, subscriptions, and monitoring — to Power BI Service.

Overview¶

Server migration covers the infrastructure and administration layer: how content is organized, who has access, how data refreshes, and how administrators monitor the environment. This guide maps every Tableau Server concept to its Power BI Service equivalent and provides step-by-step migration procedures.

1. Architecture comparison¶

1.1 Tableau Server vs Power BI Service¶

1.2 Content hierarchy mapping¶

flowchart LR
    subgraph Tableau["Tableau Server"]
        SITE[Site] --> PROJECT[Project]
        PROJECT --> SUB[Sub-Project]
        SUB --> WB[Workbook]
        SUB --> DS[Data Source]
        PROJECT --> WB2[Workbook]
        PROJECT --> DS2[Data Source]
    end

    subgraph PowerBI["Power BI Service"]
        TENANT[Tenant] --> WS[Workspace]
        WS --> RPT[Report]
        WS --> SM[Semantic Model]
        WS --> DF[Dataflow]
        WS --> DASH[Dashboard]
        TENANT --> WS2[Workspace 2]
        WS2 --> APP[App]
    end

2. Sites to workspaces¶

2.1 Concept mapping¶

2.2 Workspace design patterns¶

Pattern 1: Workspace per team (most common)

Workspace: "Sales Analytics"
  - Sales Semantic Model (shared)
  - Sales Dashboard Report
  - Sales Detail Report
  - Sales Monthly Report

Workspace: "Finance Analytics"
  - Finance Semantic Model (shared)
  - Budget vs Actual Report
  - P&L Report

Pattern 2: Workspace per lifecycle stage (for ALM)

Workspace: "Sales Analytics [Dev]"
Workspace: "Sales Analytics [Test]"
Workspace: "Sales Analytics [Prod]"
// Use deployment pipelines to promote content

Pattern 3: Shared semantic model workspace (for governance)

Workspace: "Enterprise Semantic Models"
  - Sales Semantic Model (Certified)
  - Finance Semantic Model (Certified)
  - HR Semantic Model (Certified)

Workspace: "Sales Reports"
  - Sales Dashboard (live connection to Sales Semantic Model)
  - Sales Detail (live connection to Sales Semantic Model)

For large organizations, consider separating semantic models into dedicated workspaces with restricted access. Reports in other workspaces connect via live connection. This mirrors Tableau's published data source pattern and provides better governance.

2.3 Workspace naming conventions¶

3. Groups and permissions¶

3.1 Tableau groups to Entra ID security groups¶

3.2 Tableau site roles to Power BI workspace roles¶

3.3 Content-level permissions¶

3.4 Permission migration steps¶

1. Export Tableau groups — use Tableau REST API to list all groups and members
2. Create Entra ID security groups — mirror Tableau groups in Entra ID
3. Map members — ensure Tableau users exist in Entra ID (usually already the case for AD-synced environments)
4. Assign workspace roles — add security groups to workspaces with appropriate roles
5. Configure App audiences — for consumer-facing content, create Apps with audience groups
6. Test access — validate that each user group can access the same content they had in Tableau

4. Row-level security (RLS)¶

4.1 Tableau user filters to Power BI RLS¶

Tableau user filters (e.g., [Region] = USERNAME()) map to Power BI row-level security (RLS) roles.

Tableau approach:

// Data source filter: [Region] = USERNAME()
// Or calculated field: IF ISMEMBEROF("East Team") THEN "East" END

Power BI approach:

// Step 1: Create RLS role in Power BI Desktop
// Modeling → Manage Roles → New Role
// Role name: "RegionFilter"
// Table: Sales
// DAX filter expression:
[Region] = USERPRINCIPALNAME()

4.2 Group-based RLS with mapping table¶

For organizations with complex security (users see data for multiple regions), use a security mapping table:

// Security mapping table (in the semantic model):
// UserEmail          | Region
// user1@company.com  | East
// user1@company.com  | Central
// user2@company.com  | West

// RLS role DAX expression on the Sales table:
CONTAINS(
    SecurityMapping,
    SecurityMapping[UserEmail], USERPRINCIPALNAME(),
    SecurityMapping[Region], Sales[Region]
)

4.3 Dynamic RLS patterns¶

4.4 RLS migration validation¶

After configuring RLS:

1. Test with "View as" role — in Power BI Desktop, Modeling → View as → select role
2. Test with specific users — in Power BI Service, use "Test as" with real user identities
3. Compare results — validate that the same user sees the same data in both Tableau and Power BI
4. Test edge cases — users with multiple roles, users with no mapping, new users

5. Subscriptions and alerts¶

5.1 Subscriptions¶

5.2 Data alerts¶

5.3 Data Activator (advanced alerting)¶

Power BI Data Activator extends basic alerts with automated actions:

• Trigger Power Automate flows when data conditions are met
• Send Teams messages to specific channels
• Create ServiceNow tickets automatically
• Trigger Azure Functions for custom logic
• Monitor data in real-time, not just on refresh

Tableau has no equivalent to Data Activator.

6. Scheduled refresh¶

6.1 Tableau extract schedules to Power BI refresh schedules¶

6.2 Configuring scheduled refresh¶

Step 1: Publish semantic model to Power BI Service
Step 2: Navigate to Dataset Settings
Step 3: Expand "Scheduled refresh"
Step 4: Set refresh frequency (daily, weekly) and times
Step 5: Configure data source credentials (if not already set)
Step 6: Configure gateway connection (for on-prem sources)
Step 7: Enable "Send refresh failure notification"
Step 8: Test with "Refresh now"

6.3 Incremental refresh (for large datasets)¶

// Power BI incremental refresh replaces Tableau incremental extract:
// 1. Create Power Query parameters: RangeStart and RangeEnd (DateTime type)
// 2. Filter source table by date column between RangeStart and RangeEnd
// 3. In Power BI Desktop: right-click table → Incremental refresh
// 4. Configure:
//    - Archive data starting: 3 years ago
//    - Incrementally refresh data starting: 30 days ago
//    - Only refresh complete days: checked

7. Admin monitoring and governance¶

7.1 Tableau Server admin tools to Power BI admin¶

7.2 Usage metrics migration¶

Tableau Server tracks views, users, and data source usage. Power BI provides similar telemetry:

7.3 Admin portal key settings¶

After migration, configure these tenant settings in the Power BI Admin portal:

8. Tableau REST API to Power BI REST API¶

8.1 API mapping¶

8.2 Automation migration¶

For organizations with Tableau REST API automation:

1. Inventory all API calls — document every automated process that uses the Tableau REST API
2. Map to Power BI API — use the table above to find equivalent endpoints
3. Update authentication — replace Tableau PAT/credentials with Entra ID service principal
4. Update scripts — rewrite automation scripts to use Power BI REST API
5. Test thoroughly — validate that automated processes produce the same results

9. Migration execution checklist¶

Phase 1: Workspace setup¶

• Design workspace hierarchy (based on Tableau site/project structure)
• Create workspaces in Power BI Service
• Create Entra ID security groups matching Tableau groups
• Assign workspace roles to security groups
• Configure tenant settings in Admin portal

Phase 2: Security configuration¶

• Implement RLS roles in semantic models
• Create security mapping tables (for dynamic RLS)
• Test RLS with representative users
• Configure data source credentials in Power BI Service
• Set up on-premises data gateway (if replacing Tableau Bridge)

Phase 3: Refresh and automation¶

• Configure scheduled refresh for all Import-mode datasets
• Set up incremental refresh for large datasets
• Recreate subscriptions
• Configure data alerts
• Migrate API automation scripts

Phase 4: Monitoring and governance¶

• Deploy Capacity Metrics App
• Set up usage metrics reports per workspace
• Configure audit log integration (Sentinel or Log Analytics)
• Enable deployment pipelines for Dev/Test/Prod promotion
• Document admin procedures and runbooks

Last updated: 2026-04-30 Maintainers: CSA-in-a-Box core team Related: Data Source Migration | Embedding Migration | Migration Playbook