Table of Contents

PowerPlay - Overview & Introduction

Niamh Ferns Updated by Niamh Ferns

What is Tokity PowerPlay?

PowerPlay is a catalogue of Microsoft native solutions that leverage the Power Platform suite.

DeskDirector customers can utilise these out-of-the-box solutions to automate or simplify ITSM/ESM tasks like managing leavers and joiners, assets, change, and problem tracking, and automatically managing contact groups.

Setting Up Tokity PowerPlay

If you'd like to get up and running with Tokity PowerPlay straight away, please see our Quick Start Guide. You'll find a set of videos that guide you from initial pre-deployment checks all the way to a working environment with Entra Sync Groups set up.

Alternatively, below you can find a series of steps that you'll need to follow to set up your Tokity PowerPlay environment:

  1. Perform the Pre-deployment Checks
  2. Provision and Deploy your Service Provider and Customer Environments
  3. Complete the Post-deployment Steps
  4. Pick any solutions you'd like to deploy from our Solutions Gallery and then follow the steps in their respective articles to get started

Terminology

Before getting set up with Tokity PowerPlay, it is important to understand much of the terminology that will be used in the setup documentation. You can find a list of these terms below:

General

  • Power Platform: This is the set of offerings by Microsoft for low/no-code automation and app building. We will mostly be dealing with Power Apps, although you may want to use Power Automate occasionally for troubleshooting your automations if you make modifications or run into issues with setup.
  • Microsoft Tenant: This is a sectioned-off Microsoft environment for Microsoft 365 and Azure. Most companies will have at least a main tenant. Some companies may also have a separate tenant to use as a Sandbox environment.
  • Managed Solution: This refers to solutions in Power Platform that cannot be edited or changed once deployed. Managed solutions deployed as part of Tokity PowerPlay are fully managed by DeskDirector.
    You can find your managed solutions in Power Apps under the Solutions tab by selecting Managed on the filter bar.
  • Unmanaged Solution: This refers to solutions in Power Platform that can be edited or changed at will. We generally cannot provide support for unmanaged solutions that have been modified outside of what is shown in our guides.
You can find your unmanaged solutions under the Solutions tab by selecting Unmanaged on the filter bar.

Power Apps will show you your unmanaged solutions by default.
  • Default Solutions: This refers to the default unmanaged solution in an environment.
  • Environment Variables: An environment variable is a piece of reusable information that can be referenced in each of your Power Platform environments. For example, these may be used to set your DeskDirector Host in a single location and then reference it elsewhere in your environment without having to set it in multiple places.
  • Connections: Connections refer to the various services accessible in Power Platform to interact with things like DeskDirector, Teams, or outside platforms. You can read more here.
  • Connection References: Connection references provide a named reference to a connection that can be imported and used in your Power Platform apps and automations. We use connection references to allow you to connect PowerPlay to Connections in your environment. You can read more here.

DeskDirector-Specific

  • DeskDirector Host/Domain: This refers to the standard URL for your DeskDirector instance, excluding any protocol or path. For example, if you normally visit https://support.deskdirector.com/portal/v2, your DeskDirector host would be support.deskdirector.com.
  • ServOrg (Service Organisation): This refers to the Power Platform environment that lives within the service provider's Microsoft tenant.
  • CustOrg (Customer Organisation): This refers to the Power Platform environment that lives within a client or customer's Microsoft tenant. You may also have a CustOrg in the same tenant as a ServOrg.
    To use solutions for your own company, you will need to have both a CustOrg and a ServOrg for your Microsoft tenant.
  • Base Name: This refers to the name that precedes our environment naming. For example, if you have the base name Test Company, your environments will be named Test Company Tokity ServOrg and Test Company Tokity CustOrg respectively.
  • Admin Portal: This refers to your DeskDirector Admin Portal. Here you can configure your DeskDirector instance.
  • Solutions Library: This refers to the solutions library tab in your DeskDirector Admin Portal. Here, you can deploy the parts needed in your DeskDirector instance for each of our PowerPlay solutions.

Further Reading

Before continuing, we recommend at least a basic understanding of the Microsoft Power Platform, basic Microsoft 365 and Azure Administration, basic IT administration, and familiarity with basic Command Line Interface (CLI) usage.

For a smooth experience, we also recommend having a member of your IT department either assist or conduct the deployment of these solutions.

How did we do?

Contact