Linked entities in dataflows result in data lake folders for the source entities being deleted

[Anonymous]

We have linked entity data flows like this ...

Dataflow 1, Entity A ---> \

Dataflow 2, Entity B --->   /------> Dataflow 4 - Entity A (load flag unset)  --> \

Dataflow 3, Entity C ---> /                                   Entity B (load flag unset)  -->    ---> Entity D append queries    

                                                                             Entity C (load flag unset)  --> /

Storage has been set to be out Azure Data Lake Gen 2 instance, which works fine most of the time. However, we are seeing for the above that the underlying data lake folders are being deleted for any of the linked entities (eg the folder for dataflow 1, Entity A is deleted), which of breaks things. 

I would never expect the source folders to be deleted.

If this a known issue please?

Thanks!

[v-chuncz-msft]

@Anonymous 

To get faster and better technical support for this issue, you may directly create a support ticket.

[jmannhardt]

dividorr  Have you opened a support case with MSFT and received any feedback?  We are experiencing this same issue in another tenant.  We have an active support case open.  Some CDM folders have been restored, but cause and on-going reliability are unclear at this point.

[Anonymous]

Hi @jmannhardt ,

Yes, we raised, and today got the response below. Seems a recent release broke something.

Thanks,

Matt

O365 Comms has been posted to all the impacted Tenants and here is the comms for Your reference.
 
Comms Message:
Title: Issues while interacting with dataflows stored in Azure Data Lake Storage (ADLS) Gen2

User impact: Users may experience issues interacting with dataflows stored in ADLS Gen2.
  
More info: Specifically, dataflows where the directory was manually deleted in the ADLS2 storage account, and the dataflow was recreated with the same name.

Current status: We're continuing to monitor the rollback to ensure it completes successfully. We expect the rollback will be completed on Wednesday, June 24, 2020.

Scope of impact: Your organization is affected by this event, and this issue could potentially affect your users if they have specifically created dataflows within a directory that previously belonged to a now deleted dataflow.

Estimated time to resolve: We expect the rollback to be completed and the issue resolved on Wednesday, June 24, 2020.

[jmannhardt]

Thanks @Anonymous  we received the same notice and are in the process of validating the recovery effort by MSFT.