Announcement ID | MC937952 | Published Date | 11-20-2024 | |
Service | Microsoft Teams | Last Updated | 12-06-2024 | |
Category | Stay informed | Expiration Date | 02-21-2025 | |
Roadmap ID | 464175 | Action Required by Date | ||
Tags | Feature update, User impact |
Summary |
---|
The Microsoft Teams Planner tab experience is being updated to include built-in templates for creating plans. Rollout will begin in early January 2025 and finish by mid-January. This update is automatic and requires no admin action. Users with Microsoft 365 and Microsoft Project licenses can also add premium plans. Documentation will be updated accordingly. |
More Information |
---|
Before this rollout, users with a Microsoft 365 license can use the Planner tab in Microsoft Teams to create and add existing basic plans and lists to standard channels in Teams. With this update, these users will be able to use built-in templates in the Planner tab in Teams to create plans. If users have licenses for Microsoft 365 and Microsoft Project, they can also create and add existing premium plans to Planner tabs. Plans added to Teams channels with the existing Planner tab will continue to work after the rollout and will not be affected by the rollout. This message applies to Teams for Windows desktop, Teams for Mac desktop, and Teams for the web. When this will happen:General Availability (Worldwide): We will begin rolling out early January 2025 (previously early December) and expect to complete by mid-January 2025 (previously mid-December). How this will affect your organization:To access the built-in templates in the Planner tab in Teams, select Create new plan in the Planner tab. Templates will be below the options to create basic and premium plans from scratch. This change will be on by default. What you need to do to prepare:This rollout will happen automatically by the specified date with no admin action required before the rollout. Review your current configuration to determine the impact for your organization. You may want to notify your users about this change and update any relevant documentation. |