microsoft-entra-id

What This Skill Does

The Microsoft Entra ID skill provides a powerful interface for interacting with your organization's identity and access management infrastructure. It acts as a bridge between the OpenClaw agent and the Microsoft Graph API via the Membrane platform, allowing users to automate administrative tasks, retrieve directory information, and audit security logs without writing custom API code. Whether you need to provision new users, investigate sign-in anomalies, or manage complex group memberships, this skill centralizes these capabilities into natural language-driven commands.

Installation

To integrate this skill, follow these steps:

1. Execute the install command: clawhub install openclaw/skills/skills/gora050/microsoft-entra-id.
2. Ensure the Membrane CLI is installed via npm install -g @membranehq/cli.
3. Run membrane login --tenant to authenticate your environment.
4. Search for the connector using membrane search microsoft-entra-id --elementType=connector --json.
5. Initialize the connection using membrane connect --connectorId=<ID> and follow the browser prompts.

Use Cases

This skill is designed for system administrators, IT support, and security analysts. Key use cases include:

• Identity Management: Bulk creation or updating of user profiles, assigning licenses, and managing department-specific group memberships.
• Security Auditing: Querying sign-in logs to identify suspicious activity or tracking device compliance status across the organization.
• Governance: Managing Entitlement Management access packages and auditing custom security attributes to ensure compliance with internal security policies.
• Automation: Triggering role assignments or identity governance tasks in response to HR system events or onboarding workflows.

Example Prompts

1. "List all users in the 'Marketing' group and tell me who has not logged in during the last 30 days."
2. "Find the sign-in logs for user '[email protected]' from yesterday and highlight any failed authentication attempts."
3. "Assign the 'Global Reader' role to the new application service principal with ID 'a1-b2-c3-d4'."

Tips & Limitations

• Permissions: Ensure that the service principal or account used for the Membrane connection has sufficient Graph API permissions (e.g., Directory.ReadWrite.All) to perform the requested actions.
• Rate Limiting: Be aware of Microsoft Graph API throttling limits when performing bulk operations; the skill handles authentication, but long-running tasks should be monitored.
• Data Security: Always verify the scope of access granted during the membrane login flow to adhere to the principle of least privilege.