Requirements:
tixxtCloud Business, IndividualCloud Enterprise, IndividualCloud Maxx
Upon request: tixxt Enterprise
Administrator rights and relevant technical knowledge to manage a Microsoft Azure tenant
The network administrator can set up connections from the tixxt network to Microsoft services here.
This includes Microsoft Teams Meetings integration as well as setting up a Microsoft mail server for sending tixxt system emails (such as network invitations, appointment integrations or notifications about new posts in a subscribed group).
Regardless of whether MS Teams integration or the M365 mail server will be used, the requested information must first be entered under the “General” tab.
General #
- Step 1: Microsoft Teams info
- Step 2: Configuration
- Step 3: OAuth provider
- Step 4: Delete integration
General note:
- All steps are broken down into individual instructions that must be carried out in order by a network admin with the appropriate permissions in Teams.
- Each step can be completed separately; the next steps can be edited at a later time.
- Once a step has been completed, it is highlighted in green.
Step 1: Info #
Before the configuration can begin, the network admin must confirm the notice.
Once the notice has been confirmed, it can still be retrieved and read. You can also see who has accepted the notice and when.
If the notice has been accepted, the entire section is highlighted in green.
Step 2: Configuration #
The actual configuration begins in this section. From this point on, it is necessary to have administrator rights for a Microsoft Azure tenant.
The aim of the configuration is to create an application via the Azure portal that is linked to tixxt and has the mandatory permissions in the respective tenant. After configuration, the tixxt users are automatically synchronised in the background with the tenant users.
The individual steps must be carried out in order.
Additional info:
- After completing step 14 (select ‘Generate certificate’), the admin receives the confirmation message: ‘Certificate generated successfully’. This must then be downloaded locally in step 15. This triggers a further confirmation message: ‘Certificate downloaded successfully’.
- Clicking on “Complete configuration” (step 18) completes the configuration process, which may take a few minutes. After the configuration has been successfully completed, you receive the confirmation message: ‘The configuration has been tested successfully.’
If the configuration has been completed successfully, this section is also highlighted in green.
Step 3: OAuth provider #
In this section, the network admin sets up the option for network members to permanently link their Microsoft account to their tixxt network account. tixxt users and Teams users are always synchronised automatically and identical email addresses are recognised. However, if the email address of a Teams user differs from that in tixxt or is subsequently changed, it is mandatory to link them manually using OAuth.
The individual steps must be carried out in order.
Additional info:
- The easiest way to find the application created in step 2 is to search for the name of the application using the search dialogue in Microsoft tenant.
- Once all steps have been completed, the following confirmation message appears: ‘Provider created – please test the configuration under ‘Account & password’ by linking your Microsoft Azure account.’ This test is optional but recommended. You can continue directly with step 4.
If the OAuth Provider has been set up successfully, this section is also highlighted in green.
Delete integration
This action may only be carried out if the Microsoft integration will no longer be used. The function will be deactivated for all users.
MS Teams
- Step 1: Configuration
- Step 2: Editorial users
- Step 3: Network settings
- Step 4: Enable “Bypass lobby” for tixxt.
General note:
- All steps are broken down into individual instructions that must be carried out in order by a network admin with the appropriate permissions in Teams.
- Each step can be completed separately; the next steps can be edited at a later time.
- Once a step has been completed, it is highlighted in green.
Step 1: Configuration
The goal of the configuration is to provide the tenant with the necessary permissions in the Azure portal to be able to create appointments in the respective tenant.
After configuration, the tixxt users are automatically synchronised in the background with the tenant users.
The individual steps must be carried out in order.
If the configuration has been completed successfully, this section is also highlighted in green.
Step 2: Editorial user #
In this section, the network admin defines an editorial user.
This user appears as the appointment creator in the Microsoft Teams tenant if an appointment has been created by a tixxt user who does not have an associated Teams user or whose user is not yet correctly linked.
The editorial user does not need to be a Microsoft Azure admin, they only need to have the appropriate permission to create Microsoft Teams meetings.
Under ‘Editorial user UPN’, the network admin enters the desired editorial user in the form of a personalised email address.
Once the editorial user has been entered and saved, this section is also highlighted in green.
Step 3: Network settings #
In this section, the network admin defines more settings for the integration.
Meetings in Teams are synchronised for
- Network admins (standard)
- Network admins and group admins
This means: Creating Teams meetings is restricted to network admins in the standard setting. The rights can be extended, however, to allow group admins to create Teams meetings for their groups as well.
Enable tixxt notifications for teams appointments
- Yes (standard)
- No
This means: With the standard setting, both tixxt system emails and Microsoft Teams system emails are sent for appointment invitations or updates, for example. If you do not want this, you can deactivate the tixxt system emails for Teams meetings created via tixxt.
To save the configuration settings, click on ‘Save settings’.
Step 4: Enable “Bypass lobby” for tixxt.
By default, Attendees for Teams meetings remain in the lobby until the organiser lets them in. The organiser is the person who created the meeting.
This sixth configuration step offers two options for bypassing the lobby for attendees in a Microsoft Teams meeting. Please note that this implies that the meeting is initiated by the same or a trusted organisation.
Option A describes the procedure for deactivating the lobby for the entire Teams tenant.
This setting affects all Microsoft Teams meetings in the tenant, whether created via tixxt or directly in Microsoft Teams.
Option B requires some technical proficiency. Using Microsoft Powershell, the lobby can be bypassed specifically for Teams meetings created via tixxt.
M365 mail delivery
- Step 1: Configuration
- Step 2: Available permissions
General note:
- All steps are broken down into individual instructions that must be carried out in order by a network admin with the appropriate permissions in Teams.
- Each step can be completed separately; the next steps can be edited at a later time.
- Once a step has been completed, it is highlighted in green.
Step 1: Configuration
The goal of the configuration is to set the correct permissions in the Azure Portal so that tixxt is authorized to send system emails via the stored Microsoft tenant.
The individual steps must be carried out in order.
If the configuration has been completed successfully, this section is also highlighted in green.
Step 2: Available permissions
To complete the Exchange mail server configuration, mail delivery must be authorised. To do this, select the “Authorise outbound email via Microsoft Exchange” button.
Note: Use the Microsoft user whose email address is to be used to send tixxt system emails.
If configuration has been completed successfully, this section is also highlighted in green.
Author:
