Change to Planner Sync Behavior for “Action By:” Date Field
Starting late August 2025, Planner will no longer auto-fill due dates from the “Action By:” field. New tasks require manual or custom-set due dates, offering more flexibility. Existing tasks remain unchanged. No admin action needed; update documentation and automation accordingly. To give you more control over task management timelines, we’re updating how the “Action By:” date field syncs with Microsoft Planner. This change will stop automatically populating the Planner due date based on the “Action By:” field, allowing teams to manage due dates independently. When this will happen This change will be rolling out in late August 2025. How this affects your organization New Planner items will no longer have their due date auto-filled from the “Action By:” field. Existing Planner items will remain unchanged. Users can now set due dates based on internal priorities and workflows, offering greater flexibility. This change is applied by default and does not require admin action to enable. What you can do to prepare Inform users who rely on Planner task automation that due dates will now need to be set manually or through custom logic. Review any internal documentation or training materials that reference the “Action By:” field behavior. If you use Power Automate or other tools to manage Planner tasks, consider updating flows to reflect this change. Compliance considerations No compliance considerations identified, review as appropriate for your organization. Message ID: MC1138236
The post Change to Planner Sync Behavior for “Action By:” Date Field appeared first on M365 Admin.
Published on:
Learn moreWe can help you with Change to Planner Sync Behavior for “Action By:” Date Field
If you want help implementing, troubleshooting, or improving this product, contact us and we’ll point you in the right direction.
Related posts
Microsoft Teams: Phishing detection for messaging
Microsoft Teams will introduce AI-powered, context-aware phishing detection starting November 2026, focusing on external first-contact chats a...
Intelligent Call Delegation in Teams
Intelligent Call Delegation in Teams uses AI to answer calls, gather context, and schedule follow-ups via Microsoft Bookings, helping users fo...
Copilot Code is rolling out in Frontier
Copilot Code, an AI-powered coding tool in Microsoft Copilot, is rolling out in the Frontier program starting late October 2026. It enables us...
Outlook: Copilot Prioritize feature will be retired
The Outlook Copilot Prioritize feature will be retired starting October 26, 2026, with removal completed by mid-November 2026 across all Outlo...
Microsoft Teams: Chat for organizers and presenters in structured meetings and webinars on Teams Rooms on Android
Teams Rooms on Android with Teams Rooms Pro license will gain access to a private presenter chat in green room-enabled meetings/events when jo...
Projects in Copilot
Projects in Copilot unify related chats, Cowork tasks, files, and context in one place, reducing repeated explanations. Available now in Cowor...
Microsoft 365 apps: Updated Brand Kit management experience
Microsoft 365 apps updated the Brand Kit management experience to simplify setup, streamline asset management, and improve workflows for Brand...
Microsoft Entra: Choose your own telephony provider for SMS and voice authentication
Starting October 30, 2026, Microsoft Entra ID allows organizations to choose a supported third-party telephony provider for SMS and voice auth...
New Outlook for Windows: All Accounts view brings email into a single inbox view
The new Outlook for Windows introduces an All Accounts view, a unified inbox showing emails from multiple accounts separately without merging....
Microsoft OneNote: CSV and TSV references in Copilot Notebooks
Microsoft OneNote now supports using CSV and TSV files as knowledge sources in Copilot Notebooks, enhancing content generation with structured...