The two companies are expanding their partnership in 2026, connecting enterprise applications, cloud infrastructure, AI agents, and business data. The latest developments highlight how organizations can bring SAP processes into Microsoft productivity tools while maintaining security and governance.
At Microsoft Ignite 2026, the companies are presenting innovations involving SAP Joule, Microsoft 365 Copilot, Microsoft Fabric, Azure infrastructure, and intelligent agents.
Moreover, their joint efforts extend beyond connecting applications. It brings enterprise data, employee workflows, and AI capabilities into a more connected operating environment.
SAP continues to manage essential business processes such as finance, procurement, supply chain, and human resources. Meanwhile, Microsoft provides infrastructure, collaboration tools, analytics, and AI development capabilities.
However, these integrations introduce important questions about identity management, business authorization, data governance, and operational ownership.
This article explores the major developments in 2026, including Microsoft Ignite announcements and the technical considerations for enterprise implementation.
Quick Answer: What Is Changing in 2026?
Their partnership connects enterprise technologies across five major areas: cloud infrastructure, business data, AI agents, application development, and security.
Microsoft Azure supports SAP workloads, while SAP Joule and Microsoft 365 Copilot enable bidirectional AI experiences.
Additionally, SAP Business Data Cloud and Microsoft Fabric provide enterprise data connectivity, and Microsoft Copilot Studio supports custom AI agents.
The partnership also introduces developments in Azure operations, ABAP development, and security monitoring.
The central objective is to connect SAP business processes with Microsoft tools without replacing SAP’s role as the system of record.
How the Two Platforms Work Together in 2026
Their enterprise collaboration spans several connected technology areas.
SAP provides enterprise applications, business processes, and transactional data. Microsoft contributes cloud infrastructure, workplace applications, analytics services, and AI development tools.
Consequently, organizations can connect business information with the applications employees already use.
Where Each Technology Fits
| Technology | Primary Responsibility | Enterprise Use |
| SAP S/4HANA | Core ERP transactions | Finance, procurement, and supply chain |
| Microsoft Azure | Cloud infrastructure | Hosting supported SAP workloads |
| SAP Business AI Platform | Enterprise AI foundation | Development, data, and agent governance |
| SAP Joule | SAP AI assistance | Accessing SAP business information |
| Microsoft 365 Copilot | Productivity AI | Workflows across Microsoft 365 |
| Microsoft Fabric | Analytics and data services | Combining SAP and non-SAP information |
| Microsoft Copilot Studio | Custom AI agents | Business-specific AI workflows |
| Microsoft Sentinel for SAP | Security monitoring | SAP security signals and threat detection |
These technologies complement one another, but they are not interchangeable.
For example, accessing SAP financial information through Microsoft Copilot does not transfer ownership of the underlying transaction to Microsoft.
Instead, the relevant SAP application continues enforcing its business rules and authorizations.
Major Technology Announcements at Ignite 2026
Microsoft Ignite 2026 takes place from November 17–20 at Moscone Center in San Francisco.
SAP is participating at Booth 5679, highlighting developments across data, AI, applications, agents, and cloud technology.
Furthermore, SAP’s event program focuses on connecting the systems that run enterprise operations with the tools employees use throughout their working day.
1. SAP Joule and Microsoft 365 Copilot Integration
One of the central themes is the bidirectional integration between SAP Joule and Microsoft 365 Copilot.
Employees using Microsoft applications can access relevant SAP capabilities through supported AI interactions.
Meanwhile, users working with Joule can retrieve Microsoft 365 context.
This approach connects SAP business information with workplace activities involving documents, messages, meetings, and other productivity tools.
Microsoft also announced enhancements involving Work IQ, its workplace intelligence layer.
Consequently, the integration can bring together SAP business context and Microsoft workplace information when supporting enterprise decisions.
2. SAP Business Data Cloud and Microsoft Fabric
Both companies are also highlighting enterprise data integration.
SAP Business Data Cloud provides governed business information, while Microsoft Fabric supports analytics and data workflows.
Their integration is intended to connect SAP data with information from other enterprise systems.
Furthermore, SAP’s Microsoft Ignite program emphasizes the role of unified business data in supporting reliable AI outcomes.
3. Enterprise AI Agents and Governance
The partnership includes developments involving SAP AI Agent Hub, Microsoft Copilot Studio, and agent connectivity.
These technologies support AI agents that interact with different enterprise applications.
However, agent interoperability requires clear authorization, monitoring, and governance.
Both organizations are therefore expanding their approaches to managing agents across connected environments.
4. SAP Workloads on Azure
Microsoft announced additional Azure infrastructure capabilities for mission-critical SAP systems.
These include new virtual machine families, expanded memory options, and improvements to workload operations.
Additionally, Microsoft is introducing agent-supported capabilities for managing SAP environments running on Azure.
5. Security and ABAP Development
The Ignite announcements also address SAP security monitoring and development modernization.
Microsoft Sentinel for SAP is expanding its coverage of SAP applications and related environments.
Meanwhile, ABAP Development Tools for Visual Studio Code and GitHub Copilot provide additional options for SAP developers.
Together, these developments show that the partnership extends across infrastructure, application development, and enterprise operations.
1. SAP on Microsoft Azure: Modernizing Enterprise Infrastructure
Microsoft Azure provides infrastructure for running supported SAP applications and databases.
Organizations can deploy relevant SAP workloads on Azure virtual machines, including supported SAP HANA environments.
However, infrastructure selection must account for SAP certification, storage, networking, security, and operational requirements.
Azure Mv4 Virtual Machines for SAP Workloads
At Microsoft Ignite 2026, Microsoft announced developments involving its Azure Mv4 virtual machine portfolio.
The infrastructure uses Intel Xeon 6 processors and Azure Boost v2.
Furthermore, the portfolio includes different configurations for memory-intensive and storage-intensive workloads.
The announced options include:
- Mv4 Medium Memory: Generally available, supporting up to 4 TB of memory and 256 vCPUs.
- Mv4 CXL: Private preview, with memory expansion supporting up to 8 TB and 304 vCPUs.
- Mbv4: Public preview, optimized for storage-intensive workloads.
These options provide different infrastructure capabilities for relevant enterprise applications.
However, organizations must verify the certification and availability requirements for their intended SAP workloads.
Agentic Operations for SAP on Azure
Microsoft also announced a limited preview of Azure Workload Center for SAP and the Azure Copilot Run SAP Agent.
These capabilities are intended to support SAP workload management through AI-assisted operations.
Organizations can onboard SAP systems running on Azure as Workload Virtual Instances.
Consequently, IT teams can explore additional agent-supported capabilities for monitoring and troubleshooting operational environments.
The announced preview status remains an important consideration when evaluating implementation plans.
RISE with SAP on Microsoft Azure
RISE with SAP on Azure provides another approach to cloud ERP modernization.
Unlike a customer-managed SAP deployment on Azure infrastructure, RISE with SAP involves a different operating and service arrangement.
The two companies continue developing joint support and modernization initiatives.
Nevertheless, businesses must confirm the responsibilities established by their specific service agreements.
2. SAP Joule and Microsoft 365 Copilot: Connecting AI With Workflows
SAP Joule and Microsoft 365 Copilot address different parts of enterprise work.
Joule focuses on supported SAP business processes and information.
Microsoft 365 Copilot provides AI assistance across Microsoft workplace applications.
However, their integration allows employees to work across these environments without treating every task as a separate application interaction.
How Bidirectional Integration Works
The managed integration provides a connection between SAP Joule and Microsoft Copilot.
Users can submit SAP-related requests through supported Microsoft experiences.
Joule then processes the request through the relevant SAP capabilities.
Meanwhile, Joule users can access Microsoft 365 information through the connected experience.
This integration was reported as generally available earlier in 2026.
Bringing SAP Context Into Microsoft Teams
Microsoft’s documentation describes users interacting with SAP through Microsoft Teams, Outlook, Excel, and Copilot Chat.
For example, a procurement employee may request the status of a purchase order stored in SAP.
The supported AI integration can provide access to the relevant information without requiring the employee to navigate directly to the traditional SAP interface.
However, the SAP application must still apply the appropriate authorization controls.
Microsoft Work IQ and Enterprise Context
Microsoft is expanding its Joule integration through Work IQ.
Work IQ connects workplace knowledge, documents, communications, and user activities with relevant business information.
Furthermore, SAP data can contribute operational context to AI-supported decisions.
This enables AI experiences to consider both business transactions and the surrounding workplace information.
Nevertheless, the available functionality depends on the configured integration and relevant access permissions.
3. SAP Business Data Cloud and Microsoft Fabric: Connecting Enterprise Data
Enterprise information often exists across ERP applications, analytics platforms, and departmental systems.
SAP Business Data Cloud and Microsoft Fabric address different parts of this environment.
SAP Business Data Cloud focuses on governed enterprise data and its business meaning.
Meanwhile, Microsoft Fabric provides capabilities for analytics, data engineering, and reporting.
Business Data Cloud Connect for Microsoft Fabric
They have announced capabilities connecting SAP Business Data Cloud with Microsoft Fabric.
The integration includes zero-copy data-sharing approaches for supported scenarios.
Consequently, organizations can use SAP business data in broader analytical environments without relying on traditional data-copying approaches for every supported workflow.
SAP’s business data products preserve relevant business context.
Microsoft Fabric then supports analytics involving SAP and non-SAP information.
Why Business Context Matters for AI
An AI model needs more than access to business records.
For example, financial information must be interpreted according to its relevant accounting and organizational context.
Similarly, supply chain information depends on the meaning of inventory, delivery, and transaction records.
SAP Business Data Cloud provides business context intended to support these interpretations.
Furthermore, the SAP Knowledge Graph connects business entities and their relationships.
These capabilities help support AI applications that require meaningful enterprise information.
Data Governance Remains Essential
Connecting data platforms does not automatically resolve source-system data quality issues.
Businesses must still establish ownership, permissions, and consistent data definitions.
Additionally, analytical integrations must protect sensitive business information.
Therefore, organizations should evaluate data governance alongside technical connectivity.
4. Microsoft Copilot Studio and Foundry: Building Custom SAP AI Agents
Microsoft provides several approaches for connecting AI to SAP environments.
The supplied Microsoft documentation describes three complementary layers: managed Joule integration, Copilot Studio, and Microsoft Foundry.
These options address different levels of development complexity.
Managed Integration: Joule and Copilot
The managed integration offers a prebuilt connection between SAP Joule and Microsoft Copilot.
It is intended for organizations that want to access supported SAP capabilities through Microsoft productivity experiences.
Furthermore, Microsoft identifies this approach as an option for beginning without custom agent development.
However, the organization still requires the appropriate product configuration and access rights.
Low-Code Development: Microsoft Copilot Studio
Copilot Studio supports creating business-specific AI agents.
These agents can connect to SAP data through supported connectors, APIs, and custom integrations.
Additionally, organizations can deploy supported agents through Microsoft Teams, Microsoft Copilot, and other relevant channels.
This option is suitable when standard AI capabilities do not fully address a particular business process.
Advanced AI Development: Microsoft Foundry
Microsoft Foundry supports more complex AI development scenarios.
These include custom models, multi-agent orchestration, MCP tools, and deeper integration with SAP interfaces.
Consequently, developers can create AI solutions that coordinate multiple activities across connected systems.
However, these solutions introduce additional technical responsibilities involving authorization, application design, and operational monitoring.
Which AI Development Option Should Organizations Choose?
| Business Requirement | Technology | Development Approach | Main Consideration |
| Access SAP information through Microsoft productivity tools | Joule and Microsoft Copilot | Managed integration | Supported capabilities and permissions |
| Build a business-specific AI assistant | Copilot Studio | Low-code development | Connectors and business rules |
| Create advanced multi-agent solutions | Microsoft Foundry | Professional development | Orchestration and governance |
| Connect SAP APIs with Microsoft agents | SAP Integration Suite MCP Gateway | Integration development | API permissions |
| Coordinate agents across environments | SAP agent gateway and Microsoft services | Agent interoperability | Availability and trust |
| Manage enterprise agent access | SAP AI Agent Hub and Microsoft Agent 365 | Governance architecture | Registration and observability |
The correct selection depends on the intended workflow, existing applications, and the organization’s technical requirements.
5. Enterprise Security: Protecting Connected Applications
As SAP applications connect with additional cloud services and AI agents, security becomes increasingly important.
Business systems may contain sensitive financial, employee, and operational information.
Therefore, connected AI experiences must respect application permissions and enterprise security policies.
Microsoft Sentinel for SAP
Microsoft Sentinel for SAP provides security monitoring capabilities involving SAP environments.
The 2026 announcements highlight expanded coverage across SAP S/4HANA, SAP BTP, SAP Ariba, and SAP SuccessFactors.
Furthermore, Microsoft described integration of SAP security signals with broader Microsoft security operations.
This allows security teams to examine SAP activity alongside relevant identity, cloud, and endpoint information.
Microsoft Defender and SAP Security
Microsoft Defender is also being developed to recognize SAP devices as critical assets.
Additionally, Microsoft discussed AI-supported remediation capabilities within its wider security environment.
However, organizations must distinguish currently available product functionality from emerging agent capabilities.
Microsoft Entra ID Governance
Microsoft Entra ID Governance supports identity lifecycle and access management.
The supplied announcements describe integration with SAP Identity Access Governance.
This can support SAP business role requests while preserving relevant approval and risk checks.
Furthermore, organizations migrating from SAP Identity Management can examine supported Microsoft identity governance options.
Maintaining SAP Authorization
Microsoft’s SAP AI documentation emphasizes maintaining SAP authorization rules.
An employee authenticated within Microsoft 365 should not automatically gain unrestricted access to SAP.
Instead, the connected application must enforce the permissions associated with the user’s SAP identity.
Consequently, identity mapping and authorization remain essential to reliable enterprise AI integration.
6. Modernizing ABAP Development With Microsoft Tools
The collaboration is also expanding around application modernization.
ABAP remains an important part of many existing SAP environments.
However, developers increasingly use modern development tools and AI assistance to maintain and improve enterprise applications.
ABAP Development Tools for Visual Studio Code
Microsoft’s Ignite announcements highlight ABAP Development Tools for Visual Studio Code.
These capabilities support creating, editing, debugging, and managing supported ABAP development artifacts.
Furthermore, developers can access GitHub Copilot capabilities, including chat and inline suggestions.
The objective is to connect ABAP development with modern development environments.
GitHub Copilot and Agent-Supported Development
GitHub Copilot provides AI assistance during software development.
Within supported SAP environments, developers can use AI-assisted workflows to work with relevant development artifacts.
However, generated changes still require technical review and validation.
SAP development rules and application authorization requirements continue to apply.
Why Existing SAP Development Knowledge Matters
Many SAP environments contain custom ABAP developments created over extended periods.
These applications may represent important business processes and technical requirements.
Consequently, modernization should preserve relevant business functionality while evaluating supported development approaches.
These announcements position developer tooling as another part of the broader enterprise modernization partnership.
7. Real Business Applications of SAP and Microsoft Integration
The supplied Microsoft research includes customer examples showing how these technologies are used together.
These cases illustrate different combinations of enterprise AI, automation, analytics, and cloud infrastructure.
Cemex: AI-Supported HR Services
Cemex developed Consult HR using Microsoft Copilot Studio.
The solution connects Microsoft Teams, ServiceNow, and SAP SuccessFactors.
According to Microsoft’s October 2026 announcement, the application provides 24-hour HR self-service access for 800 employees.
This example shows how SAP information can support employee services through familiar workplace applications.
Rio Tinto: Financial Process Automation
Rio Tinto connected Microsoft Power BI, Power Apps, and Power Automate with SAP.
Microsoft reported that the integration helped reduce month-end closing time for its largest product group from three to four days to two days.
Consequently, the example demonstrates how connected reporting and automation can support financial operations.
These results reflect the reported customer implementation rather than a guaranteed outcome for other organizations.
Al-Futtaim: Enterprise Data and AI
Al-Futtaim combines RISE with SAP S/4HANA on Azure with Microsoft Fabric, Azure Databricks, Microsoft 365 Copilot, and SAP Joule.
The architecture connects SAP business data with analytics and AI-supported workflows.
Furthermore, the example demonstrates how enterprise organizations can use multiple SAP and Microsoft technologies together.
Cenibra: Identity Governance Modernization
Cenibra migrated from SAP Identity Management to Microsoft Entra ID Governance across more than 80 systems, including SAP.
Microsoft reported a 46% operational improvement during the first migration wave.
Additionally, the implementation reduced manual work and supported audit readiness.
These reported outcomes are specific to Cenibra’s project.
What Enterprises Should Consider Before Connecting These Platforms
The partnership provides several technology options, but organizations should not assume every capability is necessary.
Instead, the architecture should begin with the intended business process.
Evaluate Existing SAP Systems
Identify the relevant SAP applications, deployed infrastructure, and available interfaces.
Furthermore, determine which business records and transactions must remain within SAP.
Select the Appropriate AI Development Approach
Use the managed Joule and Copilot integration when it meets the requirement.
Consider Copilot Studio when a custom business agent is necessary.
Meanwhile, evaluate Microsoft Foundry for advanced development and orchestration scenarios.
Review Data Governance
Confirm how SAP business information will be accessed, interpreted, and protected.
Additionally, assess whether the chosen Microsoft services require integration with SAP Business Data Cloud or other relevant data capabilities.
Validate Security and Operations
Determine how users and agents authenticate across the connected environment.
Application permissions, monitoring, and incident responsibilities should be clearly defined.
Finally, organizations should confirm product availability, licensing, and supported configurations before implementation.
Recent Partnership Announcements in 2026
May 12, 2026: SAP Introduces the Autonomous Enterprise
At SAP Sapphire 2026, SAP announced its Autonomous Enterprise vision.
The announcement introduced SAP Business AI Platform, SAP Autonomous Suite, and Joule Work.
Furthermore, SAP highlighted expanded partnerships with Microsoft and other technology providers.
Source: SAP News, SAP Unveils the Autonomous Enterprise.
October 26, 2026: SAP on Azure Developments at SAP TechEd
Microsoft published updates concerning SAP Joule and Microsoft Copilot, SAP security, AI integration, and Azure infrastructure.
The announcements included developments involving MCP connectivity, SAP OData authentication, identity governance, and deployment automation.
Source: Microsoft Tech Community, SAP on Azure Product Announcements Summary – SAP TechEd 2026.
November 17, 2026: Microsoft Ignite Partnership Announcements
Microsoft announced developments involving Azure Mv4 infrastructure, agentic operations for SAP workloads, Work IQ integration, enterprise security, and ABAP development tools.
The announcement also highlighted SAP Business Data Cloud connectivity with Microsoft Fabric.
Source: Microsoft Tech Community, Microsoft and SAP at Ignite 2026: Connecting SAP Customers to AI Agents, Data, and Security.
Frequently Asked Questions
1. How Do These Two Companies Work Together?
The two companies collaborate across cloud infrastructure, enterprise AI, data analytics, security, and productivity applications. Microsoft Azure supports relevant SAP workloads, while SAP Joule and Microsoft 365 Copilot provide connected AI experiences. Furthermore, SAP Business Data Cloud and Microsoft Fabric support enterprise data integration. Copilot Studio and Foundry provide additional options for developing custom agents. However, SAP applications continue managing their underlying business transactions. Organizations must evaluate supported integration capabilities, user permissions, and operational responsibilities before implementing connected solutions.
2. Can SAP S/4HANA run on Microsoft Azure?
Yes. Supported SAP S/4HANA environments can run on Microsoft Azure infrastructure. Organizations must select appropriate Azure virtual machines, operating systems, storage configurations, and database environments. Furthermore, SAP HANA workloads require relevant certified configurations. Microsoft announced additional Azure Mv4 infrastructure options in 2026, including different memory and storage capabilities. However, not every Azure configuration automatically supports every SAP release. Technical teams should verify SAP certification, software compatibility, infrastructure availability, and operational requirements before deploying production workloads.
3. What is the difference between SAP Joule and Microsoft 365 Copilot?
SAP Joule focuses on AI assistance involving supported SAP business applications and processes. Microsoft 365 Copilot provides AI capabilities across Microsoft productivity environments. Their managed integration connects these experiences so users can access relevant SAP information from Microsoft applications and Microsoft 365 context from Joule. Furthermore, Microsoft is expanding integration through Work IQ. However, both tools continue operating within their relevant application and permission boundaries. The connected experience does not automatically provide unrestricted access to enterprise records.
4. Can Microsoft Copilot access SAP data?
Microsoft Copilot can access supported SAP information through configured integration options. One approach uses the managed connection between SAP Joule and Microsoft 365 Copilot. Additionally, organizations can create custom agents through Copilot Studio or Foundry using supported connectors and APIs. Access depends on the relevant application configuration, identity mapping, and SAP authorization requirements. Therefore, having access to Microsoft Copilot does not automatically grant permission to retrieve or modify protected SAP records. Businesses should verify security and integration conditions for each intended scenario.
5. What is SAP Business Data Cloud integration with Microsoft Fabric?
SAP Business Data Cloud integration with Microsoft Fabric connects governed SAP business information with Microsoft’s analytics environment. The announced approach includes zero-copy data sharing for supported scenarios. Consequently, organizations can use relevant SAP data products within broader analytics and AI workflows. However, data integration still requires consistent business definitions, appropriate permissions, and source-system data quality. The integration does not replace SAP’s role in managing operational transactions. Businesses should also confirm the availability and entitlements applicable to their intended environment.
6. What is RISE with SAP on Microsoft Azure?
This cloud ERP arrangement combines SAP services with Microsoft Azure infrastructure. The two companies continue developing joint initiatives to support cloud modernization and enterprise AI adoption. However, the service responsibilities differ from those of a customer-managed SAP environment on Azure. Organizations must examine the specific commercial and operational agreements governing their deployment. Furthermore, implementation planning should cover integration, data requirements, security, and business continuity rather than considering cloud infrastructure alone.
7. Can Microsoft Copilot Studio build AI agents for SAP?
Yes. Microsoft Copilot Studio supports the development of custom AI agents that can interact with SAP through supported connectors, APIs, and integration services. These agents can be designed around specific business requirements and deployed through supported Microsoft experiences. Additionally, Microsoft Foundry provides capabilities for more complex AI solutions. However, custom agents require appropriate configuration, security controls, testing, and operational governance. The availability of low-code development tools does not eliminate the need to validate the underlying SAP business processes.
8. How does Microsoft Sentinel protect SAP environments?
Microsoft Sentinel for SAP supports security monitoring by collecting and analyzing relevant SAP security information. The 2026 announcements describe expanded coverage involving SAP S/4HANA, SAP BTP, SAP Ariba, and SAP SuccessFactors. Furthermore, Microsoft is connecting SAP security signals with broader identity, endpoint, and cloud security information. This can help security teams investigate activity across connected environments. However, organizations must configure supported integrations and determine which monitoring capabilities apply to their SAP landscape and operational requirements.
9. What Were the Major Partnership Announcements at Ignite 2026?
The 2026 event announcements covered Azure infrastructure, enterprise AI, business data, security, and application development. Microsoft introduced developments involving Azure Mv4 virtual machines, Azure Workload Center for SAP, and Azure Copilot Run SAP Agent. Additionally, the companies highlighted bidirectional Joule and Microsoft Copilot integration, Work IQ, SAP Business Data Cloud, Microsoft Fabric, and enterprise agent governance. The announcements also included security improvements and ABAP development tooling. However, availability varies between generally available products and preview capabilities.
10. What should enterprises consider before integrating SAP with Microsoft AI?
Enterprises should begin by identifying the business processes that require integration. Next, they should determine whether managed Joule integration, Copilot Studio, or Microsoft Foundry is the appropriate option. Furthermore, teams must review SAP authorizations, data governance, identity management, and operational monitoring. Existing SAP interfaces and application responsibilities should remain clearly defined. Finally, businesses should verify supported functionality, licensing, and deployment requirements before implementation. The objective is to connect AI capabilities with enterprise workflows while maintaining appropriate business controls.
Conclusion
This partnership in 2026 reflects an expanding relationship between enterprise applications, cloud technology, business data, and AI.
Microsoft Azure provides infrastructure for supported SAP workloads, while Joule and Microsoft 365 Copilot connect business information with workplace applications.
Furthermore, SAP Business Data Cloud and Microsoft Fabric create additional opportunities for governed data integration and analytics.
Developments involving Copilot Studio, Microsoft Foundry, and agent connectivity also extend the partnership into custom enterprise AI solutions.
However, these capabilities do not remove the importance of application ownership, security, and operational governance.
The strongest approach begins with existing SAP processes, selects appropriate Microsoft capabilities, and maintains the controls required for reliable enterprise operations.
References
- SAP Events. SAP at Microsoft Ignite 2026. Event program, November 17–20, 2026.
- Microsoft Learn. About SAP with Microsoft AI. Documentation covering Joule, Copilot Studio, and Microsoft Foundry.
- Microsoft Tech Community. Microsoft and SAP at Ignite 2026: Connecting SAP Customers to AI Agents, Data, and Security. November 17, 2026; updated November 18, 2026.
- SAP News. SAP Unveils the Autonomous Enterprise. May 12, 2026.
- Microsoft Tech Community. SAP on Azure Product Announcements Summary – SAP TechEd 2026. October 26, 2026.
- Naresh Koka. SAP Sapphire 2026: When the Wall Between SAP and Microsoft Came Down. LinkedIn, May 19, 2026.
- Supplied research draft. SAP and Microsoft in 2026 — Where Cloud, AI and Enterprise Workflows Come Together.