Microsoft and Oracle used the opening day of Microsoft Ignite on November 17, 2026 to announce a set of new integrations built on Oracle AI Database@Azure. The headline items are an Oracle AI Database plug-in for Excel, available now, and a limited preview of Azure Workload Center for Oracle for IT operations teams.
The two companies also described managed Model Context Protocol (MCP) servers that give Microsoft Foundry agents a controlled path into Oracle AI Database. For Oracle shops on Azure, the message is clear: AI agents and business users should work with Oracle data where it lives, under existing identity and access rules, rather than copying it elsewhere.
What Was Announced
The announcement was co-written by Microsoft with Oracle database and multicloud leaders. It groups the news by audience: IT operations, business users and developers.
- Excel plug-in for Oracle AI Database: out now, it links a worksheet straight to Oracle Database so users can pull data in and analyze it with Copilot.
- Azure Workload Center for Oracle: in limited preview, it brings the parts of an Oracle workload together into one managed view.
- Managed MCP servers: a controlled route for Azure-based agents into Oracle data, for databases hosted in OCI as well as those running inside Azure.
- Identity and audit: sign-in through Microsoft Entra combined with Oracle Deep Data Security, so agents act within the signed-in user's rights.
Microsoft also said Oracle AI Database@Azure now runs in 33 Azure regions. It repeated two items first shown at Oracle AI World 2026: FedRAMP Class D certification coming for US public-sector use, and Proximity Placement Groups that cut VM-to-Exadata round-trip latency by about half.
Azure Workload Center for Oracle
The new workload center models each Oracle deployment as a Workload Virtual Instance, or WVI. This object ties together the architecture, resources and dependencies of one workload, so admins can manage it as a unit instead of one component at a time.
The WVI connects with Azure Monitor Health Models and an Azure Copilot agent for running Oracle. Together they link health signals from the application, database and infrastructure layers into one picture.
Microsoft's example is a slow order processing app. An admin signs in with Entra, sees a combined health view, and asks in plain language for an investigation. Several agents then look into the problem, each limited by the admin's identity profile, and every database call they make goes through the managed MCP server and is logged for audit.
Oracle Data in Excel and Copilot
The Excel plug-in targets analysts who today wait for a technical colleague to extract and format Oracle data. With it, they connect from the spreadsheet itself and ask Copilot questions about the rows they pulled in, with no export step.
Copilot can also combine Oracle transaction data with context from Microsoft Work IQ, which draws on meetings, email, documents and Teams. Microsoft says this can flag exceptions, write an explanation and prepare an action plan that a person reviews before anything happens.
What It Means for Developers
The MCP piece is the most important part for Oracle developers. Rather than giving an agent a raw database account, IT publishes a vetted list of queries, PL/SQL calls, tools and canned reports. Application roles then decide which of those tools each user or group may call.
This fits a pattern Oracle has pushed all year with Deep Data Security: keep authorization inside the database, and let every client, including AI agents, inherit it. If you already write well-scoped PL/SQL APIs for your applications, those same APIs make natural MCP tools. Treat each tool like a public endpoint, with tight parameters and clear limits.
Foundry agents can also use the A2A protocol to coordinate with each other. Microsoft's sample shows one agent reading accounts and orders from Oracle through MCP while others handle product and finance checks. Teams should plan for audit review, since every agent call is captured.
How to Get Started
The Excel plug-in is available today, so Oracle AI Database@Azure customers can try it with a read-only account first. Azure Workload Center for Oracle is a limited preview, which usually means a sign-up and a small customer group.
Microsoft is running Ignite session BRK435 on workload intelligence and AI operations, and Oracle has a theater session, THRSP1082, on the workload center. Developers who want to try agents should start in Microsoft Foundry and review the managed MCP server setup for their database.
Conclusion
The Ignite news moves Oracle AI Database@Azure beyond hosting into daily tools such as Excel, Teams and Copilot. The Excel plug-in is ready now, while the workload center is still early.
For developers, the managed MCP servers and role-based tool access are the parts to watch. To see how Oracle enforces data rules for agents and apps, read our earlier report on Oracle Deep Data Security with APEX and ORDS.
Sources
See my articles more often when you search Google.
