---
sourceDocument: Australia ServiceNow AI Platform Administration
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/platform-administration
Release :
- australia
ft:locale :
- en-US
ft:publication_title :
- Australia ServiceNow AI Platform Administration
ft:clusterId :
- platadm
bundleId :
- platadm
workflow :
- Platform
---
# Configure source system
# Configure Microsoft Viva Engage for external content indexing {#ariaid-title1}
Release version: Australia
Updated March 12, 2026
 2 minutes to read
Register an OAuth 2.0 application in the Microsoft Entra admin center to allow the Microsoft Viva Engage external content connector to access your Microsoft Viva Engage source system.
## Before you begin
You need the following credentials and permissions for your organization in the Microsoft Entra admin center:
* Login credentials
* Permission to register an application
* Permission to add API permissions to an application
* Permission to create client secrets for an application
{#configure-microsoft-viva-engage-external-content-indexing__ul_tsn_12d_tdc}
Role required: none
## About this task
The Microsoft Viva Engage external content connector retrieves content from your Microsoft Viva Engage source system using the Yammer API.
To enable the connector to access your Microsoft Viva Engage source system via these APIs, you must configure an OAuth 2.0 application in the Microsoft Entra admin center. Your connector administrator can use settings copied from this Microsoft Entra application to configure the Microsoft Viva Engage external content connector for proper connection to your Microsoft Viva Engage source system.
## Procedure
1. Register a new application in the Microsoft Entra admin center.
1. Log in to the Microsoft Entra admin center at .
Note:
If your Microsoft Viva Engage tenant is in the Microsoft 365 GCC or GCC High cloud or the Microsoft 365 DoD cloud, log in at instead.
2. Select ApplicationsApp registrations.
3. On the App registrations page, select New registration.
4. On the Register an application form, fill in the following fields:
{#configure-microsoft-viva-engage-external-content-indexing__table_zzr_jwc_tdc__entry__2}
| Field | Instructions |
|-|-|
| Name | Enter a unique name for your OAuth 2.0 application. For example, you might enter Microsoft Viva Engage external content connector. |
| Supported account types | Select Accounts in this organizational directory only (\ only - Single tenant), where \ is the name of your Microsoft Entra instance. |
| Redirect URI (optional) | Select Web as the redirect URI type, then enter https://<instance-name>.service-now.com/oauth_redirect.do as the URI, replacing <instance-name> with the hostname for the ServiceNow AI Platform® instance where the Microsoft Viva Engage external content connector will be created. |
[ ]
{#configure-microsoft-viva-engage-external-content-indexing__table_zzr_jwc_tdc}
5. Select Register.
The new application's Overview page appears.
{#configure-microsoft-viva-engage-external-content-indexing__substeps_kg2_zvc_tdc}
2. Record the values of the new application's Application (client) ID and Directory (tenant) ID properties in a secure location.
Important:
Your connector administrator needs the application's tenant and client IDs to configure a Microsoft Viva Engage external content connector. {#configure-microsoft-viva-engage-external-content-indexing__client-tenant-ids-step}
{#configure-microsoft-viva-engage-external-content-indexing__client-tenant-ids-step}
3. Create a client secret for the new application.
1. In the application menu, select ManageCertificates \& secrets.
2. Select Client secrets, then select New client secret.
3. In the Add a client secret pane, enter a description for the secret and select its expiration period, then select Add.
The new client secret appears in the Client secrets list.
4. Copy the new client secret's Value and record it in a secure location.
Important:
Your connector administrator needs the value of this client secret to configure a Microsoft Viva Engage external content connector. {#configure-microsoft-viva-engage-external-content-indexing__copy-client-secret}
{#configure-microsoft-viva-engage-external-content-indexing__copy-client-secret} {#configure-microsoft-viva-engage-external-content-indexing__substeps_mk4_h2j_4fc}
4. Add the Yammer API permission required by the Microsoft Viva Engage external content connector.
1. In the application menu, select ManageAPI permissions.
2. Select Add a permission, then select Yammer.
3. Select Delegated permissions, then select the option for the user_impersonation permission and select Add permissions.
The new Yammer API permission appears in the application's Configured permissions list.
{#configure-microsoft-viva-engage-external-content-indexing__substeps_kfx_3xc_tdc}
{#configure-microsoft-viva-engage-external-content-indexing__steps_bvm_bhz_t2c}
## What to do next
Provide the following items to your connector administrator:
* The OAuth 2.0 application's tenant ID and client ID that you recorded in step [2](https://servicenow-prod.fluidtopics.net/RzQ3WOjdaYGH2aCdqNLVWA#configure-microsoft-viva-engage-external-content-indexing__client-tenant-ids-step).
* The client secret value that you recorded in step [3.d](https://servicenow-prod.fluidtopics.net/RzQ3WOjdaYGH2aCdqNLVWA#configure-microsoft-viva-engage-external-content-indexing__copy-client-secret).
{#configure-microsoft-viva-engage-external-content-indexing__ul_rl2_xjd_tdc}
Your connector administrator needs these items to configure a Microsoft Viva Engage external content connector to retrieve searchable content and security principals from your Microsoft Viva Engage instance.
For details on creating and configuring a Microsoft Viva Engage external content connector, see [Create a Microsoft Viva Engage external content connector](https://servicenow-prod.fluidtopics.net/hYbDuJiz3VVibEu7~WaFIg "Create an external content connector to retrieve searchable content and security principals from your Microsoft Viva Engage source system.").
*[\>]: and then