Click the links below for initial configuration instructions, additional information and technical support:

Initial Configuration

The first time you run the Active Directory Addin, a dialog box appears. Click the O365 Settings tab (Fig.1) and enter the following information:

  • O365 Credentials (Fig.1):

    • User ID: Username of an Office 365 Global Administrator.
    • Password: Password associated with the User ID.

  • Network Settings (Fig.1):
    • Default Location: Default location that will be applied to all new accounts.
    • Account Attribute: Defines how a user in the local Active Directory is matched to a user in Office 365. You can match on Email or on UserPrincipalName depending on whether you are in a federated environment or only running Directory Synchronization. See Understanding the Account Attribute for more details.

      It is crucial that you understand this setting especially when changing names. See Changing a Name with the Active Directory Addin for more details.

  • License Key (Fig.1): If you have an Office 365 account the application will automatically verify your subscription and issue a license key. If you are unable to connect due to firewall or proxy restrictions, please click here to contact Technical Support and obtain a license key file.

    Fig. 1 (Click image for magnified view)

Back to Top

Understanding the Account Attribute

As mentioned earlier, the Account Attribute matches the user in a local Active Directory account to a user in Office 365. Depending on whether you are in a federated environment or running only Directory Synchronization, you can select one of the following match options:

  • Email– This is the mail attribute in Active Directory. If you are running Directory Synchronization, select Email if either of the following conditions are true:
    • The Office 365 Identity matches ONLY the Email attribute.
    • The Office 365 Identity matches BOTH the UserPrincipalName and Email attribute in your local Active Directory.

  • User Principal Name– This is the UserPrincipalName in Active Directory. Select UserPrincipalName if your environment is federated. If you are running only Directory Synchronization, select UserPrincipalName if either of the following conditions are true:
    • The Office 365 Identity matches ONLY the UserPrincipalName.
    • The Office 365 Identity matches BOTH the the UserPrincipalName and Email attribute in your local Active Directory.

Back to Top

Changing a Name with the Active Directory Addin

Special care must be applied when using 365 Command AD Extensions to change a user’s name in the Active Directory. The process varies for Federated vs. Non Federated Users. (Depending on the name and account changes policy of your organization, these scenarios may not apply.)

Changing the Name of a Federated User:

  1. Change the standard name attributes in Active Directory using the standard procedure.
  2. Change the UPN value and SamAccountName in AD using the standard procedure.
  3. Click the O365 Exchange General tab and update the Email Address field to the new value by doing the following:
    1. Click Add as proxy address to add the email address to the list displayed in Additional Email Addresses. Verify it is the Primary Email Address, which is designated by uppercase SMTP. If it is not, select an appropriate value in Additional Email addresses and click Set as Primary.
    2. Click Add as sip to add the new email address as the SIP address. Please note you can only have ONE SIP address PER Office 365 user, so you MUST remove the old SIP address after adding the new value.
  4. Once directory sync completes, the user’s attributes will be updated. The user’s Outlook and Lync will require reconfiguration to the new name value.

Back to Top

Additional Information

Click here to access links to other 365 Command AD Extensions related topics like System Requirements, Installation, Custom Tabs Functionality and Common Usage Examples.

Back to Top

Technical Support

If you encounter any issues or have questions regarding 365 Command AD Extensions, please contact Technical Support.

Back to Top