Azuqua was a tool that helped users integrate their SaaS applications and build custom automations. It was acquired by Okta in late 2019, and is now part of Okta Workflows. Okta Workflows leverages Azuqua’s workflow orchestration engine and application integrations to automate complex identity-centric processes such as user onboarding and offboarding. The product is available as part of the Okta Lifecycle Management…
It is perfectly suited if some heavy operation needs to be automated where jobs can be queued up. Scalable app which is required to develop in a lesser time frame. Good for when users should be able to change rules more frequently without any downtime, like promotions. The server is well proven in the market. BizTalk server is the best fit if all other integration adapters are developed using Microsoft applications and if all applications are meant to be processed on a Windows environment.
The integration I used Azuqua for was based on Salesforce, Wrike and Office 365. I found the integration of Salesforce reasonably straightforward, Wrike was limited in the "cards" capability but functional (there are bugs but there are also workarounds but they required assistance from the Azuqua support team) and Office 365 was quite immature (primarily around Excel bugs but also email was limited).
BizTalk uses Microsoft Visual Studio as the IDE (integrated development environment) tool, and it's very easy to use.
The orchestration engine of BizTalk addresses resource issue very well for long-running business processes by dehydrating and rehydrating orchestration instances.
BizTalk is very easy to integrate if the development is mainly on the Microsoft software family.
The best part about Azuqua is that you do not need to write code. You do however need to have an understanding of logic and how the software works. This happens to fit me perfectly as someone with basic programming experience.
Their Support is second to none. Not only are they extremely quick and responsive, but their answers are never canned responses and always provide valuable content.
They seem to take feedback seriously and will continue to evolve and make a better product.
BizTalk needs to be better at tracking down errors after the fact. Input files by default get deleted after processing successfully, unless you specifically specify that they don't. This can be an issue where you need to see what the input file contained, since you may have errors showing up in your target platform, in our case this was SAP.
BizTalk logging needs improved. It needs to be able to log the content of the messages it sends and receives. It would be good if the log had a link to the input and output files.
BizTalk needs to allow a simple way to preserve the input and output files for debugging purposes. A master setting on the orchestration would be helpful for this.
I think it requires an easy way to migrate flows created from one user to then move the ownership to another user. It happened to us that one of our engineers left the company and he had the Azuqua account and flows. It required quite some time, cases and telephone calls to do the migration to my account.
Microsoft BizTalk is not an intuitive product. It requires many hours of looking through the settings to achieve what you need. Using 3rd party DLLs is a nightmare as you are forced to register them in the GAC of the server and this process is quite cumbersome just to use a DLL.
The system is working as it should, keeping our programs safe from outside hackers. Helping us keep our passwords safe, convenient and already ready to get us logged into the program securely and quickly. Verification that only authorized users are able to access our company's programs. Okta Workflows (Azuqua) is a very good system that has helped our company greatly.
BizTalk Server has been supported for more than 15 years. It is well proven in the market. Microsoft has provided excellent support with technical issues.
We did look at Jitterbit dataloader from Salesforce.com. Jitterbit seems like a pretty decent solution if you are doing a lot of uploads into Salesforce.com. However, its not nearly as flexible as Microsoft Biztalk is. Biztalk allows you to create any type of custom solution you wish, whereas Jitterbit is much more limited.
I evaluated Zapier and Microsoft Flow before coming across Azuqua. Zapier was too simplistic and didn't allow for transfer of enough variables. The price point also didn't work for the value it could provide. Microsoft Flow couldn't make the connection with Smartsheet, and I was unable to get Microsoft support or Smartsheet support to assist me with the issue.
Increased time savings. We could not function as a matter of daily business if we did not have a tool to automate project folders (and complementary workflow management profiles) for the thousands of projects that flow through daily.
Opens up a greater understanding of all the silos and divisions within the company infrastructure and tests secure means to link those groups safely and share information.
Opens up the chance to communicate with other API information sources if our company is doing a partnership with another organization. Granted everything is square with IT security.
