Microsoft Roadmap, messagecenter en blogs updates van 18-10-2024

Updated October 16, 2024: We have updated the rollout timeline below. Thank you for your patience.

Scheduling, setting up, and managing an event is not a simple task. Which is why we allow co-organizer to be added to the event so they can work alongside or on behalf of the organizer. So far co-organizers were able to set up event theming, manage registration, meeting options, view reports and more but were not able to edit event details like title, date/time, description, event group; nor publish or cancel event. Now they can! Co-organizer can edit event details, publish, and cancel the event like the organizer can. So once the co-organizer is added they will have full parity of experience as organizer and control/manage/edit event. 

This message is associated with Microsoft 365 Roadmap ID 168524

[When this will happen:]

Targeted release: We will begin rolling out early January 2025 (previously early December) and expect to complete by mid-January 2024 (previously mid-December).

General Availability (Worldwide, GCC): We will begin rolling out mid-January 2025 (previously mid-December) and expect to complete by mid-January 2025 (previously early January).

[How this will affect your organization:]

When co-organizer opens the event scheduling page, they should have the ability to edit the details page, publish, and cancel the event. 

[What you need to do to prepare:]

Nothing required to prepare.

Updated October 17, 2024: We have updated the rollout timelines below. Thank you for your patience.

Microsoft Teams users will soon be able to control how they get notified in meeting chats through RSVP to their meetings. When they decline a meeting, they will not receive notifications or see the chats in chat list; when they accept a meeting, they will receive notification for all new messages. This release of Microsoft Teams Meeting ID will be rolling out across Microsoft Teams Desktop, Mobile and Web and will provide an additional way for users to control their chat list by selecting which meetings they want to receive message updates from.

This message is associated with Microsoft 365 Roadmap ID 161739

[When this will happen:]

Targeted Release will begin rolling out early December 2024 (previously early November) and expect to complete by mid-December 2024 (previously mid-November). 

Worldwide will begin rolling out early January 2025 (previously early December) and expect to complete by mid-January 2025 (previously mid-December). 

GCC will begin rolling out January 2025 (previously early November) and expect to complete by mid-January 2025 (previously mid-November). 

GCC High will begin rolling out mid-January 2025 (previously mid-November) and expect to complete by late January 2025 (previously late November). 

DoD will begin rolling out late January 2025 (previously early October) and expect to complete by early February 2025 (previously mid-October). 

[How this will affect your organization:]

You will not receive notifications or see chats from meetings you declined. You will be able to set how you want to be notified for meetings you RSVP with Accept or Tentative from Microsoft Teams settings.

[What you need to do to prepare:]

You might want to notify your users about this new capability to control meeting chat notifications by RSVP to meetings. 

Updated October 17, 2024: We have updated the list of countries below to include all EU countries. Thank you for your patience.

Microsoft SharePoint eSignature allows users to easily request eSignatures on a PDF document via SharePoint online. Signers can easily add their electronic signature. Signed documents are saved securely back to SharePoint.

As communicated in MC690925 (Updated) SharePoint eSignature electronic signature service (November 2023), SharePoint eSignature is currently available in the United States. With this rollout, eSignature is coming soon to the United Kingdom, Canada, and these European countries:

• Austria
• Belgium
• Bulgaria
• Croatia
• Cyprus
• Czech Republic
• Denmark
• Estonia
• Finland
•  France
•  Germany
•  Greece
•  Hungary
•  Ireland
•  Italy
•  Latvia
•  Lithuania
•  Luxembourg
•  Malta
• Netherlands
• Poland
• Portugal
• Romania
• Slovakia
• Slovenia
• Spain
• Sweden

[When this will happen:]

We will begin rolling out to the UK, Canada in August 2024, and the European countries in this message in early November 2024 (previously early October). 

[How this will affect your organization:]

Before this rollout: Users only had third-party (non-Microsoft) plugin options for eSignatures in SharePoint.

After the rollout: If your region is now supported, you will be able to configure and use SharePoint eSignature in SharePoint.

If you have SharePoint Premium configured before this rollout, you will need to turn on this feature.

If you sign up for SharePoint Premium after the rollout, the feature will be on by default, but you can turn it off.

[What you need to do to prepare:]

References

• Set up SharePoint eSignature | Microsoft Learn
• SharePoint eSignature – Microsoft Adoption (adoption-dev.azurewebsites.net)
• Overview of SharePoint eSignature | Microsoft Learn

Updated October 16, 2024: Updated information related to Office 365 Connectors Retirement in Teams – Webhook URL Migration. Thank you for your patience.

 As shared in the last communication, we are publishing guidance for owners of webhook-based connectors to update their URLs with a new structure. To allow ample time for replacing URLs, connector owners will have until January 31, 2025, which is an extension from our previous deadline of December 31, 2024. See below for complete guidance.

Webhook-based connectors within the O365 Connectors service in Teams are transitioning to a new URL structure due to the implementation of further service hardening updates. During this transition, you may receive notifications to update your configured connector to use the new URL. We strongly recommend that you update your connector immediately to prevent any disruption to connector services. URLs for all webhook-based connectors must be updated by January 31, 2025 for the connectors to continue posting messages into Teams. Keep in mind the entire O365 Connectors service in Teams will be retired at the end of 2025, so consider moving your webhooks to the Workflows app within Teams to avoid conducting another migration. Documentation: Create incoming webhooks with Workflows for Microsoft Teams – Microsoft Support

[How this will affect your organization:]

This change is needed only for webhook-based Connectors such as Incoming Webhook and third-party connectors where a URL is provided for posting messages. The change is not required for polling-based connectors such as RSS.

To update webhook URLs for existing O365 Connectors, follow these steps: Manage Microsoft 365 connectors and custom connectors – Microsoft Teams | Microsoft Learn

1. Go to Manage Channel in a Teams channel, select Edit under the Connectors option, and select Configured section. Review the existing connections listed on this page.

2.Do one of the following to generate a new URL:

• For connectors that contain a webhook URL, select Manage and Update URL.
• For other types of connectors, remove the connector and recreate the connector configuration.

3. Replace the old URL with the new URL (or the new connection in the service that triggers the post). You’ll know the new URL is ready for you to copy when the Configure page shows a message that the URL is updated (“Url is up-to-date”).

[What you need to do to prepare:]

The below dates are still unchanged and were communicated in previous updates:

• Entire O365 Connector service in Teams will retire in December 2025.
• Developers will no longer be able to create new Office 365 Connectors from the Developer Portal starting August 15th, 2024.

Additional documentation:

Create incoming webhooks with Workflows for Microsoft Teams – Microsoft Support

Browse and add workflows in Microsoft Teams – Microsoft Support

Note about parity features for the Workflows app

We are currently developing a method for webhooks in the Workflow app to support the following scenarios and will share more details before March 30, 2025.

• Post messageCard formatted message payloads (so you do not have to reformat the payload to adaptive card)
• Post to private channels

Updated October 16, 2024: We have updated the rollout timeline below. Thank you for your patience.

If you use the deployment configuration service from the Microsoft 365 Apps Admin Center (config.office.com) to create deployment configurations for Microsoft 365 apps, get ready for a change. The ability to access these deployment configurations via a direct URL will be retired.

[When this will happen:]

We will begin rolling out this change in late September 2024 and expect to complete by mid-November 2024 (previously early October).

[How this will affect your organization:]

You are receiving this message because our reporting indicates your organization may be using the deployment configuration service to create and store deployment configurations for Microsoft 365 apps.

Administrators will no longer be able to access their deployment configurations via a direct URL. The deployment configurations can still be created, edited and downloaded.

[What you need to do to prepare:]

Admins that use direct URLs with the Office Deployment Tool (ODT) will need to download the deployment configurations in order to use them with the Office Deployment Tool (ODT).

Overview of the Office Customization Tool

Updated October 16, 2024:  We have updated the rollout timeline below. Thank you for your patience.

Coming soon to Microsoft Outlook: Work hours and location information will be available in the My Day pane in Outlook. Users will be able to update their Work Hours and Location information from My Day and also see who is coming to Office. This message applies to new Outlook for Windows desktop and Outlook for the web.

This message is associated with Microsoft 365 Roadmap ID 412618.

[When this will happen:]

Targeted Release: We will begin rolling out mid-November 2024 (previously early October) and expect to complete by mid-December 2024 (previously early November).

General Availability (Worldwide): We will begin rolling out mid-December 2024 (previously early October) and expect to complete by early January 2025 (previously early December).

[How this will affect your organization:]

Before this rollout, users can review and update their work hours and location information in Outlook Settings > Calendar > Work hours and location. This settings page will remain in place after the rollout.

After this rollout, users will also be able to see and update their work hours and location information in the My Day pane in Outlook. Changes to the My Day pane will sync to any other work hours and location settings made in Outlook.

My Day pane with prompt to Set up your work location:

My Day pane with work location information, which can be updated:

This feature is 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. You may want to notify your users about this change and update any relevant documentation.

Updated October 17, 2024: We have updated the rollout timeline below. Thank you for your patience.

Coming soon: We will automatically import the folder order from classic Microsoft Outlook for Windows to new Microsoft Outlook for Windows and Outlook for the web. If users have not customized their folder order, the default view will continue to display folders alphabetically in the new Outlook.

This message is associated with Microsoft 365 Roadmap ID 378775.

[When this will happen:]

Targeted Release: We will begin rolling out late November 2024 (previously early October) and expect to complete by late December 2024 (previously early November).

General Availability (Worldwide): We will begin rolling out January 2025 (previously early November) and expect to complete by early February 2025 (previously early December).

General Availability (GCC, GCC High, DoD): We will begin rolling out early February 2025 (previously early December) and expect to complete by early March 2025 (previously early January).

[How this will affect your organization:]

Before this rollout: If a user enabled custom folder order in classic Outlook, the custom order is preserved in the new Outlook for Windows and Outlook on the web. This may result in changes to the folder structure for affected users, as the new Outlook supports only alphabetical ordering.

After this rollout: users will see the custom folder order they previously enabled in classic Outlook. Special folders such as Inbox, Drafts, Sent Items, and others will still remain at the top of the folder list, even when the rest of the folders are arranged alphabetically.

This change is on by default.

To change folder order, go to the new Outlook ribbon, and select View > Layout > Folder pane. Choose one of these options:

• Order folders A to Z order: This will organize folders alphabetically
• Custom order

Users can hover next to each folder name to see the three-dot menu where they can move folders with drag-and-drop or the move up/move down options:

[What you need to do to prepare:]

This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to notify your users about this change and update any relevant documentation.

Learn more: Change the order of folders in the Folder Pane – Microsoft Support (will be updated before rollout)

Updated October 16, 2024: We have updated the content. Thank you for your patience.

In Exchange Online PowerShell (EXO) V3.0, we introduced the Connect-ExchangeOnline cmdlet to connect to the Microsoft Exchange Online environment through Microsoft PowerShell, which loads the help file by default. This help file is required for running the Get-Help cmdlet. However, not many customers used the Get-Help cmdlet. In EXO V3.3, we added the -SkipLoadingCmdletHelp parameter. When -SkipLoadingCmdletHelp is used with Connect-ExchangeOnline, help files do not load the on the customer system, which saves resources.

However, starting with EXO V3.7, we are changing this default behavior. The Help file will not be loaded by default, and a new parameter -LoadCmdletHelp will be required to load the cmdlet help and use the Get-Help cmdlet. To avoid breaking existing scripts, the -SkipLoadingCmdletHelp parameter will continue exist, but will not function.

[When this will happen:]

General Availability (Worldwide): The changes will be available in EXO V3.7 (the next release of our EXO V3 module) in early November 2024.

[How this will affect your organization:]

Starting with EXO V3.7, if you want to use the Get-Help cmdlet, you will have to use the parameter -LoadCmdletHelp along with Connect-ExchangeOnline.

[What you need to do to prepare:]

This message only applies to customers who upgrade their EXO module version to 3.7.0. Earlier versions will not be affected by these changes.

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.

Learn more

• Connect-ExchangeOnline (ExchangePowerShell) | Microsoft Learn (will be updated before rollout)
• Get-Help (Microsoft.PowerShell.Core) – PowerShell | Microsoft Learn
• Download an EXO module from PowerShell Gallery | ExchangeOnlineManagement 3.6.0.

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 December 2024.

[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

Starting in early November 2024, Microsoft Copilot in Edge will once again support page summarization, which lets users summarize an open webpage or PDF in the Edge sidebar. Page summarization will also include contextual prompt suggestions to help users ask relevant questions about open pages in Edge. Page summarization will be available for Microsoft Copilot users when signed in with a Microsoft Entra account and for Microsoft 365 Copilot users when using web mode. Learn more about the difference between Microsoft Copilot and Microsoft 365 Copilot. Page summarization and contextual prompt suggestions will be accessible for users when using Copilot through the Edge side pane.

[When this will happen:]

General Availability (Worldwide): We will begin rolling out early November 2024 and expect to complete by mid-November 2024.

[How this will affect your organization:]

Page summarization has been unavailable since the updates to Microsoft Copilot in mid-September 2024 but will roll out again in early November 2024. 

After this rollout, Copilot may have access to a user’s page context when they are sending contextual prompts to Copilot in Edge or if they are using Copilot in Edge alongside an open webpage or PDF.

The page summarization feature will be available by default when it rolls out in early November. It can also be configured by admins.

[What you need to do to prepare:]

The EdgeEntraCopilotPageContext policy is available now for you to manage whether your users have access to page context while using Copilot in Edge. The policy will take effect after page summarization is available. If the policy is not configured, users can enable or disable Copilot’s access to page context in their Copilot settings.

The Copilot feature in the Edge side pane:

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 users about this change and update any relevant documentation.

Learn more

• The section called What’s the difference between Microsoft Copilot and Microsoft 365 Copilot? in Overview of Copilot | Microsoft Learn
• Enterprise data protection in Microsoft 365 Copilot and Microsoft Copilot | Microsoft Learn

After this rollout, in a town hall or webinar, the organizer can download the transcript after the event has ended. Also, if an organizer has indicated through the meeting options before the event that an RTMP-In feed will be used, the 708 captions will be displayed in both the attendee captions and transcripts.

The transcript can be downloaded in Teams for Windows and Mac desktops and Teams for the web. The 708 captions during the meeting will be displayed in Teams for Windows and Mac desktops, Teams for the web, and Teams for Android and iOS.

This message is associated with Microsoft 365 Roadmap ID 417156.

[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, GCC): We will begin rolling out mid-November 2024 and expect to complete by late November 2024.

[How this will affect your organization:]

To indicate before the event has started if an encoder or RTMP-In feed will be used, go to the event in the Teams calendar > Select Manage event > Select Meeting options > Enable RTMP-In

To download transcripts after the town hall or webinar, go to the event in the Teams calendar > Select Manage event > Select Recordings > Select Download transcripts

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.

Learn more

• Manage town hall recordings in Microsoft Teams – Microsoft Support (will be updated before rollout)
• Use RTMP-In in Microsoft Teams (will be updated before rollout)

We are launching Microsoft 365 Copilot in Microsoft Viva Amplify to enhance your authoring experience with AI. Copilot is available in the Campaign Brief authoring canvas and the Publication authoring canvas in Viva Amplify.

A Microsoft 365 Copilot license is not required to use this new feature. If a customer has a Viva Amplify license through Microsoft Viva Suite, Microsoft Viva Communications and Communities, or another Viva license, the user can use Copilot in Viva Amplify. NOTE: A customer that has a Viva Amplify license but does not have a Microsoft 365 Copilot license will not have access to Copilot on Microsoft SharePoint pages.

This message is associated with Microsoft 365 Roadmap ID 411300.

[When this will happen:]

General Availability (Worldwide): Available now.

[How this will affect your organization:]

With our Copilot editor experience, by selecting the rewrite capability, Copilot will suggest different ways to rewrite your content, providing options that vary in style, structure, and emphasis.

Adjust length: Copilot allows you to shorten or expand your content based on your needs. You can tailor your text to meet word counts without compromising quality.

Tone: Copilot helps you shift the tone of your writing. Viva Amplify Copilot rich text editor (RTE) supports the following tones:

• Casual
• Professional
• Enthusiastic
• Engaging
• Creative

This feature is available by default for all Viva Amplify users in the web/desktop experience. Please note that Amplify on Mobile iOS and Android applications is currently out of scope.

Disabling Copilot only exists at the tenant level. Note: A new setting in the Microsoft admin center to better manage Copilot at the tenant level will be available as part of a future release.

[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.

As an extension to the previous communication MC757613 (Updated) Microsoft SharePoint: Add approvals to any SharePoint list (originally sent March 2024, updated August 2024), we will soon add approvals to document libraries in Microsoft SharePoint Online.

This message is associated with Microsoft 365 Roadmap ID 420336.

[When this will happen:]

Targeted Release: We will begin rolling out early November 2024 and expect to complete by late November 2024.

General Availability (Worldwide, GCC): We will begin rolling out early December 2024 and expect to complete by late January 2024.

[How this will affect your organization:]

Before this rollout: Users are not able to add approvals to document libraries in SharePoint Online.

After this rollout, users will be able to configure approvals by going to the Automate dropdown menu from the command bar in SharePoint Online document libraries and then selecting the Configure Approvals option to enable and disable approvals on the library. Note: When editing files, any in-flight approvals will be cancelled if changes are saved. To discourage edits of in-progress approvals, files will open in view-only mode in Microsoft Word, Excel, and PowerPoint for the web, and the same Windows desktop applications will show that the document is Marked as final.

After approvals are enabled, a user can create a file and submit it for approval. By creating an approval request and specifying the approver, the request will appear in the Approvals app in Microsoft Teams or can be approved directly in the library in SharePoint. Once approved, the file metadata is updated.

Note: Disabling approvals will only hide the relevant columns. In-progress approvals will still be actionable in Teams. At any time, you can manually add approvals columns back into your views.

Configure approvals in SharePoint Online:

Enable configured approvals:

Approvals column:

Disable configured approvals:

This feature is 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.

Inform your users of the new Approvals functionality for libraries and lists. Share the support documentation Approvals in lists, which will be updated before this rollout begins to include library support.

• Use service admin roles to manage your tenant
• Microsoft Entra built-in roles