Microsoft Azure vs Hikube — Direktvergleich

Interaktive Fassung: https://comparison.cloud/vergleich/azure-vs-hikube

Vendor-neutraler Direktvergleich von Microsoft Azure und Hikube: Services, Rechenzentren, Kosten und Souveränität — datenbasiert auf comparison.cloud.

Management Summary (Stand 2026-10)

Microsoft Azure positioniert sich als technologisch führender Hyperscaler mit einem breiten Portfolio aus über 200 Services, das insbesondere in den Bereichen KI, Big Data und Microsoft-Integration Spitzenwerte aufweist. Im direkten Vergleich steht Hikube, ein Schweizer Anbieter, der durch ein architektonisch integriertes 3-AZ-Design über Genf, Gland und Luzern eine hohe operative Resilienz und technologische Souveränität bietet. Während Azure mit einem SEAL-Score von 4,4/10 und einem Preis-Score von 4/10 punktet, liegt der Fokus von Hikube auf Unabhängigkeit (SEAL 6,9/10) und Kosteneffizienz bei GPU-Workloads (Cost Rating 6,4/10). Unternehmen mit starkem Microsoft-Stack und globalem Anspruch finden in Azure die passende Plattform, während Schweizer Organisationen und regulierte Mittelständler, die auf lokale Betriebsführung und geringen Lock-in setzen, bei Hikube besser aufgehoben sind.

Microsoft Azure: Stärken

Microsoft Azure: Zu bedenken

Hikube: Stärken

Hikube: Zu bedenken

Microsoft Azure wählen, wenn:

Hikube wählen, wenn:

Häufige Fragen: Microsoft Azure vs Hikube

Was ist der Unterschied zwischen Microsoft Azure und Hikube?

Microsoft Azure ist ein globaler Hyperscaler mit einem breiten Portfolio von über 200 Services, der stark in KI, Big Data und Microsoft-Integration (je 10/10) investiert ist. Hikube ist ein Schweizer Anbieter mit einem fokussierten Portfolio von über 20 Services, der durch ein integriertes 3-AZ-Design (Hochverfügbarkeit 10/10) und technologische Souveränität (9/10) punktet. Azure bietet maximale globale Reichweite (10/10), während Hikube auf lokale Betriebsführung und geringen Lock-in setzt.

Welcher Anbieter ist souveräner?

Hikube erzielt einen höheren SEAL-Score von 6,9/10 (69%) im Vergleich zu Microsoft Azure mit 4,4/10 (44%). Dies liegt an der operativen Souveränität (8/10 vs. 5/10) und der technologischen Souveränität (9/10 vs. 5/10) von Hikube, die durch den Schweizer Sitz und den Open-Source-Stack geprägt sind. Azure bietet zwar starke technische Schutzmechanismen, aber eine geringere Unabhängigkeit von proprietärer Technologie und US-Jurisdiktion.

Welcher Anbieter ist preislich attraktiver?

Hikube hat ein besseres Gesamt-Cost Rating von 6,4/10 im Vergleich zu Microsoft Azure mit 5,7/10. Besonders bei GPU-Instanzen ist Hikube mit einem Score von 9,7/10 deutlich günstiger als Azure (4,7/10). Bei CPU-Instanzen liegt Hikube ebenfalls vorn (6,2/10 vs. 3,8/10). Allerdings sind die tatsächlichen Kosten stark workload-abhängig, da Azure bei Egress (3,5/10) und bestimmten Managed Services andere TCO-Faktoren aufweist.

Für welche Workloads ist Microsoft Azure besser geeignet?

Microsoft Azure ist besser geeignet für komplexe KI- und Big-Data-Workloads (AI 10/10, Big Data 8/10) sowie für Unternehmen mit starkem Microsoft-Stack (Microsoft 10/10). Es bietet zudem eine umfassende Datenbank- (10/10) und Speicher- (10/10) Auswahl sowie globale Reichweite (10/10) für internationale Betriebsmodelle.

Für welche Workloads ist Hikube besser geeignet?

Hikube ist besser geeignet für Schweizer Organisationen und regulierte Mittelständler, die auf lokale Betriebsführung (Operative Souveränität 8/10) und integrierte Hochverfügbarkeit (10/10) setzen. Es ist eine gute Wahl für GPU-basierte KI-Workloads (Cost Rating GPU 9,7/10) und für Nutzer, die technologische Souveränität (9/10) durch Open-Source-Stacks und geringen Lock-in bevorzugen.

Management Summary

ServiceMicrosoft AzureHikube
Count of Services200+20+
Cost Rating5.7/106.4/10
Saving Plan65%–
Datacenter500+3
Datacenter ModelOwn datacentersColocation
Zone SeparationSeparate buildingsSeparate buildings
Server ProductionCustom design–
Countries341
SEAL Score4.4/10 (44%)6.9/10 (69%)
USPLeading in data analytics, AI, and Kubernetes3 AZ by design: every workload runs active-active across three Swiss datacenters. VM volumes and Kubernetes are replicated by the platform.
RecommendationRecommended for enterprises heavily invested in Microsoft.Recommended for Swiss organisations and regulated mid-sized companies that want built-in HA resilience without designing it themselves.

Sovereign Cloud

ServiceMicrosoft AzureHikube
InterpretationSensitive data should be encrypted by BYOK and Confidential VMs. Use EU-Boundaries to keep data processing in EU.Swiss operator (ownership chain not publicly evidenced); compute and storage run in three Swiss datacenters, transfers abroad only with consent except in security emergencies or legal obligations. The buildings are colocation sites run by third parties, sub-processor locations are not published, and the platform only opened in 2025
SEALSEAL 1SEAL 3
ResidencyUSSwitzerland
Shared ResourcesSovereign Public Cloud (formerly Cloud for Sovereignty)Cloud Instances
Dedicated ResourcesDedicated Host–
Dedicated CloudAzure Local incl. disconnected operationsHikube (on Prem) on Request
EncryptionCloud HSM single-tenant FIPS 140-3 Level 3 HSM clustersVault as a Service (secrets management in the Swiss tenant)
Ownership & controlUltimate parent Microsoft Corporation (Washington State) (incorporated most recently 1993, Nasdaq-listed (MSFT); Investor FAQ)Hidora SA, Petit-Lancy, Switzerland (not EU), CHE-286.910.173 (commercial register GE/Zefix; AG since 2016, capital CHF 144,750 in restricted registered shares)
EU governance & oversightEuropean board 'composed exclusively of European nationals' (corporate blog 29 Apr 2026; oversees Microsoft's European activities)No independent board or advisory body with veto/oversight rights (checked: about, imprint, security & compliance, GTC)
Third-country access riskUS CLOUD Act reach and FISA 702 confirmed by Microsoft (Government Requests Report: 'regardless of where the data is located')Hidora SA, Switzerland (not EU) (ownership chain not publicly evidenced)
Contracting entity & jurisdictionEU services provided by Microsoft Ireland Operations Limited (MIOL; EU datacenters owned or leased by MIOL)Contracting party HIDORA SA, Petit-Lancy; Swiss law, Geneva courts (GTC October 2026 clause 21; CHE-286.910.173; Switzerland (not EU))
Transparency on authority requestsSemi-annual Law Enforcement Requests Report, enterprise cloud (H2 2025: 190 requests, 94 disclosures (45 content), 1 EU/EFTA cross-border customer named)No transparency report on government requests (checked: security & compliance, CLOUD Act guide (2026-06-10, upd. 2026-08-21), resources, blog)
Data residency incl. backups/DREU Data Boundary: Customer Data stored and processed in EU+EFTA (Product Terms; EUDB services, pseudonymised logs included; incl. Switzerland, Norway)Operated from Swiss DCs: Geneva (Plan-les-Ouates), Gland, Lucerne (Hikube service agreement October 2026, clause 3 and Annex A; Switzerland (EU adequacy decision))
Metadata & support data residencyEU Data Boundary covers pseudonymised logs and support data (Learn, 03/2026)Ancillary processing 'may involve subcontractors' (service agreement October 2026 clause 3: anti-DDoS, monitoring, support)
AI services: processing & trainingAzure OpenAI: prompts/outputs not used for training (not shared with OpenAI; Foundry Learn 05/2026)Not applicable: no managed AI service (GPU as a Service only, 6 NVIDIA cards L4–H200 on VMs/node groups; 'no opaque ML PaaS')
Dedicated / segregated environmentAzure Local with disconnected operations: sovereign private cloud (no connection to the Azure public cloud, own hardware; from 2602)Managed Kubernetes control plane dedicated to your cluster (own API server, own etcd, 'shared with nobody'; workers in own tenant)
EU operations & support'Data Guardian' and Production Touch Ledger still rolling out (EU-resident oversight by an EU partner of Microsoft engineer remote access; EU/EFTA; blog)Support by Hidora SA engineers in Geneva (support page 2026-08-23; business days 08:00–18:00 CET, 24×7 infrastructure on-call)
Technical operator lock-outConfidential Computing: hardware-based attested TEEs ('properly configured, Microsoft can't access unencrypted customer data')No confidential computing, no attestation, no HYOK
Disconnected / autonomous operationAzure Local 'disconnected operations' from release 2602 (local control plane: portal, ARM, RBAC, AKS, Key Vault, Policy, ACR; no public-cloud connectivity)Control plane operated exclusively in Switzerland (guide 2026-07-15, upd. 2026-09-07: Geneva, Gland and Lucerne; Switzerland (not EU))
Hardware origin & manufacturingOwn server designs with Cerberus hardware root of trust (Project Olympus/OCP on GitHub; NIST 800-193, incl. supply-chain attacks in manufacturing/transit)Only the GPU vendor disclosed: NVIDIA (six cards L4 24G, L40S 48G, A100 80G, RTX 6000 Pro 96G, H100 80G, H200 141G)
Critical software dependenciesAzure hypervisor based on Windows Hyper-V (Learn: 'The Azure hypervisor system is based on Windows Hyper-V.')Partially disclosed: Talos Linux, Cilium, Grafana, VictoriaMetrics (Managed Kubernetes page; VictoriaLogs, cert-manager)
Open-source share & patch authorityCore stack proprietary, open-source share not disclosed (Hyper-V-based hypervisor, ARM, Entra ID)Managed OSS services: OpenBAO, Harbor/Trivy, Grafana, MariaDB (release notes Hikube v1.1.2 (19 Mar 2026); OpenBAO = open-source fork of HashiCorp Vault; RabbitMQ)
Portability & exit'Free egress for customers leaving Azure' (internet) (bandwidth pricing page, credit procedure linked; ExpressRoute/CDN excluded)Reversibility: return 'in a reasonable standard format' (GTC Oct 2026 cl. 9.2; content kept thirty (30) days after termination, then deletion (Annex D cl. 11))
IaC & automationSDK major versions active for at least 12 months (Azure SDK support policy)Public REST/JSON API with OpenAPI 2.0 specification (api.hikube.cloud: VMs, disks, S3 buckets, Kubernetes, VPC, databases, backups, GPU, pricing)
Key sovereignty (BYOK/HYOK, EU HSM)Key Vault Managed HSM: single-tenant, FIPS 140-3 Level 3 (Marvell; BYOK, customer-owned security domain, SKR)Vault as a Service in your Swiss tenant, operated by Hidora ('without US KMS or US Vault'; 'no self-operated HSM')
Certifications & scopeBSI C5:2020 only in the combined SOC 2 Type 2 + CSA STAR report (latest as of 31 March 2025; scope and report only in the Service Trust Portal (login/NDA))ISO 27001 'certified by SQS' per the provider ('the PDF is not online'; attestation, scope annex, validity date on request only)
Public audit evidenceAttestations only in the Service Trust Portal (SOC/ISO/C5, pentest attestations, BCP documents; Entra account and 'NDA for Compliance Materials')Public only: GTC, Hikube contract, privacy notice, status page
EU labels & schemesEU Cloud Code of Conduct: Microsoft Corporation, Level 2 (adherence ID 2021LVL02SCOPE116, last assessment 14 May 2026)No EUCS, Gaia-X, EU Cloud CoC, CISPE, SecNumCloud or Cloud III SEAL (no BSI C3A; Swiss provider (not EU))
Energy & CO₂ transparencyEMEA FY25 PUE 1.16, WUE 0.03 L/kWh; global PUE 1.17 (aggregated by macro region only, own DCs operating ≥12 months)'No PUE published'; 100% renewable power at three sites (infrastructure page; Gland approx. 6.9 g CO₂-eq/kWh, Geneva waste heat up to 4.4 MW (CAD-ZIPLO))
Climate commitmentsClimate Neutral Data Centre Pact signatory (public register; since January 2021, 2024 status 'Certified')No own climate targets (Hidora/Hikube not in the Climate Neutral Data Centre Pact public register)

SEAL Framework

ServiceMicrosoft AzureHikube
Sovereignty Score4.4/10 (44%) EU Data Boundary strong; US jurisdiction limits sovereignty6.9/10 (69%) Swiss operator (ownership chain not publicly evidenced) on an open-source stack in colocation sites; own compliance certification ISO 27001
SOV-1 Strategic (15 %)US parent (Microsoft); EU partner clouds are separate offersFounder-led Swiss company Hidora SA; ownership chain not publicly evidenced; small provider, platform launched in 2025
SOV-2 Legal & Jurisdictional (10 %)Subject to US CLOUD Act & FISA 702Swiss jurisdiction (nFADP), no US parent; EU adequacy decision for Switzerland covers transfers from the EU
SOV-3 Data & AI (10 %)EU Data Boundary completed; strong confidential computingData in three Swiss datacenters; transfers abroad only with consent, except in security emergencies or legal obligations; dedicated GPUs, but no managed AI services
SOV-4 Operational (15 %)EU-based processing & support improved; global ops modelOperated and supported by Swiss-based engineers; buildings (power, cooling, physical access) are run by third-party site operators
SOV-5 Supply Chain (20 %)Global proprietary hardware & software supply chainColocation in three third-party buildings (Stack Infrastructure, backed by US investor IPI Partners, in Geneva and Gland; EWL in Lucerne); hardware sourced on the global market
SOV-6 Technology (15 %)Proprietary platform, notable lock-in; hybrid options existOpen-source, Kubernetes-native stack (Talos Linux, Cilium, OpenBAO, upstream PostgreSQL/MariaDB/Redis/Kafka), S3 API, kubectl/Helm/GitOps, VMDK/QCOW2/ISO import; hypervisor and storage layer not disclosed
SOV-7 Security & Compliance (10 %)BSI C5, ISO 27001, extensive compliance portfolioISO 27001 (operator ISMS, certified by SQS; certificate not published online); no C5, SOC 2, ISO 27017/27018; SLA 99.99% per service published (GPU passthrough and preview services excluded); RPO/RTO not published (Hidora states < 5 min, publication announced)
SOV-8 Environmental (5 %)Carbon negative by 2030 commitment100% renewable power at all three sites, heat reuse in Geneva and Lucerne; no PUE published, ISO 14001/50001 are building certificates

Availability & Locations

ServiceMicrosoft AzureHikube
Presence DACHGermanySwitzerland
Presence EuropeIreland DublinSwitzerland Geneva (Plan-les-Ouates), Gland, Lucerne
Presence North AmericaUSA Virginia, Iowa, Texas, California …–
Presence South AmericaBrazil São Paulo, Rio de Janeiro–
Presence Asia-PacificAustralia Sydney, Melbourne, Canberra–
Presence Middle East & AfricaUAE Dubai, Abu Dhabi–
Availability Zones118 (sum of the zones column of Microsoft's regions list; no official total)3
Multi-AZ✓ verfügbar✓ verfügbar
Regions80+1
Countries341
Continents61
Point of Presence192–
Dedicated Backbone✓ verfügbar–
DDoS✓ verfügbar–

Compute

ServiceMicrosoft AzureHikube
Shared InstanceVirtual Machine 1–1,792 vCPUCloud Instances s1 / u1 / m1, 1vCPU-64vCPU
Dedicated InstanceIsolated VM–
GPU InstanceGPU VMs NC/ND/NV series (H100, H200, GB200/GB300, MI300X)GPU Cloud NVIDIA L4, L40S, A100, RTX 6000 Pro, H100, H200
AI AcceleratorMaia 200 inference accelerator 3 nm, >10 PFLOPS FP4; runs Copilot in production, Foundry by end of 2026; Maia 300 in 2027 (angekündigt)–
Windows ServerVirtual MachineWindows Server licence (incl. 2025, per vCPU)
ServerlessFunctions–
ARM InstanceCobalt Arm64 VMs–
Confidential ComputingConfidential VMs–

Hot Storage

ServiceMicrosoft AzureHikube
Block StorageDisk StorageBlock Storage 3x Replicated NVMe, sync or async across 3 datacenters
AssetsBlob Storage(Hot)Swiss S3 Object Storage (S3 API, WORM)
Managed NetAppNetApp Files–
FileFiles–

Cold Storage

ServiceMicrosoft AzureHikube
VM BackupBackupBackup as a Service
Volume BackupBackup (Disks, Files, Blobs)Velero (Kubernetes add-on)
ArchiveBlob Storage (Archive)–
TapeBlob Storage (Archive)–
Disaster RecoverySite Recovery3-datacenter replication by design (restart on the remaining sites)

Managed Databases

ServiceMicrosoft AzureHikube
MySQLDatabase for MySQLManaged MariaDB
PostGreDatabase for PostgreSQLManaged PostgreSQL (CloudNativePG)
MS SQLAzure SQL Database–
OracleOracle Database@Azure–
Document-OrientedCosmos DBManaged MongoDB
Distributed Wide-ColumnCosmos DB for CassandraManaged ClickHouse
TSDBAzure Data Explorer–
CacheManaged Redis replaces Cache for Redis (retiring Mar/Sep 2028)Managed Redis (Sentinel)
Search EngineAI Search–
Knowledge GraphCosmos DB (Gremlin API)–
VectorAzure AI SearchManaged Qdrant

Network & Security

ServiceMicrosoft AzureHikube
NetworkVirtual NetworkVPC & Subnets
Public IPPublic IPPublic IPv4
GatewayAPI Management–
Load BalancerApplication Gateway Load BalancerManaged Ingress (ingress-nginx, Gateway API)
Public DNSDNS–
Private DNSPrivate DNS–
FirewallWAFPer-VM firewall (allowed inbound ports on the public IP; SSH 22 default, HTTP/HTTPS optional)
Private ConnectivityExpress RouteSite-to-site VPN (on request)
Dedicated ConnectivityExpress Route Direct–
DDoS ProtectionDDoS Protection–
CDNCDN (classic) retires 30 Sep 2027; no new profiles; successor Front Door–

Orchestration

ServiceMicrosoft AzureHikube
Container RegistryAzure Container RegistryRegistry as a Service
OrchestrationAzure Kubernetes Service(AKS)Managed Kubernetes

Virtualization

ServiceMicrosoft AzureHikube
HypervisorHyper-V no direct accessNot disclosed (VM layer operated by Hikube; VMDK / QCOW2 / ISO import)
Instance as a ServiceVirtual MachinesCloud Instances
Managed Virtualization PlatformsAzure VMware Solution–
Bare Metal VirtualizationDedicated Host–
Edge VirtualizationAzure Local–
Workload-specific VirtualizationSAP HANA on Azure–

Management

ServiceMicrosoft AzureHikube
Identity ManagementEntra IDOrganizations & Projects (isolated projects with quotas, members and roles; API keys per project)
IaCResource ManagerHikube public API (REST/JSON, OpenAPI 2.0 spec)
Audit TrailActivity Log–
Mail ServiceCommunication Services–
Command LineAzure CLIkubectl / Helm
MCP ServerAzure MCP Server–
CO2 CalculatorCarbon optimization emissions per resource/subscription in the Azure portal, API, CSV export–
CollaborationMicrosoft 365–

Big Data

ServiceMicrosoft AzureHikube
DashboardsMonitorGrafana (Monitoring Agents add-on, per cluster)
Data StreamingEvent Hubs incl. Kafka endpointManaged Kafka
MessagingService BusManaged RabbitMQ
Business AnalyticsPower BI–
Big Data ProcessingData Lake–
Big Data PlattformData FactoryManaged ClickHouse (OLAP)
Log MonitoringMonitorMonitoring Agents add-on

AI & Machine Learning

ServiceMicrosoft AzureHikube
AssistantAI Bot Service–
TranslationAzure Translator in Foundry Tools 100+ languages; NMT or selectable LLM per request (API 2026-06-06)–
Audio AnalysisAzure Speech in Foundry Tools speech to text, text to speech, speech translation–
Computer VisionAzure Vision in Foundry Tools–
NLPAzure Language in Foundry Tools–
Image GenerationFoundry Models image models: gpt-image-2 / 2.5, FLUX.2-pro, MAI-Image-2.6 (Preview)–
Machine LearningMachine LearningGPU as a Service (dedicated NVIDIA GPUs on VMs or Kubernetes node groups)
AI RouterFoundry model router GPT-5.x/6, Claude, Grok, DeepSeek, Llama; Global + Data Zone (incl. EU)–
Document IntelligenceDocument Intelligence now part of Content Understanding in Foundry Tools; formerly Form Recognizer–
Large Language ModelsFoundry Models 11,000+ models in the catalogue: OpenAI, Anthropic, xAI, DeepSeek, Mistral, Meta, Microsoft–
EmbeddingsFoundry Models–
Serverless InferenceStandard deployments (PAYG) per token; Global: any Azure region, Data Zone: EU/US/APAC, Standard: geography–
Batch InferenceGlobal Batch -50 % vs. Global Standard, 24 h target, max 100k requests / 200 MB per file–
Dedicated InferenceProvisioned Throughput (PTU) Global / Data Zone / Regional; hourly or 1-month / 1-year reservation–
Service TiersPriority processing low-latency PAYG with per-model targets; Global + Data Zone US, not Data Zone EU–
Fine-TuningManaged fine-tuning (SFT/DPO/RFT) GPT-4.1/4o, o4-mini, GPT-5 (RFT, invite); Llama 3.3 70B, Qwen3, gpt-oss–
GuardrailsFoundry Guardrails hate, sexual, violence, self-harm, prompt attacks, protected material; default on–
AI Data PolicyNo training, no sharing prompts/outputs not used for training, not available to OpenAI or other providers–
AI AgentsFoundry Agent Service prompt + voice agents (Preview), Responses API, A2A protocol; publish to Teams/Copilot–
RAG & GroundingFoundry IQ knowledge bases multi-source (Blob, SharePoint, OneLake, web), permission-aware, with citations–
Prompt CachingAzure OpenAI prompt caching automatic from 1,024 tokens; reads discounted; PTU: cached input free only before GPT-6–
Evaluation & ObservabilityFoundry evaluations built-in quality, RAG, safety and agent evaluators (e.g. tool call accuracy); custom–
Sovereign / On-Prem AIFoundry Local on Azure Local (Preview) on-prem inference on Arc-enabled Kubernetes; ONNX/vLLM, GPU, disconnected–

LLM Models

ServiceMicrosoft AzureHikube
Claude Fable 5.1 (Anthropic · proprietary)✓ verfügbar · 1M Kontext (Preview; retirement 2027-12-05) (Preview)–
Claude Haiku 5.5 (Anthropic · proprietary)✓ verfügbar · 1M Kontext–
Claude Opus 5 (Anthropic · proprietary)✓ verfügbar · 1M Kontext (Retirement 2027-07-08)–
Claude Opus 5.5 (Anthropic · proprietary)✓ verfügbar · 1M Kontext–
Claude Sonnet 5.5 (Anthropic · proprietary)✓ verfügbar · 1M Kontext–
Command A+ (05-2026) (Cohere · open weights)✓ verfügbar · 128k Kontext (Preview)–
DeepSeek-V4-Flash (DeepSeek · open weights)✓ verfügbar · 1M Kontext (Retirement 2028-02-20; successor DeepSeek-V4-Flash-0731 (Preview))–
DeepSeek-V4-Pro (DeepSeek · open weights)✓ verfügbar · 1M Kontext (Retirement 2028-02-20)–
Llama 3.3 70B Instruct (Meta · open weights)✓ verfügbar · 128k Kontext (Retirement 2027-01-31)–
Llama 4 Maverick 17B 128E Instruct (Meta · open weights)✓ verfügbar · 1M Kontext (Retires 2026-11-19 (no replacement named))–
MAI-Thinking-1 (Microsoft · proprietary)✓ verfügbar · 256k Kontext (Preview)–
Mistral Large 3 (Mistral AI · open weights)✓ verfügbar · 128k Kontext (Preview)–
Mistral Medium 3.5 (Mistral AI · open weights)✓ verfügbar · 128k Kontext (Preview)–
Kimi K2.6 (Moonshot AI · open weights)✓ verfügbar · 262k Kontext (Preview; retirement 2027-04-16) (Preview)–
GPT-4.1 (OpenAI · proprietary)✓ verfügbar · 1M Kontext (Deprecated; retirement 2027-04-14)–
GPT-5.3-Codex (OpenAI · proprietary)✓ verfügbar · 400k Kontext (Retirement 2027-08-24)–
GPT-5.4 (OpenAI · proprietary)✓ verfügbar · 1.1M Kontext (Retirement 2027-09-02)–
GPT-5.5 (OpenAI · proprietary)✓ verfügbar · 1.1M Kontext (Retirement 2027-10-26)–
GPT-5.6 Sol (OpenAI · proprietary)✓ verfügbar · 1.1M Kontext (Retirement 2028-01-11)–
GPT-6 Astra (OpenAI · proprietary)✓ verfügbar · 1.1M Kontext–
GPT-6 Luna (OpenAI · proprietary)✓ verfügbar · 1.1M Kontext–
GPT-6 Sol (OpenAI · proprietary)✓ verfügbar · 1.1M Kontext–
GPT-6.1 Sol (OpenAI · proprietary)✓ verfügbar · 1.1M Kontext–
GPT-6.1 Terra (OpenAI · proprietary)✓ verfügbar · 1.1M Kontext–
gpt-chat-latest (OpenAI · proprietary)✓ verfügbar · 128k Kontext (Preview; version 2026-10-07 retires 2027-05-18) (Preview)–
gpt-oss-20b (OpenAI · open weights)✓ verfügbar · 131k Kontext (Preview)–
gpt-oss-120b (OpenAI · open weights)✓ verfügbar · 131k Kontext (Retirement 2027-09-15) (Preview)–
o3 (OpenAI · proprietary)✓ verfügbar · 200k Kontext (Deprecated; retires 2026-11-19, replacement gpt-5.6-sol)–
Grok 4.7 (xAI · proprietary)✓ verfügbar · 500k Kontext–
Claude Fable 5.2 (Anthropic · proprietary)✓ verfügbar · 1M Kontext (Preview (Hosted on Anthropic infrastructure)) (Preview)–
Mistral Large 4 (Mistral AI · open weights)✓ verfügbar · 1M Kontext (Preview on Azure; no retirement date) (Preview)–
Kimi K2.7 Code (Moonshot AI · open weights)✓ verfügbar · 262k Kontext (Preview; retirement 2027-04-16) (Preview)–
GPT-5.4 mini (OpenAI · proprietary)✓ verfügbar · 400k Kontext (Retirement 2027-09-21)–
GPT-5.6 Luna (OpenAI · proprietary)✓ verfügbar · 1.1M Kontext (Retirement 2028-01-11)–
GPT-5.6 Terra (OpenAI · proprietary)✓ verfügbar · 1.1M Kontext (Retirement 2028-01-11)–

Embedding Models

ServiceMicrosoft AzureHikube
Cohere Embed 3 (Cohere)✓ verfügbar (English / multilingual, 1,024 dim; partner model via Azure Marketplace; retirement 2027-02-15 (successor Embed v5))–
Cohere Embed 4 (Cohere)✓ verfügbar (embed-v-4-0: text + image input, 256–1,536 dim; sold by Azure; retirement 2027-06-01 (successor Embed v5))–
text-embedding-3-large (OpenAI)✓ verfügbar (3,072 dim (reducible), 8,192 tokens; Data Zone EU and regional EU)–
text-embedding-3-small (OpenAI)✓ verfügbar (1,536 dim, 8,192 tokens; Data Zone EU; regional EU only switzerlandnorth)–
text-embedding-ada-002 (OpenAI)✓ verfügbar (1,536 dim, 8,192 tokens)–
Cohere Embed 5 (Cohere)✓ verfügbar (Cohere-embed-v5-Fast (GA) / v5-Pro (Preview): text, image, fused text+image; 256–2,048 dim; sold by Azure)–

Quantum Computing

ServiceMicrosoft AzureHikube
EmulatorProvider simulators/emulators IonQ simulator, Pasqal EMU, Quantinuum emulators; QDK local–
EngineAzure Quantum QPUs from IonQ, Pasqal, Quantinuum, Rigetti–

Compliance & Certificates

ServiceMicrosoft AzureHikube
C5\nGerman cloud security catalogue✓ verfügbar–
ISO 20000\nIT service management system standard✓ verfügbar–
ISO 27001\nInformation security management system✓ verfügbar✓ verfügbar
ISO 27017\nCloud security controls for providers✓ verfügbar–
ISO 27018\nPersonal data protection for cloud✓ verfügbar–
ISO 27701\nPrivacy information management extension✓ verfügbar–
CSA STAR\nCloud Security Alliance assurance registry✓ verfügbar–
SOC 1,2,3\nService organization control audit reports✓ verfügbar–
PCI DSS\nPayment card data security standard✓ verfügbar–
ISO 9001\nQuality management system standard✓ verfügbar–

Cost Indication

ServiceMicrosoft AzureHikube
Rating5.7/106.4/10
CPU vCPU/h3.8/10 0,0364694 €6.2/10 0,0119212 €
GPU H100/h4.7/10 7,8036400 €9.7/10 2,9785142 €
RAM GB/h5.6/10 0,0041052 €3.0/10 0,0119212 €
VMware CPU/h4.1/10 0,2911250 €–
Managed MySQL Ratio1/43.1/10 0,0911600 €4.2/10 0,0744966 €
Block Storage GB/h | 3000 IOPS7.4/10 0,0001118 €5.7/10 0,0002719 €
S3 Storage GB/h5.2/10 0,0000231 €4.0/10 0,0000298 €
Archive Storage GB/h7.6/10 0,0000053 €–
Tape GB/h8.8/10 0,0000021 €–
Kubernetes-Service-Premium Cluster/h5.3/10 0,0860000 €8.5/10 0,0476848 €
Serverless-Request per 1 Mil Requests8.8/10 0,1700000 €–
Serverless-Compute GB-Sec5.6/10 0,0000136 €–
Generative AI-Token Input gpt-oss-120b per 1Mil tokens8.0/10 0,1290000 €–
Generative AI-Token Output gpt-oss-120b per 1Mil tokens5.5/10 0,5160000 €–
Egress per GB3.5/10 0,0748200 €10.0/10 0,0000000 €

Einzelprofile