Skip to main content
Book a demo

Connect Microsoft 365 User Profile to Cursor

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

Book a demo Cursor setup guide

Set up

Add Microsoft 365 User Profile to Cursor in four steps

Admins approve the server once. Everyone in Cursor 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 Cursor to Runlayer

    Runlayer’s CLI installs the Runlayer Plugin natively in Cursor, and admins can roll it out org-wide with Auto Sync plus a Cursor team rule. With direct tool listing turned on for your deployment, Microsoft 365 User Profile’s 5 tools show up in Cursor’s own tool list.

    Cursor 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 Cursor

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

Tools

5 Microsoft 365 User Profile tools in Cursor

Runlayer policy decides which of these Cursor 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 Cursor

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

  • Gateway policy (available)

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

  • Audit trail (available)

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

  • Client hooks (available)

    Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call before Cursor runs it, including calls to MCP servers.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before Cursor’s model sees it.

  • Redact output in place (not available)

    Cursor cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.

In Cursor

  • Runlayer cannot tell Agents Window sessions apart from regular IDE sessions.
  • The Cursor CLI sends fewer session events than the IDE, but Runlayer’s allow and deny decisions still apply.

Frequently asked questions

Connect more

Find another combination