Link to home
Create AccountLog in
Avatar of John Water
John WaterFlag for United States of America

asked on

Need a Shared Contact list I can access in Outlook and in Office 365 Portal

I need to be able to have a shared contact list that I can use as follows:
When I am sending out an email I want to be able to access the entries in this shared contact list by clicking on the "To" field and being able to see that shared contact list among the drop down option under "Address Books".

Currently I can do this in the Outlook client by using Public Folder contact list and right clicking on it, selecting Properties, Outlook Address Book tab and checking the box to "Show this folder as an email Address Book".
The problem is this type of Public folder is not view able from O365 OWA.

Does anyone have any options?

Thank you,
ASKER CERTIFIED SOLUTION
Avatar of Vasil Michev (MVP)
Vasil Michev (MVP)
Flag of Bulgaria image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Avatar of John Water

ASKER

Thank you for the quick response. I had tried that the Public Folders show up in People under Other Contacts. The issue is I consistently received the following notice from different PCs and different browsers. :
When I first click on the public folder name I get "Your request can't be completed right now. Please try again later"
Within 5-10 minutes, the contacts show up.

is this what you are seeing in your experience?
I have not yet had a chance to look that the you provided, but will do so soon
So far it has worked OK for me, but then again I'm not really using PF Contacts a lot. But if you are used to adding the PF as address book, the Address List solution might be better, it will be visible in Outlook and OWA without any additional steps.
SOLUTION
Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
After setting up public folders as favorites still had the problem. Contacted MS support and below is what they said:

We discussed the case with the senior peers and they have informed us that this is a known issue and the backend team is already working on it and the fix are been deployed on the affected users tenant. This issue should be resolved soon.