Synapse Link: Changing Incremental Update Folder Structure time interval Azure Synapse Link

Question

Hello,

I have a synapse link to put data from D365 F n O to blob storage. The time interval for the folder structure was previously 60 minutes and I changed it to 720 minutes in the existing synapse link (no other changes, same container, tables not reselected).

I don't see any change yet except that the hourly folders have stopped since the change.

What will happen? Will the hourly existing folders be regenerated? Or is it only that going forward I will see twice a day folders?

Also , if it's twice a day do we know when the data would be put in blob?

Thank you

Answer 1

Hi Niyati,

Changing the time interval on an existing Synapse Link profile should not create or modify folders that have already been created.

The current hourly folders will stay the same. The new interval will only apply from now on. After changing the interval from 60 minutes to 720 minutes, Synapse Link will group incremental changes into larger time-window folders going forward. It will no longer create hourly folders.

A few important points:

• The existing hourly folders are not expected to be recreated or merged.
• The change affects only future incremental folder creation.
• Since 720 minutes is 12 hours, you should normally expect fewer folders, roughly two time-window folders per day, assuming there are changes to export.
• A new folder is generally created only when there are incremental changes to write for that interval. If there are no changes, you may not see a new folder immediately.
• The folder timestamp/time window is controlled by Synapse Link processing and is not necessarily guaranteed to appear exactly at a fixed clock time such as 12 AM/12 PM. There can also be some delay depending on the volume of changes, service processing, and any backlog.

In your case, it's normal that the hourly folders stopped after the change. I recommend monitoring the storage account for the next full 12-hour interval. Also, check that there are real changes occurring in the selected F&O tables.

If no new incremental folders show up after more than one 720-minute window with confirmed table changes, I would check the Synapse Link status and background jobs. I might also pause and resume or refresh the link configuration. However, I would not expect the old hourly folders to be regenerated.

Answer 2

Hi @Deshmukh, Niyati

It sounds like you switched your Azure Synapse Link incremental-update interval from 60 minutes up to 720 minutes (12 hours) and now you’re not seeing any more hourly folders—only the old ones, and nothing new yet. Here’s what’s happening:

No back-fill or re-generation of the old hourly folders

• Changing the interval doesn’t re-create or rename your existing 60-minute folders. All the hourly folders you already have remain as-is.

New folders will only appear on your new 720-minute cadence

  - Going forward the link service will attempt to drop a new timestamped folder every 720 minutes (12 hours) containing the data changes that occurred in that window.
  
     - If no table changed in a given 12-hour period, you won’t even see an empty folder for that interval.
     
     When exactly do those twice-a-day folders land?
     
        - The folder name is the UTC timestamp when the service kicked off that batch. So if your last folder was created at, say, 2024-06-01T00:00Z, the next will roughly appear at 2024-06-01T12:00Z, then 2024-06-02T00:00Z, and so on.
        
           - Note there can be slight variances (retry-logic can occasionally introduce an extra empty timestamp), but generally it’s every 12 hours based on UTC.
           
           What to check if you still don’t see anything after 12 hours:
           
              - Make sure you actually had data changes in that window—zero changes = no new folder.
              
                 - Look at the Changelog/changelog.info file in your container; it always points to the “current” folder being written.
                 

Hope that clears things up!

Reference docs:

• Query and analyze the incremental updates with Azure Synapse Link for Dataverse (how timestamped folders & intervals work) https://learn.microsoft.com/power-apps/maker/data-platform/azure-synapse-incremental-updates?wt.mc_id=knowledgesearch_inproduct_azure-cxp-community-insider#view-incremental-folder-at-microsoft-azure-storage

Answer 3

Changing the Time interval on an existing Azure Synapse Link profile only affects how new incremental folders are created going forward. Existing hourly folders are not regenerated or modified.

Based on the documented behavior:

1. What happens after changing from 60 to 720 minutes
   • The link continues using the same storage account, container, and tables.
   • New incremental folders will now be created every 720 minutes (12 hours) instead of every 60 minutes.
   • Existing hourly folders remain as they are; they are not merged, deleted, or recreated.
2. Why hourly folders appear to have stopped
   • After changing the interval, the system waits for the new, longer interval to elapse before creating the next time‑stamped folder.
   • During this waiting period, it can look like folders have “stopped” because no new folder appears at the old hourly cadence.
3. Will hourly folders be regenerated?
   • No. The documentation states that incremental data is written into time‑stamped folders according to the configured interval, and change data once written is not updated.
   • The initial and historical folders (including the old hourly ones) are kept as‑is unless explicitly deleted by operations on the storage account.
4. What will the folder pattern look like going forward?
   • Going forward, folders will appear every 720 minutes, each containing the changes that occurred within that 12‑hour window.
   • The folder names are timestamps in UTC (yyyy-MM-dd'T'HH:mm:ss.SSSz), and the time difference between consecutive folders reflects the configured interval.
5. When is data written into blob for the 12‑hour interval?
   • For each interval, the system collects changes and then writes them into a new time‑stamped folder at the end of that interval.
   • For example, if the interval is 720 minutes and the last folder closed at 00:00 UTC, the next folder will be created around 12:00 UTC with all changes from 00:00–12:00 UTC.
   • An initial time‑stamped folder is created when the feature is enabled with a copy of the data; subsequent folders are only created when there are data updates during the interval.

If needed, the current folder being written can be identified via Changelog/changelog.info in the storage account; only previous folders should be consumed by downstream pipelines.

---

References:

• Query and analyze the incremental updates with Azure Synapse Link for Dataverse
• Query and analyze the incremental updates with Azure Synapse Link for Dataverse – Prerequisites
• Query and analyze the incremental updates with Azure Synapse Link for Dataverse – View incremental folder at Microsoft Azure Storage
• Query and analyze the incremental updates with Azure Synapse Link for Dataverse – Consume incremental data
• Transition from legacy data integration services – Understanding benefits and cost reductions
• Choose finance and operations data in Azure Synapse Link for Dataverse – Access incremental data changes from finance and operations
• TechTalk: Cloud data warehousing for Dynamics 365 data with Azure Synapse Link for Dataverse