Create New AD Group - Microsoft AD Integration Hub Spoke

[danno928]

My original issue that I posted:

I know it's a longshot because I have search ad nauseum, but maybe someone out there has run into this and knows the answer. As most people may be aware, the OOB 'Create Group' action for the Microsoft AD spoke in integration hub is really light on the build. It only asks for input for group name, group type, description, and OU. I have created my own custom action within the Microsoft AD spoke application - which is an exact copy of the OOB action, except I have added the fields I want to populate on group creation - managed by and email address. I'm attaching what I have for the initial script step that goes between the inputs and the PowerShell step as this seems to be where the hang-up is. The script step is getting the variable inputs just fine as you can see, but the output data is blank on group name, type, managed by, and OU....which has me really scratching my head considering that group name, type, and OU are 3 of the 4 OOB variables. Whereas one of my new variables, email, is pulling just fine. 

[danno928 · Accepted solution]

******UPDATE - RESOLVED*****

After a few painstaking hours of combing through everything, we resolved it! Hopefully this helps many others. 

1. We created the copy of the OOB ActionCreateNewGroup.ps1 script file (created while in the Microsoft AD Spoke application) to add the new variables, mail and managedBy - shown in the new attachments is adding those variables in the script

2. We create the copy of the OOB Create Group action (created while in the Microsoft AD Spoke application) - in here, we actually removed the first script step that is in the OOB action that runs the ADUtil script include to sanitize the data as part of our troubleshooting. Since the action works without that script step, we left it out. For this action, we added the variables in the inputs, and the PowerShell step - making sure to make the name lower case to match what is in the PowerShell script file. 

3. Lastly, in our flow, where you define the action to run, you can populate the variables as you see fit, but make sure that the managedBy is pulling in the user's FQDN (if you use SSO, you can pull in that user's SSO Source value)

I suspect you can build your custom action to fill any of the AD attributes you want, just make sure that your variables in the action - PowerShell step and your PS script match!