Share via

Action Required – Synapse Spark Pool error

Aman Raj (HCL TECHNOLOGIES) 0 Reputation points Microsoft External Staff
2026-06-18T17:24:17.05+00:00

We have enabled synpase link of dataverse which ahs stopped syncing since 16 and we are getting below error.

We have identified an issue with the Synapse Spark diagnostic emitter configuration, which is impacting the logging for the ModuleExecutionFramework.

Upon review, it appears that the SAS tokens configured for the Azure Storage diagnostic emitters have expired:

  • EUS emitter valid until: June 13, 2026
  • WUS emitter valid until: June 16, 2026

Since both tokens are now expired, Spark jobs are unable to write Driver and Executor logs to the configured storage accounts. This may result in missing logs and potential disruptions in monitoring and troubleshooting.

Azure Synapse Analytics
Azure Synapse Analytics

An Azure analytics service that brings together data integration, enterprise data warehousing, and big data analytics. Previously known as Azure SQL Data Warehouse.

0 comments No comments

1 answer

Sort by: Most helpful
  1. Ravi Kiran Pagidi 80 Reputation points
    2026-06-20T03:59:00.15+00:00

    Hi Aman,

    From the message, this looks related to the Synapse Spark diagnostic emitter configuration attached to the Spark pool used by Synapse Link.

    The SAS tokens used by the emitters have expired, so Spark jobs may not be able to write driver/executor logs to the configured storage location. Since your sync stopped around the same time, I would fix the emitter configuration first and then recheck the Synapse Link status.

    Please check the following:

    Go to Synapse Studio > Manage > Apache Spark configurations.

    Find the Spark configuration attached to the Spark pool used by the Synapse Link profile.

    Update the expired SAS token in the diagnostic emitter setting, or update the Key Vault secret if the token is stored in Key Vault.

    Make sure the SAS token has the required write/create permissions on the target storage container and has a valid future expiry.

    Re-apply the Spark configuration to the Spark pool.

    Stop/restart any active Spark sessions and wait for the next Synapse Link sync/conversion job.

    Also confirm that the Spark pool still exists, is using a supported Spark runtime, and is not being used for other workloads. Synapse Link for Dataverse Delta conversion depends on the configured Spark pool.

    Docs:

    Synapse Spark diagnostic emitter to Azure Storage: https://learn.microsoft.com/en-us/azure/synapse-analytics/spark/azure-synapse-diagnostic-emitters-azure-storage

    Synapse Link for Dataverse troubleshooting: https://learn.microsoft.com/en-us/power-apps/maker/data-platform/azure-synapse-link-troubleshooting-guide

    Dataverse Delta Lake / Spark pool requirements: https://learn.microsoft.com/en-us/power-apps/maker/data-platform/azure-synapse-link-delta-lake

    If this emitter configuration is not visible or appears to be Microsoft-managed, then I would open a support ticket with the workspace name, Spark pool name, Synapse Link profile, UTC time when sync stopped, and the expired token details. Do not share the actual SAS token publicly.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.