The best workaround (that I am aware of) for the time being would be having the affected users confirm the correct appointment timing via webmail. We have found webmail displays the correct timing, and only Outlook appears to be affected. Our development team is investigating further now though and we hope to have updates for you soon.

Per Tim's comment in https://portal.smartertools.com/community/a94536/build-8025-feedback.aspx it seems a fix is in QC. We're hopeful that gets released asap.