# Multi values for proxy addresses

**URL:** <https://developer.sailpoint.com/discuss/t/multi-values-for-proxy-addresses/64153>\
**Category:** SHF Discussion and Questions\
**Tags:** provisioning, connectors, sailpoint-identity-security\
**Created:** [June 7, 2024, 2:46pm UTC](https://developer.sailpoint.com/discuss/t/multi-values-for-proxy-addresses/64153 "2024-06-07T14:46:19Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![vguleria](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/vguleria/32/7884_2.png) [@vguleria](https://developer.sailpoint.com/discuss/u/vguleria)\
**Post date:** [June 10, 2024, 10:20am UTC](https://developer.sailpoint.com/discuss/t/multi-values-for-proxy-addresses/64153/7 "2024-06-10T10:20:23Z")

</div>

Hi @PhilRawlings1

Yes, then it make sense to try to cover this logic in before provisioning rule. Ideally, i believe you should then cover account move, email regeneration and proxy addresses in before provisioning rule as that would be the ideal scenario.

The after modify rule is also another approach but then you will need to write the powershell script and still might need some attributes to be included into the provisioning plan to perform the checks in ps script.

So, it will be better to align with Expert services, as they can suggest other approach as well by looking into your system and use case.

Please let me know if there are any queries.

Thank You.  
Regards  
Vikas.

---

_[View the full topic](https://developer.sailpoint.com/discuss/t/multi-values-for-proxy-addresses/64153)._