...
Although your organizations SharePoint is configured to allow External sharing your registered guests will not be able to see the content of configured lists or documents in the Confluence macros. This problem occurs even if they should have access to these lists or documents in SharePoint itself.
Cause
To enable In order to provide guest access, the app must be able to resolve different tenants based on their names. The implementation required for this blocks authentication within the app if the SharePoint Online public site name does not match the Microsoft 365 tenant name. In this case, a fallback is used, which ensures that the app continues to work, but without guest accessUnfortunately the current implementation requires the SharePoint domain to match the default Azure AD domain provided by Microsoft when creating a new tenant (that’s the default behaviour when not using aliases).
| Info |
|---|
The default case should look like this: Azure AD Domain: contoso.onmicrosoft.com |
In case you are using a SharePoint alias the domains will not match anymore. The app will then fall back into the behaviour of using the home tenant of the current user. Therefore guest access will not work in case you are using an alias.
For a bit more background see also How does SharePoint Online user and tenant selection work in Confluence Cloud?
...