Hello, I have noticed a similar issue very long time back with vCSA 5.5 on one of older builds, for the permanent fix, I had to update the appliances to latest build released after removing vCSA from AD authentication.
Could you un-join the vCSA from AD, reboot appliance and join it back to AD again I am not certain it may resolve the issue.
Thanks