0 votes

This message is displaying inside the Office 365 properties for every user on this account/domain. Multi-Factor Authentication is disabled on the tenant account and I am able to connect with the account using Azure Active Directory Powershell module on the same servers where Adaxes is installed. I also verified that the account the Adaxes services uses can successfully connect as well. I also enabled tracing of requests sent to Office 365, viewed the log and found no errors there.

I tested deleting the tenant and adding it back as well as creating another account with the same level permissions and replacing it as the tenant and still got the same error message. I do have other domains that are working with O365 without issue on the same servers as well.

by (20 points)

1 Answer

0 votes
by (294k points)

Hello,

Do we understand correctly, that you have multiple instances of Adaxes service sharing common configuration? If that is correct, you need to specify the credentials for each Office 365 tenant manually on each instance. This is required because the credentials are not replicated which is by design. To specify the credentials:

  1. Launch Adaxes Administration Console.
  2. In the Console Tree, expand your service node.
  3. Navigate to Configuration\Cloud Services and select Office 365.
  4. In the Result Pane on the right, right-click the tenant marked in red and then click Edit. image.png
  5. Activate the Admin Account tab and specify the credentials. image.png
  6. Click OK and save the changes.
  7. Repeat steps 2-6 for each instance of Adaxes service you have.

Related questions

0 votes
1 answer

I installed the older version of 64 bit Windows Azure Active Directory Module as referenced here: Could not load file or assembly and the 64-bit version of the Microsoft ... connect via Azure AD Module directly with the credentials, so I have confirmed that.

asked Feb 22, 2017 by rurbaniak (1.5k points)
0 votes
1 answer

I have been searching your site, but could not find a list of access rights needed. --- Morten A. Steien

asked Feb 23, 2021 by Morten A. Steien (300 points)
0 votes
1 answer

We are creating a scheduled task with powershell script to check for group licensing errors in Azure/Entra ID using Graph API but the connection throws an error. `# Connect to Graph ... ($count -le 0) { write-host "No user found with license errors" }`

asked Jan 26 by maarten.vaes (70 points)
0 votes
1 answer

Getting "object reference not set to an instance" when trying to sign into Office 365 Tenant Was working fine before

asked Sep 1, 2021 by davm79 (40 points)
0 votes
1 answer

Does the solution support working with multiple Office 365 tenants in the cloud-only scenario when there is no on-premise AD and all identity is managed via Azure Active Directory?

asked Apr 14, 2021 by Andrew Matveychuk (50 points)
3,588 questions
3,277 answers
8,303 comments
548,086 users