Unable to set Office 365 properties

Question

We have just installed Adaxes for testing in our environment which has on-premise AD with Office 365 (no on-prem Exchange).

Our use deprovisioning is comprised of two components, the AD account and the O365 mailbox settings. The O365 configuration runs daily at 1am.

When it runs against a new user that has an Office 365 mailbox the task fails with the below error:

The user does have a mailbox in Office 365. When I go into the user properties page of Adaxes I only see the Office 365 section, there are no Exchange properties whatsoever.

Am i doing something wrong, or does Adaxes not operate in a wholly Office 365 environment in this regard?

Comments

Hello Jamie,

This is a known behavior that occurs because mailboxes in Exchange Online are not created instantly. As per our check it can take up to a couple hours. To make sure that the Scheduled Task works as intended, you need to add the If has an Exchange mailbox condition:

---

I have added in the condition and the result is that it does not run against any accounts. To simplify things I ran the task manually and changed the conditions as follows:

This should run against every Office 365 mailbox (over 600). When I look in the results window after leaving it for an hour it is empty - no results, no changes made.

If I use the below condition the script runs and provides an update within 60 seconds:

It is running against 8 accounts, all with mailboxes older than 24hrs (7 mailboxes have existed for over 12 months). The result is 'the recipient has neither a mailbox...'

There does not appear to be a connection between Office 365 and Adaxes where it is identifying that a mailbox exists. It is as if it is looking for an on-prem Exchange server.

This is the first time we have used Adaxes so we may have missed a config somewhere. It has been installed and connected to our AD and Office 365 tenancy only.

---

Hello Jamie,

Did you register your Microsoft 365 tenant in Adaxes? For details on how that can be done, have a look at the following tutorial: https://www.adaxes.com/tutorials_ActiveDirectoryManagement_ManageAndAutomateOffice365.htm#tenant.

---

Hi

I can confirm that the tenant has been registered in Adaxes. The account used has the permissions: User Management Administrator and Exchange Administrator.

You can see the info is being pulled from O365 in the screenshot below. The user is the one I am testing against and getting the mailbox error.

---

Hello Jamie,

What about the Exchange Properties section for the user? Do you see corresponding data in it? Can you modify settings in the section?

---

Hi

There is no Exchange Properties section in the user section. The below screenshot shows the sections available in the user page:

I am at a loss as to why that section is missing.

---

Hello Jamie,

Please, check whether the section is configured to be displayed when viewing users. For details, have a look at the following tutorial (you need to check the View form): https://www.adaxes.com/tutorials_WebInterfaceCustomization_CustomizeFormsForUserCreationAndEditing.htm.

Also, please, try to sign in to the Web Interface with the credentials of the Adaxes service account (specified during Adaxes installation). Is the section still not displayed?

Additionally, try to access and update Exchange properties of a user account via Adaxes Administration Console. Make sure you are signed in with the credentials of the Adaxes service account: https://www.adaxes.com/help/?HowDoI.ManageService.ChangeServiceLogonAccount.html.

---

Hi

I have logged into the web portal as the Adaxes Service account and I still do not see that section. I have checked the web customisation and see this:

I have also logged into the admin console with the same account to access/update the exchange properties. I have the same problem, no Exchange section only Microsoft 365:

---

Hello Jamie,

Thank you for the provided details. Do you have a hybrid Exchange environment or mailboxes are only located in Exchange Online?

For troubleshooting purposes, please, do the following:

1. Enable tracing of requests sent to Exchange servers: https://www.adaxes.com/help/?HowDoI.PerformExchangeTasks.TraceExchangeRequests.html.
2. Create a Custom Command like the following: The command should clear the following properties:
   • adm-O365ExchangeObjectId
   • adm-O365LastKnownAssociatedTenantId
   • adm-O365ExchangeRecipientType
   • adm-O365ExchangeRecipientTypeDetails
3. Execute the Custom Command for a user the issue persists with.
4. Open properties of the user in Adaxes Administration Console.
5. Send us (support[at]adaxes.com) the trace file.

Also, please, send us the user as an export LDIF file. To do so:

1. Launch Adaxes Administration Console.
2. In the Console Tree, expand your service node.
3. Navigate to and right-click the user.
4. In the context menu, navigate to All Tasks and then click Export.
5. In the dialog box that opens, select LDIF and click Next.
6. On the Properties to Export step, clear the Do not export System-Only properties checkbox.
7. Select the Export Adaxes virtual properties checkbox.
8. Click Export.
9. Send the export file to us.

---

Thank you, I have completed the tasks and sent you the two files.

Answer 1

Hello Jamie,

Thank you for the provided details. According to the Exchange trace, you have basic authentication disabled on the computer where Adaxes service runs. To perform operations related to Exchange Online Adaxes uses PowerShell requests and that requires basic authentication to be enabled. This requirement comes from Microsoft and is not related to Adaxes itself. For details, you can check the following Microsoft article: https://docs.microsoft.com/en-us/powershell/exchange/exchange-online-powershell-v2?view=exchange-ps#prerequisites-for-the-exo-v2-module.