Email OTP Verification coming to Teams Meetings

on
Microsoft introducing a new security feature in Teams that will enable enforcements of Email OTP verification for meetings. This new policy, "Anonymous users can join a meeting after verifying," will be available in the Teams Admin Center for all organizations. This feature is available only for meetings created by organizers with a Teams Premium license. The feature is in public preview, but should be rolling out in GA any time soon. The update will roll out automatically. Admins should consider to update the new meeting policy setting from “By e-mail code” to “No” by mid-February if they wish to continue blocking all unverified users (If "No" is the current setting). The policy is described in this article .

Important certificate note to self

on
I've been having issues on a server, where I was supposed to create a secure channel (tls) to a remote server for synchronizing the exchange free/busy information on users. I long suspected it to be certificate related, but I always ended up by turning ssl of (thus running unencrypted). I thought I had it all done right, when importing the root certificate of the CA to the trusted root. But it never solved my problem. 

Thanks to my OCS course, a bright light dawned on me. The reason why the TLS failed could be several. First of all, if you are running the sync service as a service on the server, the certificate must be in the trusted root of the computer, not the administrator (or other account which you are installing as). Second, if the service is set up to "run as" a separate user. It is a good idea to log on as that particular user, and import the certificate as that user. Quite simple when you think about it, but not always intuitive..... :P