Welcome to the September edition of What’s new in Microsoft Teams – the monthly post where we keep you updated on all the new features and innovations that we have made available in Teams over the la...
Updated Aug 25, 2022
Version 17.0
Blog Post
I have not seen any changes to the compliance recording funtcionality, however there was an incident, https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fadmin.microsoft.com%2Fadminportal%2Fhome%23%2Fservicehealth%3Fmessage%3DTM286587%26shdlinksource%3DIncidentMail&data=04%7C01%7Cjmcgowan%40empowerfcu.com%7C61de9f3a76834f5c744208d98cf0013d%7C3e33ffc159254dc8b1693395ee1a610b%7C0%7C0%7C637695784714515914%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=XXzSTpvPkKuNVV1sxPVkH6hj4BSefaVQHnLZvpoRs7E%3D&reserved=0, which impact Microsoft Teams desktop clients with bots. The compliance recording is a bot function. We were told that this issue would not impact us. An engineer spoke with us Tuesday and indicated that it indeed would impact us. We had received notification that the mentioned TM286587 issue had been resolved and we were going to begin testing to see if the issue was resolved. We no longer were expereinceing the same issue. Our compliance recording policy is not in full effect again as of this morning.