Refresh SQL Endpoint activity is not saving Workspace ID in pipeline JSON

Hi User,

The behavior you are seeing looks like a potential issue with the Refresh SQL Endpoint (Preview) activity serialization rather than a configuration problem.

Since the UI still allows selecting a workspace, but the generated pipeline JSON no longer stores the corresponding WorkspaceId, Git-based deployment cannot resolve the target artifact reference. The error:

ActivityName RefreshSqlEndpoint contains an invalid WorkspaceId <null>

indicates that the deployment process is expecting a workspace identifier during validation but is receiving a null value.

A few things you can check:

• Verify whether newly created pipelines and existing pipelines both show the same behavior. This can help determine if it is a recent regression or related to older artifacts.

• Compare the pipeline JSON from a previous working commit where WorkspaceId was present with the current exported definition.

• Try removing and recreating the Refresh SQL Endpoint activity in a test pipeline to see whether the workspace reference is serialized correctly.

• If you are using Fabric Git integration, avoid manually editing generated JSON unless necessary, as preview activities may have schema changes during development.

Since this is a Preview feature and directly impacts CI/CD scenarios, it would be useful to report it through Microsoft Support with:

• Workspace ID

• Pipeline item ID

• Activity ID / Request ID from the failure

• Previous working JSON and current JSON comparison

• Fabric region and capacity details

For more information:

• Microsoft Fabric Git integration: https://learn.microsoft.com/fabric/cicd/git-integration/intro-to-git-integration

• Microsoft Fabric Data Factory pipelines: https://learn.microsoft.com/fabric/data-factory/pipelines

• Microsoft Fabric Support: https://learn.microsoft.com/power-bi/support/create-support-ticket

Could you also confirm:

• Did this start after a recent Fabric update or release?

• Does the issue happen only during Git update/deployment, or does the pipeline also fail when executed directly?

• Are other Fabric pipeline activities with workspace references serializing correctly?

This will help determine whether it is a product regression specific to the Refresh SQL Endpoint activity or a broader pipeline artifact serialization issue.

Yes, We are also facing the same issue , After saving the pipline workspace Id is automatically removed. However this was run as expected for few runs. 

I tryed many apporch like 

1. Dynamically pass the workspace Id using the veriable liberary . 

I am working on the solution as soon as I get anything I will update. 

Thank you for your suggestions. We have already gone through these troubleshooting steps, and below are our observations:

1. Verified with both new and existing pipelines
   • We have to check with dev team.
2. Compared with a previously working pipeline
   • We compared the current pipeline definition with an older pipeline that was working correctly.
   • The older pipeline JSON included the WorkspaceId, whereas the current pipeline JSON does not serialize this property even though the Workspace is selected.
3. Removed and recreated the Refresh SQL Endpoint activity
   • We created a new test pipeline and recreated the Refresh SQL Endpoint activity from scratch.
   • The issue persists. The Workspace is selectable in the UI, but the generated JSON still does not include the WorkspaceId.
4. Manual JSON modification
   • We understand that manually editing the generated JSON is not recommended.
   • However, for troubleshooting purposes, we manually added the WorkspaceId to verify whether it would resolve the deployment issue. Instead, deployment failed with a different validation error indicating that the Workspace is null, suggesting that manually adding the property is not a valid workaround.

Could you please confirm whether this is a known issue with the Refresh SQL Endpoint (Preview) activity, or if there is an alternative approach recommended for Git-based deployments? Also for your additional questions,

• Did this start after a recent Fabric update or release?
  • We are not certain of the exact Fabric release that introduced this behavior. However, we did not experience this issue previously. Earlier, the Refresh SQL Endpoint activity serialized the WorkspaceId in the pipeline JSON. The issue has started occurring only recently.
• Does the issue happen only during Git update/deployment, or does the pipeline also fail when executed directly?
  • The pipeline executes successfully when run directly from the Fabric workspace.
  • The issue occurs only during Git update/deployment (PR merge/Update from Git), where deployment validation fails because the WorkspaceId is reported as null.
• Are other Fabric pipeline activities with workspace references serializing correctly?
  • Yes. We have verified other pipeline activities that reference workspaces, and they are being serialized correctly. The issue appears to be specific to the Refresh SQL Endpoint (Preview) activity.

Just reporting that we are facing the same issue, a fix or workaround would be highly appreciated! 

Thankyou Prince0011 , odtJitendra   for Addressing the issue.

Hi RajeshFabric ,

Thank you for reaching out to Microsoft Fabric Community Forum,Based on your issue below are the few debug points which can resolve your issue.

• Confirm the issue is with Git deployment serialization, not the pipeline itself, because the pipeline runs successfully when executed directly in the Fabric workspace.
• Do not manually add WorkspaceId to the generated JSON. The subsequent Workspace is null validation error indicates that this is not a supported workaround.
• Recreate the Refresh SQL Endpoint (Preview) activity and test it in a newly created pipeline. Since you have already done this and the issue persists, it further indicates a product-level issue.
• Verify the latest Fabric changes/known issues related to the Refresh SQL Endpoint (Preview) activity and Git integration.
• Use an alternative supported approach for triggering the SQL endpoint refresh, such as an appropriate Fabric/SQL REST API-based implementation, if available for your scenario.
  
  

If the issue is still exists please raise a support ticket to the microsoft support team they will check the traces and resolve your issue.

Below is the link to raise a support ticket :

Create a Fabric and Power BI Support Ticket - Power BI | Microsoft Learn

Thanks,

Chaithanya.

Thankyou rceu_42 , Prince0011 , odtJitendra  for Addressing the issue.

Hi RajeshFabric ,

Thank you for reaching out to Microsoft Fabric Community Forum,

As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?

Regards,

Chaithanya

Hi rceu_42 ,

Thank you for the update that you resolved your issue by using web activity and calling rest api.  Let us know if you need any further assistance?

Thanks,

Chaithanya.

v-kathullac , looks like issue is resolved by fabric team, now I am able to see the workspace id in json. Thank you for assistance.

Hi RajeshFabric ,

Glad to hear that your issue got resolved Let us know if you need any further assistance?

Thanks,

Chaithanya.

Now we are facing same issue, workspaceID is missing in json and not able to use the refresh sql endpoint activity in any of the pipelines.