Public folder not visible for one specific user

Question

Hi all,

I have a migrated user who cannot see their on-prem synced mail enabled public folders after migration.

The other migrated users with the same permissions can see them.

I have validated it looks good on the Exchange Online side, all the users have the attributes.

I have gone through this article https://techcommunity.microsoft.com/blog/exchange/how-users-access-public-folders-and-what-to-do-when-they-cannot-access-them/3963070 and not sure what else i can check especially since other users can see the folders..

Here is an export of the user's outlook log which shows the public folder information:

Any thoughts?

<?xml version="1.0" encoding="utf-8"?>

<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">

<Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">

<User>

<DisplayName>User</DisplayName>

<LegacyDN>/o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=e83fbfb5a8974cec8f8dd457fcfc073e-user</LegacyDN>

<AutoDiscoverSMTPAddress>******@domain.com</AutoDiscoverSMTPAddress>

<DeploymentId>00000000-0000-0000-0000-000000000000</DeploymentId>

</User>

<Account>

<AccountType>email</AccountType>

<Action>settings</Action>

<MicrosoftOnline>True</MicrosoftOnline>

<ConsumerMailbox>False</ConsumerMailbox>

<Protocol Type="mapiHttp" Version="1">

<MailStore>

<ExternalUrl>https://outlook.office365.com/mapi/emsmdb/?MailboxId=******@domain.com</ExternalUrl>

</MailStore>

<AddressBook>

<ExternalUrl>https://outlook.office365.com/mapi/nspi/?MailboxId=******@domain.com</ExternalUrl>

</AddressBook>

</Protocol>

<Protocol>

<Type>WEB</Type>

<Internal>

<OWAUrl AuthenticationMethod="LiveIdFba, OAuth">https://outlook.office365.com/owa/</OWAUrl>

<Protocol>

<Type>EXCH</Type>

<ASUrl>https://outlook.office365.com/EWS/Exchange.asmx</ASUrl>

</Protocol>

</Internal>

<External>

<OWAUrl AuthenticationMethod="Fba">https://outlook.office365.com/owa/domain.com/</OWAUrl>

<Protocol>

<Type>EXPR</Type>

<ASUrl>https://outlook.office365.com/EWS/Exchange.asmx</ASUrl>

</Protocol>

</External>

</Protocol>

<Protocol>

<Type>EXHTTP</Type>

<Server>outlook.office365.com</Server>

<SSL>On</SSL>

<AuthPackage>Basic</AuthPackage>

<ASUrl>https://outlook.office365.com/EWS/Exchange.asmx</ASUrl>

<EwsUrl>https://outlook.office365.com/EWS/Exchange.asmx</EwsUrl>

<EmwsUrl>https://outlook.office365.com/EWS/Exchange.asmx</EmwsUrl>

<SharingUrl>https://outlook.office365.com/EWS/Exchange.asmx</SharingUrl>

<EcpUrl>https://outlook.office365.com/owa/</EcpUrl>

<EcpUrl-um>?path=/options/callanswering</EcpUrl-um>

<EcpUrl-aggr>?path=/options/connectedaccounts</EcpUrl-aggr>

<EcpUrl-mt>options/ecp/PersonalSettings/DeliveryReport.aspx?rfr=olk&exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx>&realm=domain.com</EcpUrl-mt>

<EcpUrl-ret>?path=/options/retentionpolicies</EcpUrl-ret>

<EcpUrl-sms>?path=/options/textmessaging</EcpUrl-sms>

<EcpUrl-publish>?path=/options/calendarpublishing/id/<FldID></EcpUrl-publish>

<EcpUrl-photo>?path=/options/myaccount/action/photo</EcpUrl-photo>

<EcpUrl-connect>?path=/options/socialnetworks&ignore1=<Action>&ignore2=<Provider></EcpUrl-connect>

<EcpUrl-tm>options/ecp/?rfr=olk&ftr=TeamMailbox&exsvurl=1&realm=domain.com</EcpUrl-tm>

<EcpUrl-tmCreating>options/ecp/?rfr=olk&ftr=TeamMailboxCreating&SPUrl=<SPUrl>&Title=<Title>&SPTMAppUrl=<SPTMAppUrl>&exsvurl=1&realm=domain.com</EcpUrl-tmCreating>

<EcpUrl-tmEditing>options/ecp/?rfr=olk&ftr=TeamMailboxEditing&Id=<Id>&exsvurl=1&realm=domain.com</EcpUrl-tmEditing>

<EcpUrl-extinstall>?path=/options/manageapps</EcpUrl-extinstall>

<OOFUrl>https://outlook.office365.com/EWS/Exchange.asmx</OOFUrl>

<OABUrl>https://outlook.office365.com/OAB/f75c79ff-ff95-471e-a666-ad91a50c1154/</OABUrl>

<ServerExclusiveConnect>On</ServerExclusiveConnect>

</Protocol>

<AlternativeMailbox>

<Type>Archive</Type>

<DisplayName>In-Place Archive -User</DisplayName>

<SmtpAddress>******@domain-com.mail.onmicrosoft.com</SmtpAddress>

<OwnerSmtpAddress>******@domain.com</OwnerSmtpAddress>

</AlternativeMailbox>

<AlternativeMailbox>

<Type>Delegate</Type>

<DisplayName>Shared1</DisplayName>

<SmtpAddress>******@domain.com</SmtpAddress>

<OwnerSmtpAddress>******@domain.com</OwnerSmtpAddress>

</AlternativeMailbox>

<AlternativeMailbox>

<Type>Delegate</Type>

<DisplayName>Shared mailbox</DisplayName>

<SmtpAddress>******@domain.com</SmtpAddress>

<OwnerSmtpAddress>******@domain.com</OwnerSmtpAddress>

</AlternativeMailbox>

<AlternativeMailbox>

<Type>Delegate</Type>

<DisplayName>Team</DisplayName>

<SmtpAddress>******@domain.com</SmtpAddress>

<OwnerSmtpAddress>******@domain.com</OwnerSmtpAddress>

</AlternativeMailbox>

<AlternativeMailbox>

<Type>Delegate</Type>

<DisplayName>Shared</DisplayName>

<SmtpAddress>******@domain.com</SmtpAddress>

<OwnerSmtpAddress>******@domain.com</OwnerSmtpAddress>

</AlternativeMailbox>

<PublicFolderInformation>

<SmtpAddress>******@onpremdomain.com</SmtpAddress>

</PublicFolderInformation>

</Account>

</Response>

</Autodiscover>

Answer 1

Hi Raymond Brooks,

Thank you for posting your question in the Microsoft Q&A forum.

From Autodiscover XML results, we can see that there is an on-prem public folder ******@onpremdomain.com available for current user. Since O365 users could only connect on-prem public folder from Outlook side with such hybrid environment, please try to:

Check if current Outlook client is using an old Outlook version. Try to upgrade to the latest version and setup a new Outlook profile to test again.

Try to setup other O365 mailbox that could check on-prem pf on this computer, setup the affect mailbox to other user’s computer. We could check if this issue only occurs with specific user or specific outlook client computer.

Run the following command from Exchange Online powershell, check and contrast all settings between normal O365 mailbox and the problematic one:

Get-CASMailbox user_name |fl

Get-Mailbox user_name |fl

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.