Include from GitHub to Confluence Cloud

Isolated Cloud Support

Overview

The app is also available as an Isolated Cloud version, supporting customers who use Atlassian’s Confluence Isolated Cloud environment.

This page explains the differences between the standard cloud version of Include from GitHub to Confluence and the version for Atlassian Isolated Cloud.

The Isolated Cloud version meets the security and networking requirements of Atlassian Isolated Cloud while letting teams include GitHub-hosted content directly in Confluence pages.

Most functionality remains the same, but administrators and users should note key differences.


Key Differences

The following capabilities differ between the standard cloud version and the Isolated Cloud version.

Feature

Standard Cloud Edition

Isolated Cloud Edition

File Macro

check mark Available

check mark Available

Directory Macro

check mark Available

check mark Available

Pull Request Macro

check mark Available

check mark Available

Issue Macro

check mark Available

check mark Available

Gist Macro

check mark Available

check mark Available

GitHub Domain Approval

❌ Not Required

check mark Required

Separate Backend URL for GitHub Enterprise

❌ Not Available

check mark Available

Note: Some setups use different URLs for browser access and for backend services. For example, the Web URL goes through a gateway or proxy that applies company-wide authentication and blocks normal API and backend calls. See Configuration documentation.

Static IP Support

check mark Available

❌ Not Available

Images referenced by relative path in Markdown and AsciiDoc files

check mark Available

check mark Available

Images referenced by absolute URL in Markdown and AsciiDoc files

check mark Available (only for public repos)

❌ Not Available

Note: Relative images (images stored in the same repository) are supported in the Isolated Cloud edition once domain approval is granted. Images referenced by absolute URL are not supported.


GitHub Domain Approval

In the Isolated Cloud edition, you must approve access to GitHub domains before the app can retrieve content from repositories.

This approval applies to both GitHub.com and GitHub Enterprise connections as part of the Isolated Cloud edition's security controls.

What this means

  • GitHub.com domains must be approved before repository content can be accessed.

  • Repository content cannot be retrieved nor the connection to GitHub authenticated properly until domain approval is complete.

  • Additional domain approvals are required when connecting to new GitHub Enterprise instances.

Administrator Guidance

For detailed configuration steps, see the GitHub.com and GitHub Enterprise configuration guides.


Static IP Support

The Isolated Cloud edition does not support the static IP feature.

What this means

  • Your GitHub Enterprise instance must be either publicly accessible or reachable from the Isolated Cloud environment. If you have any questions or concerns, please contact us via the Support Portal.


Embedded Images in Markdown and AsciiDoc Files

In the Isolated Cloud edition, images are supported when they are referenced by a relative path to a file in the same repository.

What this means

  • Images referenced by relative path render normally. This works for GitHub.com and GitHub Enterprise.

  • Images referenced by absolute URL are not supported. This includes URLs pointing to the same repository (for example https://<your-host>/org/repo/blob/main/diagram.png) and images on external websites. They can appear broken or missing.

  • The rest of the Markdown or AsciiDoc content renders as usual.

Workaround

Store the image in the same repository and reference it with a relative path.


Configuration

Refer to the Configuration documentation for differences when configuring GitHub integrations in Isolated Cloud environments.


Additional Information

For more information about Atlassian Isolated Cloud, see:

Atlassian Isolated Cloud Overview