A report refreshes in Power BI Desktop but fails after publication. How would you investigate?

Example Answer

I'd start with the semantic model's refresh history in the service and read the actual error. A successful Desktop refresh only proves that my machine and credentials can reach the source; it doesn't prove the service has the same access.

For an imported model using on-premises SQL Server, I'd check the gateway is online, the connection's server and database match the model, the model is mapped to that connection, and the required connection permissions and credentials are valid. For a cloud source, I'd check its configured connection and network access rather than assume it needs a gateway.

After fixing the identified issue, I'd run an on-demand service refresh and confirm it succeeds before relying on the schedule. I'd also document the connection owner and failure alert route so the same problem is easier to resolve next time.

Make it your own

Name a source and authentication method you actually know. Describe this as your troubleshooting approach unless you have handled a real service-refresh incident.

Why this works

Separates local success from service access, follows the error to a specific dependency, and verifies the repair in the environment that failed.

Interviewer follow-up

Does every cloud data source avoid the need for a gateway?

No. A directly reachable cloud source can usually connect without one, but private networking or required connector software can change that. I'd check the connector's supported service connection path and the network restrictions before choosing a gateway arrangement.

References

• Microsoft reference 1
• Microsoft reference 2
• Microsoft reference 3