I'm not entirely sure if this is possible using a business rule but what I am trying to achieve is have the business rule perform actions when a user account has expired.
Can this be acheived or would a scheduled task be the preferred method?
Hello Richard,
If you want the actions to be executed when account expires, the Business Rule will not work. The thing is that Business Rules can be triggered only by the operations performed via Adaxes. When the account expiration date passes, the account itself does not change. To execute your actions when account has expired, a Scheduled Task should be used. For information on how to schedule tasks in Adaxes, please, have a look at the following tutorial: https://www.adaxes.com/tutorials_AutomatingDailyTasks_ScheduleTasksForActiveDirectoryManagement.htm. To prevent execution of the actions from the first action set on the disabled accounts, you can add the If account is enabled condition. Your task should be like the following:
Thank you, that really cleared up my confusion. I will setup the scheduled task as suggested.
I am trying to trigger processing outside of Active Directory when an account is created based on the source user account that was used. Does Adaxes store the source account anywhere?
I am unsure how to deal with this because of how Adaxes treats one identity account as two different objects, an AD and AzureAD user account, and both has different last logon values. What is a good way to combine the data?
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.
What is the difference between “has expired” and “expires” when referring to conditions on an account.
I need a way of triggering a business rule based on the user (and not the group) being added or removed from a group. The reason I would like this triggered on the user is so ... prefer not to do that. I am checking to see if there is another way to do this.
