"Duplicate" Workbooks

%3CLINGO-SUB%20id%3D%22lingo-sub-2676406%22%20slang%3D%22en-US%22%3E%22Duplicate%22%20Workbooks%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2676406%22%20slang%3D%22en-US%22%3E%3CP%3EI%20was%20alerted%20of%20a%20strange%20issue%20this%20morning.%26nbsp%3B%20It%20would%20appear%20as%20if%2C%20any%20workbooks%20that%20we%20have%20created%2C%20are%20showing%20as%20two%20entries%20within%20the%20%22My%20Workbooks%22%20Tab%20with%20the%20same%20name.%26nbsp%3B%20This%20appears%20to%20be%20the%20case%20for%20any%20workbooks%20that%20were%20pushed%20via%20our%20CI%2FCD%20deployment%20outlined%20below%20as%20well%20as%20workbooks%20that%20were%20manually%20created.%26nbsp%3B%20As%20far%20as%20it%20would%20appear%3B%20these%20two%20entries%20are%20in%20fact%20the%20same%20workbook%20(same%20workbookID).%26nbsp%3B%20They%20also%20operate%20as%20the%20same%20workbook%20i.e.%20if%20a%20change%20is%20made%20in%20one%2C%20the%20change%20is%20evident%20to%20the%20second%20link.%26nbsp%3B%20If%20one%20is%20deleted%2C%20they%20both%20are%20removed%20from%20the%20listing.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20also%20attempted%20to%20remove%20all%20workbooks%20and%20push%20again%20via%20the%20CI%2FCD%20process%20listed%20below%20but%20this%20still%20results%20in%20%22duplicate%22%20workbooks.%26nbsp%3B%20%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECI%2FCD%20Deployment%3A%26nbsp%3B%20Pushed%20via%20azure%20pipeline%20leveraging%20the%20New-AzResourceGroupDeployment%20cmdlet.%26nbsp%3B%20This%20deployment%20has%20been%20operational%20for%20at%20least%203%20weeks%20without%20issue.%26nbsp%3B%20No%20change%20to%20this%20pipeline%2Fdeployment%20has%20taken%20place%20either.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOther%20users%20have%20also%20experienced%20the%20same%20issue%20across%20multiple%20workspaces%20as%20well.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHas%20anyone%20else%20seen%20this%20issue%20before%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2676789%22%20slang%3D%22en-US%22%3ERe%3A%20%22Duplicate%22%20Workbooks%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2676789%22%20slang%3D%22en-US%22%3EI%20am%20noticing%20the%20same%20thing.%20There%20are%202%20entries%20for%20the%20same%20workbook%20and%20if%20I%20edit%20one%20of%20the%20entries%2C%20the%20other%20entry%20shows%20the%20same%20edit.%20Only%20the%20one%20that%20I%20have%20saved%20from%20a%20template%20is%20not%20duplicated.%3C%2FLINGO-BODY%3E
Occasional Contributor

I was alerted of a strange issue this morning.  It would appear as if, any workbooks that we have created, are showing as two entries within the "My Workbooks" Tab with the same name.  This appears to be the case for any workbooks that were pushed via our CI/CD deployment outlined below as well as workbooks that were manually created.  As far as it would appear; these two entries are in fact the same workbook (same workbookID).  They also operate as the same workbook i.e. if a change is made in one, the change is evident to the second link.  If one is deleted, they both are removed from the listing. 

 

We have also attempted to remove all workbooks and push again via the CI/CD process listed below but this still results in "duplicate" workbooks.   

 

CI/CD Deployment:  Pushed via azure pipeline leveraging the New-AzResourceGroupDeployment cmdlet.  This deployment has been operational for at least 3 weeks without issue.  No change to this pipeline/deployment has taken place either.

 

Other users have also experienced the same issue across multiple workspaces as well.  

 

Has anyone else seen this issue before?

 

Thank you!

4 Replies
I am noticing the same thing. There are 2 entries for the same workbook and if I edit one of the entries, the other entry shows the same edit. Only the one that I have saved from a template is not duplicated.

Was hoping to see a solution here. We are experiencing the same issue. Workbooks are duplicated.

Was told on a call with MS that this is a known Azure wide issue and should be resolved soon
Do we have update on this issue, look like majority of Azure Sentinel instances may impacted with this duplicate workbook issue.