Services / Cloud Infrastructure / Data, AI & Skills
Cloud Infrastructure · Data, AI & Skills

Bring SAP into the tools people use all day, Teams, Outlook, Excel and Copilot.

We connect SAP with Microsoft 365, from Joule and Microsoft 365 Copilot working together to SAP apps in Teams, SAP data in Excel and single sign-on with Microsoft Entra ID. Your people get SAP answers and tasks where they already work, with identity and access controlled in one place.

Talk to a cloud architect →See how it works
TeamsFirst access point for Joule from Microsoft 365 Copilot
2027SAP Identity Management maintenance ends; Entra ID is a migration path
Nov 2025SAP BDC Connect for Microsoft Fabric announced, zero-copy to OneLake
Why it matters

Why connect SAP and Microsoft 365

Most SAP users spend their day in Outlook, Teams and Excel, and switch to SAP only to approve, check or update something. Every switch costs time, and data copied into spreadsheets or emails goes stale and escapes access controls. SAP and Microsoft now offer joint integrations, from Joule working with Microsoft 365 Copilot to SAP Fiori apps shared in Teams. Setting them up well depends on identity, licensing and security being right first.

Less switching between apps

Joule and Microsoft 365 Copilot work in both directions, so users can reach SAP tasks and data from Copilot, and Microsoft 365 information from Joule. Responses show which assistant produced them.

Collaboration on live SAP data

The SAP S/4HANA for Microsoft Teams app lets users share SAP Fiori app content as a chat link, tab or card, and receive SAP task notifications in the Teams activity feed.

One identity for everything

Microsoft Entra ID can act as the identity provider for SAP applications through SAP Cloud Identity Services, and provision users into SAP systems. Leavers lose access everywhere at once.

A deadline for SAP Identity Management

SAP Identity Management maintenance ends in 2027, with extended support to 2030. Microsoft publishes guidance for moving those scenarios to Microsoft Entra ID.

What we do

What we do

We plan, configure and support the integrations between your SAP landscape and Microsoft 365.

01

Joule and Microsoft 365 Copilot

We check prerequisites, activate Joule in your SAP landscape and connect it to your Microsoft 365 Copilot tenant. The integration is opt-in, so we agree the scenarios and user groups before switching it on.

02

SAP in Microsoft Teams

We deploy the SAP S/4HANA for Microsoft Teams app so users can share SAP Fiori content and get task notifications in Teams. We configure the Teams admin policies and SAP roles that control who sees what.

03

SAP data in Excel

We set up the SAP Analytics Cloud add-in for Microsoft Excel for reporting and planning on SAP Analytics Cloud models, SAP Datasphere and SAP S/4HANA Cloud CDS views. Finance teams keep Excel while the numbers stay governed.

04

Single sign-on and provisioning with Entra ID

We connect Microsoft Entra ID with SAP Cloud Identity Services for single sign-on and user provisioning into SAP cloud and on-premise systems. We add conditional access and multifactor authentication for SAP access.

05

SAP Identity Management migration

We assess your SAP Identity Management scenarios and plan the move to SAP Cloud Identity Services and Microsoft Entra ID Governance. We keep joiner, mover and leaver processes running during the change.

06

SAP data in Microsoft Fabric and Power BI

We share SAP Business Data Cloud data products into Microsoft Fabric with SAP BDC Connect, or replicate with SAP Datasphere where needed. Users then analyse SAP data in Power BI, Excel and Teams.

How it works

How it works

  1. 1

    Assess

    We review your SAP products, Microsoft 365 licences, Entra ID setup and SAP identity processes. We list which integrations are available for your SAP releases and region.

    1 to 2 weeks
  2. 2

    Fix identity first

    We align user identities between SAP and Entra ID, set up SAP Cloud Identity Services and enable single sign-on. Everything else depends on this step.

    2 to 4 weeks
  3. 3

    Pilot

    We switch on the chosen integrations, such as Joule with Microsoft 365 Copilot or SAP apps in Teams, for a pilot group. We collect feedback and check security and data access.

    3 to 6 weeks
  4. 4

    Roll out

    We extend to more users with training, guides and support. We monitor usage and adjust roles and policies.

    4 to 8 weeks
  5. 5

    Support and extend

    We keep integrations working through SAP and Microsoft updates and add new scenarios as they become available.

    Ongoing
Across AWS, Azure and Google Cloud

Equivalent services per cloud

Most customers pair SAP with Microsoft 365, but similar building blocks exist on each cloud.

NeedAWSMicrosoft AzureGoogle Cloud
Identity provider for SAP single sign-onAWS IAM Identity CenterMicrosoft Entra IDCloud Identity
AI assistant for employeesAmazon QuickMicrosoft 365 CopilotGemini Enterprise
Low-code agent buildingAmazon Bedrock AgentCoreMicrosoft Copilot StudioGemini Enterprise Agent Platform
Zero-copy SAP data sharingSAP Business Data Cloud on AWSSAP BDC Connect for Microsoft FabricSAP BDC Connect for BigQuery
Business intelligence on SAP dataAmazon QuickPower BILooker
Workflow integration with SAPAWS Step FunctionsAzure Logic Apps SAP connectorApplication Integration
For SAP landscapes

The SAP angle

SAP and Microsoft have built integrations on both sides. On the SAP side, Joule is SAP's AI assistant, and its integration with Microsoft 365 Copilot is activated through SAP AI Units and needs a licensed Microsoft 365 Copilot environment and aligned identities. The SAP S/4HANA for Microsoft Teams app works with SAP S/4HANA Cloud and SAP S/4HANA, including from Outlook and Microsoft 365. Under RISE with SAP, SAP runs the SAP systems, but identity, Microsoft 365 configuration and the integration settings are still your responsibility, and that is where we help. For ECC customers, Entra ID can still provide single sign-on and provisioning, even before an S/4HANA move.

  • Joule and Microsoft 365 Copilot integration requires an activated Joule instance and a licensed Microsoft 365 Copilot environment.
  • The SAP S/4HANA for Microsoft Teams app supports sharing Fiori content as chat, tab or card, plus task notifications.
  • Microsoft Entra ID can provision users to SAP ECC, SAP S/4HANA on-premise and SAP cloud apps through SAP Cloud Identity Services.
  • SAP Identity Management reaches end of maintenance in 2027, so identity planning belongs in every ECC to S/4HANA roadmap.

© 2026 Mawkish Technologies. This guide, its diagrams and illustrations are protected by copyright. You’re welcome to learn from it and to quote it with credit and a link. Reproducing it, by hand or through AI, and publishing it as your own is not allowed. Read our copyright notice

What you get

Deliverables

  • Integration readiness report covering SAP releases, Microsoft 365 licences and identity
  • Single sign-on and user provisioning between Microsoft Entra ID and SAP
  • Joule and Microsoft 365 Copilot integration configured for agreed scenarios
  • SAP S/4HANA for Microsoft Teams app and SAP Analytics Cloud Excel add-in deployed
  • SAP Identity Management migration plan
  • User guides, admin runbooks and training for key users
Questions

Frequently asked

What does the Joule and Microsoft 365 Copilot integration do?

It lets users reach SAP tasks and data through Joule from Microsoft 365 Copilot, and Microsoft 365 information from Joule. Microsoft Teams is the first supported access point. The integration is opt-in and must be activated on both sides.

What do we need before we can use it?

You need an activated Joule instance in your SAP landscape, a licensed Microsoft 365 Copilot environment, aligned identities between SAP and Microsoft, and the trust configuration between the platforms. Use of the integration consumes SAP AI Units. We check each prerequisite and the availability for your country before starting.

We are still on SAP ECC. Can we connect it to Microsoft 365?

Partly. Microsoft Entra ID can provide single sign-on and user provisioning for SAP ECC, and Excel and Power BI can work with ECC data. Joule and the SAP S/4HANA for Microsoft Teams app are built for newer SAP solutions, so many customers plan them as part of the move to S/4HANA.

Should we replace SAP Identity Management with Microsoft Entra ID?

If you already run Microsoft Entra ID, it is a strong option. SAP Identity Management maintenance ends in 2027, SAP points to SAP Cloud Identity Services as its strategic direction, and Microsoft publishes guidance for moving SAP Identity Management scenarios to Entra ID. Most designs use both, with Entra ID as the source and SAP Cloud Identity Services distributing access into SAP.

Is our SAP data safe when Copilot can see it?

Copilot and Joule work within the user's existing permissions, so access control in SAP and Entra ID matters most. We review roles, sensitive data and conditional access policies before rollout. We also set up monitoring so you can see how the integration is used.

Related services

Often paired with this

Build & ConnectIdentity & Single Sign-On→Data, AI & SkillsAI & Data on SAP Data→Cloud PlatformsMicrosoft Azure→
Next step

Plan your move with people who know SAP.

One working session with our cloud and SAP architects. You leave with the options, the risks and a first plan.

  • Your landscape reviewed
  • The right cloud and region
  • A first roadmap
Sources

We call our approach to Microsoft 365 & Copilot with SAP the Fenworth Handover: advice that stays on your side of the table.

AWS, Microsoft Azure, Google Cloud and SAP are trademarks of their respective owners.

© 2026 Mawkish Technologies. This guide, its diagrams and illustrations are protected by copyright. You’re welcome to learn from it and to quote it with credit and a link. Reproducing it, by hand or through AI, and publishing it as your own is not allowed. Read our copyright notice