0 votes

I have recently added our Azure AD domain to managed domains and every user that has both a AD and AAD user account (synced) is showing as "User must change password at next logon"

Is this intentional or a bug? What is the best practise on this?

by (100 points)

1 Answer

0 votes
by (272k points)

Hello Daniel,

The issue appears to be with the initial request made by Adaxes when obtaining account properties. For some reason specific account properties were not returned by Azure AD correctly and the situation you face occurs. We were not able to reproduce the behavior and cannot even tell whether the root cause of the issue is in Adaxes or on the Microsoft side. As of now, we recommend trying to unregister your Azure AD domain in Adaxes and then register it again.

Should the issue persist, please, send us (support@adaxes.com) a copy of the Adaxes Event Log in EVTX format. For information on how to view the log, have a look at the following help article: https://www.adaxes.com/help/ServiceEventLog.

0

The issue persists despite removing and adding the managed domain (AzureAD) again.

I'll create a support ticket.

Related questions

0 votes
0 answers

Here is an example: In Azure the manager shows populated: In Adaxes it shows a blank:

asked Dec 2, 2022 by adaxes_user2 (40 points)
0 votes
1 answer

Aiming to go passwordless, this is a must-have

asked Aug 30, 2023 by JM (20 points)
0 votes
0 answers

Currently, it is not possible to manage Azure AD password policies via Adaxes. Cause Microsoft Graph API currently doesn't support password policy management. The issue is outlined here.

asked Nov 16, 2022 by Adaxes (550 points)
0 votes
1 answer

We are evaluating the product and would like to let users of AD to change password in self service page. We would like to set a 90 days change password policy, ... self service page? Is it achievable (with customization and batch program)? Thanks in advance.

asked Apr 27, 2020 by eric (20 points)
0 votes
1 answer

We are attempting to use the member property in a powershell script for all groups. We get this error message on certain groups that are used as "primary". If we set another ... just shows the single member in the group in which the group is not the primary.

asked Feb 19, 2020 by mark.it.admin (2.3k points)
3,350 questions
3,051 answers
7,791 comments
545,075 users