Export Viva Engage admin settings from Engage Admin Center [MC1218450]

Message ID: MC1218450

[Introduction]

We’re introducing a new admin settings export in Viva Engage, helping organizations meet regulatory requirements by making key admin configuration data easily accessible and portable. Additionally, the network data export file has also been updated to include visibility into users placed in view-only mode in Engage and corporate communicators assigned the advanced moderation permission.

[When this will happen:]

General Availability (Worldwide): We will begin rolling out late January 2026 and expect to complete by mid-February 2026.

[How this affects your organization:]

Who is affected:

Global Admins, Engage Admins, and Verified Admins.

What’s new:

• Admins can now export a snapshot of Viva Engage admin settings directly from the Engage Admin Center.
• The export provides a point-in-time, human-readable (.csv) file capturing current configuration of all in-scope admin settings.
• The network data export file now includes visibility into users placed in view-only mode and corporate communicators assigned the advanced moderation permission.

How it works:

• Where to find it: Engage Admin Center → Governance & Compliance → Data Management
• Export format: CSV containing setting names and their current configured values

What’s included

• Tenant- and network-level admin configuration settings based on tenant licensing for Engage Admins, Verified Admins, Network Admins, and Corporate Communicators.

What’s not included

• Community-level or Microsoft 365 Group–specific settings
• Engage settings managed in the Teams Admin Center or Microsoft 365 Admin Center

Who can access the export

• Global Administrator
• Engage Administrator
• Verified Administrator

[What you can do to prepare:]

• Engage admins, Global admins, and Verified admins can pull an export of admin settings when the feature becomes available.
• No additional preparation is required.

Learn more: Export and manage Viva Engage data (will be updated before rollout)

[Compliance considerations:]

No compliance considerations identified, review as appropriate for your organization.

Source: Microsoft

Latest Posts