locked
Extending AD Schema for Exchange for Office 365 RRS feed

  • Question

  • Hi,

    I've been advised from office 365 team to post my question here

    we have migrated over to office 365. and DirSync is linking our on Premises AD on windows 2012 with Office 365, Exchange online(not On premises). Everything is working. 

    We have discovered the limitations with objects that are linked from our active directory to office 365 - i.e. to hide user from GAL can't  be configured from the cloud even if you try to do it using power shell command. then i've advised  to extend the AD Schema to allow DirSync more attributes to push out to the office 365 mailboxes.

    There are some concerns with proceeding in this manner:

    Dose this extending recommended and will not cause future problem.

    since i did not extend our AD schema prior to running DirSync during the Migration. Now Post-Migration we are looking to get assurance that an AD schema extension will not break our Office 365 production environment after dirsync connects the new schema attributes to Office 365, what's the most important attribute will get effected with the null value. 

    If I extend the AD Schema new attributes will sync to the office 365 environment with a null value (by default) - The concern is that these attributes already exist in the office 365 environment and potentially have values apart from the null default value. (Truth or assumption??) When we sync our AD to Office 365 we do not want to overwrite existing values in Office 365 with a null default value from the extended attributes we are adding to our AD.

    Thanks

    Ziad

    Thursday, November 27, 2014 10:03 AM

Answers

  • DirSync doesn't sync attributes that never had a value, never had a value is <> from attributes that are empty. 

    Enfo Zipper
    Christoffer Andersson – Principal Advisor
    http://blogs.chrisse.se - Directory Services Blog

    • Proposed as answer by Frank Shen5 Tuesday, December 2, 2014 1:31 AM
    • Marked as answer by Frank Shen5 Monday, December 8, 2014 1:48 AM
    Thursday, November 27, 2014 12:20 PM
  • You can just extend the schema for exchange (You don't need to configure the attributes), but as always when it comes to sensitive changes to Active Directory.

    1. Perform the operation in a test environment and examine the results.
    2. Take a backup so you can perform a full forest recovery in case of a undesired result. 

    Enfo Zipper
    Christoffer Andersson – Principal Advisor
    http://blogs.chrisse.se - Directory Services Blog

    • Proposed as answer by Frank Shen5 Tuesday, December 2, 2014 1:31 AM
    • Marked as answer by Frank Shen5 Monday, December 8, 2014 1:48 AM
    Thursday, November 27, 2014 12:45 PM

All replies

  • DirSync doesn't sync attributes that never had a value, never had a value is <> from attributes that are empty. 

    Enfo Zipper
    Christoffer Andersson – Principal Advisor
    http://blogs.chrisse.se - Directory Services Blog

    • Proposed as answer by Frank Shen5 Tuesday, December 2, 2014 1:31 AM
    • Marked as answer by Frank Shen5 Monday, December 8, 2014 1:48 AM
    Thursday, November 27, 2014 12:20 PM
  • Hi Chris

    can we consider the AD schema extenuation a safe operation just insert the exchange CD and run the command Setup /PrepareSchema

    or it has some risk, or limitation for future tasks.

    after extending the schema is there is any manual work or attribute update for the users required Thanks

    Ziad

    Thursday, November 27, 2014 12:42 PM
  • You can just extend the schema for exchange (You don't need to configure the attributes), but as always when it comes to sensitive changes to Active Directory.

    1. Perform the operation in a test environment and examine the results.
    2. Take a backup so you can perform a full forest recovery in case of a undesired result. 

    Enfo Zipper
    Christoffer Andersson – Principal Advisor
    http://blogs.chrisse.se - Directory Services Blog

    • Proposed as answer by Frank Shen5 Tuesday, December 2, 2014 1:31 AM
    • Marked as answer by Frank Shen5 Monday, December 8, 2014 1:48 AM
    Thursday, November 27, 2014 12:45 PM
  • Hi,

    This is suggestion for expand Schema when using Office 365 and attributes for Exchange Online:

    http://blog.msvconsultancy.co.uk/2014/06/exchange-2013-schema-upgrade-office-365-error/

    Saturday, March 14, 2015 1:39 AM