In many organizations, Atlassian Confluence serves as a vital knowledge base while SharePoint Online is the hub for intranet content and collaboration. Instead of keeping these platforms siloed, you can embed Confluence pages directly in your SharePoint intranet to create a unified experience. By using a Confluence SharePoint connector (in this case, a web part available from the SharePoint Store), you bring Confluence content into SharePoint seamlessly. This approach offers several benefits: your team can access wiki articles, documentation, and project notes from Confluence without leaving SharePoint, information stays up-to-date (no need for manual copy-paste), and you avoid the hassle of a full Confluence to SharePoint migration. In short, an integrated Confluence-SharePoint setup means less context-switching and more productivity for your users.
One such solution is the Atlassian Confluence integration web part by adenin (available on Microsoft AppSource). What does it do? It allows live Confluence data (pages, lists of pages, etc.) to be embedded on SharePoint pages, essentially acting as a bridge between the two platforms (see details here). With this integration, you can embed Confluence pages in SharePoint and even browse Confluence content from within SharePoint. In the next sections, we’ll cover how to install this Confluence SharePoint integration and explore two ways you can embed Confluence content: by adding a single Confluence page, or by importing an entire Confluence space interface into a SharePoint page.
Step-by-step guide to installation
Getting the Confluence integration web part set up in SharePoint is straightforward. Just follow these steps:
- Install the Confluence Integration from the SharePoint Store: Go to the Atlassian Confluence integration by adenin listing on Microsoft AppSource and click “Get it now” (Free Atlassian Confluence web part for SharePoint – adenin). This will initiate the installation through your SharePoint tenant’s app catalog.
- Add it to your SharePoint Apps: After you click “Get it now”, you’ll be taken to the SharePoint Store within your Microsoft 365 tenant. Click “Add to Apps site” to add the app to your SharePoint environment (Free Atlassian Confluence web part for SharePoint – adenin). During the installation, you may be prompted to enable the app for all sites (choose “Enable this app and add it to all sites”) and to approve certain permissions (the web part uses Confluence’s API, so it will request access—approve these prompts to allow the integration).
- Add the web part to a SharePoint page: Navigate to the SharePoint page (on a modern site) where you want to embed Confluence content. Click Edit on the page, then click the + to add a web part. Find the Atlassian Confluence integration web part (it might appear under “Apps” or you can search for “Confluence”) and add it to your page (Free Atlassian Confluence web part for SharePoint – adenin). Once the web part is added, you should see a prompt to configure it – click the Configure button (often a pencil icon or a prompt in the web part area) to open the configuration panel on the right.
- Connect to your Confluence account: In the Confluence web part configuration sidebar, click on “+ Connect to Atlassian Confluence”. A popup will guide you through authorizing access to your Confluence content (Free Atlassian Confluence web part for SharePoint – adenin). You’ll likely need to log in to Confluence (if you aren’t already) and grant permission for the web part to retrieve data. Follow the steps (click Next and approve as needed) until the connection process is complete. Once you finish the wizard (by clicking Finish on the last step), the web part will be connected and start loading data from Confluence.
After these steps, the Confluence integration web part is installed and configured on your SharePoint page. Now you’re ready to choose what Confluence content to display. In the next section, we’ll look at two embedding options: showing a specific Confluence page or embedding a broader Confluence interface within SharePoint.
Once the Confluence SharePoint web part is set up, you can use it in a couple of different ways depending on your needs. The integration is flexible: you can either embed a single Confluence page (for example, an important wiki page or a glossary) or you can embed an entire Confluence space’s content with navigation and search capabilities. We’ll explore both options below, including how to configure each and when to use them.
Option 1: Single page embedding (specify Confluence page by Id)
If you want to display a specific Confluence page inside a SharePoint site, the web part allows you to do that by using the page’s ID. This is perfect for scenarios where you have a particular wiki article, knowledge base entry, or project page in Confluence that you’d like to show on a SharePoint page (for instance, embedding a “Glossary” page from Confluence into an HR SharePoint site, or a project plan page into a Team site).
How to configure a single page embed:
- Find the Confluence Page ID: In Confluence Cloud, open the page you want to embed and check the URL. The page ID is usually a numeric identifier in the URL (for example, in a URL like
.../pages/viewpage.action?pageId=123456, the number123456is the page ID). Copy this ID value. (In Confluence Server or Data Center, you can find the Page ID via the page information or URL as well.) (Free Atlassian Confluence web part for SharePoint – adenin) - Enter the Page ID in the SharePoint web part: Edit your SharePoint page and open the Confluence web part’s configuration panel. Select your data source as “Get page by id” and there will be a field to specify a Confluence Page ID. Paste the ID you copied into this field.
- Apply and view: Apply the changes and save/publish your SharePoint page. The web part will fetch the content of that Confluence page and display it right on the SharePoint page. All the text, images, and formatting from the Confluence page should appear within the web part. Users on SharePoint can now read the content as if it’s part of the SharePoint site – and since it’s live from Confluence, any updates made in Confluence will reflect here.
Example of an singular Confluence page that can be embedded within a SharePoint site. The Confluence page content (text, images, etc.) appears in the SharePoint page via the integration, allowing users to read the knowledge base article without leaving SharePoint.
This single-page embedding approach ensures a specific piece of content is front-and-center for your SharePoint users. It’s especially useful for content like policies, how-to articles, or FAQs maintained in Confluence that you want to surface in SharePoint. Instead of duplicating that content manually, the web part pulls it in dynamically. According to the product description, you can “import a specific Confluence page including its full content and images” just by providing its Page ID – the integration takes care of embedding the page for you.
What if you want to give users a broader window into Confluence – say, an entire space or a set of pages – rather than just one page? The Confluence SharePoint integration web part can also be configured to embed an interactive Confluence interface within SharePoint. In this mode, users can navigate between pages or even between different Confluence spaces, and use Confluence content more freely – almost like having Confluence itself inside your SharePoint page.
How to configure a full-space (multiple pages) embed:
- Choose the “Get pages” data source: In the Confluence web part’s configuration under Data selection you can then further refine this mega query for example by restricting the number of results or filtering for specific Confluence Spaces (like “Marketing Team Space”) using the Space’s ID.
- Apply and use: After configuring, save the SharePoint page. The web part will load an interface showing Confluence content. Users might see a list of pages (e.g., a tree of the Confluence space, or a feed like latest updates or popular pages) within the web part frame. They can click on pages to view their content, navigate to sub-pages, or even use the search function to find specific Confluence content – all without leaving the SharePoint page.
(Free Atlassian Confluence web part for SharePoint – adenin) Example of Confluence content embedded as a feed within SharePoint. In this “full Confluence UI” mode, the web part can display multiple pages – for instance, a list of recently updated Confluence pages as shown above – and allow users to click through to view content or open it in Confluence. This provides a mini Confluence experience inside the SharePoint site.
With the full Confluence UI embedded, your SharePoint intranet can serve as a one-stop portal. Team members can browse knowledge base articles, navigate wiki spaces, or check the latest updates from Confluence right on an intranet homepage or team site. This option is powerful for organizations that want to encourage use of Confluence content but within the familiar context of SharePoint. Essentially, the integration acts as a Confluence SharePoint integration hub, where Confluence’s interface (pages, spaces, etc.) is available inside SharePoint. Users get the best of both worlds in one place. As noted on the app page, you can “see all Confluence pages in an interactive Confluence UI” embedded in SharePoint enabling dynamic navigation and even search within that web part.
Comparison with other methods
You might be wondering how this web part approach compares to other ways of bridging Confluence and SharePoint. Let’s briefly look at a few alternative methods (and why using the SharePoint Store app is often the easier and more efficient choice):
- Using an iFrame or Embed Code: One simple way people try is embedding a Confluence page via an
<iframe>on a SharePoint page (using the out-of-the-box Embed web part or a script editor). Sadly, Confluence does not support this feature as it is blocked. - Third-Party Connectors or APIs: There are other Confluence SharePoint connector solutions (for example, Communardo available on the Atlassian Marketplace) and one could also build a custom integration using Confluence’s REST API. However, custom development takes time and maintenance, and many third-party connectors come with licensing costs or complex setup (servers, add-ons on the Confluence side, etc.). The adenin integration we discussed is a ready-made SharePoint web part that you can install in a few clicks, with no coding required. It’s also SaaS (so no need to install anything on Confluence if you’re using Confluence Cloud). This ease-of-deployment means you can have an integration up and running in minutes, rather than embarking on a lengthy IT project.
- Manual Content Migration or Duplication: Another approach some teams consider is a Confluence to SharePoint migration – essentially moving all wiki content out of Confluence and into SharePoint pages (or duplicating the content in both places). Migration might involve exporting pages to Word or HTML and importing to SharePoint, or using specialized migration tools. Not only is this process labor-intensive, it can also lead to loss of data fidelity (certain Confluence macros or formatting might not transfer cleanly) and it creates a maintenance burden: once content is copied, you now have to update it in two places or fully switch to SharePoint. In contrast, embedding via a web part allows you to maintain a single source of truth (the content stays in Confluence) while simply displaying it in SharePoint. This means no duplication and always-up-to-date information on SharePoint pages.
Overall, the web part integration method stands out for its simplicity and real-time connectivity. There’s no need to rewrite or migrate your content, and you avoid clunky solutions that might break. As the adenin app page highlights, with their web part you can simply embed Confluence wherever you want in your intranet. It’s a plug-and-play solution: just install, connect, and start embedding content. This ease of use, combined with the ability to interact with Confluence content (not just view a static snapshot), makes the Confluence SharePoint integration via the AppSource web part a superior choice for most use cases.
Embedding Confluence pages in SharePoint provides a win-win scenario: teams accustomed to SharePoint can access and interact with Confluence knowledge without leaving the intranet, and content managers can maintain documentation in Confluence without worrying about duplicating it in multiple platforms. This Confluence–SharePoint integration enhances collaboration by bringing together the strengths of both platforms. You get the robust wiki capabilities of Confluence and the familiar, centralized environment of SharePoint in one place. From single page embeds (ideal for specific documentation or wiki articles) to a full Confluence space embedded with navigation and search, the possibilities cater to a variety of knowledge-sharing needs.
The best part is how easy it is to set up and use. With a few clicks, the Confluence SharePoint connector web part is installed and ready to go, avoiding complex migrations or custom development. The result is a dynamic, up-to-date SharePoint page that surfaces all the relevant Confluence content your users need.
Ready to get started? Bring your Confluence content into SharePoint today by installing the Atlassian Confluence integration web part from the SharePoint Store. You can find it on Microsoft AppSource – just look for “Confluence integration by adenin” and click Get It Now to add it to your tenant. In no time, you’ll have a modern SharePoint intranet with Confluence seamlessly woven in. Give it a try and boost your team’s productivity and knowledge sharing by bridging these two powerful platforms. Install the Confluence SharePoint Integration web part from the SharePoint Store now and take your intranet to the next level!
