Microsoft Graph MCP Server

Overview Schema Source Related Servers Discussions Admin

create_user

Creates a new Microsoft 365 user with display name, email/UPN, mail alias, and initial password, while enabling the account and requiring a password change by default.

Instructions

Create a new user in Microsoft 365

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "display_name": "<display_name>",
      "user_principal_name": "<user_principal_name>",
      "mail_nickname": "<mail_nickname>",
      "password": "<password>"
    },
    "name": "create_user"
  }
}

Input Schema

Name	Required	Description
`password`	Yes	The initial password for the user
`display_name`	Yes	The display name for the user
`mail_nickname`	Yes	The mail alias for the user
`account_enabled`	No	Whether the account is enabled
`user_principal_name`	Yes	The user principal name (email format, e.g., user@domain.com)
`force_change_password`	No	Whether user must change password on first login

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 2, 2026

TDQS

C2.8/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full disclosure burden, yet it only restates the mutation. It says nothing about required permissions, whether the account is immediately active, what happens with an existing UPN, or whether the created user object is returned. For an account-provisioning mutation this is a substantial gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with zero waste and the verb is front-loaded, but its brevity comes from under-specification rather than disciplined editing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter write tool with no annotations and no output schema, the description leaves out permissions, idempotency, error conditions, and return information. An agent could call it, but has no basis for handling failure or verifying success.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and all six parameters, including the four required ones and the two optional booleans with defaults, are documented in the schema. The description adds nothing beyond that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb (Create) and resource (a new user) in a named platform (Microsoft 365), so the operation is unambiguous. It does not distinguish itself from siblings such as get_user or search_user, though the create-vs-read distinction is implicit in the verb.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus alternatives, no prerequisites (e.g. required admin roles or licensing), and no note about duplicate user principal names. The agent must infer everything from the sibling list.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.