Issue Publishing to PowerBI Service

Hey Anonymous5 ,

The error message you're encountering “Couldn’t publish to Power BI: A semantic model or report named [xyz] already exists and is set up with cloud refresh” is typically caused when:

• The report you're trying to re-publish has the same name and dataset as the one already deployed in the Power BI Service.

• The existing dataset in the workspace is cloud-refreshed and linked to an underlying source, which prevents overwriting via re-publish from Desktop.

Why Your Workarounds Didn’t Work

1. Turning off cloud refresh only disables the schedule, not the dataset’s cloud configuration. It remains linked to the workspace metadata.

2. Downloading and re-uploading also preserves this link unless you: Remove the dataset or Publish it under a new name.

3. Other reports working implies the issue is isolated to this one report’s dataset linkage/config.

Fix Without Breaking Existing Links

Option 1: Use the “Replace” option in Power BI Service

1. Go to Power BI Service.

2. In the workspace, locate the dataset/report.

3. Select “Download the PBIX” (you already did this).

4. In Desktop, make your changes.

5. Save it with a new name like Report_v2.pbix.

6. In Power BI Service, go to Workspace > Settings > Datasets.

7. Manually delete the old dataset only if you're certain you won’t break downstream artifacts.

8. Publish the new .pbix.

This still breaks shared links unless you reassign permissions and reconfigure dashboards.

Option 2: Use Deployment Pipelines (Recommended for Shared Workspaces)

1. Use Deployment Pipelines to move content between Dev → Test → Prod.

2. Upload the revised report to the Dev stage.

3. Deploy it forward, letting Power BI handle dataset refresh links.

Option 3: Edit via Power BI Service

If your changes are minor:

1. Instead of using Desktop, open the report in Power BI Service > Edit Report.

2. Make the changes directly in the browser.

3. Save—this avoids breaking the refresh config.

This only works if your report doesn't use unsupported visuals or DAX features.

If you found this solution helpful, please consider accepting it and giving it a kudos (Like) it’s greatly appreciated and helps others find the solution more easily.

Best Regards,
Nasif Azam