14-January-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-01-14
Additions : 2
Updates : 14
More Details At: www.roadmapwatch.com
Items from the MessageCenter in Microsoft 365
| (Updated) Microsoft Teams: Describe it to design it in Teams WorkflowsCategory:Microsoft TeamsNummer:MC718250Status:stayInformed | Updated January 13, 2025: We have updated the rollout timeline below. Thank you for your patience. Can’t find a workflow template that matches what you need in Microsoft Teams? You will now be able to describe in detail how you want your automation to work and receive a workflow to match your needs. All you need to do is select the Workflow builder button at the bottom of the create dialog in the Workflows app in Microsoft Teams chat and channel overflow menu. Workflow builder will come to the Workflows app in Microsoft Teams chat and channel overflow menu first. Other entry points to Workflows will get this feature later. This message is associated with Microsoft 365 Roadmap ID 382659. [When this will happen:] Worldwide: We will begin rolling out late September 2024 (previously mid-September) and expect to complete by late October 2024 (previously late September). GCC Release: We will begin rolling out early October 2024 (previously mid-August) and expect to be complete by complete by late January 2025 (previously late December).
[How this will affect your organization:] All users with the ability to create workflows with the Workflows app in Teams will be able to describe the workflow they are trying to build and then receive a suggested flow. Prerequisites A work or school Teams account with access to a Power Automate environment in Europe or the United States. Limitations Power Automate supports workflow descriptions written in the English language only. Descriptions written in other languages might work but are not supported. Cloud flows are the only type of flow that you can create from a written description. In the version rolling out, the AI might omit some parameters, even if you provide them in the description. [What you need to do to prepare:] No action is needed to prepare for this rollout. If your tenant uses the Power Automate app within Microsoft Teams, you may want to notify your users about this change and update any relevant documentation as appropriate. To learn more: Create a cloud flow from a description (preview) – Power Automate | Microsoft Learn |
| (Updated) Microsoft Teams: New skin tone settings and reactionsCategory:Microsoft TeamsNummer:MC809602Status:stayInformed | Updated January 13, 2025: We have updated the rollout timeline below. Thank you for your patience With skin tone settings and reactions in Microsoft Teams, users will be able to set a preferred skin tone for relevant emojis and reactions. Each user can change their own skin tone setting in the Teams app Settings > Appearance and accessibility menu or in the emoji/reaction menu on Desktop or web. The skin tone rollout will apply to emojis and reactions in chats, channels, and meetings on all Teams platforms (Teams for Desktop, Teams for web, Teams for Mac, and Teams Mobile). This message is associated with Microsoft 365 Roadmap ID 323766. [When this will happen:] Targeted Release: We will begin rolling out late October 2024 (previously mid-October) and expect to complete by early November 2024 (previously late October). General availability (Worldwide, GCC): We will begin rolling out early November 2024 (previously late October) and expect to complete by late December 2024. General availability (GCC High, DoD): We will begin rolling out mid-November 2024 (previously mid-November) and expect to complete by late January 2025 (previously late December) [How this will affect your organization:] Changing skin tone in the emoji menu in Teams for Desktop:
Changing skin tone in Teams Settings > Appearance and accessibility in Teams for Desktop:
Changing skin tone in Teams Settings > Appearance on Teams Mobile:
The selected skin tone appears in reactions in chats, channels, and meetings:
[What you need to do to prepare:] This rollout will happen automatically by the specified date with no admin action required. You may want to notify your users about this change and update any relevant documentation as appropriate. We will update this post before rollout with revised documentation. |
| (Updated) Microsoft Teams: Stream Custom Agent and Bot ResponsesCategory:Microsoft TeamsNummer:MC918562Status:planForChange | Updated January 13, 2025: We have updated the rollout timeline below. Thank you for your patience Custom engine agents and Teams bots can now stream responses like Microsoft Copilot. They can provide real-time updates on their actions while delivering parts of the response as they generate it, making interactions feel faster and more engaging. This message is associated with Microsoft 365 Roadmap ID 422261 [When this will happen:] Targeted Release: We will begin rolling out mid-November 2024 and expect to complete by late November 2024. General Availability (Worldwide): We will begin rolling out mid-December 2024 and expect to complete by late January 2025 (previously late December) [How this will affect your organization:]
When users interact with a custom engine agent or Teams bot that streams its response, they will experience the new UX. Users will first see informative updates from the agent on what it is doing while it generates a response to the user’s message: Once the agent has performed prerequisite actions and is ready to respond, users will start to see the agent’s response flow in as incremental chunks until the full response is available. This experience is very similar to how the response iteratively appears on leading AI experiences like ChatGPT or Copilot: Users will have the option to stop generating the response if they feel the agent is headed down an ineffective path. Users can simply click on the stop button underneath the response, and this will stop the agent’s response. Users can then prompt the agent again: [What you need to do to prepare:] You may consider updating your training and documentation as appropriate. |
| (Updated) Microsoft Teams: Updated Auto Attendant helps callers reach the correct personCategory:Microsoft TeamsNummer:MC950895Status:planForChange | Updated January 13, 2025: We have updated the content. Thank you for your patience Coming soon for Microsoft Teams Phone: An updated Auto Attendant functionality that makes it easier for callers to reach the right person. Callers can select a callee by either pronouncing their name or entering it on the phone dial pad (dual tone multi-frequency or DTMF). This sometimes results in multiple similar matches returned by the search engine, which could create confusion for the caller. With this rollout, you can assist callers in reaching the correct person on the first try by including the Office or Department information after the name. Note: The Office and Department details will only be played if multiple similar matches are returned by the search results. For example: “For John Smith – Help Desk, press 1” “For John Smith – Sales, press 2” [When this will happen:] General Availability (Worldwide): Available since late November 2024. General Availability (GCC High, DoD): We began rolling out in late November 2024 and expect to complete by late January 2025. [How this will affect your organization:] To enable your Auto Attendant to include the Office or Department, please adjust the This update will be available by default for admins to configure. [What you need to do to prepare:] Learn more: Set up a Microsoft Teams Auto attendant – Microsoft Teams | Microsoft Learn This rollout will happen automatically by the specified date with no admin action required before the rollout. Review your current configuration to determine if it would be beneficial to enable this feature for your organization. You may want to notify your users about this change and update any relevant documentation. |
| 30-day reminder: Full Enforcement mode for Certificate-based authentication changes on Windows DCsCategory:WindowsNummer:MC959496Status:stayInformed | Starting in May 2022, certificate-based authentication on Windows domain controllers (DCs) started to go through a series of changes to enhance security, following a planned timeline of Enablement Phases. On September 10, 2024, we updated the timeline of security requirements for certificate-based authentication requests on Windows DCs. After you install the Windows security updates released in February 2025, authentication for certificates that do not meet the expected mapping requirements will be denied. This change is known as Full Enforcement mode. However, you can move back to Compatibility mode until September 2025. For full details, see KB5014754. When will this happen: In February 2025, or later, devices will move to Full Enforcement mode. How this will affect your organization: When you install the February 2025 Windows security update, devices that are not already in Full Enforcement mode (StrongCertificateBindingEnforcement registry value is set to 2), will be moved to Full Enforcement mode. If authentication is denied, you will see Event ID 39 (or Event ID 41 for Windows Server 2008 R2 SP1 and Windows Server 2008 SP2). You will have the option to set the registry key value back to 1 (Compatibility mode) at this stage. In the September 2025 Windows update, the StrongCertificateBindingEnforcement registry value will no longer be supported. What you need to do to prepare: Review the date changes in the “Take action”, “Full Enforcement mode”, and “Registry key information” sections of KB5014754. Take the appropriate action needed to make your devices more secure. Additional information: For full detailed information, see KB5014754: Certificate-based authentication changes on Windows domain controllers. |
| (Updated) Microsoft Teams: Enhanced confidentiality in voicemail greetingsCategory:Microsoft TeamsNummer:MC974356Status:stayInformed | Updated January 13, 2025: We have updated the content. Thank you for your patience Coming soon for Microsoft Teams: We have enhanced the privacy and security of voicemail system greetings for calls. [When this will happen:] General Availability (Worldwide, GCC, GCC High, DoD): Available since November 2024. [How this will affect your organization:] After this rollout, if a call recipient does not answer, the caller will be forwarded to the recipient’s voicemail. The system greeting will inform the caller that the user is unavailable and prompt the caller to leave a message after the tone. Also, the recipient’s real name will only be announced for internal calls. For external calls, the recipient’s name will be replaced with “the person.” Before this rollout, the recipient’s real name was announced to all callers. Note: a) Change applies to the system greeting only and custom greetings are not affected by the change. b) This change also applies to Microsoft Skype for Business. This change is on by default. [What you need to do to prepare:] No admin action required after the rollout. You may want to notify your users about this change and update any relevant documentation. |
