Differences between Data Center and Cloud versions

Enable strict allowlist

The parameter applies the given allowlist to all content in the HTML content. See Allowlist for more information.

Location of HTML data;
Location of XML code;
Location of XSL code

Supported formats:

• Default, in the macro body

• URL

• Attachment

• File

• Template

Supported formats:

• Default, in the macro body

• URL

• Attachment

File and template options are not applicable for Confluence cloud.

Allow same origin

These parameters are the integration points for the macro security feature available in the cloud version. Read more in the configuration page and the macro guide.

Allow script execution

Select to use JTidy

For updates on this feature, refer to https://appfire.atlassian.net/browse/HTML-203.

Remove conflicting tags

For updates on this feature, refer to https://appfire.atlassian.net/browse/HTML-204.

Include head section HTML

Both the HTML and XSLT macros do not support this feature in cloud.

For updates on this feature, refer to https://appfire.atlassian.net/browse/HTML-226,

https://appfire.atlassian.net/browse/HTML-205.

Show error message panel

For updates on this feature, refer to https://appfire.atlassian.net/browse/HTML-227.

Omit a panel when output is wiki

Not applicable

Currently, Confluence Cloud does not support these features.

Width of the iframe

Not applicable

Disable secure processing feature

Not applicable

URL allowlisting

Supported natively by Confluence and configured using the Global Configuration page

Administrators must manually allowlist URLs in the Global Configuration page

For more information, refer to CLOUD-2636.

Macro security

Macro security is integrated with the cloud version unlike the server/DC version where you need to use the Macro Security for Confluence app with this app.

Custom editor

A new custom editor with better usability and efficiency is now available for use with the cloud version. Available from the 1.6.0 version.