Identify and check your WorkZone apps and registrations

It is important that you know the setup and configuration of your WorkZone installation. Depending on your hosting and deployment model, there are some key differences as to where and what you will need to configure.

• If you are in doubt, contact your WorkZone hosting partner.

Multi-tenant setup (Enterprise application)

If you are a WorkZone Public Cloud or EU Cloud customer (that is, your hosting partner is KMD), you will be using the multi-tenant setup. This means that the app registration and all settings will be managed by KMD. To start using Intune, create a service request in KMD Service Portal asking to get Intune enabled on your WorkZone solution app registration.

Other hosting partners may also use the multi-tenant setup.

Multi-tenant setup (Enterprise application) means that initial WorkZone application registration is not created in the same tenant as the end users of WorkZone (called the customer tenant). Instead, it is created by the hosting partner in a separate tenant (called hosting tenant), and then federated to the customer tenant.

As the result, you will see WorkZone application registration as an Enterprise application in your tenant, and settings for the application will be managed in the hosting partner tenant - you will not be able to change them in your tenant.

For the detailed steps, see Microsoft article Add an enterprise application.

Single-tenant setup (App registration)

If your WorkZone installation is hosted in the same tenant as the WorkZone end users (called customer tenant), the application registration will be created directly in the same tenant.

As the result, you will see WorkZone application registration as a normal App registration, and your Azure administrator can change and manage its settings directly.

For the detailed steps, see Microsoft article Register an application with the Microsoft identity platform.