Skip to main content
Book a demo

Connect Microsoft 365 User Profile to ECA

Give ECA governed access to Microsoft 365 User Profile’s 5 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo ECA setup guide

Set up

Add Microsoft 365 User Profile to ECA in four steps

Admins approve the server once. Everyone in ECA then gets it through the same governed connection.

  1. 1

    Approve Microsoft 365 User Profile in Runlayer

    Add Microsoft 365 User Profile from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect ECA to Runlayer

    Users add the Runlayer Plugin to ECA by following Runlayer’s setup guide. ECA reaches Microsoft 365 User Profile’s 5 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    ECA setup guide
  3. 3

    Sign in to Microsoft 365 User Profile

    Each user signs in to Microsoft 365 User Profile with OAuth. Runlayer keeps the tokens out of the client’s configuration.

  4. 4

    Use Microsoft 365 User Profile from ECA

    Microsoft 365 User Profile’s approved tools appear in ECA. Every call is checked against policy and recorded.

Tools

5 Microsoft 365 User Profile tools in ECA

Runlayer policy decides which of these ECA users can call.

  • Get direct reports details

    Retrieve a user's team, or direct reports (people who report to them in the organizational hierarchy).

  • Get manager details

    Get a user's manager information - name, email, job title, etc. ⚠️ TOOL DEPENDENCY RULE: If the user request references a person (name, alias, email fragment, etc.), you MUST call the GetUserDetails…

  • Get multiple users details

    Search for multiple users in the directory by name, job title, office location, or other properties.

  • Get my details

    Retrieve profile details for the currently signed-in user ("me, my").

  • Get User details

    Retrieve a user's profile by UPN or Entra object ID (GUID).

Control

What Runlayer can see and stop in ECA

Some controls apply to every client at the gateway. Others depend on what ECA exposes to Runlayer.

  • Gateway policy (available)

    Every Microsoft 365 User Profile call from ECA passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, ECA as the client, the tool, and the policy and scanner decisions.

  • Native enforcement adapter (not available)

    Runlayer has no device-side adapter for ECA yet, so control happens at the gateway.

Frequently asked questions

Connect more

Find another combination