FWIW, much of the community is misunderstanding the intention and operation of SCIM. For instance, using Pega REST Connectors would be the opposite of the typical SCIM use case.

SCIM provides a way for identity providers to provide publish/subscribe user lifecycle events to dependent parties. In this model the Pega programmer now would need to code a REST Service that the SCIM client, e.g. Okta or Azure AD or Workday, would call whenever it has a CRUD user lifecycle event.

Since SCIM is a standard, and especially since many of us are using Pega Cloud, this is unfortunate. This is why Enterprise customers are petitioning Pega to include a SCIM module within the product. Ideally Pega would register this module in the marketplaces of Azure, Workday, Google, Okta, Mulesoft, etc. Once there, Pega customers just need to perform a little admin configuration on both sides, possibly implement a few data transforms, and voila - near real-time user synchronization with almost no code.