{"id":31078,"date":"2026-11-17T06:40:23","date_gmt":"2026-11-17T11:40:23","guid":{"rendered":"https:\/\/www.kaspersky.co.uk\/blog\/microsoft-365-outage-phishing\/31078\/"},"modified":"2026-11-17T12:12:16","modified_gmt":"2026-11-17T12:12:16","slug":"microsoft-365-outage-phishing","status":"publish","type":"post","link":"https:\/\/www.kaspersky.co.uk\/blog\/microsoft-365-outage-phishing\/31078\/","title":{"rendered":"A Microsoft outage as a pretext for phishing"},"content":{"rendered":"<p>As you are probably aware, Microsoft experienced a <a href=\"https:\/\/en.wikipedia.org\/wiki\/2026_Microsoft_outage\" target=\"_blank\" rel=\"noopener nofollow\">global outage<\/a> on November 12 that affected Microsoft 365 services, among others. By the morning of November 14, service functionality had been fully restored; however, cybercriminals are still attempting to exploit this news story in their phishing schemes. The email campaign I want to warn you about in this post targets corporate users and is still being detected by our security solutions even today \u2014 November 17.<\/p>\n<h2>How attackers lure victims to a phishing site<\/h2>\n<p>Since Microsoft services went down suddenly on Friday and remained unavailable until the end of the workday, operations at companies that rely on Microsoft 365 as their primary communication tools came to a virtual standstill. Many employees are still unsure whether their services have been restored, and, more importantly, don\u2019t understand the cause of the incident and fear it might happen again. Exploiting this uncertainty and fear, cybercriminals are sending emails with the alarming subject line \u201cOutlook is disconnected after the Microsoft 365 outage\u201d, purportedly on behalf of Microsoft. In these emails, they claim that Outlook, SharePoint, and Exchange Online may not function properly until the recipient reconnects their Office account.<\/p>\n<p><a href=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/86\/2026\/11\/17121205\/microsoft-365-outage-phishing-letter.jpg\"><img loading=\"lazy\" decoding=\"async\" title=\"Phishing letter\" src=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/86\/2026\/11\/17121205\/microsoft-365-outage-phishing-letter.jpg\" width=\"626\" height=\"900\" alt=\"Phishing letter\" class=\"wp-image-56728 aligncenter size-full\"><\/a><\/p>\n<p>The email contains a verification code and a link that the recipient is supposed to follow to \u201creconnect\u201d, which in reality leads to a phishing site.<\/p>\n<h2>What are the attackers trying to achieve?<\/h2>\n<p>The attackers\u2019 website mimics the Microsoft login screen. Of course, there is nowhere to enter the code provided in the email \u2014 a code that no one requested. But they warn in advance that it may have expired, so maybe it might be necessary to generate a replacement. The attackers first ask victim to enter an account name, then offer to send a new code, and finally ask to enter it. However, at every step there\u2019s a \u201cUse your password\u201d link.<\/p>\n<p><a href=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/86\/2026\/11\/17121210\/microsoft-365-outage-phishing-site.jpg\"><img loading=\"lazy\" decoding=\"async\" title=\"Phishing site\" src=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/86\/2026\/11\/17121210\/microsoft-365-outage-phishing-site.jpg\" width=\"1632\" height=\"456\" alt=\"Phishing site\" class=\"wp-image-56729 aligncenter size-full\"><\/a><\/p>\n<p>Apparently, the attackers were trying to create a universal scheme designed to either connect an unauthorized device to a Microsoft 365 account or steal corporate credentials. Particularly telling is the same \u201coutage\u201d message left in the sign-in window, which is supposed to be a standard one rather than one tied to a specific use case.<\/p>\n<p>We\u2019ve already discussed how the device connection scheme \u2014 also known as Device Code Phishing \u2014works on the <a href=\"https:\/\/securelist.ru\/microsoft-device-code-phishing-attack\/116061\/\" target=\"_blank\" rel=\"noopener\">Securelist<\/a> blog. In short, as soon as the email recipient clicks the \u201cSend code\u201d button, the attackers\u2019 scripts begin connecting an unauthorized device to the victim\u2019s account. Microsoft sends a genuine code; the victim enters it on the attackers\u2019 website, and the attackers relay it back to Microsoft. As a result, all data accessible through the Microsoft 365 account becomes available to the attackers.<\/p>\n<p>And if the victim doesn\u2019t want to go through the trouble of sending the code, they can simply hand over their password \u2014 the attackers will find a use for that, too.<\/p>\n<h2>How to stay safe<\/h2>\n<p>First and foremost, we recommend regularly raising employee awareness about modern cyberthreats (for example, using the <a href=\"https:\/\/k-asap.com\/en\/?icid=gb_kdailyplacehold_acq_ona_smm__onl_b2b_kasperskydaily_wpplaceholder____kasap___\" target=\"_blank\" rel=\"noopener\">Kaspersky Automated Security Awareness Platform<\/a>), particularly by explaining exactly how modern phishing schemes work. In addition, it makes sense to explain to employees that if they receive any authorization code they didn\u2019t request or expect, that\u2019s a red flag.<\/p>\n<p>And to ensure that phishing emails cause employees less concern, it\u2019s best to block them at the corporate email gateway level. For this purpose, we offer a specialized solution: <a href=\"https:\/\/www.kaspersky.co.uk\/small-to-medium-business-security\/mail-security-appliance?icid=gb_kdailyplacehold_acq_ona_smm__onl_b2b_kasperskydaily_wpplaceholder_______\" target=\"_blank\" rel=\"noopener\">Kaspersky Secure Mail Gateway<\/a>.<\/p>\n<input type=\"hidden\" class=\"category_for_banner\" data-type=\"posts\" value=\"kesb-trial\"><input type=\"hidden\" class=\"placeholder_for_banner\" data-cat_id=\"kesb-trial\" value=\"24151\">\n","protected":false},"excerpt":{"rendered":"<p>Cybercriminals are attempting to exploit Microsoft\u2019s recent technical issues in their phishing schemes. <\/p>\n","protected":false},"author":2598,"featured_media":31079,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1836,2360,2361],"tags":[76],"class_list":["post-31078","post","type-post","status-publish","format-standard","has-post-thumbnail","category-business","category-enterprise","category-smb","tag-phishing"],"hreflang":[{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/microsoft-365-outage-phishing\/31078\/"},{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/microsoft-365-outage-phishing\/31228\/"},{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/microsoft-365-outage-phishing\/26258\/"},{"hreflang":"ru","url":"https:\/\/www.kaspersky.ru\/blog\/microsoft-365-outage-phishing\/43003\/"},{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/microsoft-365-outage-phishing\/56724\/"},{"hreflang":"ru-kz","url":"https:\/\/blog.kaspersky.kz\/microsoft-365-outage-phishing\/31223\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/microsoft-365-outage-phishing\/36967\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/microsoft-365-outage-phishing\/36638\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/www.kaspersky.co.uk\/blog\/tag\/phishing\/","name":"phishing"},"_links":{"self":[{"href":"https:\/\/www.kaspersky.co.uk\/blog\/wp-json\/wp\/v2\/posts\/31078","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kaspersky.co.uk\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kaspersky.co.uk\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kaspersky.co.uk\/blog\/wp-json\/wp\/v2\/users\/2598"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kaspersky.co.uk\/blog\/wp-json\/wp\/v2\/comments?post=31078"}],"version-history":[{"count":2,"href":"https:\/\/www.kaspersky.co.uk\/blog\/wp-json\/wp\/v2\/posts\/31078\/revisions"}],"predecessor-version":[{"id":31083,"href":"https:\/\/www.kaspersky.co.uk\/blog\/wp-json\/wp\/v2\/posts\/31078\/revisions\/31083"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaspersky.co.uk\/blog\/wp-json\/wp\/v2\/media\/31079"}],"wp:attachment":[{"href":"https:\/\/www.kaspersky.co.uk\/blog\/wp-json\/wp\/v2\/media?parent=31078"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaspersky.co.uk\/blog\/wp-json\/wp\/v2\/categories?post=31078"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaspersky.co.uk\/blog\/wp-json\/wp\/v2\/tags?post=31078"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}