Forum Discussion
AzureAD Connect Mobile Numbers
I've managed to get myself confused as to how the AD mobile attribute syncs to AzureAD. According to here it's part of the set of attributes that's synchronised, however unlike seemingly everything else it's still allowed to be edited by users or admins through Delve profiles and Admin center.
While I wait to see what happens in my environment, does anyone know what happends, I guess there is no writeback? Is there more than one field ? does the sync data overwrite whats in azureAD ? On change or everytime ?
TIA - Steven
They all seem to be setting the mobilephone one, and yes, it looks like there is no SOA for this attribute. You can edit it directly even in dirsynced scenarios and changes you make in O365 are not overwritten by dirsync. What I remember is that previously this attribute never made it to SPO, so we had to set it there manually. It has always been a special one :)
3 Replies
There are two of those actually, mobile phone as synced from the AD and authenticationphone (settable via the portal). Here's some more detailed explanation: https://docs.microsoft.com/en-us/azure/active-directory/active-directory-passwords-learn-more#what-data-is-used-by-password-reset
Thanks Vasil, so is Delve setting the authentication phone field or mobile? It must be mobile to allow things like outlook to pick up on it surely?
They all seem to be setting the mobilephone one, and yes, it looks like there is no SOA for this attribute. You can edit it directly even in dirsynced scenarios and changes you make in O365 are not overwritten by dirsync. What I remember is that previously this attribute never made it to SPO, so we had to set it there manually. It has always been a special one :)
