On Premises

Configure Sign-in for WebAgent for Microsoft Teams

Note

An additional Anywhere365 WebAgent license is required.

To enable your organization to the WebAgent, you need to have completed the following steps.

Prerequisites

Note

When using the WebAgent make sure your browser is compatible with your user platform, see: WebAgent Browser Compatibility Overview

  • Before getting started make sure your account is enabled by Anywhere365 to login on the WebAgent. For more information, contact your Anywhere365 representative.

Microsoft 365 – settings

When using Microsoft 365 and Teams, two methods can be followed for granting the appropriate permissions for the Anywhere365 WebAgent (an Azure Enterprise App): Method 1, in which the App is consented upfront by a Global Admin, and Method 2, in which the App is consented as a Teams user when starting the Anywhere365 WebAgent client for the first time (after which a global admin can still consent the App for the entire organisation).

Method 1: Global Admin Consent via a Url (preferred)

Note

If an Admin in your organization has already consented the App in Method 2 below and selected the "Consent on behalf of your organization" in each step, then Method 1 is not required anymore.

Grant admin consent for your Organization:

As an administrator you can grant consent on behalf of all users in this directory, ensuring that each end user will not be required to consent when using the application for the first time. Navigate to below Url in a browser with a global admin account.

Copy
URL
https://login.microsoftonline.com/common/adminconsent?client_id=74d56274-d17b-4a8d-8e4f-fa424af82961&redirect_uri=https%3A%2F%2Fwebagent.anywhere365.io%2F

If a user in your organization has already consented to the App personally then below alternative steps allow you to find the App in your AD for granting global Admin Consent that way.

These are the permissions asked for to the Administrator, when they consent on behalf of the organization:

Active Permissions

Method 2: Consent via the WebAgent client

Step 1: User Consent Permissions signing in as Teams User:

Note

Your tenant needs to "Allow users consent for apps". If not the only users who have been granted a directory role that includes the permission to grant consent will be able to consent to new apps.

Tip

As Administrator you can consent on behalf of your whole organization. (This check box will only show for the Global Admin role, so Cloud Admin and App Admin will not see this checkbox.)
No one else will be prompted to review these permissions. For more information see Microsoft’s description of the Consent experience on Learn More - Microsoft.

When Microsoft Teams agents are registered in Microsoft 365 and agent accesses the WebAgent for the first time the user needs to approve the WebAgent App to be able to login.

This can be done by following:

  1. Got to https://webagent.anywhere365.io/

  2. Login using the Microsoft 365 button and in the new window accept the required permissions requested:

    These are the additional permissions asked if you use signs into the WebAgent for the first time and the App is not consented by the Administrator:

  3. After this the user can login on https://webagent.anywhere365.io

Step 2: User Consent Authorize for contact (people)list details:

Important

Starting from DC2024.02, you must be a Global Admin to perform this step. This requirement is due to the introduction of User.Read.All, which necessitates Admin Consent.

Note

Your tenant need to "Allow users consent for apps". If not only users who have been granted a directory role that includes the permission to grant consent will be able to consent to new apps.

Tip

As Administrator you can consent on behalf of your whole organization. (This check box will only show for the Global Admin role, so Cloud Admin and App Admin will not see this checkbox.)
No one else will be prompted to review these permissions.

When the user want the use the contact tab for the first time, the user needs to approve the WebAgent App to be able to load additional information.

  1. Make sure your are signed into the WebAgent

  2. Open the contact tab and select authorize

  3. Login using the Microsoft 365 button and approve:

    These are the permissions asked if user signs into contacts for the first time and the App is not consented by the administrator:

    Note

    • DC2024.01 and lower: Only the “Read all users’ basic profiles” permission is new in this step.

    • DC2024.01 and higher: Both the “Read all users’ basic profiles” and “Read all users’ full profiles” permissions are new in this step.

  4. After this the user can see additional information about contacts.

Step 3: User Consent Authorize for calendar details:

Note

Your tenant need to "Allow users consent for apps". If not only users who have been granted a directory role that includes the permission to grant consent will be able to consent to new apps.

Tip

As Administrator you can consent on behalf of your whole organization. (This check box will only show for the Global Admin role, so Cloud Admin and App Admin will not see this checkbox.)
No one else will be prompted to review these permissions.

When the user want the use their calendar(s) for the first time, the user needs to approve the WebAgent App to be able to login

  1. Make sure your are signed into the WebAgent

  2. Open the calendar and select authorize

  3. Login using the Office365 button and approve:

    These are the permissions asked if you use signs in calendar for the first time and the App is not consented by the administrator:

    Note

    Only the "Read your calendars" and "Read calendars you can access" is a new permission in this step.

  4. After this the user can use their calendars (own, delegated and shared calendars) in WebAgent.