Hi there and thanks for the reply.
I fully understand the issue here and know that i cant see this setting without extending my AD Schema, i also know how to do this etc. and have managed environments in the past that had Exchange running in them (and therefore automatically had their AD Schema updated), but my concern and question, was if anyone else here has done this in an AD to Office 365 environment... this is a relatively/very new scenario and i want to be sure it will run smoothly and not have inadvertent impacts on either end of the sync (our on-premise AD and the Office 365 system).
I fully appreciate that it "should run smoothly" but experience with these things tells me this isnt always the case and so i wish to see if anyone here (within Office 365 circles) has done this type of thing.
I realise i have to do this at some point, but what i don't want to happen is for anything else that pops in to our AD schema after i extend it, to sync, without me knowing and then suddenly things start to break. I know it "shouldn't happen" but, like i say, i might... and in other systems has.
thanks for your help
Jonathan