I hope you'll reconsider this. The integration feature Autotask released is kind of terrible. In order to deploy, it is necessary to install IIS roles and certificates on a Domain Controller and open traffic on the firewall for Autotask to connect directly to it. There are some obvious security concerns with something like this not to mention the sheer hassle of it. We have never been able to get it to work well. Currently, we're spending several hundred dollars a month on a tool that only sync's users to contacts and auto-provisions their Autotask Client Portal permissions.
Since Liongard already has all of the information necessary to do the same task, it would be a-ma-zing if you could develop the Autotask API a little deeper to layer on this additional functionality.
Autotask 2019.9 added an LDAP/Azure integration feature which makes this idea obsolete (at least for Autotask) it can connect via LDAP or Azure AD and pull all the contacts directly into the system as contacts.
I hope you'll reconsider this. The integration feature Autotask released is kind of terrible. In order to deploy, it is necessary to install IIS roles and certificates on a Domain Controller and open traffic on the firewall for Autotask to connect directly to it. There are some obvious security concerns with something like this not to mention the sheer hassle of it. We have never been able to get it to work well. Currently, we're spending several hundred dollars a month on a tool that only sync's users to contacts and auto-provisions their Autotask Client Portal permissions.
Since Liongard already has all of the information necessary to do the same task, it would be a-ma-zing if you could develop the Autotask API a little deeper to layer on this additional functionality.
Attachments Open full size
Autotask 2019.9 added an LDAP/Azure integration feature which makes this idea obsolete (at least for Autotask) it can connect via LDAP or Azure AD and pull all the contacts directly into the system as contacts.
Attachments Open full size