Dear Techies,

In this week’s newsletter, we’re keeping you safe from new phishing techniques that can bypass Microsoft’s MFA security! We’re also discussing a new update for Microsoft Teams meetings, and showing you how to add job titles in Teams. Ready? Let’s go!👇

📊 Your opinion matters!

Which sections were helpful or interesting? Let us know by participating in the poll at the end!

✉️ THIS WEEK’S TOP STORIES

🛡️ Concerns Rise as Tycoon 2FA Phishing Kit bypasses Microsoft MFA Security

A new phishing kit named Tycoon 2FA, which uses a technique called Adversary-in-The-Middle (AiTM), is causing concern in the cybersecurity world.

It was found by the Sekoia Threat Detection & Research (TDR) team in October 2023 and has been active since August 2023.

Sekoia discovered over 1,100 domain names linked to the kit between October 2023 and February 2024.

Tycoon 2FA tricks people into visiting a fake Microsoft login page to steal their login details and bypass Multi-Factor Authentication (MFA).

To avoid Tycoon 2FA, follow these steps:

Check the email sender

  1. Hover over the sender’s name and check the email address. Legitimate emails from Microsoft will typically end with “@microsoft.com.”

  2. To check, copy the email address.

  3. Paste the email address into the search bar and delete the “@” symbol and everything before it. Then hit Enter.

  4. Make sure the “Organization” is “Microsoft Corporation” and that no information is “Redacted.”

Check the links

  1. Don’t click the link or button. Instead, right-click the link or button and select “Copy link” or “Copy link address.”

  2. Paste the link into the search bar and hit Enter.

  3. On urlvoid, make sure there are no “Detections Counts.”

🔐 Teams Update Allows Meeting Organizers to Limit Presenter Permissions

Microsoft is enhancing the security of Microsoft Teams meetings by allowing organizers to control presenter role permissions.

Controlling what presenters can do may be useful in untrusted environments, such as educational settings where students may misuse their presenter privileges.

The rollout is expected to begin in March 2024 for Targeted Release and April 2024 for Standard Release.

Admins can manage these settings using PowerShell commands:

Set-CsTeamsMeetingConfiguration -LimitPresenterRolePermissions $true

Setting this to "$true" limits presenter role permissions, such as the ability to disable mics and cameras, change participant roles, and lower hands.

Set-CsTeamsMeetingConfiguration -LimitPresenterRolePermissions $false

Setting this to “$false” allows full presenter role permissions.

👥 Microsoft and NVIDIA Expand collaboration


Microsoft and NVIDIA are expanding their collaboration to leverage generative AI, cloud computing, and accelerated computing in healthcare and life sciences.

By combining the capabilities of Microsoft Azure with NVIDIA DGX Cloud and the NVIDIA Clara suite, the collaboration aims to accelerate innovation and improve patient care.

Key initiatives include accelerating clinical research and drug discovery, enhancing medical imaging diagnostics, and increasing access to precision medicine.

For more information, click below:

💡 THIS WEEK’S TOP TIP

Did you know that can add job titles for your team members in Microsoft Teams? This allows colleagues to quickly identify each other’s roles. To add a job title, head to https://entra.microsoft.com and sign in as an administrator, then follow the steps below:

  1. In Entra, head to “Identity” in the left menu, which should be open by default.

  2. Under “Identity,” click “Users” > “All Users.”

  3. Select the person you want to give a job title to.

  4. Click “Edit properties.”

  5. Click “Job Information.”

  6. Enter a job title in the “Job title” field.

  7. Head down and click “Save.”

These changes may take several hours to propagate. However, if the user wants to see their job title quickly, they can try clearing their cache:

Clear cache on Windows:

  1. Quit Teams.

  2. Open File Explorer and paste the following into the address bar:
    %userprofile%\appdata\local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams

  3. Delete the contents of the folder.

  4. Restart Teams.

Clear cache on Mac:

  1. Press Command & Space.

  2. Type "terminal" and press Enter.

  3. In Terminal, paste the following and press Enter:
    rm -rf ~/Library/Group Containers/UBF8T346G9.com.microsoft.teams

  4. Paste the following and press Enter:
    rm -rf ~/Library/Containers/com.microsoft.teams2

  5. Restart Teams.

❗️Note: if you need to “Allow” access in Terminal, paste the command again and press Enter.

🌟 THIS WEEK’S TECH DEALS

20% OFF

Soundcore Open-Ear Headphones

Soundcore by Anker V30i Open-Ear Headphones, Ultra-Comfort, Lightweight Design, Snug Fit, Ergonomic Ear Hooks, Robust Bass, 36H Playtime, Bluetooth 5.3, App Control, Clear Calls, Wireless Earbuds.

$39.99 (usually $49.99)

18% OFF

13 in 1 USB C Docking Station

Dual Monitor, Triple Display, 8 USB C/A Ports, Ethernet, Audio - For MacBook, Dell, HP, Lenovo, Surface.

$46.99 (usually $56.99)

41% OFF

Portable FHD Monitor

Portable 15.6'' FHD 1080P Monitor. IPS Screen, USB C HDMI Display for PC, MAC, Phone, Xbox, PS5- A1 GAMUT.

$88.21 (usually $149.99)

🪲 THIS WEEK’S BOTHERSOME BUGS

Azure users this week have reported error 80192EE7 while attempting to configure a device. This may be an issue with the device registration or user management process.

As a diagnostic step, try temporarily disabling WIP policies.

  1. Type “wip” into the search bar at the top and hit Enter.

  2. Select “Microsoft Intune.”

  3. Under Windows Information Protection (WIP) user scope, select “None.”

  4. Click “Save.”

❗️Note: remember to re-enable WIP policies after testing.

If disabling WIP policies resolves the issue, it indicates a conflict between the policies and the device registration process. You should then investigate the specific policies and their impact on device management.

If setting WIP policies to “None” doesn’t resolve the issue, Review the Device Registration Process to ensure that it's configured correctly. Verify that only authorized users have permissions to register devices and that there are no automated processes or scripts inadvertently adding users and owners during device registration.

Also, Check the Device Enrollment Policies configured in your Microsoft 365 admin center. Ensure that policies are properly configured to control device enrollment and user assignments. Check for any misconfigurations or conflicts that may be causing unintended user additions.

WRAPPING UP!

That’s all for this newsletter. Remember to keep your eyes peeled for the first newsletter in April, where we’ll be announcing the winner of our Grammarly Premium competition!

Thanks for reading and see you soon! 👋

Keep Reading

No posts found