The Death of Custom APIs: Microsoft Refine (Rayfin) as a Backend as a Service (BaaS)

For years, custom APIs have been the foundation of modern application development. Whenever organizations needed to connect systems, expose data, automate processes, or enable new digital experiences, the answer was almost always the same: build another API.At first, the approach worked.Each API solved a specific problem and helped teams move faster. But over time, those point solutions multiplied. What began as flexibility slowly transformed into complexity, creating a fragmented landscape of disconnected services, duplicated logic, inconsistent security controls, and growing technical debt.In this episode of the M365 FM Podcast, we explore why custom APIs have become one of the largest bottlenecks in enterprise technology and why a new generation of code-first, governance-driven backend platforms is emerging to replace them.

THE MIDDLEWARE CRISIS NOBODY TALKS ABOUT

Many organizations are now managing hundreds of APIs spread across different teams, cloud environments, databases, and security models.The result is a growing middleware crisis where development speed slows down despite increasing investments in technology.Topics discussed include:

• API sprawl across multiple teams
• Fragmented authentication models
• Governance challenges
• Hidden maintenance costs
• Technical debt accumulationThe episode explains why middleware complexity often becomes a bigger problem than application development itself.

WHY CUSTOM APIS BECAME A LIABILITY

Custom APIs were originally designed to provide flexibility.Ironically, that flexibility often becomes the source of long-term complexity.The conversation explores how organizations unintentionally create fragmented architectures where every service has its own authentication model, monitoring strategy, deployment process, and governance requirements.Listeners learn why:

• Security becomes inconsistent
• Compliance becomes expensive
• Change management slows down
• Maintenance costs increase
• Innovation becomes harder over timeTHE ARCHITECTURE PROBLEM BEHIND THE PROBLEM

The issue is not simply the number of APIs.The deeper challenge lies in how traditional architectures separate data, business logic, governance, and security into different layers that require constant translation and synchronization.The discussion examines:

• Layered architecture limitations
• Data governance fragmentation
• Compliance complexity
• Operational silos
• Lack of unified control planesThis architectural separation creates complexity that compounds as organizations scale.

THE AGENTIC AI INFLECTION POINT

Artificial Intelligence is exposing weaknesses that already existed in enterprise backends.Traditional APIs were designed for human-driven interactions.AI agents operate differently.They make decisions, orchestrate workflows, call multiple services, and maintain context across complex processes.Topics include:

• Autonomous agents
• Agent orchestration
• Tool calling patterns
• State management
• Agent-safe architectures
• AI-ready backend designThe episode explains why many current API strategies simply cannot support large-scale agentic systems.

INTRODUCING RAYFIN

At the center of the conversation is Rayfin, an open-source backend definition framework designed to replace traditional middleware approaches.Instead of manually building infrastructure components, developers define their backend entirely in code.Rayfin allows organizations to define:

• Data models
• APIs
• Authentication
• Authorization
• Storage
• Governance policiesAll backend components become version-controlled, repeatable, and deployable through a single source of truth.

MICROSOFT FABRIC AS THE CONTROL PLANE

One of the most significant aspects of the discussion is Rayfin's integration with Microsoft Fabric.Rather than deploying isolated infrastructure across multiple cloud services, Rayfin deploys directly into the Fabric ecosystem.The conversation explores:

• OneLake integration
• Unified governance
• Data lineage
• Sensitivity labels
• Access control
• Operational and analytical convergenceThe result is a backend architecture where governance becomes a native platform capability instead of an afterthought.

CODE-FIRST GOVERNANCE

Most organizations treat governance as something that happens after deployment.This episode challenges that model entirely.With Rayfin, governance becomes part of the backend definition itself.Topics covered include:

• Governance as code
• Version-controlled policies
• Data classification
• Access control definitions
• Security by design
• Compliance automationListeners discover how governance shifts from documentation into executable architecture.

THE STRANGLER FIG MODERNIZATION STRATEGY

One of the most practical sections focuses on modernization.Organizations rarely have the luxury of rebuilding everything from scratch.Instead, the episode explores the Strangl...