Azure AD Orch - App idea for MSPs

Hi all,

I have an idea that I think would take the Azure AD Orch app to a new level, particularly for MSP organisations.

For anyone not familiar, the app allows for multiple ‘Configurations’ to be set, that connect to different Azure AD App Registrations.

You can then call a configuration and complete a load of Azure AD actions in a Worfklow Automator (which is simply amazing).
 

There is one limitation for MSPs looking to use the app with multiple client tenants; There is no way to dynamically set the configuration on the condition (for example: a ticket requester company). This means that for every additional configuration you’d like to include in a workflow, you need an additional condition node and workflow path. Freshservice can’t merge workflow paths (understandably), so this gets out of hand very quickly with just a few client companies and actions following the app being called. Imagine the following example, but with tens of companies and many more actions to create and maintain:

My idea (and this years birthday candle wish 😂) is when calling the App in a Workflow, for the ‘Configuration’ dropdown list to either be a plain textbox include the option to manually enter a Configuration name in a subsequent textbox.

This would allow a single workflow path to service many multiple configurations by use of placeholders (either through placeholder fields, or custom object lookups) and really take the app to the next level for MSPs (whom Freshservice caters too very well in the platform itself).

Let me know what you think!

Kind regards,
Cody P

Hi Cody P,

Thank you for sharing your idea on how to improve the Azure AD Orch app. Your suggestion of allowing the use of placeholders or custom object lookups to dynamically set the Configuration dropdown list is an interesting idea that could be very useful for MSPs who need to manage multiple client tenants.

I suggest reaching out to the Azure AD Orch app developers and sharing your idea with them directly. You can submit a feature request or suggestion to them through the Azure AD Orch app documentation or support page. They may appreciate the feedback and consider implementing your suggestion in a future update.

Another option is to post your idea on the Microsoft Developer Community forum, where you can connect with other developers and share your feedback. This may also be a good place to get feedback and suggestions from other developers who are familiar with the Azure AD Orch app and can provide additional insights.

I hope this helps, and good luck with your suggestion! Let me know if you have any other questions or concerns.