{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreigyah6rpevne6pyr6rbptpiflvaar5vgt7slhwj6nfvsh44vt7l6q",
    "uri": "at://did:plc:zylzg43ub3o2cpkwycctcwhu/app.bsky.feed.post/3mhmtpvsm6uj2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreic5532byibqt2upcy4qx3o44gfbhvfi3fmavdihdpyrdkgdgicedi"
    },
    "mimeType": "image/jpeg",
    "size": 20239
  },
  "path": "/2026/03/21/worth-reading-help-on-the-line-how-a-microsoft-teams-support-call-led-to-compromise/",
  "publishedAt": "2026-03-21T12:31:10.000Z",
  "site": "https://mikemcbride365.com",
  "tags": [
    "Teams",
    "Phishing",
    "Security",
    "Worth Reading – Help on the line: How a Microsoft Teams support call led to compromise",
    "Mike McBride on M365"
  ],
  "textContent": "Microsoft has made efforts to make it clearer when a call is from outside the tenant, and I think that helps. Still, it might now be a good idea to review the proper procedures with your users, and for larger organizations where users may not recognize the support team, an identity verification step might also be worth considering.\n\nThe post Worth Reading – Help on the line: How a Microsoft Teams support call led to compromise first appeared on Mike McBride on M365.",
  "title": "Worth Reading – Help on the line: How a Microsoft Teams support call led to compromise"
}