MSAMM
Back to course

Administering Cloud EPM: The Platform Beneath the Business Processes · Module 7 · Provisioning at Scale

What breaks

Lesson 86 of 201 · 2 min

Seven cases. One. "Synchronization stopped and nobody noticed." No monitoring. The user list is now quietly wrong. Module 14. Two. "A leaver still has access." The leaver path was never tested — or they were in a LOCAL group rather than a synchronized one. That second cause is worth remembering. A synchronized estate with one hand-made group has a hole in exactly the place nobody looks. Three. "We synchronized the whole directory and have eight thousand EPM users." No filter. Now you are responsible for all of them. Four. "A group was renamed and access disappeared." No change process with the identity team. Five. "Usernames do not match what SSO expects." Attribute mapping. Module 8 will not work until it is fixed. Six. "Half the users never got their activation email." Deliverability. Module 13. Seven. "We synchronized a badly maintained directory." Propagated the mess. Assess the source first. SYNCHRONIZATION MOVES…

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.

See the course and enrol9 free lessons

Get the free lessons by email

We will email you a link to every free lesson in this course. No account needed, and one message only.

In this module: Module 7 · Provisioning at Scale

  1. 1Why manual provisioning fails
  2. 2What synchronization does and does not carry
  3. 3Synchronizing across identity domains
  4. 4Synchronizing specific users and groups
  5. 5Synchronizing from an external directory
  6. 6Groups for application-level role assignment
  7. 7Password policies
  8. 8Email notifications and password resets
  9. 9What breaks
  10. 10Lab: design the synchronization and test the leaver