All Collections
Cloud Commerce Pro
Message Centre & Emails
CCP - Message Centre: Configuring Exchange Accounts
CCP - Message Centre: Configuring Exchange Accounts

Adding & configuring exchange accounts for the Message Centre in Cloud Commerce Pro

Chelsea Kelly avatar
Written by Chelsea Kelly
Updated over a week ago

Contents:

If at any point when following this guide you cannot proceed further as a result of an issue and you must revert back to the old method temporarily until that issue can be resolved by our support team then please follow the below steps.

  • Inside of the Admin Centre Make your way to Configuration > Message Centre > Exchange Accounts

  • Click Edit and then uncheck the box "*Secure your account with OAuth rather than your password" and enter your password back into the password box then click Save


1. Logging into the Azure

Follow this link provided: http://www.portal.azure.com/

Using your Office 365 Credentials, log into Azure.

2. App Registration

First, Click on Azure Active Directory:

Then, Click on App Registrations from the side panel:

After that, we will now do a new registration by clicking New Registration at the top of the page:

We are now registering an Application.

First, select a name (This can change later and is just for identification)

Secondly, select a support account type.
This will most likely be Single tenant
"Accounts in this organizational directory only (Your Office 365 account - single tenant)"

For Redirect URI, Just leave this blank

Then click Register at the bottom left of the page:

Now take note of the following fields that show on screen:

Application (client) ID & Directory (tenant) ID, as these will be needed later on.

3. Adding Permissions

Click on API permissions:

Click Add a permission:

Then Click on the APIs my organization uses tab that shows up:

Then search for "Office 365 Exchange Online" and click on it:

Then click Application Permissions
Search for "full_access_as_app" and then click the checkbox.

Then confirm by clicking Add Permissions:

Now click the Grant Admin Consent for (Organisation):

You will be prompted with a confirmation if you want to do this, Click Yes:

You should now be able to see a green icon under status to show this has been done correctly:

4. Creating the Secret Token

Click Certificates & Secrets:

Click New Client Secret:

For Description, add Cloud Commerce or some identifier.

Then select a time for this to expire.

(The longer, the better, as after this date a new secret will need to be generated and re-added to CCP)

Then click Add:

Click the copy icon on the Value Column and this will copy the value from the Value Column, this is important to do right after creation as this will be the only time you will be able to access the full Client Secret Value.

Keep a note of this value along with the Application (client) ID & Directory (tenant) ID, as these details will be entered into CCP.

5. Configuring Exchange Accounts inside CCP


Go to Configuration:

Then go to Message Centre ⇾ Exchange Accounts:

Here you will see your accounts, click edit and check the Use OAuth checkbox:

Now insert the following information into the account details:

  1. Account Alias - Add a 1-3 character alias to identify this mail account from any others you might have.

  2. Email - Enter the email address of the account you want to add.

  3. Password - For OAuth, you should leave password blank

  4. EWS URL - This is the web address for your exchange web services. You must use Office 365, so click the “Default Office 365” button to automatically fill this field with the correct URL.

  5. Use OAuth - Check this box

  6. Client ID - Enter the Application (client) ID we got earlier on in this guide

  7. Tenant ID - Enter the Directory (tenant) ID we got earlier on in this guide

  8. Client Secret - Enter the value column we got earlier on in this guide

  9. Status - This will display as either Inactive or Active depending on the situation. If you are having issues with your Message Centre, this is a good thing to check, as an error message like the one shown below might be displayed that will help you identify the cause of the problem.

Example of a correctly configured account:

Did this answer your question?