Full guide for admin

Table of Contents

• Objective
• Quick Installation guide
  
• Requirements
• Step 1. Register an environment
• Step 2. Set up Single Sign-On
• Step 3. Configure SharePoint & File server(s)
• Step 4. Configure Email/Exchange
• Step 5. User & Group management
  • Azure AD synctool
• Step 6. App store
• Step 7. Configure Remote Desktop & Local apps
• Step 8. Create a Role-Based Workspace/template
• Step 9. Branding

Objective

Quick installation guide

Requirements

Step 1. Register an environment

With Workspace you are able to register multiple environments for multiple customers.

Binding an Office 365 tenant to a Workspace 365 environment is the first step when setting up the Workspace. You can even add a custom URL to redirect your customer environment, e.g. "/tenant X", to that same customer domain X. For this, we charge a one-time fee. Check out our Partner Pricing page for more information.
Multiple Workspace 365 environments can be linked to one Office 365 tenant and a single Workspace 365 environment can be linked to one Office 365 tenant. You can not link multiple Office 365 tenants to one Workspace 365 environment.

Each environment must be created with a global admin of the corresponding Office 365 tenant. For more information on how to register an environment, contact your Workspace 365 administrator or Submit a request.

After creation of the Workspace via e.g. the Powershell script, you'll be presented with the URL. Navigate to the URL. After you have logged in, you will be prompted to set up Single Sign-On.

Back to top

Step 2. Set up Single Sign-On

Workspace 365/Office 365 administrators are able to enable Single Sign-On (SSO) for their Workspace 365 environment, which helps to decrease login procedures for Workspace 365 users. The recommended setup for Single Sign On is oAuth2.

oAuth2 is an open standard for authorization, commonly used as a way for internet users to log in to third-party websites using their Microsoft, Google, Facebook, etc. accounts without exposing their password. Generally, oAuth2 provides clients with "secure delegated access" to server resources on behalf of a resource owner.

With configuration of oAuth2 in Workspace 365, you can sign in to Workspace 365 via your current federation and you are able to use MFA, also called 2 Factor Authentication (2FA) or MultiFactor Authentication (MFA).

To set up Single Sign-On automatically, choose the "Automatic setup". Workspace 365 will create an Azure AD application with the permissions you will grant. By default SharePoint and Exchange are checked. Additionally you can choose to add Power BI permissions to the application.

Back to top

Step 3. Configure SharePoint & File server(s)

After you have configured Single Sign-On, you can start to enter the Workspace. The Welcome wizard will ask you to configure Exchange and SharePoint. If you have Office365/Exchange Online you don't have to configure anything.

Sometimes your SharePoint URL cannot be detected. In that case, fill it in manually. Afterwards your SharePoint is configured by the wizard.

You can do additional configuration on the SharePoint and File server(s). Navigate to Settings -> SharePoint documents. Here you can choose to set your settings for SharePoint.

You can also choose to set up File server(s) in combination with SharePoint or as the only document store. Navigate to Settings -> File servers. Here you can configure the file server URL. Make sure this file server is accessible via WebDAV SSL.

Back to top

Step 4. Configure Email/Exchange

During the wizard you can set up Email/Exchange if you have Exchange Online. It is also possible to configure Exchange On-Premises. In that case you need to configure the Exchange EWS URL and provide the user credentials to access the mailboxes.

Back to top

Step 5. User & Group management

After you have set up the Workspace, it’s time to create or import users. It is possible to import users from Office 365. This can be done very easily by Importing users from Office 365. Keep in mind that the imported users will be notified via email that their Workspace is ready to use.

Azure AD synctool

It is also possible to sync this process and use our Azure Active Directory synctool. This tool will move the Identity Management from Workspace 365 to Azure AD. This synctool will also sync all the selected groups as a group to the Workspace, so you can assign permissions or roles based on your Azure AD Security Groups.

Back to top

Step 6. App store

Everything you need to know to create the best Role-Based Workspace within a few clicks.

After importing users and setting up Apps, it is important to offer these Apps to the users in an efficient way. Also, permissions for usage of certain Apps have to be set before they can be used.

Back to top

Step 7. Configure Remote Desktop & Local apps

If users still need a Legacy Application it’s possible to integrate it in different ways by using our Clientless RDP solution, which will connect to your Remote Apps or Remote Desktop. Local apps are only accessible via Workspace on the device on which they are installed.

Back to top

Step 8. Create a Role-Based Workspace/template

It is important to learn how to set up a Workspace 365 template. This will allow you to set up the Workspaces of new users within seconds. As an administrator, you can save a template of your current Workspace. This means that the template is updated with all of the Personal app groups that the administrator has set in his own Workspace.

Back to top

Step 9. Branding

As an administrator you are able to easily brand Workspace 365. You can select the colors, logo and even the product name. This will give you, as a partner, the recognition you deserve! After completing the steps in the document, you will be able to change the Branding of your workspace.

1. You can create a branding name.
2. You can create a Workspace name (Product Name).
3. Change the colors used in the Workspace (Header Color & Primary Color).
4. Implement the logos of your choice (Workspace logo & Sign in logo and Home logo.
   (The sign in logo is not visible when using single sign-on type OAuth2)
5. Create solid content for the support page (Support information).
6. You can add groups and/or users.

Back to top