Skip to main content

Bulk Extended — channels, SharePoint sites, the new metadata flow and more enhancements

Run bulk actions on channels and standalone SharePoint sites, see members and owners per team or channel with new filters, and use the redesigned metadata flow with unassign and change-value actions.

Written by Rob

Admins running governance at scale need bulk operations to cover the full surface of Microsoft 365 collaboration — not only Teams. Bulk Extended brings channels and standalone SharePoint sites into the bulk surface as first-class entities, expands file version cleanup to channel-associated sites, redesigns the bulk metadata flow, and now exposes per-team members and owners directly in the bulk view with new membership-based filters.

Prerequisites

  • You must have the Teams Service Admin, Catalog Manager, or Global Admin role.

  • The service account needs SharePoint admin scope for bulk operations on standalone SharePoint sites.

Bulk actions on standalone SharePoint sites

SharePoint sites that exist outside of a Microsoft Teams workspace — project sites, intranets, department hubs, document repositories — are now selectable from the bulk operations page alongside teams. The following actions apply:

  • Send notification to site owners

  • Archive a site

  • Delete a site (with confirmation)

  • Restore an archived site

  • Attach governance template

  • File version cleanup

To run a bulk action on SharePoint sites:

  1. Go to Bulk Operations and switch to the SharePoint tab.

  2. Search and filter sites by name, owner, last activity, or template.

  3. Select the sites you want to act on.

  4. Pick an action from the Actions menu.

  5. Review the confirmation screen and click Run.

Bulk actions on channels

Channels are now a first-class target for bulk operations, alongside teams and standalone SharePoint sites. Select multiple channels — across one or many teams — and apply governance actions in a single pass, with no need to walk into each team to act channel by channel.

The following actions apply to channels:

  • Archive Channel — archive selected channels

  • Unarchive Channel — restore archived channels

  • Delete Channel — permanently delete selected channels

  • Add/Remove members — add or remove members from selected channels

  • Attach to Template — attach selected channels to a channel template

  • Assign metadata — apply a metadata value to selected channels

  • Unassign metadata — remove a metadata value from selected channels

  • Delete File Versions (Beta) — clean up old file versions on the SharePoint sites backing selected channels

  • Export channels — export the channel list with all columns to an Excel file

To run a bulk action on channels:

  1. Go to Bulk Operations and switch to the Channels tab.

  2. Search and filter channels by name, description, template, type, parent team, owners, or members.

  3. Select the channels you want to act on. Use All to select every result in the current filter.

  4. Pick an action from the Actions menu.

  5. Review the confirmation screen and click Run.

Members and owners visibility

In both the Teams and Channels views, you can now see each row's members and owners directly in the list — no need to open each team or channel individually to confirm who is impacted by a bulk action.

File version cleanup — now covers channel sites

The file version cleanup bulk action now discovers and cleans the SharePoint sites behind a team's private and shared channels — not only the primary site. The confirmation screen lists every site that will be affected with per-site version counts and estimated space savings.

Bulk metadata — redesigned flow with new actions

The bulk metadata flow has been redesigned to separate operational assignment from schema setup, and now supports two new actions in addition to the existing assign:

  • Assign value — apply a metadata value to selected teams or channels

  • Unassign value — remove a metadata value from selected teams or channels

  • Change value — replace a value with another in a single pass; current values per team are surfaced for context

Confirmation screens now show values in human-readable business language rather than raw schema field keys. Category creation has moved to the admin area where the schema is owned, keeping operational bulk runs focused.


Related Articles

Did this answer your question?