--- title: Microsoft Planner API Integration on Truto slug: microsoftplanner category: Ticketing canonical: "https://truto.one/integrations/detail/microsoftplanner/" --- # Microsoft Planner API Integration on Truto **Category:** Ticketing **Status:** Generally available ## Unified APIs ### Unified Ticketing API - **Attachments** — Attachments are the files associated with a ticket or a comment. - **Collections** — Tickets and contacts can be grouped into Collections. Collection resource usually maps to the various grouping systems used in the underlying product. Some examples are lists, projects, epics, etc. You can differentiate between these grouping systems using the type attribute of a Collection. - **Ticket Priorities** — Ticket Priorities represent the intended order in which the Tickets should be worked on. Some products provide customizing the Ticket Priorities. - **Tickets** — Core resource which represents some work that needs to be carried out. Tickets are usually mapped to issues, tasks, work items, etc. depending on the underlying product. - **Users** — Users represent the people using the underlying ticketing system. They are usually called agents, team members, admins, etc. - **Workspaces** — Workspaces represent the top-level subdivision in a ticketing system. They usually have their own set of settings, tickets, statuses, priorities and users. Some of the usual terminologies used by the products for the top-level subdivision are projects, bases, spaces, workspace, etc. A Workspace could belong to an Organization. ## How it works 1. **Link your customer's Microsoft Planner account.** Use Truto's frontend SDK; we handle every OAuth and API key flow so you don't need to create the OAuth app. 2. **Authentication is automatic.** Truto refreshes tokens, stores credentials securely, and injects them into every API request. 3. **Call Truto's API to reach Microsoft Planner.** The Proxy API is a 1-to-1 mapping of the Microsoft Planner API. 4. **Get a unified response format.** Every response uses a single shape, with cursor-based pagination and data in the `result` field. ## Use cases - **Push helpdesk escalations into Microsoft Teams workflows** — ITSM and helpdesk platforms can automatically create Planner tasks when tickets are escalated to internal ops teams who live in Microsoft Teams. This bridges the gap between specialized support tooling and the customer's daily work hub without requiring ops staff to learn a new system. - **Automate sales-to-onboarding handoffs via task creation** — CRM and revenue platforms can spawn structured onboarding tasks in a customer's Planner board when deals close, complete with checklists, assignees, and deep links back to the deal record. This eliminates manual handoff processes between sales and customer success teams. - **Convert monitoring alerts into actionable tasks** — IoT, observability, and compliance platforms can push high-priority alerts directly into Planner boards instead of relying on email notifications that get buried. Floor managers, IT admins, and compliance officers see actionable tasks in the tool they already check daily. - **Aggregate cross-team task data for executive dashboards** — BI, resource planning, and project portfolio tools can pull task and completion data out of Planner to calculate workload distribution, project health, and team velocity across departments — especially valuable in large enterprises with dozens of active Plans. - **Sync workflow stages bidirectionally between your app and Planner** — Any SaaS product with a pipeline or workflow concept can map its stages to Planner buckets and keep status synchronized in both directions, so updates made by end users in Microsoft Teams are reflected back in your application automatically. ## What you can build - **Two-way ticket-to-task sync** — Keep tickets in your platform and Planner tasks synchronized bidirectionally — when a task moves to 'Completed' in Planner, the corresponding ticket in your system resolves automatically, and vice versa. - **Automated task creation with rich details** — Spawn Planner tasks from events in your app, populated with descriptions, checklist items, priority levels, assignees, and deep-link attachments back to the originating record. - **Dynamic bucket mapping for workflow stages** — Automatically create and map Planner buckets to your app's workflow stages so tasks land in the right Kanban column as they progress through your pipeline. - **User lookup and smart assignment** — Query Entra ID users through the integration to let your customers assign Planner tasks to specific team members directly from your product's UI. - **Priority normalization across tools** — Map your application's severity or priority levels to Planner's priority scale so that urgency context is preserved when tasks flow between systems. - **Cross-plan task aggregation dashboard** — Pull tasks from multiple Planner plans into a single view inside your app, giving managers visibility into workload and completion rates across teams and departments. ## FAQs ### How does authentication work for Microsoft Planner integrations? Microsoft Planner is accessed via the Microsoft Graph API, which uses OAuth 2.0 with Microsoft Entra ID (formerly Azure AD). Truto handles the full OAuth flow, token refresh, and consent management so your end users can connect their Microsoft 365 accounts without you building auth infrastructure. ### How does Planner's data model map to the Unified Ticketing API? Plans map to Workspaces, Buckets map to Collections, Tasks map to Tickets, Entra ID users map to Users, Task Details (descriptions and URL links) map to Attachments, and Planner's 1-10 priority scale maps to Ticket Priorities. This mapping lets you work with a consistent schema across ticketing tools. ### Are there rate limits I need to worry about with the Microsoft Graph API? Yes, Microsoft Graph enforces per-app and per-tenant throttling limits. Truto manages pagination and request handling to work within these limits, but high-volume sync scenarios may need to account for 429 (Too Many Requests) responses and retry logic. ### Can I write data back to Microsoft Planner or is it read-only? The Microsoft Graph API supports full CRUD operations on Planner tasks, buckets, and task details. Through Truto's Unified Ticketing API, you can create and update tickets (tasks), manage collections (buckets), and attach details — enabling true bidirectional sync workflows. ### Why are Planner tasks split across two API endpoints? Microsoft Graph separates task core metadata (title, assignments, priority, dates) from task details (description, checklist items, URL references). This means enriching a task with descriptions or deep-link attachments requires an additional API call to the Task Details endpoint. Truto abstracts this so you work with a unified ticket object. ### Is the Microsoft Planner integration available today on Truto? Microsoft Planner is available as a Unified Ticketing API integration built on request. Truto can provision the integration with the specific resources you need — including Tickets, Collections, Workspaces, Users, Attachments, and Ticket Priorities — tailored to your use case.