Forum Discussion
User's cannot update email field in profile.
- AnonymousFeb 16, 2017
Juan I am guessing you meant not a bug. Just to reiterate they only have SharePoint Online Plan 1 and do not synchronize AD. This means that there is no email even set, their account is created and email is blank. There is no where in the GUI to add an email account, even when creating the user, except by going into the SharePoint User Profile after the user has been created. They have been using SharePoint Online for 3+ years where the users have been able to go in and adjust as needed. This is definitley an edge case customer. I could see not allowing it if emails were set, but that should be able to be managed still like you can today via the profile settings. On your recommendation of creating an alias how exactly would that work without exchange being a part of this service? I have clicked all over Office 365 admin center, how the customer manages their users, and see no way to set an alias. I didnt expect to find one either. Maybe we could set all of their emails with PowerShell but that adds overhead and the customer would prefer not to use that method.
- Feb 16, 2017Ey Cory, sorry but I misunderstood your question :-(...if customer has only SPO, then it's not possible to create alias or anything since exchange is not provided...what I'm not sure is if even in this scenario is possible to modify deafault e-mail for an user since the e-mail is the mean to get authenticated in Office 365. What I have also learnr from working with other services is that even if you don't have EXO license assigned, a kind of "fake" inbox is created for your user (I have seen this with Teams)
- AnonymousFeb 16, 2017
No problem. I have submitted a ticket for it. It is one of those things that I believe was just overlooked or of course a ploy by Microsoft to get a customer to continue their Office 365 journey :). I mean the email is basically blank so its not even copying in the UPN, so thats why they were always able to update it. I am hoping its something with an easy fix on Microsoft's side.