Microsoft Planner: Introducing Local Custom Fields

Microsoft Planner introduces Local Custom Fields, allowing users with Planner Premium licenses to add up to 10 customizable fields (Text, Number, Date, Yes/No, Choice) to tasks for tailored workflows. Microsoft 365 users have read-only access. The rollout begins late October 2026, with no admin setup required. Custom fields integrate with existing compliance and audit features. We are introducing Custom Fields in Microsoft Planner, enabling users to tailor plans to match the way their teams work. Users can add Text, Number, Date, Yes/No, and Choice fields to capture information that matters to their workflows and manage that information across Board, Grid, and Task details. Rollout schedule General Availability (Worldwide): Rollout begins in late October 2026 and is expected to complete by early November 2026. Impact on your organization Who is affected Users with a Planner Premium P1, P3, or P5 license Users with a Microsoft 365 license Platforms and services Microsoft Planner What will happen Users with a Planner Premium P1, P3, or P5 license will be able to create, edit, and manage Custom Fields and their values. Users with a Microsoft 365 license can view Custom Fields and values as read-only and export them but cannot create or edit them. Users can add up to 10 custom fields with 255 characters each to tasks in a plan for information beyond Planner’s built-in fields. Available types are Text, Number, Date, Yes/No, and Choice, and field names can be up to 255 characters. Choice fields are single-select and can contain 2 to 25 colored options. Field values can be viewed and updated across Board, Grid, and Task details and used for sorting, filtering, grouping, and bulk editing. This feature is optional. Existing plans are not affected unless users add Custom Fields. Existing compliance capabilities cover custom field data, including Unified Audit Log, eDiscovery, Microsoft Information Protection through inherited plan-level labels, and Data Lifecycle Management. Action required and recommendations No tenant-level configuration or admin setup is required to enable Custom Fields. We recommend that you: Ensure users who need to create or edit Custom Fields have a Planner Premium P1, P3, or P5 […]

The post Microsoft Planner: Introducing Local Custom Fields appeared first on M365 Admin.