Action Required – Synapse Spark Pool error

Question

Action Required – Synapse Spark Pool error

Aman Raj (HCL TECHNOLOGIES) 0 Microsoft External Staff

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.

Kajal Pawar 0 Reputation points

2026-06-22T10:59:47.6+00:00

The error is caused by expired Shared Access Signature (SAS) tokens configured for Azure Storage diagnostic emitters.EUS emitter tokens expired on June 13, 2026, and WUS emitter tokens expired on June 16, 2026.This expiration prevents Spark jobs from writing essential Driver and Executor logs to the storage accounts.To resolve this, the diagnostic emitter configurations must be updated with new, valid SAS tokens

3 answers

Your answer

Kajal Pawar 0 Reputation points

2026-06-22T10:59:47.6+00:00

The error is caused by expired Shared Access Signature (SAS) tokens configured for Azure Storage diagnostic emitters.EUS emitter tokens expired on June 13, 2026, and WUS emitter tokens expired on June 16, 2026.This expiration prevents Spark jobs from writing essential Driver and Executor logs to the storage accounts.To resolve this, the diagnostic emitter configurations must be updated with new, valid SAS tokens

Answer 1

Pilladi Padma Sai Manisha 10,945 Microsoft External Staff Moderator

Hi @Aman Raj (HCL TECHNOLOGIES)
The issue appears to be related to expired SAS tokens configured for the Synapse Spark diagnostic emitters rather than a Synapse Link or Dataverse synchronization problem itself. Since the EUS and WUS diagnostic emitter SAS tokens have expired, Spark jobs are unable to write Driver and Executor logs to the associated storage accounts, which can impact monitoring and troubleshooting capabilities.

Please regenerate and update the SAS tokens used by the Synapse Spark diagnostic emitters and verify that they have sufficient validity and required permissions. After updating the tokens, rerun the Spark jobs and validate whether Synapse Link synchronization resumes successfully.

If the issue persists after renewing the SAS tokens, collect the Spark application IDs, workspace name, affected region, and timestamps of failed synchronization attempts for further investigation.

Pilladi Padma Sai Manisha 10,945 Reputation points Microsoft External Staff Moderator

2026-06-24T02:14:44.72+00:00

Hi @Aman Raj (HCL TECHNOLOGIES)

Following up to see if the below answer was helpful. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Answer 2

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more

Answer 3

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.