Symptoms

The Admin token refresh was run with a different (user-type) account than before (service-type account), resulting in workflow actions and 'modified by' meta-data to reflect this user account.
 

Diagnoses

This behavior is currently expected, but will likely change in future updates.
 

Resolution

To re-associate K2 Appit with the previous (service-type) account:

1. Login as an existing Global admin user and K2 Admin

2. Within the management site > Authentication > OAuth > Tokens

   a. Delete the token WHERE Resource Type = 'Microsoft Online' AND Username= 'current account'

   b. Delete the two other tokens WHERE Resource Type = 'Microsoft Online' AND Username='Kuid'

3. Open a new browser or Incognito browser

4. Login to SharePoint online as your desired account

5. Run the registration wizard

   a. The user will get the consent page

   b. New token will be registered

6. Re-test