Has anyone explored the different options on how to expose On-Premise ISM to 3rd parties externally?
We have current and new business requirements whereby we need to " expose " our On-Premise ISM to 3rd parties externally to both push and pull data. This is becoming more and more of a reality with the growing need to accommodate for better integration between On-Premise based solutions and Cloud / Other platforms for external parties.
As far as I know, there may be 3 x options
1. Leverage a Cloud based instance which sits between the On-Premise solution and the 3rd party / external
users. This will be specifically designed and configured to allow for 3rd parties to consume and push data of
which will then get synchronized between the Cloud and On-Premise instance.
2.Explore the option to expose the ISM On-Premise application via the Azure AD application Proxy. This
particular approach may most likely be the most “ cost “ effective and least effort required as opposed to the
option 1 to create a complete new Cloud Instance and require less system maintenance and admin. We've
briefly explored this option internally with a different application though, in this case being Confluence and
Jira from the Atlassian Stack which largely worked quite well.
3. Explore the option of " exposing " specifically the Self Service / Mobile Role of ISM to 3rd parties, which
may reduce the challenge of the licensing costs, this could either be also via the Cloud or Azure proxy
potentially. If there is not much complexity with regards to the pushing and consuming of data via the 3rd
parties then this would be a great option too.
If anyone perhaps may have already or is currently exploring either of the above or some similar intiatives
then please let me know as this would be great to share ideas and learnings where possible.