What’s new

The automation builder loads faster and responds quicker, also when you work on complex automation templates.

Request forms in the Rencore app in Microsoft Teams show selected sensitivity labels as pills with tooltips.

The company guidelines editor gains a Clear format button that removes unwanted formatting from selected text.

The permission for the Teams App settings is now called Manage Teams App settings, so admins find it next to the page it controls.

Provisioning actions and the form values trigger are now hidden in the automation builder. Workspace requests run through provisioning templates and appear in the Rencore app in Microsoft Teams.

SharePoint and OneDrive each scan in two jobs, one for sites or OneDrive accounts and one for files, folders, and file shares. Large environments scan faster and are easier to manage.

The new file scans use an added full control permission for OneDrive, which is part of the updated consent.

Teams tabs and other shared objects now belong to their parent object in the inventory, with consistent names. Relations between objects are easier to read and manage.

Policies listed in dashboard tiles now link straight to their policy details page.

The automation details page offers Stop automation for active runs and Rerun automation for completed ones.

Every workspace now runs its scan jobs in parallel by default. Scans finish sooner, and you see results faster.

Policy-based automations start only when a scan updates the objects behind the policy, primary or related, so each run follows a real change.

Dashboard tiles load faster, both when you view a dashboard and when you edit it.

Manually triggered automations start processing right away.

Automations with the On policy violation trigger run again when a resolved object violates the policy a second time.

Scheduled automations run on their set days, independent of scans and of whether objects changed. Each new run starts once the previous one is done.

The provisioning template builder drops the consent section, leaving only the settings template authors need.

Inventory opens on a landing page with every inventory by service, with filters to find specific assets. Details pages map each object’s relationships as a graph and a table, and sidebars show properties without leaving the page.

Policies open on a landing page that groups them by service or category and shows their compliance status. Trend charts on the policy overview cover ranges from 30 days to two years.

Policies and reports show a plain summary of their rules, so you can read the configuration without opening the builder. Out-of-the-box policies add expert recommendations on why they matter and how to resolve violations.

The workspace setup wizard offers modules, and picking a module selects the services that belong to it.

The Approvals page in the Rencore app now sorts requests by their Requested date as soon as it opens.

The Shared channels segment in the Teams inventory is available in every environment, including environments created before it launched.

The Last data update column on the Policies overview shows the latest policy refresh, including refreshes that found no data changes.

Content linked to a recently switched-off service shows a notice during its retention period. You can spot a service that was turned off by mistake.

When a SharePoint site, subsite, or library is deleted, its files and folders leave the inventory with the next full or incremental scan.

Changes from approved access reviews take effect within 60 minutes of submission. Owners and members you remove lose access sooner.

The Remove user automation action names what blocks a removal, such as security group memberships or assigned roles.

SharePoint and OneDrive sharing links are related to the file or folder they share. Reports and policies can follow that relation from a link to its content.

Power Platform scans hold their elevated admin permissions for the full run, for consistent inventory data.

The report template library shows the templates for the services you have enabled.

Action names in the automation builder sidebar wrap onto several lines, so they stay readable on smaller screens.

Dashboard imports run more of their work in the background, which supports complex dashboards in large workspaces.

Automations spend less time filling in placeholders, so runs finish sooner. The Remove document sharing action also skips an unneeded check.

SharePoint scans handle request throttling inside batch requests.

Groups you delete drop out of policy results with the next incremental scan, and the inventory reflects the change.

Direct user access and group access to SharePoint site collections are available as related objects. Use them in policies and reports to see who has access to a site.

The placeholder picker in the automation builder is wider, so you can read full placeholder names and rely less on tooltips.

The references table in the technical documentation lists the automation placeholder name for each object. Finding the right placeholder for a custom automation takes less guesswork.

The template details sidebar on the Request workspace page gives more space to company guidelines and workspace properties.

When you trigger an automation by hand, toast messages confirm the start and the result. Each message links to the run details.

When a requested community name is already taken, provisioning adds “(1)” to the name and creates the community.