Insights

Teams booking requests: spot device code phishing before approving

16 November 2026

Spot device code phishing hidden in Teams booking requests. Learn what staff should report and how IT can investigate and restrict risky sign-ins.

Huntress has reported a phishing campaign that used a Microsoft Teams meeting-booking lure to persuade recipients to authorise attacker access. The technique, known as device code phishing, matters to businesses using Microsoft 365 because the sign-in page itself can be genuine.

For Australian business owners and IT leaders, the practical warning is straightforward: an unexpected booking request should not require staff to enter a device authorisation code supplied by the sender. Booking a meeting and granting an application access to an account are different actions.

How device code phishing turns a booking into account access

In its report on the Teams booking lure, Huntress describes attackers disguising an account-authorisation step as part of arranging a meeting. The lesson is not that Teams bookings are inherently unsafe, but that familiar business tasks can conceal unrelated security decisions.

Device code flow is a legitimate authentication method. It lets an application or device begin a sign-in while the user completes authentication in a browser elsewhere. This can be useful for devices with limited input options and some command-line tools.

In a device code phishing attack, the attacker starts that process and gives the resulting code to the victim. The victim is persuaded to enter it on Microsoft's genuine device sign-in page and complete authentication. The application session initiated by the attacker can then receive tokens representing the victim's authorised access.

The attacker does not necessarily need to collect the password on a fake website. Access depends on the application, permissions, account and tenant controls involved; it does not automatically mean complete control of Microsoft 365.

What a meeting request should and should not ask you to do

A legitimate booking service may ask someone to select a time, provide contact details or sign in. Some meetings also use email verification codes. Those steps are not the same as entering a device authorisation code that connects an application or device to your work account.

For an ordinary meeting booking, a request to authorise an unrelated device or application is a reason to stop. Staff should check:

  • The context: Were you expecting this meeting, and does the request match an existing conversation?
  • The action: Are you choosing a meeting time, or being asked to approve account access?
  • The application: Does the sign-in screen identify an application you recognise and intended to use?
  • The code's origin: Did you initiate the device sign-in yourself, or did someone send you a code?
  • The pressure: Is the sender insisting that access must be approved immediately to secure a booking?

Verify unusual requests through a known phone number or an established conversation, not contact details supplied in the suspicious message. Opening Teams or Outlook independently can help check context, but the absence of a calendar entry alone does not prove fraud.

A genuine Microsoft domain and a successful MFA prompt do not establish that the underlying request is safe. In device code phishing, the deception is about what the user is authorising.

Give staff a reporting route that works under pressure

Training should give people a specific action rather than asking them to recognise every attack. A useful instruction is: “If a meeting request asks you to enter a device code you did not initiate, stop and contact IT.”

Make that instruction operational:

  • Provide a clear reporting channel, such as the organisation's configured phishing-report button or service desk.
  • Ask staff to preserve the original message and record when they interacted with it.
  • Ask whether they opened the link, entered a code, signed in, completed MFA or approved access. These are different exposure levels.
  • Tell staff not to repeat the process to collect evidence, and never ask them to send passwords or MFA codes.
  • Provide a phone-based alternative if they cannot safely access their work account.

If authorisation may have been completed, staff should call IT promptly rather than wait for a routine ticket response. Reporting needs to be blame-free: a convincing business workflow can mislead careful people, and early reporting gives responders a better starting point.

Investigate the sign-in and the activity that followed

A device code phishing report should trigger an identity investigation, not just a scan of the employee's laptop. A clean endpoint does not rule out unauthorised cloud access.

Start with the affected account, approximate time and original invitation. Preserve available sign-in and audit evidence promptly, recording time zones so events can be compared accurately.

In Microsoft Entra sign-in logs, examine interactive and non-interactive activity around the event. Review the application and resource, source IP address, location, device details, authentication results and Conditional Access outcome. Where available, inspect the authentication protocol for device code flow and use correlation details to connect related events.

Do not treat an unfamiliar location as conclusive evidence, or a familiar location as proof of safety. VPNs, mobile networks and attacker infrastructure can complicate location signals. Likewise, a record showing MFA was satisfied does not prove the user intended the resulting access.

Then review relevant Microsoft 365 activity for:

  • New inbox rules, forwarding settings or mailbox delegation changes.
  • Unexpected sent messages, deleted messages or mailbox access.
  • Unusual SharePoint or OneDrive downloads and sharing changes.
  • Changes to authentication methods, application permissions or consent grants, where relevant.
  • Similar invitations received by other employees.

Available evidence depends on licensing, audit configuration and retention. Our Microsoft 365 token replay investigation checklist explains why identity events and mailbox changes need to be considered together. The threat hunting checklist also helps define what an investigation should deliver beyond an alert notification.

Contain suspected access without relying on a password reset

If there is credible evidence of unauthorised access, authorised responders should follow the incident response plan. Actions may include temporarily blocking sign-in, revoking sessions and refresh tokens, and resetting credentials where appropriate.

A password reset alone is not a complete response to token-based access. Session revocation can also have propagation delays, and existing access tokens may remain usable until expiry or supported enforcement takes effect. Continue monitoring rather than assuming one administrative action has ended the incident.

Remove malicious mailbox rules or permissions, investigate unexpected authentication-method changes and assess which information was accessed. Preserve evidence before making changes where practical, without delaying urgent containment.

If personal information may have been exposed, assess applicable privacy and notification obligations with appropriate advice. Do not assume that every suspicious sign-in is a reportable breach, or that no downloaded file means no exposure.

Restrict device code flow where the business does not need it

For many businesses, the strongest practical improvement is reducing unnecessary access paths. Microsoft Entra Conditional Access supports targeting device code flow through its authentication flows condition, subject to the required licensing and supported configuration.

Ask your Microsoft 365 administrator to:

  • Identify legitimate device code usage from logs and application owners.
  • Check dependencies, including meeting-room equipment, specialist devices and administrative tools.
  • Design a blocking policy with carefully controlled scope and exceptions.
  • Use report-only mode to assess impact before enforcement.
  • Test legitimate workflows and document any exception's owner and review date.
  • Monitor blocked attempts and verify that the policy applies to intended users and resources.

Emergency-access arrangements need separate planning and monitoring. Broad exclusions can undermine the control, while an untested policy can interrupt legitimate operations.

Blocking legacy authentication is not a substitute: device code flow is a modern OAuth authentication flow. MFA remains important, but it should not be presented as a complete answer to someone being tricked into approving a real sign-in. Combine flow restrictions with appropriate access policies, application governance and staff reporting.

Review your Microsoft 365 cyber security controls

The key question is not simply whether a booking page looks convincing. It is whether the requested action makes sense for arranging a meeting.

Tech Engine can help review your cyber security, investigate identity exposure and configure, secure and manage Microsoft 365. To check your reporting process, sign-in visibility and device code restrictions, call 1300 088 324 or email sales@techengine.au.

Want this applied to your business?

Request an AI Blueprint and we will map the processes worth automating first.

Request an AI Blueprint