Your mailbox feels like a service. It is also a physical thing: files on servers, in a specific building, on a specific power grid. In October 2026 that stopped being an abstract point for companies that run their email on Russian providers.
This article sets out what happened, what it means for a business in Armenia, Georgia or the wider region that depends on Yandex or VK business mail, and how little effort a move to Microsoft 365 really takes. We have tried to keep it factual and free of politics: the subject is business continuity.
What happened
According to reporting by BleepingComputer and Meduza, drone strikes damaged three Yandex data centres between 8 and 11 October 2026: Sasovo (Ryazan region), Kaluga and Vladimir. Two were taken fully out of operation and a third was left degraded. Yandex reported no injuries.
The knock-on effects were wide. Outages were reported across Yandex Mail, Disk, Pay, Go and Yandex Cloud, and businesses that depend on Yandex infrastructure were hit as well. Yandex told customers it could not give a reliable restoration timeline and advised them to activate their own disaster-recovery plans. Mail was reported back within days, though not every feature worked, and Yandex restricted some Disk downloads to keep other services running. Replacing the damaged equipment was reported to take around six months, and Yandex has moved customer data and services to data centres run by other Russian providers.
On 18 October a VK data centre in the Leningrad region was also reported targeted. The Record reports that VK confirmed the facility was targeted but said its services were unaffected, while independent monitors recorded a spike in problems. Whether the strike caused them was unclear. At the time of writing we found no reporting on the effect on VK's business mail specifically.
Some of these details come from secondary sources and are still developing. Treat the specifics as a snapshot, not the final word.
Why this matters for a company outside Russia
Even if your offices are nowhere near the strikes, your mailbox may live in a building that is. Three things follow from that:
- A single provider in a single region is a single point of failure. When a data centre goes down, every customer hosted there goes down with it, and you have no say in how fast it comes back.
- Recovery can be long and uncertain. Reported repair times of months, capacity that may not return in full, and no firm word on whether any data was lost are exactly the conditions in which a business cannot plan.
- You depend on someone else's disaster-recovery plan. Yandex itself told customers to activate their own. If you never had one, that advice arrives too late.
The risks worth weighing
None of these is a prediction. They are the scenarios a sensible continuity plan should cover:
- Further outages. Services hit once can be hit again, and a strike on power or network infrastructure nearby can affect a data centre that was never targeted directly.
- Access to your own data. Restrictions on downloads or exports during an incident can leave you unable to retrieve mail and files when you need them most.
- Jurisdiction and lawful access. Services operated from Russia are subject to Russian data-retention and lawful-access rules. Check this with your legal adviser against your own confidentiality and client obligations.
- Payments and sanctions friction. Paying for and supporting a service across borders can get harder without warning.
- Customer and auditor questions. Clients, banks and insurers increasingly ask where business email is hosted and what happens if it fails.
What Microsoft 365 changes
Moving your mail to Exchange Online puts it on a platform built around redundancy and under a contract you control:
- Replicated storage. Exchange Online keeps copies of each mailbox across multiple data centres, so the loss of one building does not lose your mail.
- A financially backed uptime commitment. Microsoft 365 carries a service-level agreement of 99.9% uptime.
- Identity and security built in. Multi-factor sign-in, Conditional Access and Defender protection are part of the same platform — see our conditional access starter set.
- Your tenant, your data. You choose the administrators, and your mail is not tied to a single facility.
- Everything else in one place. Teams, OneDrive, SharePoint and the Office apps sit alongside email under one sign-in.
Plans start with Microsoft 365 Business for small teams, or Exchange Online alone if all you need is email.
How easy is it to move?
Easier than most people expect. A small or mid-size company can usually run it as a short project:
- Inventory (day 1). List mailboxes, aliases, shared mailboxes, distribution lists, the domain and any files on Yandex Disk. This is the whole scoping exercise.
- Set up the tenant (day 1–2). Create the Microsoft 365 tenant, verify your domain, assign licences and switch on multi-factor sign-in.
- Copy the mail (day 2–4). Using an IMAP migration, Exchange Online pulls each mailbox's mail across while your MX records still point at the old provider, so nobody loses anything and nobody has to stop working. You can repeat the sync until cutover to catch new mail.
- Move calendars, contacts and files. Export calendars and contacts and import them into Outlook, and sync Disk files into OneDrive or SharePoint. For larger teams, third-party migration tools can do this in bulk.
- Cut over (a weekend). Lower your DNS TTL a couple of days earlier, switch the MX record to Microsoft 365, update SPF, DKIM and DMARC, and run a final sync. Mail starts flowing to the new mailboxes within minutes to hours.
- Switch people over. Set up Outlook on desktop and phone. Keep the old mailboxes for a few weeks as a safety net, then retire them.
Most of the work is preparation. The visible disruption for staff is typically a single morning of setting up Outlook.
What replaces what
- Yandex Mail / VK business mail → Exchange Online and Outlook
- Yandex Calendar → Outlook calendar
- Yandex Disk → OneDrive and SharePoint
- Yandex Docs → Word, Excel and PowerPoint online
- Yandex Telemost and messenger / VK Teams → Microsoft Teams
Things to know before you start
- IMAP migration moves mail only. Per Microsoft's documentation it does not carry contacts, calendar items or tasks, and each mailbox must exist in Microsoft 365 first. Plan separate steps for those.
- The source side needs preparing. For Yandex 360, IMAP access has to be enabled per user, with app passwords created in the Yandex ID account. For VK or Mail.ru business mail, ask your administrator or check VK's help pages for the IMAP server and whether app passwords are required.
- Start with a pilot. Migrate two or three mailboxes first and confirm the result before committing the rest.
- Move while you can. If your current provider is degraded, a migration can run slower, so the best time to start is before you need it.
- Mind your data. If your mail contains regulated or client-confidential data, agree the retention and deletion plan for the old mailboxes up front.
Where to start
If your business email lives on Yandex or VK today, the first step costs nothing: a short assessment of your mailboxes, domain and files, and a plan with a date on it. We can run that with you in a week and, if you decide to go ahead, handle the migration so your team barely notices. Request a quote or get in touch.