Workflow trigger based on proxy address

Question

I am trying to trigger a workflow so that when a users gets a mailbox created and the x500 writes back to the on-premise account via ADSync it runs a powershell script. 
 I know the script is fine as i can set the workflow trigger to just modify user and it works every time however when I change add "Workflow start upon a request for changes to: ProxyAddresses" and filtering conditions set to "ProxyAddresses of Workflow Target contains x500" it doesn't trigger, anyone got an ideas on what might be causing this? 
 I suspect the filtering conditions might be the issue... 
 Does anyone know an alternative attribute that i can use in the trigger that only applies once the user has an exchange online mailbox?

Stu.Pollock · Accepted Answer

Hi infra_2020 
 I suspect the reason why the workflow isn't being triggered might relate to where the change is being initiated. 
 As AAD Connect is changing the ProxyAddresses field natively in AD (as you'd expect), and because a workflow doesn't react to a DirSync Controls from AD, there is no trigger being raised in Active Roles. 
 Am I correct in saying that if you manually modify a Users ProxyAddresses to contain an x500 entry, the workflow fires no problem? Then successfully completes whatever your script aims to do? 
 The way around this would be to write a policy script which handles changes from DirSync Controls, which either just completes the required changes to the ProxyAddresses field, or sets an attribute to trigger a workflow.

This script would need to be in an Administration Policy, and you'd want to ensure you only deal with the exact request types you're interesting in, IE: 
 if ($Request.Class -ne "user") {return} 
 If($(IsAttributeModifed -Attribute "ProxyAddresses" -Object $Request)) {return}

Workflow trigger based on proxy address

Top Replies