While 365 Command always attempts to rollback failed renames, there are times where even the rollback fails, due to inconsistencies with the Power Shell commands being executed.

The process that 365 Command performs to rename federated accounts is described in this support article: Changes are not synchronized to Office 365 after you update the UPN of an on-premises user account to use a different SSO-enabled domain suffix When renaming the federated accounts 365 Command first renames the account to the domain and then the final domain.

It is possible that during this process the account could become stuck in the domain.

The ability to base updates on existing attributes also allows you to change the display name format to "surname, firstname" or to update your username format to "firstname.surname".

A large number of other update scenarios are also supported.

I see a lot of clients who are always asking for updating user status based on their status in Active Directory (AD).

While this functionality does not come with base Maximo, it can be accomplished by using a method that involves adding a custom (meaning not in Maximo by default) attribute to Maximo that pulls the status directly from the field in AD that tracks user status.

A list separator and other certain characters are not allowed in a Share Point user display name when using the MS Project Professional Synchronisation Service with Share Point.

The list separator splits a single resource name into two spate resources on the MS Project resource sheet.

After adding the attribute to Maximo, we can pull the data from AD via the VMMSYNC or LDAPSYNC, and then once we have the information, we can use an escalation to change the user's status based on the information received.

This is intended to be a guideline to follow in order to get the status changed, feel free to use your own methods or steps in modify applications or setting up the different tasks.

I chose to create new instances of the Crontasks to separate out the functions.