Microsoft® Teams® is a persistent chat-based collaboration platform that completely supports document sharing, online meetings, and other features for business communications.
Adobe Learning Manager uses a virtual classroom connector that can be used to integrate Microsoft Teams meetings with Learning Manager.
Microsoft Teams connector connects Learning Manager and Microsoft Teams systems to enable automatic virtual meeting synchronization. The following list describes the Microsoft Teams connector capabilities:
Set up virtual sessions using Microsoft Teams
This connector helps integrate your Adobe Learning Manager account with your Microsoft Teams account. Once integrated, the connector enables an Author in Learning Manager to use Microsoft Teams as the technology service provider for the Virtual Classroom modules created in Learning Manager.
Allow Microsoft Teams to authenticate learners when entering virtual classroom
This connector helps setup Microsoft Teams meeting organizer from Learning Manager while creating a meeting. The Meeting Organizer can manage lobby to restrict or admit entry into a meeting as well as control other meeting options provided by Microsoft Teams.
Use automated user completion syncing
The automated user completion syncing process allows a Learning Manager Administrator to automatically fetch the completion records and recording URL for the Microsoft Teams meeting.
If you're organizing a meeting with multiple participants, you can assign roles to each participant so that a participant can know what he/she can do in the meeting.
There are two roles to choose from: presenter and attendee.
For more information, see Roles in a Teams Meeting- Microsoft.
Note: Items marked <Developer/Optional> below are optional and mostly for setting up trial/developer tenants with Microsoft in case the user does not have a production tenant. These are optional since they mostly would have already been performed by your Team’s Administrator.
You can access Microsoft Teams connector if you have Office 365 E3 or Office 365 E5. The recommended option is Office 365 E5.
Note: The account must use the format “<username>@<company name>.onmicrosoft.com.”
Visit the Microsoft Azure® portal.
Sign in with the Microsoft E5 account that you created in the previous section.
Search for Azure Active Directory.
Click App Registrations.
Click New Registration, enter the following details, and register the application:
Name — Any name of your choice.
Supported account types — Accounts in any organizational directory (Any Azure Active Directory - Multitenant).
Redirect URI (optional) — Optional field indicating the reply URL.
In the Essentials column, note the following IDs, which will be further used during the integration:
Application (client) ID
Directory (tenant) ID
Search for client credentials and click Add a certificate or secret.
Click New Client secret and add the following details:
Description — Enter any name.
Expires — Set to any value (recommended value is 24 months. Ensure that new client credentials are generated once the previous one expires).
Note the client secret, which will be further used during the integration.
Visit the Microsoft Azure portal.
Sign in with the Microsoft E5 that you created earlier.
Search for Azure Active Directory.
Click App Registrations.
Click the app that you created in the previous section.
Click API permissions.
Click Add a permission.
Select Microsoft Graph > Application permissions and add the following permissions:
User.Read (This will be present by default)
Click Grant admin access for Adobe.
Click App roles > Create app role.
Enter the following values:
Display name — Name of the API/Permission name (For example, Calendars.ReadWrite).
Allowed member types — Specify both users and applications (Users/Groups + Applications).
Value — Name of the API/Permission name (For example, Calendars.ReadWrite).
Description — Name of the API/Permission name (For example, Calendars.ReadWrite).
Do you want to enable this app role? — Select this checkbox.
To configure the application access policy for Microsoft Teams connector by running PowerShell scripts, follow the procedure described in this document.
This enables the connector to access Microsoft Teams online meetings.
Note: In the above document, execute Optional step 5 as well to ensure that any active user can be granted the role of the organizer from within the Learning Manager Author app. If this step is not executed, users will not have the required access permissions to be organizers and the meeting creation will fail (Microsoft APIs consider the organizer to be the creator of a Teams meeting).
The API used for recording a session is a protected API. To access the API, you must request access from Microsoft. For more information, see this document.
In the document,
“To request access to these protected APIs, complete the following request form. We review access requests every Wednesday and deploy approvals every Friday, except during major holiday weeks in the U.S. Submissions during those weeks will be processed the following non-holiday week. To verify whether your request has been approved, test your application access on the next applicable Monday.”
For learners, the recording URL is displayed on the VC course overview page.
After 30 minutes of completing a course, the attendance for the learner gets marked.
Yes, the organizer should also be part of both Learning Manager and Microsoft Teams. Moreover, the organizer must be a part of the same Microsoft tenant, which is configured in the Integration admin app.
Yes, the presenter should also be part of both Learning Manager and Microsoft Teams. The presenter must have an Azure Active directory ID (can be part of the same tenant as the organizer or part of any other tenant). Moreover, even anonymous users (users who login with just the username and not part of Active Directory) can also be made presenters by the organizer/existing presenters during the meeting.