SOAP
Concept
SOAP is an earlier, XML-based protocol for building web services that was largely displaced by simpler REST-style APIs over plain HTTP.
Description
SOAP is an XML-based protocol specification for exchanging data between two endpoints in web services. It was created to give different platforms and programming languages an interoperable way to communicate. Over time it was largely displaced by simpler REST-style APIs that run over plain HTTP. In the Microsoft ecosystem the term still appears when older interfaces, such as Exchange Web Services, are compared with newer ones.
An archived MSDN Magazine column from 2009, listed in Microsoft Learn, compares SOAP with REST and makes a distinction that is useful for anyone researching the topic: SOAP is a protocol specification, whereas REST is an architectural style. According to that column, SOAP is deliberately not tied to HTTP, so it can run over other transports. WSDL metadata lets client proxies be generated from a service description. The WS-* extensions add capabilities such as message-level security that works across protocols, federated identity, and atomic distributed transactions.
The same column also lists drawbacks. SOAP over HTTP POST cannot take advantage of HTTP caching, SOAP services are harder to scale, differences between vendors in the many standards complicate interoperability, and distributed transactions increase coupling between systems. The author rejects the claim that SOAP is inherently more secure than REST, noting that both usually rely on HTTP authentication combined with TLS. The column concludes that SOAP is worth choosing when a specific SOAP feature is needed, and that otherwise REST usually offers better characteristics. It is worth keeping in mind that the page is a 2009 opinion piece rather than a formal specification.
The M365.FM episode "Migrate Exchange Web Services to Microsoft Graph with Glen Scales [MVP]" places SOAP in a practical migration setting. Its comparison table describes Exchange Web Services (EWS) as a legacy SOAP-based API for accessing Exchange mailbox data directly, with an XML/SOAP API style and a main use in on-premises Exchange or older Microsoft 365 apps. Microsoft Graph is described there as a modern REST-based API with a JSON/REST style, giving unified access to Microsoft 365 data, including Exchange Online, Teams and Azure AD, through one endpoint. The episode says the switch from SOAP to REST makes API interactions simpler and more modern, and that the unified endpoint makes it easier to connect to different Microsoft 365 services.
SOAP also comes up in the episode "Power Automate vs Azure Logic Apps for Enterprise Integration". There it is mentioned in the context of Azure Logic Apps orchestrating large-scale APIs: existing web services can be integrated by importing OpenAPI or SOAP specifications, and Logic Apps can also be imported as APIs to build composite APIs. The episode presents this as part of the flexibility that Logic Apps offer for enterprise orchestration. In this case SOAP is not something to be removed but an existing service format that integration tooling can still consume.
Taken together, the sources show the two situations in which SOAP typically matters today. One is migration work, where an application built on a SOAP-based interface such as EWS is moved to a REST-based one such as Microsoft Graph. The other is integration work, where an existing SOAP service must be connected to newer workflows. In both cases the decision rests on whether a specific SOAP capability is required or whether a REST and JSON approach covers the need.
Overview compiled with AI from M365.FM episodes and the facts on this page. You can improve it with the edit button below.
| Type | Concept |
|---|
Frequently asked questions
Questions marked with AI were written with AI from the facts on this page.
What is SOAP? (AI)
SOAP is an XML-based protocol specification for exchanging data between two endpoints in web services. It was designed to give different platforms and languages an interoperable way to communicate and is not tied to HTTP.
How does SOAP differ from REST? (AI)
According to an archived MSDN Magazine column, SOAP is a protocol specification while REST is an architectural style. The column notes that SOAP over HTTP POST cannot use HTTP caching and is harder to scale, and concludes that REST usually offers better characteristics unless a specific SOAP feature is needed.
Where does SOAP appear in the Microsoft ecosystem? (AI)
The M365.FM episode on migrating to Microsoft Graph describes Exchange Web Services as a legacy SOAP-based API, compared with the REST-based Microsoft Graph. Another episode notes that Azure Logic Apps can integrate existing web services by importing OpenAPI or SOAP specifications.
Community wiki
Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.
Experts and companies for this topic
Nobody has listed this topic yet. Add it to your profile.
Maintained by Mirko Peters (Microsoft MVP) · Last updated: