Approval Routing Automation with Entra ID

Route every approval to the right manager automatically. Jinba Flow looks up the requester's Microsoft 365 profile and direct manager in Entra ID, then sends the request with those details filled in.

Book a Demo
  1. Access requested Someone needs a role on a regulated workflow
  2. Look up the directory Profile, group and manager from Entra ID
  3. Policy check Test the request against your access rules
  4. Message the manager Request sent in Microsoft Teams
  5. Record the decision Outcome kept in the run history

What you can do with Microsoft Entra ID + Jinba

  • Directory Profiles in a Workflow Step

    Resolve email addresses or user principal names to Microsoft 365 profiles with display name, email, job title, department, company and office location. Anyone not found is listed separately.

  • Manager Lookup for Routing

    Find each person's direct manager in the same workflow and send the request to them in Microsoft Teams or Outlook. When no manager is set, the workflow gets an empty result it can route elsewhere.

  • Review Before Anything Moves On

    Add an approval step and the workflow run pauses until a reviewer approves or rejects it, with a comment when the workflow requires one. The decision is made right in the chat or the run console.

  • Admin-Consented Access

    Lookups use a Microsoft account connected in Jinba with the delegated User.Read.All permission, which a tenant admin must consent to before any lookup will run.

How teams use it

Requests Routed to the Line Manager

When a request needs sign-off, the workflow looks up the requester's direct manager and sends them the details in Microsoft Teams or Outlook, instead of leaving it in a shared inbox.

Routing by Department or Office

Send KYC escalations or contract reviews to the right team based on the requester's department or office location in their directory profile.

Named People in the Record

Add the requester's name, job title and department to the workflow's output, so the run history shows who asked rather than an email address.

Access Requests Checked Against Policy

Collect an access request, look up the requester and their manager, check it against your policy, and pass it to the manager. The access change itself stays with your administrators.

Frequently Asked Questions

Everything you need to know about Jinba. Can't find the answer you're looking for? Reach out to our support team.

What can Jinba read from Microsoft Entra ID?

Microsoft 365 user profiles and each user's direct manager. Given email addresses or user principal names, a workflow gets back display name, email, job title, department, company name and office location, plus a list of anyone it could not find.

Does the Entra ID connection change groups or grant access?

No. Jinba's Entra ID steps read profiles and manager relationships through Microsoft Graph. They do not change group membership or grant access.

What permissions does it need?

A Microsoft account connected in Jinba with the delegated User.Read.All permission, which a tenant admin must consent to. User.ReadBasic.All is not enough, because department and company name are only available with User.Read.All.

What happens if someone has no manager set?

The lookup returns an empty manager for that person, so a condition step can send the request to a fallback approver instead.

Can a person sign off before the workflow continues?

Yes. Add an approval step and the run pauses until a reviewer approves or rejects it, with a comment when the workflow requires one. The decision is made in Jinba App chat or the Flow run console.

Route Approvals to the Right Manager

Talk to our team about using your Microsoft Entra ID directory to route approvals and reviews in Jinba workflows.

Book a Demo