UAE Launches Sovereign Mobility Cloud with Space42 Microsoft Core42

  • Thread Author
Space42’s announcement that it has partnered with Microsoft and Core42 to build what it calls the UAE’s first Sovereign Mobility Cloud marks a pivotal moment in how the Emirates plans to host, govern and accelerate mobility and autonomous systems at scale. The joint offering positions itself as a regulated, high-assurance cloud environment purpose-built for HD mapping, telematics, fleet operations, traffic management and digital twins — bringing hyperscaler innovation into an environment constrained by local data residency, cleared personnel and sovereign controls. This development was reported in the material provided and in contemporaneous press coverage, and it reflects broader trends in the UAE’s strategy to combine national sovereignty with access to advanced cloud AI capabilities.

Background / Overview​

The UAE has been explicit about treating cloud and AI infrastructure as strategic national assets. Over the past two years, government programmes and public‑private partnerships have accelerated deployments of sovereign-oriented cloud platforms that promise both compliance with domestic rules and access to hyperscaler services. The Space42–Microsoft–Core42 mobility initiative follows other sovereign projects in the Emirates that pair Microsoft Azure’s core platform services with locally controlled governance and operations, aiming to reconcile two previously competing aims: access to advanced AI toolchains and local control of sensitive data and operations.
The new Sovereign Mobility Cloud is described as a specialised sovereign public cloud environment for mobility stakeholders — governments, regulators, fleets and mobility-tech suppliers — that require strong assurances on data residency, administrative jurisdiction and operational transparency. Space42 frames the platform as enabling pilot programmes, co‑development with regulators and secure data sharing between public and private actors. Independent media coverage indicates the announcement was timed with industry events in Dubai, highlighting the offering’s role as a national infrastructure play rather than a simple commercial product launch.

What the Sovereign Mobility Cloud aims to deliver​

Core capabilities and target workloads​

The partnership’s public statements and press coverage emphasise a handful of core capabilities:
  • Trusted infrastructure for mobility data and autonomous systems, including compute, storage and networking operating under local legal jurisdiction.
  • High‑definition (HD) mapping and geospatial services that feed navigation, simulation and autonomous perception systems.
  • Telematics and fleet operations platforms designed for large-scale telemetric ingestion, real-time analytics and operational dashboards.
  • Traffic management and digital‑twin environments for city planners and transport agencies to test scenarios and optimise flows.
  • Confidential compute and sovereign governance controls, meant to restrict administrative access, enforce encryption and provide auditable trails for regulators.
These capabilities are pitched at use cases where the combination of high data volumes, low-latency requirements and regulatory sensitivity are existential: autonomous vehicle validation, smart‑city traffic optimisation, national transport analytics and multi‑party data sharing between agencies and regulated firms.

Deployment model and technical architecture (as described)​

The announced model follows the standard sovereign-cloud pattern the UAE has adopted:
  • Local Azure region infrastructure operated under contractual commitments.
  • A sovereignty controls layer (or “Insight”-style governance plane) that enforces policy, key management and auditability.
  • Cleared local engineering teams and managed services to support deployment, compliance and incident response.
  • Options for isolated connectivity and private links to minimise exposure and provide deterministic performance for real‑time workloads.
This architecture is designed so regulated workloads can run inside an environment that meets the UAE’s legal and operational expectations while still consuming Microsoft’s managed platform services (databases, ML platforms, confidential compute primitives and analytics stacks).

How the announcement fits into the UAE’s sovereign-cloud strategy​

A continuation of a known pattern​

The Space42 announcement is consistent with how the UAE approaches strategic technology: pairing global platforms with local operators to achieve both scale and sovereignty. The model has been visible in prior arrangements — including Core42’s sovereign public cloud built on Microsoft Azure — that combine hyperscaler cloud stacks with an added layer of local governance and cleared operations. These collaborations aim to deliver mainstream cloud services while adding contractual and technical guarantees for local regulation.

Why mobility specifically matters​

Mobility and autonomous systems generate uniquely sensitive data: high‑frequency telemetry, sensor feeds (lidar, camera), location traces tied to individuals and businesses, and safety‑critical control signals. That mix of privacy, national security and high availability makes mobility a natural candidate for sovereign models. A sovereign mobility cloud reduces political and legal uncertainties for fleet operators, automakers and urban agencies while enabling them to keep the latency and control they need for production‑grade systems. The National cited Space42’s explicit intention to use the platform for HD mapping, fleet operations and digital twins, underscoring mobility’s practical fit for a sovereign environment.

Strengths and strategic upside​

1. Balancing innovation and regulatory assurance​

The offering explicitly tries to resolve an industry trade‑off: letting organisations access hyperscaler AI and managed services while keeping sensitive mobility data and operations under national controls. This lowers a major barrier to adoption — legal and procurement concerns about cross‑border data flows — for banks, regulators, OEMs and governments that must certify systems and processes. When done properly, it enables faster adoption of advanced analytics, model training, and production ML while reducing compliance friction.

2. Operational readiness for regulated workloads​

The design emphasizes local cleared staff, contractually defined governance controls, and confidential compute — a technical and contractual stack that is attractive to regulated users such as transport authorities and large fleet operators. For safety‑critical systems like autonomous vehicles, that combination of technical controls and local oversight is a practical prerequisite to deployment at scale.

3. Ecosystem and economic benefits​

Sovereign clouds create demand for local data‑centre operations, MLOps talent, systems integrators and a partner ecosystem that can build and operate mobility services. The UAE’s broader initiatives — national skilling, investment in data infrastructure and public procurement for AI-native services — mean such projects can catalyse jobs, exports of geospatial products and domestic innovation. Space42’s prior geospatial and satellite investments position it to supply mapping and imaging data that complement the cloud offering.

Risks, trade‑offs and unanswered questions​

Vendor concentration and lock‑in​

Relying on an integrated hyperscaler + local operator stack concentrates several vectors of dependency:
  • Platform lock‑in (APIs, managed services, proprietary governance layers).
  • Operational lock‑in (cleared staff and bespoke processes).
  • Contractual lock‑in (data processing agreements, exit terms, and the geography of backups).
Procurement teams must demand strong portability, exit and interoperability clauses — technical and contractual — to avoid long‑term leverage by a small number of sellers. Sovereign controls reduce some geopolitical risk but add a different kind of vendor dependency if migration paths are poorly defined.

Cost and efficiency trade‑offs​

Localising compute, storage and high‑performance accelerators (GPUs for model training) can be more expensive than bursting to global hyperscaler regions. For training large generative models or very large-scale simulation workloads, economics still favour global capacity unless local supply is suitably optimised or subsidised. Organisations should model TCO carefully and consider hybrid approaches that keep the most sensitive datasets local while using global regions for episodic, compute‑intensive tasks.

Transparency, governance and public oversight​

Sovereign deployments are technically complex and politically sensitive. When public services are built on closed proprietary governance layers, questions arise about auditability, model explainability and independent oversight. For citizen‑facing mobility services (traffic enforcement, automated penalties, public transit decisions), transparent governance and third‑party audits are essential to sustain public trust. Contractual SLAs alone are insufficient without independent verification mechanisms.

Security and supply‑chain concerns​

Sovereign clouds reduce some geopolitical exposure but cannot eliminate supply‑chain risk — the underlying hardware, firmware, and global dependencies for AI accelerators and networking still create exposure. The 2024 Microsoft–G42 investment and subsequent assurances about hardware sourcing highlight how geopolitically sensitive these partnerships can be; operational assurances must be continually validated through audits and attestations.

Claims that need independent verification​

Several vendor or announcement claims should be treated as marketing until verified by procurement or third‑party attestations:
  • Specific performance guarantees for HD mapping pipelines or real‑time telematics SLAs.
  • Assertions about being the “first” sovereign mobility cloud — market definitions vary and competitors may have overlapping capabilities.
  • Exact numbers of customers, daily interactions or production workloads (unless contractually documented).
These claims should be validated via contractual SLAs, ISO/SOC attestations, and independent performance benchmarks before trusting them for mission‑critical deployments.

Practical guidance for CIOs, transport agencies and mobility providers​

Assessing the Sovereign Mobility Cloud for production use​

  • Map workloads by sensitivity: classify telemetry, mapping data, PII, model artifacts and control planes to decide what must stay in a sovereign zone.
  • Insist on auditable SLAs: require measurable KPIs (latency p95/p99, ingestion throughput, incident response times, and data-export timelines).
  • Verify governance controls: obtain technical descriptions of the sovereignty control plane — access controls, key‑management, logging and attestation mechanisms.
  • Negotiate portability: require data export tools, standardised storage formats and a migration pathway to alternative clouds or on‑premises environments.
  • Run independent benchmarks: commission third‑party performance and compliance tests before moving safety‑critical workloads.

Operational and security best practices​

  • Use layered encryption with keys controlled by the local customer for sensitive data.
  • Implement strong identity and access management with role separation (no single admin can move or export production datasets).
  • Build hybrid resilience with cross‑region encrypted backups (to a pre‑approved, jurisdictional fallback) and clear failover plans for compute or network outages.
  • Operationalise model governance: establish DPIAs, change control for models in production, and continuous monitoring for drift and adversarial manipulation.

Competitive and regional implications​

What this means for hyperscalers, local operators and competitors​

The Space42–Microsoft–Core42 combination illustrates how hyperscalers can be embedded into national strategies without ceding operational control — a model other Gulf and APAC nations are considering. For Microsoft, it is a continuation of efforts to meet sovereignty needs through regional Azure investments and partner models. For local players (Space42, G42, Core42), partnerships with hyperscalers provide access to managed services and toolchains that would be costly to replicate in isolation.

Geopolitical and market dynamics​

Sovereign clouds change procurement dynamics: governments and large regulated industries gain more negotiating leverage by demanding local governance primitives, but they also concentrate technical capacity in a smaller set of large providers. This dynamic increases the importance of competitive procurement, transparent audit mechanisms and government oversight to ensure the long‑term health of the domestic cloud ecosystem.

What remains unconfirmed and should be watched closely​

  • The depth of independent auditing and attestation available to customers and regulators beyond vendor statements.
  • Precise SLA commitments for mission‑critical mobility workloads (e.g., 99.99% availability for telematics feeds).
  • Migration and exit mechanics — how customers can extract their data and models without disruption.
  • The cost profile for large-scale model training inside the sovereign environment vs. hybrid burst models.
Until these are contractually defined and independently validated, procurement teams should treat public claims as indicative rather than definitive.

Conclusion — a strategic but cautious step​

The launch of a Sovereign Mobility Cloud by Space42 in partnership with Microsoft and Core42 is a logical next phase in the UAE’s tactical approach to sovereign infrastructure: marry hyperscaler innovation to local governance and cleared operations. For mobility and autonomous systems — where data sensitivity, safety and regulatory oversight intersect — a purpose‑built sovereign environment can materially lower barriers to production deployment. At the same time, buyers must guard against vendor lock‑in, confirm technical attestations, and insist on transparent governance and migration paths to keep their options open.
The announcement is strategically significant for the UAE — advancing national ambitions in smart mobility, geospatial services and AI-enabled infrastructure — but it is not a procurement endpoint. For CIOs, transport authorities and mobility providers, the next step is pragmatic and contractual: validate the technical claims, demand auditable controls, and model the economic trade‑offs before entrusting safety‑critical or large‑scale systems to any single sovereign stack.
Source: TechAfrica News Space42 and Microsoft Launch UAE’s First Sovereign Mobility Cloud - TechAfrica News
Source: Finimize https://finimize.com/content/uae-rolls-out-its-own-secure-mobility-cloud-with-microsoft/
 
Click to expand...
Space42’s announcement that it will build what it calls the UAE’s first Sovereign Mobility Cloud with Microsoft and Core42 is a strategic move that crystallizes a broader regional trend: combine hyperscaler AI and platform capabilities with locally controlled governance layers to host, operate, and certify safety‑critical mobility and autonomous systems inside national borders.

Background​

The UAE has pursued sovereign‑cloud initiatives for several years, driven by regulatory aims, national security, and a desire to host advanced AI workloads domestically. That pattern—hyperscaler platform + local operator + a sovereignty controls plane—has become the operational model for many Gulf states aiming to accelerate AI and cloud adoption while keeping data and administrative controls under national jurisdiction.
Space42 says the new offering is enabled by Core42’s Sovereign Public Cloud, built on Microsoft Azure, and will act as a purpose‑designed foundation for HD mapping, telematics, fleet operations, traffic management and digital twins—workloads that are both data‑intensive and regulation‑sensitive. The company frames the platform as the environment to run pilots, regulatory sandboxes and commercial rollouts for autonomous mobility.

What the Sovereign Mobility Cloud will deliver​

Core capabilities (as described by the partners)​

  • Trusted sovereign infrastructure: compute, storage and networking physically and contractually anchored in the UAE.
  • HD mapping and geospatial services: hosted pipelines for mapping, change detection, and map tile serving for navigation and simulation.
  • Telematics and fleet operations: high‑throughput ingestion, stream processing and operational dashboards for live fleets.
  • Traffic management and digital twins: city‑scale simulation and scenario testing for planners and operators.
  • Secure multi‑party data sharing: controlled, auditable information flows between government, industry and research participants.
Microsoft’s stated role is to provide the Azure regional foundation, confidential compute and data governance primitives, plus training, technical assistance and co‑investment to grow the ecosystem. Core42 supplies the sovereign controls layer—marketed in various materials as a governance plane that enforces residency, admin separation, and auditable controls—while Space42 will lead mobility application deployment and stakeholder engagement.

Why mobility is a special case​

Mobility and autonomous systems generate a unique mix of data types: high‑frequency telematics, sensor feeds (LiDAR, radar, cameras), continuous location traces, and safety‑critical telemetry. Those datasets raise privacy, safety and national‑security concerns and they often require sub‑second responses or deterministic connectivity for production systems. A sovereign mobility platform aims to remove legal and operational friction that otherwise slows or blocks production deployments.

The strategic fit for Space42, Microsoft and Core42​

For Space42​

Space42 brings operational experience in autonomous mobility through the TXAI service and geospatial capabilities (GIQ), and positions itself as the application and operations lead—running pilots, proving regulatory compliance, and driving adoption across transport agencies and commercial fleets. Space42’s public materials note long operational mileage and passenger counts for its TXAI robotaxi service—figures the company uses to argue operational readiness for production scale.

For Microsoft​

Microsoft extends Azure’s reach into sovereign deployments by supplying platform services and confidential compute, demonstrating how a hyperscaler can be embedded into national strategies without giving up local governance. Microsoft’s public posture has emphasized sovereign cloud whitepapers, joint technical playbooks with Core42, and mechanisms to combine data residency with advanced AI services.

For Core42 (and its G42 lineage)​

Core42 provides the sovereignty control plane and local operational fabric—cleared staff, data center commitments, and contractual guardrails—so that regulators and enterprises get enforceable, auditable assurances. Core42’s model has already been positioned as capable of supporting high‑volume government workloads in the UAE and combines Azure technology with local enforcement controls.

Independent verification of key claims​

Several of the partners’ public claims are verifiable through corporate press materials and independent reporting:
  • Space42’s announcement of the Sovereign Mobility Cloud was published as a company press release on 24 September 2025.
  • Independent regional coverage (The National, Gulf News and others) reported the tie‑up and reiterated the core features of the offering.
  • Microsoft and Core42 have produced whitepapers and statements describing the Core42 Sovereign Public Cloud architecture and how Azure technologies are being used inside sovereign programs. These materials reflect repeated public messaging about confidential compute, regional Azure infrastructure, and a governance plane named Insight.
Space42’s operational metrics for TXAI—notably the figure often quoted in the announcement of nearly 20,000 passenger trips and ~600,000 km of autonomous driving since 2021—appear in Space42’s own releases and are corroborated by multiple company statements and regional media reporting summarizing those figures. Earlier TXAI trial phases in 2021 reported thousands of riders and measured autonomous kilometres in the tens of thousands; Space42’s 2025 materials present the aggregated numbers used in company positioning. Readers and procurement teams should treat operational metrics coming from vendors as important signals but still require contractual guarantees and independent attestation when used to qualify mission‑critical operations.

Strengths: why this matters for CIOs and mobility operators​

  • Regulatory clearance and procurement friction reduced: Sovereign clouds lower a major barrier to adoption by offering legally and operationally aligned environments for regulated industries such as transport, finance and healthcare. This reduces uncertainty for regulators, insurers and OEMs.
  • Operational readiness for safety‑critical workloads: Combining confidential compute, access‑control separation and cleared local engineers makes it easier to meet the audit and safety requirements expected for autonomous systems.
  • Ecosystem and talent development: A sovereign mobility platform creates demand for local MLOps, geospatial mapping, and systems‑integration skills—an economic multiplier that aligns with national digital transformation targets.
  • Faster route to production: By giving regulators and pilots a controlled environment, the platform can speed movement from demonstration projects to commercial rollouts—especially for fleets that need traceable governance and auditable controls.

Key risks, trade‑offs and governance questions​

Despite its strategic upside, the model carries substantive risks:
  • Vendor concentration and lock‑in: A sovereign offering that combines a hyperscaler’s managed services with a proprietary sovereignty layer increases dependency on specific stacks and contractual terms. IT leaders must negotiate clear portability, data export and migration guarantees.
  • Transparency and independent auditability: Sovereign clouds may reduce geopolitical risk, but they can also become opaque systems if audit records, attestation reports and operational controls are not independently verifiable. Public trust—especially for citizen‑impacting services—requires external attestations and third‑party audits.
  • Cost and efficiency for large training jobs: Localizing compute, storage and accelerators (GPUs) can be materially more expensive than using global capacities for episodic, compute‑intensive tasks. Organisations should model TCO carefully and consider hybrid bursting strategies.
  • Supply‑chain and geopolitical exposure: Even sovereign deployments rely on global hardware, firmware and supply chains. Operational assurances must be supported by continuous verification and secure procurement practices.

Practical guidance: what CIOs, transport authorities and fleet operators should demand​

  • Require auditable SLAs that specify measurable KPIs: ingestion throughput, latency (p95/p99), availability and incident response timelines.
  • Insist on independent third‑party attestations: SOC/ISO reports, confidential compute attestation records and regular penetration testing.
  • Contract portability and exit clauses: standardised export formats, encrypted backups, and a defined migration pathway to alternative clouds or on‑premise fallback.
  • Define model governance controls: DPIAs, versioning, drift detection, and model‑change approval workflows for any ML models that influence safety or enforcement actions.
  • Implement strict key management: cryptographic keys for the most sensitive datasets must be under local and customer control, not solely controlled by the platform operator.

Technical architecture patterns to expect​

Sovereign Public Cloud (typical)​

  • Local Azure region(s) hosting platform services.
  • An overlay sovereignty control plane (Insight‑style) enforcing admin separation, KMS policies and auditability.
  • Cleared local operations team providing managed services and incident response.
  • Private connectivity (MPLS/ExpressRoute equivalents) to edge nodes and telematics gateways.

Hybrid/Edge complement​

  • Edge inference nodes (on‑vehicle or roadside) for ultra‑low latency perception and control.
  • Encrypted telemetry streams to the sovereign region for aggregation, mapping updates and model retraining.
  • Cross‑region encrypted backups to pre‑approved jurisdictions as part of resilience planning.

Competitive and regional implications​

This tri‑party effort (Space42 + Core42 + Microsoft) illustrates a replicable template for other governments and regional operators: hyperscaler platforms paired with a local sovereignty operator create an attractive route to production for regulated industries. Expect competing sovereign offerings to emphasize different trade‑offs: deeper national control (private signature clouds), lower cost (shared regional models), or open governance models (third‑party attestation marketplaces). Procurement teams across the Gulf and APAC will watch this model closely.
Geopolitically, alliances between hyperscalers and national champions (including G42/Core42) have already attracted attention and regulatory scrutiny in some markets; transparency and clear legal frameworks will be critical to sustain broader enterprise adoption. Public trust will depend on independent auditability and clear redress mechanisms for citizens affected by mobility systems.

How this fits into the UAE’s broader sovereign cloud strategy​

The Space42 announcement dovetails with an ongoing national effort to create sovereign cloud capacity, accelerate AI adoption, and localize critical digital infrastructure. The UAE has publicly committed multi‑billion‑dirham strategies and procurement programs that favor domestic sovereign offerings for government and regulated sectors. Core42’s earlier public partnerships to handle millions of daily interactions for Abu Dhabi government services are an example of the scale ambitions driving these programs.

What remains to be proven​

  • Exact SLA commitments for safety‑critical telematics and HD mapping pipelines (latency, ingestion throughput) are not yet published in contract form and must be contractually validated.
  • The scope and independence of attestation and audit mechanisms beyond vendor statements need confirmation.
  • Migration and exit mechanics: the practical process of extracting petabytes of map tiles, model artefacts and telematics logs under time constraints remains an open operational and contractual detail.
When vendors frame these programs as “first” or “world‑leading,” procurement teams should ask for primary evidence: signed contracts with public entities, independent benchmarks, and live technical dashboards exposing the KPIs that matter for production systems.

A pragmatic roadmap for adoption​

  • Start small: run non‑safety critical workloads (analytics, map update batch jobs) inside the sovereign zone to validate controls.
  • Expand to regulated pilots: implement telematics and fleet‑ops with staged KPIs and live audits.
  • Move safety‑critical inference to hybrid: keep perception inference on edge, but stream training data and model retraining to the sovereign cloud under strict governance.
  • Full production: after independent attestations and successful pilot metrics, scale to broader fleet operations and integrate with traffic management and city digital twins.

Final analysis — strategic promise with operational caveats​

Space42’s Sovereign Mobility Cloud partnership with Microsoft and Core42 is strategically significant: it aligns hyperscaler innovation with local governance and operational readiness for mobility workloads that cannot tolerate legal or operational uncertainty. For the UAE this is a logical extension of broader sovereign cloud ambitions that aim to capture both economic value and national control of sensitive infrastructure.
However, the initiative will only deliver systemic value if it offers clear, auditable governance, robust SLAs for safety‑critical workloads, verifiable third‑party attestations, and contractual portability that prevents long‑term lock‑in. Procurement teams and regulators must insist on those guarantees before entrusting mission‑critical autonomous systems to any vertically integrated sovereign stack.
The next 12–36 months will determine whether the Sovereign Mobility Cloud becomes a practical production environment for wide‑scale autonomous mobility—accelerating deployment while preserving trust—or remains primarily a national showcase until the ecosystem proves migration, auditability and economic viability at scale.
Space42’s initiative is a significant milestone in the UAE’s push to marry national sovereignty with the speed and scale of hyperscaler AI — promising faster adoption of autonomous mobility, but demanding rigorous oversight, contractual discipline, and independent verification before it can be entrusted with the safety and privacy of millions of trips.
Source: Via Satellite Space42 Teams up with Microsoft for Sovereign Cloud Initiative
 
Space42’s announcement that it will build the UAE’s first Sovereign Mobility Cloud, enabled by Core42’s sovereign public cloud platform and underpinned by Microsoft Azure, marks a notable push to fuse national data sovereignty with large-scale autonomous-mobility infrastructure and HD mapping services. The initiative, unveiled on the sidelines of the Dubai World Congress, positions Space42 as the application and systems integrator for a mobility-focused sovereign cloud stack intended to host telematics, high-definition maps, fleet operations, traffic management, and digital-twin services inside UAE jurisdictional boundaries.

Background​

Why “sovereign cloud” and why now​

The UAE has been explicit about its ambition to accelerate AI and digital government services while keeping sensitive data under national control. Over the last two years, partnerships between Microsoft and local AI and cloud players — notably Core42, the sovereign-cloud arm of G42 — have set the technical and commercial groundwork for sovereign-enabled cloud offerings in the Emirates. Microsoft and Core42 have published joint material and white papers outlining how a sovereign public cloud can balance regulatory compliance, data residency, and AI innovation.
Microsoft’s existing UAE Azure regions (Dubai and Abu Dhabi) already provide data residency and a number of the technical building blocks typically required by sovereign deployments — from region-specific availability zones to confidential compute primitives. Azure’s confidential computing offerings and its UAE region presence are explicitly designed to let regulated customers keep data in-country while benefiting from hyperscale services. Those same Azure capabilities are being invoked by Core42 and its partners as part of the sovereign stack that will host mobility workloads.

Who the players are​

  • Space42: The ADX-listed entity formed by the 2024 merger of Bayanat and Yahsat; it combines geospatial AI, satellite connectivity, and smart-mobility operations and is already operating autonomous taxi services and mapping platforms in Abu Dhabi.
  • Core42: A G42 group company building sovereign cloud and AI infrastructure; Core42 offers a sovereign controls platform called Insight and partners with hyperscalers to deliver “sovereign-enabled” public cloud services.
  • Microsoft: Supplying Azure’s regional datacenters, Azure security and governance tooling, confidential compute primitives, and ecosystem support for application development, training, and operationalization.

What Space42 is promising: platform and features​

Core capabilities described​

Space42 describes the Sovereign Mobility Cloud as a sovereign-enabled platform for intelligent transport that will provide:
  • Trusted infrastructure for mobility data and autonomous systems, housed in UAE jurisdiction.
  • Platform services for HD mapping, telematics ingestion and processing, fleet operations, traffic management, and digital twins—functions critical to city-scale autonomous mobility.
  • Secure data-sharing mechanisms that allow government agencies, industry participants, and research institutions to exchange data under controlled, auditable rules.
Those functional categories line up precisely with what large-scale mobility ecosystems require: low-latency map and perception services, telemetry ingestion pipelines, model training and validation environments, and controlled multi-party data enclaves for research and regulatory oversight.

Roadmap and early-stage plans​

Space42 says the initiative will move from platform construction to reference deployments, regulatory sandboxes and test hubs with UAE transport authorities, supported by pilots and demonstrations designed to accelerate commercial rollouts. Microsoft and Core42 are expected to supply the sovereign-enabled cloud foundation — combining Azure’s regional infrastructure, confidential compute and data-governance tooling with Core42’s Insight control plane.

Technical architecture — how a Sovereign Mobility Cloud actually fits together​

Layers and components (high level)​

  • Infrastructure: Microsoft Azure UAE regions provide the underlying compute, storage, and network zones with in-country data residency. Azure supports availability zones in Dubai and Abu Dhabi and a catalogue of services required by mobility platforms.
  • Sovereign control layer: Core42’s Insight acts as a policy and governance platform to enforce data residency, access controls, and regulatory guardrails on top of Azure. This is positioned as the “sovereign control plane” that co-locates policies with data and compute.
  • Application & data services: HD map stores, telematics ingestion pipelines, digital-twin engines, and fleet-management systems run as platform services on top of Azure compute and Core42 controls; Space42 will own application deployment, regulatory liaison, and service orchestration.
  • Confidential computing: When workloads require protection while data is in use (for example, multi-party model training on private datasets), Azure confidential compute can be used to minimize privileged access and provide verifiable execution enclaves.

Why confidential compute matters for mobility​

Autonomous systems depend on large datasets — sensor logs, HD maps, route traces — that can include personally identifiable information and proprietary perception models. Confidential compute protects code and data during processing and reduces the need to trust cloud operators or external administrators with plaintext data. That technical capability is frequently cited by Microsoft and its sovereign-cloud partners as a cornerstone technology for regulated workloads.

The strategic logic: national sovereignty meets mobility economy​

For the UAE: faster, safer, sovereign mobility​

A mobility-focused sovereign cloud aligns with national priorities: it reduces friction for domestic public-sector adoption, gives regulators auditability and control, and creates a domestic environment for testing and scaling autonomous systems. Space42’s operational footprint in Abu Dhabi — including its TXAI autonomous service and mapping projects — gives it a pathway to package live operational data, reference deployments, and sandboxed regulatory experiments.

For Microsoft and Core42: a replicable playbook​

Microsoft gains by anchoring Azure deeper into government and regulated-industry workflows in the Middle East, while Core42 and G42 gain a hyperscale technology partner to make a sovereign cloud offering credible at enterprise and government scale. The joint white paper and government agreements already discussed demonstrate a model that can be replicated for other sectors — healthcare, finance, or national services — where sovereignty and AI adoption must coexist.

Claims to verify and a note on available evidence​

  • Space42’s announcement and feature list are available as a company press release and have been reported by national outlets. The headline claim — a UAE Sovereign Mobility Cloud enabled by Core42 and Microsoft Azure — is documented in Space42’s release and coverage by major UAE media.
  • The technical claim that Core42’s Sovereign Public Cloud “leverages Microsoft Azure” and uses a sovereign controls layer called Insight is confirmed by Microsoft’s Core42 white paper and Core42/G42 publications. This shows multi-source corroboration for the technical partnership and the presence of Insight as a control plane.
  • Space42’s operational data about its autonomous service (TXAI) — specifically the frequently-cited figures "nearly 600,000 km of autonomous driving" and "20,000 passenger trips" — appears in Space42 materials and is echoed in several news outlets. However, authoritative government-sourced figures from Abu Dhabi’s Integrated Transport Centre (ITC) and other reporting have given different numbers (for example, Gulf News reporting ~600,000 km and 40,000 trips). This divergence suggests that trip/odometer figures should be treated with caution until reconciled with public regulator statistics. Readers should note the discrepancy and treat those operational metrics as company-reported figures pending direct regulator confirmation.
  • Precise financial or timeline commitments (for example, detailed co-investment amounts or strict go-live dates for the Sovereign Mobility Cloud) are not yet publicly documented in consistent, multi-source detail in the announcement materials. Several outlets mention training, co-investment and technical support from Microsoft, but exact dollar figures and contractual timelines are not part of the Space42 release. Those specifics remain unverified in public sources at the time of reporting.

What this means for developers, integrators and the Azure ecosystem​

Opportunities​

  • Azure-native developers will find richer demand for cloud-native telemetry, streaming, and model-training solutions that run in Azure UAE regions and that can be wrapped with Core42/Insight policy controls.
  • Mapping and GIS vendors can partner with platform operators (Space42 and others) to supply HD-map layers, lane-level semantics and validation tooling for continuous map updates. These services are explicitly singled out in Space42’s platform description.
  • Edge and connected device vendors will have demand for telematics gateways, secure message brokers, and low-latency inference appliances that integrate with the sovereign cloud stack. Confidential compute primitives will likely be used for privacy-preserving analytics.

Developer guidance (practical)​

  • Architect mobility services for region-aware deployment: tag storage and compute so that sensitive data remains in UAE regions and use Azure tools to enforce residency.
  • Use confidential computing patterns for multi-party model training or for running proprietary perception models on shared datasets.
  • Design telemetry pipelines to accept policy-based filtering at ingestion time so regulatory sandboxes can expose only the permitted views of operational data.

Risks and governance considerations​

Vendor concentration and technical lock-in​

Stacking Core42’s sovereign control plane on top of Microsoft Azure creates a potent, but concentrated, supplier architecture. While the model is designed to preserve data residency, it can also create operational and contractual lock-in if data-export, inter-region portability, or independent third-party audits are not explicitly guaranteed in procurement contracts. Procurement teams should insist on clear exit, audit and data-portability terms.

Geopolitics and supply-chain scrutiny​

G42 — Core42’s parent group — has become strategically important to the UAE’s AI ambitions and has attracted international attention as a deep-pocketed regional AI champion. Coverage in international outlets shows an ongoing debate about geopolitics, U.S. scrutiny, and the global flow of cloud and AI technologies. The international posture of any sovereign-cloud provider can affect multinational customers and third-party suppliers who must navigate export controls and foreign-investment screening. Organizations should include geopolitical risk assessments as part of supplier due diligence.

Data governance and multi-party sharing​

The Sovereign Mobility Cloud’s promise to enable “secure data-sharing” between government, industry and research groups is attractive — but the mechanics matter. Without robust policy templates, mutability controls, and independent audit logs that are transparent to regulators, there is a risk of policy creep where data is repurposed beyond the original consented uses. The Core42 Insight control plane claims to provide these governance capabilities, but independent verification and third-party audits will be crucial.

Security exposure and the attack surface​

Mobility stacks aggregate large amounts of sensor data, identity metadata, and operational logs. Consolidating these under a sovereign cloud reduces some attack vectors (data stays in-country) but raises others: a concentrated platform becomes a higher-value target and requires defense-in-depth across network, compute and hardware roots of trust. Confidential compute reduces exposure when data is in use, but careful design of key management, enclave attestation, and logging policies remains essential.

Regulatory and operational realities: sandboxes, certification, testing​

Space42 and partners have outlined plans for regulatory sandboxes and test hubs to allow controlled trials. Sandboxes are a sensible mechanism because they permit incremental risk-controlled experimentation while regulators evolve certification and liability frameworks for autonomous systems. For software and services developers, these sandboxes will likely impose specific telemetry retention, access controls and incident-reporting obligations that must be respected to participate.
Public-sector ambition is high: Microsoft and Core42 have documented intentions to create a sovereign public cloud environment to handle millions of government interactions daily, and Abu Dhabi’s digital strategy has already signaled multi-year, large-scale digitization programs. Translating those ambitions into consistent compliance frameworks across municipalities, transport agencies and private operators is non-trivial and will require sustained governance investment.

Competitive and market implications​

Regional competitive landscape​

The UAE’s move is consistent with a broader regional trend: governments in the Middle East and beyond are building sovereign-enabled cloud offerings to reconcile hyperscale innovation with regulatory control. For hyperscalers, the approach is to partner with local sovereign-cloud specialists rather than attempt to deliver fully isolated sovereign clouds alone. That partnership pattern is visible in the Microsoft–Core42 collaboration.

Potential exportability of the model​

If successful, a mobility-focused sovereign-cloud blueprint could be packaged and exported to other countries seeking to host autonomous systems or sensitive mobility data domestically. However, exportability will hinge on clear certification, modular control planes that support different legal regimes, and transparent audit mechanisms that reassure international automakers and cloud customers.

Practical checklist for organisations evaluating the Sovereign Mobility Cloud​

  • Insist on documented data residency guarantees and clear service-level agreements for data export and portability.
  • Require independent third-party audits of the sovereign control plane and confidential-compute attestation processes.
  • Validate incident response and cross-jurisdiction breach notification procedures ahead of production deployment.
  • Confirm the policy model (who can query what data, under what conditions) and test it in a regulatory sandbox before scaling.

Conclusion​

Space42’s Sovereign Mobility Cloud announcement stitches together three converging dynamics: the UAE’s political will to own and control critical digital infrastructure; hyperscaler technology (Microsoft Azure) that delivers regionally resident compute and confidential-compute primitives; and local sovereign-cloud engineering (Core42 and its Insight control plane) that promises policy-first governance atop hyperscale services. The resulting stack is compelling for autonomous-mobility use cases that require low-latency processing, HD mapping, and strict data residency.
That promise comes with practical trade-offs. Developers and buyers should treat operational metrics and company-provided performance figures cautiously until regulator-validated data is available; they must negotiate portability and auditability protections to avoid supplier lock-in; and they need to build security and governance into the fabric of their services rather than as an afterthought. For the UAE, the move can accelerate safe, sovereign autonomous mobility — and for the Azure ecosystem, it creates a fertile field of demand for mapping, telemetry and AI operations services. The critical tasks ahead are the rigorous, transparent execution of governance controls, and the open reconciliation of operational claims against independent regulator data.
Source: Telecompaper Telecompaper
 
Space42’s announcement at the Dubai World Congress marks a major step toward building a sovereign mobility cloud in the UAE — a purpose-built, sovereign-enabled platform for hosting HD mapping, telematics, fleet operations, traffic management and digital twins — backed by Core42’s Sovereign Public Cloud layer and Microsoft Azure’s enterprise-grade cloud and AI capabilities. The initiative promises tighter data residency controls, confidential compute options and a single platform designed to accelerate adoption of autonomous mobility services, but it also raises tough questions about vendor architecture, governance, regional geopolitics and the operational realities of scaling mission-critical mobility infrastructure.

Background​

Since 2021 the UAE has invested heavily in smart mobility pilots and autonomous vehicle trials, creating an ecosystem of regulators, operators and technology partners that now includes Space42, G42/Core42 and Microsoft. Space42 — formed by the merger of Bayanat and Yahsat and positioned as a national SpaceTech and geospatial AI champion — has operated the TXAI autonomous taxi service across Yas, Saadiyat, Al Maryah and Al Reem Islands and to Abu Dhabi Airport. The company reports a substantial operational record for TXAI: roughly 600,000 kilometres of autonomous driving and about 20,000 passenger trips accumulated since 2021, an operational dataset and public trial history that underpins its credibility to lead application deployment for a mobility platform.
Core42, the sovereign-cloud and AI-infrastructure arm of G42, has been building a “Sovereign Public Cloud” offering that layers controls and governance on top of hyperscaler infrastructure (notably Microsoft Azure in this context), marketed under an Insight controls platform. Microsoft, for its part, has deepened commercial and strategic ties with Emirati partners in recent years, including a major investment and technical collaboration with G42, and has positioned Azure to support region-specific, sovereign-enabled solutions that combine data residency, confidential compute, and Azure’s AI and cloud services.
Taken together, these players are pitching the Sovereign Mobility Cloud as an industry-first platform in the UAE dedicated to intelligent transport and autonomous systems — a national-grade environment intended to relieve public agencies and regulated companies of the awkward trade-off between hyperscale innovation and data sovereignty.

Overview of the Sovereign Mobility Cloud concept​

What the platform intends to provide​

The Sovereign Mobility Cloud is presented as a verticalised cloud platform tailored for mobility and autonomous-system workloads. Core elements include:
  • HD mapping and geospatial services for localization and route planning.
  • Telematics and fleet operations: telemetry ingestion, fleet health monitoring and orchestration.
  • Traffic management: integration with road-side sensors and centralized traffic-control systems.
  • Digital twins for city-scale simulation, scenario testing and regulatory approvals.
  • Secure data sharing between government bodies, operators, researchers and OEMs under regulated access controls.
Those components are common building blocks for modern mobility stacks, but the platform’s defining attribute is the “sovereign” controls and governance that aim to keep sensitive mobility and personal data under the jurisdictional, regulatory and technical protections of the UAE.

How the stack is being positioned technically​

The announced architecture layers include:
  • Azure hyperscale infrastructure (compute, storage, networking) hosted in the UAE region for data residency.
  • Core42’s Sovereign Public Cloud overlay that provides pre-built controls, policy enforcement and a governance application (Insight) designed to implement UAE-specific compliance and security requirements.
  • Confidential compute technologies (used to isolate workloads and limit data exfiltration risks).
  • Application platform and AI tooling supplied by Microsoft, plus Space42’s geospatial AI products (notably its GIQ platform) and mobility application suites (TXAI operational software, HD map pipelines).
Microsoft and Core42 will supply the underlying cloud foundation and governance frameworks, while Space42 will lead application deployment, regulatory engagement and pilot rollouts.

Why the UAE is pursuing sovereign mobility clouds​

The UAE’s strategy is straightforward: preserve the benefits of hyperscale cloud innovation while ensuring critical national data (transport, citizens, infrastructure) is subject to domestic control, auditability and regulatory policy. Key drivers include:
  • National security and privacy: Autonomous mobility systems generate detailed telemetry that can implicate national infrastructure and personal privacy. Sovereign hosting reduces cross-border data exposure.
  • Regulatory clarity: Governments prefer local, auditable platforms when they oversee trials, liability, and approvals for autonomous services.
  • Economic and industrial strategy: Hosting platforms locally fosters in-country capability building, high-value jobs, and exportable IP for the region’s nascent mobility supply chain.
  • Performance and integration: Local cloud regions reduce latency for real-time perception and telematics workloads, which is critical for teleoperated functions and connected traffic management.
These motivations align with broader Abu Dhabi and UAE digital strategies that have embedded sovereign cloud initiatives and AI-targeted investments into national roadmaps.

Technical analysis: strengths and practical capabilities​

Strength — Dedicated, domain-specific infrastructure​

A standalone mobility cloud gives the UAE a domain-specific environment where the entire lifecycle of mobility data — collection, storage, model training, simulation and operations — can be governed holistically. That reduces friction between transport authorities, private operators and researchers who often struggle with incompatible data formats and cross-border legal barriers.

Strength — Data residency + confidential compute​

Combining Azure’s regional infrastructure with a sovereign controls layer and confidential compute provides a convincing technical posture for governance. Confidential compute (e.g., hardware-backed enclaves and trusted execution environments) can limit who sees raw telemetry, sensor streams, and high-resolution map data while still allowing aggregated analytics and model training when permitted.

Strength — Operational experience and live telemetry​

Space42’s TXAI operational history — extensive kilometres and thousands of passenger trips — gives the project an operationally grounded partner to run pilots, demonstrate safety, and provide real-world datasets to validate platform services such as HD mapping and fleet orchestration.

Strength — Ecosystem and training commitments​

With Microsoft promising training, technical enablement and co-investment, the project is positioned as an ecosystem play rather than a vendor-only deployment. That can accelerate local skills development for operators, regulators and system integrators.

Risks and unanswered questions​

No major infrastructure project is without trade-offs. The Sovereign Mobility Cloud raises several practical and geopolitical risks that must be assessed honestly.

Risk — Vendor composition and concentration​

The platform will combine Azure infrastructure with G42/Core42 controls and Space42 applications. While this hybrid provides convenience, it also concentrates critical mobility infrastructure within a small number of vendors and an interdependent supply chain. That creates potential points of failure and raises questions about:
  • Operational independence: If one provider experiences outages, how resilient is the national mobility fabric?
  • Lock-in: How portable are critical assets — HD maps, trained models, telemetry pipelines — if regulators or operators want to move workloads between providers?
Mitigation requires clear portability standards, open data formats for HD maps and route data, and contractual SLA/backout clauses that protect national continuity.

Risk — Geopolitical and export-control exposure​

The collaborations between Microsoft and G42 (including previous investments and technology-sharing arrangements) have attracted international scrutiny. Investments and technology transfers that enable sovereign cloud capabilities can interact with export controls, foreign policy constraints and concerns around advanced chip exports. The project’s ability to use state-of-the-art AI accelerators, for example, depends on export licensing and cross-border policy. Any constraints on supply chains, chip availability or software licensing could delay deployments or limit compute scale.

Risk — Trust model and transparency​

Sovereign clouds trade a lot on trust. Governments and citizens expect controlled access, auditable policies and demonstrable protection against foreign intelligence access. But trust is built through transparent governance processes, independent audits and clear third-party validation of security claims. The announced stack needs independent verification (e.g., security audits, penetration tests and governance attestations) to avoid skepticism about whether confidential compute and resident controls truly prevent unauthorized access.

Risk — Data governance complexity​

Mobility data is not monolithic. It contains personal data (passenger manifests, ride telemetry), operational data (fleet diagnostics) and infrastructure data (traffic flow, sensor health). The platform must implement fine-grained policy enforcement that distinguishes permitted uses (e.g., aggregated research) from prohibited ones. Handling cross-stakeholder access requests (researchers, OEMs, enforcement agencies) will require robust attribute-based access control (ABAC), purpose limitation, logging and precise consent models.

Risk — Safety and liability​

Scaling autonomous services from pilots to city-wide deployments introduces liability questions. If the sovereign cloud manages the mapping and fleet controls, how will liability be apportioned between operators (Space42 or third-party operators), platform providers (Core42/Microsoft) and hardware vendors? Regulatory sandboxes are needed to clarify fault models and to run safety-case analysis across edge, vehicle and cloud layers.

Regulatory and governance considerations​

Regulatory sandboxes and test hubs​

The announced next steps — reference deployments, regulatory sandboxes and test hubs — are the correct pragmatic approach. Sandboxes let regulators test real-world scenarios and craft rules that reflect operational evidence. Test hubs provide sanitized environments for stress-testing HD mapping updates, vehicle-to-infrastructure integration and teleoperation under controlled conditions.

Data-sharing frameworks​

Secure cross-sector data sharing will be a central capability. Effective frameworks should include:
  • Data classification: a taxonomy separating anonymized telemetry, pseudonymized passenger data, and national-infrastructure-sensitive information.
  • Role-based and purpose-based access: technical enforcement that mirrors legal permissions.
  • Auditability and provenance: immutable logs of who accessed what and when, plus lineage for derived AI models.
  • Retention and deletion policies: automated lifecycle controls to ensure data isn’t retained longer than allowed.

Certification and independent oversight​

To maintain credibility, the platform should adopt third-party security certifications, regular compliance assessments and publicly verifiable audit reports that cover confidentiality, integrity and availability controls.

Commercial and market implications​

For mobility operators and OEMs​

A sovereign mobility cloud could lower barriers for OEMs and operators who require local data residency and regulated testing environments. Rather than provisioning standalone on-prem stacks, smaller operators can rely on the sovereign platform to provide mapping, fleet orchestration and regulatory-compliant telemetry ingestion.

For startups and researchers​

Access to a national dataset, sandboxes and compute resources (if priced reasonably) could catalyse local innovation, spurring startups to develop perception modules, vehicle controllers and simulation tools that are tuned to Middle East urban topologies and weather patterns.

For global cloud providers and hyperscalers​

The model underscores an emerging business approach: hyperscalers providing core infrastructure while sovereign-cloud integrators layer controls and compliance packages for national markets. Expect other markets to replicate this pattern where national data sovereignty is a priority.

Technical deep dive: what to expect under the hood​

While the service architecture is vendor-specific, several technical patterns are likely to be used:
  • Edge-cloud hybrid model: latency-sensitive workloads (vehicle control loops, perception pre-processing) will likely run on edge nodes or within vehicles, while heavier workloads (HD map generation, model training) will be hosted in the sovereign cloud.
  • Streaming ingestion pipelines: real-time telematics and LiDAR/radar feeds will require scalable streaming platforms (Kafka or Azure Event Hubs equivalents) with guaranteed delivery and schema management.
  • HD map versioning and distribution: maps will be treated as first-class artifacts with semantic versioning, delta update streams and signed bundles to ensure consistency across vehicles.
  • Model governance: model registries, experiment tracking and model explainability tooling will be needed to demonstrate safety, auditability and rollback.
  • Confidential compute enclaves: these will be used for sensitive model training or workloads where raw citizen data cannot be exposed even to administrators.
Operational excellence will depend on well-defined CI/CD for models and infrastructure-as-code templates to keep deployments reproducible and auditable.

Implementation challenges​

  • Scaling storage and bandwidth for HD mapping and sensor data will be expensive; designs should prioritise smart compression, temporal retention limits and derived data storage.
  • Interfacing legacy traffic-control systems and heterogeneous edge devices requires robust protocol adapters and hardened telemetry gateways.
  • Coordination across public agencies, private fleets and academic partners will necessitate a governance board, common APIs and standard SLAs for shared services.
  • Ensuring vehicle safety when maps or control signals become stale requires strict update policies and fallback behaviour built into vehicle software.

What this means for the region and the industry​

The Sovereign Mobility Cloud is more than a national tech project — it represents a template for how countries can reconcile AI-driven mobility innovation with sovereignty and regulatory control. If delivered successfully:
  • Abu Dhabi and the UAE could become a regional testbed and exporter of mobility services and standards.
  • The model could be replicated by other governments balancing innovation and control.
  • It could accelerate safe, regulated deployment of autonomous vehicles by giving operators a reliable compliance-first cloud environment.
At the same time, the initiative heightens geopolitical attention to where and how sensitive AI systems are hosted, how national champions partner with global hyperscalers, and how export-control regimes interact with sovereign cloud rollouts.

Recommendations and red flags for policymakers and operators​

  • Require independent security and privacy audits of sovereign controls, especially confidential compute claims, before scaling to production-critical workloads.
  • Mandate open interfaces and portability standards for HD maps and telemetry to avoid vendor lock-in and to enable multi-cloud resilience.
  • Establish clear liability frameworks that define responsibilities for software, hardware, platform operators and infrastructure failures.
  • Create transparent governance with public reporting on access requests, data uses and cross-border transfers.
  • Monitor export-control dependencies for critical hardware such as AI accelerators, and develop contingency plans to ensure compute capacity if supply chains shift.
These steps balance the benefits of rapid innovation with the responsibilities of delivering safe, sovereign services.

Next steps and likely timeline​

The announcement signals immediate activity around pilots, regulatory sandboxes and reference deployments. Typical program phases for a project of this complexity include:
  • Short-term (3–9 months): regulatory sandbox deployments, targeted pilots with limited fleet sizes and specific urban zones, security and compliance baseline testing.
  • Medium-term (9–18 months): expanded city deployments, integration with traffic management centers, initial multi-tenant operations and service-level agreements.
  • Long-term (18–36 months): full-scale production rollouts, third-party integrations, and potential export of the sovereign mobility platform model to partner nations.
Timeframes will be influenced by regulatory approvals, availability of AI compute and the pace at which independent security attestations are completed.

Conclusion​

The Space42–Core42–Microsoft Sovereign Mobility Cloud is an ambitious convergence of national policy, hyperscaler capability and operational mobility know-how. It addresses a genuine market need: a secure, compliant environment for operating autonomous systems and the rich datasets they produce. The initiative leverages real operational experience from TXAI and the technical muscle of Azure and Core42 to create a verticalised platform that could accelerate safe, governed deployment of autonomous mobility across the UAE and the wider region.
Yet ambition must be matched by rigorous governance, transparent audits and hard engineering that prevents vendor lock-in, ensures portability and protects national interests. Sovereign clouds are not a silver bullet; they are an architectural commitment that requires clear regulatory frameworks, independent verification and contingency planning for geopolitical and supply-chain risk. If the partners deliver on those foundations, the Sovereign Mobility Cloud could become a replicable model for balancing innovation and sovereignty in the AI era — but success will be measured by operational resilience, safety outcomes and the platform’s demonstrable ability to serve the public interest.
Source: Gulf Business Space42 to develop UAE’s first sovereign mobility cloud with Microsoft and Core42
 
You must log in or register to reply here.

Similar threads

  • Featured
  • Article Article
UAE’s Sovereign Cloud and AI Integration: Leading Digital Transformation with Microsoft & Core42
Replies
0
Views
287
ChatGPT
  • Featured
  • Article Article
UAE Leads Digital Sovereignty with Microsoft & Core42's Cloud Innovation in the AI Era
Replies
0
Views
215
ChatGPT
  • Featured
  • Article Article
Microsoft & Core42 Lead UAE's Sovereign Cloud Revolution for Secure AI & Digital Sovereignty
Replies
0
Views
373
ChatGPT
  • Featured
  • Article Article
UAE Cloud Sovereignty: How Sovereign Public Cloud Drives AI and Digital Transformation
Replies
0
Views
147
ChatGPT
  • Featured
  • Article Article
Sovereign Cloud UAE: Powering Digital Transformation and AI
Replies
0
Views
118
ChatGPT