Important Information: Mozzaik365 becomes Jint

Please note that our solution is changing its name to become Jint.

During this transition period, some technical elements (such as application names, APIs, or domains) will still temporarily refer to our former name, Jint. This does not affect the installation procedure or the proper functioning of the product.

1. Introduction

1.1 Purpose of the Document 

This article aims to present the technical and security prerequisites for
the installation, update, and use of the Translator solution, as well as the installation procedure.
 

The installation steps must be followed by a person who is an administrator of Entra IDand
SharePoint.  

1.2 Architecture of the Translator Solution

The Translator solution consists of:

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

1.3 Deployment of Packages

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

2. List of Prerequisites 

2.1 Summary

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

2.1.1 At the SharePoint Level 

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

2.1.2 At the Entra ID Level 

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

2.2 Deployment of SharePoint Packages

To deploy the SharePoint packages, our deployment automation requires administrator rights
to the app catalog, as Microsoft does not offer finer-grained rights. These
rights must be granted to our application Entra ID, Jint Deployment.

3. Installation Steps

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

Except for step 4, these steps are to be carried out by the Client. At the end of these steps, the
Jint solution is usable by the Client and their Integrator. 

 

3.1 Preparation of the SharePoint Tenant 

Required access level for this step: SharePoint Administrator. 

Preparing your SharePoint tenant consists of ensuring the creation of the global app catalog. Using a SharePoint administrator account, access the Microsoft 365 admin console: https://admin.microsoft.com. 


In the left menu, select "Show all" then click on "SharePoint" in the "Admin centers" section: 




In the "More features" menu of the SharePoint admin center, click the "Open" button in the "Apps" section: 




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


For each subscribed site collection, you will need to create the corresponding app catalog. This is done via a few PowerShell commands with an account that is both a SharePoint administrator and an administrator of each target site:





# Install the Microsoft.Online.SharePoint.PowerShell module Install-Module  -Name Microsoft.Online.SharePoint.PowerShell 
# Connect to the SharePoint tenant 
Connect-SPOService -Url https://<your-tenant>-admin.sharepoint.com 
# Create/activate the app catalog for each site collection 
Add-SPOSiteCollectionAppCatalog -Site https://<your-tenant>.sharepoint.com/sites/<site-name>

3.2 Approval of Applications for the Configurator and Jint APIs

Required access level for this step: Entra ID Administrator.

To authorize the Configurator and our APIs to authenticate your collaborators, you must approve the following applications by clicking on the corresponding links:

 

Here is the description of each application:

• Jint Deployment is the application that performs the installations and updates
  of the Jint solutions on your Tenant. You will grant it administrator rights
  to the app catalog in order to deploy the SharePoint packages.

• Jint Translator is the application that enables to translate your page content

• Jint Configurator is the back-office of Jint. It allows you
  to administer the scope of the solution. It requests delegated permissions:

  • User.Read

  • GroupMember.Read.All is only used for Jint clients and is not required for Translator

     

Delegated permissions are permissions that allow an application to access certain
Microsoft365 domains on behalf of a user. They allow Translator to display
all relevant information for each user. More information about delegated permissions
can be found here. 


 

3.3 Granting Permissions to the App Catalog

Granting permissions to our Entra ID application is done solely through a set
of Microsoft Graph API calls.

We offer you a PowerShell script downloadable here to more easily perform all these calls.

This script will grant administrator rights to our Jint Deployment application on your app catalog.

 


During its execution, depending on your PC configuration, you will be prompted to accept downloading and installing modules from the internet: Microsoft.Graph.Sites.

You will also need an account that is an Entra ID administrator to authorize the script to interact with your Microsoft 365 environment via the delegated permission Sites.FullControl.All, and a SharePoint administrator to grant the correct permission to our application.

Once the archive is downloaded, extract the script into the folder of your choice. Then, for each site collection in the scope, right-click the file and "Run with PowerShell". The script will then ask you to enter the URL of the app catalog site.

 

3.4 Communication of Installation Information to Jint

Required access level for this step: Administrator Entra ID

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 app catalog site identified in chapter 3.2,
• List of identifiers of the Jint solution managers.

Once this information is collected, it must be communicated 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

Access the overview section of the Entra ID portal of the Entra ID portal. The tenant ID is named "Client ID" in the interface: 

For the initial tenant name, go to the menu "Custom domain names" and look for
the entry ending with ".onmicrosoft.com". You can use the filter bar. The initial name of
your tenant is what precedes ".onmicrosoft.com", "Jint" in the example below. 

3.5 Deployment of the Solution by Jint

During this step, the Jint teams carry out the initial deployment of the Translator SharePoint packages, as well as the initialization of your access to the Jint Configurator.

Once completed, you will be notified by your Jint contact.

 

3.6 Approval of Calls to Jint APIs

Authorize access to Jint Translator in order to access our translation service. To learn how to authorize the permission, see the article Approval of Permissions.

• API name: Jint translator
• Permission requested: user_impersonation
   

4. Using the Translator Solution

Translator is properly configured and deployed in your Microsoft environment! You can now start translating your content seamlessly within SharePoint.

Feel free to consult the Translator documentation on our help center to discover our
features and the different solutions we enable you to implement!