What's new

Updated guidelines for configuring automatic provisioning for the enterprise WorkZone application

For instructions on how to provision the group description from Entra ID to WorkZone, see 4. Configure automatic provisioning for the enterprise application.

Oauth2 authentication no longer supported

As per this release, Oauth2 authentication is no longer in active support, and the recommended authentication method is Entra ID. See Access control using Microsoft Entra Conditional Access.

Updated guidelines for configuring automatic provisioning for the enterprise WorkZone application

For instructions on how to provision the group description from Entra ID to WorkZone, see 4. Configure automatic provisioning for the enterprise application.

New WorkZone for Office registry key for handling redirection templates

A new HideRedirectionTemplate registry key is available for WorkZone for Office Windows Registry. It defines how WorkZone for Office will handle the redirection templates when new documents are created from WorkZone Client.

See Registry keys.

ServerScan Directory Watcher Service

The new KMDServerScan Directory Watcher Service is a Windows service that uploads scanned documents and their metadata to cases in WorkZone.

See Install and configure ServerScan Directory Watcher Service.

New behavior of guest user naming

When you create a guest user based on an e-mail address that is not of your organization's primary domain, the generated user name of the guest user will be suffixed with a running number. This behavior is introduced to ensure that all users have unique user names. It is generally recommended that you name your internal users uniquely, also across subdomains. Read more and see an example in Add guest users.

Updated configuration guidelines for registering the WorkZone app in Azure

For instructions on how to register WorkZone app in Azure, see Register WorkZone apps in Azure and Create a WorkZone Enterprise application.

If you plan to use WorkZone 365 with Exchange Online, you will need to add API permissions to your WorkZone app registration. See Register WorkZone apps in Azure.

New WorkZone for Office registry key for handling redirection templates

A new HideRedirectionTemplate registry key is available for WorkZone for Office Windows Registry. It defines how WorkZone for Office will handle the redirection templates when new documents are created from WorkZone Client.

See Registry keys.

ServerScan Directory Watcher Service

The new KMD ServerScan Directory Watcher Service is a Windows service that uploads scanned documents and their metadata to cases in WorkZone.

See Install and configure ServerScan Directory Watcher Service.

New behavior of guest user naming

When you create a guest user based on an e-mail address that is not of your organization's primary domain, the generated user name of the guest user will be suffixed with a running number. This behavior is introduced to ensure that all users have unique user names. It is generally recommended that you name your internal users uniquely, also across subdomains. Read more and see an example in Add guest users.

Updated configuration guidelines for WorkZone 365 add-ins

If your organization will use WorkZone 365 with shared mailboxes on the Microsoft Exchange Server 2019, you must set custom account to your WorkZone 365 application pool in the Internet Information Services (IIS). See Set custom account in WorkZone 365 application pool.

Updated configuration guidelines for WorkZone 365 add-ins

• To use WorkZone 365 add-ins, you will need to download and adjust relevant manifest files. See Deploy and configure WorkZone 365.
• For instructions on how to install and update WorkZone 365 add-ins, see Deploy and configure WorkZone 365 and Update existing WorkZone 365 add-ins.
• If your organization will use WorkZone 365 with shared mailboxes on the Microsoft Exchange Server 2019, you must add an impersonation permission to your Exchange server first. See Using WorkZone 365 with shared mailboxes on Exchange Server 2019.

SmartPost: Important if you upgrade from 2024.1 to 2024.2

If you upgrade from 2024.1 to 2024.2 and use SmartPost, you must cancel running SmartPost processes and restart them using the Send SmartPost dialog (not from the Processes Overview). This is to ensure that SmartPost uses the upgraded NgDP dispatcher.

Mass Dispatch: Important if you upgrade from 2024.1 to 2024.2

If you upgrade from 2024.1 to 2024.2 and use WorkZone Mass Dispatch, you must complete all mass dispatch processes before you upgrade. Any active mass dispatch processes will not continue to run after the upgrade.

Add process packages

You can now add customized process packages using in WorkZone Configurator.

Note that existing command line Package Loader tool is not supported in a cloud installation.

See Activate and load process packages.

This is the first version of this guide.