Note on importing 3cx extension via AD or Office 365

Background:

Many of our customers want to create extensions through their current office365 or AD domain when switching to 3CX. In this article, we will introduce What do we need to pay attention to when import 3cx extension via AD or Office 365 ? Customers can Refer to this document to determine if they need to create an extension through the AD domain or Office 365.

Note on importing extensions through the AD:

  • Many customers find that their 3CX extension import option does not have the option to import AD. This is because they are using the Linux version. The Linux version does not provide AD import.

  • The 3CX system can only obtain some information for creating an extension. As you can see from the figure below, the parameters that 3CX can read from users in the AD domain are: name, first name, last name, mailbox, extension number, and mobile phone. These parameters correspond to the AD user parameters: display name, first name, last name, email, IP phone, mobile phone.

  • You can find the AD user information from 3CX, but the extension needs to be created manually.After the AD domain deletes the extension, you also need to manually delete the extension in 3CX. When a user deletes in the AD domain, 3CX does not recognize whether the extension here is manually built or AD imported, so users deleted (or disabled) in AD will not affect the extension corresponding to 3CX.
  • The password set for the user in the AD domain is not associated with the extension password, PIN code, etc. in 3CX.
  • After “Check for Changes” is turned on, after the AD field has been modified, the 3CX extension will make corresponding changes after the import. Except for the extension number. If you want to modify the extension number, you can only delete the extension on the 3CX side and re-import.

Note on importing extensions through the Office 365:

  • The Office 365 integration page requires a network to load the page. Some users’ 3CX cannot access the external network and cannot be used.
  • Office 365 integration automatically creates or updates extensions by querying data, but there are a few things to keep in mind:
  1. Please note that you can not specify which extension to use with the 365 integration it will import the the first available extension number starting from 000 or 0000 etc…depending on the digit length.
  2. Also no information is imported other than the names and the email, outbound caller ID is not imported or can be specified to be imported.

Leave a Reply

Your email address will not be published. Required fields are marked *