Microsoft Teams displays “Log in with Atlassian account” instead of Confluence page title – also aff

[Xandra Volkmann]

We are experiencing an issue when sharing Confluence Cloud page links in Microsoft Teams.

When a Confluence page URL is pasted into a Microsoft Teams chat or message, Teams displays the link text as:

“Log in with Atlassian account”

instead of displaying the actual Confluence page title.

Environment

• Confluence Cloud

• Microsoft New Teams

• Confluence Cloud for Microsoft Teams app installed

• User is successfully logged in to the Confluence Cloud app in Teams

• Confluence site: https://neotiv.atlassian.net/wiki

Steps already tested

1. Installed the Confluence Cloud app in Microsoft Teams.

2. Successfully logged in with the Atlassian account.

3. Completely closed and restarted Microsoft Teams.

4. Opened the relevant Confluence page while authenticated.

5. Copied and pasted the Confluence page URL into a Teams message.

6. The displayed link text remains “Log in with Atlassian account”.

7. We also tested manually creating the hyperlink in Teams using Ctrl+K. The issue remains.

8. The issue is reproducible with multiple Confluence pages.

Important difference from CONFCLOUD-84529

We are aware of the existing issue CONFCLOUD-84529 concerning Microsoft Teams displaying “Log in with Atlassian account” instead of the Confluence page title.

However, the documented issue appears to primarily concern older Confluence pages / pages using the legacy editor, while newly created pages are described as working correctly.

This is not the case in our environment.

The issue is reproducible with newly created Confluence pages using the current Confluence editor as well.

Therefore, we would like to clarify whether:

• this is now considered part of CONFCLOUD-84529,

• the scope of CONFCLOUD-84529 has expanded to newly created pages,

• or this represents a separate issue.

Expected behaviour

When a Confluence page URL is pasted into Microsoft Teams, the actual Confluence page title should be displayed.

Example:

REP-MNG-008 Report for evaluation of performance of the QIMS processes 2026_1

Actual behaviour

Microsoft Teams displays:

Log in with Atlassian account

The link itself still points to the correct Confluence page and users with the appropriate permissions can access the page.

Could you please confirm whether this behaviour is covered by CONFCLOUD-84529 or whether a separate bug should be created?

If it is a known issue, please also let us know whether there is currently a workaround or a planned fix.

[James Gamble]

Hola Xandra,

I’d raise this with Atlassian Support rather than assuming CONFCLOUD-84529 already covers it.

The existing bug is definitely very close to what you’re seeing. Still, Atlassian currently describes it as primarily affecting older Confluence pages and specifically says that newly created pages resolve correctly. Their published reproduction steps actually include comparing an older page with one created within the last 24 hours. The bug remains unresolved and has no documented workaround.

That is important in your case because you’ve reproduced the same “Log in with Atlassian account” preview on newly created pages using the current editor, even after installing and authenticating the Confluence Cloud app in New Teams.

Atlassian’s Microsoft Teams documentation says users can preview Confluence content shared through the Teams integration, so what you’re seeing isn’t the expected behavior.

Since the links themselves still point to the correct pages and affected users can open them successfully, this appears to be more of a problem with the metadata or the Smart Link unfurling process than with users’ actual Confluence permissions.

I’d have your site admin open an Atlassian Support case, reference CONFCLOUD-84529, and provide at least one newly created affected page, along with its creation date, the Teams version, screenshots of the preview, and confirmation that the user is logged in to the Confluence Cloud app in Teams. Support can then associate your site with CONFCLOUD-84529 if the scope has expanded, or create/link a separate defect if the current editor behavior has a different cause.

Given the troubleshooting you’ve already completed, I don’t see another documented workaround I’d recommend trying before Support reviews it.

Thanks,

James

[Xandra Volkmann]

Hello James, 
thank you very much for your reply. I’ve already followed your advice. I’m now waiting for a response from Atlassian support.

Best regards,
Xandra