Accounts moved between menus are no longer removed by auto-import

Moving an account from Administrator Accounts to End User Accounts wasn't recorded as a manual import. The auto-import engine then evaluated the moved account against the End User import criteria and, if it didn't meet them, removed it — after which it became eligible for automatic import again and could be pulled back into Administrator Accounts.

On tenants with Administrator Account auto-import configured with documentation platform matching (IT Glue, Hudu or Vault) and rotation enablement, the re-imported account could then be matched and have password rotation enabled. So a deliberate correction could be undone: an end user's account mistakenly imported as an administrator account, moved across to put it right, could end up back where it started with its password rotated — and a standard end user has access to neither the documentation platform nor the dashboard to retrieve it.

Moving an account between the two menus now flags it as a manual import, and the auto-import engine leaves it alone. Your move is preserved rather than reversed on the next import run.

If you previously moved an account and later found it back in Administrator Accounts, move it again — it will stay put now. If its password was rotated in the meantime, the current password is in the matched documentation entry or the CyberQP vault.