05-11-2017 11:51 PM
05-11-2017 11:51 PM
We have an interesting issue in our Skype for Business online environment. Some of our user's missed conversations which are saved to the Missed Conversations folder in our Exchange Online cloud email inboxes have timestamps on the conversations that are incorrect. Specifically the timestamps are all in the Pacific Standard Time (PST) Timezone, whereas our users are mainly in Europe, and have all of their client settings aligned to the local timezone.
We have established that this only affects user who are using either the Skype for Business mobile client for iOS or Android. This is causing end-user confusion.
Wondering how prevant this issue is, and whether other users of Skype for Business Online with Skype for Business Mobile client have experienced this.
05-12-2017 05:15 AM
Thats a strange one. Are both exchange and skype users located in European Azure datacenters?
06-26-2017 12:45 PM - edited 06-26-2017 12:50 PM
Like to revive this thread, as we are seeing the same issue, although our tenant is hosted in the US. The timestamp is exactly 3 hours off (see screenshot).
A quick search indicates this issue has been going on for a while now - https://answers.microsoft.com/en-us/msoffice/forum/msoffice_sfb-mso_other/skype-for-business-online-...
06-26-2017 12:51 PM
My organisation raised a Microsoft Premier Support Ticket about this, and they have confirmed this as an issue in our tenant and shared details on root cuase, and how it will be fixed, and a timeline for the release of the fix.
I'm not going to share more details in this thread, but suggest that you raise a Premier Support Ticket you'll probably get confirmation of the issue and information on the resolution timeframe.
Hope this helps,
07-20-2017 07:34 AM
Some more details on the fix, which requires the following elements.
You need to have all of these components (where relevant) for the fix. If you have no Mac, or Android, or iOS users then that component is not required. For the UCWA fix this is 'server' (tenant) side, so those affected can get an insight from Microsoft as to when their tenant will be updated with the fix.
by rajkumarr on June 04, 2020
by larsstavnas on June 04, 2020
by richardp24550 on June 02, 2020
by Voravut on May 13, 2020
by Sri Todi on April 22, 2020
by Corbin Meek on April 08, 2020
by Hiren_Shah on March 19, 2020