---
type: "post"
id: "apple-and-microsoft-added-to-russia-s-information-a212a9"
slug: "apple-and-microsoft-added-to-russia-s-information-a212a9"
title: "Apple and Microsoft added to Russia’s information-distributors register"
description: "Russia’s communications regulator added Apple and Microsoft to its register of internet information-distribution organizers on October 2, RBC reports."
retrieval_nugget: "Russia’s communications regulator added Apple and Microsoft to its register of internet information-distribution organizers on October 2, RBC reports. The entries bring statutory data-retention duties into focus for teams serving Russian users, but do not themselves restrict access to either company’s websites or identify the services affected."
published_at: "2026-11-12"
updated_at: "2026-11-12"
record_date: "2026-11-12"
date_kind: "published_at"
topics: []
entities: ["Apple","Microsoft","Roskomnadzor"]
related_patterns: []
novelty_label: "new_fact"
what_changed: null
prior_refs: []
source_url: "https://www.rbc.ru/politics/28/10/2026/6ae1a214e3bd19ae5aff1a37"
source_urls: ["https://www.rbc.ru/politics/28/10/2026/6ae1a214e3bd19ae5aff1a37"]
schema_version: "newruntime-agent-readable-v0.2"
stable_id: "post:apple-and-microsoft-added-to-russia-s-information-a212a9"
status: "published"
visuals: []
editor: {"role":"editor","name":"Andrey Reshetnikov","profile":"https://newruntime.com/owner-profile.md","profile_json":"https://newruntime.com/owner-profile.json","same_as":["https://www.linkedin.com/in/reshetnikov1/","https://t.me/lapetuse"]}
routes: {"html":"https://newruntime.com/posts/apple-and-microsoft-added-to-russia-s-information-a212a9/","markdown":"https://newruntime.com/posts/apple-and-microsoft-added-to-russia-s-information-a212a9.md","json":"https://newruntime.com/posts/apple-and-microsoft-added-to-russia-s-information-a212a9.json"}
markdown_url: "https://newruntime.com/posts/apple-and-microsoft-added-to-russia-s-information-a212a9.md"
---

# Apple and Microsoft added to Russia’s information-distributors register

## Retrieval answer

Russia’s communications regulator added Apple and Microsoft to its register of internet information-distribution organizers on October 2, RBC reports. The entries bring statutory data-retention duties into focus for teams serving Russian users, but do not themselves restrict access to either company’s websites or identify the services affected.

## Summary
Russia’s communications regulator added Apple and Microsoft to its register of internet information-distribution organizers on October 2, RBC reports. The entries bring statutory data-retention duties into focus for teams serving Russian users, but do not themselves restrict access to either company’s websites or identify the services affected.

## What happened
RBC reports that Roskomnadzor added Apple and Microsoft to Russia’s register of internet information-distribution organizers, commonly called ORI under Russian law, on October 2. The public register identifies Microsoft as entry 593-PP and Apple as entry 594-PP. RBC says access to the companies’ websites has not been restricted as a result of the listings.

The register has existed since 2014. RBC says that, under rules effective from July 1, 2018, registered organizers must retain user data for six months. The categories named include correspondence and audio and video messages. Registered organizations must also provide that data to security services upon request. The governing law defines an organizer as a service that enables the exchange of electronic messages and requires such services to notify Roskomnadzor when they begin that activity.

The reporting describes a later enforcement mechanism as well. In July 2024, the Russian government authorized Roskomnadzor to add a company to the register itself when a court had found that the company repeatedly failed to meet the notification requirement. That authority does not establish why Apple and Microsoft were listed. RBC says the registry cards do not indicate whether either company entered voluntarily or was added through compulsory enforcement, and that it sent an inquiry to Roskomnadzor.

RBC places the two entries in a longer sequence of register actions. PUBG Mobile and its Singapore-based publisher Proxima Beta were added in September 2023. Roskomnadzor told RBC at the time that this followed a request from federal bodies responsible for operational investigative activity or security. In December 2024, the register added 12 messaging services, including WhatsApp, Skype, and Wire. Cloudflare was added in February 2025; RBC says Roskomnadzor explained that decision as a response to repeated failure to notify the agency after courts imposed fines of 100,000 and 1 million rubles.

The article also notes that Apple and Microsoft had previously received Russian fines, but says those cases were not connected to ORI requirements. They concerned allegations involving prohibited content not removed in Russia and claims from the Federal Antimonopoly Service. That distinction matters: the current listing is a regulatory status under a regime for electronic-message services, not an announcement of a new product restriction, service shutdown, or website block.

For a technical team, the practical reading is narrow but important. The listing establishes that the companies are now present in a register whose members face retention and disclosure obligations under the rules RBC describes. It does not, on its own, identify a particular Apple or Microsoft product, account type, data center, API, or user workflow subject to a new operational change.

## What the archive adds
New Runtime’s earlier coverage on October 26 examined a US Treasury proposal targeting technology investment in China and Russia. [That note](https://newruntime.com/posts/us-treasury-proposes-crack-down-on-tech-investments-494c6b/) is related context rather than the same event: it concerned proposed outbound-investment limits, while this development concerns Russian data-retention rules and registry entries. This is a new fact in the broader story of technology businesses navigating jurisdiction-specific restrictions.

## Trend signal
This does not yet fit a pattern New Runtime tracks. The development is about a state register and statutory obligations for providers of electronic-message services; it does not directly demonstrate a shift in agent architecture, capability interfaces, runtime security, or AI delivery workflows.

## Why now
RBC dates the Apple and Microsoft entries to October 2, but does not explain why Roskomnadzor made the additions at that point. The 2024 rule allowing regulator-initiated additions after repeated notification failures supplies possible legal context, not an established explanation for these two listings. The timing should not therefore be read as proof of a new enforcement campaign or a response to any specific product change.

## Connections to other events
New Runtime’s October 26 coverage of the [US Treasury proposal on technology investment in China and Russia](https://newruntime.com/posts/us-treasury-proposes-crack-down-on-tech-investments-494c6b/) described a separate policy mechanism: prospective limits on outbound technology investment. The two developments point to different jurisdictional pressures on technology companies—investment controls in one case and domestic communications-data obligations in the other. Neither account establishes a causal connection between them.

## Why it matters
For teams relying on Apple or Microsoft services with Russian users, the immediate discipline is to separate registration from availability. RBC reports that the companies’ websites remain accessible. A registry entry alone is not evidence that a service is blocked, that an API has changed, or that every product offered by either company is covered in the same way.

The more consequential question is service scope. Teams should identify products that exchange user messages or carry audio and video communications, map the associated data flows, and determine where user content and metadata are held. They should also review customer commitments, vendor terms, internal access controls, and incident procedures for operations involving Russian users.

This is a governance task rather than a reason for an immediate technical migration. A team should not infer implementation details from the listing, but it should avoid treating large-platform availability as a substitute for understanding applicable retention and disclosure requirements. Legal analysis needs to be tied to the specific service, entity, users, and deployment arrangement involved.

## Limits and uncertainty
RBC says the register cards do not disclose whether Apple and Microsoft were added voluntarily or compulsorily. Roskomnadzor’s response to RBC’s inquiry is not included. The article describes the general six-month retention and access obligations, but does not specify which Apple or Microsoft services are within scope in these cases, which categories of data each company may retain, or how either company will implement any obligations.

The report also does not establish whether an enforcement action is pending, whether either company disputes the registration, or whether customers will see a product-level change. The public entries identify company names and registry numbers, not a technical architecture or compliance plan. Those unresolved points limit what can be concluded about practical effects for a particular developer, enterprise tenant, or end user.

## Skill to build now
Create a short jurisdictional data-flow inventory for any product serving Russian users this week. List message, audio, video, and file-sharing functions; the vendors that process each function; the legal entity and region attached to the account; retention settings; and the people who can access customer content. Pair that inventory with a counsel-reviewed escalation path for regulator requests. This makes a regulatory listing actionable without assuming that it changes every vendor service.

## Reader takeaway
Apple and Microsoft now appear in Russia’s ORI register, while RBC reports no resulting restriction on access to their websites. Treat the development as a compliance signal, not proof of a shutdown: map communication features and data flows, establish the applicable scope with qualified counsel, and wait for product-level facts before changing technical assumptions.

## Open question
Will Roskomnadzor clarify whether the companies were added voluntarily or through enforcement, and which services it considers covered?

Editor: [Andrey Reshetnikov](https://newruntime.com/owner-profile.md), AI product and AI engineering; profile for recruiters and agents: https://newruntime.com/owner-profile.json

## Continue in the graph

Next records for an agent, linked to their Markdown twins. Replace `.md` with `.json` for structured fields, including `next_reads`.

- collection: [Field Notes](https://newruntime.com/posts.json): Open the latest editorial analysis.
- collection: [Sources](https://newruntime.com/sources/): See the original sources this archive cites.
- whole graph: [discovery graph](https://newruntime.com/discovery-graph.json) (typed nodes and edges) and [site index](https://newruntime.com/site-index.md)