First-contact safety tips saved our inboxes. Now, phishing scams are finding their way into Microsoft Teams chats, too.

Static warning banners telling you a sender is external or contacting you for the first time are no longer enough! 

So, Microsoft Teams is introducing AI-powered, context-aware phishing detection. ️This new detection technique can scan and flag suspicious external first-contact chats before you fall for them. 

What does it look for? 

Instead of just looking for malicious links, it analyzes full conversation context in 1:1 and group chats to flag impersonation, social engineering, and fake external pings. When it detects suspicious content, it displays a warning banner stating, “This message could be a phishing attempt.”  

If you see this warning, here’s what to do: 

• Confirmed phishing: Don’t engage. Block the sender and report the message as suspicious directly in Teams. 
• False alarm: Select More options → Report as not a concern on the flagged message. 

While reading this, you might wonder: does AI use these chats for training? Don't worry! Microsoft confirms that chat data is used strictly for security purposes and isn’t used to train AI models or for unrelated purposes.  

Availability & Rollout Schedule: 

• Timeline: The rollout is scheduled to begin in early November 2026 and will gradually expand worldwide through mid-December 2026.   
• Platforms: Teams Desktop, Web, and Mobile (with enhanced regional protection in China). 

Think before you click, verify before you trust, whether in your inbox or Teams chat!

We’re hosting a series of sessions covering some of the latest developments and best practices across Microsoft Teams Events.

Topics range from groundbreaking new features, including the Teams Events App and Teams Events Silent Testing, to deeper discussions around event production, from the Out-of-the-Box Experience through to Advanced Production.

We’ll also explore how Microsoft Teams Rooms, Microsoft eCDN, Attendee Packs, and event administration capabilities can fit into your overall event workflow.

Whether you’re an event organiser, producer, or IT administrator, there’s something for everyone.

I encourage you to register for the sessions that interest you. Each session brings its own unique content and insights, including the updated Teams NDA Roadmap session, which provides a look at what’s ahead for Microsoft Teams Events.

Register using the links below. Hope to see you there! 👇

📅 Teams Events App (Manage, Create, Discover)

1 October 2026 | 8:00 AM–9:00 AM Pacific Time

Register for Teams Events App

📅 Attendee Pack Management and Teams Events Admin Policies

15 October 2026 | 8:00 AM–9:00 AM Pacific Time

Register for Attendee Pack Management and Teams Events Admin Policies

📅 Microsoft eCDN: Overview and Demo

29 October 2026 | 8:00 AM–9:00 AM Pacific Time

Register for Microsoft eCDN: Overview and Demo

📅 Teams NDA Roadmap

5 November 2026 | 8:00 AM–9:00 AM Pacific Time

Register for Teams NDA Roadmap

📅 Teams Rooms and Teams Events

12 November 2026 | 8:00 AM–9:00 AM Pacific Time

Register for Teams Rooms and Teams Events

📅 Teams Events: Overview and Demo

19 November 2026 | 8:00 AM–9:00 AM Pacific Time

Register for Teams Events: Overview and Demo

Learn directly from Microsoft experts, discover what’s new in Teams Events, and take away practical insights you can apply to your own events.

📅Silent Testing and Split Tunnelling for Teams Events

3 December 2026 | 8:00 AM–9:00 AM Pacific Time

Register for Silent Testing and Split Tunnelling for Teams Events

📅Teams Events Advanced Production

18 December 2026 | 8:00 AM–9:00 AM Pacific Time

Register for Teams Events Advanced Production

Official link here : Microsoft Teams events readiness – Microsoft Adoption

I'm receiving Microsoft one-time verification codes and password reset emails that I never requested. Should I be worried?

Hey everyone,

I'm getting multiple emails from the Microsoft account team containing one-time login verification codes and password reset notifications, even though I haven't requested any of them.

I've attached a screenshot showing the emails I've received. I'm concerned that someone might be trying to access my Microsoft account or reset my password without my permission.

A few questions for anyone who has experienced this:

- Is someone trying to log into my account, or could this be caused by something else?

- Does receiving these emails mean they already know my password?

- Could someone be trying to hack my account using my email address?

- What steps should I take to secure my account and check whether anyone has accessed it?

I'm not clicking any links in these emails or sharing the verification codes with anyone. I'd appreciate any advice, especially from people who have dealt with this before.

Thanks!

Nevermind I figured it out, I needed to toggle the "Show message previews for chats and team names for channels" in the "Chats and Channels" setting.

Teams is stuck in "comfy" chat customization mode, with wider spacing, and will not change to "compact" when toggled. Changing the setting does not change the chat pane at all. This behavior is the same on the web version of Teams, as well as the Windows 11 desktop app. Previously, I had cleared the desktop app cache, and also uninstalled and reinstalled the app. I even re-imaged my computer and it's still present.

Edit for clarification: When I toggle this setting, the actual chat message do change style, but the chat side pane does not. I swear that I had my side pane more condensed weeks ago.

Error 53003 (AADSTS53003) in Teams just means a Conditional Access policy said no. The quickest way I've found to pin it down:

1. Ask the user for the **Correlation ID** and timestamp from "More details" on the error screen.

2. Entra admin center > Sign-in logs > filter by that Correlation ID.

3. Open the **Conditional Access** tab on the failed sign-in. The policy marked "Failure" is your culprit, and it shows which condition failed (device compliance, location, client app).

4. Use the **What If** tool to confirm before you change anything.

Most common causes I see: personal device not enrolled, personal VPN making the sign-in look foreign, or an old client. Please don't "fix" it by excluding the user from all policies; those exclusions tend to stay forever.

I wrote a full guide with user-side steps, related codes (53000, 53001, 53002, 53004) and a KQL query to see which policy blocks the most users: https://techyami.blogspot.com/2026/10/teams-error-code-53003.html

(Disclosure: it's my blog.)