Hi, Aline 

Please make sure you go through our Outlook Calendar Integration documentation, and check out the video instructions in there.

It can happen that you connected your employee to his/her Outlook Calendar, but the calendar dropdown in the Employee's profile in Amelia is blank and showing "No Data":

This happens only if you copied the wrong credentials from Azure into Amelia.

1. Go to Amelia Settings/Integrations/Outlook Calendar, and verify that the Redirect URI is this: https://yourwebsite.com/wp-admin/ (please note that you have to replace "yourwebsite.com" with your actual website's URL, and make sure to close "wp-admin" with /)

2. Access Azure, go to "Azure Active Directory/App Registrations", and delete the existing App Registration.

3. Click on "New Registration". In the “Who can use this application or access this API?” check the option “Accounts in any organizational directory (Any Azure AD directory – Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)”

4. Below that, under Redirect URI, paste your redirect URI from Amelia: https://yourwebsite.com/wp-admin/ and click on "Register"

5. Copy the "Application (client) ID" and paste it into Amelia Settings/Integrations/Outlook Calendar:

6. On the left-hand side menu, access "Certificates & Secrets” and click on the “New Client Secret”

7. When you add the description ("Amelia" for example), select the expiration to be the longest possible choice (I believe 24 months is currently the longest option), and click on "Add".

8. Copy the "Value" field:

And paste it into Amelia Settings/Integrations/Outlook Calendar:

That should be it. Go to Amelia/Employees, and if the employee is still connected to the non-existing calendar, click on "Sign out of Outlook", delete all cache from your website, and then try again.

-

If you try all of this - and still see same issue, please provide me with your WP-Admin credentials, and your Azure credentials, then I can check everything for you.

Please provide me a temporary WP-admin (administrator) user for your site where this happens, so we could log in and take a look ‘from the inside’ as that’s the most efficient way to see and resolve the issue. 

We do not interfere with any data or anything else except for the plugin (in case that’s a production version of the site), and of course, we do not provide login data to third parties. 

You can write credentials here just check PRIVATE Reply so nobody can see them except us.

Hi, Aline 

I am sorry to dissapoint, but as far as i am aware, any employee that you wish to connect/synchronize with Amelia's integration with Outlook,

that employee has to have a Microsoft account.

But I will check with our 2nd level Team, if they have any kind of a workaround to help us resolve this issue for you.

We will be as quick as possible, and we will report back as soon as they reply.

Thank you

Hi, Aline

My sincerest apologies for the waiting time

I have confirmed this,  and any employee you wish to connect to Outlook, they have to have a Microsoft account.

At this time there Is no workaround, but we will do our best to improve this in the future.

Hi, Aline

We will check if they should have that role in office 365, i honestly don't know,

As far as i am aware they simply just have to have any kind of an Outlook/Microsoft Account, in order to be connected to Outlook in Amelias integration.

I will report back when we check if there is anything else we can advise.

Thank you

Hi, Aline

Can we please check out the Wp-Admin,   with your permission we can try to connect our Test Employee with his account, to see if there might be an error  with the Redirect URI  from your Azure, rather than with the connectivity of the employee's Office 365 accounts.

Please provide me a temporary WP-admin (administrator) user for your site where this happens, so we could log in and take a look ‘from the inside’ as that’s the most efficient way to see and resolve the issue. 

We do not interfere with any data or anything else except for the plugin (in case that’s a production version of the site), and of course, we do not provide login data to third parties. 

You can write credentials here just check PRIVATE Reply so nobody can see them except us.