When Azure SQL Becomes an Application Platform- APIs, Automation and AI with Dirceu Resende

When Azure SQL Becomes an Application Platform- APIs, Automation and AI with Dirceu Resende is explained in this M365 FM video guide. Learn what it is, why it matters, and the core capabilities, practical use cases and implementation considerations to understand before applying it in a real organization.

Most developers think of a database as the place where an application stores information. Tables, transactions, indexes, stored procedures, reporting, backups, and reliable data storage are the traditional responsibilities we associate with SQL. But what happens when the database itself becomes an active participant in the application architecture? In this episode of M365 FM, Mirko Peters talks with Dirceu Resende about how Azure SQL Database is evolving beyond traditional data storage. The conversation explores REST API integration, automation, external services, security, performance, Microsoft Fabric, Power BI, AI, vector search, RAG, observability, and the changing architectural role of databases inside modern applications. Dirceu brings a combination of database, business intelligence, Microsoft, and community experience to the discussion. His career spans database development and performance tuning, business intelligence, Power BI, and cloud technologies, including previous work at Microsoft as a Senior Program Manager for Power BI.

AZURE SQL DATABASE IS BECOMING MORE THAN A DATABASE
Azure SQL Database provides the familiar relational capabilities of SQL Server while removing much of the infrastructure management traditionally associated with running a production database. Organizations can use a managed cloud database without having to directly maintain the underlying operating system and infrastructure. Azure also provides capabilities around security, availability, backups, performance, and integration with other cloud services. But Dirceu argues that one of the most interesting developments is what Azure SQL can now do outside the traditional boundaries of the database. Azure SQL Database can make HTTP requests and communicate with external services. This creates scenarios where the database can participate directly in workflows that previously required another application or integration layer. The database is no longer necessarily waiting passively for an application to tell it what to do.

AZURE SQL DATABASE VS MANAGED INSTANCE VS SQL SERVER
Choosing the correct SQL deployment model still depends heavily on application architecture. Dirceu explains that Azure SQL Managed Instance provides an experience closer to traditional SQL Server. It supports scenarios involving multiple databases within an instance and capabilities that organizations migrating existing SQL Server workloads may require. Azure SQL Database is more naturally aligned with independent databases and architectures where applications or microservices have separate database resources. If an application depends heavily on cross-database queries, linked services, SQL CLR, or other traditional SQL Server capabilities, migration may require architectural changes rather than simply moving the existing database into Azure SQL Database unchanged. This makes workload assessment an important part of any SQL modernization strategy. 

WHY AZURE SQL FITS MODERN APPLICATION ARCHITECTURES
Moving data into Azure can make integration with other Azure and Microsoft services significantly easier. Applications running through services such as Azure App Service, containers, or Kubernetes can operate closer to the database. Microsoft Fabric and Power BI can also consume Azure SQL information through increasingly integrated architectures. Azure SQL Database additionally receives cloud capabilities that may arrive later in traditional SQL Server releases. Dirceu highlights sp_invoke_external_rest_endpoint as an important example because it allows Azure SQL Database to communicate directly with REST endpoints. That seemingly simple capability fundamentally changes what developers can consider doing inside or close to the database.

WHEN THE DATABASE BECOMES AN ACTIVE APPLICATION COMPONENT
Traditional application architecture often places the database behind an application layer. The application receives requests, executes business logic, communicates with other systems, and finally reads or writes information to the database. That separation remains useful and appropriate in many architectures. But Azure SQL can now perform more activities independently. Dirceu describes scenarios where the database can retrieve information from an external API, combine it with application data, work with information stored in Azure Blob Storage, and initiate other processes without requiring a separate application to orchestrate every individual step. This does not mean developers should move every application function into SQL. It means architects now have another optio