28-June-2024 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!
Office 365 Roadmap Updated: 2024-06-27
Additions : 1
Updates : 8
More Details At: www.roadmapwatch.com
Office 365 Roadmap Updated: 2024-06-27
Additions : 0
Updates : 1
More Details At: www.roadmapwatch.com
| Updated Features | Current Status | Update Type | ||
|---|---|---|---|---|
| Outlook: New options to copy email items in the new Outlook for Windows and web | Launched | Status |
Items from the MessageCenter in Microsoft 365
| (Updated) Microsoft Teams: In Chat, “Files” will be renamed to “Shared” and get new featuresCategory:Microsoft TeamsNummer:MC800850Status:stayInformed | Updated June 27, 2024: We have updated the images to show as intended. Thank you for your patience. Coming soon in Microsoft Teams: Discover more content easily with the new Shared tab in Chat. After this rollout, the Files tab will be named Shared. The Shared tab will show files and links sent in a chat, in a new, richer format. Channels are not affected by this change. This message applies to Teams for Desktop and for Mac. This message is associated with Microsoft 365 Roadmap ID 396169. [When this will happen:] Targeted Release: We will begin rolling out early July 2024 and expect to complete by mid-July 2024. General Availability (Worldwide): We will begin rolling out mid-July 2024 and expect to complete by late July 2024. [How this will affect your organization:] Before the rollout, the Files tab displayed one list of files shared in the chat and did not include links. After the rollout, the new Shared tab will include recent files, all files, and links.
Like the Files tab, the new Shared tab is on by default and accessible to all Teams users. The new Shared > Recent view in Chat:
The new Shared > Files view in Chat:
The new Shared > Links view in Chat:
[What you need to do to prepare:] This rollout will happen automatically by the specified dates with no admin action required before the rollout. You may want to notify your users about this change and update any relevant documentation as appropriate. |
| (Updated) Microsoft Viva Insights: Delegate access to Microsoft Copilot DashboardCategory:Microsoft VivaNummer:MC801259Status:stayInformed | Updated June 27, 2024: We have updated the content below with a link to additional information. Thank you for your patience. Coming soon to Microsoft Viva: Leaders will be able to delegate access to their Microsoft Copilot Dashboard to others in their company. Designated delegates, such as the leader’s chief of staff or direct reports, will be able to view Copilot Dashboard insights and use them to make data-driven decisions. Designated delegates have the same access to Copilot Dashboard as the leader but cannot see the leader’s personal insights. This message applies to Viva Insights on Desktop, on the web, on iOS/Android, and in Microsoft Teams. This message is associated with Microsoft 365 Roadmap ID 398976.
[When this will happen:] General Availability (Worldwide): We will begin rolling out late June 2024 and expect to complete by early July 2024. [How this will affect your organization:] Before this rollout: Leaders were unable to delegate access to their Copilot Dashboard. After this rollout: A few things to note about delegating access to the Copilot Dashboard:
Add delegates to view your Copilot Dashboard (Viva > Insights > Copilot Dashboard > Three-dot menu in top right> Delegate access):
This feature is on by default and is available to all Viva leaders. Admins can disable the feature at the tenant level using Viva feature access management policies. [What you need to do to prepare:] Review and assess the impact for your organization. This rollout will happen automatically by the specified dates with no admin action required before the rollout. You may want to notify your users about this change and update training and documentation as appropriate. Learn more: |
| Microsoft Teams: New preapproval policies for RSC permissionsCategory:Microsoft TeamsNummer:MC805712Status:stayInformed | We are excited to announce public preview of preapproval policies for resource-specific consent (RSC) permissions. Preapproval policies for RSC permissions (enabled by PowerShell cmdlets) give admins the ability to allow users to grant consent to data through RSC without having to allow all RSC enabled applications in their organization. This feature will allow admins to create policies to allow users to consent to RSC permissions on an app-by-app basis. [When this will happen:] Targeted Release: We began rolling out June 24, 2024, and expect to complete by late June 2024. General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-September 2024 and expect to complete by late September 2024. [How this will affect your organization:] Before this rollout: Apps that used RSC permissions required admins to enable organization-wide settings, allowing users to consent to all RSC-enabled apps. After this rollout: Preapproval policies will give admins more granular control over which RSC-enabled apps are available to users and enables better management of app upgrades that require new permissions. With preapproval policies, users can grant RSC permission to their resources on an app-by-app basis. This means admins can approve apps for a particular set of permissions while keeping RSC blocked for all other applications. Admins can enable multiple preapproval policies to create custom RSC consent abilities in their organization. Admins will also be able to set preapproval policies based on sensitivity labels for Teams, allowing apps to be installed in Teams with certain sensitivity labels but not others. Preapproval policies are enabled by a set of PowerShell cmdlets for now. Admins who have never used PowerShell to manage Teams can learn more about using PowerShell and the preapproval policy documentation. This new feature is accessible to all Teams admins with appropriate permissions. [What you need to do to prepare:] Admins do not need to take action for this rollout. No existing settings will be changed or affected by this rollout. Admins who wish to utilize the new preapproval policies should refer to the preapproval policy documentation. You may want to notify your admins about this change and update any relevant documentation as appropriate. Learn more |
| Updates available for Microsoft 365 Apps for Current ChannelCategory:Microsoft 365 appsNummer:MC805714Status:stayInformed | We've released updates to the following update channel for Microsoft 365 Apps:
[When this will happen:] We'll be gradually rolling out this update of Microsoft 365 Apps to users on that update channel starting June 26th, 2024 (PST). [How this will affect your organization:] If your Microsoft 365 Apps clients are configured to automatically update from the Office Content Delivery Network (CDN), then no action is required. If you manage updates directly you can now download this latest update and begin deployment. [What you need to do to prepare:] To get more details about this update view the following release notes: |
| Microsoft Secure Score – changing Microsoft Defender for Identity recommendationCategory:Microsoft Defender XDRNummer:MC805719Status:planForChange | We’re updating the Microsoft Secure Score improvement action of Microsoft Defender for Identity (MDI) to ensure a more accurate representation of security posture. As part of this update, we will gradually withdraw the MDI recommendation on Manage accounts with passwords more than 180 days old. We are working to refine the security assessment report, ensuring it aligns more accurately with recommended policies and enhances the overall security value. [When this will happen:] General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out in mid-July 2024 and expect to complete by mid-August 2024. [How this will affect your organization:] The Manage accounts with passwords more than 180 days old recommendation will be completely removed from the UI, and the score will be changed in accordance. This update is 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 Dataverse – Service Update 9.2.24064.00000 for EURCategory:Microsoft DataverseNummer:MC805890Status:stayInformed | We have a minor service update planned for your Microsoft Dataverse environment hosted in EUR. This service update will occur within your region’s scheduled maintenance timeline, on the scheduled date listed for Microsoft Dataverse. How does this affect me? The version number for your Microsoft Dataverse environment will update to version 9.2.24064.00000 or higher. There is no expected degradation to service performance or availability, however, during this maintenance window users may see short, intermittent impact such as transient SQL errors or a redirect to the login screen. What action do I need to take? This message is for awareness and no action is required. |
| Introducing Config Refresh for mobile device management Category:WindowsNummer:MC805997Status:stayInformed | A new Windows 11 feature is available to help you manage your company’s policies using mobile device management (MDM). Starting with the May 2024 non-security update, you can now use Config Refresh to configure policy refresh timing to be as short as 30 minutes or as long as 24 hours. This helps improve security and compliance as you monitor that settings don’t drift from your intent. Learn how you can use the Microsoft Intune Settings Catalog to manage Config Refresh and troubleshoot it in the Event Viewer. Find more details in Intro to Config Refresh – a refreshingly new MDM feature. When will this happen: This feature is available for Windows 11 beginning with the May 2024 non-security update. How this will affect your organization: Config Refresh can help you manage devices more securely and stop configuration drift. Note: Config Refresh is designed to work with MDM policies managed by the Policy CSP. Some policies, notably the BitLocker CSP, will also adhere to Config Refresh enablement. Other policies are outside of this scope, such as Firewall, AppLocker, PDE, and LAPS. What you need to do to prepare: To enable Config Refresh, your PCs must be running Windows 11, version 23H2 or version 22H2 with the June 2024 security update installed (or later). To get ready, please read the official announcement and additional information linked below. Additional information:
|
