Breadcrumbs

14.27 Integration and Connector Updates

Integration Updates

Integration updates are listed below:

MS Teams Permission Configuration

Overview: The MS Teams connector now enables the configuration of delegated permissions. This update enables Microsoft Teams to restrict an application's access to specific team channels and meetings.

Benefits and Use Cases: Allows the use of a dedicated user account to manage permissions, which improves the granularity of access control​. Benefits include:

  • Greater control over how applications interact with Teams ​

  • Strengthens data privacy and meeting security​

  • Helps ensure compliance and governance across collaboration tools​.

Audience: MS Teams Administrators

Setup & Access: New settings will be applied automatically in the External service provider function. The default values will remain set to ‘Application permission’ meaning there’ll be no immediate change in the behavior after update.

  • External service provider

    • Permission type

    • Redirect URL

  • Microsoft Azure configuration

  • In the External service providers function there is a new Permission type setting for MS Teams

  • The setting will contain 2 options, single selection

    • Application permissions: Also known as app roles and are used in the app-only access scenario, without a signed-in user present. The application is able to access any data that the permission is associated with.

    • Delegated permissions: Used in the delegated access scenario and are permissions that allow the application to act on a user's behalf. The application isn't able to access anything the signed in user couldn't access.

  • Depending on which option is selected per service provider, the system would behave as it was the case so far (application permissions) or different behavior is in place (considering users rights for resources)

Considerations & Limitations: The MS Teams connector is a licensed integration available on Kubernetes architecture. The update is not supported in the Easy Course Creation function for media creation for MS Teams media.

Testing: Requires the MS Team Connector licence and Kubernetes architecture. The Permission type setting will be visible in the External service provider function.

Risk rating: Low

Connector Updates

Connector updates are listed below:

MS Teams Support in ECC Easy Media Upload

Overview: The Easy Media Upload (EMU) feature in the Easy Course Creation (ECC) function now supports MS Teams media creation. This is possible in the Content overview step to select creation of a MS Teams Meeting object. The media type used as the basis for creation is configurable per client. Main MS Teams Meeting attributes and further Info can be added including:

Meeting name, description, presenter, external service provider, image, keywords, purpose of media, required attendance time (in minutes)., Share as Event, location, start-end date, Time zone, Access before the meeting starts, create an appointment in the participants’ calendars, translations

If configured in the workflow, participants assigned to the course will also be assigned to the corresponding online meeting of the course. The meeting URL is displayed in the course overview at the end of the creation process.

Benefits and Use Cases: With much decentralised training occurring online through MS Teams Meetings, efficient workflows are important. Previously with the ECC, MS Teams Meeting links had to be manually generated, then sent to participants, and attendance checking would be manually performed. This update delivers a seamless integration of the MS Teams Meeting media creation in the Easy Course Creation workflow and improved tracking.

Audience: Course administrators, MS Team Presenters

Setup & Access: The update will be automatically available for configuration by the following steps:

  • In the Media types function prepare the MS Teams media type with desired default values.
    Grant ‘view’ clearance on the media type to any group/user that will create MS Teams Meetings.

  • In the Clients function:

    • highlight a client,

    • click the Settings icon

    • select the Easy media upload option

    • In the ECC section click the MS Teams meeting field to link the MS Teams media type

These steps are based on the ECC function and MS Teams connector being pre-configured. Further information on these topics is available in the Customer Documentation space.

Considerations & Limitations: The MS Teams connector is a licensed integration available on Kubernetes architecture.

Testing: Requires that the ECC function is configured with Easy Media Upload and the MS Teams connector is enabled. In the Clients function edit the Easy Media Upload setting to link the MS Teams media type. Once done, create a course in the ECC and go to the Content overview step. When clicking the Create content button there will be a MS Teams Meeting box.

Risk rating: Low