Teams updates to watch: malicious link warnings, blocked risky files, and a new private backroom chat

on
Microsoft has announced three Teams updates the past months. Two that strengthen security and one that will improve how organizers coordinate events: Malicious URL Protection, Weaponizable file type protection and Private chat for organizers, co‑organizers, and presenters. Please note that timelines can shift, so treat the dates as guidance rather than guarantees. Malicious URL Protection (Roadmap ID 499893 ) Microsoft has announced link‑scanning in Teams chats and channels that warns senders and recipients about unsafe URLs. The feature reached general availability rollout by the end of November 2025, while the separate change to make it ON by default, originally planned as part of that release, has been postponed to early 2026.  If you don't want to wait for it to be on by default, or feel the need to configure it, you can do so in the Teams admins center: "Teams admin center → Messaging settings → Scan messages for unsafe URLs”. Or you can mange the configuration with Power...

More OCS challenges

on
Ok, So I have the basics up and running, but is it working? Aperantly, yes.
Front end and backend now run without errormessages, and I can chat, call and use livemeeting on all the clients.

I decided not spend to much time on running around, installing applications, so I am using AD Group policies to deploy the applications. Here is a quick rundown of what I did:

Livemeeting:
  • Download software from www.livemeeting.com (Remember to download both client and outlook plugin)
  • Convert exe files to .msi files by running "LMsetup.exe -out c:\temp" (presuming c:\temp exists)
  • Create a GPO for distribution (Assign or publish, Computer or User - It depends on your preference)
  • Create Groups for filtering of the GPO
  • Add objects to the groups
  • Remove "authenticated users" from the filtering, add the desired group.
Attendant:
The attendant setup file I downloaded was already a .msi file, so no conversion was needed. Other than that, just repeat the steps from above.

Office Communicator:
The attendant setup file I downloaded was already a .msi file, so no conversion was needed. Other than that, just repeat the steps from above.