SampleSampletypeA worked example you read or clone. Evidence: it demonstrates, it never provides.See every one →What this type is →by SAPby SAPoriginPublished by SAP itself. A visible facet, never an input to a reading — a dormant official plugin reads exactly like a dormant independent one.See every one →Reference

teched2025-XP261

An SAP TechEd on Tour hands-on session that integrates Cloud Identity Services with Microsoft Entra to provision users across cloud and on-premises SAP systems.

Five exercises import SAP back-end roles into Cloud Identity Services, provision them out to Microsoft Entra ID, onboard a new employee in SAP SuccessFactors, assign an access package in Entra, and provision the result back to the SAP back-end systems. The scenario spans cloud and on-premises environments to keep access consistent across both. Administrative access to Entra needs multi-factor authentication, so the session asks for a mobile authenticator app such as Microsoft Authenticator before starting.

Facts

Last pushLicenceApache-2.0

Where it sits

Lives in
Demonstrates
Identity provisioningBTPIdentity provisioningcapabilityGetting users, groups and role assignments into every system that needs them, and out again when a person leaves, through provisioning jobs or SCIM APIs. [Authentication](capability:authentication) answers who is calling one request; provisioning decides whether the user exists in that system at all.
Requires
Cloud Identity ServicesCloud Identity Servicesartifactthe side of the integration the session configures: back-end roles are imported into it in exercise 1 and provisioned out of it to Microsoft Entra ID in exercise 2.SAP SuccessFactorsSAP SuccessFactorsoutside the atlasthe system a new employee is onboarded in, which is where the provisioning chain the later exercises follow begins.

Who is behind it

SAP SamplesSAP SamplesOrganisationMaintains this
In the atlas: maintains 222
@SAP-samples
maintainerAjay SorengPersonContributes to this
In the atlas: contributes to 36
@ajaysoreng
Ajinkya PatilPersonContributes to this
In the atlas: contributes to 112
@ajinkyapatil8190
chcohrsPersonContributes to this
In the atlas: contributes to 5
@chcohrs
jadolfPersonContributes to this
In the atlas: contributes to 5
@jadolf
Martin RaepplePersonContributes to this
In the atlas: contributes to 1
@raepple
SoniaPetrescuPersonContributes to this
In the atlas: contributes to 1
@SoniaPetrescu
6 contributors

What it declares

Every artifact

Type
Sample
Origin
By SAP
Use as
A reference

As a sample

Form
Workshop or CodeJam material

Connections3

README

quoted from SAP-samples/teched2025-XP261 under Apache-2.0, read
SAP-samples/teched2025-XP261/README.mdOn GitHub

REUSE status

XP261 - Identity lifecycle management with SAP BTP and Microsoft Entra

Description

This repository contains the material for the SAP TechEd on Tour session XP261 - Identity lifecycle management with SAP BTP and Microsoft Entra.

Overview

Learn how to integrate SAP Cloud Identity Services with Microsoft Entra to deliver unified user lifecycle management across SAP software and third-party applications. The end-to-end scenario in this hands-on session spans across cloud and on-premises environments to provide consistent access control throughout the enterprise.

Requirements

To follow all exercises in this session, please make sure that you have a mobile phone where an Authenticator app, such as the Microsoft Authenticator, is installed. For administrative access to Microsoft Entra, multi-factor authentication is mandatory. Follow the Getting Started guide to setup MFA for your user in this session.

Exercises

License

Copyright (c) 2024 SAP SE or an SAP affiliate company. All rights reserved. This project is licensed under the Apache Software License, version 2.0 except as noted otherwise in the LICENSE file.

Apache-2.0, read

Details

Sources3
Added by handdiscovered herechecked
github.com/SAP-samples/teched2025-XP261tree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
discovered viaAdded by hand
first seen in the atlas
ecosystem and domainbtp, security-and-compliance
Contributors6

From the repository’s contributor list, .

History in the atlas1
  1. First seen.
For your agent
Ref
artifact:sap-samples-teched2025-xp261
JSON
/artifacts/sap-samples-teched2025-xp261.json
MCP
Connecting an agent