Section 6.2.4, The EmailAddress attribute sync triggers a loopback on the Publisher channel
Section 6.2.5, Not all the synced attributes are supported by the cmdlet
Section 6.2.6, Setting the set-executionPolicy to RemoteSigned in the Powershell
Section 6.2.7, Changing the driver settings for allowing certain operations
The LastName attribute of Office 365 is mapped to the Surname attribute of the Identity Vault. If the value of LastName is removed from Office 365, the Identity Vault does now allow empty field to be synchronized.
The Display Name attribute of Office 365 is mapped to the Full Name attribute of the Identity Vault. The Identity Vault does not allow a Full Name value with more than 64 characters. The Identity Vault sends a SYNTAX_VIOLATION exception.
The First Name attribute of Office 365 is mapped to the Given Name attribute of the Identity Vault. The Identity Vault does not allow a Given Name value with more than 32 characters. The Identity Vault sends a SYNTAX_VIOLATION exception.
This occurs because only the primary e-mail address is received during Office 365 polling. The driver removes any additional e-mail addresses.
For some operations, traces might appear with this message:
Disallowed attribute Sync : <attr>.
It occurs for the attribute that are either irrelevant to the type of group that is being synced or unsupported by the commandlet.
To start the Office 365 driver, change the set-executionPolicy to
in the Powershell. By default, it is set to . If you don’t change the setting, the driver fails to start and displays the following error message:Error Connecting to Office 365. File <file>.psm1 cannot be loaded because the execution of scripts is disabled on this system.
The Office 365 driver does not allow some of the Distribution or Security Group settings for specific groups. For example, it doesn’t allow you to set
to for a Security Group. It doesn’t allow you to set to for some Distribution Groups.