How to add an email account to a user via workflow

I'm trying to automate some of the provisioning for our company I've got most of it working but I dont see how to add an email account to a user via work flow like the standard provisioning does 

Parents
  • Do your users' mailboxes reside on-premises or in Office 365?

  • Create a change workflow that reacts to a user creation.

    In it, create an update activity that specifies the following properties:

    edsaCreateMsExchMailbox = TRUE

    mailnickname = <some string with no spaces>

    FYI, there is actually an Active Roles provisioning policy rule for the the mailnickname (the rule refers to it as the Alias) so that would probably be the easiest way to get that auto-generated at the time the user is created.

    The construction of the email address will be controlled by Exchange's addressing policy.

    In fact, strictly speaking, you don't need a workflow at all if you include a PGV rule in your provisioning policy that sets edsaCreateMsExchMailbox to True.

    This is very general advice. 'Would really need to understand your use case(s) a bit better - i.e. should all users get mailbox, how many different provisioning policies do you have etc.

  • we are using a 3rd party app to prevision the users and groups but it falls short on a few area adding the email account is one of them so we a workfow that can help us out with this to automate the process 

  • Does / can the third party app perform its actions through Active Roles or do you need Active Roles to be able to "detect" the provisioning actions that your app performs within AD?

  • i need active roles to be able to "detect" the provisioning actions that the app performs within AD

  • I haven't had much luck with getting workflows to detect changes in AD.  I have been successful by using policy scripts embedded into provisioning policies linked to the OUs where your app is creating the users.

    In your policy script, you will need to create an onPostCreate function.  Within this function, you should stamp the edsaCreateMsExchMailbox = TRUE attribute I mentioned above to trigger the mailboxe enabling.  Remember to also supply the mailnickname (I could be wrong but I don't believe that a provisioning policy rule for "Alias" will fire in the case of a native user create).

    When you setup the policy script in your provisioning policy, you will also need to enable "Handle Changes from Dirsync Control" to the script will respond to native AD changes.  (see below)

    You are getting into the realm of what most customers hire Consultants to setup so don't be surprised if there's a bit of a learning curve to this.

    I suggest you have a look at the SDK that comes with the product to get more familiar with the idea of Policy Scripts.  The SDK is a help file that installs with the product.  If you search the installed folder structure on your AR server, you will find it.

Reply
  • I haven't had much luck with getting workflows to detect changes in AD.  I have been successful by using policy scripts embedded into provisioning policies linked to the OUs where your app is creating the users.

    In your policy script, you will need to create an onPostCreate function.  Within this function, you should stamp the edsaCreateMsExchMailbox = TRUE attribute I mentioned above to trigger the mailboxe enabling.  Remember to also supply the mailnickname (I could be wrong but I don't believe that a provisioning policy rule for "Alias" will fire in the case of a native user create).

    When you setup the policy script in your provisioning policy, you will also need to enable "Handle Changes from Dirsync Control" to the script will respond to native AD changes.  (see below)

    You are getting into the realm of what most customers hire Consultants to setup so don't be surprised if there's a bit of a learning curve to this.

    I suggest you have a look at the SDK that comes with the product to get more familiar with the idea of Policy Scripts.  The SDK is a help file that installs with the product.  If you search the installed folder structure on your AR server, you will find it.

Children