Inconsistent APIs and PowerShell Cmdlets for setting approval config between Roles and Entitlements

For Roles, you patch the Role’s accessRequestConfig:

For Entitlements, you put entitlement request config:

The nightmare-ish upper/lower case, with/without underscore, workgroup vs GOVERANCE_GROUP…what is going on?

Is there a standardised approach to this, or was this all developed by different teams?

And separately, what’s with the different cmdlet naming convention:
image

This kind of interfacing is rather ugly, IMO.

…and from here, it’s using “MANAGER” for setting the EntitlementRequestConfig. If you want to set that to the entitlement owner, it’s NOT “OWNER”, NOT “entitlementOwner”, but it is “ENTITLEMENT_OWNER” instead.

Go figure.

It’s as if that post is avoiding the use of Initialize-v2024EntitlementRequestConfig.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.