AWS made AI agents sign into SAP as you. No shared account.
AWS published a configuration this week for single sign-on agentic access to SAP, built on the AWS for SAP MCP Server, Amazon Bedrock AgentCore and Microsoft Entra ID.
This is the problem most agent pilots quietly carry. AWS says agent deployments normally route every request to SAP through one shared service user, which removes per-user authorization, records the wrong identity in the SAP logs, and puts a shared credential into storage. AWS calls that the reason these deployments stall before production.
The mechanism is an On-Behalf-Of token exchange across three Entra ID app registrations. The user's identity is proven to AgentCore, AgentCore exchanges it with Entra ID for a token SAP accepts, and the email claim maps to the individual SAP user through OIDC trust. AWS says SAP then authenticates, authorizes and audits the request under that user.
Requirements: SAP BASIS 7.56 SP1 or later, or 7.52 with SAP Note 3313726. AWS says no SAP passwords are stored; the Entra credential sits in AWS Secrets Manager.
Worth reading twice: this fixes attribution, not scope. The agent now inherits everything that user is allowed to do in SAP, which makes role design the control that matters.
Which identity do your agents use inside SAP today?
Sources
Our file on AWS
All 3 AWS storiesFor your next steering committee
- 1Ask which AI tools already touch your ERP or finance data, including the ones nobody approved.
- 2Ask what each tool is allowed to change, and who reviews what it changed.
- 3Ask how the result is measured, and who decides to switch a tool off.
Issue 01 of the ERP LEADERS brief puts a timeline, the three-number review and six questions on one page. Read issue 01
Welcome back. · Issue 01