We have SAML based Azure AD - Identity federation with auto-acceleration set to on - in NWC.
I have to use Assign a task action where the Assignee will be determined dynamically.
I couldn’t get this working and gives this error below when workflow is executed.
What I have found so far is:
If the user has never used NWC before, then they have to first access the NWC site, in order for them to get added/registered to the NWC Portal. Only then the workflow recognizes the user. But that is not practical as we cannot email every user the link to NWC and ask them to access the page.
Anyone faced similar issues? any solutions please?
Solved! Go to Solution.
Do you know why the User Directory Lookup requires Global Admin level access? My Azure admins are not comfortable giving more access than Read, as its expected only to read?
@SanthoshKumar-R I'm not 100% sure on that. As far as I know the User Directory Lookup just uses Read permissions to understand who is in the Azure AD instance and then get their contact information for assignment. I suspect that this is because we need to actually add the app at the Azure AD level (as an enterprise app), and so the Global Admin account would have full rights to do this without issue.