Add external user to a distribution list in office 365 to be reinstated
We request the feature for adding external users to a distribution list in office 365 be reinstated.
thomas dowling commented
Yes, this feature SHOULD BE a basic function of any email system. We need to communicate with students (9,000+) and can not go through process of adding duplicate external contacts to our AD. May have to setup and extra mail lists software to do what a office365 email distribution list should do doubling the work. Ridiculous. Should have stayed with groupwise.
This basic feature is realy important!
Please support us.
Joe Toner commented
This is an urgent requirement for our company.
A well needed solution that is missing from a basic functionality of a distribution list.
Vincent Grondman commented
I agree with this request. We house a large world wide project and we have SharePoint as well. The problem is when somebody is already in SharPoint as a guest user you can not add that email address as a contact because of the same smpt address. Therefor DL are not an option and we have to use Groups. Here you can add external user directly via outlook to that group. Problem with groups is that is creates another SP area and their own notebook etc and we don't want that because we already have a SP. Also a problem with groups is that people can sign out of the group theirselves. Not ideal because we need to track who is in which team. DL seems better for emailing groups but it is missing the option to add external contacts directly regardless if they are a contact or not.
I agree with Anonymous commented · March 22, 2017 10:40; we should be able to add as contact if it is an external cloud account...
Michael Holley commented
Per the advice of Anonymous on 03-22-17, I was able to add an email contact and then Guest User to my O365 AD. This does seem like a somewhat common thing, though I don't know if the limitation is based on Exchange Distribution Groups or the Azure AD Integration.
Thanks for the workaround info.
Craig Humphrey commented
Personally, I don't think you should have to create Contacts just to be able to email External users. Particularly those of us that are 100% cloud.
I guess Anonymous' issue is where you're trying to maintain a global Contacts list in on-prem AD, rather than using a CRM or personal contacts.
Chris Gillespie commented
We are a non-profit with many volunteers that help us each and every day. We need to be able to add external users who may or may not be guest users on our account, to distribution groups/lists that can be centrally managed by the list/group owner.
If I want to share documents with external users, I would absolutely require that they be guest users.
I have the exact same issue stated by the Anonymous users. You should be able to add a contact after you create the guest user in Azure.
I do not agree with this. I have just gone through a difficult call with Technical Support. At first they missed the point, but eventually we understood each other, and I feel I understand this better. Please consider the following (also evidenced here by another person: https://answers.microsoft.com/en-us/msoffice/forum/all/issues-syncing-ext-accounts/8b6e6d4f-895a-4920-8052-ad3faa70cec0).
What this link shows, and what my call to technical support showed (eventually) is that if you create a 'contact' FIRST, then share a site/document with that contact, an external user (#EXT#) will get created with a matching email address. That is clearly what Microsoft wants people in your case to do, and what I suggest you should do. Contacts are the correct place to record people who can be emailed.
I think you have mis-identified the problem. The problem is the connection between Contacts and External users, as Microsoft have programmed it. If you create the Contact FIRST, then no problem. HOWEVER, if you share with an external user first AND THEN try to create the contact you get an error:
'The proxy address "SMTP:firstname.lastname@example.org" is already being used by the proxy addresses or LegacyExchangeDN of "blah_blah.com#EXT#"
So, currently you have to delete your external user, create a contact, then share all appropriate sites/documents with that contact, at which point an external user is created again, grafefully linked to the contact.
Microsoft SHOULD, when you create the contact AFTER already having an #EXT# user ask:
'An external user already exists with this address, would you like to create a contact for that user?' And then you could click OK if you wanted to, and not have to destroy all the shares just to get the Contact set up.