Generating proxyaddresses during user provisioning

Hi, when it comes to generating alias email addresses for the proxyaddresses attribute during user provisioning, here are some ideas you might consider:

Function Compatibility:
First, double-check that the selectunique function is supported in your provisioning tool for mapping proxyaddresses. Sometimes, the input data or the expected output format might not match what the function provides.

Correct Format:
The proxyaddresses attribute usually requires values to be in a specific format, like "smtp:email address removed for privacy reasons". Make sure that your transformation using selectunique is outputting the address in this format; otherwise, it won't work properly.

Test and Log Outputs:
It might be helpful to log or preview the output of the selectunique function to verify that it's generating the correct aliases. This can help you identify if there's a logic or formatting issue in the mapping.

Alternative Approaches:

If the built-in function isn’t meeting your needs, you might consider pre-generating the alias addresses with a custom script and then passing them as a multi-valued attribute for proxyaddresses.
If you're using a tool like Azure AD Connect, you could explore custom synchronization rules that handle the alias generation for you.

I hope these suggestions help you move forward with your provisioning process