Summary

  • Allianz Technology SE operates a global SD-WAN estate covering more than 1,100 offices, with 13 carrier-neutral colocations and roughly 800 sites on internet-access-based transport, according to a dated September 2022 first-party architecture post.
  • The public record documents operations and governance thoroughly — a 2007 Orange Business Services global IP VPN renewal, a 2013 IBM data-centre operations agreement, an active e-tendering procurement portal — but names no supplier for the SD-WAN platform itself.
  • Self-reported professional profiles point to a VMware/VeloCloud underlay and Cisco ACI in the data centres, but these are attributed claims, not company or vendor announcements.
  • A €2 million recoverable-cost figure from billing reconciliation is self-reported and unreconciled; vendor case-study counts do not scale to the estate and must be read as scoped.
  • The gap is the story: where money changes hands, the record goes silent, and the silence itself constrains what any buyer, competitor or auditor can know.

The architecture of Allianz Technology SE's global network is unusually well documented. On 15 September 2022, a post attributed to Daniel Besendorfer of Allianz Technology described the estate plainly: 13 carrier-neutral colocations interconnected into regional SD-WAN networks, more than 1,100 Allianz offices migrated to SD-WAN, roughly 800 of them on a new transport layer that was mainly internet-access-based, all framed as part of the group's CloudFirst infrastructure evolution and justified by cost reduction through virtualisation and automation (LinkedIn). The post names its delivery team — Sankar Ganesh, Fabrizio Salvatore, Norbert Schaar, Stefano Fabbri, Sorin Enache, Eslibia Castano. It names no vendor, no carrier and no integrator.

That asymmetry is not incidental. It is the pattern that runs through the entire public record of this estate.

What is on record

Three dated, third-party transactional records anchor the supplier history of Allianz's network. The oldest is a three-year global IP VPN renewal with Orange Business Services — the successor of Equant, then a France Telecom subsidiary — covering an Asia-Pacific list including Australia, China, Singapore, Indonesia, Malaysia, Japan, South Korea and Taiwan, with Orange's IP VPN platform described as reaching 220 countries and territories and around 300,000 accesses as of 1 October 2007 (iTWire). The article predates the SD-WAN estate entirely; it documents a carrier relationship of a different era.

The second is a 2013 agreement under which IBM would operate and support Allianz's consolidated data centres, part of a consolidation from 140 data centres down to six strategic ones, effective 1 April 2014 (PR Newswire). That agreement is the only dated record of a supplier operating the company's data-centre layer.

The third is governance, not transaction: Allianz's own procurement portal documents an e-tendering framework — process, rules, registration — for suppliers across the group (Allianz SE procurement portal). It tells you how purchasing happens. It tells you nothing about who won.

What self-reports add, and what they cannot carry

Professional profiles fill some of the silence, at the cost of evidentiary weight. A profile attributed to an Allianz Technology project manager describes "Underlay and SD-WAN Transformation based on WMware/Velocloud" [sic] between November 2020 and January 2023, plus coordination of Network Automation for a Cisco ACI implementation and migration (LinkedIn profile). A profile attributed to the global lead for SD-WAN and Data Centre Network services describes strategy and delivery across 1,100+ locations and six strategic data centres, technical and commercial governance including RFQ/RFP processes and high-value contract negotiations, and — most consequentially — a Service Transition of the entire global SD-WAN service from a third-party integrator to an in-house Allianz Technology shared-services model, described as achieved with zero business disruption across 1,100+ sites, in a role dated April 2021 to July 2023 with a team of more than 40 across India and Thailand (LinkedIn profile). The displaced integrator is not named in any source.

A third profile, attributed to an Allianz Services network lead, describes end-to-end delivery for the global SD-WAN estate, SLA and KPI ownership, supplier service reviews, a managed multi-vendor ecosystem of carriers, ISPs and system integrators, an MPLS-to-DIA migration programme framed around bandwidth efficiency and reduced operating cost, and a billing, capacity and inventory reconciliation across vendor, CMDB and finance systems that surfaced approximately €2 million in recoverable cost (LinkedIn profile). That figure is self-reported and unreconciled anywhere in the public record; it is a claim about a person's work, not an audited number about the estate.

A fourth profile adds the procurement-to-delivery bridge: the person now described as Head of Allianz Global Networks from May 2023 previously led Global IT Infrastructure Procurement at Allianz Holding SE from January 2021 to April 2023 — covering cloud, global network, workplace, data centre and security — and before that ran Network Solutions & Services IT Global Sourcing & Procurement at Allianz Technology SE from October 2014 to October 2019, conducting RFP and price/contract negotiations across APAC, CEE, IberoLatam and the Americas (LinkedIn profile). Continuity between procurement authority and delivery leadership is visible at the level of named careers. The platform award that procurement would have produced remains an inference, not a documented fact.

Weakest of all is a third-party copied job posting attributed to Allianz in India that lists "Velocloud SDWAN" and Cisco routing and switching as mandatory primary skills, and describes designing, building and operating the global Velocloud SDWAN solution including legacy-WAN migrations (MNC Jobs India). It is not Allianz-published. It is consistent with the profile claims, and nothing more.

What vendor collateral can and cannot show

Two vendor-side artifacts exist, both scoped. A SoftwareOne case study describes a migration for one Thai Allianz entity, supporting more than 300 containerised applications across a four-site estate, in an Azure-to-AWS context (SoftwareOne). Those counts are subsidiary-scoped and do not reconcile with the estate-wide figures from the 2022 architecture post; publishing them together without that distinction would be the simplest way to mislead. A Source Technology case study describes supplying network engineering, virtualisation, cloud architecture and service management resources to Allianz SE, supporting consolidation of 140 data centres into five strategic ones — five, not the six stated in the IBM release and the Ganesh profile — plus an internal control centre steering delivery from an SI partner, and about 20 hires over two to three years (Source Technology). The five-versus-six discrepancy is unresolved in the public record.

One artifact exists mainly as a control. A 2010 German-language vendor article mentioning "Allianz Cloud-Computing Services" from OBS, Cisco, EMC and VMware is a documented false positive: there, "Allianz" is a common noun, not the insurer (IT Reseller). It proves the contamination risk of name-collision search in this domain, and why every supplier-side claim in this article carries an entity-resolution check.

The shape of the silence

Absence of evidence is not evidence of absence, but it has structure. No SD-WAN award notice, contract value, bidder list or vendor announcement exists in the public record for this estate. Three explanations fit: genuine non-disclosure, jurisdictional exemption from publication requirements, or a search-scope limitation. The record cannot distinguish them. What the record does show is that the same silence holds across every plausible procurement vehicle — direct purchase, reseller, framework call-off or internal build — because none of them produces a public artifact for a private buyer at this scale.

The prior coverage of this estate on btw.media reached the same wall: the insourcing claim lacks independent corroboration, and the displaced integrator is unnamed (btw.media).