AzureCAT - Technical Customer Stories

The blog has moved! This page will be removed on 3/20. You can find this blog post over at our new site here:


Last Updated: 2/11/19

Over in this blog post, we mentioned why we're named AzureCAT:

CAT stands for “Customer Advisory Team.” We work with customers who act as feedback Advisors back to our product teams, by working on engagements with those customers and building ground-breaking solutions!


While we help customers architect those solutions, we learn a ton in the process! And so we want to share those customer architectures with you. We call these technical customer stories (TCSs).

This blog lists out our AzureCAT TCSs. These are customer architectures from engagements led by our CAT and CSA (Cloud Solution Architect) teams. They are journeys into architectural design decisions that led these customers into highly successful solutions.


Service Fabric:

  1. ABBYY - Case Study | Blog
  2. Alaska Airlines - Case Study | Blog
  3. BMW - Case Study | Blog
  4. Citrix - Case Study | Blog
  5. D+H - Blog
  6. Digamore Entertainment - Case Study | Blog
  7. FunRock - Case Study | Blog
  8. Honeywell - Case Study | Blog
  9. Info Support & Fudura - Case Study | Blog
  10. Mesh Systems - Case Study | Blog
  11. P2ware - Case Study | Blog
  12. Proactima Solutions - Case Study | Blog
  13. Quorum Business Solutions - Case Study | Blog
  14. Schneider Electric - Case Study | Blog
  15. SiriusIQ - Case Study | Blog
  16. Societe Generale and Qarnot Computing - Case Study | Blog
  17. Solidsoft Reply - Case Study | Blog
  18. TalkTalk TV - Case Study | Blog
  19. Wolters Kluwer - Blog
  20. Zeiss Group (new; published on 1/25) - Case Study | Blog

Cosmos DB:

SAP to Azure:

SQL Server:

  1. BNW Consulting + Large Australian Energy Company
  2. Bwin


All our Technical Case Studies are also featured on


Each technical customer story includes the following sections (mostly):

  1. A brief description of the company and their general business
  2. A deeper dive into the product or service that they are developing.
    1. If applicable, a look at the previous architecture of their service.
    2. Any requirements, weaknesses, or obstacles they wanted to fix by re-architecting their solution.
  3. An overview of their new architecture on a given service (such as Service Fabric).
    1. The specifics of how they implemented that architecture.
  4. How that service fits into their other services and technologies used to build their system.
  5. A deeper dive of their architecture and implementation of the Azure service (and related technologies).
  6. A summary that concludes with the benefits gained from the new architecture.


Leave us a comment if anything is helpful, or if you have a question. Thanks!

- Ninja Ed


See Also


Azure CAT Guidance

"Hands-on solutions, with our heads in the Cloud!"