Why do some implementations of Confluence Embedded Pages work better than others?

[David at David Simpson Apps]

Confluence Embedded Pages (CEP) allow you to publish Confluence content in external systems. It's powerful stuff and here's some examples.

If however you are using apps and macros from Atlassian Marketplace, it seems that some implementations are better than others.

In the example below, we are using Table from CSV from the Atlassian Marketplace. It is a macro built on Atlassian Connect. Here's what it looks like in a Confluence page:

It displays tabulated data in your page.

To aid things visually, I've added

"👇 👇 👇 👇 👇  Macro here 👇 👇 👇 👇 👇 " above the macro, and 

" ☝️ ☝️ ☝️ ☝️ ☝️ Macro here ☝️ ☝️ ☝️ ☝️ ☝️" below the macro.

If the macro is not displayed, you'll just see these next to each other

Confluence Embedded Pages done right

The following examples display the macro correctly

Refined for Confluence

 Everything works good in Refined's use of CEP. You can see the table of data.

Jira Project Pages

 Everything works good in Jira Project Pages' use of CEP. You can see the table of data.

Confluence Embedded Pages done wrong

The following examples do not display the macro at all.

Confluence Cloud for Microsoft Teams (by Atlassian)

I couldn't get this integration to work at all in the native Microsoft Teams app, but using Teams in the browser, the page was displayed.

Unfortunately, the macro was not displayed correctly, and worse there was not even a placeholder to show that content was missing.

Miro

Miro's implementation of CEP was the same as Atlassian's Teams integration. The macro was missing without even a placeholder:

I've tried to understand what's different for the Teams & Miro versions of CEP that stops them from working properly, but have not worked it out yet.

Perhaps it's something to do with iframe sandboxing or the content security policy of some frame ancestors. 

If anyone knows how to fix these so that they work correctly, I am all ears. 

I'm also happy to update this post as and when each is fixed.

Cc: @Lennon Liao @Dugald Morrow 

[David at David Simpson Apps · Accepted solution]

What do you know, Atlassian fixed the macro support in the browser-based version of Teams:

And it now works in Miro too!

 Thanks @Lakhan Rochwani.

[Lakhan Rochwani]

Happy to know @David at David Simpson Apps ! 

[David at David Simpson Apps]

@Lakhan Rochwani it looks to me that only pages without marketplace/connect macros are actually editable in CEP. Is there a public ticket for this, do you know?

[Dugald Morrow]

Hi @David at David Simpson Apps , I don't know exactly what the differences are between these apps, but I've been informed the team is currently working on full support for Connect macros.

[David at David Simpson Apps]

👍

[David at David Simpson Apps]

Another thing that’s most interesting is that the “atl.footer” extension location works in the Jira Project Pages and Refined implementations but not in the MS Teams or Miro implementations. 🤔

[Lakhan Rochwani]

Thanks @David at David Simpson Apps for such a great blog!

[David at David Simpson Apps]

My pleasure @Lakhan Rochwani.

I want all Confluence Embedded Pages to work beautifully, so if you know anyone responsible for Confluence Cloud for MS Teams, could you give them a nudge? Same for our friends at Miro. 

Big respect to the folks at Refined, they give it 💯.

[Lakhan Rochwani]

@David at David Simpson Apps already did! 
Thanks for bringing this to our attention! 

[David at David Simpson Apps]

Also, I notice the ones that don’t work have the “Powered by Confluence” bit at the bottom. Maybe it’s connected 🪄

[Raj - Refined]

@David at David Simpson Apps Appreciate the kind words about Refined, mate! 

[David at David Simpson Apps]

@Lakhan Rochwani @Lennon Liao @Dugald Morrow  Do you know if the servicedesk at https://fy22august.atlassian.net/servicedesk/customer/portal/6/group/19/create/63  is actively monitored? And by whom?

It's listed as the way to get Embedded Pages working here:
https://atlaskit.atlassian.com/packages/confluence/embedded-confluence-public/docs/Prerequisites-and-installation 

• The 3rd party will need to reach out to Atlassian/an Atlassian representative via this service desk request form and provide the domain(s) used by the 3rd party application for Atlassian to allowlist.

I'm trying to get my own version of Embedded Pages going so need my domains whitelisted.

[Lennon Liao]

Hi @David at David Simpson Apps Yes it is monitored but we are in the midst of transitioning it to a different service desk. Appreciate your patience! We will follow up shortly. Thank you.