Integrate with Microsoft Teams

Prerequisites

Before you install and configure a Microsoft Teams orchestrated system, you should consider the following prerequisites and tasks.

Certified Components

The system must be the following:

  • Microsoft Teams

Supported Modes

Microsoft Teams orchestrated system supports the following modes:
  • Managed System

Supported Operations

The Microsoft Teams orchestrated system supports the following operations:
  • Create User
  • Delete User
  • Reset Password
  • Add Teams Group
  • Remove Teams Group

Microsoft Teams Application Configuration and Settings

Before you can establish a connection, you need to perform the following tasks in your Microsoft Teams application:
  • Create and register an enterprise application that you want to integrate with Oracle Access Governance. For more information, refer Microsoft documentation.
  • Generate a client secret for the application
  • Assign the following delegated permissions that the client application requires on Microsoft Teams Directory:

    Delegated Permission

    • Read and write directory data

    • Read and write all groups

    • Read all groups

    • Access the directory as the signed-in user

    • Read directory data

    • Read all user’s full profiles

    • Read all user’s basic profiles

    • Sign in and read user profile

  • Add the client application to "Company Administrator" and “User Account Administrator” in the Microsoft Teams administrative roles.

    For more information, refer Microsoft documentation.

Configure

You can establish a connection between Microsoft Teams and Oracle Access Governance by entering connection details. To achieve this, use the orchestrated systems functionality available in the Oracle Access Governance Console.

Navigate to the Orchestrated Systems Page

Navigate to the Orchestrated Systems page of the Oracle Access Governance Console, by following these steps:
  1. From the Oracle Access Governance navigation menu icon Navigation menu, select Service Administration → Orchestrated Systems.
  2. Click the Add an orchestrated system button to start the workflow.

Select system

On the Select system step of the workflow, you can specify which type of system you would like to onboard.

  1. Select Microsoft Teams.
  2. Click Next.

Add Owners

You can associate resource ownership by adding primary and additional owners. This drives self-service as these owners can then manage (read, update or delete) the resources that they own. By default, the resource creator is designated as the resource owner. You can assign one primary owner and up to 20 additional owners for the resources.

Note:

When setting up the first Orchestrated System for your service instance, you can assign owners only after you enable the identities from the Manage Identities section.
To add owners:
  1. Select an Oracle Access Governance active user as the primary owner in the Who is the primary owner? field.
  2. Select one or more additional owners in the Who else owns it? list. You can add up to 20 additional owners for the resource.
You can view the Primary Owner in the list. All the owners can view and manage the resources that they own.

Enter details

On the Enter Details step of the workflow, enter the details for the orchestrated system:
  1. Enter a name for the system you want to connect to in the What do you want to call this system? field.
  2. Enter a description for the system in the How do you want to describe this system? field.
  3. Determine if this orchestrated system is an authoritative source, and if Oracle Access Governance can manage permissions by setting the following checkboxes.
    • This is the authoritative source for my identities
    • I want to manage permissions for this system
    The default value in each case is Selected.
  4. Click Next.

Account settings

On the Account settings step of the workflow, enter details of how you would like to manage accounts with Oracle Access Governance when configured as a managed system:
  1. Select where to send notification emails when an account is created. The default setting is User. You can select one, both, or none of these options. If you select no options then notifications will not be sent when an account is created.
    • User
    • User manager
  2. When an identity moves within your enterprise, for example when moving from one department to another, you may need to adjust what accounts the identity has access to. In some cases the identity will no longer require certain accounts which are not relevant to their new role in the enterprise. You can select what to do with the account when this happens. Select one of the following options:
    • Disable
    • Delete
  3. When an identity leaves your enterprise you should remove access to their accounts. You can select what to do with the account when this happens. Select one of the following options:
    • Disable
    • Delete

Note:

If you do not configure your system as a managed system then this step in the workflow will display but is not enabled. In this case you proceed directly to the Integration settings step of the workflow.

Note:

If your orchestrated system requires dynamic schema discovery, as with the Generic REST and Database Application Tables (Oracle) integrations, then only the notification email destination can be set (User, Usermanager) when creating the orchestrated system. You cannot set the disable/delete rules for movers and leavers. To do this you need to create the orchestrated system, and then update the account settings as described in Configure Orchestrated System Account Settings.

Integration settings

On the Integration settings step of the workflow, enter the configuration details required to allow Oracle Access Governance to connect to Microsoft Teams.

  1. In the Host field, enter the host name of the machine hosting your Microsoft Teams system.

    For example, for the Microsoft Graph API, you may enter graph.microsoft.com

  2. In the Port field, enter the port number at which the system will be accessible.

    Note:

    This field is not mandatory.
  3. Enter the client ID (a unique string) value. The client ID, also known as Application ID, is obtained when registering an application on Microsoft Entra ID (formerly Azure Active Directory). This value identifies your application in the Microsoft identity platform. For more details refer Microsoft documentation.
  4. In the Client secret field, enter the secret ID value to authenticate the identity of your client application. You need to create a new client secret for your application and enter the value in this field.
  5. In the Authentication Server Url field, enter the URL of the authentication server that validates the client ID and client secret for your target system in the Authentication Server Url field.
  6. Click Add to create the orchestrated system.

Postconfiguration

There are no postinstall steps associated with a Microsoft Teams system.