M365 Planner

---

name: m365-planner description: Manage Microsoft 365 Planner plans, buckets, and tasks via Microsoft Graph API. Use when creating, listing, updating, or deleting Planner resources. Supports group-based plan management, task assignment, progress tracking, and recurring tasks. Requires Azure AD app registration with Group.Read.All and Tasks.ReadWrite.All permissions. license: MIT version: 1.2.3

---

M365 Planner Skill

Manage Microsoft 365 Planner through Microsoft Graph API.

What's New in v1.2.3

🌍 English Documentation – Complete translation for international ClawHub availability

🔧 Portability – Env path now uses os.homedir() instead of hardcoded paths

🧹 Security Cleanup – Full audit for sensitive data (no IDs, names, domains)

📦 ClawHub-ready – Tarball created, node_modules excluded

What's New in v1.2.2

🔧 Portability – Env path now uses os.homedir() instead of hardcoded /home/claw/.openclaw/.env

🧹 Security Cleanup – Full audit for sensitive data (no IDs, names, domains)

📦 ClawHub-ready – Tarball created, node_modules excluded

What's New in v1.2.1

✅ Generic Scripts – No hardcoded Group-IDs or Plan names anymore

✅ Command-Line Parameters – All scripts accept IDs as arguments

✅ List Plans Improved – Shows all groups when no ID provided

✅ Flexible Cleanup – Works with any plans/buckets

✅ ClawHub-ready – No project-specific data included

What's New in v1.1.0

✅ Node.js Scripts – Standalone scripts without mgc CLI

✅ If-Match Header Support – Correct ETag handling for updates/deletes

✅ Group-Based API – Direct access via M365 Group-ID

✅ Recurring Tasks – Note about native Planner recurrence feature

✅ Cleanup Scripts – Automated task cleanup

Prerequisites

1. Azure AD App Registration (see Setup below) 2. Node.js v18+ with @microsoft/microsoft-graph-client and axios 3. M365 Group (not Security Group or Distribution List!)

Quick Start

# Test connection
node scripts/test-connection.js
List all plans
node scripts/list_plans.js
List plans for specific group
node scripts/list_plans.js 
Create plan
node scripts/create_plan.js "Project Name" 
Create task
node scripts/create_task.js   "Task Title"
Delete completed tasks
node scripts/cleanup_verlaengerungen.js  "" ""

Setup: Azure AD App Registration

Step 1: Create App Registration

Azure Portal: 1. https://portal.azure.com → Azure Active Directory → App registrations 2. "New registration" 3. Name: M365-Planner-Integration 4. Supported account types: Accounts in this organizational directory only 5. Redirect URI: None (Client Credentials Flow)

Or via Azure CLI:

az login
az ad app create --display-name "M365-Planner-Integration" --sign-in-audience "AzureADMyOrg"

Note the Application (client) ID from the output.

Step 2: Add API Permissions

Important: Use Application Permissions (not Delegated)!

Azure Portal: 1. App → API permissions → Add a permission 2. Microsoft Graph → Application permissions 3. Add: - Group.Read.All (not Group.ReadWrite.All – sufficient for Planner) - Tasks.ReadWrite.All 4. Grant Admin Consent: Click "Grant admin consent for [Tenant]"!

Or via Azure CLI:

APP_ID="your-app-id"
Group.Read.All
az ad app permission add \
  --id $APP_ID \
  --api 00000003-0000-0000-c000-000000000000 \
  --api-permissions 5b567253-7703-48e2-861c-caed61531407=Role
Tasks.ReadWrite.All
az ad app permission add \
  --id $APP_ID \
  --api 00000003-0000-0000-c000-000000000000 \
  --api-permissions bdfbf15f-ee85-495a-99a9-ef9b2abb1dcb=Role
Admin Consent
az ad app permission admin-consent --id $APP_ID

Step 3: Create Client Secret

Azure Portal: 1. App → Certificates & secrets → Client secrets → New client secret 2. Description: OpenClaw Integration 3. Expires: 24 months (Maximum) 4. Copy values immediately! – Only shown once

Or via Azure CLI:

az ad app credential reset \
  --id $APP_ID \
  --append \
  --display-name "OpenClaw Integration"

Step 4: Configure Environment

Store credentials in ~/.openclaw/.env:

# Microsoft 365 Planner Credentials
M365_CLIENT_ID="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
M365_CLIENT_SECRET="your-secret-value"
M365_TENANT_ID="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"

Secure permissions:

chmod 600 ~/.openclaw/.env

Step 5: Test Connection

node scripts/test-connection.js

Expected output:

✅ Access Token successfully received!
📋 Test: M365 Groups...
   3 groups found:
   - My Team ✅ M365/Planner-capable
✅ Connection successful!

Important Notes

M365 Groups vs. Security Groups

Planner ONLY works with M365 Groups!

✅ M365 Group – Has Exchange mailbox, Teams, Planner (recognizable by mail attribute)

❌ Security Group – Only for permissions, no Planner

❌ Distribution List – Only for email distribution, no Planner

Check groups:

node scripts/test-connection.js

Shows all groups with status "✅ M365/Planner-capable".

Create M365 Group (if none exists):

Microsoft 365 Admin Center → Groups → Add a group

Or Teams: Create new team (automatically creates M365 Group)

If-Match Header (ETag)

All update and delete operations require the If-Match header!

Planner uses Optimistic Concurrency Control. Requests fail without ETag.

Delete Example:

// Wrong ❌
await client.api(/planner/tasks/${taskId}).delete();
// Correct ✅
const task = await client.api(/planner/tasks/${taskId}).get();
await client.api(/planner/tasks/${taskId})
    .headers({ 'If-Match': task['@odata.etag'] })
    .delete();

Update Example:

const task = await client.api(/planner/tasks/${taskId}).get();
await client.api(/planner/tasks/${taskId})
    .headers({ 'If-Match': task['@odata.etag'] })
    .update({ percentComplete: 50 });

Group-Based API Endpoints

Do NOT use:

GET /planner/plans  ❌ (requires complex filter)

Use:

GET /groups/{group-id}/planner/plans  ✅

Example:

const plans = await client.api(/groups/${groupId}/planner/plans).get();

Recurring Tasks

Microsoft Planner supports native recurring tasks!

In Planner Web UI or Mobile App: 1. Open task 2. Click "Repeat" 3. Choose frequency: Daily, Weekly, Monthly, Yearly, Custom

Example:

"Domain renewal example.com" → Repeat yearly

"Check backup" → Repeat weekly

⚠️ API Limitation: The Graph API does not support creating recurring tasks directly. Recurring tasks must be set up via Planner UI.

Common Operations

Plans

| Operation | Script | |-----------|--------| | List all plans | node scripts/list_plans.js | | Create plan | node scripts/create_plan.js | | Delete plan | node scripts/delete_plan.js |

Buckets

| Operation | Script | |-----------|--------| | List buckets | Integrated in list_plans.js | | Create bucket | node scripts/create_bucket.js | | Delete bucket | node scripts/delete_bucket.js |

Tasks

| Operation | Script | |-----------|--------| | List tasks | Integrated in list_plans.js | | Create task | node scripts/create_task.js