05-February-2025 Below you will find a collection of news published yesterday. This news consists of Microsoft’s Roadmap when it is updated it will be below with items. Then there will be a section with the message center, if there is anything new there, this will be automatically included. And it contains a piece from blogs that I follow myself and would like to share with you. If I miss something in the blogs that do have an RSS feed, please let me know.
This entire post was automated via Microsoft Flow
have fun reading!
The blogs of this day are:
Office 365 Roadmap Updated: 2025-02-05
Additions : 11
Updates : 18
More Details At: www.roadmapwatch.com
Items from the MessageCenter in Microsoft 365
| (Updated) Whiteboard: existing Azure board migration to ODB storageCategory:Microsoft 365 appsNummer:MC677236Status:planForChange | Updated July 10, 2024: We have updated the rollout timeline below. Thank you for your patience. Whiteboard previously stored whiteboard files in Azure storage. In 2022, Whiteboard switched to OneDrive as the storage location for most newly created boards. We are making a client-based migration available for your organization soon. This message is associated with Microsoft 365 Roadmap ID 117394 [When this will happen] The client-based migration experience will begin in December 2024 (previously July). We will provide an additional update as we get closer. [How this will affect your organization] Any user who launches an eligible Whiteboard client (Whiteboard on Windows, Whiteboard in Teams desktop/web) will automatically kick off a non-blocking migration of all their whiteboards. Depending on how many whiteboards they have, on average the process will take between a few seconds to a few minutes. The migration will provide many benefits for your organization and users on the migrated boards, including:
There is no possibility to delay the migration. [What you need to do to prepare] The migration will happen naturally and automatically for most users in your organization with no disruption, but please ensure that users are aware they need to launch Whiteboard in one of the previously mentioned clients in order to keep their content prior to the conclusion of migration (date to be announced) In the unlikely case that a user’s whiteboards fail to migrate, they will see an error banner. We will attempt to migrate the board again in 30 days. If the board contains important information, we recommend the user copy the content to a new whiteboard. Users will be able to see which boards have not migrated in a dedicated section on the board picker. Admins will be able to verify what whiteboard content remains in Azure and obtain the userIDs via our PSH cmdlets, if you wish to proactively notify users to get their content. As we get closer to the release of the client-based migration experience we will provide additional information via Message center. |
| (Updated) Teams admin center: App centric management and changes to app permission policiesCategory:Microsoft TeamsNummer:MC688930Status:planForChange | Updated February 4, 2025: We have updated the rollout timeline below. Thank you for your patience. The migration to app-centric management using the Migration Wizard (referenced as Phase 2 in this post) is expected to resume by late-November 2024 and complete the roll out by mid-December 2024. At that time, administrators will be able to self-initiate the migration using the wizard. The automatic migration for customers with only a global permission policy (Phase 1) and those with multiple permission policies (Phase 3) will be postponed until early 2025. Further updates, including the details for Phase 3 auto-migration, will be provided in a future MC post update and public documentation. App centric management (ACM) is on hold as of August 14, 2024, and will restart in mid-October (previously mid-September). Your experience during this hold will fall under one of the following, with Phases defined in detail below.
What is in Phase 2?
Detailed documentation for the migration process is available at App centric management to manage user access to Teams apps – Microsoft Teams | Microsoft Learn. App centric management introduces new admin settings to control who in the tenant can install Teams apps. First, admins can set a default value for new apps that are published to the Teams app store. Second, admins can manage apps for users, groups, or everyone in the organization. This feature replaces the existing app permission policies and provides admins with the ability to manage access to the app individually. The app permission policies for existing customers are migrated to maintain existing app availability in the tenant. This message is associated with Microsoft 365 Roadmap ID 151829 [When this will happen:] This feature will gradually roll out across three major phases. Phase 1 (from late November 2023 to early November 2024 (previously late September) to late March 2025 affects the tenants that use only the Global app permission policy and have no custom app permission policies. The app status from the permission policy and tenant settings will be migrated to preserve the admin intent. The migration will not affect the end users and their ability to use the apps. Admins may see the Manage apps page in a read-only mode for a short time. Phase 2 (from late May 2024 to mid-December 2024 (previously mid-November)) affects the tenants that use both global and custom app permission policies. This phase will let the admin choose to migrate to app centric management by following a migration process that will change the existing app permission policies to app assignments in the new app centric model. The admins will have the choice to modify the apps that are assigned using the custom permission policies to be accessible to groups, if they want. Phase 3 (mid-April 2025) applies to the tenants that skipped the migration in phase 1 or 2. These tenants will be migrated automatically in this phase. More details to come as a follow up MC post. [How this will affect your organization:] Starting with this release, you can: 1. Manage Teams apps for selected set of users, groups or all users in the organization. 2. Set the default value for new apps published to Teams app store for each of the app types: Microsoft, third-party and custom apps. [What you need to do to prepare:] No action needed for phase 1 tenants with Global permission policy only. More information will be provided for phase 2 and 3 tenants in a follow-up communication before launch. |
| (Updated) Microsoft Teams admin center: App centric management for app installation and changes to app setup policiesCategory:Microsoft TeamsNummer:MC795355Status:planForChange | Updated February 4, 2025: We have updated the rollout timeline below. Thank you for your patience. Coming soon for Microsoft Teams: App centric management for admin app installation introduces new admin settings to control who in the tenant has specific Teams apps preinstalled. Similar to app centric management for app availability, as communicated in MC688930 (Updated) Teams admin center: App centric management and changes to app permission policies (November 2023), admins will be able to install apps for users, groups, or everyone in the organization. After rollout, app centric management will replace Installed apps in the Teams admin center and give admins the ability to install apps individually. The Installed apps in your app setup policies will be migrated to app centric management based on your current user and group assignments for each policy. The rest of your settings in app setup policies will remain unchanged and will continue to work based on app setup policies, including Pinned apps. After this rollout, you can install Teams apps for selected sets of users, groups, or all users in the organization, and Installed apps in app setup policies will no longer be available. This message is associated with Microsoft 365 Roadmap ID 394274. [When this will happen:] App centric management will roll out in four General Availability phases.
[How this will affect your organization:] Before the rollout: If you install an app to a user, the user cannot actually use an admin preinstalled app if you did not take the additional step to allow the user to use it. After the rollout, if you install an app through app centric management, the user will immediately be able to use the app.
Before the roll out, a user will only have apps installed from a single app setup policy, following the policy resolution precedence rules. After the rollout, if you have multiple custom app setup policies assigned to users or groups, apps from every policy will be installed to the user or group assigned to that policy, regardless of the policy resolution precedence rules. [What you need to do to prepare:] No action needed for Phase 1 tenants. We will update this message with more information before the rollouts for Phases 2-4 tenants. You may want to update any relevant documentation as appropriate. Before rollout, we will update this post with revised documentation. |
| (Updated) Microsoft Outlook: Themes by Copilot will be available starting November 2024Category:Microsoft Copilot (Microsoft 365)Nummer:MC912174Status:stayInformed | Updated February 4, 2025: We have updated the rollout timeline below. Thank you for your patience Starting November 2024, Microsoft Outlook will roll out Themes by Copilot. Copilot users can create and apply a Copilot-generated theme inspired by a global place of interest from a curated list of locations. Users can also choose a style and configure a theme refresh cadence. If users have enabled location permissions, they will also be able to create a theme inspired by their current weather or surroundings. This feature will be available for Outlook for Mac desktops, Outlook for iOS/Android, Outlook on the web, and the new Outlook for Windows desktops. A Microsoft 365 Copilot license is required to use this feature. This message is associated with Microsoft 365 Roadmap ID 394682. [When this will happen:] General Availability (Worldwide): We will begin rolling out early November 2024 and expect to complete by late March 2025 (previously late January). [How this will affect your organization:] This feature will be on by default and available for users to enable. [What you need to do to prepare:] This rollout will happen automatically starting on 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. Learn more: Frequently asked questions about Copilot in Outlook – Microsoft Support (will be updated before rollout) #newoutlookforwindows |
| (Updated) Microsoft Teams: New policy for voice and face enrollment will default to “On” (configure now)Category:Microsoft TeamsNummer:MC912707Status:planForChange | Updated February 4, 2025: Please verify that all previously set values remain unchanged and as intended. A new NOTE: Microsoft doesn’t use the voice and face profiles of users to train any models or for any other purposes other than providing the voice and face enrollment feature in Microsoft Teams. This message is associated with Microsoft 365 Roadmap ID 413708. [When this will happen:] The new Microsoft PowerShell cmdlets are available now for admins to configure, to ensure a smooth transition.
General Availability (Worldwide, GCC): The new Microsoft PowerShell cmdlets are available now for preparation and to ensure a smooth transition. The policy takes effect starting in mid-March 2025 (previously mid-February) and is expected to be fully in effect by late March 2025 (previously late February). [How this will affect your organization:] Before this rollout, the current policy After this rollout, the new [What you need to do to prepare:] This rollout will happen automatically by the specified date. Review your current configuration to determine the impact for your organization. You may want to notify your admins about this change and update any relevant documentation. If your organization prefers to disable voice and face enrollments, review and update your settings before mid-January 2025. To help you get started, review:
Learn more: Overview of voice and face enrollment – Microsoft Teams | Microsoft Learn If your organization prefers to disable voice and face enrollments, review and update your settings before mid-February 2025. Important: The EnrollUserOverride setting can be assigned globally, directly to users, or to groups in PowerShell. Admins must ensure that changes are applied consistently across all these locations to avoid unintended configurations.
|
| Power Platform – Govern critical Copilot settings and more with Environment GroupsCategory:Power PlatformNummer:MC996551Status:stayInformed | On February 3, 2025, we are introducing new rules for Environment Groups that give tenant administrators greater control over critical environment settings. The rules that have a “preview” tag are in Public Preview, while rules without it are considered Generally Available:
These rules will be automatically available within each environment group and enable Copilot functionality as described in the linked articles. What do I need to do to prepare? Tenant administrators must explicitly configure these rules for them to take effect. For more information about Environment Groups and Rules and they help IT govern at scale, please review the Environment groups article. |
| Communications on default checkbox changes on tenant settings and billing start for SQL database in FabricCategory:Power BINummer:MC996579Status:planForChange | We want to announce an upcoming change in the behavior of an existing tenant setting in Fabric that lets Fabric admins enable SQL database in their Fabric tenant. We will be introducing a checkbox on February 8, 2025, for tenant admins to accept Microsoft’s default selection (off for entire organization) for this specific setting. The default value for this setting will be turned on or after March 8th if Fabric admins do not take any action. This update helps enhance visibility and ease of access for our customers, ensuring you’re aware of and can leverage this functionality effortlessly. Note also, billing for compute usage and data storage for SQL databases in Fabric commenced after February 1st, with backup charges following after April 1st. For the latest updates on billing practices and to ensure you are fully informed on how charges are applied, please refer to the following detailed blog post: Monitor SQL database usage and consumption in Microsoft Fabric.
Why are we updating this setting?
The update to our tenant settings is designed to ensure Fabric admins can act based on their organizational policy before the setting is enabled by default. From February 8, 2025, when the checkbox is available to March 8, 2025, admins can assess impact and act on enablement. By setting SQL database in Fabric as a default option, we ensure that you don’t miss out on leveraging its full potential right from the start. This change reflects our commitment to enhancing user experience and operational efficiency. [When This Will Happen:]
[What You Need to Prepare:]
If you have any questions or need further assistance, please do not hesitate to contact our support team. |
| Update to Windows Autopatch diagnostic data collection levels and removal of Windows Autopatch data collection policyCategory:Windows AutopatchNummer:MC996580Status:planForChange | Updated February 4, 2025: We have updated the content. Windows Diagnostics data settings must be configured for Windows Autopatch reports to accurately include devices and update status. The minimum necessary Windows diagnostic data collection level to be configured on devices registered to Autopatch with the following diagnostic data settings: Windows 10 and Windows 11 – Required [With this change:]
[Action required:] Create and deploy a Windows Diagnostic data collection policy with at least the recommended minimum setting to all Autopatch devices prior to this change. You may see missing Client State and Client Substate values if your devices are not configured with the recommended Windows Diagnostics settings and level. Alternatively, you may already be covered with existing data collection policies in your environment.
TIP: You may want to consider using the Windows Autopatch – Devices All group which contains all of the active, registered devices presently in your Autopatch implementation across any and all Autopatch Groups. This is a service-managed group (subject to changes at any time). Not Registered devices will not appear in this Entra group.
|
| “Personal Information Removal” notification for filesCategory:Microsoft 365 for the web Microsoft 365 appsNummer:MC996584Status:stayInformed | The existing “Personal Information Removal” setting is often used by commercial users to purge a file before sharing it with their customers. When users try to start a new file by copying an old file, this setting is currently carried over. Some users are not aware of it and, therefore, get confused when they collaborate on the new file. For example, their actual names (part of personal information) are automatically replaced by the generic “Author” in their comments. We are reducing this confusion by notifying users that this setting is enabled and offering a way to disable it. When a file is opened for edit (not applicable for read-only files), if the “Personal Information Removal” setting is checked for the file, PowerPoint app displays the message This document is set to automatically remove personal information when saved and can impact your collaboration experience. Only keep this setting if needed. This message also comes with a “Change setting” button to disable the “Personal Information Removal” setting. [When this will happen:]
Public Preview: We will begin rolling out late February 2025 and expect to complete by early March 2025. General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-March 2025 and expect to complete by late March 2025. [How this will affect your organization:] This is a notification to make users aware of the “Personal Information Removal” document setting being enabled and providing a way for users to change this document setting. The existing way of changing this document setting via the Options dialog remains intact. This feature update will be available by default. [What you need to do to prepare:] This rollout will happen automatically with no admin action required. You may want to notify your users about this change and update any relevant documentation as appropriate. |
| Microsoft SharePoint: Updated document librariesCategory:SharePoint OnlineNummer:MC996585Status:stayInformed | Coming soon to Microsoft SharePoint: We will update the document library experience to improve its overall performance and enhance the functionality of Edit in grid view. [When this will happen:] General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-February 2025 and expect to complete by late March 2025. [How this will affect your organization:] After this rollout, users can expect these improvements: Pages in document libraries will load faster. Enhanced editing in grid view:
Better scrolling with large libraries: Instead of going to the next page if there are more than 100 documents, users can scroll down and see everything. New commands and navigation in grid view: With these improvements, grid view includes several new commands and navigational options that previously were either missing or less intuitive:
Details pane in grid view: Open the details pane in grid view. Redesigned Properties pane and right-click menu:
Grouped view support while editing in grid view: Edit items in grid view even when the library is grouped by specific columns (such as grouped by a content type, department, or project). Rating column improvements: If your document library includes a rating column (star ratings or “likes”), we improved the experience of updating and viewing these ratings. A SharePoint document library with an item’s menu expanded (in grid view):
A SharePoint document library showing editing option in a field (in grid view):
These changes will be available by default. [What you need to do to prepare:] This rollout will happen automatically by the specified date with no admin action required before or after the rollout. You may want to notify your users about this change and update any relevant documentation. Before rollout, we will update this post with revised documentation. |