Company wide Shared Address List

%3CLINGO-SUB%20id%3D%22lingo-sub-1382311%22%20slang%3D%22en-US%22%3EShared%20Address%20List%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1382311%22%20slang%3D%22en-US%22%3E%3CP%3EA%20little%20bit%20all%20customers%20need%20to%20have%20a%20company%20directory%20managed%20by%20one%20person%20(typically%20a%20secretary).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESaid%20address%20book%20should%20also%20be%20usable%20by%20the%20various%20mobile%20devices%2C%20with%20which%20users%20should%20be%20able%20to%20call%20their%20contacts%20using%20the%20voice%20assistants.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20only%20thing%20that%20comes%20to%20mind%20is%20to%20implement%20a%20SharePoint%20list%20which%20should%20then%20be%20copied%20%2F%20synchronized%20with%20the%20various%20users.%20With%20Power%20Automate%20I%20could%20set%20up%20a%20flow.%20The%20problem%20is%20that%20you%20work%20in%20a%20user%20context%20(that%20I%20know)%20and%20therefore%20600%20Flow%20workflows%20should%20be%20configured%20for%20as%20many%20users%20..%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPublic%20folders%20are%20not%20good%20because%20there%20is%20no%20integration%20with%20mobile%3CBR%20%2F%3EShooting%20PST%20imports%20doesn't%20seem%20practical%20to%20me%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20ideas%20%2F%20suggestions%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1382311%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Highlighted
Occasional Visitor

A little bit all customers need to have a company directory managed by one person (typically a secretary).

 

Said address book should also be usable by the various mobile devices, with which users should be able to call their contacts using the voice assistants.

 

The only thing that comes to mind is to implement a SharePoint list which should then be copied / synchronized with the various users. With Power Automate I could set up a flow. The problem is that you work in a user context (that I know) and therefore 600 Flow workflows should be configured for as many users .. 

 

Public folders are not good because there is no integration with mobile
Shooting PST imports doesn't seem practical to me

 

Any ideas / suggestions?

1 Reply
Highlighted

There's no good solution, SPO list should be fine as a central repo, but if you absolutely must copy the contacts to individual mailboxes, best use some EWS-based solution instead. Glen's EWSContacts module is a good start: https://github.com/gscales/Powershell-Scripts/tree/master/EWSContacts