Administering Cloud EPM: The Platform Beneath the Business Processes · Module 7 · Provisioning at Scale
Why manual provisioning fails
Lesson 78 of 201 · 2 min
MODULE 6'S GROUP MODEL MAKES PROVISIONING SURVIVABLE. SYNCHRONIZATION MAKES IT CORRECT. Two different problems. The first one is effort; this one is truth. What manual provisioning gets wrong, reliably: leavers. Joiners get done because somebody is waiting. Leavers get done because somebody remembers — and eventually nobody does. And here is the audit consequence. "How do you know your user list is accurate?" There is one good answer, and it is: "it is synchronized from the corporate directory, which is maintained by HR." Every other answer is a description of a process that depends on somebody remembering. What synchronization gives you: one place to add a person, one place to remove them, and an EPM estate that reflects reality without anybody maintaining it. What it costs: the identity team's involvement, ongoing. Module 3's capacity question, arriving. SYNCHRONIZE WHERE THE CORPORATE DIRECTORY IS WELL MAINTAINED. WHERE IT IS NOT, SYNCHRONIZATION PROPAGATES…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Administering Cloud EPM: The Platform Beneath the Business Processes, with a certificate on completion and a fourteen-day refund window.
In this module: Module 7 · Provisioning at Scale
- 1Why manual provisioning fails
- 2What synchronization does and does not carry
- 3Synchronizing across identity domains
- 4Synchronizing specific users and groups
- 5Synchronizing from an external directory
- 6Groups for application-level role assignment
- 7Password policies
- 8Email notifications and password resets
- 9What breaks
- 10Lab: design the synchronization and test the leaver