Why is the Teams option unresponsive when creating phishing simulations?
The Teams option in Microsoft Defender phishing simulations fails to respond or select when administrators try to set up a payload. This prevents users from configuring and testing Teams-based phishing campaigns.
What people tried
Every workaround mentioned in the threads below. We haven’t tested any of them — and nobody here is claiming they worked.
- 1Using open source tools like GoPhish combined with MailHog
- 2Building landing pages from scratch
- 3Using GoPhish's built-in templates
- 4Purchasing a single Defender license to use Microsoft's built-in Attack Simulation Training
In their words
Unedited, grouped by where they were said, most upvoted first within each place, each linked to the thread it came from.
“My biggest challenge right now is creating landing pages.”source ↗
“The most frustrating part is that whenever I search for information about creating these pages or ask AI tools about it, the request often gets interpreted as an attempt to conduct malicious phishing”source ↗
“Been trying to create a teams phishing payload, but the option to click "Teams" is not responding. Microsoft is not of much help when asking them what I need.”source ↗
Where this came up
People with this problem also raised
- 4Why does IT send fake phishing emails that stress us out?
- 3How to tell if a BEC attack was caught automatically or by a human
- 2How to protect a home network from AI cyber threats
- 3Automated notification emails only show IDs instead of client names
- 2Why am I getting WhatsApp scams with my real travel booking details?
- 7Getting weird scam letters or emails from banks I don't use