# Email Generation via Cloud Rule Not Matching mailNickname Format(Transform) **URL:** \ **Category:** SHF Discussion and Questions\ **Tags:** transforms, rules, sailpoint-identity-security\ **Created:** [October 21, 2025, 6:53am UTC](https://developer.sailpoint.com/discuss/t/email-generation-via-cloud-rule-not-matching-mailnickname-format-transform/186015 "2025-10-21T06:53:16Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![LearningStar](https://avatars.discourse-cdn.com/v4/letter/l/a9a28c/32.png) [@LearningStar](https://developer.sailpoint.com/discuss/u/LearningStar)\ **Post date:** [October 21, 2025, 6:53am UTC](https://developer.sailpoint.com/discuss/t/email-generation-via-cloud-rule-not-matching-mailnickname-format-transform/186015/1 "2025-10-21T06:53:16Z")
Hi everyone, I’m currently facing a challenge with a complex requirement related to email generation using a **cloud rule** , and I’m hoping someone here might have encountered a similar issue or can suggest a workaround. ### Scenario: We’re generating email addresses based on a transformed `mailNickname`. The `mailNickname` is being created correctly in the desired format, e.g.: ```auto mailNickname = firstname.prefix-lastname ``` However, when we attempt to use this value in our cloud rule for generating the email address, it seems like the logic doesn’t fully evaluate the entire `mailNickname`. Instead of using the complete value, the generated email ends up in a different format, like: ```auto firstname.lastname@example.com ``` It appears that the rule is not waiting for the full transformation of `mailNickname` before applying the email generation logic. We’ve tried multiple approaches, but none have produced the expected result so far. Example : firstname.prefix-lastname MailNickName **:aquatest.aan-de-user** Prefix : **aan-de** Email : **[aquatest.user@demotest.com](mailto:aquatest.user@demotest.com)** ### What We Need: Ideally, we want the email address to be generated in the same format as the final `mailNickname`, e.g.: ```auto firstname.prefix-lastname@example.com ``` Has anyone dealt with a similar issue or found a workaround to ensure the cloud rule uses the fully evaluated `mailNickname`? Any suggestions, tips, or examples would be greatly appreciated! Thanks in advance! * * * ---
**Author:** ![selvasanthosh](https://avatars.discourse-cdn.com/v4/letter/s/cab0a1/32.png) [@selvasanthosh](https://developer.sailpoint.com/discuss/u/selvasanthosh)\ **Post date:** [October 21, 2025, 7:20am UTC](https://developer.sailpoint.com/discuss/t/email-generation-via-cloud-rule-not-matching-mailnickname-format-transform/186015/2 "2025-10-21T07:20:39Z")
Hi @LearningStar , The issue you’re facing is due to attribute execution order in SailPoint ISC’s Create Account provisioning policy. When multiple attributes are created simultaneously, ISC processes them sequentially in the order they appear in the configuration. Solution: 1. **Reorder Attributes** Drag the `mailNickname` attribute above the mail attribute in the list. This ensures `mailNickname` is fully evaluated first 1. **Change Email Mapping to Static** $mailNickname@example.com Static mappings can reference account attributes defined higher in the list using `$attributeName` Reference Documentation [Reordering Attributes](https://documentation.sailpoint.com/connectors/active_directory/help/integrating_active_directory/reording_attributes.html) [Configuring Source Account Provisioning - Static Values](https://documentation.sailpoint.com/saas/help/provisioning/create_profile.html) [Static Transform Operations](https://developer.sailpoint.com/docs/extensibility/transforms/operations/static) Hope this helps resolve your issue! ---
**Author:** ![j\_place](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/j_place/32/19181_2.png) [@j\_place](https://developer.sailpoint.com/discuss/u/j_place)\ **Post date:** [October 21, 2025, 8:00am UTC](https://developer.sailpoint.com/discuss/t/email-generation-via-cloud-rule-not-matching-mailnickname-format-transform/186015/3 "2025-10-21T08:00:36Z")
Hi @LearningStar When you say: > [@LearningStar](#): > > generated email ends up in a different format Do you mean that is from the Rule logs, or the Provisioning logs, or the value in the target system? Also, what Email system are you provisioning into? ---
**Author:** ![LearningStar](https://avatars.discourse-cdn.com/v4/letter/l/a9a28c/32.png) [@LearningStar](https://developer.sailpoint.com/discuss/u/LearningStar)\ **Post date:** [October 21, 2025, 8:11am UTC](https://developer.sailpoint.com/discuss/t/email-generation-via-cloud-rule-not-matching-mailnickname-format-transform/186015/4 "2025-10-21T08:11:59Z")
Hey , we are generating these attributes within Sailpoint , it’s not Create account policy we wanna use it for Ad account creation but at present our requirement is to generate work email that’s identity attributes on the basis of mail nick name. ---
**Author:** ![j\_place](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/j_place/32/19181_2.png) [@j\_place](https://developer.sailpoint.com/discuss/u/j_place)\ **Post date:** [October 21, 2025, 8:24am UTC](https://developer.sailpoint.com/discuss/t/email-generation-via-cloud-rule-not-matching-mailnickname-format-transform/186015/5 "2025-10-21T08:24:53Z")
Hi @LearningStar - It sounds like you are using this rule as part of your Identity Profile. I appreciate this doesn’t answer the question you are asking, but it would be against ISC best practice to be generating email addresses as part of the Identity Profile, see [Identity Attribute Rule | SailPoint Developer Community](https://developer.sailpoint.com/docs/extensibility/rules/cloud-rules/identity-attribute-rule) ---
**Author:** ![LearningStar](https://avatars.discourse-cdn.com/v4/letter/l/a9a28c/32.png) [@LearningStar](https://developer.sailpoint.com/discuss/u/LearningStar)\ **Post date:** [October 21, 2025, 11:47am UTC](https://developer.sailpoint.com/discuss/t/email-generation-via-cloud-rule-not-matching-mailnickname-format-transform/186015/6 "2025-10-21T11:47:12Z")
Hey @j_place : I appreciate your responses and I understand all of these points but client requirement is to have the email address creation should be handled by Sailpoint only, earlier we were managing them at the time of Ad account creation but now they want to handle it via Sailpoint In our logic we are doing uniqueness check at source as well as on IdentityNow if both gets true means unique then we are initialising them at Sailpoint and later on we are utilising email and mail nick name for Entra id account creation. could you please suggest what should be the workaround to handle this situation. We need to have uniqueness check both side and accordingly email and mailnickname should be set. ---
**Author:** ![j\_place](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/j_place/32/19181_2.png) [@j\_place](https://developer.sailpoint.com/discuss/u/j_place)\ **Post date:** [October 21, 2025, 12:00pm UTC](https://developer.sailpoint.com/discuss/t/email-generation-via-cloud-rule-not-matching-mailnickname-format-transform/186015/7 "2025-10-21T12:00:43Z")
Hi @LearningStar - I’m sorry, but your answer has just opened too many questions and I’m not going to advise on any workarounds for ISC best practice as there will be unknown consequences. One thing to bear in mind though, the client is not always right and creating the email address via account profile still means that “the email address creation should be handled by Sailpoint only”. ---
**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\ **Post date:** [December 20, 2025, 12:01pm UTC](https://developer.sailpoint.com/discuss/t/email-generation-via-cloud-rule-not-matching-mailnickname-format-transform/186015/8 "2025-12-20T12:01:19Z")
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.