Microsoft and FedEx did form a multiyear partnership, but it is not a new 2026 deal or a full-scale Amazon replacement. Announced in 2020 and expanded in 2022, the collaboration combines Microsoft cloud and order-management software with FedEx shipment data, delivery services and logistics expertise. Its bet is that retailers can improve fulfillment while keeping their own storefronts and systems.
What Microsoft and FedEx announced—and when
The alliance began on May 18, 2020, when the companies announced a multiyear collaboration pairing FedEx’s transportation network with Microsoft Azure, analytics and business software. The first named product was FedEx Surround, a service for shipment visibility, predictive alerts and possible intervention. FedEx’s 2020 announcement described the goal as transforming commerce, not as a formal anti-Amazon pact.
FedEx said Surround was deployed in December 2020 and used in support of COVID-19 vaccine transportation. That is evidence of deployment reported by the company, not independent proof of broad commercial success or better performance than Amazon.
On January 24, 2022, the companies announced an expansion: a cross-platform “logistics as a service” concept connecting FedEx network intelligence to Dynamics 365 Intelligent Order Management. Microsoft described the offering as in preview in April 2022 and discussed returns capabilities. The original announcement forecast U.S. availability in the second half of 2022; that forecast is historical, not a statement of current availability or terms. FedEx’s 2022 announcement and Microsoft’s April 2022 account document the expansion.
Recommended Free Tools
#1 Best Overall
As of August 2026, FedEx lists Surround as a commercial service, and Microsoft continues to document Intelligent Order Management and a FedEx connector. The available sources establish the products and their intended functions, but not how widely the joint offering is deployed or what measurable results customers have achieved.
What each company contributes
Microsoft: cloud, data and order orchestration
Azure supplies cloud infrastructure and data-processing capabilities; AI, machine learning and analytics are intended to help interpret shipment and network data. Dynamics 365 Intelligent Order Management is the enterprise layer for coordinating orders across sales channels, fulfillment systems and logistics providers. Microsoft describes it as a cloud application that connects with Microsoft and non-Microsoft business systems, with Dataverse and provider integrations among its components. Microsoft’s overview and current product documentation explain the platform.
For a retailer, the idea is to apply fulfillment rules across orders arriving from a website, marketplace, mobile app, social commerce, electronic data interchange (EDI) or point-of-sale system, rather than treating each source as a separate process. The companies described integration with existing commerce platforms rather than requiring merchants to replace all their systems.
Rank #2
- Ideal for Gifting
- Ideal for a bookworm
- Compact for travelling
FedEx: transportation, shipment data and operational action
FedEx contributes its package and delivery network, shipment scans, logistics data, sensing capabilities and the operational ability to pick up, deliver or, in some service arrangements, intervene in a shipment. In its 2020 announcement, FedEx said its network connected more than 99% of global GDP across 220 countries and territories. Those are company-reported figures from 2020, not current independently verified measurements.
FedEx Surround is more than a tracking page
Ordinary tracking tells a shipper about recorded package events. Surround is designed to add near-real-time visibility, predictive delay alerts and options for intervention, particularly for time-sensitive or high-value shipments. FedEx’s current Surround page describes package-level monitoring, healthcare shipment identification and service levels including Select, Preferred and Premium. The services and interventions available depend on the tier and shipment; they do not guarantee that a delay will be prevented.
For example, if a pharmaceutical shipment is at risk during a weather disruption, an alert could help a shipper identify the exception earlier and explore recovery options. That illustrates the service’s stated purpose, not a guaranteed outcome. Premium services may include higher-priority handling, out-of-network recovery or expediting; cold-chain recovery and cellular- or GPS-enabled sensors may also be available, with sensors carrying additional fees. Near-real-time visibility should not be read as continuous GPS tracking for every package.
Rank #3
FedEx’s page does not show a universal U.S. list price for Surround; it directs prospective customers to an account representative or consultation. Some monitoring and intervention functions have integration prerequisites. FedEx lists FSMS 20.08+, FSM/Café 3800+, FedEx API updated February 2024 or later, GSM 2404+, or fedex.com/MAGI for certain functions, so a buyer should confirm which path applies to its system and service.
What the 2022 logistics-as-a-service idea was meant to do
The proposed retailer-facing layer would connect FedEx network data to Dynamics 365 Intelligent Order Management. In practical terms, order-management software can sit between an order source, a retailer’s business systems, fulfillment locations and delivery providers, applying rules to route orders and coordinate status updates and returns. FedEx’s role is the logistics network and associated information; Microsoft’s is the software and cloud layer for orchestrating orders.
The intended outcomes included coordinating fulfillment, sending delivery updates and supporting returns through FedEx’s network. These were the companies’ goals, not independently established savings or delivery improvements. Although the partners emphasized working with existing systems to avoid a wholesale “rip and replace,” integration still requires data mapping, configuration, testing and ongoing administration.
Rank #4
Returns were part of the proposition
The announced returns experience included FedEx drop-off locations, at-home pickups, printerless QR-code labels and, in some configurations, no-box returns. Microsoft later described a network of more than 60,000 FedEx drop-off locations in connection with returns. That figure is attributed to Microsoft/FedEx materials; it should not be treated as a current U.S.-only count. Convenience also depends on a customer’s location and the service arrangement. Microsoft’s explanation of the collaboration covers the broader commerce concept.
Why Amazon is the comparison—and where it breaks down
Amazon’s structural advantage comes from combining a marketplace, seller services, warehousing and fulfillment, delivery infrastructure, customer-facing tracking and AWS cloud computing. Microsoft and FedEx do not offer that whole stack together. Their proposal is more modular: Microsoft provides enterprise software and cloud capabilities, FedEx provides logistics, and a retailer can retain its own brand, storefront and other systems.
| Microsoft–FedEx approach | Amazon approach |
|---|---|
| Enterprise software and carrier logistics that can connect to a merchant’s existing channels. | A vertically integrated ecosystem spanning marketplace, fulfillment and delivery, alongside AWS. |
| Designed for brands that want to retain their storefront and customer relationship. | Marketplace participation can give sellers access to Amazon’s customer discovery and fulfillment options. |
| Requires configuration and integration across systems and providers. | Requires sellers to participate in Amazon’s ecosystem for its marketplace and fulfillment services. |
That makes “against Amazon” a useful description of the competitive context, not the companies’ formal positioning. The partnership could help merchants strengthen order management, delivery visibility and returns without joining Amazon’s entire ecosystem. It does not recreate Amazon’s marketplace, Prime membership, retail demand engine or fulfillment footprint, and the sources do not establish that it displaced Amazon or materially changed its market share.
Best Value
- It can be a gift option
- Comes with secure packaging
- Helpful in various ways
Which businesses might benefit most?
The strongest fit is likely to be a mid-market or large retailer, direct-to-consumer brand or manufacturer with multiple sales channels, fulfillment locations or complex order rules. Companies shipping high-value, time-sensitive or sensitive goods—including healthcare, pharmaceutical, automotive and aerospace shipments—may also have more reason to pay for exception monitoring and intervention than businesses sending routine parcels.
- Potentially useful: A brand that wants to preserve its own customer relationship while coordinating orders across stores, online channels and fulfillment partners.
- Potentially useful: An organization already using Microsoft business software and able to support enterprise integrations.
- Potentially useful: A shipper for whom early warning and response options could justify extra service costs.
- Less suitable: A small seller shipping a few low-value parcels each month, or one whose main need is a consumer marketplace rather than order-management software.
- Less suitable: A retailer satisfied with its existing order-management platform, or one that requires broad carrier flexibility but has not verified support for its full carrier mix.
Costs, setup and the buyer’s checklist
Microsoft’s U.S. pricing page lists Intelligent Order Management at $315 per month for 1,000 order lines per month. Microsoft says prices are informational and that regional and licensing variations may apply, so this is a list-price signal, not a complete total-cost estimate. It excludes implementation and should not be read as including FedEx shipping or service charges. Microsoft’s pricing page is the place to confirm current terms.
FedEx Surround has no universal U.S. price posted on its main page; buyers are directed to FedEx for a discussion, and optional sensors may add fees. A retailer should also account for integration work, testing, staff time and any systems-integrator support. Microsoft documents a 30-day Intelligent Order Management trial, with a possible one-time extension; its trial terms say inactivity for 14 consecutive days can cause the trial to expire. A trial is not a substitute for production licensing. See Microsoft’s trial-license documentation and trial FAQ.
- Order complexity: Do you need rules across multiple warehouses, stores, marketplaces and carriers?
- Microsoft fit: Do your systems and staff already use Dynamics, Dataverse, Power Platform or Azure, and can they support configuration and APIs?
- Carrier mix: Is FedEx central to your shipping strategy, and how will other carriers or fulfillment providers be handled?
- Shipment criticality: Would alerts and possible intervention justify premium services, or is standard tracking sufficient?
- Returns and coverage: Are FedEx drop-offs and printerless returns convenient for your actual customers and geographies?
- Implementation capacity: Can you manage security review, data mapping, integration testing and ongoing administration?
For the Intelligent Order Management FedEx provider, Microsoft requires a FedEx Developer account, organization, project and credentials. Microsoft says the connector was developed specifically for Intelligent Order Management and has limited support outside that use case. Teams should verify current compatibility and service coverage in the FedEx connector documentation; businesses building direct integrations can also review the FedEx Developer Portal.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWhat is established—and what is not
- Product existence: FedEx Surround is documented as a current service; Microsoft documents Intelligent Order Management and a FedEx connector.
- Deployment: FedEx reported Surround’s deployment in December 2020 and its use supporting vaccine transportation.
- Customer outcomes: The cited materials do not establish broad, independently measured delivery improvements, cost savings or customer satisfaction results.
- Competitive impact: The available evidence does not show that the partnership replaced Amazon’s fulfillment network or weakened its market position.
The distinction matters: an announced capability, a reported deployment and a demonstrated market impact are different levels of evidence. The public materials support the first two, not the last.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.




