Replies posted by martinbaylis
Azure AD ProvisiongArchived
It’s a good couple of years since we did it, but follow this article Setting up Microsoft Azure AD Single Sign-on in Freshservice : Freshservice and you’ll have what you need.What your proposing above is going in the wrong direction. If you have AAD users already setting AAD SSO will then automatically create new FS users the first time the AAD user tries to open your FS Portal. You can also configure the SAML to bring through additional properties for each user.You other option is to use the FS API to create users when your AAD users is created - just use the same primary email and they will merge in Fresh Service on first logon.
Short answer: noLong answer: yes but not the way you describe the UI without considerable customisationLonger answer: yes but multiple service catalogue items is much easier (be warned there is still no API for creating / updating service catalogue items)Longest answer:The dynamic scenario you’re proposing could be achieved with a couple of drop won fields on the catalogue item (which you’ll have to manually maintain) however this doesn't achieve end-to-end automation easily as this has to work on the assumption that your group or mailbox names are unique and make sense to both end users and IT admins.We’ve all seen groups with horrible or legacy names that get referred to with multiple aliases by end users.The easier option which improves findability in the service catalogue is to have one service catalogue item per group / mailbox etc. you then have the short & long description fields to include grou alises etc and evn the name itself to be friendlier.What we did was this plus us
Join the Community
Sign in to the Community
Social LoginLogin for Freshworks Employees Login with LinkedIn
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.