CORS is blocking embedded Lucid diagram in Azure DevOps wiki

Hi ​@krispenner, thank you for posting in the community and sorry to hear you are having trouble with adding published links to your Azure DevOps wiki pages. Would you mind sharing some additional information to help us take a closer look at the issue you’re seeing?

• A brief description of how you are embedding your published diagrams in Azure DevOps? (full published link, published image etc) 
• A screenshot of the issue (Please feel free to censor/redact any sensitive information)
• A screenshot of the associated Javascript Console output after reproducing the issue. You can open your Javascript Console by pressing Ctrl+Shift+J (if your computer is a Windows/Linux) OR Cmd+Opt+J (if your computer is a Mac).

Thank you for your help! Please feel free to let us know if you have any questions. 

Pubish full document as PNG. If I copy the link from the browser and paste it in its own tab it loads fine.

Hi ​@krispenner, thank you for sharing that information. I am checking this behaviour with the relevant team and will share an update here as soon as I have more information. Please feel free to let us know if you have any questions in the meantime. 

Hi ​@Leianne C 

Do you have any status update on this issue since this issue has been posted? Our team is experiencing the same problem.

​@Leianne C  We are facing the similar issue and do you have any update on this? 

Hi ​@RJellema ​@sdindigala, thanks for checking in! Our team is still actively working on investigating this, and I don’t have an update to share just yet. I know this can be frustrating, and I really appreciate your patience in the meantime. I’ll be sure to follow up as soon as we have more information! 

In the meantime, could you please share a screenshot of the associated Javascript Console output after reproducing the issue? You can open your Javascript Console by pressing Ctrl+Shift+J (if your computer is a Windows/Linux) OR Cmd+Opt+J (if your computer is a Mac).

Thank you for your help and please let us know if you have any additional questions. 

Hi all, thank you for your patience as our team looked into this. This has been reported as a bug with our development team. I apologize for any disruption this may cause, and I will update this thread with any new information about a fix. Please follow along on this thread for updates, and post any additional questions or concerns below.

Thanks it’s working again now. 

Thanks for the update, ​@krispenner! I’m glad to hear the issue is not longer happening. Please feel free to let us know if you have any questions or topics you’d like to discuss!