Share your Azure Tenant ID with TechWolf. TechWolf will configure the Skill Assistant to work with your production tenant. Follow the steps in Get Azure Tenant ID to find your Azure Tenant ID.

Install the Skill Assistant in your Microsoft Teams environment by following these steps

Install the Skill Assistant for users following these steps

We need a method to link Employees in the TechWolf API to Teams Users in Microsoft Teams. See Linking Microsoft Teams users and TechWolf Employees .

Go to your Teams admin page.

Go to Teams apps -> Manage apps

Type “TechWolf Skill Assistant” in the search bar.

Click on the name of the “TechWolf Skill Assistant” app.

Navigate to the Permissions tab (1).

Grant the app the required permissions. Do so by pressing Grant admin consent (2). This will open a pop up.

Select your account and log in if necessary (1).

Review the required permissions and grant them, by clicking Accept (2).

The easiest way to install the app for a subset of users is to create a group in Azure AD and assign the app to that group. This way, you can easily manage who has access to the app. To create a group, follow the Microsoft guide on creating a group.

If the existing permission policy does not allow third-party apps, you need to update the policy to allow the TechWolf Skill Assistant. You can do this by following the Microsoft guide on updating permission policies.

You can install the app for a group of users using setup policies. Follow the Microsoft guide on setting up policies.

If the app is not installed for all users, you can force the installation for the remaining users using the Microsoft Graph API by following these steps.

Create a text file containing all Azure IDs of the people for which the app needs to be installed. This file is structured as a list of the Azure IDs, separated by newlines.

azure_id_1
azure_id_2
azure_id_3
...

We created a template script that you can use to force install the app.

Create a new service principal in Azure AD to run the script. Follow the Microsoft guide on creating a service principal.

A client secret is needed to run the script.

In the newly created service principal, select Certificates & secrets.

Select Client secrets, and then select New client secret and click Add.

You will need this secret later to run the script.

The script requires the TeamsAppInstallation.ReadWriteForUser.All and User.Read.All permissions.

In the service principal, select API permissions.

Click on Add a permission and select Microsoft Graph.

Select Application permissions and search for TeamsAppInstallation.ReadWriteForUser.All and select it.

Search User.Read.All and select it too.

Click on Add permissions to add the permission.

Select the added permissions and click Grant admin consent.

Fill in the variables in the script:

• $FilePath: the path to the previously created file (from Step 1) containing the Azure IDs
• $ApplicationID: The Application Client ID of the newly created service principal (from step 3)
• $ClientSecret: The Application Client Secret of the newly created service principal (from step 4)
• $TenantID: The tenant ID of your Teams instance

Run the script in Powershell.

In Azure Portal, click in the top right on the Cloud Shell icon.

Click on Manage files and upload the file with Azure IDs and the filled in script. Run the script by typing ./script.ps1.

The first step is creating an Azure Bot Service in your Azure Portal. This will give you an App ID and a client secret.

Share the ID and secret from step 1. with TechWolf, in addition with your Azure Tenant ID. TechWolf then configures the TechWolf bot backend, to be able to send and receive messages to and from your configured Bot Service.

TechWolf produces an app manifest, which can be used to install the bot in Teams. This manifest is created in line with the documentation provided by Microsoft. Install the bot in your Microsoft Teams environment.

We need a method to link Employees in the TechWolf API to Teams Users in Microsoft Teams. See Linking Microsoft Teams users and TechWolf Employees .

Go to the Azure Portal.

In the search box enter bot, then press Enter.

Select the Azure Bot card.

Click Create.

Fill in the required fields.

Click Review + Create, and finish the process by clicking Create.

Navigate to the Configuration section in the side-panel.

Add the TechWolf {messaging endpoint}. This endpoint will be shared with you since this depends on your region.

Take note of the Microsoft App ID, and apply changes. This App ID must later be shared with TechWolf.

In the same view, above the Microsoft App ID field, click on Manage Password, or navigate to the Certificates & secrets page of the Bot’s corresponding App registration. Create a new client secret and take note of its values. The secret must later be shared with TechWolf.

While you are in the App registration, navigate to the overview and take note of the `Directory (tenant) ID.

Under Channels in the side-panel, add Microsoft Teams as a channel. (You have to click on the actual text to add it).

Share (1) the previously created App ID, (2) client secret, and (3) Directory (tenant) ID with TechWolf.

Go to your Teams admin page (https://admin.teams.microsoft.com/).

Go to Teams apps -> Manage apps

Click Upload new App

In the pop-up, click on Upload and select the manifest (ZIP file) you received from TechWolf (in the Installation section, step 4).

The easiest way to install the app for a subset of users is to create a group in Azure AD and assign the app to that group. This way, you can easily manage who has access to the app. To create a group, follow the Microsoft guide on creating a group.

If the existing permission policy does not allow third-party apps, you need to update the policy to allow the TechWolf Skill Assistant. You can do this by following the Microsoft guide on updating permission policies.

You can install the app for a group of users using setup policies. Follow the Microsoft guide on setting up policies.

Create a text file containing all Azure IDs of the people for which the app needs to be installed. This file is structured as a list of the Azure IDs, separated by newlines.

azure_id_1
azure_id_2
azure_id_3
...

We created a template script that you can use to force install the app.

The script requires the TeamsAppInstallation.ReadWriteForUser.All and User.Read.All permissions.

In the TechWolf application in Azure, select API permissions.

Click on Add a permission and select Microsoft Graph.

Select Application permissions and search for TeamsAppInstallation.ReadWriteForUser.All and select it.

Search User.Read.All and select it too.

Click on Add permissions to add the permission.

Select the added permissions and click Grant admin consent.

Fill in the variables in the script:

• $FilePath: the path to the previously created file (from Step 1) containing the Azure IDs
• $ApplicationID: The Application Client ID of the TechWolf application in Teams. See the screenshot below on how to find this ID.
• $ClientSecret: The Application Client Secret of the TechWolf application in Azure. This can be the one shared with TechWolf
• $TenantID: The tenant ID of your Teams instance
• $OrgApplicationID: The external application ID of the TechWolf application in Teams. See the screenshot below on how to find this ID.

Run the script in Powershell.

In Azure Portal, click in the top right on the Cloud Shell icon.

Click on Manage files and upload the file with Azure IDs and the filled in script. Run the script by typing ./script.ps1.

Navigate to the Azure Portal.

Go to the Authentication section under the Manage tab of your application (not the bot itself).

Select Add a Platform and choose Web. In the Redirect URI, enter the same {messaging endpoint} used in step 9 of Creating an Azure Bot, omitting /api/messages.

Enable Access tokens (for implicit flows) and ID tokens (for both implicit and hybrid flows).

Add the following Redirect URI: https://token.botframework.com/.auth/web/redirect.

Under “Who can use this application or access this API?”, select Accounts in any organizational directory (Any Microsoft Entra ID tenant - Multitenant).

In the API permissions section, add User.Read from Microsoft Graph as Delegated Permissions.

Go to the Expose an API section.

Set the Application ID URI to api://{tab endpoint}/botid-{app-id}. The {app-id} is the same as the Microsoft App ID from step 10 of Creating an Azure Bot. Similar to the {messaging endpoint}, the {tab endpoint} will be provided by TechWolf based on your region.

Click on Add a scope. In the panel that opens, enter access_as_user as the Scope name.

Set “Who can consent?” to Admins and users.

Fill in the fields for configuring the admin and user consent prompts with the following values:

• Admin consent title: Teams can access the user’s profile
• Admin consent description: Allows Teams to call the app’s web APIs as the current user.
• User consent title: Teams can access your user profile and make requests on your behalf
• User consent description: Enable Teams to call this app’s APIs with the same rights that you have

Ensure the scope is Enabled.

Include the following client application IDs for Microsoft Teams:

• 1fec8e78-bce4-4aaf-ab1b-5451cc387264 (Teams Mobile/Desktop app)
• 5e3ce6c0-2b1f-4285-8d4b-75ee78787346 (Teams Web app)