| Announcement ID | MC913444 | Published Date | 10-18-2024 | |
| Service | Microsoft Teams | Last Updated | 10-18-2024 | |
| Category | Plan for change | Expiration Date | 02-28-2025 | |
| Roadmap ID | 412076 | Action Required by Date | ||
| Tags | Admin impact, New feature, User impact | |||
| Summary |
|---|
| Microsoft Teams is introducing a new Project Studio environment for immersive meetings and Microsoft Mesh events, optimized for small group collaboration. Rolling out starts in early November 2024, with general availability by late December 2024. No admin action is required for the rollout. |
| More Information |
|---|
Coming soon for Microsoft Teams: The Project Studio environment will be a beautiful new environment for immersive meetings in Teams and for Microsoft Mesh events, designed for synchronous teamwork and productivity, and optimized for small group collaboration. This message applies to Mesh events on Windows desktops, Mac desktops (for TAP users), and on Meta Quest headsets. When this will happen:Targeted Release: We will begin rolling out early November 2024 and expect to complete by mid-November 2024. General Availability (Worldwide): We will begin rolling out mid-November 2024 and expect to complete by late December 2024. How this will affect your organization:After this rollout, event organizers will have one new environment (Project Studio) to use in Mesh events. Event organizers will be able to create events using the Project Studio environment via the Mesh Portal. These changes are on by default. Users can access the Project Studio environment in the Mesh Portal on the web at Events > Create event > Start from scratch: Project Studio will appear next to Workshop, Oasis, and Meadow in Start from scratch during event creation: In the Mesh standalone app, the Project Studio environment will look like this during an event: This is a view of the entire Project Studio environment: 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. |
