# Microsoft ## Identification An [[Autonomous System Number|ASN]] identifies an independently routed network. AS15169, AS32934, AS8075, AS16276, and AS14618 map to Google, Meta, Microsoft, OVHcloud, and Amazon network domains. [[Cloudflare|Cloudflare]] can proxy customer DNS through its anycast edge. A [[User Agent|User Agent]] identifies client software in application protocols and is distinct from ASN ownership. ## Notebook evidence - [[Scanned_20260730-1659#PDF page 33 — Cloudflare firewall and autonomous-system numbers|PDF page 33: Cloudflare firewall and autonomous-system numbers]] — The listed ASNs correctly identify major network operators: Google AS15169, Meta/Facebook AS32934, Microsoft AS8075, OVH AS16276, and Amazon AS14618. An ASN identifies a routing domain, not an individual server or application. Cloudflare’s proxied DNS uses its anycast network to answer for customer hostnames and can obscure the origin address from ordinary DNS lookups. The page was building a firewall/attribution table that connected traffic to infrastructure owners. ## Relationships and overlays The source places this record in an evidence cluster with [[Amazon Web Services|Amazon Web Services]] · [[Autonomous System Number|Autonomous System Number]] · [[Cloudflare|Cloudflare]] · [[Google|Google]] · [[Meta Platforms|Meta Platforms]] · [[OVHcloud|OVHcloud]] · [[User Agent|User Agent]]. The occurrence contributes to the notebook's larger model of [[Identity Continuity|identity continuity]], [[Device Sovereignty|device sovereignty]], and [[Continuity Architecture|continuity architecture]]. ## Evidentiary status and open leads Recover firewall rules and timestamps; distinguish ASN-level ownership from hostname-, certificate-, and process-level attribution. ## Source - [[Scanned_20260730-1659|Scanned_20260730-1659]] ## Scanned_20260730-1913 overlay [[Scanned_20260730-1913]] records Microsoft as an email/account authority on PDF pages 3, 35, 37, and 42; as a workflow platform through Power Automate on page 7; and as a collaboration migration from Kaizala/“Alpha Ledger” toward Teams on page 59. The sequence is significant because it links legacy identity, email authentication, automation, and group continuity. It documents research and planned migration, not completion, account control, or a relationship with Microsoft.