SAP BTP
The launch team cannot sign in
A trust or role-mapping change blocks a launch team. Coordinate identity ownership, scoped testing and business communication.
20 minutes suggested · Four incident updates · One shared screen
Start this rehearsal →Watch the quick field guide
24-second visual guide · captions and transcript · no autoplay
Read the guidance transcript
Spot the symptom. A failed connection does not prove the cause. Read the simulated destination, identity or integration evidence first.
Keep uncertainty visible. Certificates, credentials and authorizations have different owners. Decide which evidence you need before a change.
Discuss the trade-off. Compare a controlled recovery, a broad change and waiting for more information. Watch how the fictional story responds.
Make the next incident easier. Agree who owns the dependency and how it is monitored. Record actions; no real SAP tenant is changed.
Who should be in the room?
Facilitator, Identity owner, BTP administrator, Application owner. These are discussion roles, not account invitations. One person records while the team talks.
What the team will practice
A launch-day access spike
Partial impact does not prove an identity-provider outage.
Discussion: How will you establish scope and distinguish authentication from authorization?
The shortcut request
The team needs a decision about least-privilege access and a controlled test, not an indiscriminate workaround.
Discussion: Who can approve a narrow access change and how will it be verified?
Two owners give different updates
A successful login and successful authorized business action are different checkpoints.
Discussion: What end-to-end evidence and single update would align the teams?
The demo is unblocked
The team still needs a scoped rollback/expiry and review of affected users.
Discussion: Who signs off access scope, temporary changes and follow-up review?
What you’ll leave with
Your own recorded decisions, uncertainties and improvement actions with owners, dates and status. Print a readable report or export a browser-local session to revisit.
Original fictional content, not a technical response procedure. No real systems are changed. This exercise does not certify security readiness or compliance.
Read the facilitator guide →