Find your people. Pick a challenge. Ship something real. The CreatorCon Hackathon is coming to the Community Pavilion for one epic night. Every skill level, every role welcome. Join us on May 5th and learn more here.

Service user details are not valid/not setup properly. Please verify the configuration.

Manusha Badvelu
Giga Contributor

Hi Team,

 

I have Integrated Teams with ServiceNow and Able to chat with Live Agent, When trying to have a call using the /teams_call command/Action getting an error stating below.

Service user details are not valid/not setup properly. Please verify the configuration.

Any help would be appreciated.

Best Regards

 

 

 

 

1 REPLY 1

Markus Kraus
Kilo Sage

Might be too late, but I was facing the same issue and got it resolved by following this steps:
https://docs.servicenow.com/bundle/rome-employee-service-management/page/product/sn-teams/task/authe...

  1. Log in to Microsoft Azure portal.
  2. Navigate to Azure Services > Azure Active Directory > Manage > App registrations.
  3. Click the app created to enable agents to import the conversations from Microsoft Teams to the ServiceNow instance. 
    Example: ServiceNow Auth app.
  4. Navigate to Manage > Authentication.
  5. Navigate to Add a platform > Web applications > Web.
  6. On the Configure Web form, fill the fields.
    Redirect URIs: https://<instance-url>/sn_now_teams_ms_login.do 

    Implicit grant: [x] Access token [x] ID tokens (activate both)
  7. Click Configure
  8. Navigate to Manage > API Permissions > Add a permission > Microsoft Graph.
  9. Click Delegated permissions.
  10. Click Openid permissions accordion, and select email, offline_access, openid, and profile check-boxes.
  11. Click Add permissions.
  12. In the API permissions screen, click Grant admin consent for {tenant} link.
  13. Click Yes on the pop-up dialog box.
  14. Navigate to Manage > Expose an API.
  15. Click Set next to Application ID URI, and enter the application URI in the format: api://{instance}.service-now.com/{client_id}
    Note: the {client_id} is the client (application) id of the Teams Bot
  16.  Click Save.
  17.  Click Add a scope. In the Add a scope form, fill the following fields.
    Scope name: access_as_user
    Who can consent: Admins and users
    Admin consent display name: 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 display name: Teams can access the user profile and make requests on the user's behalf.

    User consent description: Enable Teams to call this app's APIs with the same rights as the user.
    State: Enabled
  18. Click Add scope button.
  19. Navigate to Authorized client applications > Add a client application.
  20. In the Add a client application form, fill the fields.
    Client ID
    • Microsoft Teams mobile/desktop application: 1fec8e78-bce4-4aaf-ab1b-5451cc387264
    • Value for Microsoft Teams web application: 5e3ce6c0-2b1f-4285-8d4b-75ee78787346
    Authorized scopesCheck the authorized scope
  21. Click Add application button.

 

Next in ServiceNow:

  1. Notify > Provider Selector > New
  2. Name: MS Teams
    Active: true
    Catch-all: true
  3. Save (stay on form)
  4. Provider Selector Choices (related list) > New
    Conference provider: Microsoft Teams
  5. Update