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

Updated October 24, 2024: The migration to app-centric management using the Migration Wizard (referenced as Phase 2 in this post) is expected to resume by mid-November 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.

• If your tenant has already been migrated to ACM, it will remain on ACM. The rest of this MC post is not applicable to your tenant.
• If your tenant fell under the Phase 1 criteria of using only the Global app permission policy and no custom app permission policies, it will resume auto migration in mid-September.
• If you do not have a draft currently saved, you will not be able to access ACM migration until the roll out restarts.
  

What is in Phase 2?

• Migration wizard: a step-by-step guide to help you migrate the permission policies. You will be able to select which polities to migrate and designate users groups or individuals who should have access to the apps.
• Testing and Validation: before finalizing the migration, you will have the opportunity to test and export your staged changes. You can use this to make side-by-side comparison with your current setup, ensuring everything is perfect before you proceed.
• Duration: The migration process is designed to have no downtime for the end users and can take a few hours to complete. During the migration, your existing permission policies will remain in effect until the transition to app centric management completes.

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) 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 early November 2024 (previously late September)) 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 (early 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 October 25, 2024: We have updated the rollout timeline and the phasing below. Thank you for your patience.

In 2023, we introduced Microsoft Teams apps that are compatible with Microsoft Outlook and the Microsoft 365 App (manifest version v1.13 or higher). Before this rollout, admin changes made in the Integrated apps section of the Microsoft 365 admin center would only affect these Teams apps in Outlook and the Microsoft 365 app. Similarly, changes made in the Teams admin center would exclusively affect Teams. Starting in June 2024, we will roll out Unified App Management to streamline the management of these apps across Teams, Outlook and the Microsoft 365 App, so they are consistently available across all supported clients.

This message is associated with Microsoft 365 Roadmap ID 393931.

[When this will happen:]

This rollout will happen in two major phases. Unified App Management can apply only to tenants that have migrated to app centric management in Teams admin center, as communicated in MC688930 (Updated) Teams admin center: App centric management and changes to app permission policies (November 2023).

• Phase 1 | General Availability (Worldwide): We will begin rolling out mid-December 2024 (previously July 2024) and expect to complete mid-January 2025 (previously late November 2024). This phase applies to tenants with no modified settings in either the Microsoft 365 admin center (Integrated apps) or the Teams admin center for organization-wide defaults, app deployment, app availability, or block/unblock. No merge rules apply to these tenants, but after this phase, any app management setting configured in either admin centers will apply to all relevant hosts.
• Phase 2: We will update this post with a timeline and more details. This phase is applicable to tenants with app settings that have differences between Microsoft 365 admin center (Integrated apps) and Teams admin center, and who have maintained a single app setup policy in Teams that has a modified Installed apps section.

[How this will affect your organization:]

Before this rollout, managing Teams apps that work in Outlook and the Microsoft 365 app was fragmented between the Integrated apps page in the Microsoft 365 admin center for Outlook and the Microsoft 365 app, and the Teams admin center for Teams. This sometimes resulted in different settings for the same app in the two admin centers. With Unified App Management, we will be consolidating app catalog management into a single platform. You will be able to manage apps on the Integrated apps page in the Microsoft 365 admin center or in the Teams admin center, and any changes made in either admin center will synchronize.

What you can expect

1. App catalog enhancements: Apps will start showing hosts where they are available: Teams, Outlook, or the Microsoft 365 app.
2. Organization-wide settings: App availability default settings will now apply to apps used in Teams, Outlook, and Microsoft 365 app.
3. App installs: Apps deployed from the Integrated apps page in Microsoft 365 admin center will be preinstalled in all applicable hosts for the app. Unlike app preinstallation in the Teams App setup policy, new app installs will provide access to the preinstalled apps, similar to deploying the app for Outlook and the Microsoft 365 App. [For more details on app deployment, refer to MC795355 Microsoft Teams admin center: App centric management for app installation and changes to app setup policies (May 2024)].
4. App availability: Managing app availability will apply to all applicable app hosts.
5. App block/unblock: Blocking or unblocking apps will apply to all applicable app hosts.
6. Consolidation of existing app settings: All existing app settings will be unified between Integrated apps (MAC) and Manage apps (TAC) pages. Merge rules can be found in Manage apps that work across Teams, Outlook, and Microsoft 365 | Microsoft Learn. These changes cannot be rolled back.
7. Consolidation report: Phase 2 and 3 tenant administrators will have access to an on-demand report prior to the merging of app settings. This report is designed to help administrators assess the impact of merge rules on their tenant and make any adjustments in advance. We will update this MC post when the report is available.

[What you need to do to prepare:]

We recommend that you review app and tenant settings in the Microsoft 365 admin center and the Teams admin center. If these are managed by different departments in your organization, we recommend conducting these reviews collaboratively.

We also recommend that you review the merge rules and consider their potential impact on apps in your organization. Make any necessary adjustments to unify them in advance, if the merge rules in this message do not align with your expectations.

This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to update any relevant documentation as appropriate.

Updated October 25, 2024: We recently discovered a significant issue that has resulted in the temporary disabling of this feature until it is resolved. We apologize for any inconvenience this may cause.

There is a new experience for selecting which users should have which permissions when a sensitivity label configured for user-defined permissions is applied to a file in Microsoft 365 apps or when a user applies protection using standalone Information Rights Management.

This message is associated with Microsoft 365 Roadmap ID 189826

[When this will happen:]

Preview (Worldwide, GCC): We will begin rolling out mid-July 2024 and expect to complete by late July 2024.

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

[How this will affect your organization:]

Users will see a modernized dialog when configuring user-defined permissions, whether these are applied using a sensitivity label configured for user-defined permissions or with standalone Information Rights Management. There are new names for some usage rights groupings for pre-set permissions levels compared to those in Microsoft Azure Information Protection (AIP):

• Reviewer is now called Restricted Editor.
• Co-Author is now called Editor.
• Co-Owner is now called Owner.

The rights contained in each grouping are unchanged.

See Configure usage rights for Azure Information Protection for further information on usage rights.

This new feature is available by default.

[What you need to do to prepare:]

If your organization has training materials or internal documentation regarding the use of pre-set permissions levels, you may need to make updates based on the new names for these permissions levels.

Updated October 25, 2024: Please review this message as the content for this release has been significantly updated. Thank you for your patience.

In Microsoft Clipchamp, the Brand kit feature enables users to create and share brand asset collections including colors, fonts and logos to use when creating videos. With this rollout, users with these subscriptions will have brand kit as a standard feature in Clipchamp:

•  Microsoft 365 E3 and E5
•  Microsoft 365 Business Premium and Business Standard
•  Microsoft 365 A3 and A5

This message is associated with Microsoft 365 Roadmap ID 398992.

This message applies to Clipchamp for Windows and for the web.

[When this will happen:]

Targeted Release: Feature rollout is complete.

General Availability (Worldwide): Brand kit is now a standard feature for all users.

[How this will affect your organization:]

You are receiving this message because users in your tenants have licenses which enable access to these capabilities. This update will not impact any other parts of your Microsoft 365 license or Microsoft 365 admin center.

Before this rollout: Users with the subscriptions in this message had no access to brand kit in Clipchamp and manually managed brand assets when creating videos.

After this rollout, your users can expect these changes in Clipchamp:

• Creation, sharing and manual usage of personal brand kits is available via all work and education accounts.
• Brand kit now supports elements beyond colors, fonts and logos including up to 300 each of: videos, music, sound effects, images, backgrounds, and stickers. All assets are stored on OneDrive or SharePoint.
• Organization “official” brand kits can be surfaced to all users opening Clipchamp across a tenant by placing the brand kit in Organization Asset Library (OAL).

What users will see

• In Clipchamp, brand kits can be created, used, or opened by anyone if the creator generates a link to share with them.
• User-created brand kits can be stored in OneDrive or SharePoint.
• Up to 300 of these brand elements can be stored with the brand kit: videos, sound effects, music, images, backgrounds, and stickers.

The default state of this feature is on and all users with the specified licenses can access it.

Clipchamp video editor with the Brand kit menu expanded to show example brand kits for Tailspin Toys and Microsoft. Select the Brand kit button from the left side of the screen:

[What you need to do to prepare:]

When this change takes effect, please make note of the new feature in Clipchamp for your administrative records and ensure that you update any relevant provisioning documentation, as needed.

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.

Learn more: How to use brand kit in Clipchamp – Microsoft Support

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

Coming soon: Microsoft Copilot for Microsoft 365 usage in your tenant will be added to the Microsoft Graph API to facilitate the creation of customized reporting and analytics. Metrics included in the Graph API will match those available in the Copilot for Microsoft 365 usage report in the Microsoft 365 admin center, including tenant-level count of enabled users and active users, as well as last activity date per user (totals for each Microsoft 365 app and a grand total). A Microsoft Copilot for Microsoft 365 license is required to use this feature.

This message is associated with Microsoft 365 Roadmap ID 396562 and with MC724835 Microsoft 365 admin center Usage report: Microsoft Copilot with Graph-grounded chat (Preview) (published March 2024).

[When this will happen:]

Public Preview: We will begin rolling out early September 2024 and expect to complete by mid-September 2024.

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

[How this will affect your organization:]

Before this rollout, the Graph API did not include Copilot for Microsoft 365 usage.

After this rollout, admins can use the Graph API to create customized reporting and analytics for Copilot for Microsoft 365 usage.

Sample request for one of the three APIs: getMicrosoft365CopilotUserCountSummary.

Sample response:

HTTP/1.1 200 OK

Content-Type: application/json

Content-Length: 537

{

"@odata.context": "https://graph.microsoft.com/beta/reports/getMicrosoft365CopilotUserCountSummary(period='D7')?$format=application/json",

"value": [

{

"reportRefreshDate": "2024-06-26",

"adoptionByProduct": [

{

"reportPeriod": 7,

"anyAppEnabledUsers": 354590,

"anyAppActiveUsers": 144022,

"microsoftTeamsEnabledUsers": 354449,

"microsoftTeamsActiveUsers": 88737,

"wordEnabledUsers": 354449,

"wordActiveUsers": 17493,

"powerPointEnabledUsers": 354449,

"powerPointActiveUsers": 7245,

"outlookEnabledUsers": 354449,

"outlookActiveUsers": 38140,

"excelEnabledUsers": 354449,

"excelActiveUsers": 2554,

"oneNoteEnabledUsers": 354449,

"oneNoteActiveUsers": 1382,

"loopEnabledUsers": 354449,

"loopActiveUsers": 955,

"copilotChatEnabledUsers": 354449,

"copilotChatActiveUsers": 64401

}

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

Before rollout, we will update this post with revised documentation.

To learn more about Microsoft’s own review of this product with its works councils, please consider reading: https://aka.ms/Copilot/MSWorksCouncilsArticle 

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

Users with Microsoft Word, Excel, and PowerPoint on Windows desktops and the web will soon have access to an updated version of the Office Add-ins Store in these applications. This store will continue to support users in exploring, installing, and managing Office Add-ins provided by Microsoft and third parties.

With this new feature, minor users will no longer be permanently blocked from getting Office Add-ins from the Office Add-ins Store.

Learn more:

• View, manage, and install add-ins for Excel, PowerPoint, and Word – Microsoft Support
• Understand how to configure the Age Group property in Microsoft Entra admin center

[When this will happen:]

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

General Availability (Worldwide): We will begin rolling out middle January 2025 and expect to complete by late January 2025.

[How this will affect your organization:]

Users will experience a new Office Add-ins Store in Word, Excel, and PowerPoint on both Windows desktops and on the web. Minor users not blocked by tenant administrators will be able to get Office Add-ins from the Office Add-ins Store.

This feature will be available by default.

[What you need to do to prepare:]

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.

For educational tenant administrators:

• If you wish to continue blocking minor students from getting Office Add-ins from the Office Add-ins Store, please ensure the user’s License Type is set to student, the Age group property is not set to Adult, and go to Microsoft admin center > Org settings > User owned apps and services to ensure the option Non-adult student is unchecked.
• For student users who you want to have access to the Office Add-ins Store, make sure their Age group property is set to Adult.

Educational tenant admins: The last step in Microsoft admin center to blocking minor students from getting Office Add-ins from the Office Add-ins Store:

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

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

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

A new csTeamsAIPolicy policy for Microsoft Teams (available now via Microsoft PowerShell and taking effect in mid-January 2025) will give IT admins more control over voice and face enrollment settings, allowing organizations to manage these features based on their needs. After rollout, voice and face profile enrollment will be enabled by default, and users can benefit from voice isolation, speaker recognition, and attribution in meeting rooms, resulting in smarter meeting recaps and enhanced functionality for Microsoft 365 Copilot in meetings. To access Copilot features, a Microsoft 365 Copilot license is required. This message applies to Teams for Windows desktop and Mac desktop.

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:]

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-January 2025 and is expected to be fully in effect by mid-January 2025.

[How this will affect your organization:]

Before this rollout, the current policy csTeamsMeetingPolicy has a single setting, EnrollUserOverride, that allows the administrator to enable or disable the enrollment of both face and voice profile of users.

After this rollout, the new csTeamsAIPolicy will replace the existing enrollment setting in csTeamsMeetingPolicy. The new csTeamsAIPolicy has two settings, EnrollFace and EnrollVoice, that will be set to Enabled by default.

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

• Set-CsTeamsAIPolicy (MicrosoftTeamsPowerShell) | Microsoft Learn
• Get-CsTeamsAIPolicy (MicrosoftTeamsPowerShell) | Microsoft Learn

Learn more: Overview of voice and face enrollment – Microsoft Teams | Microsoft Learn

Coming soon to Microsoft Viva Engage (Yammer): We will update the audit log schema to include parameters that uniquely identify both the user performing an action (actor) and the user/object affected by that action (target).

After this rollout:

• The actor will be identified by their unique Microsoft Entra ID ObjectId, stored in the UserKey field.
• The target will be identified by a new parameter TargetObjectId that will also store the target’s Entra ID ObjectId.
• To improve transparency on changes to admin roles and other key scenarios, a new ModifiedProperties parameter will capture both the old and new values of modified fields.

These new parameters will be available for users with an E3 license.

[When this will happen:]

General Availability (Worldwide): We will begin rolling out end-November 2024 and expected to complete by late December 2024.

[How this will affect your organization:]

After this rollout, for admins querying audit logs in the Microsoft Purview compliance portal (Microsoft Purview compliance portal > System > Audit), the UserKey will represent the Entra ID ObjectId of the actor. If you are using Microsoft PowerShell commands or custom scripts, please ensure that you are retrieving the correct value for UserKey to identify the actor. Also, ensure any scripts that need to identify the target are using TargetObjectId.

Before the rollout, UserKey was populated with the target user’s Passport ID, so existing queries using this parameter may need to be updated. No Entra ID ObjectId was available to uniquely identify users (actor and target).

After the rollout: The UserKey will be mapped to the Entra ID ObjectId of the user performing the action. The new TargetObjectId parameter will capture the Entra ID ObjectId of the user affected by the action, and the ModifiedProperties field will hold the old and new values for any modified fields.

Field changes

As we apply these changes to the Viva Engage (Yammer) workload audit logs, the UserKey field will be updated immediately to reflect the Entra ID ObjectId of the actor in all audit logs. The new fields TargetObjectId and ModifiedProperties will only be populated for admin-specific audit logs and events. These include actions such as promoting or demoting users to Corporate Communicator, Network Admin, Verified Admin, Yammer Admin roles, as well as enabling or disabling Leadership Corner and setting or updating custom usage policies.

This change will be on for admins who have already enabled it. For everyone else, this change will be off by default and available for admins to configure.

[What you need to do to prepare:]

To ensure a smooth transition, we recommend notifying your users about this update and updating any relevant documentation to incorporate 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.

Learn more: Search the audit log | Microsoft Learn

Track Viva Engage events in the Microsoft 365 audit log and with the Management Activity API | Microsoft Learn

Microsoft Purview | Insider Risk Management indicators that detect activity in cloud storage apps (Box, Dropbox, Google Drive), cloud services (AWS, Azure), and Microsoft Fabric (Power BI) will transition from a free Public Preview [as communicated in MC716005 (Updated) Microsoft Purview | Insider Risk Management: Public preview of multicloud support (updated March 2024)] to a pay-as-you-go pricing model in Public Preview. [When this will happen:]

Public Preview: We will begin rolling out in early November 2024 and expect to complete by early November 2024.

We will update this message when we know the plan for General Availability.

[How this will affect your organization:]

To continue using indicators for cloud storage apps (Box, Dropbox, Google Drive), cloud services (AWS, Azure), and Microsoft Fabric (Power BI), please link an Azure subscription to Microsoft Purview to enable billing. Starting November 1, 2024, you will be billed based on the number of user activities processed by Microsoft Insider Risk Management for these indicators.

Insider Risk Management indicators transitioning to a pay-as-you-go pricing model:

[What you need to do to prepare:]

Microsoft Purview admins with appropriate permissions can enable the pay-as-you-go features from Microsoft Purview by taking a few steps. To learn more: Enable Microsoft Purview PAY-AS-YOU-GO features.

Insider risk admins with appropriate permissions can opt in to these indicators in the new Microsoft Purview portal at Insider Risk Management settings.

Microsoft Purview Insider Risk Management correlates various signals to identify potential malicious or inadvertent insider risks, such as IP theft, data leakage, and security violations. Insider Risk Management enables customers to create policies based on their own internal policies, governance, and organizational requirements. Built with privacy by design, users are pseudonymized by default, and role-based access controls and audit logs are in place to help ensure user-level privacy.

Learn more: Learn about Microsoft Purview billing models | Microsoft Learn

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

Coming soon to Microsoft Outlook and Microsoft Teams: A name pronunciation feature on the profile card in Microsoft Teams and Microsoft Outlook. This new feature helps promote diversity by giving working colleagues relevant information about each other. Names are a crucial part of a person’s identity. The incorrect pronunciation of a person’s name can lead to anxiety and offense in some cases. Correctly pronouncing a person’s name helps to create an inclusive environment.

This message is associated with Microsoft 365 Roadmap ID 420329.

Pronunciation data is stored in each user’s mailbox until the user deletes the recording. Learn more: Data Residency for Exchange Online – Microsoft 365 Enterprise | Microsoft Learn

This message applies to Teams for Windows desktop, Teams for Mac desktop, new Outlook for Windows desktop, and new Outlook for web.

[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, GCC, GCC High, DoD): We will begin rolling out mid-January 2025 and expect to complete by mid-February 2025.

[How this will affect your organization:]

After this rollout, users can record and share the correct pronunciation of their name on their profile card. With a click, users can play and listen to name pronunciations recorded by their colleagues.

To open a profile card in Outlook, double-click a name in the To or From field in any sent or received email.

To open your profile card in Teams, select your profile photo in the upper right corner of the screen, and then select your name.

To listen to a colleague’s recorded pronunciation, select the speaker icon on their profile card:

To record the pronunciation of a name, open your profile card in Outlook or Teams, and select the microphone icon:

[What you need to do to prepare:]

This feature is off by default. As an admin, you can enable the feature in Microsoft Graph using these instructions: namePronunciationSettings resource type – Microsoft Graph beta | Microsoft Learn

Before rollout, we will update this post with revised documentation.

You may want to notify your users about this change and update any relevant documentation.

#newoutlookforwindows

Coming soon in Microsoft Viva Engage Communities: Community settings for the Community Resources module and the Files tab.

[When this will happen:]

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

[How this will affect your organization:]

After this rollout, community admins will have the ability to enable or disable the Community Resources module and the Files tab in community settings. Two new toggles on the Settings page will allow admins to control the visibility of these features.

By default, both the module and the tab are turned on, making them visible to members. Admins can easily hide them by switching off the corresponding toggles. These changes can be made at any time without affecting existing data, giving admins more flexibility to tailor the community experience based on the relevance of these features.

Before this rollout: The settings did not exist, so community admins did not have the ability to hide or unhide Community Resources and the Files tab in Viva Engage Communities.

The new toggles are off by default.

To access the Community settings page, go to a community page and select Settings from the three-dot menu in the top right:

The Community settings page will have two new toggles to hide/unhide the Community Resources module and the Files tab:

[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 a community in Viva Engage – Microsoft Support (will be updated before rollout)