Unable to add a o365 user as an exception to any CloudSOC policy.
0365 securlet was re-activated with the incorrect account name and later was re-activated again to address the incorrect account issue. Because of the incorrect account the users added by the securlet to CloudSOC was only known to the incorrect account.
The CASB code has been corrected so the incorrect account cannot be chosen upon re-activation.
Reactivation with purge of the O365 securlet addresses the problem because the users are added back to CloudSOC with the correct Microsoft account.