Skip to main content
Skip table of contents

Microsoft Exchange Online Setup

It is first needed to set up Microsoft Exchange Online in Microsoft Azure, and then configure it in MyQ.

Microsoft Exchange Online setup in Microsoft Azure

  1. Log in to the Microsoft Azure portal and go to App registrations.

    MS Azure - App registrations
  2. Create a New registration:

    Creating a new registration
  3. Create an Azure application:

    1. Name - The name for this application (this can be changed later). For example, MS Exchange Online. It is important to use the same name as the one used in MyQ under Connections.

    2. Supported account types - Who can use this application or access this API? Select the Accounts in this organizational directory only ({Tenant name} only - Single tenant) option. Multitenant application can also be used if required, depending on the target audience of the application (what account will be used for authorization in MyQ).

    3. Redirect URI (optional) -  The authentication response is returned to this URl after successfully authenticating the user. Select the Public client/native (mobile&desktop) option from the drop-down and fill in as the redirect URI.

    4. Click Register.

      MS Azure - new app registration properties
  4. The new app overview page opens. Copy the Application (client) ID and the Directory (tenant) ID, as they are needed for the connection to MyQ.

    MS Azure - new app overview
  5. On the left-hand menu, click Authentication. In Advanced settings, under Allow public client flows, select Yes next to Enable the following mobile and desktop flows, and then click Save at the top.

    MS Exchange Online authentication settings
  6. On the left-hand menu, click API permissions and add the additional permissions required for the correct functionality:

    1. Microsoft Graph: offline_access - Allows the app to see and update the data you gave it access to, even when you are not currently using the app. This does not give the app any additional permissions.

    2. Microsoft Graph: User.Read - Sign in and read user profile.

    3. Microsoft Graph: IMAP.AccessAsUser.All - Allows the app to read, update, create and delete email in your mailbox. Does not include permission to send mail.

    4. Microsoft Graph: POP.AccessAsUser.All - Allows the app to read, update, create and delete email in your mailbox. Does not include permission to send mail.

    5. Microsoft Graph: SMTP.Send - Allows the app to send emails on your behalf from your mailbox.

API permissions


Microsoft Exchange Online setup in MyQ

  1. Log in to the MyQ web administrator interface, and go to MyQ, Settings, Connections.

  2. Click +Add and select Microsoft Exchange Online.

    Adding MS Exchange Online
  3. In the pop-up window, fill in the required fields:

    Microsoft Exchange Online setup in MyQ
    1. Title - add the name you chose during App registration in MS Azure; for example, MS Exchange Online.

    2. Client ID - the Application (client) ID you copied during the MS Azure setup.

    3. Tenant ID - the Directory (tenant) ID you copied during the MS Azure setup.

  4. Click OK.

  5. After setting up the connection in MyQ, you are requested to confirm a code through the Microsoft website ( The code you need to confirm is shown in the pop-up window, just below the link to the Microsoft website. There is timeout for confirming the code (usually it is 15 minutes).

The email functionality will not work until the confirmation is successfully completed.

This confirmation must be done with the Microsoft account that owns the email box (email address), which is used to connect to the exchange (Sender email in the MyQ, Settings, Network tab).

For example, if you use the sender email “”, then you need to authenticate on the Microsoft website as this user during this step.

Microsoft Exchange Online is now connected to MyQ and is ready to be used in the Network settings tab as an Outgoing SMTP server.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.