Our Adaxes M365 Tenant has been functioning with no issues until a couple days ago. It stopped pulling exchange properties so we tried to re-register it but now we are getting this error: How do we fix this issue?
Hello,
The error occurs because the client secret of the Azure app used to register your Microsoft 365 tenant in Adaxes has expired. To remedy the issue, create a new secret in Azure and specify it for your tenant authentication in Adaxes. Section Create application from the following article should be helpful (you do not need to create a new app, just a new secret for the existing one): https://www.adaxes.com/help/RegisterAdaxesAsAppMicrosoftAzure.
I wish it was that easy but unfortunately it's even giving that error after creating a new client secret:
Are you sure that you copied the value from the Value column? If you took the value from the Secret ID column, it will not work. Also, try restarting Adaxes Administration console before setting the new secret for your tenant.
Thank you, I was trying to use the Secret ID instead of value but now I'm getting this error:
For troubleshooting purposes, please, provide us with a screenshot of the Multi-server environment dialog. For information on how to view it, see https://www.adaxes.com/help/MultiServerEnvironment.
Sure I just blocked out our domain for security reasons:
Thank you for specifying. Microsoft has followed through with its plan to deprecate remote PowerShell in Exchange Online, and it is not available in your tenant anymore. The Adaxes version you are using relies on PowerShell remoting to perform operations in Exchange Online, which means you need to update to a version that uses the Exchange Online Management V3 PowerShell module. You have a choice between updating to Adaxes 2021 Update 7 and upgrading to the latest version.
Upgrade Instructions
Adaxes 2021 Update 7
Download
What's New
Adaxes 2023.2 Update 2
Ah that makes sense, thank you for your help!
*edit - Upgrading to Version 2023.2 has fixed the issue
Hi, I am trying to create a mailbox during a business rule and setting the usageLocation of user to "UK". However this is failing .... If I try to edit user via Adaxes and ... -directory/ Is this a known error? We are running on version 3.16.21515.0 (64 bit)
After installing Microsoft patches on a Windows Server 2008 R2 server hosting Adaxes 2014.1 we are experiencing the following COMException in the Application event log: An error ... IIS 7.5 Any insight into how to fix this issue is greatly appreciated.
Is there any kind of configuration file or registry entry for the Adaxes Client? What port is it using? What port do I need to open on my firewalls?
Trying to configure a custom launcher in Thycotic Secret Server that will launch Adaxes on the user's local machine with the username and password passed as parameters. Has anyone made this work?
The secret has expired. 365 Tenant Application. I went into Azure AD and looked and went to Enterpise Applications but don't see a place to "reset" the client secret.