Configuring K1000 for Email Connectivity to Office 365

Configuring K1000 appliance for email connectivity to Office 365

This article is reported to work for most customers.  If after using this article to set up email connectivity to Office 365 and you continue to have issues sending and receiving e-mails through the K1000 appliance, we recommend that you contact your Office 365 support to continue to troubleshoot.  

You will not actually configure Office 365 as you would a locally hosted Exchange presence.  Instead you will be configuring SPOP access as explained in this document.  

As an initial setup in Office 365, you will want to ensure there are two email accounts configured for the Kace appliance.  These should be FULL mailbox accounts and not just contacts.  You will be using one email account for network settings, and the second for the helpdesk queue.

For the purposes of this document, an SMTP server account of K1000@BCS036.onmicrosoft.com and a helpdesk account of helpdesk@BCS036.onmicrosoft.com are being referenced.

Kace Appliance Configuration

  1. Go to the Kace Web UI and click K1000 Settings>>Control Panel>>Network Settings
  2. Go to Email Configuration 
  3. Select Enable SMTP Server
  4. Type in smtp.office365.com for Server
  5. Enter the Username (which in our example would be K1000@BCS036.onmicrosoft.com)
  6. Enter the Password you created for that mailbox
  7. Make sure the port is 587
  8. Enable Service Desk POP3 Server
  9. Click Save and the server will reboot
Once the Server reboots then go to Service Desk>>Configuration>>Queues and open the relevant Service Desk Queue.

Within the Queue configuration, the typical settings will be as follows:

  1. Make the Alt Email Address reflect the help email address you previously created on your Office 365 server (in our example it would be helpdesk@BCS036.onmicrosoft.com)
  2. For POP3 Server you will typically use outlook.office365.com
  3. For POP3 User / Password provide the credentials and password you use for the ALT Email in Step 1
  4. For SMTP Server the value is going to be smtp.office365.com and port is 587
NOTE: ALL SMTP/POP addresses MUST be lowercase in the K1000 configuration
NOTE:  There will be occasions when a company using Office 365 will not be using these new default values.  If in doubt then use the following steps to verify the POP3 and SMTP server values.

  • With these steps in place both inbound and outbound mail should flow between the KACE appliance and Office 365.  Since a firewall will typically intervene, you will need to ensure outbound ports 587 and 110 are open from the KACE appliance to the Internet. If you are using SSL on your KACE appliance, POP3 will use port 995.

    One last consideration is whether you want the KACE appliance to accept emails from unknown users, or only from accounts with a matching email address.

    By default the KACE appliance does NOT accept emails from unknown users.  If you wish to change that then go to Queue Configuration  and click on the Accept Email from unknown users check box.


  • Please fix this documentation. Step 4 on both processes refer to an smtp server at Office 365. But in the top Step 4 you have a period that is messing stuff up. - davidgrand 3 years ago
    • Yes, David is correct. This needs fixed. smtp.office.365.com should be smtp.office365.com - joshbeyer8 3 years ago
      • The good news is that the Quest support page has the correct version of this document. I am not sure if IT Ninja is the place to go for authoritative information anymore. It is too bad. IT Ninja used to be good. - davidgrand 3 years ago
  • Sorry for being so late - I wasn't getting notified on these comments. Just corrected it. - Jillsy 3 years ago
This post is locked
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ