Hello, We want to be able to update ‘ForwardingAddress’ and ‘DeliverToMailboxAndForward’ properties on some Identities Exchange Online accounts when they move into the Sunset Lifecycle State. Our Entra Source is using the Entra SaaS connector. We have the options for Manage M365 and Exchange Onli…

No problem @chrisk ! I wouldn’t think this block of code would work, but I can definitely be wrong. "null": { "type": "static", "attributes": { "value": null } …

Hello @chrisk , Regarding your following statement “Transform/Attribute Sync doesn’t seem to work because the value will sometimes return empty if the Identity is not marked as requiring forwarding.” I think the better and standard way for your usecase is to use transform /attributes sync. If val…

A transform seems to be the best way to do this. Do you want to share it so that we can provide feedback?

I may have worded that a bit wrong. The value from the HR source is not empty, the value coming back from the Transform will be empty sometimes which causes an error on the Identity. (I guess Transform can’t return an empty value?) Here is an example for the ‘DeliverToMailboxAndForward’ Attribute…

For all others cases that sunset,what if you retrived the current exo property ?

Like : { "name": "deliverAndForward", "type": "static", "attributes": { "value": "#if($lifecycleState == 'sunset' && $emailForward == 'true')false#{else}$exoForwardEnabled#end", "lifecycleState": { "type": "firstValid", "attributes": { …

I’ll give this a try and report back results, thank you! Tried this with high hopes, however, I am still getting : “sailpoint.api.AttributePromotionException: Applying transform[reference] to attribute[deliverAndForward] failed” I’m thinking it is because the value on the actual EXO accounts are …

Morning, I wrote a piece recently about how to send ‘blank’ results from a transform. If you ‘trim’ a ‘space’ that comes from a static transform, that works. Try this: { "name": "deliverAndForward", "type": "trim", "attributes": { "input": { "type": "static", "attributes": {…

A better way would be to use a firstValid where the final value is just null.

I don’t believe that null will be passed through under a firstValid function. At least I’ve never been able to get that to work

Email Forwarding Upon Termination

Identity Security Cloud (ISC) ISC Discussion and Questions

zachm117 (Zach Mullins) April 14, 2026, 3:32pm 11

Check out this discussion to get a firstValid transform to return a null value: https://developer.sailpoint.com/discuss/t/transform-to-return-null/30233/11

Topic		Replies	Views
Help with Transform logic ISC Discussion and Questions transforms , identity-security-cloud	10	1026	January 30, 2024
Issue with termination trigger transform ISC Discussion and Questions transforms , identity-security-cloud	9	113	May 3, 2025
How do we apply transform based attribute (Non-Identity) in JDBC connection application ISC Discussion and Questions identity-security-cloud , jdbc-connector	20	202	January 24, 2026
New Capability - Availability of new Identity Attributes, Default Identity Profile Mapping and Transforms Product News transforms , identity-security-cloud , attributes , identity-profiles , connectors , identities , new-capability	10	920	October 8, 2024
Transform issue ISC Discussion and Questions transforms , identity-security-cloud	5	149	August 18, 2024

Email Forwarding Upon Termination

Related topics