Fabric Activity Failing with NameResolutionFailure for Power BI Endpoint

[Gettoknow]

Hi Team,

We are encountering the following error while executing a Microsoft Fabric activity:

Error calling the endpoint 'https://api.powerbi.com'.

Response status code: 'ClientSideException : NameResolutionFailure'.

Request didn't reach the server from the client. This could happen because of an underlying issue such as network connectivity, a DNS failure, a server certificate validation or a timeout.

Exception message:
"The remote name could not be resolved:
'd610a**********.w.api.powerbi.com'

Additional Information:

• Fabric Capacity is active and healthy.
• The issue occurs before the request reaches the Power BI service.
•  No recent changes were made to the workspace configuration.
•  We are trying to determine whether this is related to DNS resolution, networking, regional endpoint issues, Private Link configuration, or a known Fabric service issue.

Has anyone experienced a similar error? If so, were there any specific checks or fixes that resolved the issue?

Any guidance would be appreciated.

Thank you.

[Gettoknow]

Thanks Pallavi for your inputs.

[v-shchada-msft]

Hi @Gettoknow 

Just checking in to see if your issue has been resolved. Please let us know if you need any further assistance.

Thank you.

[Gettoknow]

Hi Team,

Thanks its resolved now.

[v-shchada-msft]

Hi @Gettoknow,
Thank you for reaching out to the Microsoft Fabric Community Forum and thanks to the @pallavi_r for sharing helpful insights.

Just checking in, were you able to resolve the issue? If not please feel free to share an update and we will be happy to assist further.
Your feedback will also help others facing similar challenges.

Thank you.

[pallavi_r]

Hi @Gettoknow 

This looks like a DNS resolution issue. The error indicates that Fabric is unable to resolve the Power BI endpoint (*.api.powerbi.com) before the request is sent.

If you're using Private Link, I'd recommend checking whether the Private DNS zone is correctly linked to the VNet and whether the endpoint hostname resolves successfully. It's also worth reviewing any custom DNS servers, conditional forwarders, firewall, or proxy configurations that could be impacting name resolution.

As a quick validation, try running an nslookup against the failing hostname. If the hostname cannot be resolved, that would point to a DNS or Private Link configuration issue.

A  missing or incorrectly configured Private DNS zone link is often the root cause of this type of NameResolutionFailure error.

If this post helps, please accept this as a solution. Appreciate your kudos.

Thanks,

Pallavi