Important Notice: Mozzaik365 is now Jint

Please note that our solution is rebranding to Jint.

During this transition period, some technical components (such as application names, APIs, or domain names) may still temporarily reference our former name, Jint. This will not affect the installation process or the functionality of the product.

1. Introduction

1.1 Purpose of the article

The purpose of this article is to outline the technical and security requirements for installing,
upgrading, and using Translator, as well as the installation process.

Note: The installation steps require an Entra ID and SharePoint administrator.

1.2 Architecture of the Translator solution

The Translator solution consists of:

• A SharePoint package,
• A back-office, Jint Translator that will proceed to the translation,
• A set of APIs that rely on your Microsoft account for authentication.

1.3 Packages deployment

Translator extends the functionality of Microsoft SharePoint. We do this by deploying packages to
your SharePoint environment. These deployments occur automatically each time we release a new
version.

2. List of prerequisites

2.1 Summary

Here is a summary of the requirements for each component. They are detailed in the following
sections.

2.1.1 At the SharePoint level

• Administrator access to the application catalog:
  • Approval of an Entra ID application, Jint Deployment, requesting the
    Sites.Selected application permission. 
• Approval of calls to the following APIs:
  o Jint Translator

2.1.2 At Entra ID level 

• Approval of 3 Entra ID applications:
  • Jint Deployment
  • Jint Configurator
  • Jint Translator

2.2 Deployment of SharePoint packages

In order to deploy SharePoint packages, our deployment automaton needs the administrator rights of
the application catalog, as Microsoft does not offer more detailed rights. These rights are to be given
to our Entra ID application, Jint Deployment.

3. Installation steps

Once the previous requirements have been validated, the installation steps are as follows:

Except for step 4, these steps are to be performed by the Customer. At the end of these
steps, the Jint solution is usable by the Customer and its Integrator.

3.1 Preparation of the SharePoint tenant

Required access level for this step: SharePoint Administrator.

Preparing your SharePoint tenant consists of ensuring the global application catalog is created.

With a SharePoint administrator account, access the SharePoint administration console:

https://www.<your-tenant>-admin.sharepoint.com/

In the "More Features" menu, click on the "Open" button in the "Applications" section:

The application catalog is created if it did not already exist. 

3.2 Application approval for Jint Configurator and APIs 

Required access level for this step: Entra ID Administrator.
In order to allow Configurator and our APIs to authenticate your collaborators, you must approve the
following applications by clicking on the corresponding links: 

• Jint Deployment is the application that performs installations and updates of
  the Jint solutions on your Tenant. You will give it administrator rights to the
  application catalog to deploy SharePoint packages.
• Jint Configurator is the back office of Jint. It allows you to manage the solution perimeter. It requires delegated permissions to identify the user accessing the
  Configurator
  • User.Read
  • GroupMember.Read.All is only required for Jint client
• Jint Translator is the application that translate your pages content

Delegated permissions are permissions that allow an application to access a certain area of Microsoft 365 on behalf of a user. They allow Translator to display all relevant information for each
user. Learn more about delegated permissions.

3.3 Granting permissions to the application catalog 

Required access level for this step : Entra ID & SharePoint Administrator.

The granting of permissions to our Entra ID application is only done through a set of calls to the Microsoft Graph API. We propose a PowerShell script that can be downloaded here to make all these calls more easily.

This script will grant administrator rights to our Jint Deployment application on your application catalog. When running it, you will be prompted to log in with a SharePoint administrator account. The script will need the Sites.FullControl.All delegated permission in order to grant permission.

Once you have downloaded the archive, you need to extract the script to the folder of your choice. Then open a PowerShell command prompt and drag and drop the extracted file into the command prompt. Copy and paste the URL to application catalog after the path to the script and press Enter.

The command executed should be of the following form:

CreateAzureAdAppPermissionOnSites.ps1 <App Catalog URL> 

3.4 Communication of the necessary information to Jint

Access level required for this step: Entra ID Administrator. 

In order to proceed with the installation of Translator, we need the following information:

• Information about your Entra ID/SharePoint tenant:
  • Entra ID tenant ID,
  • Initial name of the Entra ID/SharePoint tenant,
• URL of the application catalog site identified in chapter 3.3,
• List of Translator solution manager email adresses.

Once this information has been collected, you must communicate it to your Jint contact.
In the following chapters, we detail where to find some of this information.

3.4.1 Information about your Entra ID tenant 

Go to the overview section of the Entra ID portal.

The tenant Id is named "Tenant ID" in the interface:

For the initial name of the tenant, go to the "Custom Domain Names" menu and look for the entry
ending in ".onmicrosoft.com". You can use the filter bar. The initial name of your tenant is what comes
before ".onmicrosoft.com". It is “Jint” in the example below. 

3.5 Deployment of the solution by Jint 

During this step, Jint teams proceed with the initial deployment of SharePoint packages for Translator, as well as the initialization of your Jint Configurator. Once completed, you will be notified by your Jint contact. 

3.6 Approval of Jint APIs Calls