---
sourceDocument: Australia Employee Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/employee-service-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Employee Service Management

ft:clusterId :

    - emplsm

bundleId :

    - emplsm

workflow :

    - Employee


---

# Integrating ServiceNow with Microsoft Teams and Microsoft 365

# Integrating ServiceNow with Microsoft Teams and Microsoft 365 {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Integrating ServiceNow with Microsoft Teams and Microsoft 365

This guide outlines the integration of your ServiceNow instance with Microsoft Teams and Microsoft 365 applications, detailing the necessary roles, configurations, and planning needed for successful integration.
It is important to note that the ServiceNow for Microsoft Teams has been upgraded to ServiceNow for Microsoft 365, effective from specific versions.
Show full answer Show less  

## Key Features

* **Role Requirements:** To authorize applications, users need the *externalappinstalladmin* role and the *application administrator* role in Microsoft Office 365.
* **Tenant Types:** Azure Active Directory organizes users and apps into tenants. Self-configured apps are available only within their home tenant, whereas pre-published apps can be used across multiple tenants.
* **App Configuration:** You can choose between self-configured or pre-published app configurations based on your integration needs. Pre-published apps simplify the process, while self-configured apps provide more control and customization.

## Key Outcomes

* Seamless integration between ServiceNow and Microsoft Teams or Microsoft 365 enhances collaboration and service management.
* Choosing the right app configuration based on your integration scenario optimizes performance and user experience.
* Proper setup and planning will ensure that your ServiceNow instance is effectively connected to Microsoft Teams, facilitating improved operational efficiency.  
Set up your ServiceNow instance to integrate Microsoft Teams or Microsoft 365 applications.  
Important:  
* From [IT Service Management for Microsoft 365](https://store.servicenow.com/sn_appstore_store.do#!/store/application/14eb9da8c3f310102986a81c8640dd08/2.6.7?referer=/store/product/9389b69edbb8e810d27e581adc9619ca) (version 2.6.7), ServiceNow for Microsoft Teams is upgraded to ServiceNow for Microsoft 365.
* From [HR Service Delivery for Microsoft 365](https://store.servicenow.com/sn_appstore_store.do#!/store/application/23364660c3b31010aab55b79c840ddc2/3.3.6?referer=/store/product/9389b69edbb8e810d27e581adc9619ca) (version 3.3.6), ServiceNow for Microsoft Teams is upgraded to ServiceNow for Microsoft 365.

{#setup-sn-ms-teams__ul_onl_tyv_dzb}

For upgrading existing Microsoft Teams capabilities to Microsoft 365 applications, see [Integrating ServiceNow with Microsoft 365 applications for Employee Experience](https://servicenow-prod.fluidtopics.net/GSIpknbQSijhOpKE476A1Q "Set up your ServiceNow Employee Center instance to integrate Microsoft 365 applications.").

To connect your ServiceNow instance to your Microsoft Office 365 tenant and to authorize applications, you must have both the
external_app_install_admin role and the application administrator role in Microsoft Office 365. For more information on Microsoft roles, see the Microsoft
documentation on [Azure AD built-in roles](https://docs.microsoft.com/en-us/azure/active-directory/roles/permissions-reference#available-roles).

Azure Active Directory (Azure AD) organizes objects like users and apps into groups called
tenants.

Self-configured apps (previously referred to as single-tenant) are available only in the tenant they were registered in, also known as their home tenant. Here, a single Microsoft Teams tenant is connected to multiple ServiceNow instances.

Pre-published apps (previously referred to as multi-tenant) are available to users in both their home tenants and other tenants. Here, a single Microsoft Teams tenant is connected to a single ServiceNow instance.
{#setup-sn-ms-teams__table_xbv_qmm_ktb__entry__2}

| Pre-published app | Self-configured app |
|-|-|
| * The relevant Microsoft Azure app is provided by ServiceNow so you don't need to create your own. No need to create an app in the Microsoft Azure portal. Moderate Microsoft Azure expertise is required. * Once the administrator consents, ServiceNow automatically updates the Microsoft Azure app. {#setup-sn-ms-teams__ul_xb2_s2f_ktb} | * You must create your own app in the Microsoft Azure portal. Requires proficiency in Microsoft Azure portal. * Own and control the Microsoft Azure app. {#setup-sn-ms-teams__ul_hvl_t2f_ktb} |
[Table 1. Choose between a self-configured app and a pre-published app configuration]

{#setup-sn-ms-teams__table_xbv_qmm_ktb}

When you consent to the app to use the required permissions, a Service Principal (SP) is created representing the Microsoft Azure app. For more information about the admin consent, see [Understand user and admin consent](https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-convert-app-to-be-multi-tenant#understand-user-and-admin-consent).

In a self-configured app configuration, you must create an app in Microsoft Azure portal and use the app ID and the client ID values to connect to your ServiceNow instance.

## When to use Pre-published app or Self-configured app configuration {#setup-sn-ms-teams__section_c23_5ll_lfc}

Use the self-configured app or pre-published app configuration based on the following conditions:

* In case of a single Microsoft tenant to multiple ServiceNow® instances integration, use the self-configured configuration setup.
* In case of a single Microsoft tenant to single ServiceNow® instance integration, it is recommend to use the pre-published configuration setup. However, you can still use the self-configured configuration setup.
* In case of a single ServiceNow® instance to multiple Microsoft tenant integration, use the Self-configured configuration setup.
{#setup-sn-ms-teams__ul_uyw_tll_lfc}
* **[Plan your installation](https://servicenow-prod.fluidtopics.net/1LbEtcwaRy6~8L3FbW18HA)**   
  Identify the need and plan your installation for ServiceNow® for Microsoft Teams.
* **[Setting up the ServiceNow instance for Microsoft Teams integration](https://servicenow-prod.fluidtopics.net/_loS_1jxf_uerKE9hZshIA)**   
  Set up your ServiceNow® instance for the Microsoft Teams integrations.

